Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

ViX in your own language? Read how easy it has been made to help!

Status
Not open for further replies.
Localization is the image of the VIX, but the original files are far from all the strings that I consider to be localized. So is there a lot of extra strings, there are some strings that locate and plug-ins that are not part Vix image, or those for which I not get the original po files. In addition, there are some strings in multiple forms. Basically, my location is somewhat universal, because most of the image I'm trying different teams and each time I have to localize, because nowhere are translated in whole or foundations. If you use yours for just the files location will contain approximately 50% of the graphical interface. my location if you do not want or can not use, so I do not mind. Basically I'm doing it for myself and after each update you again move in Vu + Una necessary ingredients.
Hi, jerry.

Sorry for my bad English

please use this file, i have merged yours with mine.
 

Attachments

Localization is the image of the VIX, but the original files are far from all the strings that I consider to be localized. So is there a lot of extra strings, there are some strings that locate and plug-ins that are not part Vix image, or those for which I not get the original po files. In addition, there are some strings in multiple forms. Basically, my location is somewhat universal, because most of the image I'm trying different teams and each time I have to localize, because nowhere are translated in whole or foundations. If you use yours for just the files location will contain approximately 50% of the graphical interface. my location if you do not want or can not use, so I do not mind. Basically I'm doing it for myself and after each update you again move in Vu + Una necessary ingredients.
Hi, jerry.

Sorry for my bad English

please use this file, i have merged yours with mine.
 

Attachments

if you look at the po above i have attached there are load are translations to be fixed.

Tak bohužel. Mořím se s tím už 8 hodin a výsledek je ten, že oproti mé původní lokalizaci ta vaše na VU+Uno nefunguje.Problémy jsou většinou s řetězci, kde se nachází STB_BOX. Někde dojde ke správné identifikaci, ale většinou ne. Dále v té vaší chybí i nadále některé řetězce. Když aktivuji ty mé , které jsou zakázané #~ ,tak lokalizace naběhne.To samé platí i pro řetězce s STB_BOX ,kde nahrazením za VU+ Uno se lokalizace taktéž zobrazuje správně.
Zatím to ještě nemám zcela zprovozněné. Až to dodělám pošlu to na fórum.

So, unfortunately. Seas mean 8 hours and the result is that compared to my original localization of yours to the VU Uno does not work.The problems are mostly with the string, where is the STB_BOX. Somewhere there is a correct identification, but usually no further in your missing continue to be some of the string. When I activate my which are prohibited # ~, so be booted localization.The same is true for strings with STB_BOX, where replacing a VU Uno, localization also displays correctly.
So far, I haven't completely turnkey. When I'm done I'll send it to the Forum.

In the meantime I found a typo in en strings:
msgid ""
"Itmes in trashcan will be deleted if less then the set space is available."
msgstr ""
"Položky v koši budou smazány ,pokud je méně místa, než je nastavené." ######### Itmes=Items?
 
if you look at the po above i have attached there are load are translations to be fixed.

Tak bohužel. Mořím se s tím už 8 hodin a výsledek je ten, že oproti mé původní lokalizaci ta vaše na VU+Uno nefunguje.Problémy jsou většinou s řetězci, kde se nachází STB_BOX. Někde dojde ke správné identifikaci, ale většinou ne. Dále v té vaší chybí i nadále některé řetězce. Když aktivuji ty mé , které jsou zakázané #~ ,tak lokalizace naběhne.To samé platí i pro řetězce s STB_BOX ,kde nahrazením za VU+ Uno se lokalizace taktéž zobrazuje správně.
Zatím to ještě nemám zcela zprovozněné. Až to dodělám pošlu to na fórum.

So, unfortunately. Seas mean 8 hours and the result is that compared to my original localization of yours to the VU Uno does not work.The problems are mostly with the string, where is the STB_BOX. Somewhere there is a correct identification, but usually no further in your missing continue to be some of the string. When I activate my which are prohibited # ~, so be booted localization.The same is true for strings with STB_BOX, where replacing a VU Uno, localization also displays correctly.
So far, I haven't completely turnkey. When I'm done I'll send it to the Forum.

In the meantime I found a typo in en strings:
msgid ""
"Itmes in trashcan will be deleted if less then the set space is available."
msgstr ""
"Položky v koši budou smazány ,pokud je méně místa, než je nastavené." ######### Itmes=Items?
 
As in my first post: 'STB_BOX' should be left as it is. During the building of an image this will automatically be replaced by the real name of the box the build is made for.
And the English text in the file should never be changed at all. Did you use 'POEDIT' to facilitate your translations?
 
As in my first post: 'STB_BOX' should be left as it is. During the building of an image this will automatically be replaced by the real name of the box the build is made for.
And the English text in the file should never be changed at all. Did you use 'POEDIT' to facilitate your translations?
 
And the English text in the file should never be changed at all.

