Hi My linux Lovers


I have one problem with redhat linux 2.1. I have one japanese character doc file in my windows i instelld japnese font in my windows box . i can able to see the japanese character file. same thing i cant see in redhat linux 2.1 box . what font i need to install in my redhat linux box


i dont know what im going to do for this problem or redhat support only english files

pl help me in this issue

Thanks and Regards
Subbiah K J

Look for packages that end in 'i18n-ja' or 'kanji' or start with 'cjk' for latex. For example, kde-i18n-ja, ghostscript-fonts-kanji

Hi js


I already installed japanese fonts in my redhat linux 2.1 box . I can see all the files in my Redhat Linux 3.0 box . i have japanese kde-dekstop in my redhat linux 2.1 box its working without any issue.
But now also im facing the same problem i cant see the jap doc


pl help me to resolve in this issue

I don't know which application you are trying to read the document with, but the is probably a 'character encoding' option under the View menu option.

If you want to edit a document, you will need to add the language support in the KDE configuration. You might want to select the option to display a language selector icon in the tray. This works best for me, because I don't want to loose the Windows key function of popping up the menu.

Also, I believe that Open Office will be able to read dbcs Japanese documents properly. Star Office 6 does. There may be a package to add japanese support for Open Office you need to install. For a version of Mandrake it is called OpenOffice.org-l10n-ja-1.1.4-5mdk.i586.rpm , If you have another distro, the 'mdk' characters won't be there, but you should have it on you disk already.

One thing to try. Recently, I tried to look at a windows .inf file that I downloaded for my amd64 laptop. The command gave a message at the top to append ==> : to the filename due to the file being little-endian doublebyte (ie UTF-16).

The first part may not work for a kde program, but you could try it just for 'shoot and holler'. But mainly, make sure that you have "UTF-16" available for encoding. You may need to install another package if it isn't an encoding option.

If you had a NTFS partition to mount and the characters for the filenames looked bad, changing the encoding in the mount statement might help.

One thing to try. Recently, I tried to look at a windows .inf file that I downloaded for my amd64 laptop. The command gave a message at the top to append ==> : to the filename due to the file being little-endian multibyte (ie possibly UTF-16).

The first part may not work for a kde program, but you could try it just for 'shoot and holler'. But mainly, make sure that you have "UTF-16" available for encoding. You may need to install another package if it isn't an encoding option.

If you had a NTFS partition to mount and the characters for the filenames looked bad, changing the encoding in the mount statement might help.

There is another encoding option for asian character that is multibye for some characters and single for others, but I don't remember what it is. However, I'm betting that the document used UTF-16.