<div dir="auto">Also, the semantics of the half-sharp, reversed flat, and slashed flat gets a little more complicated when you take Turkishmusic into account. Probably best to encode new characters (and a proposal was submitted fairly recently) even if it means leaving some detritus in the Standard. It wouldn’t be the first time.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 3, 2024 at 9:17 AM Doug Ewell via Unicode <<a href="mailto:unicode@corp.unicode.org">unicode@corp.unicode.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div dir="auto">I personally support Kirk Miller's proposal to add the more commonly used symbols as separate characters, rather <span>than complicating the encoding by adding variation selectors to change the glyph to something quite different.</span></div>
<div dir="auto"><span><br>
</span></div>
<div dir="auto"><span>We don't always realize it, but ordinary users generally don't know anything about variation selectors.</span></div>
<div dir="auto"><span><br>
</span></div>
<div dir="auto"><span>—Doug</span></div>
<div dir="auto"><span><br>
</span></div>
<div><br>
</div>
<div id="m_-6712766082136929672ms-outlook-mobile-signature" dir="auto">Sent via the Samsung Galaxy S22 Ultra 5G, an AT&T 5G smartphone<br>
Get <a href="https://aka.ms/AAb9ysg" target="_blank">Outlook for Android</a></div>
<hr style="display:inline-block;width:98%">
<div id="m_-6712766082136929672divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Unicode <<a href="mailto:unicode-bounces@corp.unicode.org" target="_blank">unicode-bounces@corp.unicode.org</a>> on behalf of Marius Spix via Unicode <<a href="mailto:unicode@corp.unicode.org" target="_blank">unicode@corp.unicode.org</a>><br>
<b>Sent:</b> Wednesday, January 3, 2024 9:09:14 AM<br>
<b>To:</b> <a href="mailto:unicode@corp.unicode.org" target="_blank">unicode@corp.unicode.org</a> <<a href="mailto:unicode@corp.unicode.org" target="_blank">unicode@corp.unicode.org</a>><br>
<b>Subject:</b> Reference glyphs of musical accidentals quarter sharp and quarter flat</font>
<div> </div>
</div></div><div>
<div><font size="2"><span style="font-size:11pt">
<div>Hi,<br>
<br>
I just noted that the reference glyphs for<br>
<br>
U+1D132 MUSICAL SYMBOL QUARTER TONE SHARP<br>
<br>
and<br>
<br>
U+1D133 MUSICAL SYMBOL QUARTER TONE FLAT<br>
<br>
on the code chart are very unusual. In the standard notation, the<br>
quarter sharp is represented by U+266F with only one downstroke and the<br>
quarter flat by a mirrored version of U+266D MUSIC FLAT SIGN (or as a<br>
variant of U+266D with a stroke). Please find the attached image for<br>
reference.<br>
<br>
I had a look at the mailing list and there was already a suggestion by<br>
Johnny Farraj in 2015, by Markus Scherer in 2018 and by Gavin Jared Bala<br>
and Kirk Miller in 2023 (request L2/23-276). The letter also includes<br>
the currently missing characters for three-quarter sharp and<br>
three-quarter flat, two characters I also see an urgent need for.<br>
<br>
Howerver, in contrast to that request, I propose to unify two suggested<br>
characters with existing ones and change the reference glyph instead of<br>
encoding a new character instead.<br>
<br>
U+1D1ED MUSICAL SYMBOL REVERSED FLAT (requested) = U+1D133 MUSICAL<br>
SYMBOL QUARTER TONE FLAT (existing)<br>
U+1D1EB MUSICAL SYMBOL HALF SHARP (requested) = U+1D133 MUSICAL SYMBOL<br>
QUARTER TONE FLAT (existing)<br>
<br>
The stroked variant of the quarter flat (which does not appear in<br>
the proposal of Gavin Jared Bala and Kirk Miller, but can be found in<br>
several pieces) could be obtained by combining U+1D132 MUSICAL SYMBOL<br>
QUARTER TONE SHARP with a variation selector (e. g. U+FE00).<br>
<br>
What do you think?<br>
<br>
Best regards,<br>
<br>
Marius<br>
</div>
</span></font></div>
</div>
</blockquote></div></div>