Springen naar inhoud


Foto

Encoding error.


  • Please log in to reply
Er zijn 17 reacties in dit onderwerp

#1 foxbob

  • Senior Member
  • 612 berichten

+18
Neutral

Geplaatst op 3 juli 2020 - 19:40

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.

Bijgevoegde Bestanden



Re: Encoding error. #2 Dimitrij

  • PLi® Core member
  • 9962 berichten

+334
Excellent

Geplaatst op 3 juli 2020 - 20:10

Maybe...

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

Test for old encoding.conf


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Encoding error. #3 foxbob

  • Senior Member
  • 612 berichten

+18
Neutral

Geplaatst op 3 juli 2020 - 20:24

Already better,but still have problems.

 

Bijgevoegde Bestanden



Re: Encoding error. #4 foxbob

  • Senior Member
  • 612 berichten

+18
Neutral

Geplaatst op 3 juli 2020 - 20:59

After rebooting the receiver, it became bad.

 

Bijgevoegde Bestanden



Re: Encoding error. #5 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 4 juli 2020 - 06:58

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


Veranderd door ims, 4 juli 2020 - 07:19

Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #6 WanWizard

  • PLi® Core member
  • 68303 berichten

+1718
Excellent

Geplaatst op 4 juli 2020 - 11:38

And merged.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Encoding error. #7 foxbob

  • Senior Member
  • 612 berichten

+18
Neutral

Geplaatst op 4 juli 2020 - 14:26

Thanks, ok now.

 

Bijgevoegde Bestanden



Re: Encoding error. #8 EnoSat

  • Senior Member
  • 182 berichten

+4
Neutral

Geplaatst op 9 juli 2020 - 20:36

and georgian string fixed (as kat) ?

Bijgevoegde Bestanden


Veranderd door EnoSat, 9 juli 2020 - 20:46


Re: Encoding error. #9 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 10 juli 2020 - 14:10

@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...

 

 

 

 

 

 

 

Bijgevoegde Bestanden


Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #10 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 10 juli 2020 - 14:41

could anyone who can read georgian check it, pls ?

Bijgevoegde Bestanden


Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #11 Dimitrij

  • PLi® Core member
  • 9962 berichten

+334
Excellent

Geplaatst op 11 juli 2020 - 07:20

Martin

estring - added georgian GEOSTD8ToUTF8 conversion

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


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Encoding error. #12 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 11 juli 2020 - 09:50

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.

Bijgevoegde Bestanden


Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #13 Dimitrij

  • PLi® Core member
  • 9962 berichten

+334
Excellent

Geplaatst op 11 juli 2020 - 09:57

 

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

I can not too :) .
Ping EnoSat
 

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Encoding error. #14 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 11 juli 2020 - 10:11

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


Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #15 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 11 juli 2020 - 12:43

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

 

Bijgevoegde Bestanden


Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #16 ims

  • PLi® Core member
  • 13600 berichten

+210
Excellent

Geplaatst op 11 juli 2020 - 18:57

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


Veranderd door ims, 11 juli 2020 - 19:15

Kdo nic nedělá, nic nezkazí!

Re: Encoding error. #17 Gold_66

  • Senior Member
  • 30 berichten

+1
Neutral

Geplaatst op 24 januari 2022 - 11:08

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.

 

Bijlage  31_5.jpg   181,85K   1 Aantal bijlagen

 

Is there anything else I should do?

Thanks in advance.


Veranderd door Gold_66, 24 januari 2022 - 11:12


Re: Encoding error. #18 Gold_66

  • Senior Member
  • 30 berichten

+1
Neutral

Geplaatst op 24 januari 2022 - 11:19

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" />




1 gebruiker(s) lezen dit onderwerp

0 leden, 1 bezoekers, 0 anonieme gebruikers