Re: [WebDNA] encoding with webdna/JS, in context of various file encodings/charsets
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105780
interpreted = N
texte = --Apple-Mail-7-822499713Content-Type: text/plain;charset=US-ASCII;format=flowed;delsp=yesContent-Transfer-Encoding: 7bitHi TomThanks for looking. I really want to nail this. How are you seeing in firebug what encoding the page is? Please tell me where to find that. (I didn't see it.)When i go here:FF > View > Character Encodingthen yes, it seems to say this page:http://www.sleeperhouse.com/admin/govTestDump/webdnaJStest_utf8.htmlis being served as ISOBut/and if I use that same menu command to set the page to UTF.. then I STILL get the behavior mentioned.Anyway, trying what you suggest,I put this in the page:[SETMIMEHEADER name=Content-Type&value=text/html; charset=utf-8]..and the page still serves up ISO. Did I use the correct syntax/ value(s) for that [SETMIMEHEADER]? (I never used that before, for setting any of the header data.) Or could you provide an example?thanks!-GOn Sep 9, 2010, at 6:09 PM, Tom Duke wrote:> Govinda,>> Hi - first and biggest problem is that the page is not being served > as UTF-8 - it is being served as ISO-8859-1. You can use Firebug > in Firefox to see this.>> You should check if you are using [setmimeheader] to define the > charset as UTF-8, if you are and that is not working then Apache may > be serving it out using a default setting. In this case you could > try using a .htaccess file with the following line:>> AddCharset UTF-8 .html>> - Tom>>>>------------Govindagovinda.webdnatalk@gmail.com--Apple-Mail-7-822499713Content-Type: text/html;charset=US-ASCIIContent-Transfer-Encoding: quoted-printableHi =Tom
Thanks for looking. I really want to nail =this. How are you seeing in firebug what encoding the page is? = Please tell me where to find that. (I didn't see =it.)
When i go here:
FF > View => Character Encoding
then yes, it seems to say this =page:
is being served as ISO
But/and if I use that same =menu command to set the page to UTF.. then I STILL get the =behavior mentioned.
Anyway, trying what you =suggest,
I put this in the =page:
[SETMIMEHEADER =name=3DContent-Type&value=3Dtext/html; =charset=3Dutf-8]
..and the page still serves up ISO. = Did I use the correct syntax/value(s) for that [SETMIMEHEADER]? = (I never used that before, for setting any of the header data.) = Or could you provide an =example?
thanks!
-G
On Sep 9, 2010, at 6:09 PM, Tom Duke wrote:
Govinda,
Hi - first and biggest problem =is that the page is not being served as UTF-8 - it is being served =as ISO-8859-1. You can use Firebug in Firefox to see =this.
You should check if you are using =[setmimeheader] to define the charset as UTF-8, if you are and that is =not working then Apache may be serving it out using a default setting. = In this case you could try using a .htaccess file with the =following line:
AddCharset =UTF-8 .html
- =Tom
=--Apple-Mail-7-822499713--
Associated Messages, from the most recent to the oldest:Thanks for looking. I really want to nail =this. How are you seeing in firebug what encoding the page is? = Please tell me where to find that. (I didn't see =it.)
But/and if I use that same =menu command to set the page to UTF.. then I STILL get the =behavior mentioned.
..and the page still serves up ISO. = Did I use the correct syntax/value(s) for that
[setmimeheader]? = (I never used that before, for setting any of the header data.) = Or could you provide an =example?