Credit goes back to Jochem. He's the one that helped me figure it out.
- Original Message -
From: Claude Schneegans [EMAIL PROTECTED]
Thanks all for your help, especially Deanna.
~|
Logware (www.logware.us): a new
Hi,
I finally figured out that the iso-8859-1 characters where replaced by y not in
the database, but during the post through the form.
As Deanna Schneider pointed out, I needed to add both lines
cfset setEncoding(url,ISO-8859-1)
cfset setEncoding(form,ISO-8859-1)
in the Application.cfm
Now, in
Claude Schneegans wrote:
Including the Javascrip files, but how do I edit them?
notepad, cfstudio (just leave the BOM alone), cfeclipse, etc.
What do you mean ghost echo, I'm still having a ?%$/ problem, and it is
not a ghost problem ;-)
an email that got somehow recycled shows up later on
Hi,
I'm still having a big problem with this application in French, moving from CF
5.0 to CFMX.
The problem is that all pages and data in the Access database are not in
Unicode, but in
plain good old iso-8859-1.
CFMX by default is converting every thing in UTF-8.
Explorer understand that it is
When on see pages like this:
http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=209threadid=814963
I can really see I'm not the only one having problems with French characters
under CFMX ;-)
--
___
REUSE CODE! Use custom tags;
See
Claude Schneegans wrote:
Do I also have to put cfprocessingdirective pageEncoding=ISO-8859-1 in
EVERY page?
not a bad idea actually (never be shy about encoding hints) but if you
want this server to ONLY handle latin-1 then:
change the defaultCharset value in cf_root/lib/neo-runtime.xml
change the defaultCharset value in cf_root/lib/neo-runtime.xml file:
var name='defaultCharset'stringUTF-8/string/var
from UTF-8 to iso-8859-1. then stop/restart the cfserver service.
Thanks for the trick. Since the server handles only English and French site, I
don't think it should be a problem
Why do I need BOTH ?
This tells the browser what format to expect the content it receives in:
cfcontent type=text/html; charset=ISO-8859-1
And this tells CF how to process the current file (and hence is required
in *every file* where you need to specifiy a page encoding):
cfprocessingdirective
Claude Schneegans wrote:
I know that you are a fervent suporter of Unicode, and I'm also, but only
where I need it,
except that we think it's always needed. retrofitting is a bore.
For some pages in some sites in some languages, YES, but for most european
languages,
iso-8859-1 is the
Jochem van Dieten wrote:
not a default standard. If only for the existence of Win1252,
which is the subtly different Windows default.
yeah it is a subtle difference, i've seen it burn quite a few pages. i'd
call that windows codepage a superset of iso-8859-1.
Claude Schneegans wrote:
http://diplomes.med.umontreal.ca/testcfm.cfm
btw that seem to work for me in ie 6.0.2800 in firefox 1.
~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble
Ticket application
This tells the browser what format to expect the content it receives in:
cfcontent type=text/html; charset=ISO-8859-1
More precisely: it tells CF to tell the browser what format to expect from what
it will recive from CF.
Then if CF knows the format, why should I tell it twice?
BTW it seems to
btw that seem to work for me in ie 6.0.2800 in firefox 1.
I used the same file to test the suggested cure, so now it works.
--
___
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address:
Hi,
The host I have some of my sites recently moved to CFMX.
As a result, all the text is converted to UTF-8.
First I find this a bit abusive since I only need latin-1, but anyway...
The trouble is that my Javascript files are still in Latin-1, but Explorer is
so minded it receives everything
One can see an example here:
http://diplomes.med.umontreal.ca/testhtm.htm
The page just contains the string é É and call a javascript file which makes
an alert with the same string
With this plain HTML file, it works ok.
Now with the exact same content in CF:
:
enctype=multipart/form-data: charset=ISO-8859-1
- Original Message -
From: Claude Schneegans [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Thursday, January 20, 2005 3:31 PM
Subject: Re: CFMX + UTF8 vs Javascript
One can see an example here:
http
If you have Homesite+ or other capable text editor (Notepad), you could
re-save your js file in the utf-8 encoding and re-upload it...
If you have LOTS of files you need to convert, I wrote a conversion tool
that lets you convert from ansi to utf-8 en-mass that you can get from
cfcontent type=text/html; charset=ISO-8859-1
cfprocessingdirective pageEncoding=ISO-8859-1
Ah ah, with both of thrm it seems to work.
Why do I need BOTH ?
in form:
You mean in EVERY forms?
Gee isn't there any setting in CFMX server to specify I don't need this UTF-8
stuff in all my sites?
If you have LOTS of files you need to convert, I wrote a conversion tool
that lets you convert from ansi to utf-8 en-mass
Well, this is fine, but I don't want to convert...
Why should I convert to UTF-8 which takes 3 or 4 characters for any accented
letter when I have been using for more that a
Claude Schneegans wrote:
Well, this is fine, but I don't want to convert...
Why should I convert to UTF-8 which takes 3 or 4 characters for any accented
letter when I have been using for more that a decade is0-8859-1 which takes
only one character?
Because not all commonly used
Because not all commonly used characters are in ISO-8859-1.
I know that you are a fervent suporter of Unicode, and I'm also, but only where
I need it,
For some pages in some sites in some languages, YES, but for most european
languages,
iso-8859-1 is the standard.
Of course, one can always use
Claude Schneegans wrote:
Because not all commonly used characters are in ISO-8859-1.
I know that you are a fervent suporter of Unicode, and I'm also, but only
where I need it,
For some pages in some sites in some languages, YES, but for most european
languages,
iso-8859-1 is the
22 matches
Mail list logo
