EUC to Shift JIS Migration

Would like to know the effort / impact and the possible pitfalls that need to be kept in mind for migrating application from EUC to shift JIS. The app is a PRO*C application. It also interfaces with Tuxedo and MQ. Any lead / help is appreciated.

(0) Would be slightly easier than migrating from Shift-JIS to EUC.
(1) Hankaku Katakana (Half Width Katakana) characters are encoded as
two-byte characters
in EUC, but are signle byte characters in Shift-JIS. Hence length
will be changed if
the original Japanese text contains Hankaku Katakanas.
(2) Shift-JIS encoding defined by JIS (X0208) and Microsoft are
slightly different.
Actually, a few (less than 10) non-Kanji characters have different
encodings in
Shift-JIS and MS Shift-JIS (or MS932). This might become a pitfall.
(3) JIS X212 (complementary Kanji characters, not widely used)
characters can be encoded in
EUC as 3 byte characters but not in Shift-JIS. (Unicode also
contains JIS X212.)
(4) Handling user defined characters (or gaiji characters) are
sometimes very difficult.
(5) "CJKV Information Processing" (Blowfish Book) by Ken Lunde,
O'Reilly will be a good
reference.

Similar Messages

'Windows-1252', 'Shift-JIS', etc. code pages are not supported encoding names exception in Windows 8.1 Phone

Hi,
We have already released our product for WinRT desktop and tablet versions.
Now we are developing the same app for Windows 8.1 Phone.
We are supporting 'Windows-1250', 'Windows-1251', 'Windows-1252', 'Windows-1253', 'Windows-1254', 'Shift-JIS', 'GB2312' and 'Big5' in both desktop and tablet versions which uses WinRT API's.
But in Windows 8.1 Phone version, i am getting 'ArgumentException' saying 'Windows-1252' is not a supported encoding name.
Please help me with a solution or workaround to support the above specified code pages for Encoding.
Regards,
Balaji Reddy. M

Does CP-1252 work? If not, this page may help:
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/cf5ca6c9-72b0-4abb-9ef5-ff77226ec642/how-to-handle-unsupported-encoding-in-xml?forum=wpdevelop
Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.
NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined
objects and unknown namespaces.

Creating File in Shift-JIS, Japanese Encoding for EFT

Hi,
We need to do EFT for the data which is present in Shift-JIS(JA16SJIS), Japanese characterset.
Our database is having
NLS_CHARACTERSET -- UTF8
NLS_NCHAR_CHARACTERSET -- AL16UTF16
File needs to be sent to the bank in the Shift-JIS format, I need to know how we can generate a file in this encoding?
Please help?
Thanks,
Priyanshu

