gpl/kindle2latex
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update readme.

Browse Source
This commit is contained in:
deeaitch
2026-02-28 22:20:44 -05:00
parent 6a003d5df4
commit 3ef56d2c52
1 changed files with 2 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -7,7 +7,7 @@ The tool parses Kindle highlights and groups them by book title, producing a LaT
* `\section{}` — per book * `\section{}` — per book
* `\subsection{}` — per highlight (metadata line) * `\subsection{}` — per highlight (metadata line)
* Highlight text — inserted as plain LaTeX content * Highlight text — inserted as plain LaTeX content
* ` \subsubsection{notes}` — placeholder for future comments * `\subsubsection{notes};` — placeholder for future comments
--- ---
@@ -83,7 +83,7 @@ Generated LaTeX structure:
\subsection{- Your Highlight on Location 123-125 | Added on ...} \subsection{- Your Highlight on Location 123-125 | Added on ...}
Highlighted text line 1 Highlighted text line 1
Highlighted text line 2 Highlighted text line 2
\subsubsection{notes}; \subsubsection{notes}
``` ```
Highlights are grouped by book title. Highlights are grouped by book title.
@@ -133,11 +133,3 @@ This repository intentionally keeps two different parsing styles:
* The TypeFactory version demonstrates a clean, extensible runtime pipeline. * The TypeFactory version demonstrates a clean, extensible runtime pipeline.
The goal is architectural exploration and comparison, not just solving the parsing task. The goal is architectural exploration and comparison, not just solving the parsing task.
---
If you want, I can also add:
* A small diagram of the parsing stages
* A section comparing performance characteristics
* Or a short "When to choose FSM vs Factory" guideline for future reuse in your blueprints repository