Template:Expand French is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use ((edit template-protected)) to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories. Any contributor may edit the template's sandbox. This template does not have a testcases subpage. You can create the testcases subpage here.

I'd like to:

1. add "mil" -> "Military" into the "switch" statement to do the topics.
2. Add a default to pass the (({topic))} parameter through to the underlying ((Expand language)) template.

Category:Military articles needing translation from French Wikipedia does exist as a subcat of Category:Articles needing translation from French Wikipedia and this would help classification; with military precision it does seem to be used on many military history articles: search for "topic=mil" and await results. But that is not yet recognised by this template.

Certainly, passing the topic through to the underlying ((Expand language)) template seems reasonable for the default switch; it would save the need to ask for further edits to the template if the categories are augmented.

This should not break anything, at worst something erroneously classified as "topic=mil" would end up in a subcategory of how it is currently categorized (and thus by inheritance still be a member of that category). Si Trew (talk) 21:36, 24 October 2014 (UTC)[reply]

@SimonTrew: If you can get a userspace copy of this template with this changes you want working and tested, feel free to poke me and I'll put it in the real template. -- Beland (talk) 19:11, 11 December 2014 (UTC)[reply]

@Beland: thanks for replying I will do. The "default" case, that is to say the passthrough if it don't match any of the topics and is taken ias a lliteral string, I think should be on all of them. This should probably be somewhere at the gnomes who do categorizing, to make them aware and have their opinions, but my prima facia opinion would be that they would prefer they were stuck in subcats. WP:Category Sorting or somesuch? Si Trew (talk) 14:30, 12 December 2014 (UTC)[reply]

Having it just put the article into a category the name of which is derived from the "topic" parameter would make it easy for people to extend the list of topics without having to edit template. I don't see a need for a whitelist; an orphaned category sweep would find any misspellings. But I don't do any translation work, so if other people have opinions I defer to them. -- Beland (talk) 15:26, 12 December 2014 (UTC)[reply]

On the article Kahun Papyri, I have added Template:Expand German and Template:Expand French. While the German View link on "View a machine-translated version of the German article." works properly, the corresponding French View link does not. (I'm getting the error: The page you requested attempted to redirect to itself, which could cause an infinite loop. https://fr.wikipedia.org/wiki/Papyrus_d'El-Lahoun)

Both languages have something substantial to add to the article, yet they are quite different from each other. In other words, there is something different to be gained from each of the languages. Thinking that the problem may stem from having two expand templates at the same time, I tried switching the order of templates, French first, then German second, but the problem remained with the French template, only. Trying to go to Google Translate directly and submitting https://fr.wikipedia.org/wiki/Papyrus_d'El-Lahoun gets me the same error. I'm not certain if the problem is with Google Translate itself, or more likely, the French Wikipedia server. While I'll attempt to translate the article myself, I thought someone should know about the problem. Hi-storian (talk) 20:14, 23 January 2016 (UTC)[reply]

This tag should be at the bottom. There are tags that contain warnings about problems, such as poor formulations, lack of supporting references or questionable content. Such tags are important for the reader and should therefore be placed at the top. Other tags are more for administration of the improvements (editing) of the encyclopedia. These should not be placed at the top, where they disturb the reader. The tag most like this one is the stub. Such tags should be at the bottom of the article, as the stub tag is. This tag (Expand French) seems to normally be placed at the top. To repeat: This makes the encyclopedia less good than it would be with the tag at the bottom. --Ettrig (talk) 17:45, 30 August 2016 (UTC)[reply]

Hi @Ettrig: Thank you for placing this warning here. I (along with many other editors) never realized that the tag had to go at the bottom of the article. As you noticed, I made the line stating that bold in the template documentation. Have a great day! Daylen (talk) 17:42, 2 May 2017 (UTC)[reply]

