> On XMMS 1.2.4, I enabled "Use X font" with font
> "-monotype-arial-medium-r-normal-*-*-100-*-*-p-*-iso8859-8" and it
> worked fine. No crash.
Tested it right now. No crash. May be because I upgraded to 1.2.4. I
installed the rpm from xmms.org, and the plugins I found at rpmfind, the
plugins are mdk. No problmes there.

> Actually, all modern TrueType fonts are Unicode. The encodings which
> are available to X depend on your fonts.dir file. If you claim your
> font has an "iso8859-8" encoding, the encoding will appear on the list.
> If the font has Hebrew glyphs in the Hebrew Unicode range, you'd see
> the characters. Otherwise, you'd see "missing character" squares.
> Simply add a "iso10646-1" encoding variant to the fonts.dir file.

> Run your GTK 1.2 and legacy programs with an LC_CTYPE=he_IL environment
> variable and they will succesfully decode the normal keymap into 8-bit
> characters. And no, Qt 2.3, Mozilla and GTK 2.0 really need proper
encodings
> to know what you meant.
> LC_CTYPE=he_IL biditext xchat
I set in ~/.xsession LC_CTYPE=he_IL and exported it. Some problems:
now kde does not input hebrew, and gtk does.
also biditext beheaves un-normal: it shows every word by itself OK, but the
sentence backward: for example I changed the album to "rishon sheni" in
hebrew, and I saw the "rhison" in left of the right. When I log in without
the LC_TYPE I see it OK, also in windows it looks OK. The second and third
parameters are the programs name to apply? (I know thease newbie are
questions, sorry, but I do not want to post this subject to gnubies-il now
since I started here)

Another problem: I added DGA and set SUID to /usr/bin/xmms. Then restarted
"biditext xmms" and biditext didnt work. I saw everything backward. I su'ed
and run "biditext xmms" and as root it was OK now. I exit the shell as root
and now I am a normal user, run biditext xmms and everything works OK again.
(?).
Can you explaing this to me?

>Simply add a "iso10646-1" encoding variant to the fonts.dir file.
perl -i -pe 's/iso8859-9/iso-10646-1/' fonts.dir?
That is waht Tzafrir wrote on thursday, but if I change teh turkish
encoding, I cant still view turkish utf documents, right? It may be safer to
add a new line which includes a iso-10656-1 after the last one, how do I do
it?

  - diego



=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to