Content deleted Content added
Drmccreedy (talk | contribs) →Existing charts: new section |
BabelStone (talk | contribs) →Comments: add my replies inline |
||
Line 42:
===Comments===
* I'm not convinced the "Notes" section at the bottom is worth the space it takes up, and I only added it as a proof-of-concept gesture to mimic existing layout convention. A collapsible (show/hide, just like the section above) section at the bottom with an additional list/table of character info (one per line) would certainly be feasible and only require a few more lines of code. Its hugeness of screen space would be the primary concern, because its expansion would displace other page content possibly including wrapped text or floating images (unlike navboxes, which occupy 100% width at the very bottom).
::We should just give first and last rows for blocks with character names derived from code points (CJK, Tangut, Nushu, ...), so the largest block is Hangul Syllables with 11,184 code points, which I agree is too long for this approach. But the next biggest blocks are Yi Syllables (1,168), Egyptian Hieroglyphs (1,072), Mathematical Alphanumeric Symbols (1,024), and Cuneiform (1,024), which I think should be acceptable if the names list is initially hidden. I don't see that displacement of other text and images would be an issue, especially as the code charts are mostly only used in the corresponding Unicode Block name articles. [[User:BabelStone|BabelStone]] ([[User talk:BabelStone|talk]]) 11:33, 10 September 2019 (UTC)
* One intuitive solution would be to mimic typical charmap program behavior by using a Javascript click handler on each character cell that populates the footer area (of about the same size as the "Notes" section, maybe slightly smaller) with the cursor-selectable name of the last clicked-upon codepoint, plus its <code>&escapecode;</code> and any additional info we care to pull from [[Module:Unicode data]] (replacing any previous content). I could whip up a demo for that in the next few days. I just worry that it might be [[WP:CLICKHERE|too interactive]] to be widely accepted.
::Nice idea but I am also concerned that turning Wikipedia into an app is a step too far. I'd like to see a prototype of it though. [[User:BabelStone|BabelStone]] ([[User talk:BabelStone|talk]]) 11:33, 10 September 2019 (UTC)
* A third approach might be to render the entire list (of names and whatnot) in a vertically scrollable footer panel containing "section" links, such that clicking on the character cell would cause the footer to scroll to and highlight (similar behavior to reflist anchors) the appropriate line. This might be [[WP:SCROLL|even less popular]].
::I think this is the best solution, regardless of [[WP:SCROLL]]. Only 50 blocks with non-algorithmic character names have more than 128 code points, so if we make the scroll window 128 rows only the 50 largest blocks will be affected. [[User:BabelStone|BabelStone]] ([[User talk:BabelStone|talk]]) 11:33, 10 September 2019 (UTC)
* On the other hand, some philosophies may have changed over the years. I mean, we do have [[:mw:Help:Extension:Kartographer|interactive scrolling maps that pop up in a fullscreen div]] now (see [[RM 2222|example]]).
* I haven't formed any opinion yet on how to handle combining character positioning, other than "oh god, I hope it's something other than <code>&nbsp;</code>" lol.
:Personally I prefer NBSP as the base for combining characters as dotted circle (which we currently use) often interferes with the character. [[User:BabelStone|BabelStone]] ([[User talk:BabelStone|talk]]) 11:33, 10 September 2019 (UTC)
―[[special:contributions/cobaltcigs|cobaltcigs]] 17:55, 9 September 2019 (UTC)
| |||