Re: Change encoding to ISO-8859-1

2004-03-05 Thread Lionel Crine
This error means that the document is written in ASCII mode with some 
characters which are not contain in the ASCII table of UTF-8.

Which means :
if you write  in a new document with ultraedit and you save it as is.
Cocoon will load the document and serialize it with this error.
BUT :
Before saving the document, you convert the document from ASCII to UTF-8 
using File - Conversions - ASCII to UTF-8
In java for example,you can do the similar thing like that :  new 
String(str.getBytes(ISO-8859-1), UTF-8);

And now it's working.
So no need to change the encoding of the serializer.
Lionel



At 20:34 23/02/2004 +, you wrote:
Hi!!!
I know this is a issue largely discussed here, but for me the tips that I 
read didn't work.
I already try to set the current encoding in the sitemap, like you can see 
here:
   map:serializer logger=sitemap.serializer.html name=html 
mime-type=text/html
   pool-grow=4 pool-max=32 pool-min=4
   src=org.apache.cocoon.serialization.HTMLSerializer
encodingISO-8859-1/encoding
omit-xml-declarationtrue/omit-xml-declaration
   /map:serializer

   map:serializer logger=sitemap.serializer.xml name=xml
   src=org.apache.cocoon.serialization.XMLSerializer
   mime-type=text/xml pool-max=32 pool-min=16 pool-grow=4
encodingISO-8859-1/encoding
   /map:serializer
After that I keep getting the same error:
org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 
of 3-byte UTF-8 sequence

Thanks in advance,
Carlos Dias
Lionel CRINE
Ingénieur Systèmes documentaires
Société : 4DConcept
22 rue Etienne de Jouy 78353 JOUY EN JOSAS
Tel : 01.34.58.70.70 Fax : 01.39.58.70.70
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Change encoding to ISO-8859-1

2004-02-23 Thread Carlos Dias



Hi!!!
I know this is a issue largely discussed here, but 
for me the tips that I read didn't work.
I already try to set the current encoding in the 
sitemap, like you can see here:
map:serializer 
logger="sitemap.serializer.html" name="html" 
mime-type="text/html"pool-grow="4" 
pool-max="32" pool-min="4" 
src=""encodingISO-8859-1/encodingomit-xml-declarationtrue/omit-xml-declaration/map:serializermap:serializer 
logger="sitemap.serializer.xml" name="xml" 
src=""mime-type="text/xml" 
pool-max="32" pool-min="16" 
pool-grow="4"encodingISO-8859-1/encoding/map:serializer

After that I keep getting the same 
error:
"org.apache.cocoon.ProcessingException: Failed to 
execute pipeline.: org.xml.sax.SAXException: Original Exception IOException : 
Invalid byte 2 of 3-byte UTF-8 sequence"

Thanks in advance,
Carlos Dias



Re: Change encoding to ISO-8859-1

2004-02-23 Thread Joerg Heinicke
On 23.02.2004 21:34, Carlos Dias wrote:

Hi!!!
I know this is a issue largely discussed here, but for me the tips that I read didn't work.
I already try to set the current encoding in the sitemap, like you can see here:
   map:serializer logger=sitemap.serializer.html name=html mime-type=text/html
   pool-grow=4 pool-max=32 pool-min=4 
   src=org.apache.cocoon.serialization.HTMLSerializer
encodingISO-8859-1/encoding
omit-xml-declarationtrue/omit-xml-declaration
   /map:serializer
   
   map:serializer logger=sitemap.serializer.xml name=xml 
   src=org.apache.cocoon.serialization.XMLSerializer
   mime-type=text/xml pool-max=32 pool-min=16 pool-grow=4
encodingISO-8859-1/encoding
   /map:serializer

After that I keep getting the same error:
org.apache.cocoon.ProcessingException: Failed to execute pipeline.: 
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of 3-byte UTF-8 
sequence
I think the problem is not the encoding setting of Cocoon, but in the 
file you are accessing in this pipeline. The encoding *specified* in 
this file (or default UTF-8) does not seem to match the encoding *of* 
the file.

Joerg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Change encoding to ISO-8859-1

2004-02-23 Thread Bert Van Kets
I use JEdit to change file encodings. It allows you to read a file in a
certain encoding, change the buffer to a different encodig, make corrections
where necessary and write out in the new encodig.

I thought I'd mention for those not knowing JEdit.

Bert


- Original Message - 
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 23, 2004 9:39 PM
Subject: Re: Change encoding to ISO-8859-1


 On 23.02.2004 21:34, Carlos Dias wrote:

  Hi!!!
  I know this is a issue largely discussed here, but for me the tips that
I read didn't work.
  I already try to set the current encoding in the sitemap, like you can
see here:
 map:serializer logger=sitemap.serializer.html name=html
