[Bf-committers] Complete absence of a POT file

[Jiří Hnídek]

Hi,
I wanted to convince Ton to start use gettext("") or _("") standard (I 
did some coding attempts too) but he was against: swithing on/off 
translation for tooltips, buttons and toolbox is much more important. 
This switching can be proceeded only at one place in source code, then 
gettext(string) can be called ... we can't use _("") standard.

xgettext is cool tool and in combination with other tools from gettext 
packege it can help translator very much.

Python script works very good, but we need replacement of xgettext. We 
need to parse all gui strings to .pot file (python script should do only 
this thing, but it should do parsing almost perfectly), that's all, 
msgmerge can manage the rest.

We need somebody, who will be boss for all translators (poke them, when 
new release is comming; propably do some testing; write some 
documentation for translators; no need to do any coding!!!). ANY 
VOLUNTEER? ;-)

Jiri

> Hi Blender developers!
> 
> Blender currently does not ship nor create a gettext PO template (a
> "*.pot" file). However, this is a necessary prerequisite for
> translating the application into other languages. Merely copying an
> existing PO file is error prone since they might be incomplete and
> outdated, and this does not provide any support for distribution
> specific patches either.
> 
> Because of the nonstandard way translations are handled in blender
> (the canonical gettext("string") or _("string") is not used), it is
> not easy to manually create a PO template with xgettext either.
> 
> How do you handle this? Is there any way to generate an up to date PO
> template in the source tree that I just did not discover? I did not
> find anything about this in the forum or in google.
> 
> Thanks in advance and have a nice day!
> 
> Martin