Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread lemzwerg
I'm not aware of such an online tool. I've posted a question on Typedrawers. http://typedrawers.com/discussion/2292/list-of-opentype-font-feature-inspection-tools At least for the command line I got the right information! Given that many people already have TeXLive installed, the `otfinfo' p

Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread tisimst . lilypond
On 2017/07/31 17:48:10, lemzwerg wrote: > If Pango really is agnostic of the features, that is really exciting and a bit > mysterious ;-). Why? It's not Pango but HarfBuzz that processes (i.e., applies) the OpenType features to a run of glyphs. Ah, I see! Thanks for clarifying that. I d

Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread lemzwerg
If Pango really is agnostic of the features, that is really exciting and a bit mysterious ;-). Why? It's not Pango but HarfBuzz that processes (i.e., applies) the OpenType features to a run of glyphs. Perhaps a note should be added, though, to mention that if the user requests a feature tha

Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread tisimst . lilypond
On 2017/07/31 16:58:40, lemzwerg wrote: In general, Pango is agnostic of the features themselves, AFAIK. It simply forwards the selected stuff to the font in question. If Pango really is agnostic of the features, that is really exciting and a bit mysterious ;-). However, the user has first

Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread lemzwerg
This is really great! Do you happen know what the current limitations are? Or rather, having the full feature list is great, but if only a few features are actually recognized by the underlying typography engine (it's still Pango, right?), that would probably be a better list to show, unless

Re: rest/mm-rest-markup

2017-07-31 Thread Thomas Morley
2017-07-31 18:09 GMT+02:00 David Kastrup : > David Nalesnik writes: > >> On Mon, Jul 31, 2017 at 9:08 AM, David Kastrup wrote: >>> Thomas Morley writes: >>> Hi David, this refers to http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html I opened a new thr

Re: Add usage of OpenType font feature to the documents (issue 328140043 by truer...@gmail.com)

2017-07-31 Thread tisimst . lilypond
On 2017/07/27 13:47:01, trueroad wrote: Thank you for your reviewing. https://codereview.appspot.com/328140043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/328140043/diff/1/Documentation/changes.tely#newcode1037 Documentation/ch

Re: rest/mm-rest-markup

2017-07-31 Thread David Kastrup
David Nalesnik writes: > On Mon, Jul 31, 2017 at 9:08 AM, David Kastrup wrote: >> Thomas Morley writes: >> >>> Hi David, >>> >>> this refers to >>> http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html >>> I opened a new thread, because this one will be about rest-markups only.

Re: rest/mm-rest-markup

2017-07-31 Thread David Nalesnik
On Mon, Jul 31, 2017 at 9:08 AM, David Kastrup wrote: > Thomas Morley writes: > >> Hi David, >> >> this refers to >> http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html >> I opened a new thread, because this one will be about rest-markups only. >> >> rest-by-number-markup and r

Re: rest/mm-rest-markup

2017-07-31 Thread David Kastrup
Thomas Morley writes: > Hi David, > > this refers to > http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html > I opened a new thread, because this one will be about rest-markups only. > > rest-by-number-markup and rest-markup were impemented by myself > commit ffa21bb1a55d2436bb4

rest/mm-rest-markup

2017-07-31 Thread Thomas Morley
Hi David, this refers to http://lists.gnu.org/archive/html/lilypond-devel/2017-07/msg00144.html I opened a new thread, because this one will be about rest-markups only. rest-by-number-markup and rest-markup were impemented by myself commit ffa21bb1a55d2436bb432c4dff7ec04df95dc6f0 My second patch