POT file for cpplib

["Martin v. Löwis"]

Joseph S. Myers wrote:
> My concern is what happens say six months from now when 3.5 branches.  
> Until then, translators working on gcc-3.4.x.pot will have been
> translating cpplib messages in gcc.pot.  What's necessary to avoid
> regressions is that all the work on these translations in gcc-3.4.x
> between now and when 3.5 branches gets carried forward to the cpplib
> translations.  If translators start *now* with using the gcc catalog as a
> starting point, then over the next several months some messages will be
> translated for gcc but not cpplib, and some vice versa, and some will get
> different translations that should be merged, and there will be a mess.  
> The proper instruction would be to concentrate on gcc.pot exclusively and
> not do any translation work on cpplib.pot until 3.5 has branched, and at
> that point start working using the then current gcc.pot translations as a
> base.

So you would like to withdraw the cpplib domain? If so, please say so.

I don't share your concerns. I'm not sure what regressions you are
talking about. If you think there might be translation which actually
break gcc/cpplip operations, we should find an algorithm that rejects
translations that potentially break gcc. If you are thinking about
mere typos - well, please do have some trust in translators getting
it right.

Regards,
Martin