Jump to content


Photo

Language assistance requested...


  • Please log in to reply
998 replies to this topic

Re: Language assistance requested... #481 ims

  • PLi® Core member
  • 13,807 posts

+214
Excellent

Posted 26 August 2018 - 16:11

Hi Ims,

 

It appears that I have misunderstood the intention of your post.  Sorry for the contextually inappropriate overreaction.

 

I still contend that the way OpenPLi handles image location management can be improved.  Also, I think it can be done to maintain backwards compatibility AND be useful for other images.

 

Regards,

Ian.

 

Sorry, my english is limited, I can not compose poems in Jambic pentameter...  :)

 

Understand, that this little change in path means change all skins (it is more than 5 PLi skins) working under PLi . And when will be finished "intergalactic" solution, then remove duplicities in this skins again.  Thats all... Due it , temporarily, could be there if then... =>no works on skins.


Kdo nic nedělá, nic nezkazí!

Re: Language assistance requested... #482 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 26 August 2018 - 16:21

Hi Ims,

 

I think I have a solution that will maintain compatibility with ALL existing OpenPLi skins.  I am still polishing off some text code for Zeros to test the new NumericalTextInput.  WHen that is done I will try coding up my proposal.

 

Regards,

Ian.



Re: Language assistance requested... #483 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 26 August 2018 - 16:48

The Estonian character š now OK. It is also on the dreambox Test feed.
Also , the two pages are OK and quote enough.

Attached Files


DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Language assistance requested... #484 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 26 August 2018 - 17:14

 

Please be aware that AFAIK PLi is the only brand that uses a default skin folder within the skin folder (on top of the standard E2 default skin)..

what is wrong about it?

 

 

It's not about right or wrong (although it's quite a strange setup); it's something to take into consideration in this thread.



Re: Language assistance requested... #485 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 26 August 2018 - 17:49

Hi Zeros,

 

I think I have finished the prototype of the new NumericalTextInput.  The new version will now use the locale based characters for all text based input.  (Hex input is the same everywhere.)

 

The big visual difference from the version I posted previously is that the current locale is checked and if that locale has been defined to have alternate character definitions the locale based data is used instead.  The data is matched in such a way that all the mode selected display options are now ALL available.  That is, if you ask for a text string that only has upper case characters then all the characters from your locale will be used.  In the previous code all the formatting options were lost if a locale was specified.  The code is now fully symmetrical.

 

I will try and update the other languages and the post a copy of the code here for testing and review.

 

Regards,

Ian.



Re: Language assistance requested... #486 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 26 August 2018 - 18:25

OK, it would be good if these letters would go exactly on these positions, as posted by Mr.blzr (on post #427)
I do not know whether it is standardized and I have no clue as to how other languages could be.

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Language assistance requested... #487 ims

  • PLi® Core member
  • 13,807 posts

+214
Excellent

Posted 26 August 2018 - 18:32

Could be added: 

self.setTitle(_("Virtual KeyBoard")) 

For full screen skins (without title) it is needed for text on top screen.


Kdo nic nedělá, nic nezkazí!

Re: Language assistance requested... #488 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 26 August 2018 - 20:39

Hi Athoik,
 

Are there any developers interested in making this happen?


Yes I am interesting adding the rendered!

 
That sounds great.  Please keep us informed of your progress.
 
Please try to make the code portable to other images.  This could be a valuable addition to Enigma2.
 
Regards,
Ian.


I created a new branch called svg that currently adds support for svg in picture player, using nanosvg library.

https://github.com/O...a8a9169e3c78945

Rendering the thumbnail needs more care... But picture player already works.

Attached File  screenshot.jpg   92.63KB   2 downloads

Any idea what should be implemented next?
 

@IanSav,
 
Of course a solution needs to be found for today skins to retrieve the proper graphics. So a "folder" based solution is needed.
 
I have created a feature in devtools to keep in mind the .svg idea.
 
https://devtools.ope....org/issues/353
 
Pr2


It's not an idea any more ;)
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: Language assistance requested... #489 MCelliotG

  • Senior Member
  • 443 posts

+35
Good

Posted 26 August 2018 - 21:02

Why not animated gif too?

Στάλθηκε από το Redmi Note 5 μου χρησιμοποιώντας Tapatalk

Re: Language assistance requested... #490 Pr2

  • PLi® Contributor
  • 6,182 posts

+261
Excellent

Posted 26 August 2018 - 21:12

There are already lots of ideas on devtools (Features), if you have time for them...   ;)  


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: Language assistance requested... #491 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 26 August 2018 - 23:26

Hi Zeros,

 

