my-girlfriend-jingtian-latex

`my-girlfriend-jingtian-latex` is a specialized LaTeX typesetting repository configured explicitly for a 5 x 8 inch print layout using the XeLaTeX engine. Despite its compact repository footprint, the setup provides a clean baseline for automated PDF generation with precise target dimensions. ### Technical Architecture & Engine Requirements The core engine choice here is XeLaTeX, built on top of a standard TeX Live distribution. XeLaTeX offers native Unicode processing and modern font handling out of the box, making it the standard choice for non-Latin scripts and custom typesetting compared to legacy `pdflatex` pipelines. The primary document entry point is `main.tex`, targeted to output a physical geometry of 5 x 8 inches—a common trim size for specialized book printing and standalone publishing projects. ### Build Pipeline & Compilation Strategy The repository utilizes a strict shell-based build pipeline designed to keep the source tree clean while enforcing hard stops on build errors. Here is the exact build sequence required to compile the document: ```bash mkdir -p build xelatex -interaction=nonstopmode -halt-on-error -output-directory=build main.tex xelatex -interaction=nonstopmode -halt-on-error -output-directory=build main.tex ``` Breaking down the specific CLI flags used in this build script: * **`-output-directory=build`**: Isolates all compilation artifacts—including `.aux`, `.log`, `.xdv`, and the final `.pdf` file—into the `build/` directory. This prevents cluttering the root directory with temporary TeX logs and metadata. * **`-interaction=nonstopmode`**: Disables the interactive CLI prompt that standard TeX engines trigger when encountering syntax issues or missing fonts. This ensures the command runs cleanly within headless automation or CI environments. * **`-halt-on-error`**: Forces the process to exit immediately with a non-zero exit code if a fatal parsing error occurs, preventing partial or broken build runs from going unnoticed. ### Multi-Pass Execution Logic The build script deliberately executes `xelatex` twice. In TeX engine mechanics, a single pass only parses the document tree and writes structural layout data (such as cross-references, page counts, and table of contents positions) into auxiliary files inside the output directory. The second execution pass reads those newly generated auxiliary files from `build/` to accurately resolve page references, adjust layout spacing, and finalize rendering. ### Setup Instructions To build this project locally, ensure you have a standard TeX Live environment installed that includes the `xelatex` executable. Clone the repository, open your terminal at the root path, and execute the build commands directly. The resulting compiled PDF will be located in the `build/` folder.