Wiktionary:Grease pit/2015/September

Double RSS posts

Hello. I, the only person who uses RSS, would like to mention that each WotD seems to get posted twice on your feed (https://en.wiktionary.org/w/api.php?action=featuredfeed&feed=wotd&feedformat=atom). While I'm here, this also seems to happen to the Commons PotD feed (https://commons.wikimedia.org/w/api.php?action=featuredfeed&feed=potd&feedformat=atom&language=en) but not the FWotD feed. Anyway, sorry if this is the wrong place for technical complaints or if saying 'feed' too many times has made you hungry. Thanks! EDIT: FWotD doing this too btw. — This comment was unsigned.

User:Yair rand/newentrywiz.js should not link to elements in a head word

This now redundant (or usually redundant) as headword modules automatically link to individual words of multi-word terms. Renard Migrant (talk) 15:01, 1 September 2015 (UTC)[reply]

Fixed. --Yair rand (talk) 21:14, 1 September 2015 (UTC)[reply]

Latvian adjectives with missing headers

There are about 2300 Latvian adjective entries with two headword lines, for two homographs, where the second headword-line is not preceded by a header. It should be straightforward to find and fix all such entries: find adj}}\n\n\{\{head\|lv\|adjective form}} and replace }\n\n\{\{head\|lv\|a with }\n\n===Adjective===\n{{head|lv|a (some entries have been fixed since the last database dump; the initial }\n\n\{ weeds those out). (If needed I can supply an outdated list of ~2600 such entries, of which a few hundred have been fixed.) Can someone with a bot do this? - -sche (discuss) 04:56, 2 September 2015 (UTC)[reply]

You overcomplicated the matter. Regex is not needed - a simple replace from

adj}}\n\n\{{head|lv|adjective form}} to

adj}}\n\n\===Adjective===\n{{head|lv|adjective form}}

does the job...--Dixtosa (talk) 17:20, 2 September 2015 (UTC)[reply]

Module:la-noun, a certain section not showing up, and irrelevant edits

I recently added a ‘verbal nouns’ row to Module:la-verb so that verbal nouns derived from Latin verbs would be shown in the verbs' conjugation tables. I noticed, however, that for certain verbs, such as abeo and indico (in both senses), it simply wasn't showing up when it should have been. I thought it might have been the result of sloppy coding, but I noticed that after I made minor edits to different sections of the section for Latin on each page, it started showing up (sure enough, if I went to edit each conjugation table and hit ‘Show preview’, it would show up as well). What's going on here? Esszet (talk) 21:21, 3 September 2015 (UTC)[reply]

It sometimes takes a little time for each page that uses the template to get updated. Another thing you can do is purge the page (if you have the clock enabled in Preferences > Gadgets > User interface gadgets, then you can purge the page by clicking the clock). --Wiki Tiki 89 21:30, 3 September 2015 (UTC)[reply]

Automated program to clean up names of minerals

Equinox created a large number of entries for minerals in this format. Although obviously each entry could use human attention, all entries of this kind could use two easy fixes: change the link to -ite into {{suffix||ite|lang=en}} (so at least it categorises) and change the context label from "mineralogy" to "mineral" (which displays the same way but again, categorises the entry correctly). Would anyone be willing to run this? —Μετάknowledge^{discuss/deeds} 05:42, 4 September 2015 (UTC)[reply]

"Aliases" in HotCat

Is it possible/desirable to modify HotCat to handle "aliases", without slowing it down too much? For instance, as discussed in WT:RFM#Category:Occupations, it would be useful if someone could type "Professions" and HotCat would know to convert that to "Occupations", or might at least add "Occupations" to the popup "autocomplete" list of categories you might be thinking of. It might also help with people not knowing whether to add "Category:American English" (if someone had to add it manually for some reason) or "US English" and things of that sort. - -sche (discuss) 03:35, 6 September 2015 (UTC)[reply]

Category:Eastern English

This category is strange, and is probably the result of a recent change in Lua. Any ideas how to fix it? --Zo3rWer (talk) 20:48, 7 September 2015 (UTC)[reply]

