RE: internal support for windows-1251 codepage added to Xerces-C and Xalan-C

[Dean Roddey <dr...@portal.com>]

This is kind of a sticky situation. Everyone wants to have this or that
encoding be internalized so they don't need an external encoding.

What really should be done is that the simple API via which a new internal
encoding is added to the list of name to encoding mappings should be
exposed. This will allow any application to create its own internal
transcoder and just install it on the parser from the outside. This avoids
the need to turn Xerces into a transcoding system, but allows anyone to add
any special case encodings they need without having to modify the parser.

--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
droddey@portal.com



-----Original Message-----
From: David_N_Bertoni@lotus.com [mailto:David_N_Bertoni@lotus.com]
Sent: Monday, January 08, 2001 8:46 AM
To: xalan-dev@xml.apache.org; xerces-c-dev@xml.apache.org
Cc: xerces-dev@xml.apache.org
Subject: Re: internal support for windows-1251 codepage added to
Xerces-C and Xalan-C



On 01/07/01, Alexander Grimalovsky <fl...@concernchaos.com> wrote:

> Hi, xalan-dev!
>
> I tried to use Xerces-C and Xalan-C and found them most suitable to my
needs.
> I want to thank all of you for these cool programs!
> But one thing is still missed in Xerces: it doesn't has internal support
for
> any cyrillic codepage. The most widely used cyrillic codepage is
windows-1251
> and I add support for this code page to Xerces-C and Xalan-C and want to
submit
> my changes to you.
> Attached archive contain files, modified by me, changes are marked by:
>
> // Added by Flying