2130 replies to this topic

[mirakels]

2nd try.

First attempt wnet wrong by some funny weird thing in the msguniq command.

 

The one that is used pushed sould be ok (famous last words)

[athoik]

2rd try much much better

 

Using the latest translations there are some untranslated menus (although translation exists).

 screenshot.jpg   58.25KB   35 downloads

 

 

#, fuzzy
msgid "Service searching"
msgstr "Αναζήτηση υπηρεσιών"

msgid "Manual Scan"
msgstr "Χειροκίνητη Ανίχνευση"

#, fuzzy
msgid "Manual scan"
msgstr "Χειροκίνητη ανίχνευση"

 

Is it possible Fuzzy flag causing that? Any idea?

Edited by athoik, 6 October 2013 - 12:03.

[Frogman]

Updated german .po-file (with some few strings at the end which are missing in the new-generated po-file)

Attached Files

•  de_po.zip   50.84KB   7 downloads

[Taapat]

Updated latvian translations.

Use what you like better- patch or po file.

Attached Files

•  0001-Latvian-translations.patch.zip   9.24KB   3 downloads
•  lv.po.zip   49.88KB   4 downloads

[pieterg]

Yes, please read the gettext manual on the fuzzy flag, such messages are ignored.

[mirakels]

So basically it means that the .po generator tools found a matching translation in the  obsolete area (#~ lines) but is not sure if the new string really matches.

 

So translators should check the 'fuzzy' marked messages and remove the fuzzy keyword if the translation is correct or is corrected.

 

Do you agree pieterg?

[Rob van der Does]

And entries marked 'fuzzy' are not being used by E2?

[mirakels]

pushed german and latvian translations.

 

@Frogman: I don't think the 'extra' messages are of any use as these text apparently are not part of the enigma2 translatable messages. Maybe you took some strings from plugins?

 

@all: there is no real use in adding translated strings if the translated string is exactly the same as the original one. E.g.:L:

 

msgid " (PiP)"
msgstr " (PiP)"
 

is just a bit of waste of time. When a msgstr is empy, the msgid will just be used.

It does not hurt (exept maybe the extra space needed), but it just takes valuable time from you as translater ...

[pieterg]

And entries marked 'fuzzy' are not being used by E2?

Fuzzy translations are 'less than 100% matches' so they need human corrections, wouldn't make sense to just use them.

[Frogman]

@Frogman: I don't think the 'extra' messages are of any use as these text apparently are not part of the enigma2 translatable messages. Maybe you took some strings from plugins?

 

No, that are messages of standard PLi like e.g.

 

msgid "Choose your Skin"
msgstr "Skin Auswahl"

 

which can be found in the top line of the skin selection screen using the standard PLi-HD skin - and it's translatable. Also some other strings like 

 

msgid "dreambox advanced remote control (native)"
msgstr "Receiver Erweiterte Fernbedienung (nativ)"

Edited by Frogman, 6 October 2013 - 22:40.

[Rob van der Does]

And entries marked 'fuzzy' are not being used by E2?

Fuzzy translations are 'less than 100% matches' so they need human corrections, wouldn't make sense to just use them.

Of course. I only wanted to know if E2 indeed doesn't use them.
So in fact the 'fuzzy's' are only there as a suggestion for the translator.

[BoxFreak]

Hello,

 

Could you please merge in the changes I posted here "28 May 2013 - 08:24" (on page 27) for fi.po. After that I can start to work on the new untranslated lines.

There were also some translations for plugins that were not previously translated in finnish... Thanks in advance.

[mirakels]

Hm merging older patches after a new set of .po files haven been generated might be quite a challenge.

 

I have never used any of the tools to do translations so have no clue on how the work. However, I would expect that a good tool would be able to load the latest version of a .po file and merge any translations from an older version into it.

In that case you should be able to get the latest .po version, import your older translations and add the translations for the new msgids.

Maybe someone here knows about available tools and can suggest how to such a thing?

[Dimitrij]

All the tools that I know work incorrectly.
The best tool is the man.

[pieterg]

gettext merges quite well (every potential merge conflict will be made available as fuzzy, so hardly any translation work is ever lost)

The procedure would be:
-revert the pofile to the old version
-apply the patch to the old po
-regenerate the pofiles
-check the resulting pofile, correct fuzzy translations
-commit the result

[Frogman]

POEdit can also merge po-files: just open the old one, then go to "Catalog => Update from POT file...", change the suffix to any files (.*) and select the new po-file. Old strings will be removed and new ones will be added.

[ims]

updated cs language

 

 

btw - there in PicturePlayer's ui.py is typo:  "Fulview resulution" 

Attached Files

•  0001-updated-cs-translate.patch.tar.gz   9.25KB   6 downloads

Edited by ims, 7 October 2013 - 13:16.

[Bag58]

So actually there are two typo's then in these two words, right?

[ims]

Yes, but I think, this can be changed in finished .po files later (and in .py) with some script by team.

[mirakels]

gettext merges quite well (every potential merge conflict will be made available as fuzzy, so hardly any translation work is ever lost)

The procedure would be:
-revert the pofile to the old version
-apply the patch to the old po
-regenerate the pofiles
-check the resulting pofile, correct fuzzy translations
-commit the result

 

 

POEdit can also merge po-files: just open the old one, then go to "Catalog => Update from POT file...", change the suffix to any files (.*) and select the new po-file. Old strings will be removed and new ones will be added.

 

I think we prefer Frogman's method!

 

 

So everyone, when your translations from before the last pot update did not make it into the repository, please recreate you .po file using POedit  as described above.