character encoding problem with message.properties in plugins

Workaround:
If the german message_de.properties file is ISO-8859-1 encoded in the in-place-plugin the special chars are shown correctly.

nevertheless a consistent behavior and file encoding is needed.

I just experienced that the behavior seems to be different between 'grails run-app' AND 'grails-run-war'

while 'grails run-app' expects the message.properties - file in the main projekt as utf-8, it expects it in in-place-plugins SO-8859-1 encoded

grails run-war shows a different behavior: It needs all the message.properties to be utf-8 encoded, to be able to display special characters correctly in the pages.

native2ascii gets called for i18n properties files when the war file is built.
I think we might have to set defaultEncoding somewhere here

Hi guys,

Just to tell this is happening in PT_BR lang too.
When the messages_pt_BR.properties is inside the applications, messages with accented chars (á,é,í,ó,ú) shows fine, but, after moving the properties files to one plugin, the accented chars shows as strange chars.

Thanks,

Can someone attach an example with steps to reproduce?

Hi,

I've attached one zip with two folders. One 'app' folder and one 'msgs' folder.
The 'msgs' is a plugin added in the 'app' application as an in-place plugin:

grails.plugin.location.msgs = "../msgs"

The application message.properties file has one line as this:

sample.message.inside.application = há hé ça ço

And the plugin, a equals line, but just with another key:

sample.message.inside.plugin = há hé ça ço

The app index.gsp (http://localhost:8080/app) is reading both propeties:

<p>App message: <g:message code="sample.message.inside.application" /></p> 
<p>Plugin message: <g:message code="sample.message.inside.plugin" /></p> 

And the output is being different for both:

App message: há hé ça ço
Plugin message: há hé ça ço

There is an screenshot of this output attached.

Thanks,

Our application don't use in-place plugins, but builded and packaged ones, happens the same way.
If you need some example of the same behaviour using a packaged plugin, just tell me and i'll attach.

Thanks,

Hi,

Is there another workaround? Other than changing the encoding of the message.properties in the plugin?

Thanks

This has also happened to me with properties defined for Spanish, such as á,é,í,ó,ú or ñ, which are rendered as �.

I have these properties defined in an external plugin, but it also happens when I have Spanish properties defined in the default messages.properties in my Grails application.

So sad. Being pushed ahead since Grails 1.3.6. More than 2 years...
Workaround: copying files from plugins to apps each build.

Pushed ahead? it has been brought forward, it was scheduled for 2.3 and I changed it to be scheduled for 2.1.5 and 2.2.1

Sry about that Graeme, just used to follow this issue being pushed.
Great to hear this. Thank you!

Lucas