Before drawing the text, jit.gl.text3d translates the sequence of
bytes in its input into Unicode charcters. The input is assumed to be
in the character encoding of the currently selected font. This means
that for some fonts, there will not be a valid translation of some
input byte sequences. Japanese text, for example, will not be visible
in a Chinese font. Also, most random sequences of bytes will have no
meaning in the multi-byte character encodings used by non-Roman fonts.

If I set the font to Osaka, & load in the file, I just get garbage.
I’ve also tried it with cyrillic, which I know is supported in fonts
like Geneva, but still with no luck. I’m no font expert — is there
something I’m missing?

M

On 5/4/07, mattyo wrote:
> I need to display some Japanese text from a file using
> jit.gl.text2d. getting a unicode-encoded file & just chucking it in
> doesn’t seem to do the trick, even with the font set to a chinese
> one. All I can find in the docs is the following:
>
> Before drawing the text, jit.gl.text3d translates the sequence of
> bytes in its input into Unicode charcters. The input is assumed to be
> in the character encoding of the currently selected font. This means
> that for some fonts, there will not be a valid translation of some
> input byte sequences. Japanese text, for example, will not be visible
> in a Chinese font. Also, most random sequences of bytes will have no
> meaning in the multi-byte character encodings used by non-Roman fonts.
>
> If I set the font to Osaka, & load in the file, I just get garbage.
> I’ve also tried it with cyrillic, which I know is supported in fonts
> like Geneva, but still with no luck. I’m no font expert — is there
> something I’m missing?
>
> M
>

M

On May 7, 2007, at 10:57, yair reshef wrote:

> i once had to deal with Hebrew fonts. there is a special kind of
> fonts, called xfonts. from what i understand they are simple bitmaps
> sprites which “just work”. had to do a spell conversion but that was
> all. search for fonts like that in your language
>
> On 5/4/07, mattyo wrote:
>> I need to display some Japanese text from a file using
>> jit.gl.text2d. getting a unicode-encoded file & just chucking it in
>> doesn’t seem to do the trick, even with the font set to a chinese
>> one. All I can find in the docs is the following:
>>
>> Before drawing the text, jit.gl.text3d translates the sequence of
>> bytes in its input into Unicode charcters. The input is assumed to be
>> in the character encoding of the currently selected font. This means
>> that for some fonts, there will not be a valid translation of some
>> input byte sequences. Japanese text, for example, will not be visible
>> in a Chinese font. Also, most random sequences of bytes will have no
>> meaning in the multi-byte character encodings used by non-Roman
>> fonts.
>>
>> If I set the font to Osaka, & load in the file, I just get garbage.
>> I’ve also tried it with cyrillic, which I know is supported in fonts
>> like Geneva, but still with no luck. I’m no font expert — is there
>> something I’m missing?
>>
>> M
>>

On 5/7/07, mattyo wrote:
> as far as I can tell, they are just a set of fonts for xwindows –
> the mac OS recognizes them?
>
> M
>
>
> On May 7, 2007, at 10:57, yair reshef wrote:
>
> > i once had to deal with Hebrew fonts. there is a special kind of
> > fonts, called xfonts. from what i understand they are simple bitmaps
> > sprites which “just work”. had to do a spell conversion but that was
> > all. search for fonts like that in your language
> >
> > On 5/4/07, mattyo wrote:
> >> I need to display some Japanese text from a file using
> >> jit.gl.text2d. getting a unicode-encoded file & just chucking it in
> >> doesn’t seem to do the trick, even with the font set to a chinese
> >> one. All I can find in the docs is the following:
> >>
> >> Before drawing the text, jit.gl.text3d translates the sequence of
> >> bytes in its input into Unicode charcters. The input is assumed to be
> >> in the character encoding of the currently selected font. This means
> >> that for some fonts, there will not be a valid translation of some
> >> input byte sequences. Japanese text, for example, will not be visible
> >> in a Chinese font. Also, most random sequences of bytes will have no
> >> meaning in the multi-byte character encodings used by non-Roman
> >> fonts.
> >>
> >> If I set the font to Osaka, & load in the file, I just get garbage.
> >> I’ve also tried it with cyrillic, which I know is supported in fonts
> >> like Geneva, but still with no luck. I’m no font expert — is there
> >> something I’m missing?
> >>
> >> M
> >>
>
>