Jean-Marc Lasgouttes wrote:
"Helge" == Helge Hafting <[EMAIL PROTECTED]> writes:
Helge> I guess I now have to check out the new nb.po and re-do all my
Helge> changes? Or is there a simpler way? Using the existing patch
Helge> will reset a lot of line numbers in the po file - I guess that
Helge> won't work too well.
Yes, the po files were modified in the mean time. If you have a
complete lyx-devel tree, you can do "make nb.po-update" and your po
file should be updated with the new entries.
I tried that - with hopeless results:
With my nb.po:
$ make nb.gmo
rm -f nb.gmo && /usr/bin/msgfmt -c --statistics -o nb.gmo nb.po
2225 translated messages, 92 fuzzy translations, 525 untranslated messages.
Note the number of translated messages
make nb.po-update
nb:
msgmerge nb.po lyx-unicode.pot -o nb.new.po
.........[removed lots of dots]...... done.
$ make nb.gmo
rm -f nb.gmo && /usr/bin/msgfmt -c --statistics -o nb.gmo nb.po
2070 translated messages, 211 fuzzy translations, 536 untranslated messages.
Ouch! Lots of stuff lost! Running the resulting lyx looks more like
LyX-1.5 before I translated new stuff. Only a few new strings survived.
Something clearly went wrong here - many strings was
lost and is no longer in the po file. Such as the menu entry
"Cross-Reference".
Norwegian LyX now shows the english "Cross-Reference"
and the string is not translateable.
Looking closer at the po file, I see:
#: lib/ui/classic.ui:218 lib/ui/stdmenus.ui:266
msgid "Cross-reference...|r"
msgstr "Kryssreferanse...|K"
So it seems msgmerge thinks this is now written with a lowercase "r"
in "reference". Looking up the files in question however shows:
grep Cross < ../lib/ui/classic.ui
Item "Cross-reference...|r" "dialog-show-new-inset ref"
grep Cross < ../lib/ui/stdmenus.inc
Item "Cross-Reference...|R" "dialog-show-new-inset ref"
Hm - msgmerge thinks "Cross-reference" and "Cross-Reference"
is the same string - and runtime Lyx do not ???
I believe I have the full sources, I ran svn update today.
Anything special I need to do to make this work right?
It looks like msgmerge merges strings in a wrong way?
Helge Hafting
