progdvb.com

For correct viewing OSD in my language I need ISO/IEC 6937 support.
Is it possible to add this.
Thanks.

It doesn´t help me to change font in OSD setting.
There is still lot of mistakes in OSD bar with EPG data from channel.
I tried to change font in OSD settings but it is still the same, maybe
this function doesn´t work.
Can anybody help me?

Which card do you use ?

TT Sky Star 1 ver.1.3

Then try this : http://www.zshare.net/download/bootfiles-rar.html

Copy the ´root´ file to : \Progdvb\Modules\boot\24

This is all i can do for you...

Thanks, I will try.
But it is interesting that OSDmenu doesnt change font after change in
OSD settings, font style is still the same, maybe itis bug(SS1 HWmode).
SS1 users can test it.

No in HWmode the style comes out of the ´Root´ file...

SiLencer wrote:No in HWmode the style comes out of the ´Root´ file...

But when I manually insert new osd.ini with other style(colour,font size)
I can see the change in HWmode.

But the type of character set comes from the root file...thats what i mean..

Example : There is a german root file with ä ü ö ...these characters don´t exists in other root files...

Can somebody explain to me again why EPG data in OSD are not correct.
In OSD is problem with ž,š,č but in EPG data style of the font is correct.
Also EPG info in the bottom line in ProgDVB is correct.
Only OSD is the main problem. Is there any idea please?

OK, I will also try...

Are you sure to have a real hardware mode for both PC screen and SS1 hardware TV out , means no level / quality bars available in OSD, driver is NOT the KS from TT 2.19c (or similar by hauppauge, but some 2.18 version number)? Else your PC screen picture is NOT made in HW mode.
In other words, your OSD must be absolutely identical on PC screen and hardware TV out, if you are in a real hardware mode. Else you are not.

Does software mode work on your system?
If yes, find out, if it's the same there, regarding that special characters.
If you have exactly the same wrong characters as in HW mode, it's some kind of a charset identification / transcoding problem.

But if in SW mode the OSD instead shows like the GUI based displays (status bar and EPG window)...
... it's exactly what SiLencer already told about.

Hardware OSD indeed used pixmap characters, which are read from the 'root' firmware file.
That characters are available in three sizes, each group with it's own pixmaps.
They are 128 different symbols in each set.
So, there are some limitations, even for a fully localized file, no more than 128 different characters available. 'What's now' and 'What's next' are fed from EPG data, that use full charsets of 256 possible symbols...
This means, not all chars are possible both upper and lower case.
Also depends on the provider, as for some special chars there's more than one way to address them.

BTW, you've mentioned a few special characters, please tell us, what shows up instead, for each.
Check out small and medium font size for that OSD section, compare.

That's the way people find out, what OSD character would have to be edited to what other.

Some localized root files are only edited for one of the three sizes.

Font_OSD_Edit.exe (google for it or look through DVB related download pages) edits the pixmaps one by one, on a bit base, so it's a lot of work to do.
It's GUI looks like greek to me, but it's Windows standard, so not required to understand each name on the surface.

And changing a pixmap's width can cause trouble, better not try. Write down each detail before and after, to avoid confusion.

The editor stores exaclty one older version, so make safety copies in different folders, store away each new version with some proven progress..


Well, sounds a bit complicated, and yes, it really is...

Thanks all for advice.
OSD with new bootfiles (THX SiLencer) in softmode is excellent(with ž,č,š,ť..), but I want to use my card in HW mode.
So I will collect characters and what shows up instead.