Le samedi 14 octobre 2017, 18:26:01 CEST Dave Cridland a écrit : > As an example, Goffi has repeatedly and eloquently stated that Markdown > won't produce a stable rendering of an input document, and therefore is > totally useless for, for example, the blog-style use he puts XHTML-IM to. > In fact, XHTML-IM itself is actually too limited for his case - he needs to > extend it.
The arguments are valid for instant messaging too, for blogging the case is already solved as the only implementations I know already use XHTML (but a new XEP to detail this and the security consideration would be nice indeed). So far nobody has objected or answered my points, so I don't see how it would be sane to go with any Markdown flavour (even if it's the fashion, we are talking about long term future proof specifications). So if there is a consensus to use an alternative to XHTML-IM (is there?), why we don't follow my proposal to have a period to propose syntaxes on a wiki page and show use cases, to finally being able to choose one which really fit our needs? This doesn't have to be months, it can be just 2 weeks. I really have the feeling that people are proposing Markdown because hey it's used on Github and Slack (with different flavours) and my client already implement it (my own client already implement it, and it's the default syntax for those saying I don't like it). But when arguments are exposed showing how it is a bad thing, nobody answer and people keep saying "hey let's just use Markdown". This really doesn't seems reasonable. And to be honest, I'm not the only one proposing alternatives, Creole has been mentionned, as well as XML based syntax, or other proposition, but that just seems ignored. Goffi _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
