TTD Forum

Hello,

Jag's EPG (2.7 and the latest, which I have: 3.0.5) are unable to show cyrillic characters in program name & description, while the channel name is displayed ok.

This feature is essention for those people, who is watching Russian NTV+ from 36E.

Have you checked, if the compression in JAG is not activated.
I think, that this can be a problem. As you write, the channel name is correct. So JAG have no problems with the chacacters, but I think, he write wrong characters in the internal database when the compression is enabled.

When not, only JAG can fix this

Are the characters in the original EPG correct ?

[quote=""Maliboy""]
Have you checked, if the compression in JAG is not activated.
[/quote]
I'll check that out this evening.

[quote=""Maliboy""]
Are the characters in the original EPG correct ?
[/quote]
Yes, the characters in the original EPG are correct, however looks ugly.
I also have a question: Is it possible for TAP to override displaying some characters, for example 66 chars of russian alphabet?
Or it is the case for patching a firmware?

[quote=""justason""]I also have a question: Is it possible for TAP to override displaying some characters, for example 66 chars of russian alphabet?
Or it is the case for patching a firmware?[/quote]

I think, the question can only a 'TAP guru' answer.
But I think, for displaying in a TAP, it is possible when the characters are avaiable in the firmware...

[quote=""Maliboy""]Have you checked, if the compression in JAG is not activated.
I think, that this can be a problem. As you write, the channel name is correct. So JAG have no problems with the chacacters, but I think, he write wrong characters in the internal database when the compression is enabled.

When not, only JAG can fix this

Are the characters in the original EPG correct ?[/quote]

It doesn't matter: with or without compression cyrillic characters in EPG are not readable.

[quote=""justason""]It doesn't matter: with or without compression cyrillic characters in EPG are not readable.[/quote]

After you have disable the compression, have you clear the EPG buffer file and rescan the stations with cyrillic characters in the epg ? Because, if the compression is the problem, the error is still available after disable the compression because the error is still in the buffer file.

Otherwise, JAG must take a look. But I think, the problem is, that he has only DVB-T and so he has no station with cyrillic characters...

[quote=""Maliboy""]After you have disable the compression, have you clear the EPG buffer file and rescan the stations with cyrillic characters in the epg ? Because, if the compression is the problem, the error is still available after disable the compression because the error is still in the buffer file.

Otherwise, JAG must take a look. But I think, the problem is, that he has only DVB-T and so he has no station with cyrillic characters...[/quote]

Well, I have tried to.
No luck.
Just to see, how beautiful it is, I have attached 2 photos.
(Didn't manage Screenshot TAP to work with Jag's EPG)

Hi,

do you have select Russian in the language setting menu?
The text compression of Jag's EPG definitive DO NOT supporting cyrillic characters!
Here the compression must be set to "OFF"!

Maybe the TAP API call for the event description use a another characters code table conversion as the internal functions. Maybe here a code replacement table is required?!

To analysing the problem better it should be useful to get a screenshot of the same text from the original EPG and Jag's EPG (long event description)!
To make screenshot's you can use ScreenCapture_OSD (start ScreenCapture_OSD before Jag's EPG): http://www.topfield.de/files/Firebird/S ... re_OSD.zip.

Make at the best two screenshots of a large text!


Jag

[quote=""Jag""]Hi,

do you have select Russian in the language setting menu?
[/quote]
It is possible, but doing that has no impact on Jag's EPG

[quote=""Jag""]
The text compression of Jag's EPG definitive DO NOT supporting cyrillic characters!
Here the compression must be set to "OFF"!

Maybe the TAP API call for the event description use a another characters code table conversion as the internal functions. Maybe here a code replacement table is required?!
[/quote]
It is OFF, because in settings it says "Only English and German languages are supported." - or something like this.

[quote=""Jag""]
To analysing the problem better it should be useful to get a screenshot of the same text from the original EPG and Jag's EPG (long event description)!
To make screenshot's you can use ScreenCapture_OSD (start ScreenCapture_OSD before Jag's EPG): http://www.topfield.de/files/Firebird/S ... re_OSD.zip.

Make at the best two screenshots of a large text!


Jag
[/quote]

Thanks,
I'll do screenshots this afternoon, as soon as I get home.

--------
By the way, (about the character table), I'm interesting to change outlook of these cyrillic characters, because, they _REALLY_ looks ugly.

Is it possible to:
1) Change outlook of these symbols
2) At the TAP level to override character displaying
---
A) Replace memory region, which contains character bit-blocks with "proper" region. Or re-route calls to a "proper" region
B) Create string manually

Please advise.

Here are the screenshots.

I beg your pardon...

It was my mistake. Yes, after selecting system language as russian, EPG started to show cyrillic letters correctly.

o-o-ps.