<div id="gwp52beef1f"><div id="gwp52beef1fh"><div class="gwp52beef1fb" data-message-body="true"><div><br></div><div class="gwp52beef1f_nh_extra"><p>Dnia 25 października 2025 08:29 Asmus Freytag via Unicode <unicode@corp.unicode.org> napisał(a):<br></p><blockquote class="gwp52beef1f_nh_quote gwp52beef1f_bd-l_base gwp52beef1f_bd-c_primary.50 gwp52beef1f_pl_2 gwp52beef1f_m_0"><div id="gwp52beef1f_gwpcee74020"><div id="gwp52beef1f_gwpcee74020h"><div data-message-body="true" class="gwp52beef1f_gwpcee74020b"><p>Again, the identity of the Unicode character is giving by
encoding the intended mappings. If Unicode decides to map the same
character to similar characters on different platforms, that is
not a problem, as long as implementers know that the intent is to
use a platform-specific rendering (and not assume that there is
only one possible rendering per character).<br></p><p>If you feel that the guidance available to implementers in the
text of the standard or in an annotation of the nameslist is not
sufficent, then the remedy would be to ask for the explanation to
be updated. We are unfortunately locked in as far as character
names are concerned, but we can add a note (best in the text of
the standard) that explains that emulators for some systems will
need an adjusted design so a sequence or other arrangement of
these characters looks correct.<br></p></div></div></div></blockquote></div><div>Indeed the character names cannot be changed due to stability policies. An explanation note has been provided for U+1FB81 that claims "The lines corresponding to 3 and 5 are not
actually block elements, but can show any horizontally
repeating pattern", but still implicitly enforces 1÷8 blocks for top and bottom. However, this doesn't address other cases such as the PETSCII C64 variation. And if 1FB70—1FB81 1FBB5—1FBB8 1FBBC were all noted to no longer require exact 1÷8 blocks, that would also not remedy the issue because it would introduce an inconsistency with the existing 1÷8 or 7÷8 block characters 2581 2589 258F 2594—2595, which already have established compatibility precedents that require the exact fraction, but are also used in the Unicode 13.0 mapping to PETSCII and Apple II character sets despite those platforms using varying thickness (consistent with light box drawings, except for the 1÷8 top and bottom blocks in C64, where the 1÷4 top and bottom blocks are made consistent instead).<br></div></div></div></div><div><br></div>