Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329130 - [nls tooling] Properties file editor should not translate non-ISO-8859-1 characters if properties file has UTF-8 encoding
Summary: [nls tooling] Properties file editor should not translate non-ISO-8859-1 char...
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.7 M4   Edit
Assignee: Deepak Azad CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-30 04:21 EDT by Peter Stibrany CLA
Modified: 2010-12-07 07:10 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Stibrany CLA 2010-10-30 04:21:01 EDT 
Build Identifier: Version: 3.7.0 Build id: I20101028-1441

Eclipse 3.7M3 introduced auto-escaping of typed and pasted non-ISO-8859-1 characters in properties file editor. This is nice, but Java 1.6 supports loading properties file with different encodings than iso-8859-1 and therefore this escaping is no longer absolutely necessary.

In our project we keep properties files in UTF-8 and load them as such. Please make it possible to disable this auto-escaping feature, either by some configuration option, or better yet, by recognizing that properties file encoding is set to UTF-8 (or simply different than ISO-8859-1).


Reproducible: Always
Comment 1 Deepak Azad CLA 2010-11-03 13:23:25 EDT 
Fixed in HEAD in 
PropertiesFileAutoEditStrategy.java
PropertiesFileSourceViewerConfiguration.java
PropertiesFileAutoEditStrategyTest.java

The auto-escape feature now acts according to the properties file encoding.
Comment 2 Raksha Vasisht CLA 2010-12-07 07:10:43 EST 
Verified for 3.7 M4 with  I20101206-1800.