[Po4a-devel] Re: po4a README.maintainers

Hello, Nicolas François <nicolas.francois(a)centraliens.net&gt; (11/02/2006): As Denis said, you should also document the situation when there are several POT files. Quoting Denis: I'm not sure this is the best solution, as it is hard to refactor addenda, for example. Maybe: / /doc/ /doc/en/ /doc/en/<pkg1>/ /doc/po4a/ /doc/po4a/add_<ll>/ /doc/po4a/<pkg1>/ /doc/po4a/<pkg1>/po4a.cfg /doc/po4a/<pkg1>/po/ /doc/<ll>/ /doc/<ll>/<pkg1>/ Mostly yes. and defoma, menu (switches made and sleeping in the BTS) Valéry Perrin promised me to make the switch for man-db debconf will switch in a few days, once Cyril Brulebois has finished to update the French translation (the patch is nearly ready). And maybe some others. About the README.maintainers: * I have made a few minor corrections, but I'm not a native-speaker, just as you, so my corrections may be wrong :-) * Sentences added about the autoconf check * Sentences added for distribution-specific build systems. I really think that using po4a should not depend on the distribution, so the use of debian/rules is a mistake. * I'm not sure about this paragraph: We recommend to use a configuration file with po4a that does not require any option (put the options in the configuration file). This permits to easily check that the POT is up-to-date with the documentation and that the Unless the missing end of the sentence is really convincing, IMO, the use of external options is not a problem, and may ease the portability of the configuration file. As Denis said, translators should not care about the sources. The document regeneration should be documented, so that it is as easy for the translator to adapt the configuration file or the Makefile. Cheers, -- Thomas Huriaux