model-writtenrun 9631 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
Nov 2018 - Mar 2019 · 15 entries
- Jürgen Purtz opened the thread with a page-layout diagram, documentation-build changes, and a proposed SVG workflow, reporting successful HTML, PDF, and EPUB output but an unresolved single-file HTML problem in #1.
- Bruce Momjian warned that maintaining native files from multiple editors could lose changes and preferred standardizing on Inkscape in #3, while Andres Freund requested maintainable workflow documentation in #7 and Magnus Hagander advocated using SVG directly in browsers in #9.
- Jürgen proceeded with optional tool-specific sources plus mandatory portable SVG output in #13, published the workflow wiki in #15, and supplied page-layout, GIN, and dump/restore diagrams in #16.
- After documenting the difficulties of embedding SVG through DocBook 4 validation in #18, Jürgen posted Alexander Lakhin's stylesheet solution in #19 and incorporated it into the complete graphics patch in #25.
- Tatsuo Ishii identified missing figure numbering and trailing whitespace in #27; Jürgen responded with figure markup, index entries, and lists of figures, tables, and examples in #31.
- Peter Eisentraut's reviews in #32 and #34 identified incorrect build dependencies, naming issues, unsuitable images in man-page sources, and unnecessary figure-list customization; revisions through #35 corrected the dependencies and names, moved the dump diagram into the backup chapter, and deferred the lists.
- At Peter's request in #36, Jürgen added an in-tree README and documentation-authoring guidance in #37 explaining how tool-specific and optimized SVG files should be maintained together.
- Peter's export experiment in #38 exposed that the checked-in optimized SVG also contained manual edits, which Jürgen explained in #39; after Bruce's simplification proposal in #40 and Tom Lane's concerns about unreadable diffs in #41, Jürgen dropped the manual optimization step in #43.
- Peter supplied a major rewrite in #44, generating the GIN diagram with Graphviz and the page-layout diagram with Ditaa so contributors could edit logical structures instead of coordinates, while retaining SVG output and improving PDF scaling.
- The rewrite in #44 left out the dump/restore diagram because Peter did not find it sufficiently useful, and consequently also omitted the associated backup-chapter rewrite and the earlier Inkscape workflow documentation.
- Tom initially proposed distributing generated SVG only in tarballs in #45, then stressed that all contributors must be able to build documentation in #48; Peter ultimately committed the generated images as well, avoiding new image-generation requirements for ordinary documentation builds, as announced in #50.
- Commit ea55aec0a9 landed the two diagrams from #44 with unchanged image content, an images directory and separate generation Makefile, workflow instructions, HTML Help support, and restored single-file HTML embedding, crediting both Jürgen and Peter.
- After landing, Tatsuo renewed the request for figure indexes in #52, and Jürgen deferred lists of figures, tables, and examples to a separate proposal in #54; Peter welcomed a few additional diagrams using the accepted tools in #57.
- Tom reported a buildfarm failure in #53; Peter pointed to a Java accessibility configuration workaround in #55, and Magnus confirmed that applying it restored the build in #59, while whether to document the apparent Debian/Ubuntu packaging issue remained open in #61.
- Jürgen revived the uncommitted dump diagram with Inkscape grouping and connectors in #60, but Peter opposed adding Inkscape before exhausting alternatives in #62, and Alvaro Herrera closed the thread with a comparable Ditaa example in #64, leaving that diagram and broader tool support unresolved.