This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: AW: Problem parsing cp1252 with msxsl > UTF-8 ?
- From: "Agnes Kielen" <a dot kielen at home dot nl>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 14 Jun 2002 13:08:56 +0200
- Subject: Re: AW: [xsl] Problem parsing cp1252 with msxsl > UTF-8 ?
- References: <41937298F962D411A87F004033E227AA2DA7A4@nt06.hamburg.hanseorga.de>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hi,
AceHTML has among other encodings also UTF-8. At least the commercial one
version 5. Version 4 is for free. You can try that.
Cheers,
Agnes
----- Original Message -----
From: "Braumüller, Hans" <h.braumueller@hanseorga.de>
To: <xsl-list@lists.mulberrytech.com>
Sent: Friday, June 14, 2002 11:11 AM
Subject: AW: AW: [xsl] Problem parsing cp1252 with msxsl > UTF-8 ?
> Hi,
>
> great, now i understand. So i must get an enabled UTF-8 text-editor, i am
> using homesite and sometimes ultraedit. It seems that they have no UTF-8
> support.
>
> Do you know one?
>
> Thanks,
>
> Hans Braumüller
>
>
> > Any time you save a text file or transmit it over a network,
> > you have a series
> > of bytes representing the characters in the document. The
> > encoding is how
> > those bytes map to characters.
> >
> > UTF-8 maps all 1.1 million Unicode characters to a series of
> > 1 to 4 bytes per
> > character. You certainly do have those German characters
> > available in utf-8,
> > but instead of being mapped to 1 byte each, as they would be
> > in iso-8859-1,
> > they are mapped to 2 bytes each.
> >
> > A text editor that doesn't tell you what encoding it is using
> > when you save
> > the document is probably relying on the underlying OS to make
> > encoding/decoding decisions, and it probably isn't using
> > Unicode internally at
> > all; rather it just manages buffers of bytes fed to it by the
> > OS. Solution:
> > get a smarter text editor that lets you choose the encoding
> > to save files
> > with.
> >
> > The encoding declaration in an XML document is a reflection
> > of the actual
> > encoding used *throughout* file. You must not save a file with all the
> > characters encoded as iso-8859-1 bytes, while having
> > encoding="utf-8" in the
> > file, for example. You must also avoid mixing encodings in
> > the same file (some
> > characters using one encoding, some using another).
> >
> > - Mike
> > ______________________________________________________________
> > ______________
> > mike j. brown | xml/xslt: http://skew.org/xml/
> > denver/boulder, colorado, usa | resume:
> > http://skew.org/~mike/resume/
> >
> > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> >
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list