<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Ugh, sorry. I knew they looked familiar from a Unicode
standpoint, but I checked the pipeline and they weren't there.
Should have googled for them in a Unicode context.</p>
<p>The branch symbol and the row- and column-number characters
should be encoded. They seem to be quite popular. The neatocool
path separators are questionable. I was reminded of the Powerline
symbols upon coming across <a class="moz-txt-link-freetext" href="https://starship.rs/">https://starship.rs/</a>, a feature-heavy
prompt-setting program for various command shells, which uses the
branch symbol by default.
<a class="moz-txt-link-freetext" href="https://awesomeopensource.com/projects/powerline/theme">https://awesomeopensource.com/projects/powerline/theme</a> lists
eighteen projects using or involving the Powerline symbols. This
really shouldn't be an issue. Is it odd for the Script Ad-Hoc to
recommend characters but the UTC not to pick them up (without
saying why)? Seems strange to me. And then "round 2" proposal
was dropped and not added to the register? Also odd. Anyway,
like I said, they seem to be used heavily by a lot of projects.
The SAH's points about using the existing LOCK character and not
encoding the triangles are reasonable, at least at this point.
But the branch symbol has become very common.</p>
<p>~mark<br>
</p>
<div class="moz-cite-prefix">On 10/11/21 19:16, Rebecca Bettencourt
via Unicode wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH=y87bAzZyA4t6NOxhQfgiifW1FYMraCDDH=DnDxNGFyEvfmw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">As you (Mark) discovered, the name originates
from the piece of software which first used these
characters, called Powerline. It's a plugin for vim, tmux,
bash, i3, and several other environments that adds a fancy
status line to the terminal.
<div><br>
</div>
<div>The characters have been proposed before, in document
L2/19-068R2. The SAH recommended encoding three of them
(the branch symbol and the row and column number symbols)
but the UTC took no action. I vaguely recall a
recommendation (from the SAH?) for the author, Renzhi Li,
to contact the "Terminals Working Group" (Doug Ewell, me,
and a few other individuals) to work out integrating them
into a "round 2" Symbols for Legacy Computing proposal. We
were never contacted by the author but we integrated them
into a "round 2" proposal anyway, with the suggestion to
use the same code points as were recommended by the SAH.</div>
<div><br>
</div>
<div>That "round 2" proposal was brought to the UTC but for
some reason was never added to the document register. We
had an hour-long meeting in which the UTC reviewed it and
had several concerns that were not resolved within
that hour. The proposal has not progressed further since
then.</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"><br>
-- Rebecca Bettencourt</div>
</div>
</div>
<div dir="ltr" class="gmail_signature"><br>
</div>
</div>
</div>
</div>
</blockquote>
</body>
</html>