<html style="direction: ltr;">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body bidimailui-charset-is-forced="true" style="direction: ltr;">
<div class="moz-cite-prefix">On 12/14/20 12:02 PM, Sławomir Osipiuk
via Unicode wrote:<br>
</div>
<blockquote type="cite"
cite="mid:000c01d6d23a$ee6a5350$cb3ef9f0$@gmail.com">
<pre class="moz-quote-pre" wrap="">On Fri, Dec 11, 2020 at 1:13 PM Christian Kleineidam via Unicode <a class="moz-txt-link-rfc2396E" href="mailto:unicode@unicode.org"><unicode@unicode.org></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Create a new unicode character for begin/end italic formatting and begin/end bold formatting that works like the unicode character for the Right-to-Left switch.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
If you or someone else chooses to make a proposal, my own recommendation would be this:
- Assign a new character U+E0002 FORMAT TAG
- The syntax follows the specification for tagging (chapter 23.9)
- U+E0002 can be followed by any combination of U+E0062 (bold) U+E0065 (emphatic) U+E0069 (italic) and U+E0079 (underlined) to indicate a span of text with that formatting.
- U+E0002 U+E007F CANCEL TAG to cancel all formatting
- Any use of U+E0002 overrides previous formatting (i.e. a "bold" tag alone cancels a previous "italic" tag), so format nesting must be done by combining all desired formats into a single tag.
- This method should only be used in cases where formatting is required without a higher-level protocol
- This method should not be used in instances where loss of formatting would greatly alter the meaning of the text or render it incomprehensible.
- Strikethrough and super/subscript are deliberately omitted for the above reason.</pre>
</blockquote>
<p><br>
</p>
<p>This has probably been discussed before, but hey, if you're going
with something that mark-up-y, why not this?</p>
<p><br>
</p>
<p>All TAG symbols placed between a U+E003D TAG LESS-THAN SIGN and a
U+E003E TAG GREATER-THAN SIGN, inclusive, are to be treated as if
they were they corresponding ASCII characters, and run that
through an HTML renderer. I guess if you wanted you could
stipulate some reduced or restricted subset of HTML (maybe good
not to allow JS and all; just a thought), but why reinvent the
wheel of formatting markup? You've got something that works and
is quite powerful, and implementable without too much fuss using
existing invisible characters. Plain text is just another form of
HTML.<br>
</p>
<p><br>
</p>
<p>If this sounds disturbing and wrong to you, then other
pseudo-markup ideas probably should as well.</p>
<p><br>
</p>
<p>~mark<br>
</p>
<br>
</body>
</html>