2009/12/18 Dimitris Glezos <gle...@indifex.com>: > On Fri, Dec 18, 2009 at 3:23 PM, Nick Schermer <nickscher...@gmail.com> wrote: >> 2009/12/18 Mike Massonnet <mmasson...@gmail.com>: >>> 2009/12/18 Leandro Regueiro <leandro.regue...@gmail.com>: >>> Regarding the pot files, thanks Glezos for pointing out the "POT >>> intltool" option, however all the projects are setup with "POT" only, >>> so it seems. I can't edit them, and it will take someones full evening >>> to update them all. Anyhow, that sounds like a great solution :-) >> >> This does not work for components that have both a pot file for >> documentation and a pot file for the 'code'. Like terminal. /me will >> take care of all the other core components that do not fall in this >> category (as a start). > > Our design decision was the following: If there are two different > translatable modules, with potentially different settings (i18n > method, refresh frequency, etc), you can easily add them and manage > them as separate components in the project page. Just define the 'file > filter' in a way that limits each component to its directory > structure.
To all translators, I'll split the products that ship documentation in a (for example) master and master-docs component. The first one uses the generated intltool pot file from transifex the latter the pot file created by xml2po. Thanks Glezos for the info. Nick _______________________________________________ Xfce-i18n mailing list Xfce-i18n@xfce.org http://foo-projects.org/mailman/listinfo/xfce-i18n
