all groups > dotnet internationalization > september 2006 >
You're in the

dotnet internationalization

group:

Display iso-8859-1 characters using codepage 28591



Display iso-8859-1 characters using codepage 28591 tobi
9/19/2006 6:00:02 AM
dotnet internationalization: hello all,

Using framework 2.0 I have to display a text, given as a xml data file.
The given text contains extended unicode data (see below '↑' represents
arrow up 8593 )
<?xml version="1.0" encoding="iso-8859-1" ?>
<help>
<display>↑</display>
</help>

According to the Encoding class, the codepage for iso-8859-1 holds the
WindowsCodePage 28591 which mapped to codepage Windows-1252.

No culture settings displays the right sign on my DotNet Form.

How is it possible to display unicode characters from changing encodings on
my form.

do a japanese website which is integrated an US
english e-commerce website. the japanese folks whom we work with
currently have a translation program (in VB) which supposedly
translates the japanese (postal) address into a corresponding english
one. they make use of it in excel (where they enter the address).

we are trying to incorporate the same code here in our dotnet webpage
but with no success. the main issue is in finding out the 'ascii' value
of a japanese character. the vb program they supplied has this logic :

surname = StrConv(RomaN(jp_surname), vbNarrow)

and the RomaN function is like follows :

RE: Display iso-8859-1 characters using codepage 28591 tobi
9/19/2006 6:36:01 AM
Thank you for response, but the mentioned 'RomanN ' function is missing.
Could you post it?


[quoted text, click to view]
Re: Display iso-8859-1 characters using codepage 28591 Michael S. Kaplan [MSFT]
9/24/2006 9:11:12 AM
"tobi" <tobi@discussions.microsoft.com> wrote...

[quoted text, click to view]

This is not true. cp28591 does not map to cp1252; they are two separate
encodings.

[quoted text, click to view]

You bring data in from an encoding and convert it to Unicode; from ther you
can display it....

[quoted text, click to view]

Converting from full width to narrow assumes Unicode on both sides, and
further there are no such characters on either cp28591 *or* cp1252. What are
you trying to do, exactly?


--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap


This posting is provided "AS IS" with
no warranties, and confers no rights.

AddThis Social Bookmark Button