> The way I'm used to thinking about commands would include "@" in any
> internal command.  Since users can't use "@" under normal circumstances
> said commands are protected from user manipulation.  Commands without
> "@" are user commands.  Hence, when I saw three versions of the
> includescore command, none with an "@" in them, I assumed that they were
> all user commands which represented an evolving naming convention with
> all of them being included for backwards compatibility.
> 
> Would it be a good idea to modify the internal commands somewhat?  Maybe:
> \greincludetexscore -> \gre@includetexscore
> \greincludegabcscore -> \gre@includegabcscore
> 
> Additionally the commands using the "legacy" naming conventions could
> issue a warning indicating that they are depreciated and may be removed
> at some point.

But, but that would mean making the change for all internal commands,
and there are quite a few of them... I cannot remember why I haven't
used this (though I remember asking myself the question). It's possible
that it was in order to keep PlainTeX compatibility (which is important,
though not useful right now)...

> While I tried to make the README have fully detailed instructions, there
> is just so much that one can do with plain text.  Right now I'm testing
> the engines on TeXWorks, which functions very similarly to TeXShop and
> has versions for Windows and Linux.

This is really good!

>  While I don't have a Linux machine
> (and am not familiar enough with it to use Parallels to create a VM of
> it) I can and will test them on Windows (XP at least) in addition to Mac
> OSX.  Preliminary tests have them working already in OSX (I just have to
> double check some stuff with paths and filenames).  Once I get them
> working on Windows as well, I'll start working on a full set of
> documentation for the website that includes pictures and examples.  I've
> already checked out a copy of the website in preparation for that.

Great, thanks!
-- 
Elie

_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel

Répondre à