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/changes.tely:1037:
On 2017/07/26 20:09:33, lemzwerg wrote:
> It would be nice to have an example of a feature that needs an index
(e.g.,
the
> `salt' or `swsh' features).
Done.
https://codereview.appspot.com/328140043/diff/1/Documentation/notation/text.itely
File Documentation/notation/text.itely (right):
https://codereview.appspot.com/328140043/diff/1/Documentation/notation/text.itely#newcode1464
Documentation/notation/text.itely:1464:
On 2017/07/26 15:38:12, pkx166h wrote:
> Would it be appropriate to add something after this @lilypond
example like:
>
> For the full OpenType font feature list please see:
>
> @uref{https://www.microsoft.com/typography/otspec/featurelist.htm}
>
> Otherwise LGTM
Done.
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 they're all recognized, of course.
https://codereview.appspot.com/328140043/
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
