←  [EN] Third-Party Development

Forums

»

Encoding error.

foxbob's Photo foxbob 3 Jul 2020

Good evening.There was an incorrect display of the encoding in the channel selector.I have a problem at 31.5E.More guys say there is 39E.Enigma2-last develop-enigma2_2.7+git18530+68eca8e.

There are only a lot of lines in the log

[convertDVBUTF8] reserved 30
[convertDVBUTF8] reserved 30
[convertDVBUTF8] reserved 30
[convertDVBUTF8] reserved 30
[convertDVBUTF8] reserved 30

There are no problems with the Russian language.

Attached Files

Quote

Dimitrij's Photo Dimitrij 3 Jul 2020

Maybe...

https://github.com/O...9acc029eb716ca9

Test for old encoding.conf

Quote

foxbob's Photo foxbob 3 Jul 2020

Already better,but still have problems.

 

Attached Files

Quote

foxbob's Photo foxbob 3 Jul 2020

After rebooting the receiver, it became bad.

 

Attached Files

Quote

ims's Photo ims 4 Jul 2020

add lines:

0x001 0x001 ISO8859-5 # 31.5°E
0x002 0x001 ISO8859-5 # 31.5°E
0x003 0x001 ISO8859-5 # 31.5°E
0x004 0x001 ISO8859-5 # 31.5°E

 

and commented line:

#1 1        # 0.8°W 12.687 H    ... btw - no broadcast on 12678


Edited by ims, 4 July 2020 - 07:19.
Quote

WanWizard's Photo WanWizard 4 Jul 2020

And merged.

Quote

foxbob's Photo foxbob 4 Jul 2020

Thanks, ok now.

 

Attached Files

Quote

EnoSat's Photo EnoSat 9 Jul 2020

and georgian string fixed (as kat) ?

Attached Files


Edited by EnoSat, 9 July 2020 - 20:46.
Quote

ims's Photo ims 10 Jul 2020

@EnoSat ... as I saw, 0x003 0x001 will be removed from encodings.conf .  RUS will be ok still on this transponder, I hope (I hope, no next services have 0x003 0x001 there) .

 

But sorry, Georgian is not implemented in E2 (and it is not broadcasted in true geostr8, but with dropped prefixes). I can add it to cpp (in owif it is visibled yet), but I am affraid, no fonts in our e2 are full with georians chars...

 

 

 

 

 

 

 

Attached Files

Quote

ims's Photo ims 10 Jul 2020

could anyone who can read georgian check it, pls ?

Attached Files

Quote

Dimitrij's Photo Dimitrij 11 Jul 2020

Martin

estring - added georgian GEOSTD8ToUTF8 conversion

Great job.
Now I know who I will turn to for help with encoding ;) .

Quote

ims's Photo ims 11 Jul 2020

Martin

estring - added georgian GEOSTD8ToUTF8 conversion

Great job.
Now I know who I will turn to for help with encoding ;) .

Here is our Liberation Sans regular font with added georg. chars (I placed georgians chars from dejavu sans... resized to 94% and moved little down. I think, nobody will create new true georgians chars for "Liberation Sans").

Last develop ModifyPLiHDSkin plugin can change all fonts to Regular font now. You can try it, if is it useable. I cannot read it.

Attached Files

Quote

Dimitrij's Photo Dimitrij 11 Jul 2020

 

You can try it, if is it useable. I cannot read it.

I can not too :) .
Ping EnoSat
 
Quote

ims's Photo ims 11 Jul 2020

As I saw his language on Owif, i think, he cannot read it too.

Quote

ims's Photo ims 11 Jul 2020

All G. fonts in Regular ... very similar with LiberationSans.

 

Attached Files

Quote

ims's Photo ims 11 Jul 2020

Encoding.conf is not needed for georgian channels on 31.5E. EPG is broadcasted with flag for set encoding (0x1E)

 

Note - it works in develop only yet


Edited by ims, 11 July 2020 - 19:15.
Quote

Gold_66's Photo Gold_66 24 Jan 2022

Hi, sorry for bringing up this 1,5 year old thread again, but I couldn't quite succeed to have correct fonts of georgian channels on 31.5E, although I added these lines in encoding.conf

 

add lines:

0x001 0x001 ISO8859-5 # 31.5°E
0x002 0x001 ISO8859-5 # 31.5°E
0x003 0x001 ISO8859-5 # 31.5°E
0x004 0x001 ISO8859-5 # 31.5°E

 

and commented line:

#1 1        # 0.8°W 12.687 H    ... btw - no broadcast on 12678

 

and sent this font to usr/share/fonts

 

All G. fonts in Regular ... very similar with LiberationSans.

 

This is how they look like, all other fonts are ok, only georgian ones appear as rubbish.

 

Attached File  31_5.jpg   181.85KB   1 downloads

 

Is there anything else I should do?

Thanks in advance.


Edited by Gold_66, 24 January 2022 - 11:12.
Quote

Gold_66's Photo Gold_66 24 Jan 2022

Couldn't edit previous message twice - I forgot to mention that I changed the font name in skin.xml file as well, like this:

 

<font filename="LiberationSans-RegularG.ttf" name="Subs" scale="100" />

Quote