BBS:      TELESC.NET.BR
Assunto:  Re: MARKDOWN kludge
De:       Rob Swindell
Data:     Mon, 2 Mar 2026 01:06:36 -0800
-----------------------------------------------------------
  Re: Re: MARKDOWN kludge
  By: Matthew Asham to Carlos Navarro on Sun Mar 01 2026 01:40 pm

 >
 > CN> My 2c: in case of something like that being implemented, could it be
 > CN> better to use a more general kludge, such as MARKUP?
 > CN> ^aMARKUP: Markdown 1.0
 > CN> That would allow for specifying other formats, like BBCode, Gemtext,
 > CN> etc.
 >
 > This makes more sense to me.
 >
 >
 > I've done up a second draft based on this this feedback.
 >
 >
 > 1. INTRODUCTION
 > ---------------
 >
 > This document defines the MARKUP kludge line for use in FidoNet-
 > compatible echomail and netmail messages. Its purpose is to indicate
 > that the body of a message is formatted using a named markup syntax,
 > allowing capable reader software to render the message with appropriate
 > formatting while remaining fully readable by legacy software that does
 > not support this kludge.
 >
 > Unlike a Markdown-specific kludge, MARKUP provides a general mechanism
 > for identifying the body format of a message. This allows the same
 > extension point to be used for Markdown, BBCode, Gemtext, and other
 > formats without requiring a new kludge definition for each syntax.
 >
 >
 > 2. DEFINITIONS
 > --------------
 >
 > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
 > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
 > document are to be interpreted as described in FTA-1006.
 >
 > "Kludge line": A line in a FidoNet message body beginning with the
 > ASCII SOH character (0x01), used to carry machine-readable metadata
 > not intended for direct display to the end user.
 >
 > "Markup syntax": A textual formatting language used within the visible
 > message body to express structure or presentation, such as Markdown,
 > BBCode, or Gemtext.
 >
 >
 > 3. THE MARKUP KLUDGE
 > --------------------
 >
 > 3.1 Syntax
 >
 > The MARKUP kludge line has the following syntax:
 >
 >     ^AMARKUP:  
 >
 > where ^A represents the ASCII SOH character (0x01),  is a
 > registered or otherwise well-known markup format identifier, and
 >  is a format version string meaningful within that format.
 >
 > Examples:
 >
 >     ^AMARKUP: Markdown 1.0
 >     ^AMARKUP: BBCode 1.0
 >     ^AMARKUP: Gemtext 1.0

There's the Synchronet-supported message markup format too:
https://wiki.synchro.net/ref:markup
-- 
Rob Swindell
FTSC Standing Member
--- SBBSecho 3.37-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

-----------------------------------------------------------
[Voltar]