It's a result of "east" and "eastern" being defined in Module:labels. When and why did they creep in? They seem too broad to be useful. Are they useful, or can they be removed? If they're kept, the short-term solution seems to be to add "eastern Pennsylvania" etc as an alias to "Pennsylvania" and then change "lunch kettle" etc to use "eastern Pennsylvania" rather than "eastern|_|Pennsylvania", the way "NYC" is currently an alias of the "New York" state label (because I didn't think there were enough NYC-specific words to merit separating them from NY state's words).

CodeCat recently did something that created a whole bunch of these categories, things like Category:Javanese English when people referred to the Java programming language in {{context}}, and awkward constructions like Category:North Korean Korean instead of Category:North Korean. I'm reluctant to create categories for these oddities, so Special:WantedCategories is full of them. Chuck Entz (talk) 21:14, 7 September 2015 (UTC)[reply]

Why not create the silly things and make then subcategories of something? I intend to do something similar for all of the pages that are "wanted" more than 50 times. DCDuring TALK 22:26, 7 September 2015 (UTC)[reply]

No, they should certainly not be created but instead dealt with, especially situations like Category:North Korean Korean that are splitting categorisation messily. @CodeCat —Μετάknowledge^{discuss/deeds} 04:29, 9 September 2015 (UTC)[reply]
The problem is very general: top down creation of categories, often of excessive fineness and often using generic categories without regard to how individual topics, languages, PoSes, etc are subcategorized in the world outside of Wiktionary. It seems that we are doing violence to reality to reduce it to something that we can have an "elegant" (read simple) technical solution for. In light of the apparently insufficiently flexible architecture, I am skeptical that the problems will actually be solved rather than minimally patched. The silly categories could be created and subcategorized into some kind of category of shame, with sensibly named categories inserted manually. I suppose we have to appreciate that the straitjacket imposed by our systems doesn't cause even more silliness and awkward wording. DCDuring TALK 11:28, 9 September 2015 (UTC)[reply]

Category:English words suffixed with -o-

This is a MewBot-created category, three of whose four entries are my fault. How should -o- be correctly indicated, so that the category can be deleted? @CodeCat —Μετάknowledge^{discuss/deeds} 23:39, 7 September 2015 (UTC)[reply]

Presumably the same as the other categories in Category:English words by infix. DTLHS (talk) 00:09, 8 September 2015 (UTC)[reply]

@DTLHS: But it's an interfix, not an infix, and we wouldn't want it to behave like one either. —Μετάknowledge^{discuss/deeds} 04:28, 9 September 2015 (UTC)[reply]

@Metaknowledge: See Category:English words by interfix then. --Wiki Tiki 89 14:42, 9 September 2015 (UTC)[reply]

Quick Accel question

Typical situation: there is an {l} wrapped in an #if to display an mdash if there is nothing to put in the {l}, otherwise display the term in the {l}.

