Georg Baum wrote:
Helge Hafting wrote:
1. Translations that doesn't work:
The menu items "Tools" and "New from template",
and quite a few other strings are untranslateable.
Some of these actually have a translation in the existing file,
but it doesn't take. The english text remains while all my other
changes works. What to do about such things?
Find out why it does not work?
Which is why I asked the question.
I have no idea what failure modes a "po" file can have.
I edit the strings, and sometimes the translated text isn't
used by lyx. I don't know why.
Looking at one example, "Document" (in the main menu) is
translated, but lyx doesn't use it. Looking closer, it seems that
the line number is off by two.
Should I fix the line numbers in such cases, or is there an automated
way of doing that? The po-file probably wasn't written by hand
originally?
2. Obviously wrong translations:
Not bad work by the previous translator, but stuff that can't be right
because the translated string have nothing at all to do with the message.
It may even be another unrelated _english_ string where
the norwegian one should be.
I am not sure if I understand this correctly, but if you mean the case that
one english string needs two differrent norwegian translations depending on
context we have a mechanism for that:
Not what I meant.
I wondered why the distributed no.po contains oddities like:
msgid "Objectname"
msgstr "Octave"
which is obviously wrong. It is a mistake nobody could possibly make
in translation. (Not a misspelling, not a slightly bad choice of words)
so it just have to be some sort of software screwup.
"To:[[as in 'From page x to page y']]" and
"To:[[as in 'From format x to format y']]" appear both as "To:" in the
english version, but you have different translatable strings.
Nice to know that such a mechanism exists.
Helge Hafting
