Community
Participate
Working Groups
This is an improvement suggestion for IDE editor used for *.properties files. Create a "Hello, World" project with NLV string to be printed (the characters must be different from Latin-1 codeset, let's say Russian). Select Source > Externalize strings, confirm creation of Message.properties and click Finish. Message.properties file is shown using \u Unicode representation: hello_world.0=\u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439, \u041D\u043E\u0432\u044B\u0439 \u0413\u043E\u0434\! This makes *property files "thing-in-itself" - one can not read it, can not edit it, can not search through it - only use it for output. This severely restricts usability of the IDE and makes NLS Message.properties files hardly usable for any language with non Latin-1 characters. The suggestion is to add a support of this Unicode representation to the text editor used for *properties files. The files should still be stored in \u representation, but they should be searched, viewed and edited as regular national text to make reading and modification possible.
Added TVT3.1 #46 to title for our tracking purposes.
> The files should still be stored in \u representation, but they should be > searched, viewed and edited as regular national text to make reading and > modification possible. Viewing and editing will become easier with bug 65571. Keeping this bug open for the searching part.
(In reply to comment #2) > > The files should still be stored in \u representation, but they should be > > searched, viewed and edited as regular national text to make reading and > > modification possible. > Viewing and editing will become easier with bug 65571. Keeping this bug open > for the searching part. Filed bug 328019 for that.