[Standards] Council Minutes 2020-05-27

Tedd Sterr teddsterr at outlook.com
Tue Jun 2 19:52:15 UTC 2020

It probably is the best unicode charater to use for this purpose; I have doubts over whether this is a good thing to enable in the first place.

First you realise joiners aren't classified as whitespace, so then you have to prepend it instead, but that would need special handling, and then they're not always rendered correctly because some text renderers handle unicode badly (I have had similar issues with these kinds of things in the past, specifically ZWSP), then you find …

It just feels dirtier by the minute.

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

On Tue, Jun 2, 2020, at 15:14, Tedd Sterr wrote:
>  At first glance this looks like a cute solution, but it starts to
>  resemble a dirty hack the longer you look at it.

How so? Semantically this seems like the sort of thing joiners are for.
Eg. this is similar to the mechanism for breaking up combining emojis,
similar to breaking up letters in joined texts, etc. we're just breaking
up the styling directive from the text it would otherwise style.

>  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.

In general I feel the same way, but others said the all or nothing
approach was confusing and I do see the appeal of wanting a bold button
on a toolbar to work without breaking the rest of the text too. I could
go either way, but if we do want to unstyle individual blocks and spans,
this seems like a simple convenient way to do it.

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

More information about the Standards mailing list