Wikipedia:Templates for discussion/Log/2024 September 27
In this article, we will explore Wikipedia:Templates for discussion/Log/2024 September 27 and its impact on today's society. Wikipedia:Templates for discussion/Log/2024 September 27 has been a topic of interest and debate for a long time, and its relevance continues to be evident in various areas. Different perspectives and approaches that have emerged around Wikipedia:Templates for discussion/Log/2024 September 27 will be analyzed, as well as its evolution over time. In addition, the implications that Wikipedia:Templates for discussion/Log/2024 September 27 can have in different contexts will be addressed, from everyday life to the global level. This article will provide an exhaustive analysis of Wikipedia:Templates for discussion/Log/2024 September 27 and its influence on various aspects of society, with the aim of offering a comprehensive and enriching vision of this broad and significant topic.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The only real English article linked is the embassy in the Netherlands. The India entry is a redirect. Pointless to have a nav box for 1 entry. LibStar (talk) 15:13, 27 September 2024 (UTC)
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
Replace and delete lang-?? templates
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The result of the discussion was merge to Template:Langx, then replace and delete. Please note the excluded templates on the given subpage list. Primefac (talk) 13:11, 7 October 2024 (UTC)updated 14:03, 8 October 2024 (UTC) by request to be explicit
The {{lang-??}} templates are all more-or-less forks of some ancient ancestor. Like {{lang}} the primary purpose of these templates is to render non-English text in a way that is html-correct and compliant with the Manual of Style. {{langx}} uses the same rendering code as the {{lang-??}} templates so, given the same language tag and text, renders an identical output:
{{lang-es|casa}} → ]: <ilang="es">casa</i>] → Spanish: casa
{{langx|es|casa}} → ]: <ilang="es">casa</i> → Spanish: casa
Like {{lang}}, {{langx}} supports all of the 8000+ languages listed in the IANA language-subtag-registry file. {{lang-??}}: one template for one language; {{langx}}: one template for 8000 languages.
Background
The {{lang-??}} and {{langx}} templates differ from {{lang}} in that they prefix the non-English text with a link to the language article name:
{{lang|es|casa}} → <spantitle="Spanish-language text"><ilang="es">casa</i></span> → casa
{{lang-es|casa}} → ]: <ilang="es">casa</i>] → Spanish: casa
{{langx|es|casa}} → ]: <ilang="es">casa</i> → Spanish: casa
For editors who need another language template, their options til now have been:
fork a new {{lang-??}} template
use the lang_xx_italic() utility function in {{lang}}
{{lang|code=es|text=casa|fn=lang_xx_italic}} → ]: <ilang="es">casa</i>] → Spanish: casa
manually prepend a language-article link to {{lang}}:
]: {{lang|es|casa}} → ]: <spantitle="Spanish-language text"><ilang="es">casa</i></span> →Spanish: casa
create the template using {{language with name}} (which more-or-less does what item 3 does...)
do it all manually (not recommended because not html correct):
At this writing template tagging is underway. There are editors who dislike the invasive nature of TfD tags. To minimize annoyance, only instances of {{lang-de}} will display TfD tags.
As the creator of {{lang-ymm}}, I did not get notified. Could you please send notifications to the template creators? This seems quite stealthy with neither notifications being sent nor TfD tags being displayed apart from a single instance of over 1000 templates. 1234qwer1234qwer418:14, 28 September 2024 (UTC)
I did write in the OP: At this writing template tagging is underway. There are editors who dislike the invasive nature of TfD tags. To minimize annoyance, only instances of {{lang-de}} will display TfD tags. I chose not to notify the authors of the 1145 templates because it is a deal of work to research who they are and then notify them. I will if compelled to but would rather not.
It just seems like this TfD is hardly visible to anyone apart from TfD regulars and people who happened to stumble across a specific template from the set. 1234qwer1234qwer423:52, 30 September 2024 (UTC)
Ok, I set {{lang-ru}} to display the tiny TfD notification. If you think that is still insufficient, a list of 'high-use' {{lang-??}} templates is at Module:Transclusion_count/data/L lines 13–74. Feel free to change |type=disabled to |type=tiny in whichever template(s) you think appropriate; remember, {{lang-zh}} is not party to this nomination.
Hey, thanks for the tag. If I understand correctly, if you turn, say, {{lang-ru|Москва|Moskva}} into {{langx|ru|Москва|Moskva}}, it will all still work fine? It appears so. I didn't know {{langx}} even existed until now, I've always used the {{lang-..}} template by copying it from existing pages. It seems rather cumbersome and duplicative compared to the universally applicable {{langx}}. NLeeuw (talk) 14:35, 1 October 2024 (UTC)
You understand correctly. You didn't know about {{langx}} because it didn't exist before 2024-09-20.
I'm seeing one problem with the langx template when used for certain languages: it uses an italic font. Italic fonts do not go well with Cyrillic scripts (and probably other non-Latin scripts) because italic letters in Cyrillic look very different from non-italic letters. Examples of two words first written in non-italics and then followed by the same word in italics: театр = театр and добывать = добывать. I checked lanx|ru and saw that you accounted for that and that the letters are not displayed in italics for Russian, however, for more obscure Cyrillic languages langx is still using italics which needs to be fixed before deleting lang-??, e.g. {{langx|xal-Ru|хурул}} still renders in italics: Kalmyk: хурул.
Glad Nakonana pointed it out and Trappist the monk fixed it. I only recently learnt understand Cyrillic letters, and italicised they are still very confusing. Great work, all this, Trappist. :) NLeeuw (talk) 19:34, 2 October 2024 (UTC)
I've added a temporary fix for redirects from improper names to proper ISO 639-1 language tags. {{lang-chu}} works because it is a redirect to {{lang-cu}} (the correct language tag). While your example now accepts chu and renders the text correctly, the template is emitting a code: chu promoted to code: cu maintenance message. I'm not sure that I'll make the same fix for the ISO 639-2, -3 tags.
Replace usages with {{Langx}} and delete all lang-?? templates. The current system of creating and maintaining over 1.1k templates (with the protentional of it increasing to 8k templates) is a bad system to keep.
It always requires active maintenance. If in the future a feature is added, support will need to be manually added to those templates that need it. Here is a very recent example of a template request from a user requesting to add categories or Template:Lang-tdd and Template:Lang-prk, which converted the templates to the newer lang system.
It requires watching over 1k templates to make sure everything is ok and no vandalism or accidental breakage happens. Here is an example of something slipped through and stayed undetected for over 2 years: Template:Lang-clm had over two years a broken category
New templates are always being created. Some of them are created for no real reason and left unused: Template:Lang-mtm, Template:Lang-nio, Template:Lang-ohu examples of recently created templates (and currently unused).
The proposed system eliminates all of this and has everything located in one template. For users the change is only one additional character more so is a non-issue. As shown in the proposal, related systems, have previously been converted with much success. Gonnym (talk) 13:44, 27 September 2024 (UTC)
I have no particular preference but would like to point out that the old label seems to allow for the easy creation of new labels, split offs, and mergers of linguistic varieties ("languages"). Is this correct?
Why is that important? Linguistics has begun to acknowledge the dynamic nature of the notion "language": what used to be, e.g., German in LUX, is now called Luxembourgish, while Belgian German is something else today. Another example: new languages are being discovered, usually as split offs from what was homogenizingly been considered one language. The language count on Ethnologue increases by about 50 languages a year.
We need a system that allows for an easy change, with the option to list dual classifications when consensus hasn't been reached and two - or more - classifications are in widespread use. MinTrouble (talk) 15:34, 29 September 2024 (UTC)
I originally wanted {{lang-xx}} but that name is already in use. Unable to think of a better name, we settled on {{langx}} where the 'x' is an arbitrary character to disambiguate from {{lang}} so it can mean anything you want it to mean. If you have a better name...
Support merge. A better name, per Wikipedia:Template namespace#Guidelines (Template function should be clear from the template name, but redirects can be created to assist everyday use of very popular templates), would be helpful. I'm fine with "langx" as a redirect, but ideally, the canonical template name should be something like "Language text" or "Non-English text" or "Text in language", all of which are currently available names. There is probably a better name that I am unable to come up with at the moment. – Jonesey95 (talk) 17:10, 27 September 2024 (UTC)
Please, can we not decide that here? Please take up that discussion at another venue, perhaps Template talk:Lang. The ultimate name of the {{langx}} template has nothing to do with the proposition at hand. Eschew WP:BIKESHEDING.
I don't think there's much argument against the replacement, but it is relevant what it is replaced with, because that impacts the future editing of those tens or hundreds of thousands of pages, just like any other template name pattern does. Are you seriously saying we should do the replacements first and then hold a separate RFC for renaming that in turn? That seems like much more flagrant WP:NOTBURO violation to me, because we'd explicitly avoid fixing both problems at once. --Joy (talk) 07:50, 28 September 2024 (UTC)
Please don't put words into my mouth that I have not spoken. I suggested another venue so that editors who are interested can hash out the details of which template name is best to propose. Feel free to discuss a name change {{langx}} → {{<whatever>}} at any time and at anyplace but not here in this discussion. {{langx}} exists so a parallel TfD is an option. Agree on a better name and then start a TfD. All I want, here, is to avoid sidetracking this discussion (as we are doing now). If you do start another TfD, post a link to it here. Should this TfD conclude in the affirmative, I'm sure that implementation can be delayed until the conclusion of that rename TfD. There is no hurry.
I mean your proposal is to replace and delete this and the ultimate name has nothing to do with that, but it does, because before we delete lang-xx we have to replace all those transclusions with something, and if we use langx but people then want something else, then we have to do it twice, which is a ton of extra work for no tangible gain; choosing something first would prejudice the name choice later because most people would just say it's not worth the effort. If you think you were misunderstood, try being clearer next time. :) --Joy (talk) 10:51, 29 September 2024 (UTC)
Did I not write: {{langx}} exists so a parallel TfD is an option. Agree on a better name and then start a TfD. Did I not write: Should this TfD conclude in the affirmative, I'm sure that implementation can be delayed until the conclusion of that rename TfD. There is no hurry. The {{langx}} name will exist either as the canonical name or as a redirect to some other name. If this TfD concludes in the affirmative, the many upon many instances of the 1145-ish {{lang-??}} templates will not be switched overnight. There is time to adust the process even after it has begun. Can we stop having this discussion here? Please take it to Template talk:Lang or my talk page.
Support. Replacing all usages with {{langx}} and deleting the templates makes the most sense to me, and it'll greatly minimize headaches later on I guess. Yes, might be a pain in the arse to replace all the usages, but it'll even out long term (and fwiw I think {{langx}} is a very servicable name for it) 🔥HOTm̵̟͆e̷̜̓s̵̼̊s̸̜̃🔥 (talk・edits)23:49, 27 September 2024 (UTC)
It might not necessarily be such a pain! AutoWikiBrowser could semi-automate regex replacements of \{\{lang-({2,3}(?:-)*)\| to {{langx|$1| to be at least less fiddly.
This would obviously lean on the assumption that all {{lang-XX}} templates' {{#invoke:lang}} invocation work in the same way, so it'd need some testing still. Miaadatawitch!talk · contribs05:38, 28 September 2024 (UTC)
Alas, that regex doesn't work; try this (regex101.com is your friend):
\{\{ang\-({2,3}(?:-*)*)\|
But, even a working regex is problematic because it will find-and-fix templates that it ought not find-and-fix: {{Lang-sq-definite}}, {{lang-rus}}, {{lang-grc-gre}}, {{lang-zh}}; there are others.
I'm not sure why we're discussing implementation details already, but compiling a template-by-template list of replacements in an xml file to load into AWB seems like the least error-prone solution. 1234qwer1234qwer418:17, 28 September 2024 (UTC)
I would rather not discuss implementation details here. If you wish to discuss this further, please use my talk page or Template talk:Lang.
Support. Although there are not as many problems with the lang-?? templates as there used to be due to the modularization of the class of templates, issues still remain and the maintenance burden is unnecessary. Further, Trappist is one of the most experienced template maintainers on Wikipedia, if they think this is necessary, then it almost certainly is. Psiĥedelisto (talk • contribs) please alwaysping!02:03, 28 September 2024 (UTC)
Support; beyond converting things over this seems like the most elegant and headache-free approach. It would help to modify the relevant MoS entry when this is done too. No real objection to keeping it {{langx}} - it x-plicitly says the language name, which sets it aside from {{lang}}. Miaadatawitch!talk · contribs05:48, 28 September 2024 (UTC)
Will {{langx}} have presets for which languages to italicise and which not to, which to link and which not to, ...? I don't know if that's that much easier to maintain. 1234qwer1234qwer418:13, 28 September 2024 (UTC)
I wrote in the OP: {{langx}} uses the same rendering code as the {{lang-??}} templates so, given the same language tag and text, renders an identical output and using your {{lang-ymm}} as an example taken from Lower Shabelle:
Comment Do whatever it takes, but quickly, so as to remove the ugly "‹See Tfd›" markup in the articles. For the sake of sanity of old farts like me, I'd rather have old templates kept as redirects to preserve the old habits, but I can be taught simple new tricks, so this is not a big deal (unlike the urgency!). Full disclosure: I happen to know German a little bit, so I am one of the few ones being hurt. --Викидим (talk) 21:44, 28 September 2024 (UTC)
The convenient thing about the name {{langx}} is that it is only one letter different from {{lang}}. Yeah, converting {{lang-de|...}} to {{langx|de|...}} is a two-character change but most of those conversions will be done by automation. Quickly depends on the community. If this TfD gets relisted, it will be a while; if not, TfDs usually last a week or so.
Well, then I hereby beg the powers that be not to relist this TfD. IMHO the biggest issue here are the temporary stickers in the articles: since visually there will be no change (while I consider appearance of the current templates unsightly, I have no improvement proposals), I expect very little disruption. So I hereby Support the change for the sake of expediency. Викидим (talk) 03:24, 29 September 2024 (UTC)
Question about process: What's the advantage of immediately replacing and deleting such templates, as opposed to converting them to wrappers and eventually replacing and deprecating their use? Abrupt changes can be harder for human editors to adjust to. --Paul_012 (talk) 02:17, 29 September 2024 (UTC)
I don't understand. What would the wrapper be? What would it wrap? Give a real life example please because I'm having trouble imagining where the benefit of such a process lies.
IIUC, the wrapper would be to simply change the text of {{lang-de}} from {{#invoke:lang|lang_xx_italic|code=de}} to {{#invoke:langx|de}}. I don't see how that requires any "process" at all — anyone could go do that today, if they cared enough. After that, the process of search-and-replacing all lang-de's into lang's would be tedious, but mechanical and obviously a no-op, and again I wouldn't expect anyone to care about it. In fact, it really seems to me like there's no upside or downside to any of this fiddling: the code for these lang-foo templates is already shared in a single place ({{lang}}). Quuxplusone (talk) 16:09, 29 September 2024 (UTC)
Yeah, I thought about that but, like you, I couldn't see an upside ... to any of fiddling. And just a point of clarification, the sharing is not with {{lang}} but with Module:Lang which supports all of the {{lang}}, {{lang-??}}, and {{langx}} templates.
Support. Having a separate template for each language is an old way of doing things; if we now have ways to simplify the process by combining everything in one place, we should do that instead of grandfathering the old way. Bearcat (talk) 15:24, 29 September 2024 (UTC)
Support. This change makes perfect sense to me, and to be honest I never really saw a good reason to have all those separate language templates in the first place. GommehGaming101 (talk) 14:18, 30 September 2024 (UTC)
Support. Makes sense to me. I hadn't even heard of {{langx}} until now; I've always used the {{lang-..}} template just by copying it from existing pages. It seems rather cumbersome and duplicative compared to the universally applicable {{langx}}. I'll happily switch now that I know it exists! NLeeuw (talk) 14:45, 1 October 2024 (UTC)
Support – I wonder if there is some way to make the tfd notification badge only show up for those of us who care about it, similar to the way we can make cs1 ref errors show up in preview, or the thing that makes unreliable sources get highlighted in red. GA-RT-22 (talk) 17:47, 1 October 2024 (UTC)
Support merging but do not delete lang-xx templates. I would turn the lang-xx templates into wrappers of langx if only to not every instance of a lang-xx template in diffs turn into a redlink. –Fredddie™23:34, 1 October 2024 (UTC)
Moderate support. Unifying the templates appears to simply things and have no disadvantages. I'm saying moderate support because I'm not well-versed in this beyond reading the proposal and some of the discussion. The Quirky Kitty (talk) 13:45, 2 October 2024 (UTC)
Abstain I should note that personally writing the status quo template has become muscle memory, and I imagine for others It's a small difference and consistency is good, but why did this need to be changed? Langx is efficient but seems a little odd in form.--~Sıgehelmus♗(Tøk)01:22, 3 October 2024 (UTC)
In principle I support this simplification. If I understand correctly, lang-zh is exempted because it has additional parameters beyond just displaying the language in an html tag? What other languages are exempt? Japanese, presumably? Toadspike09:38, 3 October 2024 (UTC)
As for what to do with the old templates, I would suggest maybe redirecting the 100 most used and deleting the rest, but I suppose we'll cross that bridge when we come to it. Occidental𓍝Phantasmagoria18:56, 4 October 2024 (UTC)
Support for lang‑… templates that have a 1∶1 mapping of parameters to {{langx}}, i. e. you can essentially replace template names without any loss of information, oppose for other templates such as {{lang-zh}}. Comment: One could think of extending {{langx}} so a 1∶1 mapping {{lang-zh}} ↔ {{langx}} is achieved, but in the long‑term I’m afraid this will be a pain in the neck. ‑‑ K (🗪 | ✍) 04:44, 4 October 2024 (UTC)
If you know of any other {{lang-??}} templates that set |size=, tell me.
If you want to enable the TfD notification for {{Lang-ar}}, you are free to do so: change |type=disabled to |type=tiny. According to the High-use bot, the {{lang-ar}} notification will be visible on 46,000 (permalink) articles.
Support This would also make talk discussions and maintenance of documentation easier, grouping similar languages together e.g RTL or other non Romanized scripts. ~ 🦝 Shushugah (he/him • talk) 10:13, 5 October 2024 (UTC)
Support the replacement, per above. However, I think it is preferable to keep the lang-xx templates, indef protect them, and prevent their transclusion, so as to make older article revisions render without redlinks to these widely-used templates. Janhrach (talk) 12:33, 5 October 2024 (UTC)
Question. It seems this proposal will successfully pass. What will then happen with the original {{lang-xyz|}} templates? Will they be deleted, or redirected to the new template and protected? Thanks. - Darwinek (talk) 12:41, 5 October 2024 (UTC)
The title of this TfD is Replace and delete lang-?? templates, so, without a consensus mandate to do otherwise, the unused templates will be deleted.
Question: Is putting a link to this page really mandatory on every article which uses these templates? I’m sure language template discussion wouldn’t be of any importance to your average Joe. БудетЛучше (talk) 20:31, 5 October 2024 (UTC)
Hardly every article which uses these templates. The TfD notification is disabled for all but two {{lang-??}} templates: {{lang-de}} and {{lang-ru}}. Combined, those two templates are used on approximately 132,000 articles. I don't know how many articles use one or more of the {{lang-??}} templates. This search has returned results between 330,000 and 420,000 articles before timing out.
Oh. The language scope makes sense now, since most language/country/culture-specific articles I read are about Russian. БудетЛучше (talk) 16:19, 6 October 2024 (UTC)
Oppose deletion per Fredddie/Janhrach above; this would needlessly make old revisions harder to read. Surely there's a better alternative (e.g., redirecting to a template that would at least print the foreign-language word). No opposition to the rest of the proposal, though. Extraordinary Writ (talk) 00:18, 7 October 2024 (UTC)
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
Delete. Little to navigate between, contrary to the purpose of a navbox, and unlikely to grow in the future as articles on embassies are almost never notable. Geschichte (talk) 07:18, 28 September 2024 (UTC)
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.
The following is an archived discussion concerning one or more templates or modules. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template's talk page or in a deletion review).
2 of the 3 English links are up for deletion. The 3rd one for Japan is actually a link to the building rather than an actual embassy article. LibStar (talk) 00:32, 27 September 2024 (UTC)
The above is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the template or module's talk page or in a deletion review). No further edits should be made to this section.