Welcome to the Forum,
I assume you mean Electronic Funds Transfer under EFT because of mentioning a bank. (but please note wikipedia http://en.wikipedia.org/wiki/EFT does not have this one but defines several others)
Okey so you would need to convert the character set.
And this may depends on the tool you use to generate the output files.
Lets see how I would do this in a linux env:
If you have a modern linux environment you most likely have utf8 characterset as environment character set. So to match this you would setup NLS_LANG to this utf8 accordingly.
see more here: The correct NLS_LANG setting in Unix Environments [ID 264157.1] https://support.oracle.com/CSP/main/article?cmd=show&id=264157.1&type=NOT
This way you can get UTF8 output files from the oracle client tools without any other change I think.
Finally you can convert this file with another tool. e.g. command line tool like "iconv" or "recode"
OR
You can try to get oracle client to do this conversion for you. It should do this automatically.
but you would need to setup both OS locale and NLS_LANG to your Japanese character set and see if it does work or not. You may feel that I'm not 100% sure here...
OR
You can try to use inbuilt CONVERT oracle function if you use an application server or other tool but not an standard client...
http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/functions034.htm#SQLRF00620
HTH, Zoltan

[SOLVED]Need Shift-JIS to wine a Japanese game (or not)

The game in question is Little Busters.
I have heard at animesuki forums that the game runs fine with winelocale. Thing is, winelocale is for ubuntu. I used to use ubuntu, and I could probbably go back to it, but I know I'd complain about something and distro hopping isn't a good habit.
So I want to try to get this game working on Arch.
I think the first step I need is to get Shift-JIS locales in Arch. It is not in the /etc/locale.gen file and I tried adding it with similar syntax and that just gave me an error.
EDIT: Got a working crack. Thanks Procyon.
Last edited by sokuban (2008-09-21 19:39:48)

Procyon wrote:
I think it comes down to uncommenting ja_JP.UTF-8 in /etc/locale.gen, running locale-gen, and then LANG=ja_JP.UTF-8 wine program_name.exe
At least, this has worked for me for a PC98 emulator, and some Japanese shmups.
Not using LANG=ja_JP.UTF-8 makes me see only blocks.
EDIT:
And fonts maybe... I don't know where I got it all, but my Windows/fonts is 100MB.
Wow that seemed to work. I didn't even need Shift-JIS or winelocale. Before I tested with just "LANG=ja_JP wine exe" and that worked with some programs but not this one for some reason.
Thanks.
I'm pretty sure winelocale doesn't work on Archlinux. The guy said it probbably doesn't work on debian even. Though the guy said that to use it you need to install Shift-JIS which is available on ubuntu, and said something about lang= not working well with Shift-JIS because it wasn't ASCII compatible or something. That's why I thought I had to get that locale.
Yes, I know Japanese. Its a bit of a pain sometimes since there are all sorts of problems Linux has with Japanese. Though I have even more problems since I need Chinese as well. (I've got the whole mess somehow sorted out now, but before I had problems with Japanese fonts breaking Chinese fonts and all.)
Slightly offtopic but what PC98 emulator did you get working with Linux? Anex?
EDIT: Well the install worked fine, but the actual game gives me
err:aspi:SCSI_OpenDevice Failed to open device /dev/sg0: 許可がありません
That error many times until an error with gibberish comes up. The Japanese in the Failed to open device error means no permissions.
Last edited by sokuban (2008-09-15 19:28:46)

What do you do when SJIS isn't Shift JIS

Using Tomcat 4.01 I put the following directive into
JSP pages
<%@ page contentType="text/html; charset=Shift_JIS" %>
A quick test on the database I am using shows that a small percentage of (Japanese) peoples names don't pass through the unicode <=> SJIS conversion. What is more concerning is that 100% of the Japanese addresses in the database don't pass through the conversion cleanly.
If I use the MS932 or Cp943 encodings the tests work
but how can I get Tomcat to use MS932 or Cp943 ?

I assume you are gathering data in a form in which you have specified Shift_JIS as the charset...
It turns out that many JSP containers do not convert form data to Unicode correctly. They often assume incoming data is in the charset of the JSP container or simply in 8859-1. This may be the source of your problems.
One workaround may be the following:
1. include a hidden charset field in the form
2. read the charset from the posted form
3. use that charset to help you retrieve the correct data from the form.
Regards,
John O'Conner

Japanese hotmail

I've got an issue with cfmail japanese encoding with
registered japanese hotmail accounts.
My cfmail comes up garbled in these type account, but the
proper japanese character comes out fine
in other mail formats.
Can anyone explain to me what is going on here? and if there
is a solution to japanese registered
hotmail.
thnx
mookie

Hi Mookie,
I tried to type Japanese characters (mixture between kanji,
hiragana and katakana) in Dreamweaver 8.0.2 (in these encodings:
Japanese EUC, Japanese Shift-JIS, Unicode UTF-8) and sent it to my
Japanese Yahoo account (got no Hotmail) and it doesn't work also.
But when I typed it in Notepad (UTF-8) and sent it to the
same account, it works.
No idea why .. maybe I don't know how to format it in
Dreamweaver but it works well in Notepad.
<cfmail to="" subject="test" type="html" from="test">
Testing 
[期間限定]ネットでお得な
金利キャンペーン実施中！
 
</cfmail>
Regards,
Keiko

Migrating Japanese Characters from MS SQL Server 2000 to Oracle 9i usng Jsp

Hi ,
I have a situation where the Japanese characters are to be migrated from MS SQL Server 2000 to Oracle 91 and then render the same using JSP.
I followed the below approach,
1. Extract the Japanese data from MS SQL Server and generate an XML
2. Parse the XML and store it into Oracle 9i database which is of UTF-8 encoding.
3. On retreiving and rendering using the Shift-JIS adds few junk characters additionally.
When I try to copy paste the Japanese contents from XML to a text file, it is working fine.
Could some one help me in resolving this issue?
It is very urgent, and any help would be greatly appreciated.

There is documentation in the reference guide sent with the workbench, there is this discussion forum, the support web page (which includes tech notes and FAQ's), and the company specific procedural language documentation.
There is also an older document for use with the old sybase toolkits which may be obscelete, and there are some internal documents which were for internal consumption.
Turloch
Oracle Migration Workbench Team

File character encoding format conversion

Hi People,
uname -a
Linux abcd.us.com 2.6.32-400.21.1.el5uek #1 SMP Wed Feb 20 01:35:01 PST 2013 x86_64 x86_64 x86_64 GNU/Linux
I am trying to convert a file abcd.dat
# file abcd.dat
abcd.dat: binary Computer Graphics Metafile
#file -i abcd.dat
abcd.dat: application/octet-stream
I've tried dos2unix in vain.
dos2unix: converting file abcd.dat to UNIX format ...
dos2unix: converting file abc.dat to UNIX format ...
dos2unix: problems converting file abc.dat
I've used iconv successfully earlier with this command
iconv -f UTF-16 -t UTF-8 abcd.dat > abcd.abc
only, this time I do not know the "from" format of the file,
#iconv -l
The following list contain all the coded character sets known. This does
not necessarily mean that all combinations of these names can be used for
the FROM and TO command line parameters. One coded character set can be
listed with several different names (aliases).
437, 500, 500V1, 850, 851, 852, 855, 856, 857, 860, 861, 862, 863, 864, 865,
866, 866NAV, 869, 874, 904, 1026, 1046, 1047, 8859_1, 8859_2, 8859_3, 8859_4,
8859_5, 8859_6, 8859_7, 8859_8, 8859_9, 10646-1:1993, 10646-1:1993/UCS4,
ANSI_X3.4-1968, ANSI_X3.4-1986, ANSI_X3.4, ANSI_X3.110-1983, ANSI_X3.110,
ARABIC, ARABIC7, ARMSCII-8, ASCII, ASMO-708, ASMO_449, BALTIC, BIG-5,
BIG-FIVE, BIG5-HKSCS, BIG5, BIG5HKSCS, BIGFIVE, BS_4730, CA, CN-BIG5, CN-GB,
CN, CP-AR, CP-GR, CP-HU, CP037, CP038, CP273, CP274, CP275, CP278, CP280,
CP281, CP282, CP284, CP285, CP290, CP297, CP367, CP420, CP423, CP424, CP437,
CP500, CP737, CP775, CP803, CP813, CP819, CP850, CP851, CP852, CP855, CP856,
CP857, CP860, CP861, CP862, CP863, CP864, CP865, CP866, CP866NAV, CP868,
CP869, CP870, CP871, CP874, CP875, CP880, CP891, CP901, CP902, CP903, CP904,
CP905, CP912, CP915, CP916, CP918, CP920, CP921, CP922, CP930, CP932, CP933,
CP935, CP936, CP937, CP939, CP949, CP950, CP1004, CP1008, CP1025, CP1026,
CP1046, CP1047, CP1070, CP1079, CP1081, CP1084, CP1089, CP1097, CP1112,
CP1122, CP1123, CP1124, CP1125, CP1129, CP1130, CP1132, CP1133, CP1137,
CP1140, CP1141, CP1142, CP1143, CP1144, CP1145, CP1146, CP1147, CP1148,
CP1149, CP1153, CP1154, CP1155, CP1156, CP1157, CP1158, CP1160, CP1161,
CP1162, CP1163, CP1164, CP1166, CP1167, CP1250, CP1251, CP1252, CP1253,
CP1254, CP1255, CP1256, CP1257, CP1258, CP1361, CP1364, CP1371, CP1388,
CP1390, CP1399, CP4517, CP4899, CP4909, CP4971, CP5347, CP9030, CP9066,
CP9448, CP10007, CP12712, CP16804, CPIBM861, CSA7-1, CSA7-2, CSASCII,
CSA_T500-1983, CSA_T500, CSA_Z243.4-1985-1, CSA_Z243.4-1985-2,
CSA_Z243.419851, CSA_Z243.419852, CSDECMCS, CSEBCDICATDE, CSEBCDICATDEA,
CSEBCDICCAFR, CSEBCDICDKNO, CSEBCDICDKNOA, CSEBCDICES, CSEBCDICESA,
CSEBCDICESS, CSEBCDICFISE, CSEBCDICFISEA, CSEBCDICFR, CSEBCDICIT, CSEBCDICPT,
CSEBCDICUK, CSEBCDICUS, CSEUCKR, CSEUCPKDFMTJAPANESE, CSGB2312, CSHPROMAN8,
CSIBM037, CSIBM038, CSIBM273, CSIBM274, CSIBM275, CSIBM277, CSIBM278,
CSIBM280, CSIBM281, CSIBM284, CSIBM285, CSIBM290, CSIBM297, CSIBM420,
CSIBM423, CSIBM424, CSIBM500, CSIBM803, CSIBM851, CSIBM855, CSIBM856,
CSIBM857, CSIBM860, CSIBM863, CSIBM864, CSIBM865, CSIBM866, CSIBM868,
CSIBM869, CSIBM870, CSIBM871, CSIBM880, CSIBM891, CSIBM901, CSIBM902,
CSIBM903, CSIBM904, CSIBM905, CSIBM918, CSIBM921, CSIBM922, CSIBM930,
CSIBM932, CSIBM933, CSIBM935, CSIBM937, CSIBM939, CSIBM943, CSIBM1008,
CSIBM1025, CSIBM1026, CSIBM1097, CSIBM1112, CSIBM1122, CSIBM1123, CSIBM1124,
CSIBM1129, CSIBM1130, CSIBM1132, CSIBM1133, CSIBM1137, CSIBM1140, CSIBM1141,
CSIBM1142, CSIBM1143, CSIBM1144, CSIBM1145, CSIBM1146, CSIBM1147, CSIBM1148,
CSIBM1149, CSIBM1153, CSIBM1154, CSIBM1155, CSIBM1156, CSIBM1157, CSIBM1158,
CSIBM1160, CSIBM1161, CSIBM1163, CSIBM1164, CSIBM1166, CSIBM1167, CSIBM1364,
CSIBM1371, CSIBM1388, CSIBM1390, CSIBM1399, CSIBM4517, CSIBM4899, CSIBM4909,
CSIBM4971, CSIBM5347, CSIBM9030, CSIBM9066, CSIBM9448, CSIBM12712,
CSIBM16804, CSIBM11621162, CSISO4UNITEDKINGDOM, CSISO10SWEDISH,
CSISO11SWEDISHFORNAMES, CSISO14JISC6220RO, CSISO15ITALIAN, CSISO16PORTUGESE,
CSISO17SPANISH, CSISO18GREEK7OLD, CSISO19LATINGREEK, CSISO21GERMAN,
CSISO25FRENCH, CSISO27LATINGREEK1, CSISO49INIS, CSISO50INIS8,
CSISO51INISCYRILLIC, CSISO58GB1988, CSISO60DANISHNORWEGIAN,
CSISO60NORWEGIAN1, CSISO61NORWEGIAN2, CSISO69FRENCH, CSISO84PORTUGUESE2,
CSISO85SPANISH2, CSISO86HUNGARIAN, CSISO88GREEK7, CSISO89ASMO449, CSISO90,
CSISO92JISC62991984B, CSISO99NAPLPS, CSISO103T618BIT, CSISO111ECMACYRILLIC,
CSISO121CANADIAN1, CSISO122CANADIAN2, CSISO139CSN369103, CSISO141JUSIB1002,
CSISO143IECP271, CSISO150, CSISO150GREEKCCITT, CSISO151CUBA,
CSISO153GOST1976874, CSISO646DANISH, CSISO2022CN, CSISO2022JP, CSISO2022JP2,
CSISO2022KR, CSISO2033, CSISO5427CYRILLIC, CSISO5427CYRILLIC1981,
CSISO5428GREEK, CSISO10367BOX, CSISOLATIN1, CSISOLATIN2, CSISOLATIN3,
CSISOLATIN4, CSISOLATIN5, CSISOLATIN6, CSISOLATINARABIC, CSISOLATINCYRILLIC,
CSISOLATINGREEK, CSISOLATINHEBREW, CSKOI8R, CSKSC5636, CSMACINTOSH,
CSNATSDANO, CSNATSSEFI, CSN_369103, CSPC8CODEPAGE437, CSPC775BALTIC,
CSPC850MULTILINGUAL, CSPC862LATINHEBREW, CSPCP852, CSSHIFTJIS, CSUCS4,
CSUNICODE, CSWINDOWS31J, CUBA, CWI-2, CWI, CYRILLIC, DE, DEC-MCS, DEC,
DECMCS, DIN_66003, DK, DS2089, DS_2089, E13B, EBCDIC-AT-DE-A, EBCDIC-AT-DE,
EBCDIC-BE, EBCDIC-BR, EBCDIC-CA-FR, EBCDIC-CP-AR1, EBCDIC-CP-AR2,
EBCDIC-CP-BE, EBCDIC-CP-CA, EBCDIC-CP-CH, EBCDIC-CP-DK, EBCDIC-CP-ES,
EBCDIC-CP-FI, EBCDIC-CP-FR, EBCDIC-CP-GB, EBCDIC-CP-GR, EBCDIC-CP-HE,
EBCDIC-CP-IS, EBCDIC-CP-IT, EBCDIC-CP-NL, EBCDIC-CP-NO, EBCDIC-CP-ROECE,
EBCDIC-CP-SE, EBCDIC-CP-TR, EBCDIC-CP-US, EBCDIC-CP-WT, EBCDIC-CP-YU,
EBCDIC-CYRILLIC, EBCDIC-DK-NO-A, EBCDIC-DK-NO, EBCDIC-ES-A, EBCDIC-ES-S,
EBCDIC-ES, EBCDIC-FI-SE-A, EBCDIC-FI-SE, EBCDIC-FR, EBCDIC-GREEK, EBCDIC-INT,
EBCDIC-INT1, EBCDIC-IS-FRISS, EBCDIC-IT, EBCDIC-JP-E, EBCDIC-JP-KANA,
EBCDIC-PT, EBCDIC-UK, EBCDIC-US, EBCDICATDE, EBCDICATDEA, EBCDICCAFR,
EBCDICDKNO, EBCDICDKNOA, EBCDICES, EBCDICESA, EBCDICESS, EBCDICFISE,
EBCDICFISEA, EBCDICFR, EBCDICISFRISS, EBCDICIT, EBCDICPT, EBCDICUK, EBCDICUS,
ECMA-114, ECMA-118, ECMA-128, ECMA-CYRILLIC, ECMACYRILLIC, ELOT_928, ES, ES2,
EUC-CN, EUC-JISX0213, EUC-JP-MS, EUC-JP, EUC-KR, EUC-TW, EUCCN, EUCJP-MS,
EUCJP-OPEN, EUCJP-WIN, EUCJP, EUCKR, EUCTW, FI, FR, GB, GB2312, GB13000,
GB18030, GBK, GB_1988-80, GB_198880, GEORGIAN-ACADEMY, GEORGIAN-PS,
GOST_19768-74, GOST_19768, GOST_1976874, GREEK-CCITT, GREEK, GREEK7-OLD,
GREEK7, GREEK7OLD, GREEK8, GREEKCCITT, HEBREW, HP-ROMAN8, HPROMAN8, HU,
IBM-803, IBM-856, IBM-901, IBM-902, IBM-921, IBM-922, IBM-930, IBM-932,
IBM-933, IBM-935, IBM-937, IBM-939, IBM-943, IBM-1008, IBM-1025, IBM-1046,
IBM-1047, IBM-1097, IBM-1112, IBM-1122, IBM-1123, IBM-1124, IBM-1129,
IBM-1130, IBM-1132, IBM-1133, IBM-1137, IBM-1140, IBM-1141, IBM-1142,
IBM-1143, IBM-1144, IBM-1145, IBM-1146, IBM-1147, IBM-1148, IBM-1149,
IBM-1153, IBM-1154, IBM-1155, IBM-1156, IBM-1157, IBM-1158, IBM-1160,
IBM-1161, IBM-1162, IBM-1163, IBM-1164, IBM-1166, IBM-1167, IBM-1364,
IBM-1371, IBM-1388, IBM-1390, IBM-1399, IBM-4517, IBM-4899, IBM-4909,
IBM-4971, IBM-5347, IBM-9030, IBM-9066, IBM-9448, IBM-12712, IBM-16804,
IBM037, IBM038, IBM256, IBM273, IBM274, IBM275, IBM277, IBM278, IBM280,
IBM281, IBM284, IBM285, IBM290, IBM297, IBM367, IBM420, IBM423, IBM424,
IBM437, IBM500, IBM775, IBM803, IBM813, IBM819, IBM848, IBM850, IBM851,
IBM852, IBM855, IBM856, IBM857, IBM860, IBM861, IBM862, IBM863, IBM864,
IBM865, IBM866, IBM866NAV, IBM868, IBM869, IBM870, IBM871, IBM874, IBM875,
IBM880, IBM891, IBM901, IBM902, IBM903, IBM904, IBM905, IBM912, IBM915,
IBM916, IBM918, IBM920, IBM921, IBM922, IBM930, IBM932, IBM933, IBM935,
IBM937, IBM939, IBM943, IBM1004, IBM1008, IBM1025, IBM1026, IBM1046, IBM1047,
IBM1089, IBM1097, IBM1112, IBM1122, IBM1123, IBM1124, IBM1129, IBM1130,
IBM1132, IBM1133, IBM1137, IBM1140, IBM1141, IBM1142, IBM1143, IBM1144,
IBM1145, IBM1146, IBM1147, IBM1148, IBM1149, IBM1153, IBM1154, IBM1155,
IBM1156, IBM1157, IBM1158, IBM1160, IBM1161, IBM1162, IBM1163, IBM1164,
IBM1166, IBM1167, IBM1364, IBM1371, IBM1388, IBM1390, IBM1399, IBM4517,
IBM4899, IBM4909, IBM4971, IBM5347, IBM9030, IBM9066, IBM9448, IBM12712,
IBM16804, IEC_P27-1, IEC_P271, INIS-8, INIS-CYRILLIC, INIS, INIS8,
INISCYRILLIC, ISIRI-3342, ISIRI3342, ISO-2022-CN-EXT, ISO-2022-CN,
ISO-2022-JP-2, ISO-2022-JP-3, ISO-2022-JP, ISO-2022-KR, ISO-8859-1,
ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7,
ISO-8859-8, ISO-8859-9, ISO-8859-10, ISO-8859-11, ISO-8859-13, ISO-8859-14,
ISO-8859-15, ISO-8859-16, ISO-10646, ISO-10646/UCS2, ISO-10646/UCS4,
ISO-10646/UTF-8, ISO-10646/UTF8, ISO-CELTIC, ISO-IR-4, ISO-IR-6, ISO-IR-8-1,
ISO-IR-9-1, ISO-IR-10, ISO-IR-11, ISO-IR-14, ISO-IR-15, ISO-IR-16, ISO-IR-17,
ISO-IR-18, ISO-IR-19, ISO-IR-21, ISO-IR-25, ISO-IR-27, ISO-IR-37, ISO-IR-49,
ISO-IR-50, ISO-IR-51, ISO-IR-54, ISO-IR-55, ISO-IR-57, ISO-IR-60, ISO-IR-61,
ISO-IR-69, ISO-IR-84, ISO-IR-85, ISO-IR-86, ISO-IR-88, ISO-IR-89, ISO-IR-90,
ISO-IR-92, ISO-IR-98, ISO-IR-99, ISO-IR-100, ISO-IR-101, ISO-IR-103,
ISO-IR-109, ISO-IR-110, ISO-IR-111, ISO-IR-121, ISO-IR-122, ISO-IR-126,
ISO-IR-127, ISO-IR-138, ISO-IR-139, ISO-IR-141, ISO-IR-143, ISO-IR-144,
ISO-IR-148, ISO-IR-150, ISO-IR-151, ISO-IR-153, ISO-IR-155, ISO-IR-156,
ISO-IR-157, ISO-IR-166, ISO-IR-179, ISO-IR-193, ISO-IR-197, ISO-IR-199,
ISO-IR-203, ISO-IR-209, ISO-IR-226, ISO/TR_11548-1, ISO646-CA, ISO646-CA2,
ISO646-CN, ISO646-CU, ISO646-DE, ISO646-DK, ISO646-ES, ISO646-ES2, ISO646-FI,
ISO646-FR, ISO646-FR1, ISO646-GB, ISO646-HU, ISO646-IT, ISO646-JP-OCR-B,
ISO646-JP, ISO646-KR, ISO646-NO, ISO646-NO2, ISO646-PT, ISO646-PT2,
ISO646-SE, ISO646-SE2, ISO646-US, ISO646-YU, ISO2022CN, ISO2022CNEXT,
ISO2022JP, ISO2022JP2, ISO2022KR, ISO6937, ISO8859-1, ISO8859-2, ISO8859-3,
ISO8859-4, ISO8859-5, ISO8859-6, ISO8859-7, ISO8859-8, ISO8859-9, ISO8859-10,
ISO8859-11, ISO8859-13, ISO8859-14, ISO8859-15, ISO8859-16, ISO11548-1,
ISO88591, ISO88592, ISO88593, ISO88594, ISO88595, ISO88596, ISO88597,
ISO88598, ISO88599, ISO885910, ISO885911, ISO885913, ISO885914, ISO885915,
ISO885916, ISO_646.IRV:1991, ISO_2033-1983, ISO_2033, ISO_5427-EXT, ISO_5427,
ISO_5427:1981, ISO_5427EXT, ISO_5428, ISO_5428:1980, ISO_6937-2,
ISO_6937-2:1983, ISO_6937, ISO_6937:1992, ISO_8859-1, ISO_8859-1:1987,
ISO_8859-2, ISO_8859-2:1987, ISO_8859-3, ISO_8859-3:1988, ISO_8859-4,
ISO_8859-4:1988, ISO_8859-5, ISO_8859-5:1988, ISO_8859-6, ISO_8859-6:1987,
ISO_8859-7, ISO_8859-7:1987, ISO_8859-7:2003, ISO_8859-8, ISO_8859-8:1988,
ISO_8859-9, ISO_8859-9:1989, ISO_8859-10, ISO_8859-10:1992, ISO_8859-14,
ISO_8859-14:1998, ISO_8859-15, ISO_8859-15:1998, ISO_8859-16,
ISO_8859-16:2001, ISO_9036, ISO_10367-BOX, ISO_10367BOX, ISO_11548-1,
ISO_69372, IT, JIS_C6220-1969-RO, JIS_C6229-1984-B, JIS_C62201969RO,
JIS_C62291984B, JOHAB, JP-OCR-B, JP, JS, JUS_I.B1.002, KOI-7, KOI-8, KOI8-R,
KOI8-T, KOI8-U, KOI8, KOI8R, KOI8U, KSC5636, L1, L2, L3, L4, L5, L6, L7, L8,
L10, LATIN-9, LATIN-GREEK-1, LATIN-GREEK, LATIN1, LATIN2, LATIN3, LATIN4,
LATIN5, LATIN6, LATIN7, LATIN8, LATIN10, LATINGREEK, LATINGREEK1,
MAC-CYRILLIC, MAC-IS, MAC-SAMI, MAC-UK, MAC, MACCYRILLIC, MACINTOSH, MACIS,
MACUK, MACUKRAINIAN, MIK, MS-ANSI, MS-ARAB, MS-CYRL, MS-EE, MS-GREEK,
MS-HEBR, MS-MAC-CYRILLIC, MS-TURK, MS932, MS936, MSCP949, MSCP1361,
MSMACCYRILLIC, MSZ_7795.3, MS_KANJI, NAPLPS, NATS-DANO, NATS-SEFI, NATSDANO,
NATSSEFI, NC_NC0010, NC_NC00-10, NC_NC00-10:81, NF_Z_62-010,
NF_Z_62-010_(1973), NF_Z_62-010_1973, NF_Z_62010, NF_Z_62010_1973, NO, NO2,
NS_4551-1, NS_4551-2, NS_45511, NS_45512, OS2LATIN1, OSF00010001,
OSF00010002, OSF00010003, OSF00010004, OSF00010005, OSF00010006, OSF00010007,
OSF00010008, OSF00010009, OSF0001000A, OSF00010020, OSF00010100, OSF00010101,
OSF00010102, OSF00010104, OSF00010105, OSF00010106, OSF00030010, OSF0004000A,
OSF0005000A, OSF05010001, OSF100201A4, OSF100201A8, OSF100201B5, OSF100201F4,
OSF100203B5, OSF1002011C, OSF1002011D, OSF1002035D, OSF1002035E, OSF1002035F,
OSF1002036B, OSF1002037B, OSF10010001, OSF10020025, OSF10020111, OSF10020115,
OSF10020116, OSF10020118, OSF10020122, OSF10020129, OSF10020352, OSF10020354,
OSF10020357, OSF10020359, OSF10020360, OSF10020364, OSF10020365, OSF10020366,
OSF10020367, OSF10020370, OSF10020387, OSF10020388, OSF10020396, OSF10020402,
OSF10020417, PT, PT2, PT154, R8, RK1048, ROMAN8, RUSCII, SE, SE2,
SEN_850200_B, SEN_850200_C, SHIFT-JIS, SHIFT_JIS, SHIFT_JISX0213, SJIS-OPEN,
SJIS-WIN, SJIS, SS636127, STRK1048-2002, ST_SEV_358-88, T.61-8BIT, T.61,
T.618BIT, TCVN-5712, TCVN, TCVN5712-1, TCVN5712-1:1993, TIS-620, TIS620-0,
TIS620.2529-1, TIS620.2533-0, TIS620, TS-5881, TSCII, UCS-2, UCS-2BE,
UCS-2LE, UCS-4, UCS-4BE, UCS-4LE, UCS2, UCS4, UHC, UJIS, UK, UNICODE,
UNICODEBIG, UNICODELITTLE, US-ASCII, US, UTF-7, UTF-8, UTF-16, UTF-16BE,
UTF-16LE, UTF-32, UTF-32BE, UTF-32LE, UTF7, UTF8, UTF16, UTF16BE, UTF16LE,
UTF32, UTF32BE, UTF32LE, VISCII, WCHAR_T, WIN-SAMI-2, WINBALTRIM,
WINDOWS-31J, WINDOWS-874, WINDOWS-936, WINDOWS-1250, WINDOWS-1251,
WINDOWS-1252, WINDOWS-1253, WINDOWS-1254, WINDOWS-1255, WINDOWS-1256,
WINDOWS-1257, WINDOWS-1258, WINSAMI2, WS2, YU
==================================================
also,
#which od
/usr/bin/od
but I don't know how to use it.
==================================
#cat -v abcd.dat
has a lot of ^@
===================================
#echo $LANG
en_US.UTF-8
======================================================================================
#hexdump -C abcd.dat|head -5
00000000 00 22 00 34 00 36 00 32 00 39 00 33 00 22 00 7c |.".4.6.2.9.3.".||
00000010 00 22 00 32 00 30 00 31 00 33 00 2d 00 31 00 31 |.".2.0.1.3.-.1.1|
00000020 00 2d 00 31 00 38 00 20 00 30 00 38 00 3a 00 30 |.-.1.8. .0.8.:.0|
00000030 00 39 00 3a 00 34 00 38 00 22 00 7c 00 22 00 33 |.9.:.4.8.".|.".3|
00000040 00 36 00 37 00 22 00 7c 00 22 00 53 00 75 00 73 |.6.7.".|.".S.u.s|
=======================================================================================
#vi abcd.tst
testing
esc:wq
#file abcd.tst
abcd.tst: ASCII text
Let me know the complete iconv command with from-and-to encoding.
Appreciate any help.

Hi BalusC,
as we write in jsp page as <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
is their something we can write in .properties file
russian words are not correctly displayed in browser......how we can dispaly it in correct format...??
i have all russian words in my .properties file
Thanks a lot

Japanese characters display with wrong encoding all of a sudden...

I had no issues before when it came to typing in Japanese in DW using the windows language bar , I would just change the keyboard to JP(japanese) and then start typing within DW code view, but then one day after doing updating my main template and using the find and replace feature in DW all the Japanese characters turned into question marks, diamonds with question marks and ASCII alphanumeric codes..
also the spaces in my documents turned into blocks. It was a mess,
*I don't know if it was something I triggered accidentaly or if it was some type of bug....I also remember copying and pasting text and Japanese characters from another website that I created(but I had done that a dozen times before and it was never a problem).
Long story short, after not being able to find a solution I decided to manually delete the weird symbols and start over, I typed in Japanese using the windows language bar as always and began typing away inside the same pages that displayed those weird characters (sorry I don't know what the proper name for them is)and it accepted the Japanese characters with no issues, it was working just like it did before.
but my question is "What happened?" was that a bug in DW or was it something on my end?
I would like to know so I can fix the problem incase this happens again.
I've always had utf-8 as the charset and it's never been an issue. (and I all my pages are saved as utf-8 as well)
--Which is why I am confused why all the Japanese got messed up.
Here is the head code of one of the pages that had the problem:
Thank you.

Without seeing an actual page, it's impossible to say what happened, but the most likely explanation is that you did something wrong. Asian characters, such as Japanese, require correct encoding. If the encoding is incorrect, you end up with mojibake.
I suspect that what happened is that you copied and pasted from Shift-JIS or EUC-JP encoding into a different encoding. It's quite possible that your page was set to iso-8859-1 (Western European) without realizing.
By the way, your head code didn't show up in your post.

Encoding issue with Chinese and Japanese characters but not for Korean

Hi All,
I am dealing with the problem below and have tried a lot of options to correct this. Could anyone help me resolve the issue?
Some japanese text is returned to my jsp from SAP, the text looks like PTú÷»à .
When I manually set the encoding of my browser to Shift-JIS, the problem is resolved and the text is seen as １５日締当月末現金
However, I set my response.setContentType as Shift-JIS, the browser automatically selects the encoding as Shift-JIS, but my characters get displayed as ??????
I had a similar problem with Korean characters, and I used,
decodedString = new String(strToBeDecoded.getBytes("iso-8859-1"),"EUC-KR");
It worked and I did not have to use the setContentType method of servlet response. This code however does not work for either Japanese or Chinese characters.
Please let me know, if there is anyway of getting the characters right on the screen.
I am using Sun Java Application Server 8.1.
Thanks,
Priya

Get rid of legacy character encodings and just use UTF-8 all the way.
Read this to learn more: [http://balusc.blogspot.com/2009/05/unicode-how-to-get-characters-right.html].

Chinese Characters on Zen Mi

(repost in Asia forums as it might be more appropriate)
I have just got the Zen Micro and must say I am quite impressed with it overall. However, there is one problem which really prevents me from enjoying the player, and that is that the player is unable to display the Simplified Chinese ID Tags of my mp3s properly. The ID tags of these tracks are readable in Windows Media Player 0, but when I transfer it over to the Zen Micro, they show up as glibberish. I have tried using Mediasource, but it refuses to even load some of these tracks, while syncing the tracks through My Computer simply causes Windows Explorer to crash.
I believe that there is nothing wrong per se with the tagging of my tracks as these tracks display flawlessly in my other mp3 players like my iPod and my iRi'ver player, so I'm afraid the problem might lie with the Zen Micro itself.. is there an issue with transferring tracks with chinese ID tags using an English Language version of Windows and how do I overcome this problem? I am quite frustrated as quite a large number of my favourite songs are tagged in chinese... hope the Creative engineers can try to fix this problem, perhaps with the WMP0 plugin for the player?I have tried following the instructions in the Knowledge Base regarding Chinese tagged files, but to no avail as they seem to refer to another version of Mediasource. I have spent many hours trying to find a solution to this problem but to no avail, hope someone can help!

I just got the Zen Micro a few days ago and I do like it very much (even though I think the FM reception could be further improved upon). The only thing that has prevented me from fully enjoying my player is the problem I'm experiencing displaying non-English track info. Most of my files are tagged in Japanese Shift-JIS and they're fine on my computer when my Japanese software is turned on, but it *just* won't display correctly on my player and it's getting frustrating (the Zen Micro *is* supposed to be able to display East Asian languages, no?). I've tried everything I could think of.
) I can't change the language and regional settings on my computer to Japanese (or Chinese for that matter) since I'm running WinME and there aren't any options for me to do that anyway.
2) Changed the settings in the Music Library (using the Zen Micro Media Explorer) to Japanese. My Micro displayed nonsense.
3) Tried dragging and dropping to the Media Library. Same garbage.
4) Tried changing the encoding method from Shift-JIS to EUC-JIS. Shows up as a different set of gibberish this time.
5) I've contacted customer support and done whatever they've told me (rip from the CD using WMP9, rename the file in Japanese, transfer to CMS, then PC Music Library and then to the player). I've tried transferring from WMP to the Zen Micro itself as well. Still no go.
I've even changed the display language in the player itself to Japanese but it's still not working.
Help would be much appreciated. Help please? Somebody? Anybody?
Message Edited by betelgeusian on 2-27-2004 0:29 PM
Message Edited by betelgeusian on 2-27-2004 0:37 PM

