Re: Encoding of web.xml
on Tue, 19 Aug 2003 23:51:20 -0600 (CST) Antonio Gallardo [EMAIL PROTECTED] wrote: Hi: Why the web.xml of cocoon is still having: ?xml version=1.0 encoding=ISO-8859-1? I already changed it to ?xml version=1.0 encoding=UTF-8? and it works. Of course it works, UTF-8 is superset of ISO-8859-1. Regards, Rufio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Joerg Heinicke dijo: Is there any problem with ISO-8859-1 or do you think switching to UTF-8 would be good in general? I think switching all to UTF-8 would be good in general. It is a step ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a deprecated encoding. The IETF recommend UTF-8 instead of any other flavor of ISO-885x-x. Windows changed to UNICODE. Linux is already using UTF-8 as the default encoding. Well, we are moving there. AFAIK we (the world) are currently migrating all the computers and systems to the well know UNICODE. The idea is to allow all of us to mix on the same page code in German, Chinesse, English, etc. without have to worry of the encoding. The migration to UTF-8 is a important issue and since a date (sorry I dont remember the exactly date) any application cannot be considerated internet ready if it does not use UNICODE. Any application using ISO-8859 or similar will be cosiderated non-complaint. I learned about all this stuff (UNICODE, UTF-8, ISO-8859-1) when started in Cocoon I had the common problems generating the HTML pages. My target language (Spanish) needs ñ, Ñ, Á, á. etc. Of course other languages need other symbols that are not well rendered. XHTML 1.0 also has UTF-8 as the default encoding. Java has UTF-8 as the default encoding. Many other applications are migrating or are already migrated. Please read more about unicode at: http://www.unicode.org/standard/WhatIsUnicode.html By the way If we can change to UTF-8 I think many other problems will go away. On the other hand some old applications and browser will not be able to display UTF-8 correctly. I mean maybe IE 3.0 or below. It is part of all this thing. And the is the main reason why we are having problems seeing the copyright symbol on the Cocoon main page of the distribution. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
rufio dijo: Of course it works, UTF-8 is superset of ISO-8859-1. Yep. But the correct would be have all in UTF-8 and not using the deprecated ISO-8859-1 Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Wow, what a /hymn/ on UTF-8 :-) I know the advantages of UTF-8 and even if there is currently no need for switching I did it. The conversion was done hopefully correctly by jEdit. Joerg Antonio Gallardo wrote: Joerg Heinicke dijo: Is there any problem with ISO-8859-1 or do you think switching to UTF-8 would be good in general? I think switching all to UTF-8 would be good in general. It is a step ahead. UTF-8 is the default standard of every XML doc. The ISO-8859-1 is a deprecated encoding. The IETF recommend UTF-8 instead of any other flavor of ISO-885x-x. Windows changed to UNICODE. Linux is already using UTF-8 as the default encoding. Well, we are moving there. AFAIK we (the world) are currently migrating all the computers and systems to the well know UNICODE. The idea is to allow all of us to mix on the same page code in German, Chinesse, English, etc. without have to worry of the encoding. The migration to UTF-8 is a important issue and since a date (sorry I dont remember the exactly date) any application cannot be considerated internet ready if it does not use UNICODE. Any application using ISO-8859 or similar will be cosiderated non-complaint. I learned about all this stuff (UNICODE, UTF-8, ISO-8859-1) when started in Cocoon I had the common problems generating the HTML pages. My target language (Spanish) needs ñ, Ñ, Á, á. etc. Of course other languages need other symbols that are not well rendered. XHTML 1.0 also has UTF-8 as the default encoding. Java has UTF-8 as the default encoding. Many other applications are migrating or are already migrated. Please read more about unicode at: http://www.unicode.org/standard/WhatIsUnicode.html By the way If we can change to UTF-8 I think many other problems will go away. On the other hand some old applications and browser will not be able to display UTF-8 correctly. I mean maybe IE 3.0 or below. It is part of all this thing. And the is the main reason why we are having problems seeing the copyright symbol on the Cocoon main page of the distribution. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Encoding of web.xml
Joerg Heinicke dijo: Wow, what a /hymn/ on UTF-8 :-) I know the advantages of UTF-8 and even if there is currently no need for switching I did it. The conversion was done hopefully correctly by jEdit. Thanks, I know this is a little change (and maybe meaningless), but I hope it would help us in the standarization. :) Best Regards, Antonio Gallardo. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Encoding of web.xml
Hi: Why the web.xml of cocoon is still having: ?xml version=1.0 encoding=ISO-8859-1? I already changed it to ?xml version=1.0 encoding=UTF-8? and it works. Best Regards, Antonio Gallardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