Unfortunately, for a long time, the consensus among the users was to put this template at the top. As I explained above, I think that is a bad variant. So it is not a fact that it "had to go to the bottom". But since the new instruction has now stood for quite a while, and since my changing campaign has met so little resistance, maybe we can now say that the tide has swung. I am very happy that you seem to agree with me on where this template should be placed. --Ettrig (talk) 05:11, 3 May 2017 (UTC)[reply]

"...and since my changing campaign has met so little resistance..."

*cough*       *cough*

• Template talk:Expand language#EW left unapproved doc change in place
• Template talk:Expand language#Attempts to change the placement of expand language templates without consensus
• User talk:Ettrig#Please stop repositioning language templates immediately
• edits to Template:Expand language/howto revs: 736868908, 738299129, 738320908, 738386778, 738410553, 738410819, 738476519.
• WP:ANI#User:Ettrig

*cough* Mathglot (talk) 02:02, 18 June 2017 (UTC)[reply]

Yes, this is exactly what I mean. A lot of words but very little discussion. In the examples above, I answered every argument. But there were very few. When the discussions died out, I continued changing. As there was no consensus, it should not be considered wrong to do so. --Ettrig (talk) 15:09, 19 June 2017 (UTC)[reply]

Consensus can be observed, even if not stated. In practice, the template has been placed at the top, even during the period between 2012 and 2014 when it was "supposed" to be in the "references" section. — Arthur Rubin (talk) 03:02, 20 June 2017 (UTC)[reply]

• Why would it be placed at the bottom? There is a reason it is used and it is because of issue(s) with the entire article that make the French article a significantly better source of info. This is perfectly appropriate to be signaled to the reader. Just like any other template, I appreciate it that it's placed at the top. In my opinion, the only thing that should go at the bottom should be stub templates, which are appropriately small. —Мандичка^YO 😜 07:43, 10 April 2018 (UTC)[reply]

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

Change the German example on this (and on all other foreign-language expansion templates to their respective languages) to French. 𝕎𝕚𝕜𝕚𝕎𝕒𝕣𝕣𝕚𝕠𝕣𝟡𝟡𝟙𝟡 (talk) 12:53, 14 October 2019 (UTC)[reply]

 Not done: According to the page's protection level you should be able to edit the page yourself. If you seem to be unable to, please reopen the request with further details. To change the documentation page, ensure you navigate to Template:Expand French/doc or similar. Izno (talk) 13:19, 14 October 2019 (UTC)[reply]

Izno, WikiWarrior isn't a template editor... I'm blind, sorry. --Trialpears (talk) 13:32, 14 October 2019 (UTC)[reply]

@Trialpears: His edit request isn't clear. I interpreted it as a request to change the documentation. Does he want the Content in this edit is translated from the existing German Wikipedia article at [[:de:Exact name of German article]]; see its history for attribution. changed? The correct location to request that change is Template:Expand language, the change for which is not obviously trivial and will require some more discussion prior to the edit request (specifically both a consensus generation discussion and a discussion as to proposed implementation). --Izno (talk) 13:38, 14 October 2019 (UTC)[reply]

(edit conflict) Yep realized the same and edit conflicted with you. I will be looking into adding an override to ((Expand language)) shortly. --Trialpears (talk) 13:41, 14 October 2019 (UTC)[reply]

@Izno and Trialpears: No, that's not what I mean. I mean change the German example in this article to a French example, change the German example in Template:Expand Spanish to a Spanish example, etc. 𝕎𝕚𝕜𝕚𝕎𝕒𝕣𝕣𝕚𝕠𝕣𝟡𝟡𝟙𝟡 (talk) 12:13, 15 October 2019 (UTC)[reply]

@WikiWarrior9919: Please provide the exact text you want to change. --Izno (talk) 12:15, 15 October 2019 (UTC)[reply]

Change this... :

A model attribution edit summary (using German): Content in this edit is translated from the existing German Wikipedia article at [[:de:Exact name of German article]]; see its history for attribution.

...to this:

A model attribution edit summary: Content in this edit is translated from the existing French Wikipedia article at [[:fr:Exact name of German article]]; see its history for attribution.