Encoding problem (via ORB)

Hello,
I posted this problem few months ago, but still havent been able to solve this.
I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
The server returns string containing chinese characters to the client.
However, my chinese characters dont appear properly on the client side.
If i run the client on the Solaris OS there is no problem with it.
I tried converting the encode of the string by getting its byte and creating
a new string with encoding parameter. None of this seems to work.
I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
show properly.
Any ideas on how i can overcome this encoding problem where the C/S is
communicating via CORBA (ORB)?
Thanks in advance.

Thanks for your reply
Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
Following is a example URL
It's a MAC discussing froum with BIG5 encoding in Taiwan.
http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
It's a froum topic posted by me. I input some japanese into this topic
If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

Character encoding across Web application contexts

 If I submit an HTTP request encoded in SHIFT-JIS across Web application contexts,
 the characters seem to get mangled. Do I need to do anything special to pass request
 objects that are encoded in SHIFT-JIS to another context.


a. EUC-JP
EUC is Extended Unix Code.
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=x-euc-jp">x-euc-jp should be EUC-JP. You use x- for non-registered
encoding names with IANA.
b. JIS
Japanese Industrial Standard
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=iso-2022-jp">To be precise, JIS means nothing. JIS has many standards.
It is an ISO-2022 encoding applied to JIS code sets.
c. Shift_JIS
Microsoft's Japanese encoding method loosly based on
JIS.
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=x-sjis">Use "charset=Shift_JIS" in most cases.
>
d. UTF-8You use charset=UTF-8.
- Which one of the above 4 I should use? Either one is fine as long as you include the meta tag
in HTML. If you want to support older generation of
browsers, then skip UTF-8. If you target i-mode
phone browser, use Shift_JIS.
- Do I have to worry about the encoding of the
Japanese data being entered by user in the input
fields in the HTML form?Yes. Use the same encoding as the encoding of the form.
Make sure to call response.setEncoding to set the
enxoding for the parameter processing.
- What should be encoding of the content of html
output generated by the JSP?Use contentType tag in page directive.

