Template talk:Non-English-language text category

Languages Template‑class

	Language portal This template is within the scope of WikiProject Languages, a collaborative effort to improve the coverage of languages on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LanguagesWikipedia:WikiProject LanguagesTemplate:WikiProject Languageslanguage
Template	This template does not require a rating on Wikipedia's content assessment scale.

extra space

please remove extra space after pipe of category or simply change "Category:Articles containing non-English language text| " to "Category:Articles containing non-English language text|". This extra space has made Category:Articles containing non-English language text this:)Ladsgroup^بحث 00:19, 5 July 2011 (UTC)[reply]

Done. --Closedmouth (talk) 15:26, 11 July 2011 (UTC)[reply]

Thanks:)Ladsgroup^بحث 04:25, 12 July 2011 (UTC)[reply]

Prohibition should be relaxed

The blurb text currently reads: "This category should only be added with the {{Lang}} family of templates, never explicitly." I don't think this is a wise prohibition. Sometimes the name is given in a foreign language before the English, thus making use of the {{Lang}} template inapproriate. In those instances, for the lack of a multilingual support template which covers such cases, we should be allowed to add this category directly to the articles, as is possible with other hidden maintenance categories such as Category:Year of birth missing. __meco (talk) 09:18, 20 April 2012 (UTC)[reply]

One reason to add categories manually is when nesting categories.--Error (talk) 18:15, 25 June 2021 (UTC)[reply]

LargeCategory TOC

Can someone modify this so that if the contents are larger then 3,000, {{LargeCategoryTOC}} is used instead of {{Category TOC}}? Vegaswikian (talk) 02:03, 19 June 2013 (UTC)[reply]

Template documentation

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please create template documentation of this article. --kwan-in (talk) 08:20, 12 October 2013 (UTC)[reply]

Done --Redrose64 (talk) 12:37, 12 October 2013 (UTC)[reply]

Miscategorisation

Some recent changes by Zyxw (talk · contribs) are putting categories inside themselves, for example Category:Articles containing Chinese-language text; Category:Articles containing Havasupai-Hualapai-Yavapai-language text; and Category:Articles containing Mohave-language text. --Redrose64 🌹 (talk) 09:41, 19 July 2017 (UTC)[reply]

@Redrose64: Thanks for pointing this out. It was caused by the {{Lang-x}} examples. I have fixed the three categories you mentioned and will fix any others that I find. -- Zyxw (talk) 10:54, 19 July 2017 (UTC)[reply]

Thank you --Redrose64 🌹 (talk) 19:49, 19 July 2017 (UTC)[reply]

Increase parameter count

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please provide a seventh parameter so that Category:Articles containing undetermined-language text doesn't truncate the last (sixth) entry: "Template:ISO 639 name und-lat." Thanks, --User:Usien6 17:28, 12 December 2017 (UTC)[reply]

By the way, if someone can figure out how the heck are some articles ending up in Category:Articles containing Undetermined-language text, (notice the miscapitalization) please reach me through my talk page… Thank you --User:Usien6 17:28, 12 December 2017 (UTC)[reply]

@Usien6:

Partly done I added the parameter, but have left the request open in case someone can answer your miscategorization question. — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ< 20:38, 12 December 2017 (UTC)[reply]

@Usien6: A one-character edit to Module:Language/data/iana languages would fix the "Undetermined" category name. I don't know if there would be side-effects, so I'll ping Trappist the monk, who has been working on the "lang" templates. -- John of Reading (talk) 07:21, 13 December 2017 (UTC)[reply]

Dear @SMcCandlish: Dear @John of Reading: Thank you for your prompt replies. The miscategorization issue is now fixed. The truncation of the seventh parameter is not, though. Even after purging. Please, reconsider, --User:Usien6 11:36, 13 December 2017 (UTC)[reply]

@Usien6: Should be fixed now? I edited {{Category articles containing non-English-language text/core}} and {{Category articles containing non-English-language text/inner core}} -- John of Reading (talk) 12:18, 13 December 2017 (UTC)[reply]

I missed something in sub-templates? Incontheivable! ;-) — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ< 14:07, 13 December 2017 (UTC)[reply]

Thank you It works fine, now --User:Usien6 15:53, 14 December 2017 (UTC)[reply]

Template name incorrect in examples

The template name is incorrect (in different ways) in each of the usage examples. DferDaisy (talk) 00:31, 24 July 2019 (UTC)[reply]

~/inner core

Template:Category articles containing non-English-language text/inner core is responsible for the right-floating box with the heading: "This category is indirectly triggered by the templates". I think that this is not true. None of the templates in Category:ISO 639 name from code templates that I inspected – just a few, there are 1100+ templates in that category – emit categories. Further, ~/inner core says:

This category should only be added with the {{Lang}} family of templates, never explicitly.

One last tidbit: there is a slow-burning move afoot to deprecate and remove all of the {{ISO 639 name <code>}} templates in favor of a single parameterized template {{ISO 639 name|<code>}} that uses Module:ISO 639 name (which shares data files with Module:Lang).

So the questions are:

Should ISO 639 language templates (individual or parameterized) categorize?
1. If yes:
  - Should the ISO 639 templates share the same categories as those purportedly reserved for {{lang}}?
    1. If categories should not be shared:
      - How shall the ISO 639 language categories be distinguished from the existing categories?
  - In view of the slow-burn move towards deprecation and removal, should implementation of categorization be deferred to the parameterized template?
2. If no:
  - Shall ~/inner core be edited to remove the right-floating box?

—Trappist the monk (talk) 16:46, 12 August 2020 (UTC)[reply]

Slow burn caught a gust of wind: Wikipedia:Templates for discussion/Log/2020 August 14 § ISO 639 name from code templates

—Trappist the monk (talk) 18:39, 14 August 2020 (UTC)[reply]

There having been no discussion, and because the TfD closed as delete, I have removed the right-floating box from Template:Category articles containing non-English-language text/inner core.

—Trappist the monk (talk) 23:51, 23 August 2020 (UTC)[reply]

template errors

Gonnym, are you aware that there are now 33 tranclusions of this generating an error. If not, see Category:Lang and lang-xx template errors. Thanks MB 17:41, 28 August 2020 (UTC)[reply]

Yes, and those are valid errors, which is why they are tracked. --Gonnym (talk) 17:58, 28 August 2020 (UTC)[reply]
Gonnym, it would be helpful if the language name were wikilinked so that the error message at e.g. Category:Articles containing Luba-Kasai-language text would read "Error: Luba-Kasai is not a valid ISO 639 or IETF language name." That would be helpful to people stumbling across the category for some reason.

Also, should the empty categories be speedy-deleted to clear that error category? I'm assuming that they are empty because categories with the "corrected" language name (i.e. matching the ISO's name, instead of Wikipedia's consensus name for the language, a possibly questionable choice that probably could have been discussed more) have been created and populated automatically by {{Lang}}. – Jonesey95 (talk) 04:00, 21 September 2020 (UTC)[reply]
@Jonesey95: If you notice Category:Articles containing Luba-Kasai-language text was created in 2016 and Category:Articles containing Luba-Lulua-language text (the one being used) was created in 2017, and neither by me. If you have any issue with these categories, please direct that at whoever did the change in 2017. My change only introduced the error message so these empty and redundant categories can be easily identified and deleted. And yes, these should be speedy as I'm slowly doing, but alone it takes me quite a while to verify each category is not a false positive. Added the language link as requested. --Gonnym (talk) 07:23, 21 September 2020 (UTC)[reply]

Misidentification of PIE

Category:Articles containing Piro-language text points to Piro language which is a disambiguation page. It should point to Piro Pueblo language. --Error (talk) 12:53, 19 January 2022 (UTC)[reply]

I believe Trappist the monk will be able to fix that. – Uanfala (talk) 14:46, 24 January 2022 (UTC)[reply]

Template working strangely at Category:Articles containing Kuman (Russia)-language text

This template is working strangely at Category:Articles containing Kuman (Russia)-language text. It links to the disambiguation page Kuman language instead of Kuman (Russia) language, which is what I would expect, given the category name. Compounding the confusion, there are two language articles claiming the ISO 639 code "qwm": Fergana Kipchak language (the redirect target for Kuman (Russia) language) and Cuman language. Can anyone here explain/fix any of this? This situation makes me think of the immortal Dire Straits line "Two men say they're Jesus; one of them must be wrong." – Jonesey95 (talk) 02:16, 22 January 2023 (UTC)[reply]

Fixed the categories Category:Articles containing Kuman (Papua New Guinea)-language text (kue) and Category:Articles containing Cuman-language text (qwm). Category:Articles containing Kumam-language text (kdi) does not need fixing; note the name 'Kumam', not 'Kuman'.

The articles that claim qwm will have to be addressed elsewhere; perhaps at Talk:Fergana Kipchak language and / or Talk:Cuman language or even better at Wikipedia talk:WikiProject Languages. The ISO 639-3 custodian defines qwm as 'Kuman (Russia)'.

—Trappist the monk (talk) 17:29, 22 January 2023 (UTC)[reply]

Looks good. I posted a note for the WikiProject. – Jonesey95 (talk) 17:53, 22 January 2023 (UTC)[reply]