dss-x — archive

Fwd: [dss-x] Markdown code section fixed and rendered as PDF

From: Andreas Kuehne
To: [email protected]
Date: Sat, 24 Nov 2018 18:00:00 -0000

Hi all, Detlef raised the question of a MarkDown template for OASIS specifications. Maybe that's just a trained expectation ... the RFC did a good job even without a shiny logo. But if it boosts the acceptance of our stuff, I'll go with any shiny layout! Are there OASIS official standards out in a MarkDown-only style? Greetings, Andreas -------- Weitergeleitete Nachricht -------- Betreff: AW: [dss-x] Markdown code section fixed and rendered as PDF Datum: Thu, 22 Nov 2018 07:17:42 +0100 Von: [email protected] An: 'Andreas Kuehne' <[email protected]> Hi, yes, the OASIS Template needs some more polishing to produce something, which in the end looks like an OASIS Standard. Could OASIS help here? BR, Detlef ----- UrsprÃngliche Nachricht ----- Von: [email protected] <[email protected]> Im Auftrag von Andreas Kuehne Gesendet: Mittwoch, 21. November 2018 22:53 An: dss-x <[email protected]> Betreff: [dss-x] Markdown code section fixed and rendered as PDF Hi, see attached the PDF output of the markdown version. The 'single-line-code' flaw pointed out by Ernst Jan was an artifact of the Word->Markdown conversion.Fixed now. I discussed the pro and cons of MarkDown and Word with Stefan. My major aspects are - November nearly over and no version ready - Word is an capricious beast - MarkDown allows reuse of content in Swagger Do you see other relevant topics? Greetings, Andreas Attachment: smime.p7s Description: S/MIME Cryptographic Signature