Hi

In my first message I forgot to mention that I also tested with the
following lines on my cfml file without no luck.

 <cfcontent type="text/html; charset=utf-8">
 <cfscript>
 SetEncoding("url", "utf-8");
 SetEncoding("form", "utf-8");
 </cfscript>

I always received the "ISO-8859-1" as a response from
  getPageContext().getResponse().getCharacterEncoding()

I did not test with the META tag, but i think that the answer should
be the same.

I really don't have an answer to you... :(

Perhaps you use some HTML entities translator, that converts "á" into
"&aacute;" :)

Dante

On 4 mayo, 21:36, "Nitai @ SixSigns" <[email protected]> wrote:
> Quick question on this matter again.
>
> Why did you have to change the server settings for this? We have all kinds
> of languages in our application and have a setting of UTF-8 for the pages
> like: <meta http-equiv="content-type" content="text/html;charset=utf-8" />
> and never had a problem with any chars.
>
> Kind Regards,
> Nitai
>
> On Tue, May 5, 2009 at 2:25 AM, Dante <[email protected]> wrote:
> > I have an Open Blue Dragon installed with Tomcat 6.0 on Ubuntu 8.04.
>
> > The problem was that I can't view the latin characters like  "á" or
> > "ñ"  on any .cfm page.
>
> > I changed the character encoding on the bluedragon.xml file to
> > ISO-8859-1 without success.
>
> > If I called getPageContext().getResponse().getCharacterEncoding() I
> > received "ISO-8859-1"
>
> --
> Razuna SaaS On-Demand - Hosted Digital Asset Management 
> Solutionhttp://www.razuna.com/
>
> Razuna - Open Source Digital Asset Managementhttp://www.razuna.org/
>
> SixSigns - Enrich people’s lives and web 
> experiencehttp://www.sixsigns.comhttp://blog.sixsigns.com
>
> Follow us on Twitterhttp://twitter.com/sixsigns

--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to