https://sourceforge.net/p/gnuplot/bugs/2838/2025-11-22T16:53:34.391000ZRecent changes to 2838: Windows: 6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console2025-11-22T16:53:34.391000Z2025-11-22T16:53:34.391000ZEthan Merritthttps://sourceforge.net/u/sfeam/https://sourceforge.netf716a839111910d2efaf25ecd7fde621e6dbbec8

<div class="markdown_content"><ul> <li><strong>summary</strong>: 6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console --&gt; Windows: 6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console</li> <li><strong>Group</strong>: --&gt; </li> <li><strong>Priority</strong>: --&gt; </li> </ul></div>

2025-11-22T14:43:42.372000Z2025-11-22T14:43:42.372000ZIlya Zakharevichhttps://sourceforge.net/u/ilya-z/https://sourceforge.net212ce7eec80e3c92dce6c65a5007c2d2aa746f74

<div class="markdown_content"><p>Just in case — for people who never saw it before: the support of these chars¹⁾ is backwards compatible — they take <strong>2</strong> UTF-8 surrogates to encode, and take the “<strong>2</strong> cells worth” of the screen real estate to be shown. So the <code>readline</code> code does not need to be changed.²⁾</p> <blockquote> <p>¹⁾ … and of combining marks — but those “do not always work”; I could find neither rhyme or reason with combining marks refusing to be placed correctly time to time!</p> <p>²⁾ Hmm, maybe I’m too optimistic: one needs to be careful to not split those for partial display of the too-long lines! But <code>gnuplot</code>⸣s readline does not seem to support this intelligently anyway…</p> </blockquote></div>

2025-11-22T14:32:22.459000Z2025-11-22T14:32:22.459000ZIlya Zakharevichhttps://sourceforge.net/u/ilya-z/https://sourceforge.neta5c65b961c6e6a4e0acf86f0e442823570816cf8

<div class="markdown_content"><p>Composing another bug report today, I found that the CLI of <code>gnuplot</code> with <code>set encoding utf8</code> would ruin the plane-1 Unicode char in <code>☺😊</code> — when one tries to input these from keyboard (my layouts — and fonts — allow this. As well as “much more” — to put it mildly).</p> <p>Instead, <code>☺��</code> is shown. The code to replace the UTF-16 surrogates by <code>�</code> can be safely disabled now (at least when the surrogates come in correct pairs).</p> <p>Thanks,<br/> Ilya</p></div>

2025-11-22T14:32:22.459000Z2025-11-22T14:32:22.459000ZIlya Zakharevichhttps://sourceforge.net/u/ilya-z/https://sourceforge.netea2425cfcf59d05c9c3fce641ee3b872ef1f16f1

<div class="markdown_content"><p>Ticket 2838 has been modified: Windows: 6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console<br/> Edited By: Ethan Merritt (sfeam)<br/> Summary updated: '6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console' =&gt; 'Windows: 6.0.3: The obfuscation of planes-1,2,3 Unicode characters is not needed anymore in Windows 11⸣s console'</p></div>