On Wed, 15 Jun 2011 16:24:56 -0600, Alex Rousskov wrote:
On 06/15/2011 03:17 PM, Tsantilas Christos wrote:
From what I can understand a translator will use a program like the
poedit to read the above output and produce a new file for a
language.
For example the error-details.txt.el.po file.
I thought the translation blobs produced by your script will go into
existing .po files that are already used for translating error pages
and
such. In other words, for any supported language, Squid will have a
single .po file that Squid loads and uses for translations. Am I off
track here? Amos?
That was the idea. Yes.
- the English "template" version of error-details.txt needs to go in
errors/error-details.txt,
- scripts/update-pot.sh needs to run your convert right after the
per-page dictionaries for-loop. and before the call to msgcat. You can
see from that for-loop where the resulting .po needs to be.
That gets it into the system for people to translate.
As for getting it out again....
I think po2text in error/Makefile.am ".po.lang:" target should
produce the translated version of errors/el/error-details.txt or
errors/error-details.el.txt / .txt.el
Then the question becomes, how do we allow the admin to edit the
results? an /etc/squid/error-details.txt which loads first and overrides
anything we provide?
Amos
