Template talk:Unicode chart Halfwidth and Fullwidth Forms
 | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
Reverted note. It's useful but misplaced. It should be in one of the articles that includes that chart. Individual characters aren't footnoted and if they were, there would be hundreds of footnotes in the charts.
editThe following, unsigned comment was added to my user page. I've copied it here so any discussion could have a wider audience:
While I'm not dismissing your decision out of hand, on many pages individual characters are footnoted, if there's something special about them. Your argument that we'd have hundreds of footnotes is clearly a straw man.
A downside of trying to put the note in the specific Unicode block article is that the direct connection between the character and the note gets lost. I know from experience that this makes it harder to find information about a specific character.
But if you really think this footnote clutters up the Hangul article too much (and if you do, shouldn't the other two be removed also?) why not use some template magic that makes the footnote only appear on pages that ask for it?
Here's my reply:
There are four standard notes: version, grey/non-assigned, black/noncharacter, and deprecated. I'm aware of only four templates with custom note(s):
- The Emoji template includes two additional references, but it isn't a Unicode block.
- Hangul Jamo has two custom notes explaining green/white background highlighting.
- Miscellaneous Symbols has two custom notes about omitted and inherited characters, but only if the emoticons parm is passed (using template magic)
- Sutton SignWriting has a custom note of "U+1D84D, U+1D84F, U+1D851, U+1D85C, U+1D85E, U+1D8F6, U+1D904 shown with modifier U+1DA9B SW-F2".
None of the notes are anchored to an individual code point cell; they are all anchored to the chart title. I am strongly opposed to changing this convenstion.
I don't think notes about how a character is used belong in the 300+ code chart templates. I see this as a slippery slope that could lead to hundreds of notes. That said, I probably wouldn't have reverted the edit if the anchor had been on the title instead of the individual code point cell. I'm not sure if others would have though. I retain my position that an explaination of how HANGUL FILLER is used should appear in articles and not in the code chart template. DRMcCreedy (talk) 17:02, 9 December 2019 (UTC)
- Agreed that notes on individual characters do not belong in the template, but should be added as text in the appropriate article, in this case Halfwidth and Fullwidth Forms (Unicode block). However, the comment "It is meaningless in Unicode" is not appropriate and should be excluded or rewritten to explain exactly how it is meaningless in Unicode. BabelStone (talk) 17:10, 9 December 2019 (UTC)
I am not sure which code charts are made using templates or not, it doesn't matter to the reader, but your assertion that none of the charts contain notes on individual characters is patently false. There are plenty, see Code page 437#Character_set for just one example. Your slippery slope argument is clearly a straw man, nobody is suggesting to add notes to characters like the individual jamo for example, because one can already see what they are. But HWHF is a mystery character.
I don't see why the other notes are better just because they're linked from the title. If the HWHF had been linked from the title, it would it have been more acceptable, even though it would have been functionally worse? Of course not. I think if notes in character tables are unacceptable, the present two notes should go as well.
Your assertion that the statement that HWHF is meaningless in Unicode is inappropriate is false. The character is obviously meaningless in a Unicode context and if you're too dumb to see why just check the reference provided. And given that it is, that's an exceptional property for a character and it should be noted.
So... 1) Why must the present notes be on the character code templates and why can't they be in the relevant articles?
2) Why is the solution to make (some) notes in the character code template appear only in its main article unacceptable?
3) Would turning the HWHF table cell into a hyperlink that leads to an explanation be acceptable?
4) Why is neither of you replying productively? Why are you just concerned with removing important information and not thinking about actual solutions?
— Preceding unsigned comment added by 2a02:a455:1903:1:c4d6:4de4:7855:38b5 (talk)
Some remarks:
| “ | your assertion that none of the charts contain notes on individual characters is patently false. There are plenty, see Code page 437#Character_set for just one example. | ” |
The Unicode block charts, versus the charts of mappings of legacy encodings to Unicode, have different requirements and use a different system. Hence the notes on Code page 437 (OEM-US), noting where different Unicode mappings may be more appropriate in specialised contexts. Note that the actual charts of legacy encodings are not supplied as templates; they are formatted using templates, but the actual charts are defined in the articles themselves and only used in the one article.
(The charts for legacy encodings including them are currently limited to KS X 1001 § N-byte Hangul code; I suppose the EBCDIC version could be added somewhere.)
| “ | Your assertion that the statement that HWHF is meaningless in Unicode is inappropriate is false. The character is obviously meaningless in a Unicode context and if you're too dumb to see why just check the reference provided. And given that it is, that's an exceptional property for a character and it should be noted. | ” |
Apart from calling people "dumb" being not exactly good form here… the objection wasn't that it was incorrect as such (indeed it doesn't exhibit its KS C 5601 behaviour when included in a Unicode document), but rather that it doesn't really explain anything (i.e. that Unicode uses its own Hangul composition system, so the KS C 5601 system isn't used; modern Wansung combining sequences are expected to be mapped to precomposed characters in Unicode, and the filler just shows up as a space—much of which is indeed explained in that source).
| “ | Why must the present notes be on the character code templates and why can't they be in the relevant articles? | ” |
Basically, they're notes explaining the formatting of the chart itself, and the Unicode version for which the chart was produced. I'm not 100% sure why they're footnotes.
| “ | Would turning the HWHF table cell into a hyperlink that leads to an explanation be acceptable? | ” |
Well, that's what's (at least in theory) done for the several non-printing characters in General Punctuation (Unicode block), with nobody seeming to complain, so that would seem reasonable? The filler character's role in KS X 1001 (KS C 5601) is explained at KS X 1001 § Character set 0x24 / 0xA4 (row number 4, Hangul jamo), but a new section might be warranted. I'll probably add your reference there.