Er zijn 31 reacties in dit onderwerp

[blzr]

I added to tuxtext.ttf font missing Polish diacritic characters (Ą, ą, Ę, ę, Ń, ń, Ś, ś, Ż, ż, Ź, ź)
tested, working ok, so maybe update of original font would be possible?

this font is used for console, and with translated on-screen messages, lack of these characters is a bit annoying,
eg. I made a Polish translation for BackupSuite plugin, but with current font it's pretty useless...
TIA

//and btw. regarding attachments - is it really necessary to forbid attaching of eg. .md5, .py .ttf or no-extension files? IIRC on an old forum all above types of attachemnts were allowed /?/...

Bijgevoegde Bestanden

•  tuxtxt.ttf.tar.gz   26,88K   55 Aantal bijlagen

[Pedro_Newbie]

Nice to hear there is a Polish translation (on its way) for the BackupSuite

[blzr]

...tested, working ok, so maybe update of original font would be possible?

so it seems that the answer is 'uhm... no'?

[pieterg]

I will add it, but what about the tuxtxt.otb font, which I believe is used by default?

[pieterg]

ah I see, you mean it is used by e2 as well.

[blzr]

yep, I meant font that is used by enigma,
thanks for commiting
btw. you've got this font both in enigma tree and in tuxtxt - if you update only one of them everything will be ok?

and regarding tuxtxt.otb - it lacks only Ą, Ę, Ń, Ź, Ż of which first 3 are not used (unless something is in ALL CAPS) and only lack of the last character is actually noticeable...
anyway, I added missing bitmaps, but after generating an updated font I got validation errors and TXT is not working (and I'm a very beginner with fonts )...

[pieterg]

I didn't even realise it was still there, just did a quick check to make sure they don't conflict.
But the e2 one is not installed....

[blzr]

ok, thanks again

[macnuts]

yep, I meant font that is used by enigma,
thanks for commiting
btw. you've got this font both in enigma tree and in tuxtxt - if you update only one of them everything will be ok?

and regarding tuxtxt.otb - it lacks only Ą, Ę, Ń, Ź, Ż of which first 3 are not used (unless something is in ALL CAPS) and only lack of the last character is actually noticeable...
anyway, I added missing bitmaps, but after generating an updated font I got validation errors and TXT is not working (and I'm a very beginner with fonts )...

I'd never done with fonts or teletext before but I found a "workaround" for the otb font. In the fontforge I generated the font as True Type and changed its extension to .odb. It is a brute force solution but it worked for me.

[macnuts]

I meant .otb in last post, of course.

[ims]

Added missing CZ chars.

Bijgevoegde Bestanden

•  tuxtxt.ttf.tar.gz   29,2K   27 Aantal bijlagen

[ims]

I will add it, but what about the tuxtxt.otb font, which I believe is used by default?

strange ... I am add czech chars to all 3 tabs (21,22,23) there in tuxtxt.otb, but nothing happends.

Interesting - some czech chars in .otb missed, but on teletext are.
Eg: In all fonts is "dcaron" made as "d" with "apostrof" ( ď ), but on TV in teletext is caron top "d" ... some as "ˇd" ).
Is there some table and txt using basic chars and adding "ˇ" or "´" only ?

[ims]

Yes, if i change graphics caron , is changed caron on "ď". For Upper cz nat chars is used chars + BREVE, but for some UPPER chars it is not made.

[blzr]

I have experienced similar /?/ problems with uppercase chars when modifying (PL) tuxtxt.otb font - even when I added eg. Ż (Z with a 'dot') it was displayed as Z (and same with Ą, Ę, Ń, Ź)
but maybe it's just my lack of knowledge - I simply copied eg. Z and then added a 'dot' manually to the bitmap using fontforge editor
//but nevertheless it is better now - it's 'clean' char (without glyph) displayed instead of an empty field...

[ims]

I think, i found it ... there in otb are empty some "acute etc ...".

See on 3rd line in table G2table[4][6*16] there in tuxtxt_common.h. There are next diacritical for LAT and its position in otb font. In .otb are this positions empty ( f.eg. 0x0301 ... is used as acute for some nat chars - in otb is empty.)

If you want know, what chars must be in position in .otf, see to page 116, row 3 here : http://www.google.co...NOlOLyw&cad=rja

[ims]

Problem is, that f.eg. 0x301 ( acute) is displayed still left.

Veranderd door ims, 16 november 2011 - 11:01

[ims]

I think, problem with Ń, Ź ( for CZ it is on Ý, Í, Á, É, for Slovak Ľ, ...) is here:
it is made as char 0x0301, but:
- cell in font is empty. Glyph is composed as U + 0x00B4. Acute on 0x00B4 is made as: U+0x0020 U+0x00B4 ( same as next diacritic marks - mark with space before => is centered)

When is cell empty, it is not 0x0301 accepted. For accepting there must be in cell "anything". But when is there "anything", then top on char is displaying some strange, because then result is as "some + 0x0020 + 0x00b4". If I fill with "white" pixel, then is not centered ... etc ...

I think, in this case must be in table G2table[4][6*16] line 3: 0x00B4 and not 0x0301 => will take true centered Acute or edit Gliph of 0x0301 to U+0x0020 U+0301.

- may be, your next PL chars will be made from A + left aligned some mark.

Veranderd door ims, 16 november 2011 - 11:31

[ims]

Solved - in font from 0x00B4 copy reference into cell 0x0301 => i have acute on all upper chars :-)

Try this, if it helps You with Ń, Ź.

Note: i am little edit "breve" , because it is used as caron on upper chars, but is is not well visible ( i made its bitmap as caron)

Bijgevoegde Bestanden

•  tuxtxt.otb.tar.gz   15,01K   10 Aantal bijlagen
•  teletext.jpg   100,7K   46 Aantal bijlagen

Veranderd door ims, 16 november 2011 - 12:06

[blzr]

thanks for your help, I'll give it a try...
if it works, then only remains to solve the problem 'ogonek' 0328 (Ą, Ę)...
for (most frequently used) Ż (with a 'dot') I think about replacing it with 01B5 'Z with stroke' (which can be used interchangeably) //and is even better 'identifiable' in text imho

[ims]

23: better ring on top U and better Acute (not so masive), Breve as Breve, but little better.

Bijgevoegde Bestanden

•  tuxtxt.otb_1.tar.gz   15,01K   16 Aantal bijlagen