Hi Taco,
I would try Xavier's suggestion.
Unfortunately what you are seeing is what we should probably call the
Plone hack. What we should be doing is beating programmers who use this
hack over the head with piles of wet printed copies of PO files.
Perhaps then it will beat some sense into their heads. I honestly have
no idea how they actually hope that translators will translate the file.
What they have inserted into msgid should go into #: and the English
text must go into msgid. These are the consequences of this hack:
1. Any editor will battle with this type of file, including Pootle
2. All information that the translator expects will be in the wrong
place
3. Translators might actually translate the location id as if it
was the real text
4. All the Gettext tools will have problems; thus you can't
leverage any of their value.
5. All advantage of TM is lost since you cannot align source with
target.
But hey I guess it makes it easier for the programmer, no idea why or
how though. Perhaps actually getting someone to localise the software
is not that important. The PO file was designed in a certain way for a
certain reason, there are a million ways to achieve what they want to do
and still hide the translator from the hack.
</rant>
So please try poswap and tell us if it can help to get around this
problem :)
On Wed, 2007-11-07 at 20:45 -0300, Xavier Alvarez wrote:
> Taco,
>
> If I understand correctly, in your POT you have tokens as msgids
> and the 'real text' is in the en.PO ... And what you wish to do
> is have translators see the 'real text' when translating instead
> of the tokens, right?
>
> I don't know if it applies but, "poswap"[1] in the toolkit[2] may
> be what you are looking for. I've never used it though, but
> here's what the comment says:
>
> "This tool builds a new translation file with the target text
> (translation) of the input file(s) as source language of the
> output file it creates. As an example, this makes it possible to
> have French as the source file for translation, rather than
> English. poswap was introduced in version 1.0 of the translate
> toolkit.
>
> Note that this requires no change in the software project and is
> only a manipulation of the strings in the existing files. The
> only requirement for this tool is a French translation."
>
> In your case you would probably feed the en.PO as the in-between
> language... but I'm just guessing :)
>
>
> Cheers,
> Xavier
>
> [1] http://translate.sourceforge.net/wiki/toolkit/poswap
> [2] http://translate.sourceforge.net/wiki/toolkit/index
>
>
>
> On Wednesday 07 November 2007 14:56, Lars Kruse wrote:
> LK> Hi,
> LK>
> LK> > So let me rephrase my question:
> LK> >
> LK> > We have a lot of .po files for the english language.
> LK> > Example from wizard.po file:
> LK> >
> LK> > msgid "addressField"
> LK> > msgstr "Full Address"
> LK> >
> LK> > We have added languages to the project using the same .po
> LK> > file but with empty msgstr:
> LK> > msgid "addressField"
> LK> > msgstr ""
> LK> >
> LK> > So my question is: how does pootle determine where to get
> LK> > the original msgstr from.
> LK> > Currently the 'Original' field shows the msgid
> LK> > "addressField" which does not help much translating.
> LK>
> LK> As far as I know, this design is not the common way of using
> LK> po-files. Usually the "msgid" is the english text and the
> LK> "msgstr" contains the translation. With your way of doing
> LK> it, it will be hard for common tools to recognize, which
> LK> translations are outdated or fuzzy, or?
> LK>
> LK> Maybe you could use a kind of mapping instead? For example a
> LK> file that combines your short names (e.g. "addressField")
> LK> and the english translations? This could be the source for
> LK> the po-files.
> LK>
> LK> just a thought ...
> LK>
> LK> Lars
> LK>
> LK>
> ----------------------------------------------------------------
> ---------
> LK> This SF.net email is sponsored by: Splunk Inc.
> LK> Still grepping through log files to find problems? Stop.
> LK> Now Search log events and configuration files using AJAX and
> LK> a browser.
> LK> Download your FREE copy of Splunk now >>
> http://get.splunk.com/ LK>
> _______________________________________________
> LK> Translate-pootle mailing list
> LK> [email protected]
> LK> https://lists.sourceforge.net/lists/listinfo/translate-pootle
> LK>
>
--
Dwayne Bailey
Translate.org.za
+27-12-460-1095 (w)
+27-83-443-7114 (cell)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle
