Document all outside-staff-priority values; neaten table (issue 280580043 by philehol...@googlemail.com)

2016-01-01 Thread PhilEHolmes
Reviewers: , Message: Please review. Description: Follows on from a question on -user. There aren't that many values of outside-staff-priority, so it seems easiest to list them all if we're going to list most. The adjustments to the column widths get rid of unnecessary line wrapping. Please

Re: Document all outside-staff-priority values; neaten table (issue 280580043 by philehol...@googlemail.com)

2016-01-01 Thread Simon Albrecht
On 01.01.2016 13:43, philehol...@googlemail.com wrote: Reviewers: , Message: Please review. Description: Follows on from a question on -user. There aren't that many values of outside-staff-priority, so it seems easiest to list them all if we're going to list most. The adjustments to the

Re: Document all outside-staff-priority values; neaten table (issue 280580043 by philehol...@googlemail.com)

2016-01-01 Thread Carl Sorensen
On 1/1/16 5:43 AM, "lilypond-devel-bounces+c_sorensen=byu@gnu.org on behalf of philehol...@googlemail.com" wrote: >Reviewers: , > >Message: >Please review. > >Description: >Follows on from a question

Re: Document all outside-staff-priority values; neaten table (issue 280580043 by philehol...@googlemail.com)

2016-01-01 Thread Phil Holmes
- Original Message - From: "Carl Sorensen" To: ; ; Sent: Friday, January 01, 2016 4:14 PM Subject: Re: Document all outside-staff-priority values; neaten table (issue

Re: Snippet 706: Generating custom flags

2016-01-01 Thread Masamichi HOSODA
>>> By your patch, `@S' and `@P' are no problem. † and ‡ occur no >>> errors but they are missed in PDF. > > Yes, there are more problems in texinfo.tex with non-8bit engines – it > seems that the complete UTF-8 logic is severely broken in that case. > > For 8bit engines, the glyphs for † and ‡