Posted 8 February 2017 - 11:28
sure, cpp files can use po. but what part of the cpp files show output that is directly shown on screen that needs to be translated?
As far as I know the C code is for pure lowlevel stuff and Python is for the user interface.
I think we do not want Chinese log messages as part of a crash description, do we?
Posted 8 February 2017 - 19:08
Would you please point me to a correct guide for it ? It seems I'm not the only one having problems with enigma2.pot creation.Why do we need a enigma2.pot?
Normally the enigma2.pot is generated automatically from the sources
For translations we have a specail thread: https://forums.openp...-post-them-here
Open Vision sources: https://github.com/OpenVisionE2
Posted 8 February 2017 - 19:40
There should be some description in that thread....
But basically translators work with th LANGUAGE.po files (e.g. nl.po). to add the translations.
The only thing we should do is regularly generate new .po files that include the new strings (when strings changes happened in the enigma2 python or xml files).
However so far this is still a manual process as they must be committed
The enigma2.pot files is not tracked in the enigma2 git. The .po files are
Posted 8 February 2017 - 19:45
Open Vision sources: https://github.com/OpenVisionE2
Posted 8 February 2017 - 23:21
Yes, I plead guilty (but in my defence, no of the other people in the team did so
This indeed is a bit of a weird thing. We should somehow automate this so it is done regularly (or even on every change...)
so guess what.... I rebuild the po files and pushed them!
Generating them gave below warnings:
RecordTimer.py:512: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/DiskInfo.py:38: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/EpgList.py:291: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Task.py:470: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/About.py:135: warning: Empty msgid. It is reserved by GNU gettext:
gettext("") returns the header entry with
meta information, not the empty string.
lib/python/Screens/AutoDiseqc.py:194: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/AutoDiseqc.py:284: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/ChannelSelection.py:1053: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/InfoBar.py:542: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/Ipkg.py:58: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/Ipkg.py:58: warning: 'msgid_plural' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/MovieSelection.py:1927: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Screens/PluginBrowser.py:128: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/ClientsStreaming.py:107: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/ClockToText.py:94: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/ClockToText.py:97: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/EventName.py:130: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/EventName.py:131: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/RemainingToText.py:58: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Components/Converter/RotorPosition.py:32: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Plugins/SystemPlugins/FastScan/plugin.py:100: warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
lib/python/Plugins/SystemPlugins/FastScan/plugin.py:100: warning: 'msgid_plural' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
Posted 9 February 2017 - 08:36
message = _("You must switch to the service %s (%s - '%s')!\n") % (type, self.service_ref.getServiceName(), self.name)
Of course, it is a possibility that in the some language these arguments it is better to use in a different order.
Edited by Taapat, 9 February 2017 - 08:39.
Posted 9 February 2017 - 10:11
yes I know they are warnings. It put it here just as a hint in case someone see a simple fix for (some of) them...
Posted 9 February 2017 - 11:20
Open Vision sources: https://github.com/OpenVisionE2
Posted 9 February 2017 - 12:16
so guess what.... I rebuild the po files and pushed them!
Before that, you could add my pull request where these new values already translated: https://github.com/O...nigma2/pull/634
Now, due to the POT-Creation-Date change, he has a conflict 
.
Posted 9 February 2017 - 15:46
Thanks a lot
I think if you do this every month it would be ok.
Did you remove obsolete strings too ?
yes the tooling does that automatically. The obsolete strings are put at the end of the .po file prefixed by a #.
It is up to the translators to remove these when they think they are really useless (some may be handy as the strings has been changed slightly and the translation can be easily reused (but that may depend on the editing tools again...))
Posted 9 February 2017 - 15:48
so guess what.... I rebuild the po files and pushed them!
Before that, you could add my pull request where these new values already translated: https://github.com/O...nigma2/pull/634
Now, due to the POT-Creation-Date change, he has a conflict
Sorry about that 
. This was probably one of the reason not to automate the .po generation process...
Is it hard to merge the changes back in your current copy as probably there are many new strings you have to translate now?
Posted 9 February 2017 - 16:05
Posted 9 February 2017 - 16:14
Ok I resolve conflict on github by myself.
Edited by Taapat, 9 February 2017 - 16:14.
Posted 11 February 2017 - 07:50
https://github.com/O...nigma2/pull/644 Update unicable.xml thanks to Open ATV
Edited by Persian Prince, 11 February 2017 - 07:50.
Open Vision sources: https://github.com/OpenVisionE2
Posted 11 February 2017 - 08:38
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 11 February 2017 - 09:04
https://github.com/O...nigma2/pull/645 Not related to unicable.xml though
Open Vision sources: https://github.com/OpenVisionE2
Posted 11 February 2017 - 16:21
https://github.com/O...nigma2/pull/645
github is such pain in ... because it automatically merges new commits in last merge request and I have to wait for it to be merged or closed.Open Vision sources: https://github.com/OpenVisionE2
Posted 11 February 2017 - 18:45
Edited by Taapat, 11 February 2017 - 18:45.
Posted 12 February 2017 - 11:36
https://github.com/O...nigma2/pull/648
https://github.com/O...nigma2/pull/650
https://github.com/O...nigma2/pull/653
Open Vision sources: https://github.com/OpenVisionE2
Posted 13 February 2017 - 10:55
https://github.com/O...nigma2/pull/657
https://github.com/O...nigma2/pull/658
https://github.com/O...nigma2/pull/659
Open Vision sources: https://github.com/OpenVisionE2
0 members, 3 guests, 0 anonymous users
