Tracy Llenos a écrit :
> Hi,
>
> I noticed some wrong outputs when using a punctum mora -- something
> like (b.) puts the dot on the line, since in gregoriotex-syllable.tex,
> there is this patch:
>
> \def\calculateglyphraisevalue#1#2{%
> ...
> \ifx b#1%
> \global\tempcount=\number 2%
> %\global\isonaline=1 % temporary (or not) patch, for some complex
> reasons (think of a vertical episemus for a c)
> \fi%
> ...
>
>
> If this is going to be a "somewhat permanent" :-) temporary patch,
> then I made this workaround for the \punctummora and \augmentumduplex
> macro definitions (looking back though, it may be better for the
> visual score output if the punctum mora special case is handled inside
> \calculateglyphraisevalue instead, so that the dot's height is
> slightly adjusted the same way as for the other lines...):
>
> Index: tex/gregoriotex-signs.tex
> ===================================================================
> --- tex/gregoriotex-signs.tex (revision 506)
> +++ tex/gregoriotex-signs.tex (working copy)
> @@ -190,7 +190,11 @@
> \else %
> \hskip\spacebeforesigns%
> \fi %
> +\ifx b#1%
> +\calculateglyphraisevalue{c}{4}%
> +\else%
> \calculateglyphraisevalue{#1}{4}%
> +\fi%
> \raise \glyphraisevalue \hbox{\gregorianfont \char 14}%
> \ifnum#2=1\relax %
> \setbox\Tempwidth=\hbox{\gregorianfont \char 14}%
> @@ -204,7 +208,11 @@
> % a function to typeset a augmentum duplex, the argument is the
> letter of the height of the augmentum duplex
> \def\augmentumduplex#1{%
> \hskip\spacebeforesigns%
> +\ifx b#1%
> +\calculateglyphraisevalue{a}{2}%
> +\else
> \calculateglyphraisevalue{#1}{2}%
> +\fi %
> \raise \glyphraisevalue \hbox{\gregorianfont \char 15}%
> \relax%
> }
>
>
>
> My actual question is about the augmentum duplex- because there is
> wrong output there too. For example, it's too low with (ij..) or
> (dgd..). I rewrote the "libgregorio_gregoriotex_write_auctum_duplex"
> function in gregoriotex-write.c of my local copy, and the visual score
> output produced by GregorioTeX is now correct, but I'm not sure I did
> it in a "good" way. Perhaps someone can explain this background
> first... Is the augmentum duplex XML property meant to only describe
> the specific case of two dots in adjacent spaces? What should
> something like this (ei..) be labelled then? Or does "augmentum
> duplex" describe any two vertically aligned dots, in which case it's
> non-unique, and a little peculiar that it's only a property of one
> note, since it needs information from 2 to determine how far apart the
> dots are. Am I making sense? :-)
>
I'll check it out, I think the best way would be to only modify the
\calculateglyphraisevalue. I'll try to do that today.
Don't you want to subscribe to gregorio-devel and help me with the
maintenance of gregorio? I've been working on it during three years,
I'll try to release a stable version and to communicate about it in the
different monasteries I know, but after that I think I'll be quite
tired... And not so many people understand TeX as you do.
Thank you,
--
Elie
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
