|
From: | Urs Liska |
Subject: | Re: Annotate and Lilyglyphs |
Date: | Fri, 06 Feb 2015 21:54:01 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
Hi Craig, Am 06.02.2015 um 20:28 schrieb Craig
Dabelstein:
Thank you for testing. This at least shows me where the problem is - unfortunately an area I'm quite unfamiliar with ...
OK, the problem seems to be that the regular _expression_ that matches "any text between two "@" characters" doesn't correctly work when there are more than two such characters in the string. I would have to sort out how that regular _expression_ can match these pairs independently. Your solution just circumvents the problem but is actually not acceptable (means: it is not acceptable that such a workaround is necessary) because that means that *anything* between the two LaTeX expressions will be also parsed literally, which may be OK in cases but may also cause trouble in other cases, e.g. message = "The @\crotchet is wrong (see #12), but the \quaver@ should be fine." Here I'd want the # to be printed (referencing an issue in the tracker), but as it is it would be printed literally instead of the escaped version \#. But this makes me think if that hybrid approach of possibly mixed plain text and LaTeX code is really a good idea after all. Maybe it would be better to decide about a format for messages and simply treat the message consequently. That would mean there should be a global option saying "message body is entered as plaintext|latex|markdown|html" (as a project wide preference) and/or there can be a local property in an annotation saying message-format = "latex" What do you think? Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |