On Thu, Jul 10, 2014 at 11:47:41AM +0200, Élie Roux wrote: > > Because pretty much all pressus glyphs (with the exception of pressus maior > > with episema (and episema and celeriter) are there both for maior and minor, > > instead of saying for pressus minor it is alternate form in all cases it is > > IMHO better to say which pressus you mean, after all, the glyphs are very > > different (pressus maior virga + oriscus + punctum, pressus minor just > > oriscus + punctum). Similarly for quilismas (in the modern font above > > the author also uses everywhere ql2 vs. ql3 in the names). > > Well, this seems a good enough reason, do not hesitate to modify the > wiki page with this change!
So, I've updated the nabc page with lots of new ls: kinds,
added gr for gravis, pi for pressus minor, gl for quilisma with 2 loops
(is there any latin commonly used name for those two quilisma shapes?),
added letter modifiers to su (subpuncta) and pp for prepuncta (feel free to
suggest better names for any additions).
With subpuncta (or prepuncta) if there is height (or newly shape) specified,
I wonder if the syntax isn't ambiguous for the parser and we shouldn't
require ; in that case. Say if there is
visudst...
shall the parser parse it greedely as virga with one subpunctum at height d
followed by stropha followed by ... or as virga with one subpunctum
at default height followed by distropha followed by ...? Or is whitespace
required between each neume? vi vi vi instead of vivivi? Or do we require
the number of subpunctas to be always specified with a number? Then it
would need to be visud1st and not be ambiguous.
How do we express e.g. scandicus with 2, 3 or 4 prepunctis?
The first two are in Cardine's table, so the first two supposedly it could
be
sc and sc1
Do we treat
vipp2 and vipp3 as synonymous to those? Do we write scandicus with 4
punctis as vipp4 or scpp2 (normal scandicus with extra two prepunctis)?
Also, there is ~ and > alternation listed, but Cardine's table lists only
liquescens augment. and diminut., so shall > or ~ be used for the last
column in the table (and < always for the second to last)?
When I find time, I'd like to create a table of equivalences between the
glyph names from SGModern and assumed nabc strings describing for those,
so that a lua script can generate font tables with glyphs from both fonts
and the expected nabc description of those.
Jakub
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
