Le samedi 14 octobre 2017, 16:57:09 CEST Denver Gingerich a écrit :
> On Sat, Oct 14, 2017 at 04:05:10PM +0200, Goffi wrote:
> > Markdown is a terrible choice because:
> >
> > 1) as its name state it's a writting syntax and not a publishing one.
> > There is not such thing as invalid Markdown (every text is valid
> > Markdown), but the result will differ according to rendering library
> > used.
> > Even original author says that it's not a publishing format ("HTML is a
> > publishing format; Markdown is a writing format." cf. https://
> > daringfireball.net/projects/markdown/syntax)
> >
> > 2) it's not specified and it's unlikely that it will be (and yes I know
> > about common Markdown and RFCs about the MIME type and the guidance on
> > Mardown).
> >
> > 3) there a dozen of flavours, more or less (in)compatibles
> >
> > 4) as stated by Jonas, it's really hard to extend without side results
> > (should I interpret ~bla bla~ as strikethrough? Yes my librarie is doing
> > it! Oh wait no, it's not an official syntax, there is not strikethrough
> > in Markdown…
> > https://daringfireball.net/linked/2015/11/05/markdown-strikethrough-slack
> > ).
> >
> > 5) it's limited (no color, no strikethourgh in classic syntax)
> >
> > 6) official syntax allow embedding HTML, so libraries may or may not
> > interpret <script> as HTML, ruining the whole purpose of "changing syntax
> > because it's better for security".
> >
> >
> > I've repeated this a couple of times in previous emails, and I haven't
> > seen
> > any of this point objected or answered.
>
> I suggested using Creole 1.0 instead of Markdown in
> https://mail.jabber.org/pipermail/standards/2017-October/033556.html - I
> know it doesn't have all the features you mention (ie. missing color), but
> I think it addresses many/most of your other points, especially 2) and 6).
> Is it insufficient in other ways?
yes I've seen, and why not. But this ask to inspect the thing deeply and to
have input from the community to see various use cases (for instance I've
mentioned the use of colors to send colored output of CLI commands, or for
unknown languages, those are niche use cases but still are to be taken into
account).
If we really go with a new syntax I think we should have transition period to
list the candidates (on the wiki for instance), to list the use cases, and to
select (or create) the best syntax we find. It's a choice which will have a
major impact for the whole XMPP community for years, so it needs a lot of
thinking IMHO.
To come back to the content type thing: the ability to use any syntax with a
MIME/Content type could be useful for something local to a client (I'm
thinking about drafts, but this would probably be more useful for blogs than
for instant messaging), but it is IMHO a bad way to go for publishing instant
messages.
Cheers
Goffi
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________