OK, it would be good if these letters would go exactly on these positions, as posted by Mr.blzr (on post #427)
I do not know whether it is standardized and I have no clue as to how other languages could be.

 

That is exactly what I used for the template.

 

Regards,

Ian.



Re: Language assistance requested... #492 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 26 August 2018 - 23:31

Hi Ims,

 

Could be added: 

self.setTitle(_("Virtual KeyBoard")) 

For full screen skins (without title) it is needed for text on top screen.

 

This should not be necessary.  Add a "title=" attribute to the "VirtualKeyBoard" screen in the skin.  (Hint, the "title=" attribute is fully translatable and allows the skin controller to tweak the title text without needing to tweak the code.)

 

I haven't tried this on OpenPLi but it should work.  Please tell me if it doesn't.

 

Regards,

Ian.



Re: Language assistance requested... #493 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 26 August 2018 - 23:39

Hi Athoik,

 

Any idea what should be implemented next? 

 

Does this mean that SVG images can now be used in the skin engine?

 

If you are asking about other graphical additions then I would support MCelliotG's suggestion for animated GIFs.  (As long as they aren't a performance killer in the UI.)

 

Regards,

Ian.


Edited by IanSav, 26 August 2018 - 23:40.


Re: Language assistance requested... #494 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 27 August 2018 - 05:01

Hi Ims,

 

Could be added: 

self.setTitle(_("Virtual KeyBoard")) 

For full screen skins (without title) it is needed for text on top screen.

 

This should not be necessary.  Add a "title=" attribute to the "VirtualKeyBoard" screen in the skin.  (Hint, the "title=" attribute is fully translatable and allows the skin controller to tweak the title text without needing to tweak the code.)

 

I haven't tried this on OpenPLi but it should work.  Please tell me if it doesn't.

 

Regards,

Ian.

 

The preferred way is indeed to use the selftitle and hence no full title should be in the skin. Translations should be done via the E2-po, not via/by skinners.

Only a few screens for plugins that lack this will have to use the full title in the skin.
 



Re: Language assistance requested... #495 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 27 August 2018 - 05:10

Hi Rob,

 

 

 

Could be added: 

self.setTitle(_("Virtual KeyBoard")) 

For full screen skins (without title) it is needed for text on top screen.

This should not be necessary.  Add a "title=" attribute to the "VirtualKeyBoard" screen in the skin.  (Hint, the "title=" attribute is fully translatable and allows the skin controller to tweak the title text without needing to tweak the code.)

 

I haven't tried this on OpenPLi but it should work.  Please tell me if it doesn't.

 

The preferred way is indeed to use the selftitle and hence no full title should be in the skin. Translations should be done via the E2-po, not via/by skinners.

Only a few screens for plugins that lack this will have to use the full title in the skin.

 

The "title=" attribute in the skin is fully translated by the same translation system used in the code.  All the skin titles, and "text=" attributes should be in English and will be translated for you.  ;)

 

Regards,

Ian.


Edited by IanSav, 27 August 2018 - 05:11.


Re: Language assistance requested... #496 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 27 August 2018 - 05:42

Are you sure that applies to PLi as well?

Anyway the selftitle is the preferred way: it requires less skin code.



Re: Language assistance requested... #497 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 27 August 2018 - 06:19

Hi Rob,

 

I checked the OpenPLi sources and the code is there as well.

 

As you will discover when I present more of my code, I have a preference to allow as much user configurability as possible without adding bloat.  Hard coding titles in the Python does not follow that philosophy.  It adds unneeded code to the module when the skin engine already does the work for you.  With this style skin developers and users are able to easily change the titles for themselves (if the skin method is used).  I use this a lot in my code.  :)

 

The only place this doesn't work is where the title is programmatically changed while the code is running.

 

Regards,

Ian.


Edited by IanSav, 27 August 2018 - 06:20.


Re: Language assistance requested... #498 littlesat

  • PLi® Core member
  • 57,242 posts

+702
Excellent

Posted 27 August 2018 - 06:59

I did abort two merge request from fairbird because I think we can make this smarter... I’m considering that skin_default stuff could be made a some kind of don’t care....

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Language assistance requested... #499 ims

  • PLi® Core member
  • 13,807 posts

+214
Excellent

Posted 27 August 2018 - 07:12

Hi Ims,

 

Could be added: 

self.setTitle(_("Virtual KeyBoard")) 

For full screen skins (without title) it is needed for text on top screen.

 

This should not be necessary.  Add a "title=" attribute to the "VirtualKeyBoard" screen in the skin.  (Hint, the "title=" attribute is fully translatable and allows the skin controller to tweak the title text without needing to tweak the code.)

 

I haven't tried this on OpenPLi but it should work.  Please tell me if it doesn't.

 

Regards,

Ian.

It works for not full screen skins, where screen has own title... but for full screen skins is title=" "  for nothing...


Kdo nic nedělá, nic nezkazí!

Re: Language assistance requested... #500 IanSav

  • PLi® Contributor
  • 1,491 posts

+51
Good

Posted 27 August 2018 - 07:32

Hi Ims,

 

Yes, you need to have a space to create a blank title.  This is due to an issue in skin.py where the string is translated unconditionally.  This is wrong.  If the title is set to "" the system generates the language status screen.  This is a quick fix.

 

Some screens are uncontrollable because the title has been hard coded in Python.  :(

 

Regards,

Ian.




7 user(s) are reading this topic

0 members, 7 guests, 0 anonymous users