Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312971

Summary:	Localization Editor does not accept < and > characters
Product:	z_Archived	Reporter:	Daniel Barboza Franco <nkvg64>
Component:	Sequoyah	Assignee:	Project Inbox <localization.sequoyah-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ericc, kpqb38, nkvg64, wmg040
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Daniel Barboza Franco

2010-05-14 15:27:33 EDT

The parser that we use converts &lt; and &gt; to < and >. The side effect of this is that it is not possible typing something like 4 < 5 in our editor. When someone is typing < or > our editor expects a tag, and this will generate an error, on the other hand if someone types &lt; it will be converted to < leading to the same problem.

Possible solution:
We could add an option that changes the way our editor behaves so that we can accept both scenarios (tags and mathematical inequalities).

Comment 1 Daniel Drigo Pastore

2010-08-05 13:05:39 EDT

The behavior of the parser was changed to correctly support the symbols '<' and '>'. 

a) When the sequences '&lt;' and '&gt;' are rendered in the graphical editor, they are unescaped to the symbols '<' and '>'. Those symbols are used only to represent HTML tags that can be inserted in texts to be translated.

b) When '&amp;lt;' and '&amp;gt;' are rendered in the graphical editor, they are unescaped to the sequences '&lt;' and '&gt;'. Those sequences must be used if the user wants to show '<' or '>' in texts to be translated.

Conclusion: if anyone needs to use the mathematical symbols '<' or '>' in a text, they should use the escaped sequences '&lt;' and '&gt;'.

Comment 2 Eric Cloninger

2010-08-11 12:05:58 EDT

+1 for Helios SR1