...and so on for all the other foreign-language templates. 𝕎𝕚𝕜𝕚𝕎𝕒𝕣𝕣𝕚𝕠𝕣𝟡𝟡𝟙𝟡 (talk) 12:17, 15 October 2019 (UTC)[reply]

You must wait for the parent template to be worked. Izno (talk) 16:01, 15 October 2019 (UTC)[reply]

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

In the third to last bullet there's a missing colon or "is" after "a model attribution edit summary". Danstronger (talk) 13:33, 10 November 2021 (UTC)[reply]

 Done Change made to Template:Expand language at Special:Diff/1054749378. User:GKFX^talk 21:54, 11 November 2021 (UTC)[reply]

Template:Expand language has an RFC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. --N8_wilson 11:56, 5 June 2022 (UTC)[reply]

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

Should include the standard aliases "cult" and "transp" for Culture and Transportation topics. Numberguy6 (talk) 16:52, 25 January 2023 (UTC)[reply]

 Completed. P.I. Ellsworth , ed. ^put'r there 00:57, 26 January 2023 (UTC)[reply]

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

Description of suggested change: Since there are 18 subcategories within the Geography topic category, we should add the topics to the template, under topic codes such as "geo-fr", "geo-ca", etc. instead of having to add the categories to the pages manually. And we should remove geo-by-country cats for non-French-speaking countries, since those are never going to have more than a few

Diff:

Numberguy6 (talk) 02:50, 24 March 2024 (UTC)[reply]

A few questions:

1. The new list has 32 added geo tokens, but the geography category only has 18 subcats, as you've mentioned. Can you explain the larger number?
2. Have you thought about the rendering of the table at § Topics and categorization, and how you envision that changing? Or, would you do it as a second table? Bear in mind that this table is generated automatically by templates ((Expand language/howto)) and ((EL table row)). I'm somewhat concerned with having a really long table in the doc, but maybe there's a way around that.
3. If envisioned as more of an exception limited to French (and maybe a small handful of other languages), then maybe it could be handled as an exception, the way commune is now using the supplemental data file ((Expand French/topics)), which afaicr, is the only such special token defined for any Expand language, but things may have changed since last I looked. If envisioned as a new overture to create subtemplates of existing token-categories that might spread across a lot of languages, then maybe updating/howto and table row would be better. At first blush, I might go with the former to start with, even if the ultimate goal is the latter.
4. This question is more of a long-range concern, but a while back, I looked into the possibility of combining all of the Expand language templates into a single template (the way it should've been done in the beginning) and convinced myself that it was possible to do but would be very tedious, sort of along the lines of what Primefac did when combining all of the dozens of separate templates per language into one ((Family name hatnote)) template, possibly even worse than that one. The only reason I mention this now, is that if we move on this edit request, whatever solution we come up with should not make merging all of the Expand LanguageName even more difficult than it already would be, or impossible.

Thanks, Mathglot (talk) 06:38, 24 March 2024 (UTC)[reply]

A further question:

5. Looking at § Topics and categorization, if geo has 18 subcats, the special topic commune has 84! That definitely seems a lot more than what I remembered. In any case, would you propose to do something similar with that, with sub-subtopics for the communes, or is that a different situation? Or should we simply defer that, and do that in a separate edit request, or perhaps not at all?

Thanks. Mathglot (talk) 07:47, 24 March 2024 (UTC)[reply]

1. I put every French-speaking country to the list. There are a lot of articles that aren't sorted, and that don't have the Expand language template added yet.
2. We could have a collapsible table.
3. I think this exception could also be applied to other languages with thousands of articles (e.g. German).
4. I have not thought about that.
5. I have not thought about that.

Numberguy6 (talk) 17:23, 24 March 2024 (UTC)[reply]

Deactivating edit request as the proposer is now a template editor. * Pppery * _{it has begun...} 04:16, 13 April 2024 (UTC)[reply]