Community
Participate
Working Groups
when editing the following example in a property file, the two '\t's in following example will be interpreted as "tabs". It would be very helpfull if properties file editor recognized these special characters, highlighted them differently as \t and then also highlight them as "normal" when escaped, as in \\t (maybe then the single escape character getting some special highlight). This would help avoid "silly" errors. (as tab is not intended in following example ... it just happens to be a directory name in windows. osgi.syspath=D:\tests\testarea\plugins
good idea.
This won't make it into 3.2
*** Bug 328017 has been marked as a duplicate of this bug. ***
With bug 65571 there is a hover in the editor which shows the real string. This hover can also be used to verify the typed property value.
The editor could also show - an error marker if the there is a malformed \uxxxx sequence. Currently this just fails at runtime. - a warning is there is an unnecessary \. Currently this is just silently ignored. Or instead of showing markers, these incorrect characters could be colored differently to indicate a problem.
(In reply to comment #5) > The editor could also show > - an error marker if the there is a malformed \uxxxx sequence. Currently this > just fails at runtime. > - a warning is there is an unnecessary \. Currently this is just silently > ignored. > > Or instead of showing markers, these incorrect characters could be colored > differently to indicate a problem. Please don't load your thoughts into an unrelated bugs.
>Please don't load your thoughts into an unrelated bugs. Unrelated because we never use coloring to report problems: we always use markers and/or annotations. Please file a new bug where we can discuss how to report incorrect characters.
(In reply to comment #7) > Unrelated because we never use coloring to report problems: we always use > markers and/or annotations. Please file a new bug where we can discuss how to > report incorrect characters. I know the error reporting part is unrelated, but the identification of special/incorrect characters would be common code... Anyway filed Bug 328374.