I suppose the English text being used as an index key, so they shouldn't be changed. But, if any of them has typo, what do you do to correct it? Do you leave it alone and create new correct one?
 
Last edited by a moderator:
And the English text in the file should never be changed at all.

I suppose the English text being used as an index key, so they shouldn't be changed. But, if any of them has typo, what do you do to correct it? Do you leave it alone and create new correct one?
 
I suppose the English text being used as an index key, so they shouldn't be changed. But, if any of them has typo, what do you do to correct it? Do you leave it alone and create new correct one?
Never change it in the file: just post a remark here, and it will be picked up. Then (after some time) it will appear in the po-file, and will need a translation.
 
I suppose the English text being used as an index key, so they shouldn't be changed. But, if any of them has typo, what do you do to correct it? Do you leave it alone and create new correct one?
Never change it in the file: just post a remark here, and it will be picked up. Then (after some time) it will appear in the po-file, and will need a translation.
 
As in my first post: 'STB_BOX' should be left as it is. During the building of an image this will automatically be replaced by the real name of the box the build is made for.
And the English text in the file should never be changed at all. Did you use 'POEDIT' to facilitate your translations?

We talk about a situation where we recreate the file from "andyblac" .He locates by TextEdit in iMac, then from him in PoEdit create mo file to upload VU+Uno, a try Enigmu. Each team probably adapts the original enigma of Dreambox chain and may be slightly or completely different.

Eg.: Image Manager and BH Image Manager or Image manager etc. Similarly, you can even edit the original po file (when no other way) because they obviously are not in the en po file after some strings correctly:
Eg.: Na VU+Uno není funkční třeba řetězec "Set your Drembox settings." But when I change the "Set your VU+ Uno Settings." then displayed in the GUI correctly. Similarly, it keeps me in your image (Vix) :
#, python-format
msgid ""
"Your STB_BOX will be restarted after the installation of service\n"
"Ready to install \"%s\" ?"
msgstr ""
"Váš STB_BOX se po instalaci služby restartuje\n"
"Chcete nainstalovat \"%s\" ?" .....................................Non localizet in czech Gui...

#, python-format
msgid ""
"Your VU+ Uno will be restarted after the installation of service\n"
"Ready to install \"%s\" ?"
msgstr ""
"Váš VU+ Uno se po instalaci služby restartuje\n"
"Chcete nainstalovat \"%s\" ?" ....................................is localized in czech GUI.

It's not a mistake translator, but there must be some error in the scripts, or somewhere similar. I'm not programmer or linux not control. I just wanted to help at least one image to follow the Czech localization.
 
As in my first post: 'STB_BOX' should be left as it is. During the building of an image this will automatically be replaced by the real name of the box the build is made for.
And the English text in the file should never be changed at all. Did you use 'POEDIT' to facilitate your translations?

We talk about a situation where we recreate the file from "andyblac" .He locates by TextEdit in iMac, then from him in PoEdit create mo file to upload VU+Uno, a try Enigmu. Each team probably adapts the original enigma of Dreambox chain and may be slightly or completely different.

Eg.: Image Manager and BH Image Manager or Image manager etc. Similarly, you can even edit the original po file (when no other way) because they obviously are not in the en po file after some strings correctly:
Eg.: Na VU+Uno není funkční třeba řetězec "Set your Drembox settings." But when I change the "Set your VU+ Uno Settings." then displayed in the GUI correctly. Similarly, it keeps me in your image (Vix) :
#, python-format
msgid ""
"Your STB_BOX will be restarted after the installation of service\n"
"Ready to install \"%s\" ?"
msgstr ""
"Váš STB_BOX se po instalaci služby restartuje\n"
"Chcete nainstalovat \"%s\" ?" .....................................Non localizet in czech Gui...

#, python-format
msgid ""
"Your VU+ Uno will be restarted after the installation of service\n"
"Ready to install \"%s\" ?"
msgstr ""
"Váš VU+ Uno se po instalaci služby restartuje\n"
"Chcete nainstalovat \"%s\" ?" ....................................is localized in czech GUI.

It's not a mistake translator, but there must be some error in the scripts, or somewhere similar. I'm not programmer or linux not control. I just wanted to help at least one image to follow the Czech localization.
 
I just wanted to help at least one image to follow the Czech localization.
Yes, that's very clear and much appreciated :thumbsup:

But we must follow specific rules to get things done the proper way (and to prevent translations to get lost over time).
For the rest: let's await Andy's reply to this, as he is a programmer and he knows his way around how this has been implemented in his image-building environment.
 
I just wanted to help at least one image to follow the Czech localization.
Yes, that's very clear and much appreciated :thumbsup:

But we must follow specific rules to get things done the proper way (and to prevent translations to get lost over time).
For the rest: let's await Andy's reply to this, as he is a programmer and he knows his way around how this has been implemented in his image-building environment.
 
Status
Not open for further replies.

OpenViX Feeds Status

Back
Top