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):
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 la
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
in the Application.cfm
Now, in order the application is completely CF 5 and CFMX compatible, I use
>>change the defaultCharset value in cf_root/lib/neo-runtime.xml file:
UTF-8
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
>>a better long term solution is to con
Claude Schneegans wrote:
> Do I also have to put 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 file:
UTF-8
from UTF-8 to iso-8859-1. then sto
When on see pages like this:
http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=209&threadid=814963
I can really see I'm not the only one having problems with French characters
under CFMX ;-)
--
___
REUSE CODE! Use custom tags;
See http://w
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 U
>>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 addres
>>This tells the browser what format to expect the content it receives in:
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 be working fine with only http://www.conten
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
http://
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:
> 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
> Why do I need BOTH ?
This tells the browser what format to expect the content it receives in:
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):
Tim.
--
--
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 s
>>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:
>
> 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 chara
>>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
>>
>>
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?
When I'll make a new site in chinese, may be I'll select UTF-8, but for the
time bein
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
http://store.newmed
TECTED]>
To: "CF-Talk"
Sent: Thursday, January 20, 2005 3:31 PM
Subject: Re: CFMX + UTF8 vs Javascript
> 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 a
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:
http://diplomes.med.umontreal.ca/te
21 matches
Mail list logo