A last missing link for interoperable representation

Tex via Unicode unicode at unicode.org
Mon Jan 14 16:08:23 CST 2019



I agree 100%. Asking where is the harm was an actual question intended to surface problems. It wasn’t rhetoric for saying there is no harm.


Also, it may not be obvious to social media, messaging platforms, that there is a possibility of a solution. Often when a problem exists for a long time, it fades into unconsciousness. The pain is accepted as that is the way it is and has to be.

It becomes part of the culture. Asking if there is a pain and whether a solution would be welcomed is consciousness raising.


I agree about leading standardization. I thought some legitimate needs were raised. The questions were designed to quantify the use case as well as the potential damage.


I didn’t think anyone was recommending more math abuse. I thought it was raised as an example of people resorting to them as a solution for a need. Of course they are also an example of playful experimentation.



Regarding messaging platforms, although twitter is one example in the social media space, today there are many business, commercial, and other applications that embed messaging capabilities for their communities and for servicing customers.

I wouldn’t dismiss the need just based on twitter’s assessment or on the idea that social media is just for casual or “fun” use. Clarity of communications can be significant for many organizations. Having the proposed capabilities in plain text rather than requiring all of the overhead of a more rich text solution could be a big win for these apps.





From: Unicode [mailto:unicode-bounces at unicode.org] On Behalf Of Asmus Freytag via Unicode
Sent: Monday, January 14, 2019 1:21 PM
To: unicode at unicode.org
Subject: Re: A last missing link for interoperable representation


On 1/14/2019 2:08 AM, Tex via Unicode wrote:

Perhaps the question should be put to twitter, messaging apps, text-to-voice vendors, and others whether it will be useful or not.

If the discussion continues I would like to see more of a cost/benefit analysis. Where is the harm? What will the benefit to user communities be?

The "it does no harm" is never an argument "for" making a change. It's something of a necessary, but not a sufficient condition, in other words.

More to the point, if there were platforms (like social media) that felt an urgent need to support styling without a markup language, and could articulate that need in terms of a proposal, then we would have something to discuss. (We might engage them in a discussion of the advisability of supporting "markdown", for example).

Short of that, I'm extremely leery of "leading" standardization; that is, encoding things that "might" be used.

As for the abuse of math alphabetics. That's happening whether we like it or not, but at this point represents playful experimentation by the exuberant fringe of Unicode users and certainly doesn't need any additional extensions. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20190114/f6b63c53/attachment.html>

More information about the Unicode mailing list