mime-type=text/html
 pool-grow=4 pool-max=32 pool-min=4
 src=org.apache.cocoon.serialization.HTMLSerializer
  encodingISO-8859-1/encoding
  omit-xml-declarationtrue/omit-xml-declaration
 /map:serializer
 
 map:serializer logger=sitemap.serializer.xml name=xml
 src=org.apache.cocoon.serialization.XMLSerializer
 mime-type=text/xml pool-max=32 pool-min=16 pool-grow=4
  encodingISO-8859-1/encoding
 /map:serializer
 
  After that I keep getting the same error:
  org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence

 I think the problem is not the encoding setting of Cocoon, but in the
 file you are accessing in this pipeline. The encoding *specified* in
 this file (or default UTF-8) does not seem to match the encoding *of*
 the file.

 Joerg

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Change encoding to ISO-8859-1

2004-02-23 Thread Carlos Dias
Let me see if I understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a different
encoding, right?!

CD
- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 23, 2004 8:39 PM
Subject: Re: Change encoding to ISO-8859-1


 On 23.02.2004 21:34, Carlos Dias wrote:

  Hi!!!
  I know this is a issue largely discussed here, but for me the tips that
I read didn't work.
  I already try to set the current encoding in the sitemap, like you can
see here:
 map:serializer logger=sitemap.serializer.html name=html
mime-type=text/html
 pool-grow=4 pool-max=32 pool-min=4
 src=org.apache.cocoon.serialization.HTMLSerializer
  encodingISO-8859-1/encoding
  omit-xml-declarationtrue/omit-xml-declaration
 /map:serializer
 
 map:serializer logger=sitemap.serializer.xml name=xml
 src=org.apache.cocoon.serialization.XMLSerializer
 mime-type=text/xml pool-max=32 pool-min=16 pool-grow=4
  encodingISO-8859-1/encoding
 /map:serializer
 
  After that I keep getting the same error:
  org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence

 I think the problem is not the encoding setting of Cocoon, but in the
 file you are accessing in this pipeline. The encoding *specified* in
 this file (or default UTF-8) does not seem to match the encoding *of*
 the file.

 Joerg

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Change encoding to ISO-8859-1

2004-02-23 Thread Joerg Heinicke
On 23.02.2004 21:53, Carlos Dias wrote:
Let me see if I understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a different
encoding, right?!
Yes. This happens if you use an encoding-unaware editor or the editor 
can not handle the specific encoding. jEdit is a good suggestion by 
Bert, btw. You can get it at jedit.org.

Joerg

- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
org.xml.sax.SAXException: Original Exception IOException : Invalid byte 2 of
3-byte UTF-8 sequence
I think the problem is not the encoding setting of Cocoon, but in the
file you are accessing in this pipeline. The encoding *specified* in
this file (or default UTF-8) does not seem to match the encoding *of*
the file.
Joerg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Change encoding to ISO-8859-1

2004-02-23 Thread Joerg Heinicke
Another good hint might be to use a browser like IE or Mozilla to view 
the XML file because they tell you if something is wrong with the file 
and no editor/application/cocoon is involved.

Joerg

On 23.02.2004 21:50, Joerg Heinicke wrote:

On 23.02.2004 21:53, Carlos Dias wrote:

Let me see if I understand your answer... you are saying that the file is
defined with a specific encoding, but has characters that are in a 
different
encoding, right?!


Yes. This happens if you use an encoding-unaware editor or the editor 
can not handle the specific encoding. jEdit is a good suggestion by 
Bert, btw. You can get it at jedit.org.

Joerg

- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
org.xml.sax.SAXException: Original Exception IOException : Invalid 
byte 2 of
3-byte UTF-8 sequence

I think the problem is not the encoding setting of Cocoon, but in the
file you are accessing in this pipeline. The encoding *specified* in
this file (or default UTF-8) does not seem to match the encoding *of*
the file.
Joerg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Change encoding to ISO-8859-1

2004-02-23 Thread Carlos Dias
The XML file is generated by a process that create a file with UTF encoding.
So I have to change the encoding from the base file, or use the UTF. But I
think doesn't work for the character set of my country (Portugal)?!

Thanks for the support,
CDias
- Original Message -
From: Joerg Heinicke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 23, 2004 8:51 PM
Subject: Re: Change encoding to ISO-8859-1


 Another good hint might be to use a browser like IE or Mozilla to view
 the XML file because they tell you if something is wrong with the file
 and no editor/application/cocoon is involved.

 Joerg

 On 23.02.2004 21:50, Joerg Heinicke wrote:

  On 23.02.2004 21:53, Carlos Dias wrote:
 
  Let me see if I understand your answer... you are saying that the file
is
  defined with a specific encoding, but has characters that are in a
  different
  encoding, right?!
 
 
  Yes. This happens if you use an encoding-unaware editor or the editor
  can not handle the specific encoding. jEdit is a good suggestion by
  Bert, btw. You can get it at jedit.org.
 
  Joerg
 
  - Original Message -
  From: Joerg Heinicke [EMAIL PROTECTED]
 
  org.xml.sax.SAXException: Original Exception IOException : Invalid
  byte 2 of
  3-byte UTF-8 sequence
 
  I think the problem is not the encoding setting of Cocoon, but in the
  file you are accessing in this pipeline. The encoding *specified* in
  this file (or default UTF-8) does not seem to match the encoding *of*
  the file.
 
  Joerg

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]