ISO-2022-JP support and ISO-2022-JP-2 escape sequences

I have a mail generated by Outook with some Japanese text in. Outlook has set the charset as ISO-2022-JP. The ISO-2022-JP encoded text of the mail can be found here.
Java 1.5 and 1.6 fail to load this text properly when using the ISO-2022-JP charset. The description of this charset is JIS X 0201, 0208, in ISO 2022 form, Japanese. I'm guessing that the problem is due to the use of an escape sequence that is defined in [ISO-2022-JP-2|http://www.mhonarc.jp/RFC/rfc1554.txt]. The escape sequence is hex 1B 24 42, which means that the charset is JIS X 0208-1983.
There's no ISO-2022-JP-2 charset support in Java 1.5, not sure about 1.6.
I'm thinking about writing a filter reader as a hack to add support for ISO-2022-JP-2. I guess that if I remove the escape sequence, the text should load properly using one of Shift-JIS, EUC-JP or ISO 2022 JP. Any suggestions?
Edited by: bobajobrob on Mar 25, 2008 12:19 PM

1B 24 42 (ESC $ B) is valid in ISO-2022-JP. However, the text file includes invalid characters in the JIS X 0208 standard. The ISO-2022-JP converter in Java strictly follows the standards.
There are some ISO-2022-JP "variants" that are supported under different encoding names with compatibility workarounds. Please refer to Sun's bug ID 6173388 for details.

