Template talk:ISO 639 name

src: upload.wikimedia.org

Video Template talk:ISO 639 name

Siap untuk menerapkan?

I've made some changes today to ensure that ISO 639 names | XXX produces exactly the name of ISO 639 XXX . View User talks: MSGJ/Sandbox3 for comparison.

• Are we sure that all form templates {{ISO 639 name XXX}} are not included in this one?
• Which template uses this? I know about {{lang}}; is there something else?
• What should we do with template {{ISO 639 name XXX}}?
  1. Ignore them
  2. Direct them to this template
  3. Mark them as depreciated and eventually delete

--Ã, Martin (MSGJÃ, Ã, Â · talk) 12:38, 29 April 2009 (UTC)

You can do what I do with the interwiki translation template: replace the code with the appropriate code from this template to generate the data, and then I can boot the new code into the article after a little while when we make sure it works well, assuming no objections. - xeno ^talk 12:44, April 29, 2009 (UTC)

I believe the situation is not that many articles mention the template directly. Most calls come through {{lang}} and the switch can be very easy. On substitutions, I would advise against doing so. Okay, the name of the language probably will not change, but once you do, you lose the ability to add additional functionality. And the replacement benefits, I think, are small. --Ã, Martin (MSGJÃ, Ã, Â · speech) 13:19, 29 April 2009 (UTC)

It's a bit hard to see what's left until {{lang}} has been changed, so why not finish that part, wait a minute, and then check "What's the link here" in all templates to see what's left for do. If not many then it could be worth removing the old template. - WOSlinker (talk) 22:26, ​​â € <â € <29 April 2009 (UTC)

What I mean by subst, is that because you have replaced "ISO 639 pl" with "{{ISO 639 name | pl}}", when I rested the ISO 639 pl, it finally puts the ISO 639 name template on. Do not put the ISO 630 template name itself. Erm, I think I should say replace, easier this way =) - xeno ^talk 23:28, 29 April 2009 (UTC)

Maps Template talk:ISO 639 name

Duplicate Template: Language

This templage has the same function as {{Language}} and should be redirected and abandoned. This will ensure that only one ISO 639 code list is used in the English Wikipedia. Please give your comment before I request {{editprotected}}. AndreasÃ, 20:13, July 13, 2009 (UTC)

Hmm. This template seems to include all ISO 639-1, -2, and -3, while {{language}} seems to understand only IDO 639-1, e.g. just know "de" for German, not "ger" or "deu".
However, they can still be merged, and probably should be. I wonder why Martin created this one, let's wait for what he said Cheers, Amalthea 20:36, July 13, 2009 (UTC)

I created this to replace hundreds of form templates {{ISO 639 name de}}, {{ISO 639 names ja}}, etc., etc. In fact, this template is not used anymore because it was found that the big switch was detrimental to performance. View Talk Template: Lang # Simplify the template for discussion. Unfortunately, a neat solution is not the best solution in this case, although I hope that one day it will change and we can use this template and discard everything apart. I would definitely support the merging of this functionality, if it is duplicated. I believe there may be some other templates out there that do the same thing with this as well. --Ã, Martin (MSGJÃ, Ã, Â · talk) 14:18, July 14, 2009 (UTC)

Oh, I did not even notice it. - xeno ^talk 14:25, July 14, 2009 (UTC)

Templates and Templates: Language/id in use. If the performance is better with sub-templates than a switch, we'd better change this template to "{{ISO 639 name {{code}}}}}" with some checks to ensure that "ISO 639 name & lt; x & gt ; " there is? John Vandenberg ^(chat) 10:31, 11 November 2011 (UTC)

Yes we have to, this template also does not support anything like a lot of code as a systemic solution, even though I hooked up a lot in the past, and systemic solutions have the advantage that anyone can add new code, high remain protected. I will make it so. Rich Farmbrough , 01:58, March 22, 2012 (UTC).

