# md.too - Release Notes ## Build 260527 - 2026-05-27 A feature build. Markdown that wraps at 80 columns renders correctly now, exported PDFs gained syntax coloring and table shading, and you can flip any document to its raw text. ### New - **View the raw text of any document.** A new button in the toolbar (and in the Quick Look preview) flips between the rendered Markdown and the plain UTF-8 source. The source view is read-only but fully selectable, so you can copy exact text out of a document without the renderer reflowing it. It sits to the left of the theme button; in Quick Look it is in the top-right overlay. - **Code blocks are syntax-colored in exported PDFs.** Fenced code (` ```swift `, ` ```python `, and the rest) now carries the same keyword / string / comment / type colors in the exported and shared PDF that it has on screen. Previously PDF code was a single flat color. ### Fixed - **Hand-wrapped lists and block quotes render correctly.** If you wrap your Markdown at ~80 columns, a list item whose text continued onto the next line - or a sub-bullet indented under it - used to render as a gray code block. Lists and quotes now follow CommonMark's container model, so wrapped continuation lines and nested items stay part of the list. This is the change most likely to affect documents you already have, and it should only make them look more correct. ### Also - **Tables in exported PDFs get subtle zebra striping** (alternating row shading) so wide tables are easier to follow on paper. - **The theme button moved to the trailing (far-right) end of the toolbar**, the same corner it already occupies in the Quick Look overlay, so it is in the same place everywhere. ### What stayed the same on purpose The renderer's output for documents that already rendered correctly, the syntax highlighter's colors, the read-only nature of the app (md.too never writes to your `.md` files - the new text view is view-only too), and zero third-party dependencies. ### What to test - A `.md` file you hand-wrap at 80 columns with multi-line list items or nested bullets - confirm it renders as a list, not a code block. - Export a document with fenced code to PDF; confirm the code is colored and matches the screen. - Toggle the source view in the app and in a Quick Look preview; confirm the text is selectable and copy/paste yields clean plain text. - Anything that renders visibly worse here than on github.com for the same source. - PDF export results that look different from what's on screen (font, spacing, missing images, table shading). ### Known rough edges - The first `.md` file with many remote images may take a moment to fully paint while inline fetches complete. - Very wide tables may scroll horizontally; the layout is correct but visually busy. - On-screen tables do not yet have the zebra striping that the PDF export does. - Display math `$$E = mc^2$$` uses a small LaTeX subset. Full LaTeX is intentionally out of scope; complex equations may not render the way a TeX engine would. ### Where to send feedback GitHub Issues: https://github.com/leok7v/md.too/issues GitHub Discussions: https://github.com/leok7v/md.too/discussions Or the TestFlight feedback button. Screenshots help; attaching the source `.md` file helps more. Thank you for testing.

This is a maintenance build. No new features. If everything keeps working the way it did, that's the expected outcome. The window no longer briefly freezes when another editor saves over the file you have open. If you keep md.too open on a README while you git pull, or while you save the same file from VS Code or Vim, the live re-render used to pause the UI for a fraction of a second during the external write. That pause is gone. On a fast SSD with a small file you probably never noticed it; on a network share or while another editor was doing an atomic rename, you might have. Image loading on iOS/iPad and in Quick Look previews is slightly more efficient. When you scroll past an image fast, or switch documents while images are still loading, the app stops the in-flight network request immediately instead of letting it run one extra round. You won't see this directly. Battery may notice in the long run.