RE: Sudden difference in interpretation of #160 - update

2004-01-09 Thread H . vanderLinden
ne. :-( Thanks and bye, Helma > -Original Message- > From: J.Pietschmann [mailto:[EMAIL PROTECTED] > Sent: Thursday, 08 January 2004 21:07 > To: [EMAIL PROTECTED] > Subject: Re: Sudden difference in interpretation of #160 - update > > > [EMAIL PROTECTED] wrote

Re: Sudden difference in interpretation of #160 - update

2004-01-08 Thread J.Pietschmann
[EMAIL PROTECTED] wrote: Internet Explorer is on "encoding: auto-select" which defaults to ISO 8859-1 with or without in the page header. Same goes for Opera. There are multiple ways for a browser to get hints for the encoding: 1. The HTTP content-type header, which optionally specifies a characte

RE: Sudden difference in interpretation of #160 - update

2004-01-07 Thread Antonio Gallardo
[EMAIL PROTECTED] dijo: > Now all I have to figure out is how to tell Internet Explorer a UTF-8 page > is on the way, since most browser users will have the encoding set to > auto. A hard task. ;) We had the same problem with IE and your question clear my mind. An easy way to solve this is to let

RE: Sudden difference in interpretation of #160 - update

2004-01-07 Thread H . vanderLinden
AAGH > I thought you read Mike Browns article? Anyway, try this: > http://www.joelonsoftware.com/articles/Unicode.html I did, but it probably didn't sink in. I read this article as well and the lightbulb went off: Internet Explorer is on "encoding: auto-select" which defaults to ISO 8859-1

Re: Sudden difference in interpretation of #160 - update

2004-01-07 Thread J.Pietschmann
[EMAIL PROTECTED] wrote: I know, but I don't know how to verify what you mean by file encoding. I mainly use a programming editor (MultiEdit) or XMLSpy to edit my files. All of my files are plain XML (no special characters like  ). Only in the final XML2xHTML.xsl files I introduce some   characters

RE: Sudden difference in interpretation of #160 - update

2004-01-07 Thread H . vanderLinden
Hello, sorry for overlooking your post. > I use Tomcat 4.1.29 and I don't have this kind of problems. I > think the > problem is how the files are encodded. As I stated before it Ok. I did a quick test myself by running my webapp using the Cocoon jetty setup and the problem remained. > is not

RE: Sudden difference in interpretation of #160 - update

2004-01-06 Thread Antonio Gallardo
[EMAIL PROTECTED] dijo: > Guys, > > I read some of the posts in the mail-archives that the problem lies in > Tomcat 4.1.29 (which I use too). So I copied my project directory to the > cocoon-2.1.3/build/webapp dir and started Jetty from the Cocoon dir. It > states to use Xalan 2.5.2, but the proble

RE: Sudden difference in interpretation of #160 - update

2004-01-06 Thread H . vanderLinden
Guys, I read some of the posts in the mail-archives that the problem lies in Tomcat 4.1.29 (which I use too). So I copied my project directory to the cocoon-2.1.3/build/webapp dir and started Jetty from the Cocoon dir. It states to use Xalan 2.5.2, but the problem remains. Bye, Helma > -Orig

Re: Sudden difference in interpretation of #160 - update

2004-01-04 Thread Martijn Bouterse
[EMAIL PROTECTED] wrote: Hi, Good guess, but unfortunately both ideas don't work. In character entity references xhtml is similar to html 4, so both use the same code for nbsp (#160). As far as I can deduct from all the information, UTF-8 includes Latin-1, which includes the code for nbsp. So,

RE: Sudden difference in interpretation of #160 - update

2004-01-04 Thread H . vanderLinden
(ISO-8859-1 as well as UTF-8) the code for nbsp is 160. Any other ideas, guesses? Thanks. Bye, Helma > -Original Message- > From: Simon Hürlimann [mailto:[EMAIL PROTECTED] > Sent: Sunday, 04 January 2004 21:55 > To: [EMAIL PROTECTED] > Subject: RE: Sudden difference in in

RE: Sudden difference in interpretation of #160 - update

2004-01-04 Thread Simon Hürlimann
HiOn Sun, 2004-01-04 at 21:23, [EMAIL PROTECTED] wrote: > Hi, Helma > > > I use   as nbsp entity. This worked. I don't really know > > what happened, but now a capital A with a ^ (decimal code 194) > > is displayed instead of a space. > > I traced the problem back to serialize type="html" vs "

RE: Sudden difference in interpretation of #160 - update

2004-01-04 Thread H . vanderLinden
Hi, I traced the problem back to serialize type="html" vs "xhtml". The latter shows the A. Can anybody explain why and what to use for   in xhtml? Thanks. Bye, Helma > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Sunday, 04 January 2004 21:19 > To: