Closed Melissa37 closed 8 years ago
The above redone to show the proper characters,
From Graham: The last time we saw this I thought we were going to look at the possibility to move from < back to < for the < characters. We had good support for that. I don't think it was a final decision though, because you mentioned < was part of the new procedure you'd devised.
I was going to have to rework how the text is parsed in order to try and fix this. < comes through as a < character, natively, and and it conflicts with the tag recognition logic for finding
From Graham: The last time we saw this I thought we were going to look at the possibility to move from < back to < for the < characters. We had good support for that. I don't think it was a final decision though, because you mentioned < was part of the new procedure you'd devised. I was going to have to rework how the text is parsed in order to try and fix this. < comes through as a < character, natively, and and it conflicts with the tag recognition logic for finding, tags, etc.
I can look at writing an automated test against this new tagging scheme, and then try and rewrite the way these nested tags are dealt with.
Graham to look at this week