Bug 328374

Summary:	[nls tooling] Properties file editor should report errors for incorrect characters
Product:	[Eclipse Project] JDT	Reporter:	Deepak Azad <deepakazad>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	daniel_megert
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Deepak Azad

2010-10-21 11:28:01 EDT

The properties file editor should 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.

Comment 1 Dani Megert

2010-10-21 11:36:10 EDT

This would need a builder. Questionable whether we want to waste performance for such a feature.

What we could do easily is reporting this as part of our "Find Broken Externalized Strings" action.

Comment 2 Deepak Azad

2010-10-21 11:45:39 EDT

(In reply to comment #1)
> What we could do easily is reporting this as part of our "Find Broken
> Externalized Strings" action.
How about showing the problems the same way as Spell errors in an open editor? The computation could probably be done along with coloring of special characters (Bug 106721).

Comment 3 Dani Megert

2010-10-21 11:48:08 EDT

(In reply to comment #2)
> (In reply to comment #1)
> > What we could do easily is reporting this as part of our "Find Broken
> > Externalized Strings" action.
> How about showing the problems the same way as Spell errors in an open editor?
> The computation could probably be done along with coloring of special
> characters (Bug 106721).

Yep, good idea!