andy/Probability-and-Statistics-Notes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Started a PreTeXt book.

Browse Source
This commit is contained in:
andyeisenberg
2025-12-28 16:44:30 +00:00
parent a6bd475da4
commit 5602f92eb7
12 changed files with 664 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/pretext-cli.yml
+117
View File
@@ -0,0 +1,117 @@
# This file was automatically generated with PreTeXt 2.32.0.
# If you modify this file, PreTeXt will no longer automatically update it.
#
# This workflow file can be used to automatically build a project and create
# an artifact for deployment. It can also be used to deploy the project to
# GitHub Pages or Cloudflare Pages.
#
# The workflow is triggered on pull requests or can be run manually. You can uncomment
# the `push` event to have it run on pushes to the main branch as well.
name: PreTeXt-CLI Actions
on:
# Runs on pull requests
pull_request:
branches: ["*"]
## Runs on pushes to main
#push:
# branches: ["main"]
# Runs on demand
workflow_dispatch:
jobs:
build:
runs-on: ubuntu-latest
container: oscarlevin/pretext-full
steps:
- name: Checkout source
uses: actions/checkout@v4
- name: install deps
run: pip install -r requirements.txt
- name: set up node
uses: actions/setup-node@v4
with:
node-version: '22'
- name: install local ptx files
run: pretext --version
- name: build deploy targets
run: |
version="$(pretext --version)"
major="$(echo $version | cut -d '.' -f 1)"
minor="$(echo $version | cut -d '.' -f 2)"
if [ "$major" -ge 2 -a "$minor" -ge 5 ]; then
echo "PreTeXt version is 2.5 or greater; using new build command"
pretext build --deploys
else
echo "PreTeXt version is less than 2.5, using old build command"
pretext build
fi
- name: stage deployment
run: pretext deploy --stage-only
- name: Bundle output/stage as artifact
uses: actions/upload-artifact@v4
with:
name: deploy
path: output/stage
deploy-cloudflare:
runs-on: ubuntu-latest
needs: build
if: vars.CLOUDFLARE_PROJECT_NAME != ''
permissions:
contents: read
deployments: write
steps:
- name: Download artifact
uses: actions/download-artifact@v4
with:
name: deploy
path: deploy
- name: Create 404.html
run: echo "404 page not found" >> deploy/404.html
- name: Publish to Cloudflare
uses: cloudflare/pages-action@v1
with:
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
projectName: ${{ vars.CLOUDFLARE_PROJECT_NAME }}
gitHubToken: ${{ secrets.GITHUB_TOKEN }}
branch: ${{ github.head_ref || github.ref_name }}
directory: deploy
deploy-ghpages:
runs-on: ubuntu-latest
needs: build
if: vars.PTX_ENABLE_DEPLOY_GHPAGES == 'yes' && github.ref == format('refs/heads/{0}', github.event.repository.default_branch)
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "page"
cancel-in-progress: false
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Download website artifact
uses: actions/download-artifact@v4
with:
name: deploy
path: deploy
- name: Setup GitHub Pages
id: check
uses: actions/configure-pages@v4
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: deploy
- name: Deploy to Github Pages
id: deployment
uses: actions/deploy-pages@v4
.github/workflows/pretext-deploy.yml
+68
View File
@@ -0,0 +1,68 @@
# This file was automatically generated with PreTeXt 2.32.0.
# If you modify this file, PreTeXt will no longer automatically update it.
#
name: Build and Deploy
on:
# Currently, this workflow only runs when manually selected (the `workflow_dispatch` event).
# If you would like it to run on other events, uncomment some of the lines below.
# # Runs on pull requests
# pull_request:
# branches: ["*"]
# # Runs on pushes to main
# push:
# branches: ["main"]
# # Runs every day at 00:00 UTC
# schedule:
# - cron: '0 0 * * *'
# Runs on demand
workflow_dispatch:
permissions:
contents: write
jobs:
build-and-deploy:
runs-on: ubuntu-latest
container: oscarlevin/pretext-full
steps:
- name: Checkout source
uses: actions/checkout@v4
- name: set up node
uses: actions/setup-node@v4
with:
node-version: '22'
- name: add gh-cli
run: |
apt-get update
apt-get install gh jq -y
- name: setup git config
run: |
git config --global --add safe.directory $(pwd)
git config user.name "${{ github.actor }} via GitHub Actions"
git config user.email "${{ github.actor }}@github_actions.no_reply"
- name: install deps
run: pip install -r requirements.txt --break-system-packages
- name: install local ptx files
run: pretext --version
- name: build deploy targets
run: pretext build --deploys
- name: run deploy
run: pretext deploy --no-push
- name: push gh-pages branch
run: git push origin gh-pages --force
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
README.md
+49 -18
View File
@@ -1,29 +1,60 @@
# PreTeXt Codespace
# My PreTeXt Book
Use this template repository to quickly start a new [PreTeXt](https://pretextbook.org) project entirely in the cloud, using GitHub Codespaces.
This README was generated by running `pretext new book`. You should feel free to edit this to describe your project.
## Instructions
Look for the green button at the very top right of this page. The button should say `Use this template` (if not make sure you are logged in to GitHub).
Click on the button and select "Create a new repository". On the next page, give your project a name, select public or private (this can be changed later), and click the "Create repository from template" button.
The main source file is `source/main.ptx`. This includes the other chapters of the book.
You now have a GitHub repository saved in your account. You can come back to that page any time you want to work on your project (note the URL or else find it in the list of your repositories when you log in to GitHub).
To compile the book as an accessible website, run `pretext build web` in a terminal from any directory of this project.
To start work on your project, go to the green button at the top of *your* repository's page, which will say `<> Code`.
To preview your output, run `pretext view web`.
1. Click on this button.
2. Click on the tab that says "Codespaces."
3. Click "Create codespace on main."
To deploy your output to GitHub pages, run `pretext deploy`.
This will open a new tab with a browser version of VS Code including everything set up to start working. (When you first create a codespace for a project, it may take 5-10 minutes; when you restart a codespace it will be much faster). The first thing you should do is create a new PreTeXT project.
To compile a pdf, run `pretext build print`.
### Creating a New Project
---
1. Open the command palette by hitting `Ctrl+Shift+P` (or `F1`) and start typing "pretext new". You will see a command titled "PreTeXt: New Project".
2. Hit `Enter` and select what sort of project you would like to create.
3. Select the current suggested folder for the location of your project.
Below you will find some advice for working with PreTeXt, including help with using the [PreTeXt Codespace](https://github.com/PreTeXtBook/pretext-codespace) online editor through GitHub if you don't want to install the required software on your own computer.
The window should reload and you will have your project there. This readme will be gone, but you will get a new one with some new hints.
Next time you want to work on your book, return to your newly created repository, go to the green `<> Code` button, and select the codespace you previously created. If you don't see that codespace (perhaps you deleted it to save space), you can always create a new codespace.
## Learning PreTeXt
See the [PreTeXt documentation](https://pretextbook.org/documentation.html) for links to a variety of resources.
We also recommend browsing through the [annotated sample article](https://pretextbook.org/examples/sample-article/annotated) and [annotated sample book](https://pretextbook.org/examples/sample-book/annotated/) if you want to find examples and see the PreTeXt source for those examples quickly.
## Using GitHub Codespaces
GitHub Codespaces are a way to set up your whole authoring system entirely in your browser. In case you are not already reading this inside a codespace, you can create one specifically designed for authoring in PreTeXt by using [this template](https://github.com/PreTeXtBook/pretext-codespace).
### Important: how to save your files
The most important thing to remember when authoring in a codespace is that you are making all your edits on a *virtual machine* off in some remote server farm. This means there is an extra step to save your files. You can save files in the editor (in your browser), but this just saves them to that virtual machine. To make sure you can access these files, even if the virtual machine goes away, you need to sync them to github.com. This is done by *committing* your changes and then *pushing* those commits (or "syncing" them). You might see a warning when you restart your codespace that you have "uncommitted changes" -- make sure you commit them when you are done working.
### Troubleshooting: Latex-images and pdfs
We have tried to keep the codespace small (so it starts up quickly and doesn't eat through your monthly storage allotment), so we do not include a full TeXLive distribution. We have tried to include most packages and fonts you are likely to need to generate images using `<latex-image>` elements, and to generate PDF print output. However, if you run into a situation where the LaTeX gives errors about packages missing (like it cannot find a `mypackage.sty` file), here is what you should do.
1. To quickly resolve the issue yourself, open a terminal (``Ctrl+Shift+` ``) and use the TeXLive Package Manager to install the missing package.
a. If you know that the package is called `mypackage` then enter the following two lines:
```bash
tlmgr install mypackage
tlmgr path add
```
b. If you don't know the name of the package, but know it should contain `mypackage.sty`, then you can search using
```bash
tlmgr search --global --all "mypackage.sty"
```
2. To ensure that you don't have to repeat this step every time you recreate the codespace, add the package name to the list of installs inside the file `.devcontainer/installLatex.sh` which gets run every time a codespace is created.
3. Better yet, post the name of the missing package to this [GitHub issue](https://github.com/PreTeXtBook/pretext-codespace/issues/21) and we will add it to the devcontainer. This has the advantage that you will still get updates that other authors submit (if you edit the `installLatex.sh` file, then it won't be updated when you run `pretext update`).
### Troubleshooting: sageplot images
By far the largest space-hog in a PreTeXt authoring environment is SageMath, which is only required if you generate images using sageplots. By default, SageMath is not installed in a PreTeXt codespace, but it should be easy to install if you need it.
Just open the command palette (`Ctrl+Shift+P` of `F1`) and search for "PreTeXt: Install SageMath". This will also update the `.devcontainer/devcontainer.json` file so that the next time you create a codespace for this project, it should install automatically.
project.ptx
+73
View File
@@ -0,0 +1,73 @@
<?xml version="1.0" encoding="utf-8"?>
<!-- This file was automatically generated by PreTeXt 2.32.0. -->
<!-- If you modify this file, PreTeXt will no longer automatically update it.-->
<!-- This file, the project manifest, provides the overall configuration for your PreTeXt project. To edit the content of your document, open `source/main.ptx`. See https://pretextbook.org/doc/guide/html/processing-CLI.html#cli-project-manifest. -->
<project ptx-version="2">
<targets>
<target name="web" format="html" />
<target name="print" format="pdf" />
</targets>
</project>
<!-- SAMPLE MANIFEST illustrating all options. Defaults are given (mostly). -->
<!-- <project
ptx-version="2"
source="source"
publication="publication"
output-dir="output"
site="site"
stage="output/stage"
xsl="xsl"
asy-method="server"
generated-cache=".cache"
>
<targets>
<target
name="web"
format="html"
source="main.ptx"
publication="publication.ptx"
output-dir="web"
deploy-dir="interactive"
xsl="custom-html.xsl"
asy-method="server"
/>
<target
name="web-zipped"
format="html"
source="main.ptx"
publication="publication.ptx"
output-dir="web"
compression="zip"
asy-method="server"
/>
<target
name="runestone"
format="html"
platform="runestone"
/>
<target
name="print"
format="pdf"
source="main.ptx"
publication="publication.ptx"
output-dir="print"
output-filename="mybook.pdf"
latex-engine="pdflatex"
deploy-dir="pdf"
/>
<target
name="latex"
format="latex"
/>
<target
name="braille"
format="braille"
braille-mode="emboss"
/>
</targets>
</project>
-->
publication/publication.ptx
+215
View File
@@ -0,0 +1,215 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This is the publication file for a newly generated PreTeXt book. -->
<!-- By changing the values of attributes here, you can change how -->
<!-- the output looks and functions. For the complete documentation -->
<!-- of publication-file options, see -->
<!-- https://pretextbook.org/doc/guide/html/publisher-file-reference.html -->
<!-- Commented settings below illustrate some possible changes you can -->
<!-- make from the default values. -->
<publication>
<common>
<!-- Level at which are html files generated (chapter/section/etc): -->
<!--<chunking level="1" />-->
<!-- Depth for table of contents. 0 means no TOC -->
<!--<tableofcontents level="1" />-->
<!-- Visibility of exercise components where they first appear. -->
<!-- There are four components (statement/hint/answer/solution) for each -->
<!-- of five exercise types (inline/divisional/worksheet/reading/ -->
<!-- project). -->
<!--<exercise-inline statement="yes" hint="yes" answer="no" solution="no" />-->
<!--<exercise-divisional statement="yes" hint="yes" answer="no" solution="yes" />-->
<!--<exercise-worksheet statement="yes" hint="yes" answer="no" solution="no" />-->
<!--<exercise-reading statement="yes" hint="yes" answer="no" solution="no" />-->
<!--<exercise-project statement="yes" hint="yes" answer="yes" solution="yes" />-->
<!-- Style of fill-in-the-blanks: -->
<!--<fillin textstyle="underline" mathstyle="shade" />-->
<!-- You can set a watermark: -->
<!-- <watermark scale="0.5">DRAFT</watermark> -->
<!-- Mermaid diagram themes -->
<!-- <mermaid theme="default" /> -->
<!-- QR code image: set path to an image to put in center of QR codes -->
<!-- <qrcode image="image.png" /> -->
</common>
<!-- Set where external assets and generated assets will be -->
<!-- stored or created. Directories are relative to the main -->
<!-- source PreTeXt file -->
<source>
<!-- Paths to folders containing external assets and generated assets -->
<!-- relative to your main source file. -->
<directories external="../assets" generated="../generated-assets" />
<!-- Set which marked elements are included in this version: -->
<!-- See
https://pretextbook.org/doc/guide/html/publication-file-source.html#publication-file-source-version -->
<!-- <version include="videos labs"/> -->
</source>
<numbering>
<!-- the divisions element describes the numbering of divisions. -->
<!-- @part-structure should be "decorative" or "structural", -->
<!-- were the latter would restart numbering chapters within each -->
<!-- part (this only matters if your book has parts). -->
<!-- The attribute @chapter-start give the number of the first -->
<!-- chapter. @level says how deep (chapter->section->subsection)-->
<!-- numbering should appear. -->
<!-- For use with a book organized by part, you can set the -->
<!-- @part-structure to "decorative" or "structural" -->
<!--<divisions part-structure="decorative" chapter-start="0" level="2"/>-->
<!-- The next elements say how the levels deep to break up the -->
<!-- numbering of the respective elements. Can't be more than the -->
<!-- @level on divisions above. -->
<!--<blocks level="2" />-->
<!--<projects level="2" />-->
<!--<equations level="2" />-->
<!--<footnotes level="2" />-->
</numbering>
<!-- LaTeX specific options: set @print="yes" to get pdf set up -->
<!-- for printing; set @sides="two" if the printing would be two- -->
<!-- sided. @pageref="yes/no" controls whether page number are -->
<!-- included in cross-references -->
<latex>
<!-- Replace the <latex> tag above with the one below to try these-->
<!--
<latex
print="no"
sides="one"
open-odd="no"
pageref="no"
font-size="10"
draft="no"
latex-style="dyslexic-font"
>
-->
<!-- Control text justification and bottom page behavior. Add content intended for \geometry{} inside the <geometry> element. -->
<!--
<page right-alignment="flush" bottom-alignment="ragged" crop-marks="letter">
<geometry></geometry>
</page>
-->
<!-- The asymptote/@links set to "yes" would produce -->
<!-- links the html version of asymptote graphics. -->
<!--<asymptote links="no" />-->
<!-- Covers: provide paths to pdfs for front and back covers: -->
<!--<cover front="cover-front.pdf" back="cover-back.pdf" />-->
<!-- Set @formatted to "no" to remove formatting on worksheets: -->
<!--<worksheet formatted="yes" />-->
</latex>
<html>
<!-- A possible attribute for the html tag above is @short-answer-responses, with values either "always" or "graded". As in: -->
<!--<html short-answer-responses="always">-->
<!--The platform host can be "web" or "runestone"-->
<!--<platform host="runestone"/>-->
<!-- Whether to knowl a particular elements is set here -->
<!-- Lots of elements have this possibility; see the guide -->
<!--<knowl
theorem="no"
proof="yes"
definition="no"
example="yes"
example-solution="yes"
project="no"
task="no"
remark="no"
objectives="no"
outcomes="no"
figure="no"
table="no"
listing="no"
list="no"
exercise-inline="yes"
exercise-divisional="no"
exercise-worksheet="no"
exercise-readingquestion="no"
/>-->
<!-- Specify the theme for the html by giving names to -->
<!-- override defaults. Ex:<css theme="denver"/> -->
<!-- See also -->
<!-- https://pretextbook.org/doc/guide/html/publication-file-online.html#online-style-options -->
<!--<css theme="denver"/>-->
<!-- Search can be default or none, or you can use a Google-cx number to use google's search
feature (but then variant should be set to none to avoid conflict) -->
<!--<search variant="default" />-->
<!-- Table of Contents: focused="yes" enables expand/collapse functionality. -->
<!-- @preexpanded-levels controls how deep to expend toc initially. -->
<!--<toc focused="yes" preexpanded-levels="1" />-->
<!-- Navigation options: linear or tree, and whether there is an "up" button -->
<!--<navigation logic="tree" upbutton="no" />-->
<!-- xref options: control whether cross-references are knowls or links -->
<!--<cross-references knowled="cross-page" />-->
<!-- Embedded calculators. For math, this could be geogebra-classic, geogebra-graphing,
geogebra-geometry, and geogebra-3d. For ActiveCode, you can specify a language (python,
javascript, etc). -->
<!--<calculator model="geogebra-classic" activecode="python" />-->
<!-- Set the base URL of where the online version is hosted to have links in other formats -->
<!-- <baseurl href="https://changetomywebsite.org"/> -->
<!-- Control behavior of online WeBWorK, per type: -->
<!--<webwork
inline="dynamic"
divisional="dynamic"
reading="static"
worksheet="static"
project="dynamic"
/>-->
<!-- Use the tabbed viewer for tasks in exercises. "project" and "reading" can be added to the list of types in the @tabbed-tasks attribute (but not worksheet). -->
<!--<exercises tabbed-tasks="inline divisional"/>-->
<!-- Video privacy: the default value of "yes" disables certain tracking cookies for embedded videos. -->
<!--<video privacy="yes"/>-->
<!-- Asymptote Click to Enlarge links -->
<!--<asymptote links="yes"/>-->
<!-- Feedback button can be added with a link to an email or form -->
<!--<feedback href="mailto:youraddress@yourUni.edu"/>-->
<!-- Magic IDs identify HTML pages to analytics services -->
<!-- Presence implies relevant Javascript will be added -->
<!-- StatCounter requires both values to be set -->
<!-- <analytics
google-gst="UA-0123456-1"
statcounter-project="0123456"
statcounter-security="0123456"
/> -->
</html>
<epub>
<!-- The cover tag can have a @front attribute to specify a cover image. -->
<!-- <cover front="cover.jpg"> -->
</epub>
<!-- To use WeBWorK, you need a server. -->
<!-- <webwork server="https://webwork-ptx.aimath.org" /> -->
<!-- @course, @coursepassword, @user, and @userpassword can also be set. -->
<!-- You can also set how tasks are revealed for webwork problems using the @task-reveal attribute on the above-->
</publication>
requirements.txt
+2
View File
@@ -0,0 +1,2 @@
# This file was automatically generated with PreTeXt 2.32.0.
pretext == 2.32.0
source/backmatter.ptx
+23
View File
@@ -0,0 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file contains all of the "backmatter" material -->
<!-- In comments, we show examples of how to have hints to divisional -->
<!-- excercies appear in a section, and then their -->
<!-- solutions in the next. Then there is an appendix -->
<!-- with all notation generated, and finally the index. -->
<backmatter xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="backmatter">
<title>Backmatter</title>
<!-- <solutions divisional="hint"> <title>Selected Hints</title> </solutions> -->
<!-- <solutions divisional="solution"> <title>Selected Solutions</title> </solutions> -->
<!-- <appendix> <title>List of Symbols</title> <notation-list/> </appendix> -->
<!-- <index> <title>Index</title> <index-list/> </index> -->
<colophon>
<p> This book was authored in <pretext />. </p>
</colophon>
</backmatter>
source/ch-chapter-title.ptx
+13
View File
@@ -0,0 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter xml:id="ch-chapter-title" xmlns:xi="http://www.w3.org/2001/XInclude">
<title>Chapter Title</title>
<introduction>
<p> Text before the first section. </p>
</introduction>
<!-- include sections -->
<xi:include href="sec-section-name.ptx" />
</chapter>
source/docinfo.ptx
+35
View File
@@ -0,0 +1,35 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- The docinfo block is the analogue to the latex preamble -->
<!-- This is where you can define macros and other book-wide -->
<!-- settings. -->
<docinfo xmlns:xi="http://www.w3.org/2001/XInclude">
<!-- A unique name for the book in a catalog; for example, see https://pretextbook.org/catalog.html and https://runestone.academy/ns/books/index. It contains a simple lowercase string with no dashes or other special characters. See https://pretextbook.org/doc/guide/html/sec-publishing-to-runestone-academy.html for more information. -->
<document-id>changeme</document-id>
<!-- A brief description for the book in a catalog; see the links above. The @shelf is used only when publishing to Runestone; see https://runestone.academy/ns/books/index for a list of valid values. You must copy these @shelf names exactly, including capitalization. -->
<blurb shelf="AP Computer Science"> A simple string (no markup is allowed) to describe your book. </blurb>
<!-- The next three lines are likely for mature projects only: -->
<!-- <brandlogo url="" source="images/cover.png"/> -->
<!-- <covers front="images/front.pdf" back="images/back.pdf"/> -->
<!-- <document-id>unique-book-id</document-id> -->
<!-- macros for defining latex math shortcuts. It is good practice -->
<!-- to define these semantically, so that the macro relates to what-->
<!-- it defines. -->
<macros> \newcommand{\N}{\mathbb N} \newcommand{\Z}{\mathbb Z} \newcommand{\Q}{\mathbb Q} \newcommand{\R}{\mathbb R} </macros>
<!-- If you put any latex-image elements you can include preambles -->
<!-- for those in the next element. -->
<latex-image-preamble> \usepackage{tikz, pgfplots} \usetikzlibrary{positioning,matrix,arrows} \usetikzlibrary{shapes,decorations,shadows,fadings,patterns} \usetikzlibrary{decorations.markings} </latex-image-preamble>
<!-- It is possible to rename elements: -->
<!-- <rename element="assemblage" xml:lang="en-US">Summary</rename> -->
<!-- Specify the default type of cross reference: -->
<!-- <cross-references text="type-global" /> -->
</docinfo>
source/frontmatter.ptx
+39
View File
@@ -0,0 +1,39 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This frontmatter division will contain all content before the -->
<!-- first chapter. Fill in and comment/uncomment to see how this -->
<!-- works. -->
<frontmatter xmlns:xi="http://www.w3.org/2001/XInclude" xml:id="frontmatter">
<bibinfo>
<author>
<personname>You</personname>
<department>Your department</department>
<institution>Your institution</institution>
</author>
<date>
<today />
</date>
<website>
<url href="https://pretextbook.org">My Website</url>
</website>
<copyright>
<year>2020<ndash />2024</year>
<holder>You</holder>
<shortlicense> This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit <url href="http://creativecommons.org/licenses/by-sa/4.0/" visual="creativecommons.org/licenses/by-sa/4.0"> CreativeCommons.org</url>
</shortlicense>
</copyright>
</bibinfo>
<titlepage>
<titlepage-items/>
</titlepage>
<colophon xml:id="front-colophon">
<colophon-items/>
</colophon>
</frontmatter>
source/main.ptx
+22
View File
@@ -0,0 +1,22 @@
<?xml version="1.0" encoding="utf-8"?>
<pretext xml:lang="en-US" xmlns:xi="http://www.w3.org/2001/XInclude">
<!-- we first include a file which contains the docinfo element: -->
<xi:include href="./docinfo.ptx" />
<book xml:id="my-great-book">
<title>Andy's Book</title>
<subtitle>An example to get you started</subtitle>
<!-- Include frontmatter -->
<xi:include href="./frontmatter.ptx" />
<!-- Include chapters -->
<xi:include href="./ch-chapter-title.ptx" />
<!-- Include backmatter -->
<xi:include href="./backmatter.ptx" />
</book>
</pretext>
source/sec-section-name.ptx
+8
View File
@@ -0,0 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="sec-section-name" xmlns:xi="http://www.w3.org/2001/XInclude">
<title>Section Title</title>
<p> Text of section. </p>
</section>