Il giorno ven, 23/12/2005 alle 02.15 +0900, JC Helary ha scritto: > > Are there so many advantages using xliff? I do not nothing about this > > format I just started googling. > > maybe you want to look at these links besides for all the oasis pages: > http://xliff-tools.freedesktop.org/snapshots/po-repr-guide/wd-xliff- > profile-po.html > http://xml.sys-con.com/read/121957_1.htm) I will go and study ASAP. > there are a number of tools that handle documentation files in xliff > while I don't see how an html manual could confortably (for the > translator that is) be handled as a .po file. I always think about HTML manuals are they are generated by SGML/XML DocBooks that can be translated using po4a and tools of this sort. It's my fault I did't know other way to manage translation different from po or XML/SGML code. My experience is that after gnome documentation adopted po convertion for manuals italian translation speeded up. This sound like the example of the hammer, if you know how to use the hammer all the world is made by nails. ;) > Right now, when you have the GUI as .po and the rest as whatever > format, how do you leverage the memories from the .po translation to > the doc translation and reciprocally ? Memories in translation tools should be a good improvement. > also the fact that using xliff will open the world of gettext > localization to the rest of the localization world and most probably > drive non-gettext localizers to the world of free software. We hope. There is lots of free software widly used that need to be internationalized, too. Bye Stefano -- Stefano Canepa aka sc: sc@linux.it http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall)
Attachment:
signature.asc
Description: This is a digitally signed message part