On 29 févr. 08, at 12:50, Aijin Kim wrote:
Hi Dick,
I don't have much experience with OmegaT. I think it's the best way
to ask community's help on this. :)
Hi all,
Some strings of po files have a line which was added to make each
msgid string be unique using --duplicates=msgid_comment
Hi all,
Some strings of po files have a line which was added to make each
msgid string be unique using --duplicates=msgid_comment option
during executing oo2po.
http://translate.sourceforge.net/wiki/toolkit/
duplicates_duplicatestyle
How can OmegaT or poedit handle the added line?
Since the
On Fri, Feb 29, 2008 at 7:04 AM, Jean-Christophe Helary
[EMAIL PROTECTED] wrote:
On 29 févr. 08, at 12:50, Aijin Kim wrote:
Hi Dick,
I don't have much experience with OmegaT. I think it's the best way
to ask community's help on this. :)
Hi all,
Some strings of po files have a
Hi JC,
I guess what Ain mentioned was that 'msgctxt' option during oo2po saves
the comment line in another field rather that adding to msgid fileld.
Then there won't be no change with msgid string.
So for current po files, do you simply ignore the comment line in your
translation?
Thanks,
Hi Ain,
Thanks for you comment.
Do you know if Poedit or OmegaT support msgctxt?
Aijin
Ain Vagula wrote:
Since the string is a msgid it is handled as a source string and is
displayed as translatable.
... thats one reason we switched to msgctxt comment style, where
identifier is
Dick Groskamp wrote:
[...]
AFAIK most Dutch translators use OmegaT but otherwise we have to make
some kind of switch
It's far from something I'm specialized in, but the last time I made a
contribution, I used Pootling (0.2.0). Maybe that dóes make a
difference? Pls. send me something to
Poedit supports from 1.3.8, dont know about OmegaT.
ain
On Fri, Feb 29, 2008 at 8:44 AM, Aijin Kim [EMAIL PROTECTED] wrote:
Hi Ain,
Thanks for you comment.
Do you know if Poedit or OmegaT support msgctxt?
Aijin
Ain Vagula wrote:
Since the string is a msgid it is handled as a
On 29 févr. 08, at 15:20, Aijin Kim wrote:
Hi JC,
I guess what Ain mentioned was that 'msgctxt' option during oo2po
saves the comment line in another field rather that adding to msgid
fileld. Then there won't be no change with msgid string.
So for current po files, do you simply ignore
Hi JC,
Thanks a lot for your kind explanation.
So you mean that you manually delete the msgid_comment part from each
target string?
If so, it should be better that source string doesn't include the
msgid_comment line in source string to avoid additional work, right?
Now, I'm thinking if we
