-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am 19.02.14 03:30, schrieb Warren Block: > On Tue, 18 Feb 2014, Benedict Reuschling wrote: > >> Another tool is textproc/po4a that Thomas Abthorpe showed me on >> one of the hacker lounges two years ago in Canada. He set up a >> test project for a translation into en_GB to see how these tools >> fit our toolchain. >> >> He send me the following mini-howto, which I extended a bit for >> a first commit to the german doc repo recently: >> >> <mini-howto> install textproc/po4a install editors/poedit # >> optional install devel/gtranslator #optional install lokalize # >> somewhere in kde4, too lazy to look >> >> To prep a new translation, inline, same directory the following >> works. Substitute en_GB for the language of your choice. >> >> po4a-gettextize -f xml -m article.sgml -p article.pot # renders >> to pot file > > I can use poedit to do the translation, but I always get > article.pot:7: header field 'Project-Id-Version' still has the > initial default value >
I have this in my pot file header: "Project-Id-Version: 1\n" "Language: de\n" I guess we need to fill these automatically when a new or an updated translation is created. Maybe we could fill in some values from SVN (revision comes to mind) or use some kind of auto-incrementing counter for each new translated document. These are the things we need to figure out. Another question is: do we keep those po files holding the translated strings in our doc repo alongside the translation? Or do only the translation projects keep them for themselves? > It does appear to save the translations to article.pot, this is > something to do with catalogs. Manually editing article.pot and > setting "Language: \n" to "Language: en_GB\n" then complains about > the "Project-Id-Version" line having a default value. > >> I put everything in the DevSummit wiki page and will start a >> separate one with the results from the summit to continue from >> there: >> >> https://wiki.freebsd.org/201405DevSummit/Translation > > The instructions don't seem to be there. On another page? Well, I thought about putting them there, but decided against it as I want the discussion to be open rather than present a solution beforehand. Maybe someone else knows a better tool. I will demonstrate it, but will also show the current drawbacks and what I see with my translator hat on. The process in the mini-howto will get you started for sure, but it is very open for improvement. Cheers Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTBPqSAAoJEAQa31nbPD2LjGQIALfGCjQy5elI6L7hFxlRVkop c3OfKQLh8RuemK52ShxrdAv5m4BQng1PPIh28IFWBnEWgTKxUmg0pcMXwtvfvnUG zbLLmz9CZ2IUmyGJ19CRkqN9ImJZgdbnrxfKuCtRP6Qn83xIPYBTIRqI7c8thDvq Z6hlYVOnJ4hop+4FSLh6AqMnMTC/P38W1ekZb63RD/qA9YyF9lmO3wP5CNmey0Gk OWTa7XfY4eFpnokq/KCi6ysH9vYwmrvHirF/9IW6XT9XYjWxTJVN9Gnn07rBJZx3 O2qv6yucUitXOqhaFsZIci6cDt4MNcZzpyMjzqJW0u+pHutbs20zQKvueciBGGk= =FKUq -----END PGP SIGNATURE----- _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "[email protected]"
