I was thinking of handling it like the Linux kernel documentation...? On 1/26/09, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > On Mon, 26 Jan 2009, Peter Krefting wrote: >> Jakub Narebski wrote: >> >> > With GUI translations we just use gettext conventions. I don't know >> > any such convention for docs: >> >> There is a lot of documentation being translated using PO files. po4a - >> http://po4a.alioth.debian.org/ - is a nice starting point for that. > > I'm not sure if XLIFF wouldn't be better format to use to translate > _documents_. Gettext was meant to translate, I think, not very long > messages in programs. > > Also I am not sure how much support this idea has. True, in last Git > User's Survey[1] 63% to 76% wanted (parts of) Documentation... but that > was out of 325 people who answered this question, with 3236 responses > to survey in total, so numbers are more like 6% - 8%. > > [1] http://git.or.cz/gitwiki/GitSurvey2008 > [2] http://translate.sourceforge.net/wiki/ > > -- > Jakub Narebski > Poland > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