Is it better to wrap the WT:ACCEL spans specifically around the {l} (inside the #if) or it doesn't matter and they can be wrapped around the whole thing? (I kind of suppose there is absolutely no diff but wanted to check.) Neitrāls vārds (talk) 12:02, 8 September 2015 (UTC)[reply]

Just use {{head}}, it does all these things automatically. —CodeCa t 15:26, 13 September 2015 (UTC)[reply]

CodeCat, I forgot to mention that this was in the context of inflection tables as opposed to headword line (and my orig. question can probably be disregarded altogether as there's probably zero difference.)

Also, can you add this to that page: User talk:Conrad.Irwin/creationrules.js#Please add (Moksha, Erzya, Latvian (nouns)? Or perhaps simply unprotect it, as I don't see how that page could have any appeal to vandals. Neitrāls vārds (talk) 22:55, 16 September 2015 (UTC)[reply]

For JavaScript, the protection is built in to the software and can't be taken off. That's a good thing too, because running scripts on a user's computer has a HUGE appeal to vandals. —CodeCa t 23:31, 16 September 2015 (UTC)[reply]

Min Nan "o͘"

In POJ there is a letter that looks like an o with a dot at the upper right. Wikipedia uses o + combining character "U+0358 combining dot above right" (o͘), but on Wiktionary it is a mixture of either the above or o + "U+00B7 middle dot" (o·). This leads to issues like 圖#Pronunciation (tô͘; combining dot above right) not properly linking to tô· (middle dot), and red links that point to o·-bá-sáng (middle dot) and not o͘-bá-sáng (combining dot above right). Is there a way to fix this with a bot? —suzukaze (t・c) 04:23, 12 September 2015 (UTC)[reply]

Well theoretically that set of characters could appear in other valid contexts, so a bot probably wouldn't work. I can get you a list of pages and page titles where it occurs though. DTLHS (talk) 04:35, 12 September 2015 (UTC)[reply]

@suzukaze-c User:DTLHS/cleanup/min nan o DTLHS (talk) 05:00, 12 September 2015 (UTC)[reply]

Cool. I forgot to mention that there can also be tone markings on the o͘ (ô͘, ó͘, ò͘, ō͘). I suppose they'd become "ô·, ó·, ò·, ō·". —suzukaze (t・c) 05:09, 12 September 2015 (UTC)[reply]

Alright, I can look for all of them. DTLHS (talk) 05:19, 12 September 2015 (UTC)[reply]

As DTLHS says, a bot might not work (perhaps if it were restricted to only editing spans tagged as Min Nan?); however, you could go through the list with AWB — that would probably be faster than going through it by hand. - -sche (discuss) 05:44, 12 September 2015 (UTC)[reply]

i've never been able to get awb to work on this computer —suzukaze (t・c) 05:59, 12 September 2015 (UTC)[reply]

The remaining instances relevant to Min Nan are mostly in the links to other-language Wiktionaries; should the links be removed? —suzukaze (t・c) 02:54, 14 September 2015 (UTC)[reply]

Category tree bug

It looks like {{poscatboiler}} is not correctly subcategorizing by-language meta-categories. E.g. Category:One-letter words by language is turning up under Category:Terms by lexical property by language, and not under Category:Character counts by language; or Category:Terms derived from DC Comics by language is turning up under Category:Terms by etymology by language, and not Category:Terms derived from fiction by language. --Tropylium (talk) 15:16, 13 September 2015 (UTC)[reply]

I don't see Category:One-letter words by language in Category:Terms by lexical property by language. —CodeCa t 15:25, 13 September 2015 (UTC)[reply]

It wouldn't, because the change in the output of {{poscatboiler}} wouldn't propagate through to the categories without an edit. I just did a null edit on Category:One-letter words by language, and you should be able to see it in Category:Terms by lexical property by language now. This seems to be a case of all the intermediary links in the chain being skipped for umbrella categories, but not the language-specific ones. Chuck Entz (talk) 15:56, 13 September 2015 (UTC)[reply]

I still don't see it, no matter how many null edits I do. —CodeCa t 16:36, 13 September 2015 (UTC)[reply]

I figured out where the disconnect is: the category in question is actually Category:Terms by lexical property subcategories by language. The confusion lies in the fact that the breadcrumbs are completely different for the umbrella categories as opposed to the language-specific ones, so it's easy to overlook that the one similar-looking part is different, too. If this restructuring was intentional, it wasn't handled very well. Everyone is used to the umbrella categories and the language-specific categories having exactly the same tree structure, so the obvious conclusion is that this is a bug. Chuck Entz (talk) 20:42, 13 September 2015 (UTC)[reply]

The "by language" categories never had umbrella categories, they always went into their own lumped-together category. Formerly, this category was decided by the specific category template being used, but then we merged them so it's just part of the data modules. The only exception has been the topical category tree, where the umbrella categories follow a structure parallel to the language-specific ones. —CodeCa t 21:02, 13 September 2015 (UTC)[reply]

Thorndyke and others

A male surname? I think a template or module needs editing. SemperBlotto (talk) 15:40, 15 September 2015 (UTC)[reply]

Nope, just Wonderfolly. --Zo3rWer (talk) 15:45, 15 September 2015 (UTC)[reply]

By the way, in Czech, there are male and female surnames. --Zo3rWer (talk) 15:47, 15 September 2015 (UTC)[reply]

Not really, if it's anything like Russian: the surnames themselves are genderless, but there are male and female forms that match the gender of the person named (a man would be called by the masculine form, and a female would be called by the feminine form). It's very much like adjective gender in any number of languages: you say sabio for a man, sabia for a woman, and loco for WF... Chuck Entz (talk) 01:54, 16 September 2015 (UTC)[reply]

It seems the Wikipedia article Grammatical gender in Spanish forgot to mention the WF gender. Maybe it's too advanced a topic for an online encyclopedia. But back to the topic (or rather, the previous digression): Some people, even for Russian, consider male and female surnames to be separate lemmas, but I cannot agree with this view (after all, a brother and a sister really have the same last name). --Wiki Tiki 89 02:00, 16 September 2015 (UTC)[reply]

I'd consider the feminine forms to be inflected forms of the masculine, just as with adjectives. —Aɴɢʀ (talk) 13:39, 16 September 2015 (UTC)[reply]

I seem to remember, when researching my Viking roots, that I have seen Norwegian surnames ending in -dottor as well as in -son. Would that be similar to the Russian usage? SemperBlotto (talk) 13:55, 16 September 2015 (UTC)[reply]

In some ways. In Russian the distinction is grammatical (for example, a surname ending in a consonant for the masculine nominative will usually have an -а added for the feminine nominative), but the Norwegian distinction of -son and -dottir is semantic, since these suffixes literally mean "son" and "daughter". The best way for you to understand the Russian system is with plurals, since English also sometimes pluralizes surnames (the Joneses) and in Russian, plural is just another gender/number class that also applies to surnames; thus, the same way you would use the plural form of a surname to refer to a family, you would use the feminine form of a surname to refer to a female member of the family. --Wiki Tiki 89 14:13, 16 September 2015 (UTC)[reply]

template R:L&S

Could someone please explain how this template works and show me where its parameters are explained? It seems one can but doesn't need to add the lemma e.g. R:L&S|pŏpŭlus. And why does it not work with that word? It should link to http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.04.0059%3Aentry%3Dpopulus1 --Espoo (talk) 20:10, 16 September 2015 (UTC)[reply]

You just need to look at the template's documentation. The first parameter is displayed, the second is the page name on Lewis & Short. I have fixed the usages on populus. SemperBlotto (talk) 20:22, 16 September 2015 (UTC)[reply]

Thanks for fixing that. My naive expression was in fact asking where the documentation is, but i found it now. It'd be nice if your fix could be used to better explain what the template's documentation unsuccessfully tries, and instead now uses the unhelpful and confusing expression "search term". In fact i wouldn't have understood your explanation either without the example since i would never have guessed that the lemma's page name on L&S is populus1.

This is probably the wrong place to ask for help with editing, but could you fix my edit "rare" as a label for the rare variant "adagio" on adagium? --Espoo (talk) 20:53, 16 September 2015 (UTC)[reply]

Module:pl-IPA (or maybe modules in general?)

I'm trying to edit Module:pl-IPA, and I've noticed that when I try to do so, characters are occasionally entered one space behind that occupied by the cursor. I've never encountered this problem with other modules, but I highly doubt it would be specific to this one; is anyone else having this problem in this module or in any others? I'm using Safari on OS X 10.10.5. Esszet (talk) 17:20, 17 September 2015 (UTC)[reply]

Yes, I've noticed this when dealing with some Unicode punctuation. You can always do your editing offline and then copy and paste it in though. DTLHS (talk) 17:53, 17 September 2015 (UTC)[reply]

I did in spite of that what I wanted to do…can it be fixed? Esszet (talk) 22:33, 17 September 2015 (UTC)[reply]

@DTLHS Can it? Esszet (talk) 20:02, 20 September 2015 (UTC)[reply]

Template:rfdef

Shouldn't this template also put articles in a category, like Category:Requests for definition? Purple backpack89 20:25, 17 September 2015 (UTC)[reply]

It does- maybe you have hidden categories turned off? Category:Italian entries needing definition DTLHS (talk) 22:44, 17 September 2015 (UTC)[reply]

Accelerated entry creation broken again?

Some time around midday today Seattle time, green links stopped appearing. I was in the middle of creating several Japanese entries when this happened, and I was using the green links to accelerate the creation of hiragana and romaji entries.

I just checked the history at User:Conrad.Irwin/creationrules.js, which I think is the right code, and nothing has changed today. Can anyone help explain what's going on with our infrastructure, and (better yet) fix it? ‑‑ Eiríkr Útlendi │^{Tala við mig} 00:01, 18 September 2015 (UTC)[reply]

CodeCat made an edit based on code written by Neitrāls vārds, which broke all accelerated creation links; I then reverted the edit. (There's a discussion about this at the Tea room currently.) Green links appear to be working again, but not for Japanese, AFAICT, which is odd. Perhaps they can sort this out. —Μετάknowledge^{discuss/deeds} 04:06, 18 September 2015 (UTC)[reply]

What's even weirder, they were working, then CodeCat's edit happened and they didn't work, then you reverted and they did work, then *something* happened on some other page entirely and they stopped working again. “WTF” is the general impression I'm left with. Our infrastructure seems entirely too fragile. ‑‑ Eiríkr Útlendi │^{Tala við mig} 16:49, 18 September 2015 (UTC)[reply]
Ooookay... Accelerated entry creation for Japanese appears to be mostly working, except in a few oddball corner cases.

Could someone have a look at 什麼#Japanese, elucidate why accelerated entry creation isn't working for the hiragana and romaji spellings listed in the POS headline, and fix the issue? ‑‑ Eiríkr Útlendi │^{Tala við mig} 21:53, 18 September 2015 (UTC)[reply]

I still can't figure this out. Once again, pinging @CodeCat, Neitrāls vārds —Μετάknowledge^{discuss/deeds} 22:28, 18 September 2015 (UTC)[reply]

English plurals and "These entry templates may help when adding words"

The "Plural" button on Special:Search creates pages in the obsolete Category:English plurals category. —suzukaze (t・c) 20:51, 20 September 2015 (UTC)[reply]

Fixed in diff. Enosh (talk) 12:24, 21 September 2015 (UTC)[reply]

`edittools` borkage: newlines now non-functional

As a New! IMPROVED! bug that just started appearing today, newlines included in my User:Eirikr/edittools page no longer render correctly in the edittools dialog, nor do they insert correctly when using the edittools dialog, appearing as the black-diamond � character instead.

What is going on here? ‑‑ Eiríkr Útlendi │^{Tala við mig} 04:07, 21 September 2015 (UTC)[reply]

Category for pjt-conj-la

Somebody ought to add a category to the template {{pjt-conj-la}}. --Lo Ximiendo (talk) 21:50, 21 September 2015 (UTC)[reply]

And {{pjt-conj-ra}} and {{pjt-conj-wa}}. --Lo Ximiendo (talk) 22:10, 21 September 2015 (UTC)[reply]

Added to Category:Pitjantjatjara verb inflection-table templates based of usage. Enosh (talk) 07:25, 22 September 2015 (UTC)[reply]

Broken Latin templates

Entries such as omnis, vulgaris, officinalis, and benghalensis are currently showing a whole lot of wikicode where the declension table is meant to be. It's hard to tell who or what broke it. Is anyone working on fixing this? @CodeCat? @JohnC5? —Pengo (talk) 02:50, 22 September 2015 (UTC)[reply]

Fixed now. Thanks. —Pengo (talk) 10:01, 22 September 2015 (UTC)[reply]

Also, is there a reason we have so much redundant wikicode in Module:la-adj/table? We ought to be keeping templates in the Template: namespace and calling frame:expandTemplate to use them (as I've done in Module:la-utilities). If la-adj/table was actually simplifying or generalizing something it might make sense, but it's just a text dump of a template into code, which offers little advantage and makes it much more difficult and error prone to edit. —Pengo (talk) 02:50, 22 September 2015 (UTC)[reply]

How would you handle the conditional inclusions? —CodeCa t 19:50, 22 September 2015 (UTC)[reply]

@CodeCat: [ping @Esszet] I kind of didn't want to reply because I didn't want to prescribe how to code when I'm not doing the coding, but I've been thinking about it, so these are just suggestions. Do what you like. But here's four possible ways I'd do it which I think are preferable to having a large block of wiki code in lua:

Use the conditionals that already exist in wiki template syntax, or better yet, just use the existing high-level table templates (the ones which are used by other templates. These meta-templates is what I'll be referring to as just "templates" here). They might be a little ugly, but at least you don't have wrap all your wiki code inside Lua with \n's and quotes and stuff. And the templates are arguably clearer and easier to edit by mere mortals, or at least understandable by a large existing user base who already grok the wikicode template syntax. This is what I've done in Module:la-utilities. It uses frame:expandTemplate (search for it) to show the template using the exact same generic templates as the old way. e.g. {{Template:la-decl-noun-table}}
A different approach: Do it all in lua, but follow the Don't repeat yourself mantra: e.g. supply with table-building function with a list of column and row headings, store formatting code in strings or functions which get re-used, and generate the table by looping through the rows and columns without repeating the the same wikicode over and over. This would be the most flexible approach. It would allow the same code to generate many kinds of declension tables, and you'd only have to work out how to do tricky things like footnotes once. This would probably be my preferred eventual approach but would take more effort to set up, and could make the templates more difficult to edit if the resulting framework wasn't flexible and easy to use.
Or: Remove the conditionals entirely. In this case, the meta-template would be clearer if the locative row was always visible, but its value was a dash (—) to show that it doesn't have that declension. You could then make clean version of a template like {{la-decl-noun-table}} with no conditionals at all (as it would only be fed clean data from lua) (Personally, showing an empty locative row would be my preferred visual style regardless of which technical approach is taken, and I've thought that pre-lua, not just as excuse to code in a different way).
If you really want to have the locative still be optional though, split the meta-templates in two: create a new template which contains the locative declension and one which doesn't. e.g. create a {{la-decl-noun-table-loc}} which always shows the locative row while using a different template when it's not to be shown. Advantage of being editable by anyone with zero lua coding and simpler wiki-syntax (it shouldn't even need messy {{#if:{...}}} if it's fed clean data from lua), disadvantage of creating more redundancy / similar templates. However, compared to the zillions of templates we need currently, it doesn't seem that bad. I originally only included this option for completeness, but it doesn't seem that bad now that I think about it.

Take whatever approach you like, but I hope these are helpful suggestions. If it works already, refactoring to something more elegant probably isn't a huge priority. Happy coding. —Pengo (talk) 07:30, 12 October 2015 (UTC)[reply]

Turn italic into normal in CategoryTree

The documentation of Template:table:chess pieces/en uses #CategoryTree to display a list of similar categories at the end of the page. (chess pieces, colors, suits, etc.) That list is in italic, can it be normal (as in, font-style: normal;)? I tried editing MediaWiki:Common.css but was unable to do it. --Daniel Carrero (talk) 19:15, 22 September 2015 (UTC)[reply]

@Daniel Carrero

body[class*="page-Template_table"] .CategoryTreeLabel {
	font-style:inherit;
}

should work —suzukaze (t・c) 07:06, 28 September 2015 (UTC)[reply]

and possibly

body[class*="page-Template_table"] .CategoryTreeLabel:before {
	content:"•";
	padding-right:0.75em;
}

for fake css bullets because the plain list is plain —suzukaze (t・c) 07:09, 28 September 2015 (UTC)[reply]

It works when I use that CSS code on Special:MyPage/common.css, but it does not work when I use the same code on MediaWiki:Common.css (diff). Why is that? --Daniel Carrero (talk) 19:48, 28 September 2015 (UTC) Nevermind, working great! Thanks! --Daniel Carrero (talk) 21:53, 28 September 2015 (UTC)[reply]

extending sh-noun and other templates for multiple head parameters

Could someone extend the sh-noun and other sh-* templates to work with multiple head parameters like it was done to sh-proper noun? It doesn't seem particularly complicated but I don't want to mess anything up as I'm not familiar with MediaWiki's templating syntax. Thanks. Fojr (talk) 15:15, 23 September 2015 (UTC)[reply]

Declension tables and multimedia objects

It seems that declension tables cannot be placed horizontally in line with multimedia objects (see here). I'm using Safari on a Mac; could this be the same bug as that which causes there to be a gap between the language header and the first sub-header underneath it when there's a FWOTD template along with a multimedia object between them in the source code (see here)? Esszet (talk) 14:56, 25 September 2015 (UTC)[reply]

Fixed: diff. As you can see, it is not declension tables in general, but specific templates that for some reason added clear: both to their CSS. You will likely have to fix this in other Slovak declension templates. --Wiki Tiki 89 15:47, 25 September 2015 (UTC)[reply]

template:poscatboiler

This template needs repair (or something).

See Category:List templates for use of {{poscatboiler|en|list templates}}. DCDuring TALK 04:53, 28 September 2015 (UTC)[reply]

What seems to be the problem? {{poscatboiler}} works well with Category:English list templates, which are templates with specific lists of words in English. Category:List templates uses the same name but is for a few random templates that do something else, including some code for formatting different types of lists. I suggest renaming it to something else or just dumping the contents into Category:Templates in case the category is not very useful by itself. --Daniel Carrero (talk) 05:20, 28 September 2015 (UTC)[reply]

Sorry, I meant Category:English list templates. The supplementary lists, often very useful, for oldest edited member of the category and newest additions to the category are empty in fact whereas there certainly should be members. DCDuring TALK 06:41, 28 September 2015 (UTC)[reply]

True, I see the problem now. There is an extension called DynamicPageListEngine that would help with that, which has been mentioned in a previous discussion about this problem. I created Wiktionary:Votes/2015-09/Installing DynamicPageListEngine to propose installing it; the vote explains how it would fix the problem, too. --Daniel Carrero (talk) 19:22, 29 September 2015 (UTC)[reply]

'Summary' namespace

Yes. There's a "Summarize" link above every thread. Clicking on it opens an edit window for creating a Summary-namespace page. The text from that page then gets displayed after the words "Thread summary:" in the first message of the thread. It does look like nobody has used this feature in quite a while, though. Chuck Entz (talk) 01:35, 30 September 2015 (UTC)[reply]

No category in Russian for Orthodox Christianity?

I was surprised to find out there's no such thing as Category:ru:Orthodox Christianity or similar. Could someone who understands the category system create it? Thanks! Benwing2 (talk) 05:48, 30 September 2015 (UTC)[reply]

How about Category:ru:Eastern Orthodoxy? You don't have to completely understand the category system to work with it: I went to Category:en:Roman Catholicism and went to its parent category to see what was there. I saw that there was Category:en:Eastern Orthodoxy, but there was no Category:ru:Eastern Orthodoxy, so I created Category:ru:Eastern Orthodoxy by putting {{topic cat}} in it.

If I had needed to add a category to the module, I would have clicked on the edit link in the text of Category:en:Roman Catholicism, which would take me to its data module, copypasted the section for Roman Catholicism at the right place in the alphabetical order, and replaced all the details to make the new section. The only way you can go wrong if you don't change the syntax is to specify a parent category that doesn't exist, which will give you a module error. Chuck Entz (talk) 12:39, 30 September 2015 (UTC)[reply]

Thank you. That works. I'll use your advice next time I need to create a category. Benwing2 (talk) 04:29, 1 October 2015 (UTC)[reply]