glossaryText field should put all text on one line, and not use \-characters as line breaks.

[RieksJ]

The glossaryText field is not on one line, but contains -characters that designate line breaks.

Thus, if such a line were to include a lengthy termref such as this is a very long showtext, it could be spread over two lines, which would mean that the TRRT might not recognize it as the termref that it is.

[morethinks]

Created a PR for this issue. glossaryText wasn't the only field having this problem.
#46

[brianorwhatever]

@RieksJ when you say "The glossaryText field is not on one line" do you mean in the test files or is there a specific location you are referring to? It appears Ryan has fixed this in the test files but before closing this would like to confirm that is the correct location.

[RieksJ]

Back in October, I used the MRG generator (locally) on the 'curated texts' of the TEv2 documentation. The result is here. Lines 63, 91-92, and more, show what's wrong.

I can imagine though that it is not just the glossaryText field that would suffer from broken lines. I expect that there may be other fields that have lengthy texts. The terms in the essif-lab framework repo, for example, have fields 'hoverText' that will also be quite long.

I am under the impression that MRG-entries that are created according to the current version of the spec would not have such issues. Could you make sure this is the case?