FreeLists / openbeos / [openbeos] Re: StyledEdit issues : text encodings,opentracker integration, etc.

[DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>]

>StyledEdit from R5 supports only the encodings that
>are supported from BFont so I suspect they used that
>approach in that situation.  IMHO the BFont approach
>is less worse than than the conversion approach but
>the coverage is abysmal! (no east asian language 
>support at all)
>
>I'm prepared to implement the BFont approach with the
>understanding that at some later point coverage will
>be expanded.  But I would like some assurances from
>our font people that it's a reasonable assumption.
>
>I am especially worried since my cursory examination
>of the freetype library yielded *no* occurances of 
>"8859" in the code.  R5 supports font display for all
>ISO-8859 standards from 1 to 10. (and MacRoman too)
It will be. I can assure you that R2 will have good support for a variety of 
encodings. I will extend FreeType2 to support all of R5's encodings, but they 
will be there along with a few which FreeType has given us for free. It's not 
scheduled for duty for a while because I'm still figuring out how to *use* it 
before I start hacking away. What we currently have given to us by FreeType2 
are symbol, Unicode, Latin 1, Latin 2, Shift-JIS, Wansung, Johab, Apple 
Roman, Big 5, and GB 2312. They are all declared in freetype.h. The reason 
you can't find 8859 in there is because it isn't used - the ISO 8859 specs 
are referred to by the encoding name Latin.

>I could see a possible future where we decide that
>BFont::SetEncoding will not be supported due to the
>constraints of our font engine.  In that case I'll 
>have to wander back over to the conversion method
>in the end anyway.  So... anybody care to play 
>prognosticator?
>
>Andrew
I'd be interested in understanding more why you think this. Contact me off-
list.

--DarkWyrm