Hi there,
I just switched to Appfuse 2 and I am having issues with the encoding of
german umlaute.
I already changed every umlaut to the corresponding html-entity.
But in the CountryTag the following line returns values which are displayed
as some cryptical "?":
final String name = available[i]
I would suggest using something like Firebug to look at the response headers
and ensure everything's coming back as UTF-8. Also, are you able to
reproduce this problem on the demo site?
http://demo.appfuse.org
On Thu, Feb 4, 2010 at 7:41 AM, ess wrote:
>
> Hi there,
>
> I just switched to Appfu
Well, everything works just fine on thee demo-page.
The pages generated inmy project return:
in header, just as the dem does.
It seems to be not just a problem with the CountryTag:
After I changed my ApplicationResources to contain e.g. "ö" instead of
"ö", the webtest fail becaus they wont find
The CountryTag generates its list of countries using
Locale.getAvailableCountries().
http://source.appfuse.org/browse/appfuse/trunk/web/struts/src/main/java/org/appfuse/webapp/taglib/CountryTag.java?r=HEAD
Maybe the buildCountryList() method needs some enhancements?
On Thu, Feb 4, 2010 at 8:16 A
I already looked at that, but it used to work just fine before and when
debugging this thing everything is alright, too.
It really seems to be a general encoding problem!
--
View this message in context:
http://n4.nabble.com/Umlaute-in-CountryTag-tp1468889p1468963.html
Sent from the AppFuse - U
Are there any changes regarding encoding-setting made in Appfuse 2?
--
View this message in context:
http://n4.nabble.com/Umlaute-in-CountryTag-tp1468889p1469015.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---
I don't think so, but AppFuse 1.x was last released in 2006 and I've been
working on 2.x ever since. 4 years is a long time and it's certainly
possible things could've changed.
On Thu, Feb 4, 2010 at 9:07 AM, ess wrote:
>
> Are there any changes regarding encoding-setting made in Appfuse 2?
> --
