10 replies to this topic

[blzr]

could you please add new transponder /11411H 13E/ of PL provider cyfra+ to the encoding.conf?

1100 318 #Hotbird 13.0 Cyfra+

updated encoding.conf attached
thank you in advance

Attached Files

•  encoding.conf.tar.gz   999bytes   35 downloads

[blzr]

any word on this?
//patch attached, just in case...

Attached Files

•  encoding_conf.patch.tar.gz   331bytes   14 downloads

[hemertje]

New commits:

commit 7c3be9bf623183de2c3a311219bab93ecda34b36
Author: pieterg <pieterg@users.sourceforge.net>
Date: Sat Nov 12 16:28:33 2011 +0100

encoding.conf: add Cyfra+ transponder encoding override

as suggested by blzr

[marto]

I would like to continue this topic as our(BG) problem is related to the same encoding.conf file.
Few days ago SatelliteBG provider, start implementing Bulgarian EPG on some simulcrypt with SkyLink channels. In order to have it displayed correctly on OpenPli e2 images, we have to comment the following lines in encoding.conf file:
3205 3 # ASTRA 23.5° Skylink 117968 Barrandov
3215 3 # ASTRA 23.5° Skylink
3221 3 # ASTRA 23.5° Skylink 11 914 History
So if we make the above lines appear like this,

#3205 3 # ASTRA 23.5° Skylink 117968 Barrandov
#3215 3 # ASTRA 23.5° Skylink
#3221 3 # ASTRA 23.5° Skylink 11 914 History
there is no problem and everything is correct with the Bulgarian letters. Not sure if it still OK with chesh or slovac letters though.

So my question to devs is, is it possible to implement the following:
After choosing in Menu/Setup/System/Auto Language selection EPG language selection Bulgarian, automatically the above 3 lines to be commented or even deleted if necessary?
May be this will save us from editing the above lines after each online update in order to have correct letters on EPG.

[pieterg]

sounds like an ugly hack I'm afraid...
That's really a big problem, with simulcrypt you really need both providers to cooperate, and stick to the encoding standards...

[marto]

Both providers are using the correct encoding standards for their languages, but maybe the problem is that one is using cyrillic letters and the other latin(with some special characters).
On other (non e2 ) receivers everything is fine with the BG EPG, so the encoding standard is correct for sure. Otherwise it will be not possible to get it correctly on e2 even if we comment the lines from my previous post.
IMO now with this lines in encoding.conf
3205 3 # ASTRA 23.5° Skylink 117968 Barrandov
3215 3 # ASTRA 23.5° Skylink
3221 3 # ASTRA 23.5° Skylink 11 914 History
the receiver is trying to "translate" the cyrillic letters into Czech and as result of that we have the following letters as seen on the screenshot below.
I was thinking the "EPG language selection" option was created exactly for the simulcrypt channels, but looks like there is still something wrong with it.

Attached Files

•  screenshot.jpg   57.5KB   38 downloads

[pieterg]

Both providers are using the correct encoding standards for their languages

If that's the case the transponders do not have to be listed in encodings.conf.
The fact that they are, leads me to believe skylink is using the wrong encoding.

but maybe the problem is that one is using cyrillic letters and the other latin(with some special characters).

No, that should be no problem, as encodings are signaled in the eit data itself.

[ims]

0x2be 0x600 #0.8°W - UPC Direct (VIVA)

[daddelfalk]

Hi Guys,

please verify, if the change to encoding.conf are really necassary. As the last changes made by DMM itelf are also not required for your OpenPLI-Images to Fix german Umlaut like "ö" or special Characeters like "ß"

We should keep the encoding.conf as lean as possible.

[marto]

If that's the case the transponders do not have to be listed in encodings.conf.
The fact that they are, leads me to believe skylink is using the wrong encoding.

Yes indeed. You are right. The problem should be with Skylink encoding as without those three lines the BG letters are OK, but I can notice changes in some Czech letters.
If it's possible "EPG language selection" option to fix this by doing some changes in encoding.conf file would be nice. Then both parties will be happy with correct EPG.

[littlesat]

The EPG language selection just select the correct EPG language and does not cover different encodings....