Chinese characters on zen touc

is it possible to have chinese titles and track information on zen touch ?

I just got the Zen Micro a few days ago and I do like it very much (even though I think the FM reception could be further improved upon). The only thing that has prevented me from fully enjoying my player is the problem I'm experiencing displaying non-English track info. Most of my files are tagged in Japanese Shift-JIS and they're fine on my computer when my Japanese software is turned on, but it *just* won't display correctly on my player and it's getting frustrating (the Zen Micro *is* supposed to be able to display East Asian languages, no?). I've tried everything I could think of.
) I can't change the language and regional settings on my computer to Japanese (or Chinese for that matter) since I'm running WinME and there aren't any options for me to do that anyway.
2) Changed the settings in the Music Library (using the Zen Micro Media Explorer) to Japanese. My Micro displayed nonsense.
3) Tried dragging and dropping to the Media Library. Same garbage.
4) Tried changing the encoding method from Shift-JIS to EUC-JIS. Shows up as a different set of gibberish this time.
5) I've contacted customer support and done whatever they've told me (rip from the CD using WMP9, rename the file in Japanese, transfer to CMS, then PC Music Library and then to the player). I've tried transferring from WMP to the Zen Micro itself as well. Still no go.
I've even changed the display language in the player itself to Japanese but it's still not working.
Help would be much appreciated. Help please? Somebody? Anybody?
Message Edited by betelgeusian on 2-27-2004 0:29 PM
Message Edited by betelgeusian on 2-27-2004 0:37 PM

EUC to Shift JIS Migration

Similar Messages

Maybe you are looking for