[Standards] Council Minutes 2020-05-27

Tedd Sterr teddsterr at outlook.com
Tue Jun 2 19:14:39 UTC 2020

At first glance this looks like a cute solution, but it starts to resemble a dirty hack the longer you look at it.

You're hoping to add a neat little feature for little cost, but it's going to be additional unnecessary complexity in almost all cases. If you're aiming to keep 0393 small, neat, and clean then maybe this isn't a good way to go. I don't even see much realistic use for styling *this* but not *this* - messages are either fully styled or fully unstyled - don't over-complicate things.

From: Standards <standards-bounces at xmpp.org> on behalf of Sam Whited <sam at samwhited.com>
Sent: 02 June 2020 18:45
To: standards at xmpp.org <standards at xmpp.org>
Subject: Re: [Standards] Council Minutes 2020-05-27

Drat, you're right, I thought it was in category Z but it doesn't look
like it is.

Sticking it before the directive would work as well. Alternatively we
could expand the definition of what's not allowed immediately after a
thing that might be a styling directive to include category C as well as
category Z. It would make sense to me that they're not allowed either,
and it means word joiner can be used as written.

I have no particular preference either way, but if anyone else sees a
flaw with either solution that I'm missing let me know.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20200602/b446c560/attachment.html>

More information about the Standards mailing list