Re: GDP: consistency in @q @qq @samp @code

2007-10-12 Thread Werner LEMBERG
> Other than the possibility of using @musicterm{} instead of @var{} > (but producing the same output), I like this. Me too. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GDP: consistency in @q @qq @samp @code

2007-10-11 Thread Graham Percival
Kurt Kroon wrote: Does TeXInfo give you access to just that part, or do you have to make changes in a global style sheet, which then affects all outputs (not just the HTML)? As far as I know, we _just_ change the HTML style sheet. I don't think we can change the output for other formats. (I

Re: GDP: consistency in @q @qq @samp @code

2007-10-10 Thread Graham Percival
(I'm CCing this back to -devel. Kurt: if this causes problems for you, feel free to remove the -devel CC when you reply.) Kurt Kroon wrote: On 10/9/07 11:46 PM, "Graham Percival" <[EMAIL PROTECTED]> wrote: In that case, I don't think that @samp{cresc} (as in "@samp{crescendo} is often abbrev

Re: GDP: consistency in @q @qq @samp @code

2007-10-09 Thread Graham Percival
Werner LEMBERG wrote: How about @[EMAIL PROTECTED] }} instead? I think that actual input should be in a monospace font, and these commands nest without problem. This is redundant -- @samp{} already produces fixed-width output. Oops, I didn't realize that. In that case, I don't think that @s

Re: GDP: consistency in @q @qq @samp @code

2007-10-09 Thread Werner LEMBERG
> How about @[EMAIL PROTECTED] }} instead? I think that actual input should > be in a monospace font, and these commands nest without problem. This is redundant -- @samp{} already produces fixed-width output. Werner ___ lilypond-devel mailing l

Re: GDP: consistency in @q @qq @samp @code

2007-10-09 Thread Graham Percival
Werner LEMBERG wrote: @code{}: actual lilypond code or property/context names. @samp{}: refers to pieces of notation, such as: @samp{crescendo} is often abbreviated as @samp{cresc.}. Sounds fine. Actually, I've always tried to clean up the code accordingly. However, sometimes it's better IM

Re: GDP: consistency in @q @qq @samp @code

2007-10-08 Thread Werner LEMBERG
> I'd like to have some consistent usage amongst these terms. Here's > my proposal: > > @code{}: actual lilypond code or property/context names. > > @qq{}: only for actual quotes -- ie "he said" or "she wrote". > > @samp{}: refers to pieces of notation, such as: @samp{crescendo} is > often abbr

GDP: consistency in @q @qq @samp @code

2007-10-08 Thread Graham Percival
I'd like to have some consistent usage amongst these terms. Here's my proposal: @code{}: actual lilypond code or property/context names. @qq{}: only for actual quotes -- ie "he said" or "she wrote". @samp{}: refers to pieces of notation, such as: @samp{crescendo} is often abbreviated as @sam