Community
Participate
Working Groups
The parser that we use converts < and > 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 < 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).
The behavior of the parser was changed to correctly support the symbols '<' and '>'. a) When the sequences '<' and '>' 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 '&lt;' and '&gt;' are rendered in the graphical editor, they are unescaped to the sequences '<' and '>'. 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 '<' and '>'.
+1 for Helios SR1
