[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-9357) Using JBoss Tools Properties Editor, some (but not all) non-ASCII characters are changed to their equivalent \u escaped version

[Matthew Farwell (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Farwell updated JBIDE-9357:
-----------------------------------

    Attachment: foo.properties


Correctly encoded file

> Using JBoss Tools Properties Editor, some (but not all) non-ASCII characters are changed to their equivalent \u escaped version
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-9357
>                 URL: https://issues.jboss.org/browse/JBIDE-9357
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: integration
>    Affects Versions: 3.1.0.GA
>         Environment: Windows 7, Eclipse Galileo, JBoss Properties 
>            Reporter: Matthew Farwell
>            Assignee: Alexey Kazakov
>              Labels: eclipse, properties
>             Fix For: 3.3.0.M3, 3.3.0.Beta1
>
>         Attachments: foo.properties, jboss-foo.properties-properties.png, jboss-plugins.png
>
>
> In Eclipse Galileo
> 1) Create a file foo.properties
> 2) Change the project & file properties to be UTF-8 (See jboss-foo.properties-properties.png)
> 2) Enter the following lines into foo.properties
> barbar=fédéral
> foobar=Numéro 
> 3) Close the foo.properties
> 4) Reopen foo.properties, the file now looks like:
> barbar=fédéral
> foobar=Num\u00E9ro
> If I save this file, the file gets saved in this form. This screws up the way that these strings are displayed on the site. Note that only the Numéro is transformed.
> Additional info:
> The files are read using org.springframework.context.support.ReloadableResourceBundleMessageSource, so the \u00E9 isn't interpreted correctly.
> For exact version number (3.1.0.v200910281724M-H247-M4), see jboss-plugins.png. (
> The workaround for this problem is 1) To have a unit test to find strings which have been badly transformed. 2) Don't use JBoss Tools Properties Editor :-)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira