mirror of
https://github.com/kuhyx/WUT_Computer_Science.git
synced 2026-11-13 21:50:55 +01:00
Krzysztof kuhy Rudnicki
ffa5dad02a
The 250-line cap applies to prose too, and the reports were the worst
offenders -- ENUME's projectA.tex alone was 1,876 lines. Each is now a
preamble plus one \input{} per section, which is how a long LaTeX document is
normally organised; not one byte of prose was rewritten.
"The PDF is unchanged" is checked by a script rather than by eye, because
hashing the PDF cannot work: pdflatex stamps a /CreationDate and an /ID into
every build, so two runs of the SAME source already differ. tex_fingerprint.sh
compares what a reader sees instead -- page count plus a hash of the extracted
text -- and it is stable across rebuilds of untouched sources, which is the
property that makes it usable as a gate.
It earned its keep immediately. Both ECOTE reports quote an example LaTeX
document inside an lstlisting block, so \end{document} appears in the middle
of the file; splitting on the FIRST one stranded everything after it. Same
page count, different text, caught automatically. EOPSY lab3 exposed a second
bug: a \section{} title that runs onto the next line.
Result: 19 .tex over the cap -> 1. The survivor,
ELAC/.../03-building-nfa-...tex, is 418 lines of consecutive tikz figures
with no subsection to split on and needs a hand-placed boundary.
Verified: 29 splits across two passes (section, then subsection for the
pieces still over), every one reporting `unchanged` from
scripts/tex_fingerprint.sh --check.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0172dj34FDpao6wsix8ZuCzE
46 lines
1.3 KiB
TeX
46 lines
1.3 KiB
TeX
\documentclass[12pt]{article}
|
|
\usepackage[left=0.75in,right=0.75in,bottom=0.75in]{geometry}
|
|
\usepackage[polish]{babel}
|
|
\usepackage[utf8]{inputenc}
|
|
% T1 is required for Polish ogonek characters; without it pdflatex
|
|
% fails with "Command \k unavailable in encoding OT1".
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage{hyperref}
|
|
\usepackage{graphicx}
|
|
\usepackage{enumitem}
|
|
\usepackage{url}
|
|
\usepackage{listings}
|
|
\usepackage{booktabs}
|
|
\usepackage{multirow}
|
|
\usepackage{float}
|
|
\usepackage{titlesec}
|
|
\usepackage{xcolor}
|
|
\graphicspath{ {../images/} }
|
|
|
|
% Configure hyperlinks
|
|
\hypersetup{
|
|
colorlinks=true,
|
|
linkcolor=blue,
|
|
filecolor=magenta,
|
|
urlcolor=blue,
|
|
pdftitle={System e-Toll - Dokumentacja},
|
|
pdfauthor={},
|
|
pdfsubject={Wymagania funkcjonalne i niefunkcjonalne systemu e-Toll},
|
|
pdfkeywords={e-Toll, wymagania, architektura, system}
|
|
}
|
|
|
|
\title{System e-Toll \\
|
|
\large Dokumentacja systemu do zbierania danych na temat ruchu pojazdów\\po polskich drogach i naliczania należności za przejazdy}
|
|
\author{Dawid Budzyński, Filip Budzyński \\ Artur Romaniuk, Krzysztof Rudnicki, Jakub Woźniak}
|
|
\date{\today}
|
|
|
|
\begin{document}
|
|
|
|
\maketitle
|
|
|
|
\input{sections/01-wymagania-funkcjonalne}
|
|
\input{sections/02-wymagania-niefunkcjonalne}
|
|
\input{sections/03-decyzje-architektoniczne}
|
|
\input{sections/04-projekt-systemu-w-postaci-modelu-c4}
|
|
\end{document}
|