Doc: CG - Updates for building the LP Docs using XeLaTex

Doc: CG - Updates for building the LP Docs using XeLaTex

Issue 4780

Updates to the CG for building
the LP Docs using XeLaTex -
instead of the default pdfTex -
where certain symbols (asterix,
pilcrow, section obelix and
diesis signs) are not printed
in the PDF output.

An @warning{} has been added
with explanation on how to
install texlive-xetex.

Note: This does not mean XeTeX
is a mandatory requirement,
unlike the main TexLive packages
already documented.

This patch also includes
additional small typos
and grammar fixes.

[trueroad, 2016-02-26 14:18:26]

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
File Documentation/included/compile.itexi (right):

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:232: asterisk, pilcrow, section, obelisk
and diesis signs) may not be
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.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:233: printed in the PDF output.  In this
case XeLaTeX can be used instead.
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.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:241: @code{XeLaTex} instead of
@code{pdfTex} to generate the PDF documents if
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:316: asterisk, pilcrow, section, obelisk
and diesis signs) may not be
However some ligatured glyphs in LilyPond snippets (including fi etc.) may not
be printed in the PDF output.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:317: printed in the PDF output.  In this
case XeLaTeX can be used instead.
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:325: @code{XeLaTex} instead of
@code{pdfTex} to generate the PDF documents if
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:385: asterisk, pilcrow, section, obelisk
and diesis signs) may not be
However some ligatured glyphs in LilyPond snippets (including fi etc.) may not
be printed in the PDF output.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:386: printed in the PDF output.  In this
case XeLaTeX can be used instead.
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:394: @code{XeLaTex} instead of
@code{pdfTex} to generate the PDF documents if
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:446: asterisk, pilcrow, section, obelisk
and diesis signs) may not be
However some ligatured glyphs in LilyPond snippets (including fi etc.) may not
be printed in the PDF output.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:447: printed in the PDF output.  In this
case XeLaTeX can be used instead.
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:455: @code{XeLaTex} instead of
@code{pdfTex} to generate the PDF documents if
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:633: asterisk, pilcrow, section, obelisk
and diesis signs) may not be
However some ligatured glyphs in LilyPond snippets (including fi etc.) may not
be printed in the PDF output.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:634: printed in the PDF output.  In this
case XeLaTeX can be used instead.
XeTeX instead of XeLaTeX

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
Documentation/included/compile.itexi:636: to build the LilyPond documentation
will use @code{XeLaTex} instead of
XeTeX instead of XeLaTeX

[pkx166h, 2016-03-01 19:26:49]

Hosoda-san's edits. Domou.

[pkx166h, 2016-03-01 19:27:26]

Many thanks.

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
File Documentation/included/compile.itexi (right):

https://codereview.appspot.com/287240043/diff/1/Documentation/included/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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/compil...
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.

[trueroad, 2016-03-02 09:40:32]

LGTM

[pkx166h, 2017-03-19 19:05:23]

author James Lowe pkx166h@gmail.com
Thu, 25 Feb 2016 06:59:07 +0000 (06:59 +0000)
committer James Lowe pkx166h@gmail.com
Thu, 10 Mar 2016 18:25:39 +0000 (18:25 +0000)
commit f2f2ed7bd177ed22334c9d3bc1ab3352050557e7