Talk:UniCode
Table organisation
I think it's a bad idea to include rows for which no meaning as an instruction has been assigned; not only does it clutter the table for readers, but it makes the page harder to edit, since there's a lot of rows to skip through.
Additionally, splitting it into transcluded subpages is pointless; if a page is too long to edit comfortably, then it'll be too long for the server to render and browsers to view comfortably, and so if any splitting should be done, then it should be accomplished via links from a central page, rather than transclusion. However, I don't think that should be a problem for quite a while; the page currently contains 510 codepoints, and is at a fairly reasonable size. If the codepoints without an assigned meaning are omitted, then it should remain at an acceptable size for quite a while before requiring splitting, even if new instructions are assigned rapidly.
Therefore, since a single page with only the codepoints that have been assigned a meaning is more convenient for both readers and editors, I suggest the existing subpages are substituted into the main article, and the rows without an assigned meaning be removed. Splitting into multiple pages can be done once the page becomes large enough to require it. Does anyone have any objections to this? —ehird 04:05, 22 April 2012 (UTC)
- This seems like a good idea, and I support it, but I suspect NSQX will manage to mess it up somehow. —Maharba 05:45, 22 April 2012 (UTC)
- Seconded. --Ørjan 15:03, 22 April 2012 (UTC)