Template talk:Infobox Unicode block: Difference between revisions

Content deleted Content added
Unexpected redlink: new section
Hnvnc (talk | contribs)
 
(36 intermediate revisions by 5 users not shown)
Line 10:
 
Must say, the top 'Usage' section does not mean anything to me. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 22:23, 28 March 2013 (UTC)
:Is that a little clearer? [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]]<sub><small>[[WP:WikiProject Writing systems|WS]] [[WP:WikiProject Heraldry and vexillology|Vex]]</small></sub><sup style="margin-left:-7.0ex">[[Special:Contributions/Vanisaac|contribs]]</sup> 00:24, 29 March 2013 (UTC)
 
== Unexpected redlink ==
 
For example, page [[CJK Radicals Supplement]]. Why does this template, on that page, produce a red link while pure pagename=block name? -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 22:32, 28 March 2013 (UTC)
:I don't know what you're talking about. [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]]<sub><small>[[WP:WikiProject Writing systems|WS]] [[WP:WikiProject Heraldry and vexillology|Vex]]</small></sub><sup style="margin-left:-7.0ex">[[Special:Contributions/Vanisaac|contribs]]</sup> 00:24, 29 March 2013 (UTC)
::The page has {{tl|Infobox Unicode block}}, all fine. Then, the template box shows title [[CJK Radicals Supplement]] in a red link. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 00:50, 29 March 2013 (UTC)
:::The infobox shows up just fine for me. [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]]<sub><small>[[WP:WikiProject Writing systems|WS]] [[WP:WikiProject Heraldry and vexillology|Vex]]</small></sub><sup style="margin-left:-7.0ex">[[Special:Contributions/Vanisaac|contribs]]</sup> 01:06, 29 March 2013 (UTC)
::::See page [[CJK Radicals Supplement]]. It has {{tl|Infobox Unicode block}}. Top right of that page, the {{tl|Infobox Unicode block}} title, gives a ''red'' wikilink. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 01:14, 29 March 2013 (UTC)
:::::There are literally zero red wikilinks on that page. There is something wrong with your browser/connection. [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]]<sub><small>[[WP:WikiProject Writing systems|WS]] [[WP:WikiProject Heraldry and vexillology|Vex]]</small></sub><sup style="margin-left:-7.0ex">[[Special:Contributions/Vanisaac|contribs]]</sup> 05:13, 29 March 2013 (UTC)
::::::You are right. It is even worse. It uses the <code>darkred</code> color, against [[WP:COLOR]].
:::::::This is a (secundary) reason to revert using font-color in the caption. See below: [[#Caption font color]] -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 22:55, 30 April 2013 (UTC)
 
== Caption font color ==
 
I have undone the coloring of the ''caption font color''. First of all, Unicoded does not have a "script type", so we are entering OR. Secondary, it uses color ''without meaning''. The reader can not see the meaning (it is not even elsewhere, as in a key/legend). Third, one color was ''red'', which suggested a redlink. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 22:55, 30 April 2013 (UTC)
 
== Please keep disambiguation ==
For the script1 parameter, many pages that use this template have a comment of "Please keep disambiguation so template works" followed by an internal link (for example, <nowiki>[[Glagolitic (script)|Glagolitic]]</nowiki>) on the [[Glagolitic (Unicode block)]] article. I don't see where the template is doing anything special with this. Is it just a link with a label? If so, can we dispense with this confusing (at least to me) warning? [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 02:44, 29 August 2014 (UTC)
:You're right. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 15:15, 29 August 2014 (UTC)
 
== Grouping data ==
 
I note that the infobox has two sorts of data: about ''block content'' (scripts, symbols) and ''block structure'' (U+ numbers, plane, non-assigned code points). I propose to put those together. This being a block, the content (script) data can go below. Maybe add header "Content"? -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 17:52, 20 November 2016 (UTC)
 
Version details can stay at the bottom, with a header. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 17:54, 20 November 2016 (UTC)
 
== Links to previous and next blocks ==
 
I often wish there were links to the previous or next blocks, as in the Wiktionary appendices on Unicode blocks, such as [[wikt:Appendix:Unicode/Latin-1 Supplement]]. This can be done with Lua. Would it be appropriate in this infobox? — [[User:Erutuon|Eru]]·[[User talk:Erutuon|tuon]] 21:23, 15 April 2018 (UTC)
: Same here but couldn't decide on formatting and if it should be next by code point range, next by block name, or both. [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 21:26, 15 April 2018 (UTC)
:: Well, personally I've only been interested in neighboring blocks by codepoint. I don't know why one would want to find the next or previous block by alphabetic order, because that is often meaningless: for instance, [[Basic Latin (Unicode block)|Basic Latin]] borders [[Bamum Supplement]] and [[Bassa Vah (Unicode block)|Bassa Vah]]. What would be more useful is links to other blocks that contain characters in the same script: Basic Latin, Latin-1 Supplement, Latin Extended-A, Latin Extended-B, Latin Extended Additional, Latin Extended-C, Latin Extended-D, Latin Extended-E. — [[User:Erutuon|Eru]]·[[User talk:Erutuon|tuon]] 00:44, 16 April 2018 (UTC)
 
== Related blocks ==
 
In [[Early Dynastic Cuneiform (Unicode block)]], {{U|Theknightwho }} added this hatnote:
{{also|Cuneiform (Unicode block)|Cuneiform Numbers and Punctuation|l2=Cuneiform Numbers and Punctuation (Unicode block)}}
 
While being GF, and a good idea, I have removed it [https://en.wikipedia.org/w/index.php?title=Early_Dynastic_Cuneiform_(Unicode_block)&diff=1074116005&oldid=1074109445&diffmode=source] with es
:{{mono|1="rm 'see also' hatnote (goodfaith): obviously content related, so should be in article body (infobox? See also section?)"}}.
 
Now I am here to propose such addition to article content.
*'''Proposal 1''': in Infobox subsection, for content-related Unicode blocks, add {{para|related blocks}} to list these. For example:
{{left|1={{infobox
|abovestyle=background:#CCE;
|above = Early Dynastic Cuneiform
|headerstyle=background:#E6E6FF;
|header20=Related Unicode blocks
|data21={{ubl
|[[Cuneiform (Unicode block)|Cuneiform]]
|[[Cuneiform Numbers and Punctuation (Unicode block)|Cuneiform Numbers and Punctuation]]}}
}}}}
{{clear}}
It will require discipline, from this intention, to limit the to content-related (ie, limit to same script, or same symbol set).
 
-[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 09:40, 27 February 2022 (UTC)
:I support this proposal. [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 17:21, 27 February 2022 (UTC)
::I have re-added the hatnote by Theknightwho (OP): many Block articles have it this way, so better consistent. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 17:31, 27 February 2022 (UTC)
 
== Script in PUA ==
 
{{slink|Cirth|ConScript_Unicode_Registry}} is a script published being in PUA (private use block). We could think of a better presentation of this notion. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 11:02, 27 February 2022 (UTC)
:Created {{clc|Category:Miscellaneous Unicode blocks}} for these. [[ConScript_Unicode_Registry]] lists many more. Maybe thoser PUA subs are unfit for {{tlf|Infobox Unicode block}}. -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 13:06, 27 February 2022 (UTC)
:The category also contains deleted blocks (version 1&ndash;>2 etc.), like [[Hangul (obsolete Unicode block)]]. (Could not find, easily, list of changes at Unicode-sites, e.i. definitive formnal block changes back then). HTH -[[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 07:42, 28 February 2022 (UTC)
 
== Parameter "latest change" ==
 
I have boldly added {{para|latest change}} to the live infobox. Per suggestion by {{U|Spitzak}} on my talkpage.
 
Usage: it requires a ''version number'': {{para|latest change|14.0}} &rarr; [see example in the documentation]. Later we can expand this with more options (like free text, reference).
 
I hereby ask {{U| Drmccreedy}}: when you edit any Block for version 15, please add {{para|latest change|15.0}}. It will show, and we can find it back later on. [[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 15:57, 13 September 2022 (UTC)
:I can use it although it seems that it should be a calculated value based the other parms. And should probably be latestchanged (without a space). [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 19:09, 13 September 2022 (UTC)
::There are changes to a block that cannot be calculated: I just met three in v15: new abbreviations &tc., [https://en.wikipedia.org/w/index.php?title=Unicode_alias_names_and_abbreviations&type=revision&diff=1110103880&oldid=1086556309&diffmode=source U+0019, U+0616, U+1BBD]. Anyway, worth to keep the idea & develop then. I myself see the need for freetext additions. Since there is no error, we can postpone this development. [[User:DePiep|DePiep]] ([[User talk:DePiep|talk]]) 19:27, 13 September 2022 (UTC)
 
==Replacing the <code>codechart</code> parameter==
I'm proposing a change in how this template shows links to the Unicode PDF code chart and the webpage/namelist.<br />
'''Some background''':
* On 2022-02-25 user {{ping|Theknightwho}} added the <code>codechart</code> parameter to show a link to Unicode's PDF code chart.
* On 2023-06-11 {{ping|Hnvnc}} added the ability to autogenerate the PDF and webpage/nameslist links based on starting code point if <code>codechart</code> is absent. Great feature.
* In July 2023 I removed the <code>codechart</code> parameters on all the articles where it was just the starting code point, letting the template autogenerate the links. That only leaves these articles to consider:
**[[Cirth#ConScript Unicode Registry]] doesn't use the <code>codechart</code> parm so both the PDF and webpage/nameslist links are bad (Error 404)
**[[Hangul (obsolete_Unicode_block)]] has three infoboxes:
***[[Hangul (obsolete Unicode block)#Korean Hangul Syllables block|Korean Hangul Syllables]] Infobox uses <code>codechart = https://www.unicode.org/versions/Unicode1.0.0/CodeCharts1.pdf#page=33</code> which is fine for the PDF link but the webpage/namelist link is wrong and goes to CJK Unified Ideographs Extension A because of the reused starting code point
***[[Hangul (obsolete Unicode block)#Hangul Supplementary-A block|Hangul Supplementary-A]] doesn't use the <code>codechart</code> parm and both autogenerated links are bad (Error 404).
***[[Hangul (obsolete Unicode block)#Hangul Supplementary-B block|Hangul Supplementary-B]] has the same issue as -A
**[[Private Use Areas]] doesn't use the <code>codechart</code> parm on any of its three infoboxes:
***[[Private Use Areas#Unicode PUA_blocks|Private Use Area]] infobox is fine as-is
***[[Private Use Areas#Unicode PUA_blocks|Supplementary Private Use Area-A]] infobox has an OK PDF link but a bad webpage/nameslist link (Error 404)
***[[Private Use Areas#Unicode PUA_blocks|Supplementary Private Use Area-B]] has the same issue as -A
**[[Tengwar#Unicode]] doesn't use the <code>codechart</code> parm so both the PDF and webpage/nameslist links are bad (they point to the Private Use Area because the first code point for this ConScript block is U+E000)
**[[Tibetan (Unicode block)]] has two infoboxes:
***[[Tibetan (Unicode block)#Block|Tibetan]] doesn't use the <code>codechart</code> parm and both autogenerated links are correct.
***[[Tibetan (Unicode_block)#Former Tibetan block]] uses <code>codechart = https://www.unicode.org/versions/Unicode1.0.0/CodeCharts2.pdf#page=100</code> so the PDF link is correct but the webpage/nameslist link goes to the Myanmar namelist because of the reused starting code point
'''My proposal''' is to delete the <code>codechart</code> parm and add the <code>codechartoverride</code> parameter:
*If <code>codechartoverride=omit</code> is specified, omit both links.
*If <code>codechartoverride=https://...</code> is specified, use the supplied URL for the PDF link and skip the webpage/namelist link.
*If <code>codechartoverride</code> isn't specified, autogenerate both links as is currently done.
'''After the template is changed''':
*Add <code>codechartoverride=omit</code> to [[Cirth#ConScript Unicode Registry]], [[Hangul (obsolete Unicode block)#Hangul Supplementary-A block|Hangul Supplementary-A]], [[Hangul (obsolete Unicode block)#Hangul Supplementary-B block|Hangul Supplementary-B]], [[Tengwar#Unicode]], and [[Tibetan (Unicode_block)#Former Tibetan_block]]
*Update [[Private Use Areas#Unicode PUA_blocks|Supplementary Private Use Area-A]] infobox with <code>codechartoverride=https://unicode.org/charts/PDF/UF0000.pdf</code> so no webpage/nameslist link is produced
*Update [[Private Use Areas#Unicode PUA_blocks|Supplementary Private Use Area-B]] infobox with <code>codechartoverride=https://unicode.org/charts/PDF/U100000.pdf</code> so no webpage/nameslist link is produced
I think this addresses all the issues in how code charts/namelists are linked. Does anyone have any issues with this approach? [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 17:44, 30 July 2023 (UTC)
 
:Thank you very much @[[User:Drmccreedy|Drmccreedy]] for catching the edge cases. My apologies for not considering potential issues, as I initially only aimed to get the link to the webpage into the infobox. [[User:Hnvnc|Hnvnc]] ([[User talk:Hnvnc|talk]]) 18:23, 30 July 2023 (UTC)
::I don't think we even need a new <code>codechartoverride</code> parameter, just retool the existing <code>codechart</code> parameter to handle <code>codechart=omit</code>, and you should be good to go. [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]], GHTV<sup> [[Special:Contributions/Vanisaac|cont]]</sup><sub style="margin-left:-3.5ex"><small>[[WP:WPWR|WpWS]]</small></sub> 23:01, 30 July 2023 (UTC)
:::We would also need to change the behavior so if <code>codechart</code> is used, no link to the webpage/namelist is created. Initially, <code>codechart</code> was the only way to get the PDF link displayed then autogeneration was introduced. That's why I'm recommending changing the parameter name to <code>codechartoverride</code> to make it clear that it ''overrides'' the automatic generation of the PDF and webpage/namelist links. [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 23:41, 30 July 2023 (UTC)
::::The problem is that you're going to have to go through and change all the extant instances of <code>codechart</code> into <code>codechartoverride</code>, when all except the few "omit" instances are going to be absolutely identical in parameter value. And when looking at the functionality being implemented, <code>codechart=omit</code> is actually a better description of the behavior than <code>codechartoverride=omit</code>, while <code>codechart=http://example.com</code> is just as descriptive as <code>codechartoverride=http://example.com</code>. The only time an editor who would even notice a change in functionality is if they used the "omit" keyword. Changing the parameter name can only have a negative effect when editors who are used to the extant parameters don't get their desired results after the change. [[User:Vanisaac|Van]][[User talk:Vanisaac|Isaac]], GHTV<sup> [[Special:Contributions/Vanisaac|cont]]</sup><sub style="margin-left:-3.5ex"><small>[[WP:WPWR|WpWS]]</small></sub> 00:58, 31 July 2023 (UTC)
:::::OK. If the hangup is changing the parameter name, here is my '''revised proposal''':
*If <code>codechart=omit</code> is specified, omit both links.
*If <code>codechart=https://...</code> is specified, use the supplied URL for the PDF link and skip the webpage/namelist link. This change affects the three instances where the <code>codechart</code> parameter is currently used.
*If <code>codechart</code> isn't specified, autogenerate both links as is currently done. This is the 325 times the "Infobox Unicode block" template is currently included without the <code>codechart</code> parameter.<br>Any objections? [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 03:02, 31 July 2023 (UTC)
::::::I've made the change to the <code>codechart</code> parm as outlined. [[User:Drmccreedy|DRMcCreedy]] ([[User talk:Drmccreedy|talk]]) 02:48, 4 August 2023 (UTC)
:::::::@[[User:Drmccreedy|Drmccreedy]] Thank you. Great solution. [[User:Hnvnc|Hnvnc]] ([[User talk:Hnvnc|talk]]) 04:43, 4 August 2023 (UTC)