Jump to content

Template talk:Unicode chart C1 Controls and Latin-1 Supplement

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Common formatting is used by over 300 Unicode block templates and should be discussed before it is changed.

[edit]

Got insta-reverted with above comment.

Of course I didn't change all 300 blocks, this is an EXPERIMENT. I'm not going to change all 300 until there is agreement. Sorry but previous experience has shown that NO "discussion" will happen unless the changes are actually made. Prove me wrong by actually posting some "discussion" below this:

My altered version:

C1 Controls and Latin-1 Supplement[1]
Official Unicode Consortium code chart (PDF)
0 1 2 3 4 5 6 7 8 9 A B C D E F
U+008x PAD HOP BPH NBH IND NEL SSA ESA HTS HTJ VTS PLD PLU RI SS2 SS3
U+009x DCS PU1 PU2 STS CCH MW SPA EPA SOS SGC SCI CSI ST OSC PM APC
U+00Ax NBSP ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ SHY ® ¯
U+00Bx ° ± ² ³ ´ µ · ¸ ¹ º » ¼ ½ ¾ ¿
U+00Cx À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï
U+00Dx Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß
U+00Ex à á â ã ä å æ ç è é ê ë ì í î ï
U+00Fx ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ
1.^ As of Unicode version 13.0

Changes (please discuss each individually):

  1. Removed dotted boxes and made NBSP smaller to avoid annoying column width variations depending on whether control characters are in them or not.
  2. Removed whitespace by changing table class to "chset"
  3. Monospace for the numeric code point values to match appearance used in other templates like {{unichar}}.
  4. Removed the word "Notes" between the table and the footnotes.

Other changes I experimented with, and either did not like or was unable to achieve:

  1. Use {{efn}} for footnote, mostly so they can be more easily added to cells
  2. Make the title using "|+" so it matches other wikipedia tables (this produced bad line spacing)
  3. Attempt to get the control characters vertically centered.
  4. Make the PDF link into a reference or efn

Spitzak (talk) 20:18, 15 September 2021 (UTC)[reply]

  • The lack of dashed boxes around the codes for control characters could be problematic. Those dashed boxes are a normative signifier in Unicode charts for invisible characters. I don't really see any benefit to these cosmetic changes. What were you trying to accomplish with it? Is there a context where the altered version works better? Given that you have a set of hundreds of templates with identical formatting, will the new formatting work for the context in which the rest of the templates are used as well? This just seems like change for change's sake, and that's really not a compelling reason to invest all the time and effort to either migrate everything or to have this one particular template violate the consistent presentation of this standardized information. VanIsaac, MPLL contWpWS 20:58, 15 September 2021 (UTC)[reply]
  • FYI: Initial discussions with @DePiep: and @BabelStone: about the formatting of these Unicode charts are here.
  1. Dotted boxes (Unicode's dashed box convension) have semantic value so I oppose removing them. They're not limited to control characters. See Template:Unicode chart Arabic for example.
  2. The new format seems cramped to me, but I suppose could be considered "compact" to other readers. I wonder how it will fare for items like Template:Unicode chart Arabic Presentation Forms-A, Template:Unicode chart Geometric Shapes Extended, and Template:Unicode chart Javanese. I like the current, loose spacing better.
  3. I don't see any improvement or detriment to monospaced code point values or the removal of the "Notes" heading in the footer.
    DRMcCreedy (talk) 21:16, 15 September 2021 (UTC)[reply]