source: pst/typesetting/typesetting.xml

Last change on this file was 45ab6c7, checked in by Xi Ruoyao <xry111@…>, 2 years ago

more SVN prop clean up

Remove "$LastChanged$" everywhere, and also some unused $Date$

  • Property mode set to 100644
File size: 3.7 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
8<chapter id="pst-typesetting">
9 <?dbhtml filename="typesetting.html"?>
11 <title>Typesetting</title>
13 <para>
14 This chapter includes <application>texlive</application> applications that
15 create output equivalent to typesetting.
16 </para>
18 <para>
19 There are two alternative routes through this chapter:
20 </para>
22 <para>
23 Some people may wish to use the binary installer, either because of the
24 complexity of installing all of <application>texlive</application> from
25 source, or because they only want a part of the package, or perhaps because
26 they wish to get updates as soon as those are available (the source is only
27 updated annually, but the binaries and associated tex and sty files are
28 updated for approximately 10 months). These people should begin at <xref
29 linkend="tex-path"/> and then follow the <xref linkend="tl-installer"/>
30 instructions. After installing, they can run <command>tlmgr</command> to
31 update their system.
32 </para>
34 <para>
35 Most people reading BLFS will wish to build from source. BLFS used to
36 start by installing <application>install-tl-unx</application> and then
37 use that to bootstrap the build. Nowadays, we build almost the whole
38 of <application>texlive</application> <emphasis>without</emphasis> a
39 binary install, by adding the separately-packaged texmf files into this
40 build. For this, begin at <xref linkend="tex-path"/> then go to <xref
41 linkend="texlive"/> which will install most of
42 <application>texlive</application>, together with <emphasis>all</emphasis>
43 of the supporting files. This almost-complete install can then be used
44 to build the remaining parts of <application>texlive</application>:
45 <xref linkend="asymptote"/>, <xref linkend="biber"/> and <xref
46 linkend="xindy"/>.
47 </para>
49 <para>
50 Because the texmf files (including documentation, fonts, scripts and
51 supporting files) are all in one tarball, it is not practical to limit what
52 gets extracted in a sensible way (you could exclude one or other of the
53 typesetting engines, not its many supporting files) when building from
54 source in this manner.
55 </para>
57 <para>
58 In either case, BLFS installs into
59 <filename class="directory">/opt/texlive/&texlive-year;</filename>.
60 </para>
62 <para>
63 Also, please note that texlive is released annually, and updating from the
64 previous year to the current year is no longer supported. If for some
65 reason you wish to keep versions for multiple years, for most things
66 you can mount the old or new system at /opt/texlive and fix up your
67 PATH as necessary. However doing that will not preserve any changes in
68 <filename class="directory">texmf-local</filename> and if you build
69 from source and try to run a newer version of
70 <application>biber</application> with an older version of
71 <application>biblatex</application> it is unlikely to work.
72 </para>
74 <xi:include xmlns:xi="" href="tex-path.xml"/>
75 <xi:include xmlns:xi="" href="tl-installer.xml"/>
76 <xi:include xmlns:xi="" href="texlive.xml"/>
77 <xi:include xmlns:xi="" href="asymptote.xml"/>
78 <xi:include xmlns:xi="" href="biber.xml"/>
79 <xi:include xmlns:xi="" href="dvisvgm.xml"/>
80 <xi:include xmlns:xi="" href="xindy.xml"/>
Note: See TracBrowser for help on using the repository browser.