On Fri, Mar 02, 2007 at 10:00:04AM +0100, Leandro Regueiro wrote:
On 3/1/07, Colin Marquardt <colin@...57...> wrote:
If you make a good manual I would translate it. I don't like the idea of use SVG for docs. Please use another format.
SVG can be converted to po with xml2po, so translators would have it as easy as with docbook. (I still like docbook for a task like a manual more.)
Of course I expect to translate using gettext or another handy system for translating. About the little helps and introductions in svg, I think that are helpful, but them don't replace a good manual in another format, unless the svg can be protected against changes by the readers. About the links to example in svg, I think that are the best solution.
I think there may be some confusion propagating here. In general I think the leading proposal is to use SVG only for example images, and to use Kevin's drupal system for the actual editing.
An idea being kicked around is that perhaps we could include a way to export to docbook, and from that into SVG just as we do with tutorials. Then it would be possible for people to read the manual in Inkscape just like the tutorials. But the SVG in this case would strictly be read-only, and no one would be editing content in SVG directly.
There is another idea (which I originated) to set up webdav on the server, to make it easier for people to edit and upload example svg images. It was acknowledged that text handling in Inkscape/SVG is not too good, especially as regards translation; for this reason it's not really worth giving serious consideration to the idea of editing the whole manual in SVG. It'd just be too painful.
Bryce