Content deleted Content added
m Archiving 1 discussion(s) from Talk:Unicode) (bot |
m Archiving 1 discussion(s) from Talk:Unicode) (bot |
||
Line 200:
[[User:Peter M. Brown|Peter Brown]] ([[User talk:Peter M. Brown|talk]]) 19:06, 24 February 2019 (UTC)
== What does [[MOS:ALLCAPS]] require in [[Unicode#Architecture_and_terminology|Unicode § Architecture and terminology]]? ==
In full, the bullet point in [[MOS:ALLCAPS]] relevant to Unicode reads:
:The names of [[Unicode]] code points are conventionally given in small caps (tip: enter the name in all caps into the template {{tlx|sc2}}). Example: {{xt|the character <code>⁓</code> (U+2053, {{sc2|SWUNG DASH}})}}. This is only done when presenting tables of Unicode data, and when discussing code point names as such. Otherwise prefer unstyled, plain-English character names (whether they coincide with code point names or not): {{xt|the hyphen and the en dash}}, not {{!xt|the {{sc2|HYPHEN-MINUS}} and the {{sc2|EN DASH}}}}.
The Unicode article currently contains the text:
:For code points in the [[Basic Multilingual Plane]] (BMP), four digits are used (e.g., U+0058 for the character LATIN CAPITAL LETTER X)
This is contrary to MOS, as the discussion contains the all-caps text LATIN CAPITAL LETTER but does <u>not</u> present a table and is <u>not</u> about code point names as such but rather about a standard way of designating code points, one that involves hexadecimal digits.
I replaced this with text that does conform to MOS. [[User:LiliCharlie|LiliCharlie]] has reverted it, restoring the nonconforming code. Though the associated edit summary correctly quotes MOS:ALLCAPS as saying "The names of Unicode code points are conventionally given in small caps", the convention in question is provided by the Unicode Standard and the MOS spells out a different convention to be followed in Wikipedia articles. With some clearly-specified exceptions, we are forbidden to use code-point names in the manner prescribed by the Unicode Standard. Rather, we are instructed to use plain-English character names ''whether they coincide with code point names or not''. Editors are welcome to improve on the phrase I used, "the character 'X' in English and related languages", perhaps referring to the Latin ancestry of the character, but such emendations should still conform to the MOS.
[[User:Peter M. Brown|Peter Brown]] ([[User talk:Peter M. Brown|talk]]) 21:47, 24 February 2019 (UTC)
: That's clearly wrong, or at best confusing, since the hyphen-minus and the hyphen are two totally different things. In any case, we should not bring in plain English character names because we're not talking about plain English characters. If necessary, I'm fine with removing the names altogether; they're not needed for the example.--[[User:Prosfilaes|Prosfilaes]] ([[User talk:Prosfilaes|talk]]) 01:34, 25 February 2019 (UTC)
::Well, we can use plain English ''referring expressions'', can't we, even we don't call them "names"? And the reader would surely appreciate seeing glyphs to get some idea what we're talking about; these could be put in parentheses. How about the following?
:::For code points in the [[Basic Multilingual Plane]] (BMP), four digits are used, e.g. U+00F7 for the division sign (÷); for code points outside the BMP, five or six digits are used as required, e.g. U+13254 for the [[Egyptian hieroglyph]] designating a winding wall ( [[File:Hiero O4.png|text-bottom|15px]] ).
[[User:Peter M. Brown|Peter Brown]] ([[User talk:Peter M. Brown|talk]]) 19:49, 26 February 2019 (UTC)
|