Disambiguation link notification for August 16
An automated process has detected that when you recently edited Macintosh Ukrainian encoding, you added a link pointing to the disambiguation page Ukrainian (check to confirm | fix with Dab solver).
(Opt-out instructions.) --DPL bot (talk) 09:18, 16 August 2018 (UTC)
Stop removing large portions of contents
Please stop removing large portions of contents as you did in the Xerox Character Code Standard article. We are Wikipedia and don't depend on projects like Wiktionary. I'm not sure what you were after, but in either case, please discuss such bold intended changes before on the article talk pages and don't carry them out unless there is consensus for them. --Matthiaspaul (talk) 09:24, 4 September 2018 (UTC)
- I see that you are also carrying out mass changes to other character set tables and the corresponding template framework. Please stop this immediately, there is no consensus for these changes. --Matthiaspaul (talk) 09:30, 4 September 2018 (UTC)
- As most of your edits don't have an edit summary could you please explain what you were after? --Matthiaspaul (talk) 09:44, 4 September 2018 (UTC)
- User:Spitzak was apparently trying to boldly redo the formatting and change the colouration to match Unicode character categories. i.e. L/P/S/M/Z/C (and had been editing the templates, reducing the number of colours etc accordingly). I couldn't come up with any point to counter this with (after all, Unicode character categories are, for all their flaws, an objective non-OR system), so I was trying to make things consistently use that scheme.
- While I was editing the template framework, that was mostly with the intention of trying to tidy it up after Spitzak. While I did add the kuten stuff, that had been included in most of the tables it was applicable to for some time already, outside the template call; I thought it would be tidier to support it in the templates themselves.
- As for XCCS, including a couple of kanji tables but not all of them feels slightly misleading (at best suggesting the rest of the mapping not to be known, and at worst suggesting that to be the encoding's entire kanji support), and whilst I could comparatively easily generate the full set and include them, that would increase the article length to many times what it is currently. Hence I was linking to where the full information was already available.
- Whilst it didn't have a lead byte table until I recently added it, JIS X 0208 had been pointing to Wiktionary for that purpose for almost 9 months now, KS X 1001 had been doing so for no short space of time and KPS 9566 had been doing so ever since its tables were added, and you're the first person to complain, so I (I thought) reasonably assumed people were happy with that. -- HarJIT (talk) 11:12, 4 September 2018 (UTC)
- Hi HarJIT, thanks for your reply.
- Can you point me to where Spitzak is boldly trying to redo the formatting, because Spitzak has been advised (by me) not to do it without community consensus.
- While the existing tables are not perfect, I would rather add more information (codes, colors, attributes) to them whereas Spitzak apparently wants sleak small tables with only the glyphs being shown for mobile devices - which would make it impossible to derive character mapping information and exceptions from the tables and therefore would render them meaningless for "serious" work.
- What exactly do you mean by "colouration to match Unicode character categories"? Given that most oode pages and character sets long pre-date the advent of Unicode, I'm not sure if applying Unicode categories to them makes sense. Our current system appears to be loosely based on ASCII character categorization, but with some extensions.
- --Matthiaspaul (talk) 18:53, 4 September 2018 (UTC)