Document the new approach for gnulib localization

2024-12-08 Thread Bruno Haible via Gnulib discussion list
And this patch finally documents approach (a) from <https://lists.gnu.org/archive/html/bug-gnulib/2024-12/msg00034.html>. 2024-12-08 Bruno Haible Document the new approach for gnulib localization. * doc/gnulib-tool.texi (Localization): Recommend to use the gnuli

Re: gnulib localization

2006-11-06 Thread Bruno Haible
Sergey Poznyakoff wrote: > The idea of a compendium textual domain, which > gnulib is at TP, is that a translator, preparing his localzation will > download it and merge with his translaton using msgmerge. Do you know how many translators actually do this? Very few, I would say. I don't have preci

Re: gnulib localization

2006-11-06 Thread Sergey Poznyakoff
Bruno Haible <[EMAIL PROTECTED]> wrote: > What's missing is that gnulib-tool copies the POT & PO files into the > destination project, possibly with measures to avoid collisions with other > versions, and/or arranges to define DEFAULT_TEXT_DOMAIN to "gnulib". I doubt it should. The idea of a com

Re: gnulib localization

2006-11-02 Thread Bruno Haible
Sergey Poznyakoff wrote: > The "gnulib" textual domain was defined exactly for that purpose. OK, that is good for the moment as well. It is quite well translated already, see http://www.iro.umontreal.ca/translation/registry.cgi?domain=gnulib . What's missing is that gnulib-tool copies the POT & P