Stream: committers
Topic: Markdown Change
Grahame Grieve (Feb 19 2018 at 02:29):
@all The markdown format is about to change for R4. I'll be changing the markdown processor to GFM for the main build, and for all R4 implementation guides. R2 and R3 implementation guides will still use the old markdown format. note that what will drive the selection of syntax in the IG publisher is the stated version in the ig.json file
In terms of what actually changes, I haven't found any published comparison of the syntaxes. Weird. But it looks like nothing in the limited markdown we've used in the specs (mainly links and lists) changes. The custom [[[link]]] format doesn't change.
I've checked most of the main build. Doing this threw up one difficult issue, for which I apologise. When excel is looking for line breaks in a cell, it looks for the characters " " in the xml, not \n. The java xml library reads " " and converts them to \n when saving - hence, in spreadsheets edited since the day before the NOLA meeting, end lines have been been lost in markdown, and I can't recover them. I've recovered them for all the spreadsheets not edited in that time.
Grahame Grieve (Feb 19 2018 at 02:32):
Grahame Grieve (Feb 19 2018 at 02:33):
that's what the characters " " is supposed to contain - just testing zulip
Grahame Grieve (Feb 19 2018 at 03:52):
Apologies for the sweeping changes to all the spreadsheets. Nailing down the markdown/excel bug... I should've tested a little more before committing. I think I have it right now
Eric Haas (Feb 19 2018 at 17:23):
@Grahame Grieve What is the bottom line for committers do we need to go through the comments and description and update the text to replace line breaks with ?
Grahame Grieve (Feb 19 2018 at 19:37):
no I think I found and fixed them all. The bottom line is: be alert for broken stuff in the markdown as you review
Last updated: Apr 12 2022 at 19:14 UTC