Another option is to start using {{#language:.. |..}} (documented in mw: Help: magic words), but there are still some differences between the names of the languages ​​supported by the enwp templates, the commons templates and the mediawiki software. View commons: Template_talk: Language # Make_use_of_MediaWiki_1.18_capabilities. John Vandenberg ^(chat) 4:54, November 26, 2011 (UTC)

src: upload.wikimedia.org

Edit request on May 6, 2012

I have nominated this template for deletion, so please add {{tfd | inline = yes}} .

Liam987Ã, 16:11, May 6, 2012 (UTC)

Done , even if I use type = tiny . Chris Cunningham (user: thumperward) (talk) 09:47, May 9, 2012 (UTC)

src: bernadettepollard.com

Switch to module

I have converted this tpl to Lua; there are two clear benefits to this:

• the list of languages ​​is much more manageable (see Module: name/data ISO 639; I have imported all code from the live event except a few incorrect ones, and added some more)
• we can convert string by fuzzy, that is, as long as basic ISO code is defined, merge code will find match, for example:
  • {{ISO 639 names | ar-x-nastaliq}} ->
  • {{ISO 639 names/sandbox | ar-x-nastaliq}} ->

etc.

This in turn behaves just as it is now in life.

I think I will make a protected edit request within a few days if nobody opposes this change and if I do not make a mistake. Templates avoiding the parent tpl should be edited (to change the space to the vertical bar). - Lfdder (talk) 18:31, 8 September 2013 (UTC)

• Which code do you find "not feasible"?
• I hope you do not mind having edited the data template to remove all redundancies and nipples. I do not think this will make it harder to maintain, the data page is 90% smaller, and the (single) prayer is now significantly faster.
• It will always be slower than the transclusion of the dependent template, but maintainability obviously defeats the current hack.Ã, :)
• Currently undefined codes show {{error}} that can be captured - I think this behavior should be preserved.
• What is the meaning of the code parameter name code that is obfuscated in Template: name/sandbox ISO 639? Just to handle empty parameters and display controls on the template page?
• Once this is used, all old helper templates should be deleted. I can do it semi-automatically while verifying that no transklusi is left, if you want.
• A rather broader question, apart from moving to module: I was wondering if it would not be better to have a custom template for the ISO-639 list. In meta templates you usually want a more narrowly defined input and throw an error if the input is wrong. For example, {{Infobox language}} has explicitly defined inputs for various ISO 639 codes and uses one/few of them as parameters for this template, but the blurring of this template will hide the input error instead of pointing them to the editor.
  This template does not have/that/many transclusions with 5000 (and its strange cousin {{language}} has less) so of course it can be done to take this opportunity and divide it into a more specific template.

Amalthea 21:11, September 8, 2013 (UTC)

• Some nothing like cz for Czech country code or lowercase like in zh-cn (should be zh-CN). Check out the trial here.
• Well, I think we should keep the entry "redundancy" and nil. There is no redundancy in the output because the tables are combined at the bottom and the same key will overwrite the previous one; nil entry discarded. Also, we may want to define lots of nil.
• Not noticeably slower.
• I'll add it back, thanks. Finish - Lfdder (talk) 22:18, 8 September 2013 (UTC)
• Yeah, that's for what. This will only skip | code = to the script if it is set or empty, but not if it does not exist at all.
• That's good, thanks.
• This module has two modes: simple (tight) or fuzzy. Infobox lang can call the module directly with simple . Other templates like {{lang}} would like to be fuzzy. For what is more special template? These two things? Or do you have something else in mind?

Thanks for the feedback! - Lfdder (talk) 21:40, 8 September 2013 (UTC)

Increased fuzzy logic, will now try to match the merge code of the derived before falling back to the base code. - Lfdder (talk) 11:07, September 9, 2013 (UTC)

• {{ISO 639 name/sandbox | zh-Hant-CN}} ->
• {{ISO 639 names/sandbox | zh-Hant}} -> traditional Chinese
• {{ISO name 639/sandbox | zh}} -> Chinese

All {{#ifexist: {{{ISO 639 names {{{1}}} |...}} testing needs to be changed to use #if and vertical bar. They will still work after importing the sandbox because they are not interacting with this template, so this can be done after applying the module - but before deleting all template names ISO 639. - Lfdder 08:16, 12 September 2013 (UTC)

Import sandbox to show live with modules. - Lfdder (talk) 11:26, 13 September 2013 (UTC)

Thank you for taking the time to write this! I just think that the language name template is too complicated when I meet your edit request - and now I see that that's what you think from the beginning. By the way, I've made some tweaks to spaces and comma placements. There are several different styles out there that I've seen used, but the indentation in the module namespace is always done with four spaces, as far as I've seen. The same is true for comma placement - in the module namespace, I've only seen it at the end of the relevant row, not at the beginning of the next one.

Also, I agree with Amalthea about the nil values, and I have deleted them again. It seems to get Lua to process many table entries for not much reason. I know Lua is very fast when compared to templates, but why make it do the job when not necessary? If you want to enter a key for maintenance purposes, maybe commenting on them would be a better idea. Or, my preferred solution, you can create a subpage somewhere that lists everything that will not actually be used in the live template.

And finally, is there any chance to create Module: ISO 639 name/doc and Module: ISO 639 name/data/doc? It would be useful to have some special documentation for the module, though just to say that all it does is implement the old ISO 639 template templates. Best - Mr. Stradivarius ^{? talk?} 12:31, 13 September 2013 (UTC)

Re. the nils, they are only processed once (and discarded) when the data is imported. It should not have an impact on performance. (I think.)

I've added documentation for Modules: ISO name 639, will do the same for the data in a bit. Thank you, - Lfdder (talk) 13:42, 13 September 2013 (UTC)

I have replaced all the names of the languages ​​with their ISO names (used for mixed titles of Wikipedia pages and names that exist in all ISO 639 tpl names), which means that if this goes live now, it will ruin the sorting category for {{lang}} and so on, so I have pulled the edit request. I also added another mode to the script (explained in the doc module). Would appreciate any feedback. - Lfdder (talk) 17:00, 14 September 2013 (UTC)

src: upload.wikimedia.org

Loop error with empty parameter

{{ISO 639 name |}} (with empty parameters) makes template loop errors. It only affects 2 pages, which I know, {{User x}} and {{User x/doc}}. - PC-XT 06:45, March 31, 2014 (UTC)

I installed fixes in the sandbox, but I also fixed the x User template, so I'm not sure it really needs to be applied. - PC-XT 06:33, 5 April 2014 (UTC)

src: blog.avidadserver.com

Add Hopi language

Can someone add the Hopi language code, " hop "? I noticed it does not appear in the {{rd from language}} template with the given language code. --Xiaphias (talk) 07:57, 15 November 2014 (UTC)

This can not be changed in this template; all it does is transcluding different language-specific templates. {{ISO 639 name | hop}} produces the {{ISO 639 hop name} transclusion, which contains the name of the language. It functions as intended: Hopi.

View the {{r from alternative language}} source code, it will display the language only if the category for that language exists. Therefore, everything needed for a redirect template to work for Hopi redirects creates Category: Redirects from Hopi and/or Category terms: Redirects to Hopi language. SiBr ₄ (talk) 12:59, November 15, 2014 (UTC)

Only note for future changes (after active Hopi): testing adds Hopi to the main documentation causing the "loop error" mentioned earlier (see previous section). We may need to apply sandbox fixes, when Hopi should be included in the documentation. GermanJoe (talk) 13:28, 15 November 2014 (UTC)

src: upload.wikimedia.org

Help with Tuvan/Tyvan?

For {{ISO 639 name tyv}} gives Tuvan. However Tyvan is actually a transfer to Tuvan. Some of the pages that use it seem set to see it as Tyvan, others, like Category: Redirects from Tuvan language? use Tuvan. I do not want to change the template values ​​from Tyvan to Tuvan without ensuring that it will not mess up anything. Naraht (talk) 21:45, January 18, 2015 (UTC)

src: upload.wikimedia.org

Template-protected edit requests on February 11, 2015

~ ait? Brayn not ait?

Not done: It's unclear what changes you want to make. Please specify specific changes in the format "change X to Y". - {{U | Technical 13}} (e o t o) 15:06, 11 February 2015 (UTC)

src: s3.amazonaws.com

Describing a template

Can the description be added to explain the criteria for being on the table? I can not find the Filipino language, although the page says that it has ISO 639-2 and ISO 639-3 codes. Also, the description "Code1" through "Code4" must also be entered, or the column headings should be made more descriptive in the table; The current description mentions that the template completes three standards, but there are four codes and relationships with the standard are not mentioned. --Ost (talk) 20:47, June 2, 2015 (UTC)

src: upload.wikimedia.org

Return an empty string for code that is not in the list

As a result of categorization changes, I see redirects as categories, for example in fricative bilabial Voiceless. Does this appear for others? I do not know why this happened; I hope the "ifexist" test will pass, because there is a page in Template: ISO name 639 {1}, even if it is a redirect. - Jonesey95 (talk) 14:31, 8 April 2017 (UTC)

I see the redirect too. This is not the easiest template to work on, but per that and this note is left on my talk page, we need to find a better solution. wbm1058 (talk) 20:43, 9 April 2017 (UTC)

src: s3.amazonaws.com

Where is Old French ??

Is this Old French deliberately left out of this list for a reason? We have Old English, Old Irish, and Old Church Slavonic (for crissake!) But not Old French ? If I'm more confident with modifying the relevant code/template, I'll stab myself, buis zut alors, je ne l'ai pas! (bien que je puisse essay!). Is there a story? If so, put it on me. KDS 4444 ^Talk 05:43, March 14, 2016 (UTC)

The list in the documentation does not cover all possibilities, but the template does not accept Old French as an argument: {{Language | fro}} . Cordialement, --capmo (talk) 07:15, March 14, 2016 (UTC)

Sweet! Thank you! KDS 4444 ^Talk 08:42, March 14, 2016 (UTC)

src: upload.wikimedia.org

Request edited edit by template on February 1, 2017

Please change the Sami language (which does not exist, it is a redirect to the language family) to Northern Sami. Florian Blaschke (talk) 05:13, February 1, 2017 (UTC)

See Sami for more information. I think this editor might be looking for "sme" to represent "Northern Sami", but I'm not sure. Code "se" should not be used to write written language, because it is a language family. Someone with some domain expertise may be able to help more. - Jonesey95 (talk) 05:38, February 1, 2017 (UTC)

It looks like "Northern Sami" is correct based on the SIL page, so I have changed it by editing it to Template: ISO 639 sme name. There are also some related categories that need to be moved - I'll do it now. - Mr. Stradivarius ^{? talk?} 06:42, February 1, 2017 (UTC)

Actually, it turns out "se" refers specifically to Northern Sami as well. "Se" is the ISO 639-1 code for Northern Sami, and "sme" is the ISO 639-3 code for North Sami. Other Sami variants do not have ISO 639-1 codes. - Mr. Stradivarius ^{? talk?} 07:03, February 1, 2017 (UTC)

Thank you, Mr. Stradivarius! --Florian Blaschke (talk) 11:20, 1 February 2017 (UTC)

src: upload.wikimedia.org

Template-protected edit request on September 28, 2017

Can someone substitute this template neatly by wrapping three calling templates in {{{| safesubst:}}} , because it's overridden in {{internetquelle}}. P p p e r y 23:37, 28 September 2017 (UTC)

Completed - JJMC89 (T Ã, Â · C) 00:13, 29 September 2017 (UTC)

Hawaii

Can someone add a Hawaii person to the list (Code: haw ). I tried to do my own editing but quickly stuck with vermicelli. Thank you in advance. nagual design 04:46, November 24, 2017 (UTC)

Hawaiian has been supported by this template since 2010. {{3x | p}} ery (talk) 21:15, 5 June 2018 (UTC)

Source of the article : Wikipedia