Module talk:lect
Add topicLatest comment: 1 year ago by Theknightwho in topic Broken
Broken
[edit]@Erutuon, Theknightwho, this module is unfortunately broken now. {{lect}} is intended to be filled out as {{lect|parent_family_code|etymology_lang_code}}, so {{lect|xme|bdr}} should be returning Badrudi (xme-bdr), but is instead returning West Coast Bajau (bdr). -- {{victar|talk}} 01:51, 11 May 2023 (UTC)
- @Victar It’s probably worth updating it to ditch having to enter two codes. It’s now possible to obtain the family code from the etym-only language directly. Theknightwho (talk) 02:16, 11 May 2023 (UTC)
- Hang on - I’ve just had a look at the code, and I’m afraid using that model is fundamentally flawed: not every etym-only language follows that format, and even the ones that do don’t necessarily use the parent family for the first part. I also don’t really understand what the advantage of doing it this way is in the first place, either - why not just have one parameter list? Theknightwho (talk) 02:25, 11 May 2023 (UTC)
- The purpose of the module is so you can write out long strings dialects, like
{{lect|xme|abz|far|qoh|yar|cim|nar|jow|qal}}, with the added benefit of not having to include a prefix for each. Each first queried forparentcode-*, then if not found, searched for that code alone. --{{victar|talk}}02:31, 11 May 2023 (UTC)- @Victar It's a seriously bad idea to subdivide language codes like that, because it creates the possibility of ambiguity if
foo-barandbarare both in the same family. It's also unintuitive, because no other templates work this way. Just include the prefixes... Theknightwho (talk) 22:20, 25 May 2023 (UTC)- Like, OMG, so seriously bad. Thanks for letting me know. --
{{victar|talk}}06:31, 26 May 2023 (UTC)- @Victar No-one cares, Victar. You're impossible to argue with, so most of us have stopped bothering. Theknightwho (talk) 06:33, 26 May 2023 (UTC)
- LMFAO, catch you at your next desysop vote. --
{{victar|talk}}16:22, 26 May 2023 (UTC)- Feel free to nominate me, if you like. Theknightwho (talk) 16:24, 26 May 2023 (UTC)
- @Victar There is no consensus for you making this change, and it goes against the principles of how language codes work on Wiktionary. This is not a helpful approach. I will lock the page if you reinstate this again. Theknightwho (talk) 16:38, 26 May 2023 (UTC)
- Feel free to nominate me, if you like. Theknightwho (talk) 16:24, 26 May 2023 (UTC)
- LMFAO, catch you at your next desysop vote. --
- @Victar No-one cares, Victar. You're impossible to argue with, so most of us have stopped bothering. Theknightwho (talk) 06:33, 26 May 2023 (UTC)
- Like, OMG, so seriously bad. Thanks for letting me know. --
- @Victar It's a seriously bad idea to subdivide language codes like that, because it creates the possibility of ambiguity if
- The purpose of the module is so you can write out long strings dialects, like
- Hang on - I’ve just had a look at the code, and I’m afraid using that model is fundamentally flawed: not every etym-only language follows that format, and even the ones that do don’t necessarily use the parent family for the first part. I also don’t really understand what the advantage of doing it this way is in the first place, either - why not just have one parameter list? Theknightwho (talk) 02:25, 11 May 2023 (UTC)