<br><div class="gmail_quote">2009/3/22 Yaakov Nemoy <span dir="ltr"><<a href="mailto:loupgaroublond@gmail.com">loupgaroublond@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009/3/21 Matthew Daniels <<a href="mailto:danielsmw@gmail.com" target="_blank">danielsmw@gmail.com</a>>:<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Satya,<br>
<br>
A docbook XML editor, especially web-based as you propose, could definitely<br>
be useful for the docs team. I don't think it would totally eliminate the<br>
need to know XML, but it doesn't need to. Just giving a way for contributers<br>
to write content without having to learn a rich markup language would<br>
probably mean we could recruit more people and get things done faster.<br>
<br>
Keep us updated on your progress!<br>
</blockquote>
<br></div>
I've also found that for some people (myself included) that having WSYWIG and XML side by side can work as a good on the job learning aid. You could certainly market it as away for beginners to get used to working with XML.</blockquote>
<div><br>I almost wrote that in my earlier post, and concur with Yaakov. Being able to see the code is also good for diagnostics (for both the human and machine editors). <br><br>If you need people to contribute comments about why this would be valuable, feel free to contact me. <br>
</div></div><br clear="all"><br>-- <br>-- <br>| Karen G. Schneider<br>| Community Librarian<br>| Equinox Software Inc. "The Evergreen Experts"<br>| Toll-free: 1.877.Open.ILS (1.877.673.6457) x712<br>| <a href="mailto:kgs@esilibrary.com">kgs@esilibrary.com</a><br>
| Web: <a href="http://www.esilibrary.com">http://www.esilibrary.com</a><br>| Be a part of the Evergreen International Conference, May 20-22, 2009!<br>| <a href="http://www.solinet.net/evergreen">http://www.solinet.net/evergreen</a> <br>