<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I don’t see them in any of the G2 character sets in <div class=""><a href="https://www.etsi.org/deliver/etsi_en/300700_300799/300706/01.02.01_60/en_300706v010201p.pdf" class="">https://www.etsi.org/deliver/etsi_en/300700_300799/300706/01.02.01_60/en_300706v010201p.pdf</a></div><div class="">(ETSI EN 300 706 V1.2.1 (2003-04)
European Standard (Telecommunications series)
<b class="">Enhanced <u class="">Teletext</u> specification</b>).</div><div class=""><br class=""></div><div class="">/Kent K<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">1 apr. 2023 kl. 01:26 skrev Doug Ewell via Unicode <<a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a>>:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div class="">
<div dir="auto" class="">They are in at least the T.101-G2 set, used for teletext.</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">—Doug</div>
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class=""><br class="">
</div>
<div id="ms-outlook-mobile-signature" dir="auto" class="">
<div class=""><br class="">
</div>
Sent via the Samsung Galaxy S22 Ultra 5G, an AT&T 5G smartphone<br class="">
Get <a href="https://aka.ms/AAb9ysg" class="">Outlook for Android</a></div>
<hr style="display:inline-block;width:98%" tabindex="-1" class="">
<div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> Unicode <<a href="mailto:unicode-bounces@corp.unicode.org" class="">unicode-bounces@corp.unicode.org</a>> on behalf of Manuel Strehl via Unicode <<a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a>><br class="">
<b class="">Sent:</b> Friday, March 31, 2023 5:23:08 PM<br class="">
<b class="">To:</b> <a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a> <<a href="mailto:unicode@corp.unicode.org" class="">unicode@corp.unicode.org</a>><br class="">
<b class="">Subject:</b> Re: How do U+2571..U+2573 connect?</font>
<div class=""> </div>
</div>
<div class="BodyFragment"><font size="2" class=""><span style="font-size:11pt;" class="">
<div class="PlainText">Thanks for the answer! I almost thought that this was what’s going on.
<br class="">
From looking at the Wikipedia page, <br class="">
<a href="https://en.wikipedia.org/wiki/Box-drawing_character" class="">https://en.wikipedia.org/wiki/Box-drawing_character</a>, it seems that those
<br class="">
three were not part of any larger legacy encoding. (The curved corners <br class="">
come from Acorn Computers by the way, acording to that article.)<br class="">
<br class="">
This leaves me wondering, where those three characters come from at all.<br class="">
<br class="">
Manuel<br class="">
<br class="">
Am 01.04.23 um 01:06 schrieb Asmus Freytag via Unicode:<br class="">
> The easy answer is that these do not consist of a single set. For <br class="">
> example, the single-, double-line regular-stroke symbols and their <br class="">
> combinations, form a subset that is supported by the DOS code page <br class="">
> 437. Another common DOS code page (850) has only the single-line ones.<br class="">
><br class="">
> Neither set contains any element that terminates in the middle of the <br class="">
> cell.<br class="">
><br class="">
> Those, as well as the heavy stroke or mixed weight combinations are <br class="">
> presumably supported somewhere else, as are the curved corners. I <br class="">
> don't know off hand what the character sets are from which these were <br class="">
> derived, but again, I would not be surprised if they supported only a <br class="">
> subset.<br class="">
><br class="">
> The diagonals, therefore, are not necessarily from any of those <br class="">
> subsets, and therefore likely never intended to be used to provide <br class="">
> diagonal connections.<br class="">
><br class="">
> A./<br class="">
><br class="">
><br class="">
> On 3/31/2023 3:46 PM, Manuel Strehl via Unicode wrote:<br class="">
>> Hi,<br class="">
>><br class="">
>> if you look at the Box Drawing block, e.g., <br class="">
>> <a href="https://codepoints.net/box_drawing" class="">https://codepoints.net/box_drawing</a>, every character goes through the
<br class="">
>> middle of the edges of an imagined rectangle around the glyph. That <br class="">
>> is, apart from U+2571, U+2572 and U+2573, the diagonal lines. Those <br class="">
>> touch exclusively the corners of said rectangle.<br class="">
>><br class="">
>> I fail to imagine how these three characters could ever attach to any <br class="">
>> of the other characters in this block. Are they not meant to do that <br class="">
>> or am I missing a trick here?<br class="">
>><br class="">
>> Thanks for any pointers!<br class="">
>><br class="">
>> Cheers,<br class="">
>> Manuel<br class="">
>><br class="">
>> PS: This question was triggered by this reddit post: <br class="">
>> <a href="https://www.reddit.com/r/Unicode/comments/127y7dn/looking_for_box_drawing_characters/" class="">
https://www.reddit.com/r/Unicode/comments/127y7dn/looking_for_box_drawing_characters/</a><br class="">
><br class="">
><br class="">
<br class="">
</div>
</span></font></div>
</div>
</div></blockquote></div><br class=""></div></body></html>