On Sun, Nov 12, 2006 at 08:17:30PM +0100, Alberto Hernando wrote: > I don't have problems with this. Or, at least, I don't think my problems are > for this reason. For example, with some settings in fstab, my accented words > in text files just dissapear, or things like ? and squares appear. If I write > new files, I can use accents with no problem. But I'll try more fonts. There is certainly a lot which all needs to be right at the same time, and I'm not sure I understand it all. At the moment, I'm transitioning to urxvt and everything was looking acceptable until I decided to try adding greek and russian keymaps - on some of my systems, everything is fine. On one system, the alternate keymaps produce no output in xterms (but are fine in e.g. konqueror and firefox, and I don't have urxvt on it), on another I can get greek or russian in xterms but not in urxvt! Fun. All I can do is wish you luck!
And before anybody jumps in to offer me help - my latest systems work, it's only extending the facilities to some of my older systems that gives problems. Eventually, I'll rebuild all my systems, and get a whole new set of problems. Certainly, 'squares' are a font problem - xterm doesn't seem able to use fontconfig, and kde might have some problems. In your chosen X terminal, either configure it to use freemono (hard to read, but good coverage) or (for xterm) run a new one with that font specified (xterm -fa FreeMono). After that, try to find a font which looks good and provides adequate coverage for you. At one time, I was omitting Bitstream Vera because I intended to use DejaVu, but forgetting to edit either fonts.conf or local.conf to reference DejaVu. The result was that I ended up with Luxi Mono in my xterms - it looks _very_ nice but has an extremely limited coverage (it was the first available font from the list for monospace - xterm just uses the first available font from the list, at least for TTFs). Question marks might imply non-displayable characters (there is fairly good correspondence between iso-8859-15 characters and UTF-8, at least for Spanish, but some -15 character values are not legal in UTF-8). > > > > In your original post, you said you could type and see japanese > > characters - out of interest, how do you type them, and into which > > application(s) ? > > Look for and old thread of mine "writing in japanese". You'll basically need > scim and anthy. You could use skim for kde too. For gtk apps, you don't have > to do many things, just scim/anthy/uim would work. But for kde, skim enables > you to enter Japanese (kana and kanji) in any app. You need utf-8 locales for > it, of course (that's why...). It can be a bit tricky to do. If you want to > try, start a new thread, I'll help you if I can. > Thanks, but it was just idle curiosity coupled with an interest in knowing what people are using for other languages. With greek and russian I can pronounce (some of) the individual letters, with japanese I wouldn't have a clue. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
