2009/4/21 Masato Hashimoto <[email protected]>: > On Tue, 21 Apr 2009 12:05:09 +0200 > Mike Massonnet <[email protected]> wrote: > >> 2009/4/20 Mike Massonnet <[email protected]>: >> > Masato Hashimoto wrote: >> >> >> >> Hi maintainers, >> >> >> >> I updated the following Japanese translations of po-doc. >> >> >> >> libexo/trunk/po-doc/ja.po >> >> thunar/trunk/po-doc/ja.po >> >> >> >> Could you make these documentation(xml, html)? >> >> Regards. >> >> Hi Masato, >> >> For what it's worth, the documentation works as following: >> >> In general, there is a po-doc directory set up. When you add a new po >> file, a new directory has to be set up where the docbook resides. It >> is specified within po-doc/Makefile.am and in general it is unders >> docs/. Once the directory is set up, in order to update the xml+html >> file you have to run: >> make -C po-doc update-xml; to update the xml.in files >> ./autogen.sh --enable-xsltproc --enable-xml2po; to compile the xml.in >> files to xml >> make -C docs; to build the docs >> >> When the documentation is being updated, the maintainer of the >> documentation (the developer in general) has to run: make -C po-doc >> update-po. Of course after that, he has to update the xml files. >> >> Cheers >> Mike > > Hi Mike, > > Well... I know the works that you mentioned by i18n-wiki. I always do it > on my local copy for testing (sometimes forget, though). > Or should I do any other actions to request for making documentation?
Ok, well the next time you can try to update the XML, perhaps you have write access already, otherwise keep posting on the ml. In the case of Thunar/Exo/Terminal, they have implied distcheck flags to build the xml and html files, which means final tarball have always up to date xml + html files. Other projects don't work like that. Its worth to always update them for users installing from svn. > Regards Mike _______________________________________________ Xfce-i18n mailing list [email protected] http://foo-projects.org/mailman/listinfo/xfce-i18n
