Cyrillic letters in name are not readable after scanning 45E Vivacom.

[plevel]

After scanning Vivacom at 45E , cyrillic channel names -unrecognised!
15 channels at 4 transponders(11475V,12520V,12560V,12600V) on Vivacom DTH 45 East.
After zapping on transponder , names are corrected, but is annoying to see unrecognised symbols, instead correct channel name in cyrillic.
Names in lamedb and lamedb5 are also in these unrecognised symbols.
Channels with latin names and EPG are not affected!

[Huevos]

Scanned how?

[plevel]

With Autobouquetsmaker 3.3 , provider Vivacom 45E.
With scheduled scan and manual scan from plugin menu, result is the same.
With AB Pulse 4K and Gigablue HD Quad Plus.
2 receivers same problems.
After zapping on channels on tne same transponder, letters are fixing, but is very annoying..

[LraiZer]

https://github.com/oe-alliance/AutoB...ader.c#L21-L26

Enigma2 has built-in dvb code for 8859-5 Cyrillic.

ABM is currently limited to iso 8859-1 Latin1 valid dvb chars only at present.
I guess someone needs to use iso 8859-5 for Cyrillic instead of limiting with iso 8859-1 Latin1.

[plevel]

Thanks for the hint, but where to seek the solution- may be in encoding.conf or must be insert in code of ABM?

[Huevos]

https://github.com/oe-alliance/AutoB...ader.c#L21-L26

Enigma2 has built-in dvb code for 8859-5 Cyrillic.

ABM is currently limited to iso 8859-1 Latin1 valid dvb chars only at present.
I guess someone needs to use iso 8859-5 for Cyrillic instead of limiting with iso 8859-1 Latin1.

I'm not sure how that helps because then we lose all the 128-255 chars from Latin1.

We really need it to follow the standard and choose the charset based on ETSI EN 300 468 Annex 2.

A.2 Selection of character table
Text fields can optionally start with non-spacing, non-displayed data which specifies the alternative character table to be used for the remainder of the text item. The selection of character table is indicated as follows:
- if the first byte of the text field has a value in the range "0x20" to "0xFF" then this and all subsequent bytes in the text item are coded using the default character coding table (table 00 - Latin alphabet) of figure A.1;
- if the first byte of the text field has a value in the range "0x01" to "0x0F" then the remaining bytes in the text item are coded in accordance with the character coding tables which are given in table A.3;

Currently we just use the default, which is Latin1.

I'm not sure of the code changes we need to implement this.

[plevel]

I am ready to test some code changes!

[plevel]

Could you make .ipk file just for this case(Vivacom) with cyrillic.
I think this will be partial fix for the problem...

[Huevos]

This will have to wait until someone with the ability to fix it has time.

[Huevos]

@plevel,

1. Enable debug logs (in system menu).
2. In ABM switch on extra debug.
3. Do a scan of that provider.
4. Post the debug logs here.

What hardware are you using?

[plevel]

I am using Gigablue HD Quad Plus with OpenATV 7.3 and Pulse 4K with open pli 8.3.
I will debug Gigablue HD Quad Plus now.

[plevel]

https://mega.nz/file/EHxzGRoI#T9VOeW...WiVcNCBBLoOLRM

Debug log.

[Huevos]

I am using Gigablue HD Quad Plus with OpenATV 7.3 and Pulse 4K with open pli 8.3.
I will debug Gigablue HD Quad Plus now.

Ok, on the GB Quad Plus can you add the supplied files from the zip file to /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/scanner.

Reboot and scan again. Get logs too.

[plevel]

On Gigablue worked OK, problem was fixed!
I will upload debub logs lately today.
And will try this files on Pulse 4K also.

[plevel]

https://mega.nz/file/oThSABKQ#UifUyE...bfkIP1h1EMx7P8

Debug log.