|
From: | Urs Liska |
Subject: | Re: ScholarLy and Latex |
Date: | Wed, 7 Mar 2018 17:12:42 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
Hi Craig, sorry for the delay, but I had quite reduced capacities during the past week. I'm even more sorry to inform you that what you experience is "expected behaviour" and the result of incomplete implementation :-( The exported annotations put a number of information items (including the message!) in one optional argument, followed by four mandatory arguments with the curly braces.
However, in the .sty file the commands are defined to expect six arguments, the first one being optional: \newcommand{\criticalRemark}[6][]{ \annotation[#1]{#2}{#3}{#4}{#5}{#6} {Critical Remark}}This makes \criticalRemark call \annotation, pass its six arguments to it and one hard-coded "Critical Remark" argument as seventh. The code exported from scholarly does not export that sixth argument, and consequently it is empty when it reaches \annotation. As you have noticed, if you copy the entry to the end of the list of arguments it will be printed correctly. I'm not sure what to advise you right now. Your are actually suffering from the fact that I didn't manage to keep hold of the project. In addition to what is "publicly" available there is an "initial LaTeX package" in the repository, on the unmerged branch 'initial-latex-package' with substantial code additions and unfortunately the lack of review on my part. Maybe this branch is actually ready to be merged, but I simply don't really know. And unfortunately I can't promise to change that immediately. Although I should take your report as the incentive to finally get back to that, now that lyluatex is also "out". I have pushed a temporary fix to the temp-print-message branch. If you checkout that branch and recompile the LilyPond score the annotation message will be added to the list of arguments, and your report.sty will properly read in the message. But I don't really like that hack, and you have to be aware that this interface may not be stable. Sorry for not having much better info for you Best Urs Am 02.03.2018 um 10:25 schrieb Craig
Dabelstein:
|
[Prev in Thread] | Current Thread | [Next in Thread] |