Template talk:BCP47

Lua error and hidden docs[edit]

@Tacsipacsi Hiyo. I'm wondering if it would be 'easy' to fix the Lua error that is currently showing on this page?

(It currently just shows: Lua error in Module:Documentation at line 140: message: type error in message cfg.container (string expected, got nil).)

It seems to be (?) preventing the display of the docs subpage (Template:BCP47/doc) which left me extra-confused for a few minutes, about this already complex template! Cheers, Quiddity (WMF) (talk) 01:06, 30 October 2021 (UTC)[reply]

@Quiddity (WMF): Just the usual, GeneralNotability broke the half wiki by careless usage of the Include all templates option on Special:Import. This particular breakage was reverted by Billinghurst, but I suggest reverting the following fully protected templates’ and modules’ changes as well:

The first three are just potentially broken (e.g. parameters dropped), so if someone carefully examines them and determines that nothing is broken (or fixes pages that are), they don’t need to be reverted; the protection banner config is, however, definitely and severely broken—no Lua errors, but it displays huge banners where it shouldn’t and adds redlinked categories instead of existing ones, so it should certainly be reverted. Also, Template:Tqq has been protected as High-risk template despite of not having a single transclusion; I suggest unprotecting it. —Tacsipacsi (talk) 15:24, 30 October 2021 (UTC)[reply]

Tacsipacsi, I've already apologized for the screwup and made it clear that I won't be doing that again, the passive-aggressive commentary isn't necessary. I've made the reverts you suggested. GeneralNotability (talk) 15:27, 30 October 2021 (UTC)[reply]

@GeneralNotability: I don’t know where and when did you apologize, but I certainly didn’t see it—if I did, I wouldn’t have used this language. Also, I’m much more mad at the extension than at you personally, sorry that this wasn’t clear (the just the usual also refers to that it happened again, not that you did it again—I don’t even track whether you’ve made such mess before, but I suppose you haven’t, it’s a lesson for a lifetime 🙂). Thanks for the reverts. —Tacsipacsi (talk) 15:44, 30 October 2021 (UTC)[reply]

Tacsipacsi, all right, thank you - believe me, I am very mad at myself for messing up. I apologized here a few minutes before this, and yeah - I won't be making this mistake again, trust me. GeneralNotability (talk) 15:46, 30 October 2021 (UTC)[reply]

By the way, what about Template:Tqq? Why is it fully protected without any usage? —Tacsipacsi (talk) 15:45, 30 October 2021 (UTC)[reply]

Tacsipacsi, I protected preemptively - assuming people start using it, it's one of those templates that gets used all over the place (at least, that's how it is on enwiki). If that's inappropriate I'll remove the protection. GeneralNotability (talk) 16:58, 30 October 2021 (UTC)[reply]

@GeneralNotability: Even on enwiki, w:Template:Tqq is transcluded 827 times, which is not quite all over the place. (w:Template:Talk quote inline is indeed used on tens of thousands of pages, but that’s not what you protected here. Its Meta equivalent Template:Talk quotation was created four years ago, and still has just over 500 transclusions.) Also, User:MusikBot II works here on Meta as well, so templates that should be protected just because they’re used a lot, will be protected when they’re actually used a lot, manual protection is needed only for not much used yet sensitive templates like those used on the main page. —Tacsipacsi (talk) 18:00, 30 October 2021 (UTC)[reply]

Comment it all sucks big browns that there are not global modules and templates, and until that sort of thing happens, this will happen with the existing system. A good system would have measures in place, and not rely on human behaviour for actions and inactions. — billinghurst sDrewth 10:59, 31 October 2021 (UTC)[reply]

Please revert change to i-tsu[edit]

Please revert the change at [1]; this was made by a newcomer (that has never done anything else on this wiki, never discussed with anyone, not created hios user page) just before that template was blocked from editing, but it should have been reverted. It changed the mapping of legacy "i-tsu" from the standard ISO 639 code "tsu" into the invalid ISO 639 code tstu, and must be reverted back to tsu (the code for the language spoken in Taiwan and most often named Tsou in English, Tsou-ngî in Romanized Chinese Hakka, 鄒語 in Chinese, ツォウ語 in Japanese; documented alternative names found in Glottolog, or The Linguist List include Tso, Tsoo, Tsu-U, Tsu-Wo, Tsuou, Tzo or Cou; Tibola, Tibolah, Tibolak or Tibolal; Namakaban; Niitaka; old unprecise sources also give Formosan). That remapping is also documented in the IANA database for BCP47 subtags. verdy_p (talk) 15:00, 28 February 2023 (UTC)[reply]
Also please place the "?" within HTML comments in |i-enochian=x-enochian? and |i-mingo=x-mingo? (this is an old omission, but I could never get it fixed by myself). These legacy IANA codes have no known mapping. You may have suggestion about their historic uses, but I never found a reference I could read to explain their inclusion in the IANA database before the reform of BCP47 within RFC464 (taking into account the creation of ISO 15924, deprecation of "i-*", new fallback rules and a major update of the IANA database when ISO 639-3 and ISO 639-5 were first released. I think that 'i-mingo' are now considered of subgroups of independant Iroquoian/Seneccan languages in the United States (not really macrolanguages, possibly ethnogeographic), but may be one of these languages. 'i-enochian' refers to an construct occult language briefly used in En,glish and has stuill not been standardized, it may persist in IANA on demand of some US or British libraries for classification purpose in catalogs of 16-th century books. It was written in the Latin script but also with its own occult script (not standardized in the UCS by Unicode/ISO/IEC 10646 or in ISO 15924). verdy_p (talk) 15:08, 28 February 2023 (UTC)[reply]

Please change mapping for tokipona[edit]

@Tacsipacsi and GeneralNotability:

Tokipona now has a standard BCP47 code (from ISO 639-3). Please remove the existing line |tokipona|tp=x-tokipona, and insert the line |topkipona|tp=tok in the previous section (just before the existing line |zh-classical=lzh): it's no longer necessary to use a "x-*" private-use code for strict BCP47 conformance with that language.
Reminder: Please also apply the two fixes in "Please revert change to i-tsu", requested since last February, and still not applied (one is an old incorrect edit applied by a newcomer that never contributed anything on our wikis, that still needs to be reverted from the non-conforming tstu back to the correct code tsu, and the other is about the two question marks "?" for Enochian and Mingo, that must be within HTML comments; there are still no other clear replacement, so they must still map to a standard private-use "x-*" code). verdy_p (talk) 16:06, 2 September 2023 (UTC)[reply]