This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Le Heux
aleheux at kobo.com
Fri Mar 15 23:11:39 CET 2013
Hi, >>It was just one example. Another would be ripe-566, which has a couple >> of tables. Sure, you can create an ASCII art tables, but doing so and at >> the same time everything below 72 characters of width might not be >> easiest thing in the world. A future document might want to include some >> other figures or other external content which cannot be (easily) >> represented in plain text. > >The various TeX flavors can generate PDF/A. I understand that this >would add complexity for people who need to create PDFs. Which may be >a benefit overall as this would result in a stronger incentive to use >plain text. All this while still allowing easily diffed collaboration >on text files in all cases. *if* plain text becomes the authoritative format, the RIPE NCC can then use whatever tools to create whatever formats of policy documents that they deem useful. No need to get dirty and bring TeX into the discussion ;) Alex Le Heux Kobo Inc
- Previous message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
- Next message (by thread): [ncc-services-wg] Pre-PDP discussion: "All RIPE documents should be plain text"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]