Many thanks.
https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi File Documentation/included/compile.itexi (right): https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode232 Documentation/included/compile.itexi:232: asterisk, pilcrow, section, obelisk and diesis signs) may not be On 2016/02/26 14:18:26, trueroad wrote:
In this issue, missing glyphs are not asterisk, pilcrow, section,
obelisk and
diesis signs. Ligatured glyphs in LilyPond snippets (including fi etc.) are missing.
How about this?
However some ligatured glyphs in LilyPond snippets (including fi etc.)
may not
be printed in the PDF output.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode233 Documentation/included/compile.itexi:233: printed in the PDF output. In this case XeLaTeX can be used instead. On 2016/02/26 14:18:26, trueroad wrote:
XeLaTeX means XeTeX with LaTeX. Similary, pdfLaTeX means pdfTeX with LaTeX. In other words, pdfTeX corresponding to XeTeX instead of XeLaTeX.
How about this?
In this case XeTeX can be used instead.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode241 Documentation/included/compile.itexi:241: @code{XeLaTex} instead of @code{pdfTex} to generate the PDF documents if On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode316 Documentation/included/compile.itexi:316: asterisk, pilcrow, section, obelisk and diesis signs) may not be On 2016/02/26 14:18:26, trueroad wrote:
However some ligatured glyphs in LilyPond snippets (including fi etc.)
may not
be printed in the PDF output.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode317 Documentation/included/compile.itexi:317: printed in the PDF output. In this case XeLaTeX can be used instead. On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode325 Documentation/included/compile.itexi:325: @code{XeLaTex} instead of @code{pdfTex} to generate the PDF documents if On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode385 Documentation/included/compile.itexi:385: asterisk, pilcrow, section, obelisk and diesis signs) may not be On 2016/02/26 14:18:26, trueroad wrote:
However some ligatured glyphs in LilyPond snippets (including fi etc.)
may not
be printed in the PDF output.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode386 Documentation/included/compile.itexi:386: printed in the PDF output. In this case XeLaTeX can be used instead. On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode394 Documentation/included/compile.itexi:394: @code{XeLaTex} instead of @code{pdfTex} to generate the PDF documents if On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode446 Documentation/included/compile.itexi:446: asterisk, pilcrow, section, obelisk and diesis signs) may not be On 2016/02/26 14:18:26, trueroad wrote:
However some ligatured glyphs in LilyPond snippets (including fi etc.)
may not
be printed in the PDF output.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode447 Documentation/included/compile.itexi:447: printed in the PDF output. In this case XeLaTeX can be used instead. On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode455 Documentation/included/compile.itexi:455: @code{XeLaTex} instead of @code{pdfTex} to generate the PDF documents if On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode633 Documentation/included/compile.itexi:633: asterisk, pilcrow, section, obelisk and diesis signs) may not be On 2016/02/26 14:18:26, trueroad wrote:
However some ligatured glyphs in LilyPond snippets (including fi etc.)
may not
be printed in the PDF output.
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode634 Documentation/included/compile.itexi:634: printed in the PDF output. In this case XeLaTeX can be used instead. On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/diff/1/Documentation/included/compile.itexi#newcode636 Documentation/included/compile.itexi:636: to build the LilyPond documentation will use @code{XeLaTex} instead of On 2016/02/26 14:18:26, trueroad wrote:
XeTeX instead of XeLaTeX
Done. https://codereview.appspot.com/287240043/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
