Re: markups: s/<>/{}/

2004-11-28 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Ok, I think I got it. This is not very straightforward. > no, that's why we need a guru like you to do it :-) > > > make web runs OK, except in input/regression where it fails on > ancient-fonts.ly -- I guess this is not related. ancient-font also fails over here.

Re: markups: s/<>/{}/

2004-11-28 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: >> There is one thing I have not done yet: adding a rule in convert-ly. > > I'm not sure that it will be feasible to add convert-ly rules, since > you have to deal with correctly nesting { } I've added a rule that should c

Re: markups: s/<>/{}/

2004-11-27 Thread Nicolas Sceaux
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > I'm not sure if it's feasible, but one thing that I did have in mind > is to convert > > { c b \bold { d e } f g } > > to > > { c b \bold d \bold e f g } > > ie. flattening a (markup_head_1_list + markup_list) that is inside a > markup_list

markups: s/<>/{}/

2004-11-27 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Hi > > Here is a patch for changing < ... > by { ... } in markups. > I had some reduce/reduce conflicts, so I had to rearrange the markup > rules a bit in order to get rid off them. > > As this is not exactly trivial (for me), I send the patch to the list > before comm

markups: s/<>/{}/

2004-11-27 Thread Nicolas Sceaux
Hi Here is a patch for changing < ... > by { ... } in markups. I had some reduce/reduce conflicts, so I had to rearrange the markup rules a bit in order to get rid off them. As this is not exactly trivial (for me), I send the patch to the list before commiting, for comments. May I? make web does