http://livedocs.macromedia.com/coldfusion/6/Developing_ColdFusion_MX_Applications_with_CFML/indexSearch2.htm
Don't know if that helps or not, but perhaps it will guide you in the right direction?
HTH
-Ryan
-----Original Message-----
From: Stavros Tekes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 14, 2003 2:34 AM
To: CF-Talk
Subject: CF Problem with Langauges (??)
Hi all!
Lately I have changed my Cold Fusion host to one abroad (outside
Greece). Eversince I am trying to make Greek appear propertly on my pages.
Although I have managed to make most pages appear ok in Greek, I still
haven't managed to do the same with pages that use the CFSearch tag.
Although my host has installed the European/Asian Language Pack, replaced
their cfxneo.dll (under c:\cfusionMX\lib\) with the double byted cfxneo from
the MM website and restarted all their Cold Fusion services, I still can't
retrieve search results in Greek properly.
I hardcoded the search term (which is in Greek) on cfsearch tag in order
to be sure that the encoding does not get lost after the FORM posting takes
place but still nothing was retrieved. The same web page on my server here,
runs great (I used the same verity collection, by replacing the files that
verity created for my collection on the host computer with the ones it
created on my server, just to be sure that it is not a cfindex fault).
The cfm page that uses CFSEARCH also uses these encoding lines at its
top
<cfprocessingdirective pageencoding="iso-8859-7">
<cfcontent type="text/html; charset=iso-8859-7">
(iso-8859-7 is for Greek encoding)
The Greek characters are all represented by question marks (??
?????????? ??? ???? ... etc) which I believe means that character
information has been lost. I also noticed that when I changed cfcontent to
<cfcontent type="text/html; charset=utf-8"> Greek again didn't come out
right, but instead of question marks, different characters were returned (Ie
?aneanaoYo oui ni?i ... etc). That seemed more promising.
I realise that both cftags should be pointing at the same encoding
values, cause one determines the output encoding while the other sets the
encoding of the data which forms the page content. Furthermore we changed
their default Java Encoding to Greek as well, but that still didn;t do any
good. (all of the above were tested by using null as a search string since
Greek words returned no results on my host)
After everything I have tried I can't come to the conclusion whether it
is a verity problem or not. The only problems I get are on the pages that
use the Cfsearch tag and only on my host. Everything works great on my
computer.
I run out of ideas! Don;t know what to try next, so if anyone can help,
will be a life saviour to me!
Thanks in advance,
Stavros
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
