Wiktionary:Requests for moves, mergers and splits

Definition from Wiktionary, the free dictionary
Jump to: navigation, search
Wiktionary Request pages (edit) see also: discussions
Requests for cleanup
add new | history | archives

Cleanup requests, questions and discussions.

Requests for verification
add new | history | archives | old index

Requests for verification in the form of durably-archived attestations conveying the meaning of the term in question.

Requests for deletion
add new | history | archives

Requests for deletion of pages in the main namespace due to policy violations; also for undeletion requests.

Requests for deletion/Others
add new | history

Requests for deletion of pages in other (not the main) namespaces, such as categories, appendices and templates.

Requests for moves, mergers and splits
add new | history | archives

Moves, mergers and splits; requests listings, questions and discussions.

{{rfc-case}} - {{rfc-trans}} - {{rfdate}} - {{rfd-redundant}} - {{rfdef}} - {{rfe}} - {{rfex}} - {{rfap}} - {{rfp}} - {{rfphoto}} -

All Wiktionary: namespace discussions 1 2 3 4 5 - All discussion pages 1 2 3 4 5

This page is designed to discuss moves (renaming pages) mergers and splits. Its aim is to take the burden away from the beer parlour and requests for deletion where these issues were previously listed. Please note that uncontroversial page moves to correct typos, missing characters etc. should not be listed here, but moved directly using the move function.

  • Appropriate: Renaming categories, templates, Wiktionary pages, appendices, rhymes and occasionally entries. Merging or splitting temp categories, templates, Wiktionary pages, appendices, rhymes.
  • Out of scope: Merging entries which are alternative forms or spellings or synonyms such as color/colour or traveled/travelled. Unlike Wikipedia, we don't redirect in these sort of situations. Each spelling gets its own page, often employing the templates {{alternative spelling of}} or {{alternative form of}}.
  • Tagging pages: To tag a page, you can use the general template {{rfm}}, as well as one of the more specific templates {{move}}, {{merge}} and {{split}}.


Unresolved requests from before June 2012[edit]

June 2012[edit]

Category:Reference templates[edit]

To Category:English reference templates, whilst obviously removing all the non-English ones. We already have Category:Reference templates by language, but English is not in that category! The switch over to ...by language has gone well so far, why buck the trend whilst it's working? Mglovesfun (talk) 19:54, 23 June 2012 (UTC)

But when is a reference 'English'? Some could be used for other languages as well, especially etymological dictionaries. —CodeCat 20:06, 23 June 2012 (UTC)
Well, categorization isn't intended to (and won't) stop user using reference templates whenever they are useful. Nor does categorization have to be limited to only one language. Mglovesfun (talk) 21:16, 23 June 2012 (UTC)
I support creating Category:English reference templates. I am neutral on deleting Category:Reference templates. (Note that currently, a lot of reference templates belong both to Category:Reference templates and to a language-specific category. I don't know whether that's useful or not.) —RuakhTALK 12:54, 27 June 2012 (UTC)
  • Oppose. Is a template for Spanish-English dictionary a Spanish reference template or English reference template? Keep things simple by placing all reference templates to Category:Reference templates. --Dan Polansky (talk) 10:02, 14 September 2014 (UTC)

July 2012[edit]

Template:deftempboiler into Template:form of[edit]

There doesn't seem to be a crucial difference between these two templates, and they are both used for the same things. So I think merging them would be better, while adding the missing functionality of one to the other. See WT:GP#Singulative help for prior discussion. —CodeCat 11:41, 4 July 2012 (UTC)

Any merge must be effected carefully so that transcluded instances are not affected. (Or at least so that transcluded instances of {{deftempboiler}} aren't affected. Preferably also {{form of}}, but it's been edited in a way that affects transcluded instances without those pages ever thereafter being checked for still-accuracy, so further bad edits wouldn't be the end of the world.) If that's done, I support.​—msh210 (talk) 16:55, 4 July 2012 (UTC)


An anonymous user added a rfm template to this word, claiming it doesn't exist. I think it does, however, for the following reasons:

  1. I found it in a reputable source (Fennell, T.G, & H. Gelsen. 1980. A Grammar of Modern Latvian. Paris, New York, The Hague: Mouton Publishers. ISBN 90 279 7936 7), where it is not only mentioned, but given as the basic example of a set of words with irregular defective declension (the full defective paradigm of klausītājies is given on p. 1070).
  2. A google search reveals several occurrences (59) of the word, including several folk songs, and also a Latvijas Radio programme for 02-11-2011 (last word in the green text at 10:10 and at 23:10).

The total number of occurrences, however, is low, even taking into account the relatively small number of Internet pages in Latvian, and this word has a more regular counterpart klausītājs (which is where the anonymous user wants to move klausītājies to). This rarity, together with the existence of the more regular counterpart, is probably what motivates the anonymous user's impression that the word doesn't exist. I suggest that this word be kept, perhaps with an added context tag like 'rare' or 'old fashioned'. --Pereru (talk) 02:57, 12 July 2012 (UTC)

Create the regular form and make this an alternative form iff you can actually cite it (I believe Latvian still requires 3 citations). This doesn't really belong at RFM. --Μετάknowledgediscuss/deeds 12:20, 16 July 2012 (UTC)
The Google search I mentioned above yielded 59 results, many legitimate. Do these count as citations? Should they go on the citation page? (I haven't done anything with citations thus far. There probably is a page here at Wiktionary about how to handle citations, right? Could you direct me to it?) Well, I'll create the regular page, link klausītājies to it as an alternate form (but keeping the declension, which is different and irregular), and remove the RFM tag. --Pereru (talk) 17:08, 19 July 2012 (UTC)
Crash course on citations: citations must be durably archived (so, not off a Google search). Effectively, citations must be from Google Books, Google Groups, or a physical book/magazine/newspaper. Citations must be uses, not mentions (see w:use-mention distinction), so dictionaries don't count except for example sentences. For Latvian, every sense needs three citations to pass RFV. Citations must be formatted according to WT:". Does that cover it sufficiently? --Μετάknowledgediscuss/deeds 19:39, 19 July 2012 (UTC)

mind one's p's and q's[edit]

I agree with the comment on the talk page that two of the apostrophes should be taken out: [[mind one's Ps and Qs]]. Should the apotrophic form be a soft redirect, or a hard one? Or do you like the apostrophes and oppose a move? - -sche (discuss) 17:43, 19 July 2012 (UTC)

Soft. I.e., both, if attested, should exist, and the less common should be defined as a form-of.​—msh210 (talk) 21:39, 26 July 2012 (UTC)


I keep seeing this used as a reference template, which is annoying, since the formatting is totally wrong for that. Presumably the problem is with the name. Renaming it to something more transparent, like {{quote-book-2}} or {{quote-book-again}}, should help. (Or, better yet, merging it into {{quote-book}}. Or, best yet, getting rid of all quotation templates. They cause more problems than they solve.) —RuakhTALK 19:35, 26 July 2012 (UTC)

Yeah, move it somewhere else. Mglovesfun (talk) 09:47, 30 July 2012 (UTC)
Move or delete. Re: "I keep seeing this used as a reference template, which is annoying, since the formatting is totally wrong for that": Exactly. --Dan Polansky (talk) 21:19, 4 January 2013 (UTC)

Category:Arabic numerals[edit]

This name is misleading. Based on how our categories are named, you would expect this to contain terms in the Arabic language, but it doesn't. It should probably be named something like Category:Hindu-Arabic numerals, or something else than 'numerals'. —CodeCat 11:19, 30 July 2012 (UTC)

Absolutely agree. Mglovesfun (talk) 08:43, 31 July 2012 (UTC)
Yeah, Hindu-Arabic isn't ideal, but it's a whole lot better. --Μετάknowledgediscuss/deeds 15:37, 31 July 2012 (UTC)
I noticed we also have Category:Roman numerals. These categories have no indication of language, presumably because they are translingual. But I'm not sure if Category:Translingual Hindi-Arabic numerals sounds any better. —CodeCat 15:49, 31 July 2012 (UTC)

If it's translingual, would it include ,,,,,,,,, or ١,٢,٣,٤,٥,٦,٧,٨,٩,٠? Chuck Entz (talk) 13:21, 5 August 2012 (UTC)

I support, it’s a more correct name. — Ungoliant (Falai) 16:23, 5 August 2012 (UTC)

August 2012[edit]

Я in Old Church Slavonic[edit]

There are quite a few terms in OCS on Wiktionary that use the letter Я for 'ja'. However, as far as I know, that letter didn't actually exist at the time OCS was written. w:Ya (Cyrillic) explains that it developed as a scribal variant of Ѧ, which stood for a nasal vowel 'ę' which later developed into 'ja' in many Slavic languages. So it is a bit like distinguishing i/v and j/u in Latin. There is a big difference though: Ѧ itself is still used in OCS in its original form and sound 'ę', while the letter was used in OCS to represent the sound 'ja' and Ѩ stood for 'ję'. So using Я in those words seems like an anachronism. Should our OCS terms be moved to their OCS-era spellings, or are the spellings with Я actually attested in the original manuscripts? —CodeCat 15:42, 18 August 2012 (UTC)

I think we should be using ꙗ whenever the OCS sound was [ja], ѧ whenever it was [ę] (i.e. [ɛ̃]) and ѩ whenever it was [ję] (i.e. [jɛ̃]). I'm not sure to what extent these get confused in the manuscripts, and a certain number of {{alternative spelling of}}s may be necessary, but I think the main lemma should reflect the historically correct letter, meaning я shouldn't be used for OCS at all. —Angr 22:06, 18 August 2012 (UTC)
OCS spelling apparently followed a rule that any front vowel not preceded by a consonant had a j- inserted before it automatically (apparently there were no vowel-initial words?). So that would have eliminated most use cases for ѩ, and I'm not sure how widely it was used. OCS spelling was far from consistent and may often reflect dialectal pronunciation rather than normalised 'reconstructed' pronunciation. I am quite sure that я did not occur in OCS as it was just a variant of ѧ, but it's possible that words later spelled with ѧ/я etymologically should have ѧ, ꙗ or ѣ, which were or became [ja] in various dialects (but differently in each). So we would need to find out the etymological origin of our current words with я before we can move them. —CodeCat 22:54, 18 August 2012 (UTC)
ѩзꙑкъ is an example of a word spelled with ѩ. How many OCS words do we have spelled with я? It shouldn't be hard to find or figure out which letter is the right one. Looking through Category:Old Church Slavonic nouns it seems most entries with я were created by Ivan Štambuk. Maybe he could be prevailed upon to help put them right. —Angr 16:36, 19 August 2012 (UTC)

September 2012[edit]


should be merged with Appendix:Proto-Indo-European/sóh₂wl̥. The last is more complete. --Fsojic (talk) 11:59, 4 September 2012 (UTC)

Yes I agree. Can you do the merge? —CodeCat 12:20, 4 September 2012 (UTC)
Redirect or I suppose {{alternative form of}}. Mglovesfun (talk) 19:56, 9 September 2012 (UTC)
Redirect --Μετάknowledgediscuss/deeds 20:38, 9 September 2012 (UTC)

information velocity[edit]

I think all three definitions can be merged. If not, then at least the third can merge with the second. The definitions are:

  1. (physics) The speed at which information is transmitted through a particular medium
  2. (marketing) The speed of information flow about a product in a market
  3. (financial markets) The rate at which information that influences the price of securities in informationally efficient markets moves through the market.

--WikiTiki89 (talk) 15:14, 13 September 2012 (UTC)

  • Either merge, or delete (as sum of parts). SemperBlotto (talk) 15:21, 13 September 2012 (UTC)
  • We've typically handled contentious merging of senses at WT:RFD, leaving this page for merging of pages. Anyway, delete the entry AFAICT.​—msh210 (talk) 16:13, 13 September 2012 (UTC)
    • I'm not really sure if the first definition can be considered the same thing as the others. It seems doubtful that a physicist and someone in marketing would use it with the same meaning, considering the vast difference between the two fields and the way in which physicists have specific definitions for things. In particular, a physicist would not talk about information flow from person to person, but through a medium such as a vacuum or air. The other two definitions can be merged, though. —CodeCat 20:04, 13 September 2012 (UTC)

Category:English lexicons to Category:English terms by usage[edit]

This seems more clear than the rather vague 'lexicon' which the average user will probably not understand. We should probably rename Category:English etymologies to Category:English terms by etymology too, and Category:English parts of speech to Category:English terms by part of speech while we're at it. —CodeCat 17:20, 20 September 2012 (UTC) (Note: It's implied that the categories for other languages will be renamed, too) —CodeCat 17:21, 20 September 2012 (UTC)

The existing name may obscure, but it is not vague, unlike the proposed name which is vague without using obscure words. DCDuring TALK 16:11, 26 July 2014 (UTC)

take it easy[edit]

I think [[take it easy]] and [[have it easy]] should be respectively moved to [[take it]] and [[have it]] since they can both be used with other adjectives (or are they adjectives being used as adverbs?). For example: take it slow, have it bad, etc. --WikiTiki89 (talk) 13:22, 27 September 2012 (UTC)

Two of the three senses at [[take it easy]] relates to the conventional use of the imperative, which conventional uses are idioms, as some idiom dictionaries show.
As to the other sense, there is nothing special about "it" in this case. Many nominals can occupy its slot: "I take this kind of request personally.", "He took her deciding to leave hard". I think we already have the right sense of take#Verb. I would replace the definition with {{&lit|take|easy}}. DCDuring TALK 14:30, 27 September 2012 (UTC)
Ok, I can concede that sense #3 is idiomatic. But sense #2 is really just a particular use for sense #1. Also, "I'm gonna stay home and take it easy." and "I was criticized but did not take it personally." do not use the same sense of "take it". --WikiTiki89 (talk) 14:45, 27 September 2012 (UTC)
But it is conventionalized.
I can't find applicable definitions of take it at Collins or RHU, the only two credible OneLook dictionaries that cover it among the five references that have entries. Do you mean of take#Verb? I think they do. Something like "receive or accept". DCDuring TALK 15:08, 27 September 2012 (UTC)
Since when do we do things exactly like other dictionaries? --WikiTiki89 (talk) 15:21, 27 September 2012 (UTC)

have it easy[edit]

There are certainly fewer nominals that seem to fit the "it" slot, but "life" and various periods of time ("the rest of the day") do. If you allow for other adjectivals (eg, ready, available, pending, full, outstanding, interested, comparable[+complement], like[+complement], similar[+complement]), it doesn't seem very special at all. DCDuring TALK 14:50, 27 September 2012 (UTC)

If I say "He has it ready." without context, you will wonder what "it" is. If I say "He has it easy." or "He has it bad.", you unambiguously know that I am referring to his quality of life. It may seem that "it" simply refers to "life", but you can't say "He has life easy." It's the same sort of abstract "it" as in "It is raining." You can try say that "it" refers to the sky but that doesn't really work either. --WikiTiki89 (talk) 15:19, 27 September 2012 (UTC)

October 2012[edit]

honor, honour[edit]

The definitions need to be synced up or merged, and the translations of honor#Verb should be moved to honour#Verb (simply because that's where most of the translations already are). - -sche (discuss) 17:37, 9 October 2012 (UTC)

Happy New Year[edit]

Is there any reason the 'H' is capital? I think it should be moved to happy New Year, which currently redirects to it. --WikiTiki89 12:28, 20 October 2012 (UTC)

Move per nomination. Mglovesfun (talk) 17:18, 25 January 2013 (UTC)
Agreed. Move per Wikitiki89. — I.S.M.E.T.A. 15:42, 13 January 2015 (UTC)
Lots of examples of "Happy New Year" being used mid-sentence though. 1, 2, 3, 4 Smurrayinchester (talk) 16:52, 13 January 2015 (UTC)

December 2012[edit]


This should be renamed Category:Humans. Compare Category:People, Category:Social sciences, Category:Given names. - -sche (discuss) 05:29, 2 December 2012 (UTC)

Or Category:Humanity. Mglovesfun (talk) 11:26, 3 December 2012 (UTC)
Support Humanity (lol) —Μετάknowledgediscuss/deeds 07:28, 4 February 2013 (UTC)
Wait, what's the different between this and Category:People? Is there one? Should there be one? - -sche (discuss) 07:37, 4 February 2013 (UTC)
Yeah, cats like 'Emotions', 'Age', and 'Thinking' seem better placed in 'Humanity' than in 'People' IMO. So I think we oughn't to delete it, just rename it. —Μετάknowledgediscuss/deeds 07:41, 4 February 2013 (UTC)


The Digor and Iron dialects of Ossetian seem quite different, and already many (most?) of our entries distinguish which is meant. It seems to me that there is a fair chance that the two are separate enough to deserve being called different languages here. —Μετάknowledgediscuss/deeds 04:46, 19 December 2012 (UTC)

I've seen them referred to as separate languages before, but there's still some debate over that. Doesn't matter to me. But would there still be plain Ossetian language entries or would all be sorted into the new languages? There are some that aren't labelled as either Iron or Digor.Word dewd544 (talk) 17:58, 20 December 2012 (UTC)
Iron is by far the more common dialect, and the literary Ossetian language is based on Iron. However, Digor is different enough that it could be considered a separate language. The main things against it here are the relatively small number of speakers and that it does not yet have a written standard, as far as I know. But there is now a Digor dictionary out there, and it’s probably just a matter of time before Digor develops a literary standard of its own. I think it’s unlikely that we will get enough Digor contributions to make a difference, but it is always possible that someone will start entering words from a Digor dictionary. The Digor language code is oss-dig. We could use os for Ossetian proper (and Iron), and oss-dig for Digor. —Stephen (Talk) 02:20, 21 December 2012 (UTC)
In that case, I support. — Ungoliant (Falai) 03:40, 21 December 2012 (UTC)
A standard language based on one widely-spoken dialect, and another lect sometimes considered a dialect and sometimes considered its own language? This reminds me of Tosk vs Gheg Albanian: some references say they're mutually unintelligible separate languages, speakers say their differences present no impediment to communication. Unfortunately, we lack speakers of the Ossestian lects, and the dictionary of Digor is said to waffle, the author calling it a language and the editor calling it a dialect. Stephen is probably right that it's just a matter of time before Digor develops its own standard (and merits separation as much as Luxembourgish and Limburgish do from each other and from German); OTOH, Wiktionary, like Wikipedia, is not a crystal ball. My preference would be to wait and not split them for now. If we do split them, I agree with using {{os}} for Iron (compare {{lt}} and {{sgs}}), and we should devise an exceptional code for Digor that fits our usual naming scheme (ira-odg or ira-dig), rather than using Linguist List's ersatz "oss-dig". - -sche (discuss) 03:42, 21 December 2012 (UTC)

Category:English terms with obsolete senses[edit]

As per the discussion in the Beer Parlor, I suggest that this category be reserved only for words that are not fully obsolete (i.e., that contain at least one current sense), and that all words that have only obsolete senses (i.e., fully obsolete words) be moved back to Category:English obsolete terms. (I think it would be better to, as CodeCat suggested, simply leave non-fully obsolete words uncategorized, which would imply eventually deleeting Category:English terms with obsolete senses, but I'm OK with leaving it there for partially obsolete words if others want that.) --Pereru (talk) 08:33, 19 December 2012 (UTC)

SupportCodeCat 02:26, 21 December 2012 (UTC)
I'd like to support it, but not if there is no implementation scheduled. I would not be happy if this was our policy and two months from now most of the terms that were supposed to be in it were not. We need a dump run to identity the L2 sections that need the categorization. And maintaining it really should be part of an AF-type bot. I do hope that this is intended to be applied to all living languages. Are all obsolete tags not in English marked with lang= tags? DCDuring TALK 13:01, 21 December 2012 (UTC)
I would also support requiring lang=en for these tags, because people constantly forget those tags and put entries in the English categories. In fact the whole "English as default" thing doesn't work too well... I've lost count of how many instances of {{term}} without a language I've had to fix... —CodeCat 13:38, 21 December 2012 (UTC)
How can implementation be scheduled? How are such actions decided? (I've just created a {{obsolete term}} for fully obsolete terms, and I plan to slowly add it to all Latvian words for which it is appropriate, so as to slowly fill Category:Latvian obsolete terms; but how about English and all the other languages?) --Pereru (talk) 02:01, 22 December 2012 (UTC) I've just transfered abstrude and a few other similar terms to Category:English obsolete terms by changing the tag from {{obsolete}} to {{obsolete term}}. Is that part of what should be happening? --Pereru (talk) 02:04, 22 December 2012 (UTC)
Should {{obsolete}} be used for obsolete senses or obsolete terms? Using it for obsolete terms has one advantage: anyone can skim the list of obsolete terms and immediately spot a word they know is still in use. Trying to spot a completely-obsolete term among a list of terms with obsolete senses would be much harder. —CodeCat 02:20, 22 December 2012 (UTC)
On the other hand, people are more likely to use the shorter, generic name {{obsolete}} where it doesn't belong than to use the longer, explicit name {{obsolete term}} where it doesn't belong, so I think using {{obsolete}} only for obsolete terms and not for senses would be counter-intuitive and a bad idea. My preference would be to use {{obsolete}} for senses... but perhaps we should insist upon two explicitly named templates, {{obsolete term}} and {{obsolete sense}} (both with the display text "obsolete"?). Using two explicitly dedicated templates would make separate categorisation of entirely obsolete terms and of terms with obsolete senses practical, too. Btw, the "obsolete terms" category could be a subcategory of the "terms with obsolete senses" category, like "proper nouns" are a subcategory of "nouns". And we could keep {{obsolete}} (because new users and visitors from other projects may call it directly or in creative ways, like {{context|UK|obsolete|_|outside of|_|dialects}}), but treat its Whatlinkshere as a standing, self-updating cleanup list. - -sche (discuss) 04:39, 22 December 2012 (UTC)
I tend to agree with -sche above; {{obsolete sense}} would make, well, sense. But now there's one thing bugging me: shouldn't fully obsolete terms have the "obsolete" tag somewhere in their inflection line? Or else we'd have to add an {{obsolete term}} tag to every single sense, or else we imply that one of the obsolete senses is actually current... --Pereru (talk) 03:48, 23 December 2012 (UTC) By the way, in principle everything applies mutatis mutandis to the other Period labels archaic and {{dated}}, right? --Pereru (talk) 03:50, 23 December 2012 (UTC)
So you are saying that obsoleteness of a term is not a context? I suppose that is true, but we don't have any system currently in place for indicating term-wide contexts. This has been a problem in the past too... for example {{cardinal}} or {{personal}} shouldn't really be usage labels either. —CodeCat 03:55, 23 December 2012 (UTC)
We indicate obsolescence on the sense line when only one of several senses is obsolete, so I think obsolescence should also be indicated on the sense line when all senses are obsolete: indicating obsolescence on each sense line in all cases adds clarity. Meanwhile, we indicate on the inflection/headline line when certain inflected forms are obsolete (or dialectal, etc; see [[learn]], [[work#verb]], etc): so indicating the obsolescence of senses on the inflection line, when the inflected forms are not any more obsolete (or {{dated}}!) than the word itself, would be confusing. I expect some people wouldn't notice the tag on the inflection line, and would thus think that no sense was obsolete (not what you want), or would notice the tag but think (logically) than it applied to the inflections and again that the senses were not obsolete (again, not what you want)... I think it's better to indicate the obsolescence of the senses on the sense line. (How many highly polysemous obsolete words are there, anyway?) - -sche (discuss) 05:09, 23 December 2012 (UTC)
We don't do this for any other register or dialect: We don't have separate categories for US-only terms and for those with US-only senses, nor separate categories for math-specific terms and for those with math-specific senses. Why should obsolete be different?​—msh210 (talk) 06:06, 23 December 2012 (UTC)
For one thing, it would give us a list of terms which a bot could use to identify terms that should probably not be used in definitions. The same would be true in varying degrees for {{archaic}}, {{dated}}, {{rare}}, and possibly others. DCDuring TALK 10:27, 23 December 2012 (UTC)

Template:arc and Template:syc[edit]

The same language in two different scripts with two different literary standards, and yet each quite similar to each other. I think I see a pattern. —Μετάknowledgediscuss/deeds 07:49, 21 December 2012 (UTC)

"Arc" should only be used for "Imperial Aramaic" (aka "Official Aramaic"), ideally written in the Old Aramaic script rather than Hebrew. Current usage does not reflect that though and there are a whole mix of dialects intertwined within the "arc" code, so that one at least should be split. "Syc" should stay as it is. --334a (talk) 08:04, 21 December 2012 (UTC)
I think SIL has done a really bad job with the classification of Aramaic languages. ARC was an umbrella code that was used to describe all later Aramaic varieties in ISO-639-2 in ISO 639-3 they introduced SYC for classical Syriac, by far the most widespread form of literary Aramaic.--Rafy (talk) 17:38, 28 December 2012 (UTC)

frs to gmw-fre[edit]

I propose to create {{gmw-fre}} as an unambiguous code for the "East Frisian" variety of Frisian, and switch all remaining transclusions of "frs" to "gmw-fre". Currently, we use {{frs}} for the that variety of Frisian, but {{frs}} is ambiguous: it appears to have been intended by the ISO to designate either "Saterland Frisian" (the last surviving variety of East Frisian, which has the code {{stq}}) or "Eastern Frisian" (a variety of Low German which, like other German varieties, has been subsumed into {{nds-de}}). (In the first of two previous discussions of {{frs}}, all participants assumed that {{frs}} and {{stq}} referred to Frisian and therefore debated merging them. The second discussion investigated whether {{frs}} referred to a Frisian lect or a Low German one: ultimately, it seems it's unknowable, since Ethnologue hasn't responded to requests for clarification.) - -sche (discuss) 18:56, 28 December 2012 (UTC)

I personally don't see the point. There is an existing, valid code which may (or may not) have ben intended for this language. Even when we follow ISO standards, we do tend to, for example, redefine the spatial or temporal extent of that code in a different way than Ethnologue might. This seems to be the same thing to me. If {{frs}} is ever officially demystified, and it's not in line with our coverage, then we can revisit the matter. For now, I advocate against moving it. —Μετάknowledgediscuss/deeds 20:16, 28 December 2012 (UTC)
All we want to avoid is people making entries in East Frisian. We could just turn it into an etymology code and move it to {{etyl:frs}}? —CodeCat 20:24, 28 December 2012 (UTC)
I think allowing/barring East Frisian entries is a separate question. Saterland Frisian is the last living dialect of East Frisian, but at least some terms from other East Frisian dialects are attested, and I can see how some people might prefer to have ==East Frisian== entries for those terms, or simply to have East Frisian terms like we have Middle High German terms. I don't think the question of whether to allow or ban that should be rolled into the question of what code to use.
I oppose "{{etyl:frs}}". Ethnologue calls "frs" a "Low German" (not "Frisian") language, claims it's spoken by only 2000 people (the Frisian lect is dead, but Saterland Frisian is spoken by 6000; the Low German lect is spoken by 230 000), and says it's not mutually intelligible with Saterland Frisian (which is true of the Low German lect, untrue of the Frisian lect). Randomly guessing which one of those lects to use the ambiguous code for is one thing... but designing a brand-new code that is intentionally ambiguous (like {{etyl:frs}})?
Given Ethnologue's ambiguity and the fact both lects go by "East Frisian" (though the Low German one also uses "Eastern Frisian", and the Frisian one might, too), I suspect that some of the {{frs}} words I've seen in etymologies and haven't been able to find {{stq}} cognates/descendents of are indeed the product of people using "frs" to mean "Low German". (I haven't been able to confirm any yet because East Frisian and Eastern Frisian are both relatively obscure.) - -sche (discuss) 22:51, 28 December 2012 (UTC)

January 2013[edit]

Category:Requested entries and Category:Requested entries by language[edit]

I think these are the same thing? They should be merged, but which name should the merged category have? —CodeCat 00:40, 10 January 2013 (UTC)

Category:Requested entries contains User:Brian0918/Hotlist, that seems to be the only difference. Mglovesfun (talk) 19:04, 10 January 2013 (UTC)

never-never land[edit]

Tagged {{rft}} with the comment "redirect to, alternate form of, or synonym of neverland?" But the Tea rooms discussions apparently petered out ages ago. - -sche (discuss) 05:44, 11 January 2013 (UTC)

Shouldn't be redirected or soft-redirected (made an alt form), IMO. Are the terms really synonymous? If so, one could be defiend as the other + {{gloss}}. - -sche (discuss) 05:46, 11 January 2013 (UTC)


It can get no worse than this. We evidently call a language Numana-Nunku-Gbantu-Numbu. The name is formed by hyphenating the four major dialects. I propose that we instead call it Sanga, listed as an alternative by Ethnologue. Although it appears to have just as many uses as Numana-Nunku-Gbantu-Numbu on BGC for the meaning "a language of Nigeria", it does appear to be citable as the name of the ethnic group which speaks it, which I think is a damn sight better than the current condition. —Μετάknowledgediscuss/deeds 08:11, 14 January 2013 (UTC)

You think that's bad? Look at Template:gel (Kag-Fer-Jiir-Koor-Ror-Us-Zuksun). The horror, the horror. - -sche (discuss) 08:36, 14 January 2013 (UTC)
The name WP suggests, "Gbantu", does get one GBC hit... in an specifically unpublished paper cited in Zwischen Bantu und Burkina; "Gwantu" gets nothing relevant. I like your suggestion of "Sanga" (I even managed to dig up one or two citations of it as a language name). Support renaming. - -sche (discuss) 09:17, 14 January 2013 (UTC)
Be careful. It looks like you're confusing it with Sango ({{sg}}). —Μετάknowledgediscuss/deeds 09:22, 14 January 2013 (UTC)
Oh, you're right. That's... ugh. As silly as its current name is, giving it a name that's only attested in reference to some other language would obviously be undesirable... and calling it by the name of only one of its dialects (Gbantu) isn't exactly ideal, either (compare {{mij}}), although I'd go along with it for lack of a better option. It may be that, as with {{gel}}, the least odious (or at least, least confusing) thing to do is leave it as-is. :/ - -sche (discuss) 23:18, 14 January 2013 (UTC) - -sche (discuss) 02:06, 15 January 2013 (UTC)
Well, can you figure out what the first cite refers to? That might help. And as I mentioned, it still may be a more logical choice, considering that google books:Sanga Nigeria isn't too sparse. —Μετάknowledgediscuss/deeds 07:14, 15 January 2013 (UTC)


I propose that we merge this template with {{slim-wikipedia}} (by redirecting it there, or deleting it and moving {{slim-wikipedia}} to {{wikipedia}}). I believe this will help reduce entry clutter without affecting usability because, unlike the “In other projects” box, {{slim-wikipedia}} can still be easily seen, and because {{wikipedia}}’s bigger logo, longer text and greater waste of vertical space are useless. — Ungoliant (Falai) 21:48, 16 January 2013 (UTC)

I haven't noticed the larger size being that much of a problem, though. And Wikipedia has an identical-looking set of templates I think, so it helps with cross-project consistency. —CodeCat 21:57, 16 January 2013 (UTC)
Strong oppose. I think that without this template, few would notice the Wikipedia links. Sorry, Ungoliant. —Μετάknowledgediscuss/deeds 01:50, 17 January 2013 (UTC)
Tend to support but hesitantly. Put me down as an abstain. Mglovesfun (talk) 17:15, 25 January 2013 (UTC)
Support. {{wikipedia}} wastes a lot of space. --Yair rand (talk) 08:32, 29 January 2013 (UTC)
Support if {{slim-wikipedia}} has all the features {{wikipedia}} does (linking to more than one article, linking to foreign-languages Wikipedias, etc.). (I haven't checked.)​—msh210 (talk) 16:52, 29 January 2013 (UTC)
Oppose per Metaknowledge. - -sche (discuss) 19:35, 31 January 2013 (UTC)
Support merging the two; Oppose making it smaller. How is space on web pages being wasted, particularly by a box that floats to the right of the content? Is scrollbar an endangered resource? Michael Z. 2013-02-03 00:26 z
Keep. In entries where there are multiple L2s, each with their own language-specific wikipedia links, not to mention their own images, it's not unheard of for the wikipedia box from one language to end up at least partially across from the entry for the neighboring language- so space is, indeed, sometimes a problem. That said, I don't agree with eliminating the option of ever using a full-size wikipedia box even in the majority of cases where space isn't an issue. Like Μετάknowledge says, it's good to have it highly visible sometimes. Chuck Entz (talk) 03:58, 3 February 2013 (UTC)
  • {{slim-wikipedia}} was originally intended to be the only interproject link template that could appear above the first L2 header. It was intended to send folks to WP in cases where there might be a proper Wiktionary entry, but WP had an entry or a disambiguation page that had material not in and not appropriate for Wiktionary. The principal situation would have been for English proper noun entries for which there might be many proper noun that did not meet our prevailing criteria for inclusion or had not yet been entered. The rationale for the placement was that this was the encyclopedic equivalent of {{also}}. It was made small to take up less vertical screen space.
Oppose. If this project link box is to be smaller, then all should be. If the original rationale for {{slim-wikipedia}} as a special box for above-first-L2 placement is considered currently valid then the rationale for small size also remains. DCDuring TALK 01:38, 3 February 2013 (UTC)
Support merge Why can't we just add a parameter like |slim=yes so you could have the slim version show up when invoking {{wikipedia}}? You could keep the slim version and amend it as necessary and eat the cake too. TeleComNasSprVen (talk) 21:21, 29 December 2013 (UTC)
Support a merge if done like this, but otherwise, oppose. — Carolina wren discussió 00:16, 24 February 2014 (UTC)



And its 6 members:

Also involved are unligatured twins of most of these

These are all fine entries, but the rare ligatured forms shouldn't be the lemmas. Right now, there are alt-form entries for each of these with the preferred unligatured spellings. What I would like to do is to swap the ligatured with the unligatured entries: move the ligatured entry to a temporary name, move the unligatured entry into its place, and move the ligatured entry to where the unligatured entry was. After that, it should be a simple matter of switching ligatures for diphthongs and vice-versa in the texts of the entries. This should preserve the edit histories and keep the content intact.

I realize there are probably many other cases like this, but this one is small and contained enough to be easily accomplished without much fuss. I almost just went ahead and did it myself, but figured it was better to give it due process.

Please note that I'm not talking about the pondian difference of oe vs e- just the characters used to represent the UK spelling. Chuck Entz (talk) 05:37, 19 January 2013 (UTC)

Support. — Ungoliant (Falai) 06:00, 19 January 2013 (UTC)
It's predictably down to Doremítzwr (talkcontribs), someone I would consider a POV pusher with respect to using archaic spellings when contemporary spellings are available. Support. Mglovesfun (talk) 10:43, 19 January 2013 (UTC)
SupportCodeCat 14:08, 19 January 2013 (UTC)
To be pedantic, Category:English words prefixed with cœn- won't change. Mglovesfun (talk) 21:57, 29 January 2013 (UTC)

Template:ko-freq and subpages of Appendix:Korean frequentatives[edit]

KYPark (talkcontribs)'s latest pseudoscientific pet project, which ought to be moved to the subpages of User:KYPark. I have moved a couple things, as previous editors have moved his off-topic musings, rants, etc to his userspace, but I just wanted to ensure that there is consensus for this. —Μετάknowledgediscuss/deeds 06:34, 25 January 2013 (UTC)

February 2013[edit]

Appendix:Tausug adverbs[edit]

Judging by their definitions, most of these words aren't actually adverbs. It's a short, low-quality wordlist, but I think the best place for it is at Index:Tausug. —Μετάknowledgediscuss/deeds 02:42, 1 February 2013 (UTC)

Category:zh-tw:Variant Pronunciations[edit]

This category has a bad name that refers to an obsolete code, but the content is good. It should be merged into Category:Taiwanese Mandarin and then it can be deleted. Same goes for Category:zh-cn:Variant Pronunciations and Category:Chinese Mandarin. —Μετάknowledgediscuss/deeds 07:23, 4 February 2013 (UTC)

"Chinese Mandarin" is very unclear as a name, though. It doesn't actually tell me what it really is, and only from what you said can I figure out that it is somehow distinct from "Taiwanese Mandarin". Many people would probably understand it to be a synonym of "Mandarin" or "Mandarin Chinese". —CodeCat 22:50, 10 February 2013 (UTC)
The correct category is Category:cmn:Variant pronunciations (before Mandarin->Chinese conversion is complete). Standard Taiwanese Mandarin (Guoyu) could be marked as "Taiwanese Mandarin" (even after the conversion), if they are different from mainland standard. An example is 普遍, which shows two standards. --Anatoli (обсудить/вклад) 23:27, 6 April 2014 (UTC)


It is rather unusual for us to use a bare adjective as a category name. I can't really think of anything substantially better, but if someone has an idea, I'd be glad to hear it. —Μετάknowledgediscuss/deeds 07:30, 4 February 2013 (UTC)

Category:Sailing is already taken as a subcat (though I don't know what the difference is supposed to be), so perhaps Category:Nautical terminology? —Angr 13:45, 4 February 2013 (UTC)
I believe Category:Sailing has to do specifically with sailboats: you can set sail in a submarine, but the verb "surface" isn't a sailing term (unless you're doing a really bad job of it)... Chuck Entz (talk) 14:23, 4 February 2013 (UTC)
What about Category:Boating? That's what Wikipedia's Sailing category is a subcat of. —Angr 15:03, 4 February 2013 (UTC)
I like your previous suggestion, Nautical terminology. If you take a look, a lot of it is sailors' slang. —Μετάknowledgediscuss/deeds 20:50, 4 February 2013 (UTC)
There is slang, and there is jargon. The sailing argot of the late 19th-early 20th century was also translingual; there is ample evidence the industry required proficiency in the technical language but did not require the ability to otherwise communicate with colleagues or officers. Much of nautical terminology refers to maritime and shipping law, e.g. Singapore was established as an entrepôt port (which term is completely lacking the tax-relevant character: it is a port/warehouse at which goods may be stored for transshipment without incurring taxes.) - Amgine/ t·e 19:04, 8 April 2014 (UTC)

Category:Zhuang characters[edit]

Move to Category:Zhuang sawndip. Should probably also be a member of Category:Han characters -- Liliana 23:00, 9 February 2013 (UTC)

Category:Coordinate term templates[edit]

This category (and the templates in it) seem to fulfill the same purpose as list templates (Category:English list templates). So they should probably be merged, and the templates themselves converted. —CodeCat 14:55, 10 February 2013 (UTC)

Support. — Ungoliant (Falai) 16:11, 10 February 2013 (UTC)

jemandem etwas in die Schuhe schieben[edit]

...and jemanden über den Löffel barbieren, jemandem über den Weg laufen, jemanden hinters Licht führen, and other German verb phrases containing "jemand*" and "etwas": should some of all of them drop "jemand*"? I note that our English entries sometimes but not always omit "someone"s and "something"s, e.g. we have [[lay at the feet of]] (which, when said that way, sounds like what a dog does) rather than [[lay something at the feet of]], but then we have [[cross someone's path]]. (Actually, "lay at the feet of" needs a placeholder, IMO; see my post just below this one.) - -sche (discuss) 21:13, 12 February 2013 (UTC)

  • My gut instinct is to remove accusative jemanden but keep dative jemandem, but I'm not sure I can articulate exactly why. Direct objects just feel somehow more removable from idiomatic verb phrases than indirect objects. —Angr 21:51, 12 February 2013 (UTC)
Move all. I would remove such placeholders generally. The necessary complements (no matter if accusative or dative) can be specified next to the definition. The reason we have a placeholder in cross someone's path probably is that it has the genitive-'s and thus can't be removed (other than by replacing it with "X's" or something like that). Longtrend (talk) 18:22, 13 February 2013 (UTC)

Category:English diminutives of male given names[edit]

Category:English diminutives of female given names[edit]

I think these need to be split as not all of the names are diminutives. Some are non-diminutive nicknames. Alternatively it could be renamed Category:English nicknames of male given names. Or it could be Category:English male nicknames.

I think that nickname and diminutive are overlapping categories. Aren't Francine and Mariella diminutives of Frances and Maria, respectively? But they are not nicknames. Similarly, Jake is a nickname for Jacob/Jacques, but not a diminutive.

I don't know whether the categories and their application are correct with respect to other languages, but the application of {{given name}} has lead to a bad result for English. DCDuring TALK 00:17, 13 February 2013 (UTC)

Do you mean that a diminutive has something added (Franc+ine, John+ny) and a nickname has something subtracted (Jake-(c)ob, Rob-ert)? Or what is the difference? Is this a meaningful way to split a category? Francine is defined as a formal given name in French and English. It derives from an ancient diminutive, but that's etymology. The diminutive definitions and categories are based on the way a name is used, not on its grammatical form. Diminutives and formal given names often overlap, and what's a diminutive in one language may be a formal given name in another: Tommy for example. So use of Template:given name seems reasonable.
I agree that "diminutive" is not the perfect category name, but are the alternatives any better? "Nickname" applies to words like Shorty, Dubya, Shug that are not linguistically related to a person's real given name. "Pet name" sounds too colloquial to me, and "hypocorism" is the opposite of a "pejorative" with Russian names. Changing the name would take a lot of manual work. Not all the entries use the template. --Makaokalani (talk) 14:45, 20 February 2013 (UTC)
What makes you think that "'nickname' applies to words... that are not linguistically related to a person's real given name"? I would certainly say Tom is a nickname for Thomas, Bill is a nickname for William, Liz is a nickname for Elizabeth, etc. Those aren't the only kind of nicknames, but they are nicknames. —Angr 15:07, 20 February 2013 (UTC)
Sure, but terms like Shorty should not be listed in the same category with Tom, Bill and Liz. You can create a separate category for them. I meant "the word nickname also applies to..."--Makaokalani (talk) 15:52, 20 February 2013 (UTC)
Whatever else, the current name is applicable only to a subset of those now in the category. It is mostly populated by {{given name}} when the parameter 'diminutive' is applied. If there were other possibilities for other kinds of derivations, then the template would not create the erroneous results it does. A category of derived names for which diminutives would be a subcategory would be fine with me.
The template did not specify 'diminutive' until January 2010. I'd be happy with a rollback to the edit before that, but there have been later changes that may have some value. DCDuring TALK 00:34, 21 February 2013 (UTC)
The members of the categories are called hypocorisms or pet names, judging from online dictionaries. The current name is wrong, IMHO, or misleading anyway. --Dan Polansky (talk) 21:34, 25 February 2013 (UTC)
Thanks. I'd meant to look up hypocorism. It is not really suitable for use as part of a category name if we intend the category for use by normal users, rather than us or language professionals. I probably would be OK to group nicknames, diminutives, and other similar types of names, if there are others to include. DCDuring TALK 23:06, 25 February 2013 (UTC)
Just to make clear that we are discussing the same thing: I oppose splitting the diminutive categories. It would be confusing, and impossible to do in many languages (e.g. Finnish). Tom and Bill certainly belong to the same category as Tommy and Billy. Terms like Dubya and Shorty are now uncategorized and need some other category ("Nicknames?"). Terms like Francine are not diminutives in English or French. (I can see some old entries have confusing definitions like "A male given name, diminutive of X" , the diminutive part properly belonging to the etymology.) I oppose removing the diminutive= parameter from Template:given name. Changing it to something else, and changing the names of all diminutive categories (21 male, 16 female) would not bother me provided someone else does it all, including the tiresome manual work. Webster's 2003 definition of diminutive includes: "used of affixes (as -ette, -kin, -ling) and of words formed with them (--), of clipped forms (as Jim), and of altered forms (as Peggy)", so the present category name is not completely wrong. Our definition of diminutive includes endearments.--Makaokalani (talk) 09:42, 2 March 2013 (UTC)
  1. Is this category supposed to be directed at normal users or linguists or is it intended as some kind of maintenance category? Diminutive for normal users implies "small" and may connote "belittling".
  2. In English, the categorization based on affixes alone cannot be semantic, it is etymological. The word "diminutive" does not seem appropriate for display on the definition line in cases where "diminutive" in the normal user sense is not accurate, though the etymological sense applies. Perhaps we need to create a special template for use in the etymology section of names to categorize into diminutives. I am aware that diminutives seem to be virtually inflectional in some languages, at least in the opinion of, say, some of our Dutch contributors. But I don't think that an approach based on that model is appropriate for English.
  3. It seems to me that we have can have almost nothing to say about the meaning of names, rather than their derivation. At best we can provide a non-gloss definition. I doubt that we have a fact base to use to check the correctness of such assertions as often used as a pet name/term of endearment. DCDuring TALK 13:17, 2 March 2013 (UTC)
Another candidate term: familiar form: try google books:"familiar form"; there, Dictionary of First Names by Iseabail C. MacLeod, Terry Freedman, 1995 uses the term. In spite of Merriam-Webster's "diminutive" entry siding with Makaokalani, I still disfavor "diminutive". --Dan Polansky (talk) 16:16, 2 March 2013 (UTC)
That might work. But I'm not sure that a person whose birth certificate says his given name is Jim views the name as a "familiar form" or a "pet name" or a "diminutive".
If we don't consign the relationship to other names to Etymology, the only place it belongs IMO, then for display we need something other than "diminutive" for those cases where that is in appropriate, eg, Jimbo. It is obviously related to James, but is decidedly NOT a diminutive. DCDuring TALK 16:48, 2 March 2013 (UTC)

March 2013[edit]


This is called from several main-namespace entries. It should be moved into the Template: namespace and those entries which call it should be updated. - -sche (discuss) 03:38, 11 March 2013 (UTC)

I subst:ed the only remaining transclusion. Mglovesfun (talk) 22:52, 17 March 2013 (UTC)

I haven't the foggiest[edit]

Shouldn't this be at not have the foggiest (now a redirect) or perhaps better at have the foggiest. Certainly this doesn't only occur in the first person singular.

I think there is always a negative associated with this idiom, but the following kinds of usage are not rare:

I don't think he had the foggiest about selecting the best lemma entry.
I wonder whether he has the foggiest about what he's doing.

This is what favors the non-negative as lemma with redirects from the most common forms, including those with -n't. DCDuring TALK 01:11, 18 March 2013 (UTC)

This is a canonical negative polarity item in English, found only in negatives (including negation of the main clause when the NPI occurs in a subordinate clause) and questions (including indirect questions like "I wonder whether..."), just like any in "John does not have any potatoes", "I don't think John has any potatoes", "Does John have any potatoes?", "I wonder whether John has any potatoes" but *"John has any potatoes". I'd say move to have the foggiest or even the foggiest since I think "have got the foggiest" is also used. —Angr 11:53, 19 March 2013 (UTC)
Should any (explicit-verb-containing) negative polarity item contain "not" in the headword? I think not, though there may turn out to be exceptions. Of course, redirects from the most common negative containing forms might be helpful. DCDuring TALK 16:50, 19 March 2013 (UTC)
Move to have the foggiest, retain the redirect (would not be an ambiguous redirect). Mglovesfun (talk) 17:56, 19 March 2013 (UTC)
I think "idea" is an essential part of undIerstanding the phrase, even though it's dropped in some forms. Suggest we first create foggiest idea (idiom) and then either redirect other terms there or to have the foggiest idea (have the foggiest could be an alt. form). Facts707 (talk) 22:17, 16 November 2013 (UTC)
Having said that, I see "foggiest clue", "foggiest notion", etc. are not uncommon. I also updated foggiest with a second sense. It seems to make foggiest idea and have the foggiest idea less useful. Also, "get the foggiest..." is also popular.Facts707 (talk) 22:41, 16 November 2013 (UTC)

Category:English words with different meanings in different locations[edit]

This was originally nominated at WT:RFDO as this page didn't exist yet. I feel uneasy about the title. There's clearly some merit to it, like pissed meaning drink in the UK and angry in the US, but I hate the title 'English words with different meanings in different locations'. Mglovesfun (talk) 11:53, 29 March 2013 (UTC)

A similar page was RFDed/RFMed in the past; I'll see if I can find it. It was the one which was originally titled something like "words having different meanings on different sides of the pond"(!)... - -sche (discuss) 20:03, 16 March 2014 (UTC)

April 2013[edit]

Template:han tu form of[edit]

Two editors on 𫋙 and Talk:𫋙 (no I can't see those links either) have objected to the name han tu, saying it should be chu nom. I have no opinion on the matter. Mglovesfun (talk) 11:55, 7 April 2013 (UTC)

There is no need to move or rename this. It's just that using this template in 𫋙 and 𪜚 (which are chữ Nôm) is wrong. There is no problem using it in Sino-Vietnamese words; all pages linking to it are using it correctly except for those two. Wyang (talk) 12:02, 7 April 2013 (UTC)
Since that was me who made those two edits, what's the difference? Mglovesfun (talk) 14:07, 7 April 2013 (UTC)
Kauffner (talkcontribs) moved it unilaterally; I moved it back. Mglovesfun (talk) 22:14, 17 April 2013 (UTC)
"Hán" means Classical Chinese. "Nôm" is Vietnamese written with Chinese-style characters. The template says it is for "Vietnamese written in Chinese characters", so it should be called "Nom form of". Tự (words) and chữ (characters) are just descriptors and should not be treated as part of the name. See Vietnamese Nôm Preservation Foundation. Vdict defines hán tự as "Chinese literature", and chữ nôm as "demotic script (Ancient Vietnamese script)." I note that the phrase "unilateral" is being misused above, as there was in fact another editor who agreed to the move. Update: I looked at some of the links. They are mostly Vietnamese readings for modern Chinese characters. This is properly called "Han-Viet" or "Sino-Vietnamese reading". Every Chinese character has a reading of this kind; It's the Vietnamese equivalent to pinyin or Wade-Giles. You can get such readings from this site. Kauffner (talk) 04:45, 1 May 2013 (UTC)
Weirdly, that editor is the one that commented here and doesn't agree with it. Don't ask me why that is. Mglovesfun (talk) 10:38, 1 May 2013 (UTC)
Perhaps we can create another template for Nôm? In Vietnamese dictionaries, the Hán reading is labeled "H" or "Hv." (for Hán Việt). The Nôm reading is labeled "N". There is none of this Hán tự stuff. Update Here is a Vietnamese dictionary that uses the label "Hv" for Han readings. Type "nom" or some other syllable into the search function. Kauffner (talk) 16:11, 8 May 2013 (UTC)


I propose to move this to flash-bang. Primary usage seems to hyphenated, followed by usage with a space (flash bang), and as a single word (flashbang).”. bd2412 T 01:11, 20 April 2013 (UTC)

Moved. - -sche (discuss) 02:32, 22 January 2015 (UTC)

Module:zh to Module:cmn-common and Module:Hani-common[edit]

I suggested moving this on the talk page, and User:Wyang threatened to stop editing if we moved this. I don't think such a threat is really appropriate, so I am bringing it up here. My reasoning is that we don't treat zh as a language, and this module contains things that are specific to Mandarin that are not used for other Chinese languages. Therefore, I think that this should be split into a Mandarin-specific module (which would contain Pinyin transliteration) and a module for general handling of Han script (which would work for all languages that use it, presumably Japanese too). —CodeCat 12:43, 20 April 2013 (UTC)

I am not aware of all the background, but it seems to me that separating language- and script-specific processing functions is a different thing from how we organize our Chinese-language entries (which I see Wyang is concerned about). Anyway, Wyang should come up with any justification at all if he expects us to take his argument seriously. Michael Z. 2013-04-20 17:30 z
I feel like Wyang is holding us hostage... I don't care where we put it, so I guess oppose if that's what it takes. Not a proud oppose, mind you, but a coerced oppose. —Μετάknowledgediscuss/deeds 02:48, 21 April 2013 (UTC)
What's in the name? It seems User:Wyang is too sensitive about the issue. Well, the Chinese Wikipedia and Wiktionary uses "zh", even if they are in standard Mandarin. For many Chinese Mandarin = "Standard Chinese". User:Wyang is a smart editor, with great linguistic and coding skills, very productive and responsive too. I don't know. I second Metaknowledge, oppose as well but it's not very good to hold us hostage. It's much better to try and explain your position. --Anatoli (обсудить/вклад) 23:34, 23 April 2013 (UTC)
S  Wyang seems to have left en.Wiktionary, without actually saying why he opposes the split. Was he opposed to the existence of the language code cmn, or its use, or the idea of a Mandarin language? Michael Z. 2013-04-24 16:05 z
Judging from his user page, it seems that he felt that all Sinitic languages were one language, and treated the way we split them as a personal attack on him for some reason. —CodeCat 16:26, 24 April 2013 (UTC)
I'm bringing this back up. The code "zh" is still deprecated, so this should still be renamed for consistency. —CodeCat 01:02, 16 January 2014 (UTC)
@User:Atitarev Everyone knows what I think and knows what I think is unconstitutional. What else am I supposed to say here? That this treatment is a stupid, stupid policy that the unfamiliar are desperately clinging onto? It's not a personal attack on me; it is just stupidity of the power-holding unfamiliar majority. Wyang (talk) 03:50, 16 January 2014 (UTC)
In general, I agree with Wyang that the Chinese dialects should not have been split, but, it is a policy that was voted on (I can't even seem to find the archive of that discussion). But regardless of whether you agree, you need to follow policies, otherwise Wiktionary would not work. --WikiTiki89 04:01, 16 January 2014 (UTC)
Don't kill the messenger of the bad news :). I only advised you about the update. You yourself are inconsistent, you seem to dislike separation of Chinese dialects/topolects/languages/whatever but you're upset that your own dialect is not represented. FYI, I myself hold the view that Chinese entries can potentially be unified, especially considering that formal written Chinese is 99% the same across all existing dialects, especially on the single word level and all dialectal words (very minimal in quantity) can be addressed under "Chinese". I follow the vote, though, which makes sense, if you study it in a cool manner. --Anatoli (обсудить/вклад) 04:00, 16 January 2014 (UTC)
I am upset that covering the pronunciations in Shanghai or Guangzhou for example (making other dialects represented) would incur reduplications of essentially all content under the language heading. This is why I dislike separation. They are not contradictory. Wyang (talk) 04:06, 16 January 2014 (UTC)
Actually, there was probably no official vote, just lengthy discussion, e.g. here: Wiktionary:Beer_parlour_archive/2009/May#A_modest_request and made a policy. Like I said before, you can still set up a vote (or a revote, if there was a vote) and change this, only if you act coolly (without throwing tantrums :) . There are pros and cons - essentially the same writing and a huge number of cognates on the words that ARE different and the fact that remote topolects ARE mutually incomprehensible (the actual sounds). Since Wiktionary represents a WRITTEN language, it is possible to unify all Chinese topolects and show regional differences in pronunciation and usage. The same way Serbo-Croatian was done but that's a long battle. If you're not ready, please stick to the standard, as I said, there are pros and cons and people are aware of both similarities and differences. --Anatoli (обсудить/вклад) 04:16, 16 January 2014 (UTC)
The main point for unifying Serbo-Croatian was also reduplication of contents but all Serbo-Croatian forms are also mutually comprehensible, which made it easier but still there was a lot of resistance from nationalists (still is). I don't know if it's possible to sufficiently represent major Chinese forms under one header. --Anatoli (обсудить/вклад) 04:21, 16 January 2014 (UTC)
Chinese dialects are also mutually comprehensible in written form, and this dictionary is written not spoken. We can of course include pronunciations and audio files from different dialects just like we do with other languages. --WikiTiki89 05:17, 16 January 2014 (UTC)
If this a reply to me then this is what I also said. My last comment was about ability to cover large portions of dialects (can we, should we?), if they are necessary, so that Min Nan, Cantonese, Wu, etc. speakers can't complain that their topolect is not presented (pronunciation or variations in meaning or usage). --Anatoli (обсудить/вклад) 05:23, 16 January 2014 (UTC)
What I meant was that you said that Serbo-Croatian dialects were merged because they are mutually comprehensible, so I just pointed out that that applies to Chinese as well in written form. As for properly representing dialects of Chinese, merging won't affect that. If they are properly represented, they will continue to be. If they aren't then, they still won't be. The advantage will just be that there will be less duplication. --WikiTiki89 14:50, 16 January 2014 (UTC)

When I try to read any of our entries like I would an actual dictionary and I see a ton of different headers of varying shapes and sizes, my mind turns off to the content and I start believing what I'm reading is actually Wikipedia. Wyang's proposed version (see the entry for ) is much 'cleaner' and easier to read than the mess we have now, where each dialect wants representation and the majority of them have to be duplicated from the 'translingual' definition at the top. I hardly think there is going to be much, if any, information lost were we to collapse them under one header. And Anatoli brings up a good point: while the pronunciations may be different, the characters are so standardized that in written form they are mutually intelligible. While it is true we are different from other dictionaries, there are already several things inherent to Wiktionary that we should work with, like the fact we are online (not everybody has an internet connection) and that most of our content is written, not spoken (and the rest is on Commons). What do I expect when I read something like from jisho? Easy access to graphical etymology, radical, stroke count, derived shapes, and the different pronunciations for each region for the same character. And then there's our current entry on . Why does Middle Chinese get a ton of headers in its own section when all it has is a one word pronunciation section?

The layout that Wyang chose:

* Chinese:
*: Cantonese: [[安全]]
*: Classical Chinese: [[安全]]
*: Gan: [[安全]]
*: Hakka: [[安全]]
*: Huizhou: [[安全]]
*: Jinyu: [[安全]]
*: Mandarin: [[安全]]
*: Middle Chinese: [[安全]]
*: Min Bei: [[安全]]
*: Min Dong: [[安全]]
*: Min Nan: [[安全]]
*: Min Zhong: [[安全]]
*: Old Chinese: [[安全]]
*: Pu Xian: [[安全]]
*: Xiang: [[安全]]
*: Wu: [[安全]]

is quite fine, compact, and gets the information across easily. It has its own deficits, not everything is perfect the first time, but it's a much needed improvement over the current system.

And if anyone's worried the "Chinese" header is too prominent we can always suggest alternative versions, but we need something better than what we have now. My tentative modification to his layout:

* Translingual (character, radical, stroke count, metadata)
* Graphical etymology, etymology
* Pronunciation table:
*: Cantonese: (pronunciation)
*: Classical Chinese: (pronunciation)
*: Gan: (pronunciation)
*: Hakka: (pronunciation)
*: Huizhou: (pronunciation)
*: Jinyu: (pronunciation)
*: Mandarin: (pronunciation)
*: Middle Chinese: (pronunciation)
*: Min Bei: (pronunciation)
*: Min Dong: (pronunciation)
*: Min Nan: (pronunciation)
*: Min Zhong: (pronunciation)
*: Old Chinese: (pronunciation)
*: Pu Xian: (pronunciation)
*: Xiang: (pronunciation)
*: Wu: (pronunciation)
(I noticed the layout for [[Special:Redirect/revision/19364045|斗]] lacked readings + transliterations/translations for the other Sinitic languages, but we can fix that later, and besides those languages have their own headers anyway.)
* Definition table:
# definition
#* quotation (dialect)
* Usage notes:
* References:

TeleComNasSprVen (talk) 07:08, 16 January 2014 (UTC)

Thanks, this version of 斗 also includes pronunciations and transcriptions (Pinyin, Jyutping, POJ), and how various readings developed from the variant Old Chinese pronunciations (on the right). The senses are shared by the Chinese varieties. Wyang (talk) 08:11, 16 January 2014 (UTC)

Merge Wikisaurus:idiot and Wikisaurus:fool?[edit]

I realize that idiot and fool can carry different shades of meaning (idiot implies low intelligence, whereas fool implies poor judgment, which doesn't necessarily preclude intelligence), but given the amount of overlap between Wikisaurus:idiot and Wikisaurus:fool, I'm wondering if a merge of the two pages might be warranted. Astral (talk) 00:51, 27 April 2013 (UTC)

Well I dunno, while Wikisaurus probably doesn't have as much content as a real thesaurus at all, y'know thesauruses do tend to have entries for both say, word X and word Y, where word Y is a listed synonym for word word X. User: PalkiaX50 talk to meh 02:17, 27 April 2013 (UTC)
I agree with such a merger. I think we have an opportunity here to create a better thesaurus, one that provides a more informative communication of nuance. Just about every set of synonyms has subtle shades of meaning, formality, and so forth, that can best be compared on a single thesaurus page. bd2412 T 19:58, 27 April 2013 (UTC)
The template {{ws}}, used to add words to Wikisaurus pages, allows for the inclusion of a definition that appears upon mouse-over. I think this feature is sufficient to communicate subtle nuances of meaning. But the placement of many terms on Wikisaurus:idiot and Wikisaurus:fool strikes me as somewhat arbitrary. I mean, what makes dimwit a synonym of idiot, but not of fool? A single, consolidated Wikisaurus page would be easier to manage, and would make it easier for readers to find synonyms, as right now some dictionary entries link to Wikisaurus:fool while others link to Wikisaurus:idiot. Astral (talk) 22:33, 27 April 2013 (UTC)
  • Oppose; I think a meaningful distinction can be maintained. --Dan Polansky (talk) 09:13, 10 January 2015 (UTC)
  • Oppose: "fool" is not used in the context of mental disorders and "idiot" is not used in the context of court jesters. Purplebackpack89 17:40, 13 January 2015 (UTC)

Mandarin topical categories[edit]

It was discussed and agreed here: Wiktionary:Beer_parlour/2013/April#Some_small_changes_to_Mandarin_.28also_Cantonese.2C_Min_Nan.29_entry_structure_and_about_topic_categories_-_suggestion that Mandarin topical categories are to be similar to other languages with no distinction between traditional and simplified (no affect on parts of speech, only topical categories).

Simple renaming of categories to remove "_in_simplified_script" and "_in_traditional_script" is not a good idea before entries are corrected.

1. Could all Mandarin entries be edited by a bot to remove " in simplified script" and " in traditional script" in them? I.e. they should belong to Category:cmn:Family, not Category:cmn:Family in traditional script or Category:cmn:Family in simplified script?

That's the first step.

2. We also agreed that sorting order should be the same for trad./simpl., so that entries are sorted like simplified - by numbered pinyin, e.g. "jie3jie", not "女05姐姐" (see 姐姐). This is harder. It's OK if just the 1st part is done.

That entry instead of

[[Category:cmn:Beginning Mandarin in simplified script|jie3jie]]
[[Category:cmn:Family in simplified script|jie3jie]]
[[Category:cmn:Beginning Mandarin in traditional script|女05姐姐]]
[[Category:cmn:Family in traditional script|女05姐姐]]

Should have:

[[Category:cmn:Beginning Mandarin|jie3jie]]

The above entry is both simplified and traditional, if it's only one, then the category name should just be shortened.

3. When all entries are fixed, categories with "_in_simplified_script" and "_in_traditional_script" should be removed to without the suffix, or, if the shorter names exists, just deleted but not before the first step is done.

Is that possible? Can someone take it on? --Anatoli (обсудить/вклад) 01:22, 10 May 2013 (UTC)

May 2013[edit]

address with the polite V-form[edit]

Does English really not have a better term for this? I imagine that even if English doesn't have this phenomenon itself, it would still have a word to describe it in other languages. Also, what is its antonym? —CodeCat 13:21, 12 May 2013 (UTC)

The antonym is thou, though it may be obsolete. — TAKASUGI Shinji (talk) 17:31, 12 May 2013 (UTC)
I think English really doesn't have a word for this, even when talking about other languages. When I want to talk about it, I use the verb found in whatever language I'm discussing, so if I'm talking about French, I'll say vouvoyer and if I'm talking about German I'll say siezen. As in "When I was in Paris, I vouvoyered my host parents until they asked me to tutoyer them, but when I was in Vienna, I duzened my host parents right away." (Actually, this brings up an interesting phenomenon I've noticed among English-speaking expats living in Germany: when we adopt German verbs when speaking English, some of us leave the infinitive -en on and say "I siezened him, I duzened her", while others of us drop the -en and say "I siezed /ziːtst/ him, I duzed /duːtst/ her".) —Angr 18:37, 12 May 2013 (UTC)
Yep, the non-Romance words don't even start with V, which I find problematic. Mglovesfun (talk) 20:44, 18 May 2013 (UTC)
The formal pronoun is called V-form and the informal T-form regardless of language. Thus, this could be moved to address with the V-form (and address with the informal T-form to address with the T-form). — Ungoliant (Falai) 21:09, 18 May 2013 (UTC)

Rock Paper Scissors[edit]

Tagged but not listed. Also Scissors Paper Stone, Paper Scissors Stone. Should not have any capital letters, perhaps this is uncontroversial enough to just move them. Mglovesfun (talk) 10:20, 18 May 2013 (UTC)

S.  Michael Z. 2013-05-18 18:42 z
Are we supposed to know what that means? —Angr 20:32, 18 May 2013 (UTC)
My best guess is 'support', but it is a guess. Mglovesfun (talk) 20:43, 18 May 2013 (UTC)


Should be merged into [[briar]], which has better structure, but not all of the content of [[brier]]. DCDuring TALK 14:39, 20 May 2013 (UTC)

Yes check.svg Done. - -sche (discuss) 22:58, 22 January 2015 (UTC)

June 2013[edit]

Appendix:Japanese Swadesh list[edit]

This page is quite a dog's breakfast. The list includes numerous terms that don't belong in a Swadesh list; see the list's Talk page for details.

Glancing over the list, I thought some of the content looked different from how I remembered it. Poking around in the history of the Appendix:Japanese Swadesh list page and the Wiktionary:Japanese Swadesh list page, I realized why -- apparently Croquant (talkcontribs) and I had had the same idea at nearly the same time back in 2006, and he launched the Appendix: page, while I launched the Wiktionary: page four days later.

Comparing the two pages, the Appendix page has gotten a lot more editing traffic, but sadly appears to be less usable -- more Chinese-derived terms, more compounds, and more inflected forms (all inappropriate for a Swadesh list), and less useful information given (no Notes or Usage, for instance). Add to that the fact that the wikicode is harder to work with (as each column is given in a single huge list, but it's each row instead that the editor must work with).

With all that in mind, I'd like to propose that we merge the Appendix:Japanese Swadesh list page with the Wiktionary:Japanese Swadesh list page, with a bias towards keeping the wikicode from the Wiktionary: page and merging in any preferred data from the Appendix: page. If no one objects, I may set to that task in a week or two. Once done, my sense is that we should delete Wiktionary:Japanese Swadesh list, or at least turn it into a redirect to Appendix:Japanese Swadesh list. If anyone feels otherwise, please chime in. -- Eiríkr Útlendi │ Tala við mig 19:47, 1 June 2013 (UTC)

This sounds more like a subject for WT:RFM Chuck Entz (talk) 19:57, 1 June 2013 (UTC)
  • Ah, yes, somehow I'd gotten it into the back of my head that RFM was only for moves, not for mergers. Moving there. -- Eiríkr Útlendi │ Tala við mig 01:14, 2 June 2013 (UTC)

Anatoli's Angr's post here copied from Appendix talk:Japanese Swadesh list:

I don't think anyone has taken lexicostatistics seriously in forty years. All Swadesh lists are useless for determining the genetic relatedness of languages, regardless of whether they're filled with native words or loanwords, because the methodology has proven to be flawed. The only point in having Swadesh list appendices at Wiktionary is to provide a list of basic words that we need to have entries for. —Angr 20:44, 1 June 2013 (UTC)
Arrowred.png Is lexicostatistics as a whole discredited, or just Swadesh's approach? Is there any value in keeping these pages, then? Should we just remove them, if they're not to be maintained? We have plenty of other, more highly-trafficked lists that help us keep track of what terms we're missing and might want to add. Curious, -- Eiríkr Útlendi │ Tala við mig 23:27, 4 June 2013 (UTC)
Both. Lexicostatistics makes the assumption that language change is a homogenous, continuous process that can be reduced to mathematical models. In the real world, there are things like regional and social variation, and things like sociopolitical and economic forces (not to mention blind luck) that often determine which form survives. Swadesh lists are interesting, and provide a rough view of variation between languages, so they're probably worth keeping in the appendices. I wouldn't base anything on them as evidence, though. Lexicostatistics is usually a lot better than flipping a coin, but there are too many ways for it to go wrong, since it depends on unverifiable past events. Chuck Entz (talk) 02:09, 5 June 2013 (UTC)
Considering the amount of work I've put in on the Burmese and Irish Swadesh lists and the amount of work I'm planning to put in on the Lower Sorbian, Old Irish, and Welsh Swadesh lists, I'd be opposed to deleting them. I don't know of any other lists of terms we need for those languages. —Angr 12:58, 5 June 2013 (UTC)

@Chuck, thank you for the detail. I'm clearly behind in my reading.  :)

@Angr, understood. I'm fine with keeping them.

That said, if we are to keep them, I feel rather strongly that the lists should be cleaned up -- despite Angr's comment, known-borrowed words have no place in any such list, even if the methodology has been entirely discredited. At the bare minimum, drilling down to root forms for these concepts would itself give us a list of terms needed for etymological purposes. I'm working through JA terms to add etymologies, which is how I wound up coming back to this list in the first place.  :)

Also, if we are to keep them, presumably we should only keep one per language, yes? And presumably in the Appendix: namespace?

Cheers, -- Eiríkr Útlendi │ Tala við mig 15:34, 5 June 2013 (UTC)

  • I'm sorry, I don't see any reason to exclude loanwords if a loanword is the most common term for a particular concept. The English Swadesh list itself has a large number of loanwords, including they, husband, animal, forest, fruit, flower, skin, egg, vomit, give, count, sky, mountain, and correct. One per language, yes, though there's nothing wrong with keeping some language-family lists too, though these need to be kept within reason. Some currently existing ones run off the right edge of the screen because they contain so many languages. AFAICT all Swadesh lists are already in Appendix: mainspace, which seems like the best place for them to me. —Angr 16:05, 5 June 2013 (UTC)
  • Re: namespaces, my original comment in this thread concerns a duplication, with one such JA Swadesh list in Appendix:, and one in Wiktionary:.
  • Re: loanwords, my understanding was that the whole point of Swadesh lists was for historico-comparative research? If so, known loanwords would be irrelevant. I'm not opposed to keeping a list of modern terms for Swadesh concepts, but that wouldn't be a Swadesh list then, no? Would an acceptable compromise be to add a column with a header such as Modern equivalent? -- Eiríkr Útlendi │ Tala við mig 16:14, 5 June 2013 (UTC)
If anything, I'd rather have a separate column for native words that are now obsolete/archaic or that now have different meanings. To stick with the English examples, the native words deer, blossom, hide, spew, and reckon are all modern English too, so it would be odd to exclude them from the "Modern equivalent" column. They just don't mean "animal", "flower", "skin", "vomit", and "count" anymore, or are at least not the most common way of expressing those ideas. But they could be in a column to show that they are the modern English descendants of the Old English words that did have those meanings. —Angr 16:39, 5 June 2013 (UTC)
  • I was thinking about something along the lines of the format at Wiktionary:Japanese Swadesh list. This includes some JA-specific headings, but the Usage and Notes columns could conceivably be used to convey this kind of information -- like for deer, to describe how it is used now and how that differs from the older meanings. -- Eiríkr Útlendi │ Tala við mig 21:47, 5 June 2013 (UTC)

Wiktionary:Sample entry[edit]

This was created as an example of how Simple Wiktionary (simple:Wiktionary:Main Page) formats entries. I started to update it to en.Wikt format... but it's redundant to Wiktionary:Entry layout explained#Additional_headings. Should we merge the two pages by deleting WT:SE, or merge them by moving the sample entry off WT:ELE and putting it on WT:SE? - -sche (discuss) 18:08, 26 June 2013 (UTC)

Question book magnify2.svg Input needed
This discussion needs further input in order to be successfully closed. Please take a look!

I like it. I wouldn't get involved in trying to revise WT:ELE when Wiktionary:Sample entry could be so useful for the most basic questions. WT:ELE should be some kind of definitive manual for resolving many questions not faced by new contributors. At least one version of the Sample entry should be much simpler - therefore less complete. DCDuring TALK 01:41, 23 January 2015 (UTC)

"xx nouns lacking gender" to "xx terms with incomplete gender"[edit]

Sometimes we want things other than nouns to have genders, but I doubt we want another category for that. "terms" is better than "entries" because we also include genders in translations, which are not entries. There is also a difference between lacking a gender altogether and simply having an incomplete gender. For example, Slovene nouns divide masculine nouns into animate and inanimate, and this is normally specified as part of the gender (m-an, m-in). So if you specify just "m" for a Slovene noun, it's not a complete gender, but it's not lacking a gender either. So "incomplete" is more inclusive. The same applies to Dutch, where users may specify "c" as the gender but this should really be "m" or "f". —CodeCat 17:31, 29 June 2013 (UTC)

Category:Combining diacritics‎ - Category:Combining characters[edit]

This seems redundant to me. -- Liliana 19:18, 29 June 2013 (UTC)

Support merger. - -sche (discuss) 23:01, 22 January 2015 (UTC)

sleep on it[edit]

Can we merge this into sleep on? I don't see why they should be separate since they have the same meaning. Mglovesfun (talk) 14:54, 16 July 2013 (UTC)

Sure. But this should remain as a redirect to sleep on. I think that many folks only come across the expression with it and may look it up that way. The same principle probably applies to many expressions. I suspect that many of the entries we have containing a verb and it merit similar treatment, though each would need to be inspected to confirm that. DCDuring TALK 17:12, 16 July 2013 (UTC)

A. E. F.[edit]

B. E. F.[edit]

C. E. F.[edit]

Into A.E.F./B.E.F/C.E.F. Surely spaces alone aren't a good enough reason to have these as alternative form, could even merge the whole lot into the dotless forms AEF/BEF/CEF. Mglovesfun (talk) 16:25, 17 July 2013 (UTC)

Template:polytonic to Template:grc-Grek or to Template:Grek-polyton[edit]

The first option brings it in line with other script codes like Template:fa-Arab and Template:nv-Latn. The language code in the name doesn't have any meaning in itself, it's just to give a meaningful distinction.

The second makes it more compliant with the official language subtag registry, which recognises "polyton" as a subtag to indicate polytonic Greek (not as a script code in itself!). See [1]. This option is probably the more "correct" of the two. —CodeCat 13:06, 23 July 2013 (UTC)

Grek-polyton is preferable because not all Greek written in polytonic is Ancient Greek. Modern Greek is officially defined as starting in 1453 and it was written in polytonic for over 500 years after that. —Angr 09:12, 27 July 2013 (UTC)
Like I said, the language code doesn't mean it's used only for Ancient Greek, it just means "the Ancient Greek script variety" or "the variety of the script associated with Ancient Greek". In the same way, "fa-Arab" is used by many other languages beside Persian. —CodeCat 11:14, 27 July 2013 (UTC)

Not renamed. The script code in Module:scripts/data was not changed either. Keφr 14:04, 3 January 2015 (UTC)

Appendix:Portuguese verbs in -or[edit]

Move to Appendix:Portuguese verbs ending in -or, so it sounds less strange. — Ungoliant (Falai) 12:01, 25 July 2013 (UTC)

Yes. Not sure this needs a debate though. Mglovesfun (talk) 19:02, 27 July 2013 (UTC)


Hereafter is stilted to say the least, and incomprehensible to many native English speakers. I propose that we use something like Category:Afterlife. —Μετάknowledgediscuss/deeds 03:46, 30 July 2013 (UTC)

Yup. Mglovesfun (talk) 09:56, 30 July 2013 (UTC)
  • I agree. —Angr 13:37, 2 August 2013 (UTC)
Support. - -sche (discuss) 08:46, 17 November 2013 (UTC)

Template:CGK to Template:oko-Kore or Template:okm-Kore[edit]

To make it fit with the naming scheme used by our other script codes. —CodeCat 11:58, 31 July 2013 (UTC)

Though it would fit with {{okm}} more ({{oko}} is from the period of time before Hangul was invented), I'd actually prefer it to be kept as is, because it's occasionally used outside Korean (Category:Cia-Cia language comes to my mind). -- Liliana 14:05, 31 July 2013 (UTC)
The language code doesn't really have any significance as far as I can tell. For comparison, "fa-Arab" is used by a lot more languages than just Persian, look in Module:languages for all occurrences of "fa-Arab". We could (and maybe should) come up with a better naming scheme for scripts like these. —CodeCat 15:21, 31 July 2013 (UTC)

August 2013[edit]

Category:Regionalisms - Category:Regional terms by language[edit]

A big mess with lots of overlap and miscategorization. -- Liliana 23:30, 1 August 2013 (UTC)

I think there was a similar proposal a while ago, I just don't remember where it went. Also there's Category:Dialectal terms by language to make it more interesting. —CodeCat 23:35, 1 August 2013 (UTC)

do you speak something[edit]

Good idea, crappy title, badly executed. Maybe do you speak... would be better. —Μετάknowledgediscuss/deeds 00:13, 17 August 2013 (UTC)

I disagree that this is badly executed, I don't think it's more than a little bit worse than anything else. How about do you speak (something) or do you speak (language)? Mglovesfun (talk) 11:17, 14 September 2013 (UTC)
Originally this was named do you speak...?. Of course, the question mark is not needed and should not be used there. —Stephen (Talk) 11:33, 14 September 2013 (UTC)


I think it should be moved to Category:en:Bones. --ElisaVan (talk) 08:59, 21 August 2013 (UTC)

Support, but let's call it "List of bones". There are a lot of categories like this that could benefit from less ambiguous names. DTLHS (talk) 23:43, 21 August 2013 (UTC)
No preference; it's not exactly ambiguous what either skeleton or bones refers to. Mglovesfun (talk) 11:07, 14 September 2013 (UTC)

bee's knees[edit]

Suggest merging the bee's knees into bee's knees. Per redirect at the the cat's pyjamas. I'm not sure of Wiktionary SOP, so noting here. HTH. Quiddity (talk) 23:10, 22 August 2013 (UTC)

I would suggest, instead. merging the other way: is bee's knees ever used in any other combination than with "the", as in the bee's knees? Chuck Entz (talk) 00:34, 23 August 2013 (UTC)
I too would suggest unifying them as the bee's knees. Mglovesfun (talk) 19:44, 23 August 2013 (UTC)

September 2013[edit]

Category:Greenlandic Eskimo Pidgin language[edit]

I propose renaming the language Greenlandic Eskimo Pidgin to Greenlandic Pidgin. google books:Greenlandic Eskimo Pidgin doesn’t even pass CFI, while google books:Greenlandic Pidgin does. Another possibility is West Greenlandic Pidgin, which is what Wikipedia calls it.

The language’s only entry originally had the heading “Greenlandic Pidgin”, which was then changed by Daniel Carrero apparently without due process, so that’s an argument for speedy-renaming it back to the original name. — Ungoliant (Falai) 14:35, 1 September 2013 (UTC)

Yes check.svg Done. - -sche (discuss) 23:08, 22 January 2015 (UTC)


I am proposing that entries such as *reťi (and *moťь, *noťь, *dъťi and others) and *meďa (and *svěťa, etc.) be renamed to *rekti (*moktь, *noktь, *dъkti) and *medja (*světja), respectively; i.e. as they usually spelled in academic works. Another inconsistency is that some entries have the intrusive *l, while others do not (compare *čaplja : *zemja). -- 10:45, 14 September 2013 (UTC)

I support using -kt-/-tj-/-dj- in these cases. WT:ASLA already specifies that epenthetic l's should be included, so Appendix:Proto-Slavic/zemja needs to be moved to Appendix:Proto-Slavic/zemlja. —Aɴɢʀ (talk) 10:50, 24 September 2013 (UTC)
There is no difference between -kt- and -tj-, the distinction is purely etymological. So I don't support making it. And WT:ASLA did not originally specify that the l should be included, Ivan unilaterally rewrote most of that page and it does not represent consensus. —CodeCat 11:21, 24 September 2013 (UTC)
If the difference is purely etymological, then surely the etymology section of an entry is the place to make it. I don't see any objections being raised to the inclusion of the -l-, and in consensus-building silence implies consent. Personally I'd prefer to exclude it because we should be giving the oldest reconstructable form (hence -kt-) and the -l- is "unetymological". —Aɴɢʀ (talk) 11:49, 24 September 2013 (UTC)
Surely if we want the oldest reconstructable form, we should be reconstructing PIE and not Proto-Slavic? Reconstructions should concern themselves with the latest common ancestor, not the earliest. There is no descernable difference between -kt- and -tj- in Slavic, both have the exact same outcome in all languages. So the comparative method that linguists use to make reconstructions will give one phoneme, which has been labelled as *ť on Wiktionary and Wikipedia. To reconstruct the difference between -kt- and -tj- requires "outside information", which is not always available. It would be a bit like reconstructing the distinction between short a and o for Proto-Germanic depending on their origin, even though these clearly merged. —CodeCat 11:55, 24 September 2013 (UTC)
And concerning -j- or -lj-, there is no clear linguistic consensus on whether -lj- is original or -j-, so we just picked one to standardise on. —CodeCat 11:57, 24 September 2013 (UTC)
Internal reconstruction within the protolanguage and comparison with sister languages and protolanguages is also part of historical linguistics, and distinguishing tj < *kt from tj < *tj provides useful information. We don't have to put blinders on and look only at what's reconstructable from the daughter languages, especially since the majority of published sources don't either, and do distinguish the two types of tj. If we didn't allow internal reconstruction within the proto-language, we'd never reconstruct any PIE laryngeals at all except in words directly attested in Anatolian (and even then we would never reconstruct h₁ at any rate). —Aɴɢʀ (talk) 12:11, 24 September 2013 (UTC)
I think you're mistaken. While some linguists are in the habit of reconstructing laryngeals to account for any occurrence of *a or a long vowel, there are many who don't and disagree with this practice. Ringe for example explicitly argues that not all cases of *a should be reconstructed as *h₂e just for the sake of it. But there are many cases where the descendants rule out *a and require *h₂e, so then it can be reconstructed. This doesn't apply to Slavic *ť though. There are no examples of any discernable difference between *kt and *tj in any Slavic language, so trying to distinguish them is always going to be an irregular and incomplete process. And there's also a more esthetic argument: Proto-Slavic didn't allow syllables to end in an obstruent, and we don't have reconstructions with obstruent-final syllables anywhere. Yet *noktь has such a syllable, so it would be internally inconsistent if we used this representation, unless we somehow "decide" that *kt is actually a single phoneme. And if you get to that point then you might as well just respell that phoneme as *ť... —CodeCat 12:53, 24 September 2013 (UTC)
What cases are there where non-Anatolian descendants "rule out *a and require *h₂e"? Reconstructing kt in Proto-Slavic is no different than reconstructing ɸ in Proto-Celtic (or, as I said, h₁ in PIE—or for that matter e-vocalism next to h₂ and h₃); if we know from other evidence that it was there, there's no reason to exclude it, and certainly no reason for reconstructions to "concern themselves with the latest common ancestor, not the earliest". —Aɴɢʀ (talk) 14:15, 24 September 2013 (UTC)
Well actually, the Proto-Slavic we reconstruct here is not actually the latest common ancestor, it's later. As far as I can tell, we have certain sound changes applied to our reconstructions, even though they can be demonstrated to have occurred after certain other changes that we don't apply. For example, the liquid diphthongs were changed in a dialect-specific way before the vowels *o and *a differed in quality (because *or is lengthened to *ra in South Slavic). But the quality distinctions must have arisen before a whole lot of accent changes that happened in late Common Slavic, such as the creation of accent class B (which we reconstruct). But in all of these cases we represent "archiphonemes" that can be reconstructed for all Slavic languages based on comparative evidence. *or is an archiphoneme that should be understood as meaning different things in different Slavic dialects. The same should be done for *ť, for which comparative evidence gives only a single phoneme rather than two, so there is nothing beyond that to reconstruct. —CodeCat 14:39, 24 September 2013 (UTC)


конденсат Бозе — Эйнштейна[edit]

To конденсат Бозе - Эйнштейна. I think the common practice is to use plain hyphens in page names? —CodeCat 20:26, 15 October 2013 (UTC)

Not universally. Hebrew, at least , uses U+05BE. I can't speak for конденсат Бозе — Эйнштейна.​—msh210 (talk) 18:31, 16 October 2013 (UTC)
WT:Entry titles does actually say to use the hyphen minus not any of the dashes. What does WT:ARU say? WT:Entry titles is quite new and therefore does not necessarily reflect a strong consensus. Mglovesfun (talk) 21:20, 16 October 2013 (UTC)
Not an easy one but I'd say keep as is. The form "Бозе-Эйнштейн" (with a plain hyphen) would imply that it is a name of one person, "" is implying that there were two people. Cf. names of people "Склодо́вская-Кюри́" (Skłodowska-Curie), "Бонч-Бруе́вич" (Bonch-Bruyevich) (these are hyphenated names). If something was named after Skłodowska-Curie and another person, the only would be to use "". Not sure about transliteration of "", which also has grammatical usage in Russian. --Anatoli (обсудить/вклад) 22:56, 16 October 2013 (UTC)
I found the applicable rule about "тире (tirɛ́)" (): тире (I should have known it!). "...ме́жду имена́ми со́бственными, совоку́пностью кото́рых называ́ется уче́ние, явле́ние и т. п. (уравне́ние Менделе́ева — Клапейро́на; матч Каспа́ров — Ка́рпов)" - "("" is used) ...between proper names, whose combination is used to name a teaching (doctrine), a phenomenon, etc. (e.g. Mendeleyev - Clapeyron equation, Kasparov - Karpov match). --Anatoli (обсудить/вклад) 23:10, 16 October 2013 (UTC)
Keep as is, then.​—msh210 (talk) 05:54, 22 October 2013 (UTC)

Are we using typewriting or typesetting conventions for our main entries? Shouldn’t we be consistent in this?

Good English-language typography would use an en dash or real apostrophe in certain places (e.g., Bose–Einstein condensate, don’t) instead of a hyphen or neutered typewriter apostrophe (Bose-Einstein condensate, don't). I don’t know about Russian type-writing conventions, but in English usage the em dash is typically typed as a double hyphen (as конденсат Бозе--Эйнштейна), or perhaps a spaced hyphen (конденсат Бозе - Эйнштейна).

Anatoli, is the long dash always spaced in Russian typesetting? Michael Z. 2013-11-18 02:55 z

google books:"конденсат Бозе — Эйнштейна" shows both spaced and unspaced m-dashes (and some of the spaced dashes are short enough to be n-dashes, but that could just be the strange font. --WikiTiki89 03:10, 18 November 2013 (UTC)
After taking a closer look at more of the results, it seems that every combination of {n-dash, m-dash, hyphen} × {spaced, unspaced} exists. --WikiTiki89 03:12, 18 November 2013 (UTC)
Missed the questions, sorry. The prescribed method is to space the long dash but this rule is not always followed, apparently. Re "Are we using typewriting or typesetting conventions for our main entries?". It's both typographical and correct web version. The long dash is often replaced with a short dash in informal writing but the long dash and spaces around are standard in this case. --Anatoli (обсудить/вклад) 03:15, 18 November 2013 (UTC)


This is an unused template that contains only a schoolboy exercise of the conjugation of do, mostly perphrastic, of course, and incomplete as a table of all periphrastic equivalents of all tenses and aspects that can be expressed in English. Thus it is misnamed and misleading. If anything it ought to be in the creator's user space, renamed as {{en-conj-do}}. DCDuring TALK 14:41, 17 October 2013 (UTC)

If you plug in other terms, it outputs the forms of the verb you've plugged in. Observe: {{en-conj|love|loved||loving}} yields:
That doesn't mean we really need it, of course, but it does do more than you thought it did. —Aɴɢʀ (talk) 16:24, 17 October 2013 (UTC)
I was so annoyed that it didn't work as it used to, as the inflection-line template (or redirect thereto) for English conjugations, that I didn't bother to look. That it has no documentation makes that particularly easy. It needs the "principal parts" (3, 4?) in order to generate the periphrases that it covers.
Were it deployed in English L2s I think it would be a great way to ensure that we get fewer native speakers to use Wiktionary, to continue phase one of the linguistic cleansing process. DCDuring TALK 16:54, 17 October 2013 (UTC)
Do you mean the inflection-line template for English conjunctions? That's now at {{en-con}}. Anyway, I have no objection to deleting this (it's unused anyway) since we already provide the principle parts on the headword line and everything is derivable from those parts, especially if we have an Appendix:English verbs for the benefit of learners. —Aɴɢʀ (talk) 17:29, 17 October 2013 (UTC)
Besides, it needs fixing: buried deep in the paradigm are "he will has" and "he would has". Chuck Entz (talk) 02:17, 18 October 2013 (UTC)

I created a documentation that there are no more confusions and thus I think this discussion is finished, Keep as is. --Bigbossfarin (talk) 13:49, 28 October 2013 (UTC)

I don't think so. There is so little value to English conjugation tables that it doesn't seem to me that it merits taking a name that should be used for English conjunctions. Mindless uniformity across languages might be fine for other languages, but not for English on English Wiktionary. Why not rename it as {{en-conjugation}}? DCDuring TALK 14:00, 28 October 2013 (UTC)
I'm split. The template is too well made to delete, but on the other hand it is entirely useless since we don't conjugate English verbs in entries (and I would be opposed to doing so). I guess I would support moving it to {{en-conjugate}}. But I definitely oppose moving {{en-con}} to {{en-conj}} and would also oppose redirecting {{en-conj}} to {{en-con}}. If {{en-conj}} doesn't contain a conjugation table, then it most certainly should not contain a conjunction template. This is not mindless uniformity, this is to avoid confusion. --WikiTiki89 14:20, 28 October 2013 (UTC)
Another way to avoid confusion would be to rename "xx-conj" templates to "xx-conjg". We know have confusion among contraction, conjunction , and conjugation templates, which could be avoided by other shortcuts "xx-contr", "xx-conjct", and "xx-conjg". This template name has the most potential for confusion. DCDuring TALK 15:49, 28 October 2013 (UTC)
Maybe you're right, but using different abbreviations for each language is much more confusing than having ambiguous abbreviations. --WikiTiki89 15:58, 28 October 2013 (UTC)
A discussion about the name of the templates you can already find here: Template talk:en-con. Since this discussion names of some templates for conjunctions were changed to "xx-con", see: {{eo-con}}, {{nl-con}}, {{arc-con}}, {{cmn-con}}, {{lo-con}}, {{nan-con}}, {{hy-con}}, {{ka-con}}, {{xcl-con}}, {{sh-con}}, and {{ur-con}}. So everyone who wants to use {{en-conj}} for header of conjunctions is wrong, and if you look at Special:WhatLinksHere/Template:en-conj there is not one content page which uses this template as header. I don't think that we have to move anything because it would be a big effort to change the lemma of all the listed templates. Greetings Bigbossfarin (talk) 12:35, 29 October 2013 (UTC)
Could we rename -decl and -conj to -infl instead? Then the problem would be sidestepped. And "infl" is more general, because it can apply to things that aren't conjugation or declension, like Dutch pronominal adverbs or Irish prepositions. Declension and conjugation are primarily Indo-European-biased terms and don't fit well in many other cases, nor is it even clear what should be done when they're mixed together. —CodeCat 16:19, 20 November 2013 (UTC)

November 2013[edit]

various places where WT:LANGTREAT and Module:languages are inconsistent[edit]

Module:languages includes codes from the individual members of several language/dialect groups which WT:LANGTREAT says, without citing any discussion, should be merged. Something needs to change: either WT:LANGTREAT should be updated to note that the individual varieties are allowed, or their codes should be removed from the module. The following language/dialect groups are affected:
(Note 1: whenever the merging of a particular dialect group had been discussed and that discussion was cited by LANGTREAT, I simply updated the module.)
(Note 2: Haida, Cree and Kalenjin face the same issue; I expect to write about them later.)
- -sche (discuss) 05:16, 20 November 2013 (UTC)

the Baluchi lects[edit]

Baluchi (bal) has at least six dialects. Ethnologue has encoded three, namely bcc (Southern Baluchi/Balochi), bgp (Eastern Baluchi/Balochi) and bgn (Western Baluchi/Balochi).

Various editions of the Encyclopedia Britannica say that "Despite the vast area over which Balochi is spoken, its numerous dialects are all mutually intelligible." / "Despite the vast area over which [Balochi] is spoken, its six dialects (Rakhshani, Sarawani, Kechi, Lotuni, the Eastern Hill dialects, and the coastal dialects) are all believed to be mutually intelligible." Alan S. Kaye, in Phonologies of Asia and Africa (including the Caucasus) (ISBN 1575060191), on page 762, is slightly more cautious: the "Balochi dialects [...] are six in number, and with one exception they are all mutually intelligible." (Emphasis mine.) He writes that Eastern Hill is among the mutually intelligible dialects, but Google hides enough of his book that I can't see which one he considers unintelligible.

What should be updated, the module (to remove the dialects) or LANGTREAT (to legitimize them)? - -sche (discuss) 05:16, 20 November 2013 (UTC)

I don't think there is a difference. These should most certainly be merged. -- Liliana 17:25, 20 November 2013 (UTC)

the Gondi lects[edit]

Stephen Tyler (not the singer), in his oft-cited works on Gondi, states "Though I have no real evidence, the general pattern seems to be for geographically adjacent Koya and Gondi populations to speak different, but mutually intelligible Gondi dialects. Where these populations are geographically non-contiguous, the dialects are not mutually intelligible. This same pattern probably prevails among all Gondi dialects." WP says "The more important dialects are Dorla, Koya, Maria, Muria, and Raj Gond." Ethnologue, meanwhile, as encoded only two varieties, ggo (Southern Gondi) and gno (Northern Gondi). Should we deprecate those two codes? Or deprecate the macro-code gon and recognise those dialects? Or allow all three? - -sche (discuss) 05:16, 20 November 2013 (UTC)

Persian, Dari, etc[edit]

Although LANGTREAT notes that they should be subsumed into fa, the following codes still exist in Module:languages:

  • pes, for "Western Persian", the most common variety of Persian. We should merge it into fa because it *is* fa.
  • prs, Eastern Persian / Dari, the variety of Persian spoken in Iran Afghanistan. Its status as a separate language, and its very name 'Dari', were products of Afghanistani politics. Not even Afghani speakers of the language call it 'Dari' or consider it separate from Persian; we shouldn't consider it separate, either.
  • aiq, Aimaq, a variety spoken by nomads in Afghanistan and Iran. It is sometimes considered specifically a variety of Dari (which is itself little more than another name for Persian, as explained). It differs from standard Persian mainly in matters of pronunciation, something we usually handle with {{a}} rather than separate L2s.
  • haz, Hazaragi, another Afghan variety. WP summarizes scholarly opinion (with citations, for which look here): "The primary differences between Standard Persian and Hazaragi are the accent and Hazaragi's greater array of Mongolic loanwords. Despite these differences, Hazaragi is mutually intelligible with other regional Persian dialects."
  • deh and phv, Dehwari and Pahlavani, which it is hard to find information on because even WP simply redirects the words to "Persian".

As indicated above, my opinion is that we should merge all of those codes into fa.
Incidentally, LANGTREAT originally also banned Tajik (tg), but this was not supported by scholarship or by our own practice (we had hundreds of Tajik entries), so after two discussions, I updated the page to note that Tajik is allowed. LANGTREAT made no mention of Judeo-Persian (jpr), Bukhari (bhh), Judeo-Tat (jdt) or Tat (ttt), and past discussions of them have assumed they were separate languages, so I also updated the page to reflect that. - -sche (discuss) 05:16, 20 November 2013 (UTC) (fixed think-o)

The Persian lects are an interesting issue; they are on the whole pretty similar, but Persian and Tajik have separate literary and cultural traditions, and I believe Dari does too. I think it is best to keep them separate. The Jewish varieties are often written in the Hebrew script and have a separate cultural tradition, so I think it would probably be handy to keep them separate as well. All the rest probably ought to be merged into their macrolanguages, unless there are script conflicts I'm unaware of (it is, of course, easier to keep with one script per language). —Μετάknowledgediscuss/deeds 05:23, 20 November 2013 (UTC)
The difference between Dari and Persian is not great AFAIK, there are some references on Wikipedia. Tajik should stay separate, not just because it's in Cyrillic. It's very different from Persian and has many Russian and Turkic loanwords. There is also a significant difference in phonology (vowels). Persian e, o and â are usually i, u and o in Tajik. ZxxZxxZ (talkcontribs) may be able to say a bit more. --Anatoli (обсудить/вклад) 05:36, 20 November 2013 (UTC)
We also currently include "Parsi" (prp) and "Parsi-Dari" (prd), which Wikipedia suggests are spurious(!). - -sche (discuss) 05:58, 3 December 2013 (UTC)
Regarding Dari, to merge Dari into Persian, we would have to figure out what to do with transliterations. In standard Persian, ē merged with ī into what we transliterate as i (no diacritic) and ō merged with ū into what we transliterate as u. In Dari, ē and ī and ō and ū are still differentiated. Furthing complicating the problem, standard Persian e, o, ey, and ow are pronounced i, o, ay and aw in Dari, although these differences are not phonemic. The other differences are not as much of a problem, but see a brief description at w:Dari#Phonology. --WikiTiki89 14:37, 4 December 2013 (UTC)

The followed was copied here by User:-sche from User talk:Dijan:

Hi, Do you think Dari can be merged with Persian? See Wiktionary:Requests_for_moves,_mergers_and_splits#Persian, Dari, etc. {{context|Dari|lang=fa}} can still be used. CC ZxxZxxZ (talkcontribs). --Anatoli (обсудить/вклад) 04:56, 4 December 2013 (UTC)

That has been the practice on Wiktionary. Dari should be under the Persian heading with {{context|Dari|lang=fa}} label. That is what we do already. Take a look at فاکولته, for example. Regarding the transliteration of long vowels, ZxxZxxZ (talkcontribs) has been trying to implement a classical Persian transliteration (which is pretty much used for Dari by scholars) as a standard for all Persian entries. So far, it's been a slow and selective process. I'm not opposed to it and it can easily be indicated as the standard Wiktionary practice in the Appendix:Persian transliteration. --Dijan (talk) 06:35, 5 December 2013 (UTC)
Thanks. Do you mind posting your answer on Wiktionary:Requests_for_moves,_mergers_and_splits#Persian, Dari, etc and perhaps address Persian/Dari vowel differences raised? Where can I look at the classical transliteration? --Anatoli (обсудить/вклад) 00:18, 6 December 2013 (UTC)
By the way, if you happen to know anything about Parsi or Parsi-Dari (and about their relationship to Farsi and Dari), your input on that subject would also be appreciated over in the same section. :) - -sche (discuss) 00:53, 6 December 2013 (UTC)
I support keeping Dari (and Western Persian) under Persian heading, but I'm not sure what to do about transliteration. By the way, Eastern Persian / Dari (prs) is the variety of Persian spoken in Afghanistan, not Iran, that of Iran is the first one, Western Persian (pes). --Z 17:48, 12 December 2013 (UTC)
Oh, yep, I've fixed my think-o. - -sche (discuss) 21:25, 12 December 2013 (UTC)
I've merged pes and prs into fa. - -sche (discuss) 22:42, 27 May 2014 (UTC)

the Uzbek lects[edit]

Uzbek (uz), Northern Uzbek (uzn) and Southern Uzbek (uzs). Which, if any, should go? - -sche (discuss) 05:16, 20 November 2013 (UTC)

The latter... -- Liliana 17:25, 20 November 2013 (UTC)
Quoth Asya Pereltsvaig in Languages of the World: An Introduction (2012, ISBN 1107002788), page 102: "Sometimes Standard Uzbek is also referred to as Northern Uzbek, to distinguish it from a related language, Southern Uzbek, spoken by 1,400,000 speakers in northern areas of Afghanistan." (The Concise Encyclopedia of Languages of the World, 2010, adds that "Southern Uzbek includes the dominant urban dialects of Tashkent, Bukhara, Samarkand, etc.") So, uzn should definitely go. uzb should probably go, too, in part because it doesn't seem to be a single, unified thing with firm differences from uz / uzn; instead, it's the other part of the continuum that starts with northern/standard Uzbek and gets progressively more "Iranized" / influenced by Persian, e.g. in in the pronunciation of vowels (per the Concise Encyclopedia of Languages of the World and the works of Settar Cabbar). - -sche (discuss) 21:30, 21 November 2013 (UTC)

Category:English words with consonant pseudo-digraphs[edit]

Should be Category:English terms with consonant pseudo-digraphs. Ditto for Category:English words with vowel pseudo-digraphs. Mglovesfun (talk) 18:29, 20 May 2010 (UTC)

I've moved this thread out of the archive of unresolved discussions that went stale in 2010 in the hope that we can finally resolve it. - -sche (discuss) 06:35, 21 November 2013 (UTC)

December 2013[edit]

Rhymes pages from using : as the separator to using /[edit]

So for example from Rhymes:Dutch:-ɑn to Rhymes:Dutch/-ɑn. Using / makes more sense because the software splits page names on slashes. —CodeCat 00:29, 8 December 2013 (UTC)

I agree. Plus it would be less likely to be confused with 'ː' (the long vowel symbol). --WikiTiki89 00:38, 8 December 2013 (UTC)
Why keep the hyphen? Mglovesfun (talk) 19:19, 9 December 2013 (UTC)
  • I oppose. Keep it where it is, keep the hyphen. --Dan Polansky (talk) 07:33, 14 September 2014 (UTC)
This discussion has been overtaken by events, and by a vote about this subject. - -sche (discuss) 23:09, 22 January 2015 (UTC)


Lunfardo is a Spanish argot of sorts from the region of the River Plate. Currently there are Spanish entries for it, but they point out the Lunfardo heritage in the etymology sections, using this template, as if Lunfardo were a dialect of a different language. I see Lunfardo as a register of Spanish instead, and think that (like vesre) we should change it to being a context label and edit all the entries thus. Note that some Lunfardo words only seem to be used in running text in milongas, whereas others have been borrowed into the mainstream and are found in otherwise normal/colloquial Spanish text; I'm not sure how we can or should try to distinguish these. —Μετάknowledgediscuss/deeds 04:19, 9 December 2013 (UTC)

The context label for Spanish can be created if necessary, but I oppose the deletion of this template as there are Lunfardo loanwords in other languages. — Ungoliant (Falai) 19:06, 9 December 2013 (UTC)
If that's true, then it does seem worthwhile to keep this template (or, now that it's been moved to a module: this code). - -sche (discuss) 21:16, 21 December 2013 (UTC)
Kept. - -sche (discuss) 23:10, 22 January 2015 (UTC)

Appendix:Glossary of police vehicle slang[edit]

It seems like this could be moved into the Wikisaurus entries for police car, paddywagon, etc, and/or into a hypernym entry like Wikisaurus:police vehicle. (The "police bike" terms, which both seem literal and unidiomatic, could probably be dropped along the way.) - -sche (discuss) 08:28, 9 December 2013 (UTC)

Done. - -sche (discuss) 23:14, 22 January 2015 (UTC)

Category:English terms derived from Medieval Greek[edit]

To Category:English terms derived from Byzantine Greek. We have a separate code "gkm" for Byzantine Greek, so we might as well use it. —CodeCat 18:37, 9 December 2013 (UTC)

Moved. - -sche (discuss) 02:37, 22 January 2015 (UTC)

Category:US State Capitals[edit]

This category-rename request was listed on RFC all the way back in 2009, before this page existed (IIRC). I've moved it here in the hope that we can finally address it.

This topical category that is a subcategory of Category:Capital cities needs a rename, but there are several logical possibilities, so I wanted to get some input.

Category:US state capitals
The simplest rename, but still somewhat clunky and not well suited to be paralleled for similar topical categories covering other countries. Plus I'd prefer to avoid using US in category names.
Category:American state capitals
Better suited to paralleling, say for example in Category:Canadian provincial capitals, but unlike Category:American English, I don't think the ambiguity of American can be justified on the grounds of euphony.
Category:State capitals of the United States
Form that I'd happen to prefer. However...
Category:State capitals in the United States
... is the form used on Wikipedia, but the equivalent categories for other countries are a mixture of in and of so I don't see a compelling reason to blindly follow Wikipedia here.

In short unless consensus calls for another choice, I'll see about moving these over to Category:State capitals of the United States in about a week or so. — Carolina wren discussió 03:50, 18 November 2009 (UTC)

I think I prefer an option not listed: Category:Capital cities of US states. --EncycloPetey 01:32, 22 November 2009 (UTC)

I think we should go with Carolina Wren's Option 1 and move this to Category:US state capitals. - -sche (discuss) 02:18, 10 December 2013 (UTC)

To be honest, I don't see why we need this category. Isn't Category:Cities enough? --WikiTiki89 02:30, 10 December 2013 (UTC)
Hm, this category is the one outlier in Category:Capital cities; we never actually had the Category:Canadian provincial capitals which Carolina wren mentioned. OTOH, extreme overcategorization of placenames does seem to be the fashion of the day; see the categories which were recently created, one for each of the various Divisions of Pakistan, India and Bangladesh. I don't actually have a strong opinion on whether it stays or goes... just that if it stays, everything after "US" should be lowercase. - -sche (discuss) 06:35, 10 December 2013 (UTC)
I would go as far as to say that we don't even need Category:Capital cities. If people want a list of capital cities, they can go to Wikipedia. --WikiTiki89 13:51, 10 December 2013 (UTC)

The Rwanda-Rundi lects[edit]

We currently separate {{rw}}, {{rn}}, {{haq}}, {{suj}}, {{han}}, and {{vin}}, which can all be treated as a single language and often are; their separation seems largely political. The Wikipedia page Rwanda-Rundi language catalogues the differences between rw and rn: they are pretty minor, and a lot seem to have to do with regular spelling differences and tones, which are not even reflected in the standard orthography and could thus be relegated to pronunciation sections. To quote Zorc and Nibagwire's Kinyarwanda and Kirundi comparative grammar (2007):

The terms dialect and language are used loosely in everyday communication. In linguistic terms, the two are bound together in the same definition: a language consists of all the dialects that are connected by a chain of mutual intelligibility. Thus, if a person from Bronx, New York can speak with someone from Mobile, Alabama, and these two can converse with someone from Sydney, Australia without significant misunderstandings, then they all form part of the English language. Kigali [the capital of Rwanda] and Bujumbura [the capital of Burundi] are similarly connected within a chain of dialects that collectively make up the Rwanda-Rundi language.

Kimenyi's A Relational Grammar of Kinyarwanda (1980) explains that:

This language [Kinyarwanda, rw] is very close to both Kirundi [rn], the national language of Burundi, and Giha [haq], a language spoken in western Tanzania. The three languages are really dialects of a single language, since they are mutually intelligible to their respective speakers.

That seems like a strong case for merger to me, although I'd like to see if any academic sources disagree. (Pinging User:-sche as well, just to try it out.) —Μετάknowledgediscuss/deeds 01:52, 17 December 2013 (UTC)

I got the ping, thanks. :) I've just been busy. I'll look into this more closely soon, but on the face of it, it does seem like we could merge them. (And that reminds me that en.Wikt really needs to have a discussion about merging Nynorsk and Bokmal. It's bizarre that we manage to accept that Drents and Twents — and, to use the example above, the English of Alabama and the English of Australia — are not separate languages, but haven't managed to accept that Nynorsk and Bokmal aren't. But that's for another discussion...) - -sche (discuss) 06:04, 19 December 2013 (UTC)
But cf. Appendix:Swadesh lists for Bantu languages, which shows large differences between the two. -- Liliana 14:41, 14 February 2014 (UTC)

Category:French plurals to Category:French noun forms or Category:French noun plural forms[edit]

Category:Portuguese plurals to Category:Portuguese noun forms or Category:Portuguese noun plural forms[edit]

Category:Italian plurals to Category:Italian noun forms or Category:Italian noun plural forms[edit]

Same for Aragonese, Asturian, Aromanian, Corsican, Emilian, Extremaduran, Friulian, Galician, Gallo, Guernésiais, Istro-Romanian, Jèrriais, Ladin, Ladino, Ligurian, Middle French, Mirandese, Neapolitan, Norman, Occitan, Old Spanish, Romansch, Sicilian, Tarantino, Venetian.

These languages have more than one form called "plural", as adjectives can also have plurals. So these categories have misleading names. This move was already done for Spanish and Catalan some time ago, so we might as well do it for all languages whose use of "plural" matches that of Spanish. I don't know if we should use "noun forms" or "noun plural forms", though. (Spanish uses Category:Spanish noun forms) —CodeCat 19:29, 25 December 2013 (UTC)

I'd prefer just to categorize them all as plurals. However that's not politically possible, and since it isn't, I'd prefer Category:French noun plural forms since we won't be including inflected forms like joueuse, which in terms of its formation is an inflected form, even if it's a lemma in its own right. Mglovesfun (talk) 21:56, 26 December 2013 (UTC)

take someone's point -> take the point[edit]

As the target seems to be the most common form. I'm also going to soft redirect with {{alternative form of}}:

And also note the exclamatory entry point taken. TeleComNasSprVen (talk) 10:35, 28 December 2013 (UTC)

January 2014[edit]

Non-idiomatic Vietnamese words[edit]

The following pages should be moved to titles that do not include classifiers:

Though more descriptive than English articles, Vietnamese classifiers serve the same grammatical function. Therefore, Wiktionary should not have entries like "con gián" ("a cockroach").

See also Wiktionary:Requests for deletion#Non-idiomatic Vietnamese words.

 – Minh Nguyễn (talk, contribs) 10:29, 3 January 2014 (UTC)

I've used Wyang (talkcontribs),s template {{vi new}} to create "bạch dương". It seems to work well and adds IPA. I've also added a desired parameter (cls=) - a classifier (also measure word, counter) "cây". Since this problem (as it turns out) with Vietnamese dictionaries is quite common, when new entries are created, old entries should probably be turned to hard redirects rather than deleted. See [2], which translate "poplar" as "cây bạch dương" rather than simply "bạch dương" or "(cây) bạch dương", making users believe that classifier "cây" is part of the word. My Berlitz dictionary has the same erroneous feature (inconsistent, like vdict.com). --Anatoli (обсудить/вклад) 02:31, 7 January 2014 (UTC)
In the event that someone learning Vietnamese actually confuses a classifier as part of the actual word, I'd support hard redirecting them to the actual word entry. There are some words that are taken from Sino-Vietnamese readings of Han characters, so it'd not be unusual for people to conflate the two in terms of grammar. By the way, is your name Anatoli or Atitarev? TeleComNasSprVen (talk) 04:56, 7 January 2014 (UTC)
OK, then. Not sure what you mean by confusion with Chinese. The Sino-Vietnamese terms are borrowed without the classifier and Chinese classifiers are never added in translations in any dictionaries the way Vietnamese are sometimes. See 拖拉机 (tuōlājī) to see how the measure word (classifier) 台 is displayed. I haven never seen 台拖拉机 or similar as a mistranslation. My name is Anatoli Titarev, Atitarev is my nickname @Wiktionary. --Anatoli (обсудить/вклад) 05:18, 7 January 2014 (UTC)
Re: "Sino-Vietnamese terms are borrowed without the classifier and Chinese classifiers" Yes but, how would English learners of Vietnamese distinguish between the two, between words that need classifiers and words like khách sạn (Han-derived was what I meant) which don't need them? Unless they actually looked at some of the usage notes at con, or a general Vietnamese tutorial on grammar. Too often, dictionaries translate these things inaccurately enough people will just assume con is part of the actual word. TeleComNasSprVen (talk) 06:01, 7 January 2014 (UTC)
On further thought, I don't think English speakers would be likely to confuse particles like the, el, las, le, les as part of the word they're modifying, so maybe my argument doesn't hold as much weight, but there really ought to be a proper introduction to Vietnamese grammar that would dispel some of the confusion translation programs introduce, especially when they include con as part of the word. TeleComNasSprVen (talk) 06:08, 7 January 2014 (UTC)
Vdict.com is largely a mirror of the Free Vietnamese Dictionary Project, which the Vietnamese and French Wiktionaries have also imported. (FVDP's Vietnamese-English dictionary is riddled with errors, so it shouldn't be imported here.) I believe FVDP's English-Vietnamese dictionary was intended for Vietnamese speakers who need to look up English words, so a bit of inconsistency in classifier usage wouldn't have been viewed as a significant problem. – Minh Nguyễn (talk, contribs) 07:04, 7 January 2014 (UTC)
I think "cls=" parameter could be more descriptive than just showing classifier in brackets, like Mandarin "mw=", see 拖拉机 entry.
Re: errors in dictionaries. It seems for Vietnamese people is natural to translate English words with classifiers, like "dog" is "con chó". It's different from other languages with classifiers. E.g. in Mandarin "a dog" is (yī tiáo gǒu), in Japanese (ippiki no inu) you need a number before a classifier. Since this "riddled with errors" dictionaries are common, we need redirects, rather than deletions. You can move entries to entries leaving a redirect behind. Do you guys have the authority to move entries? You can request the right, I think.
See also Wiktionary:Beer_parlour/2013/November#Measure word regarding formatting of classifier (measure word, counter) entries. --Anatoli (обсудить/вклад) 22:17, 8 January 2014 (UTC)
One of the more interesting things I found reading Minh's links to the various scientific publications attempting to analyze Vietnamese was the use of this construction of con in dialogue:
"Tôi muốn mua con heo."
"Mấy/Bao nhiêu con?"
"Hai con." (instead of "hai heo")
I'm not sure how classifiers function in the other languages ("re: you need a number before a classifier") but it is pretty unique in Vietnamese. TeleComNasSprVen (talk) 23:22, 8 January 2014 (UTC)
In other languages you can also use "number + classifier" only or "determiner + classifier", like English "this one", "3 of those", etc. --Anatoli (обсудить/вклад) 23:37, 8 January 2014 (UTC)
In your example above "Tôi muốn mua con heo." do you need a classifier? Doesn't it mean "a pig" (one pig)? Is "con" without a number imply "one (of)"? Mandarin equivalent:
Wǒ yāo mǎi zhū. (no classifier, just I want to buy a pig/pigs (ambiguous), "one pig" would be / (yī tóu/zhǐ zhū)
/ Yāo mǎi jǐ tóu/zhǐ?
/ Liǎng tóu/zhǐ. --Anatoli (обсудить/вклад) 23:54, 8 January 2014 (UTC)
My analogy regarding the English article "a" works in isolation, but the two languages are different enough that you can surely find situations where the analogy falls apart. As I tried to explain to Dan Polansky in the RfD, my point was that both English and Vietnamese tend to introduce nouns with an auxiliary word.
Anyhow, "Tôi muốn mua con heo" could be understood as either "I want to buy [this/that] pig" ("Tôi muốn mua con heo [này/đó]"), or as "I want to buy a pig" ("Tôi muốn mua [một] con heo"). As in Mandarin, you'd typically say, "Tôi muốn mua heo," without the classifier, to ambiguously mean "I want to buy pig." More examples:
  • In response to "Mấy con?", "Mỗi một con" means "Every single one" (literally, "Each one [CLS]"). But note that some linguists take this to be evidence that classifiers are just nouns that can be used a certain way, not a distinct part of speech. It is simpler to think of "con heo" as a noun phrase.
  • "Tôi trồng chuối" means "I plant banana trees," even though the sentence leaves open the possibility of literally stuffing bananas into the ground. "Tôi trồng cây chuối" would be the stilted machine translation.
  • w:vi:Mít ("Jackfruit") starts out: "Mít là loài thực vật ăn quả... Quả mít là loại quả quốc gia của Bangladesh." ("Jackfruit is a fruit-bearing plant species... The jackfruit is the national fruit of Bangladesh.")
 – Minh Nguyễn (talk, contribs) 08:16, 9 January 2014 (UTC)
In Mandarin you can also say 我想買一隻豬 ("I want to buy a pig"), 我想買隻豬 ("I want to buy a pig") or 我想買豬 ("I want to buy pig"), exactly the same as Vietnamese. Wyang (talk) 08:25, 9 January 2014 (UTC)
While I don't think we should have classifiers in lemmas, it's too strong to call their use in translations "errors". This is the convention, especially for translationaries aimed at Vietnamese speakers. Besides, many dictionaries are perfectly upfront about their usage, even if they don't have the space to remind readers in every entry. – Minh Nguyễn (talk, contribs) 08:16, 9 January 2014 (UTC)
The move is complete of all terms listed (if I haven't missed any). --Anatoli (обсудить/вклад) 06:28, 23 April 2014 (UTC)

advice animal[edit]

Shouldn't this definition be moved to the plural form advice animals, which is more popular in terms of use? TeleComNasSprVen (talk) 18:20, 10 January 2014 (UTC)

Category:Alternative forms by language[edit]

All categories here only contain other categories now, no entries. Most of the subcategories don't really fit the Wiktionary definition of an "alternative form", either, though. We treat an alternative form as a form that is more or less interchangeable, and has the same usage frequency and register. But that definitely doesn't apply to rare, dated or archaic forms, or to misspellings or proscribed forms, and so on. So this category and its subcategories should really be renamed. But to what? —CodeCat 16:31, 23 January 2014 (UTC)

no flies on[edit]

to no flies on someone.

See WT:TR#no flies on. DCDuring TALK 13:12, 24 January 2014 (UTC)

  • Oppose. If it's established practice here that we can refer to nonconstituents as "phrases" (as suggested at the discussion linked to above), then I prefer to keep this entry where it is and call it a "phrase" rather than a noun. If I read "there are certainly no flies on him" and didn't know what it meant, no flies on rather than no flies on someone would be what I looked up. —Aɴɢʀ (talk) 13:33, 24 January 2014 (UTC)
You could certainly make the case that this expression is not "really" a noun as it is virtually exclusively used as part of a predicate, ie, not as a subject of a clause or object of a preposition. DCDuring TALK 18:51, 24 January 2014 (UTC)
And the fact that it modifies another noun directly. No noun could syntactically fit in "There are ___ that man." —Aɴɢʀ (talk) 19:28, 24 January 2014 (UTC)
I can think of one noun that would fit: no-fly zone. (sorry, I'll go now). By the way, Wiktionary needs an entry for the noun nonconstituent (non-constituent). Pengo (talk) 21:42, 25 January 2014 (UTC)

Category:Constellation Genitives[edit]

At a minimum, this should be Category:Constellation genitives, but is there an even better name for it? Should it exist at all? - -sche (discuss) 22:16, 26 January 2014 (UTC)

Appendix:Latin/oclus to oclus[edit]

oclus is a Vulgar Latin form, not a mere alternative spelling of oculus. And it is attested in the w:Appendix Probi, so it's not a reconstruction. --Fsojic (talk) 14:58, 28 January 2014 (UTC)

caula to caulae[edit]

caulae is a plurale tantum, no reason to have it in the singular. --Fsojic (talk) 19:08, 28 January 2014 (UTC)

February 2014[edit]

Merge Category:Euphemistic forms by language into Category:Euphemisms by language[edit]

I think we should merge Category:Euphemistic forms by language (and it's subcategories) into Category:Euphemisms by language (and it's subcategories). --WikiTiki89 17:48, 6 February 2014 (UTC)


Karachay is a regional division of the w:Karachay-Balkar language: Category:Karachay and Category:Balkar can be found in Category:Regional Karachay-Balkar. This category seems to be strictly an artifact of {{Karachay}} being changed to use the topical category system rather than the regional category system, which was continued in module:labels/data. I'm guessing it was originally done that way to avoid automatic generation of Category:Karachay Karachay-Balkar.

Given that everything in both Category:Karachay and this category are all in the Karachay-Balkar language (language code krc), this seems like a misuse of the topical category system. This was brought up last year in the Beer Parlour (Wiktionary:Beer_parlour/2013/May#Karachay and Science context labels, but apparently ignored- probably because it was the wrong venue.

We should change the label "Karachay" to a regional label with plain_categories="Karachay" in the module, and merge this category into Category:Karachay. Chuck Entz (talk) 20:49, 17 February 2014 (UTC)

wouldn't say boo to a goose[edit]

not to be able to say boo to a goose

These aren't the only variations. Searching on "to say boo to a goose" and "said boo to a goose" shows that, although the nominated entries cover the vast majority of uses, there are a significant minority that seem to show productivity centered around the set phrase "say boo to a goose".

I think should create an entry for "say boo to a goose" with a definition to the effect of "speak up; be assertive", and note that it's mostly used in the negative to describe timid or unassertive people. The two nominated entries should then be merged with it, and perhaps converted to redirects. Chuck Entz (talk) 21:25, 17 February 2014 (UTC)

Another common variant, somewhat old-fashioned nowadays, is "say bo to a goose". —Aɴɢʀ (talk) 13:59, 27 June 2014 (UTC)

Renaming “Upper Guinea Crioulo” to “Guinea-Bissau Creole”[edit]

Compare: google books:"Upper Guinea Crioulo" (10 hits), google books:"Guinea-Bissau Creole" (1650 hits). — Ungoliant (falai) 05:18, 18 February 2014 (UTC)

Support. The old name can stay as an alternate name, natch, and the autonyms Kriol, Crioulo, Kriolu, Kriyol, and Kiriol can be added as other alternate names. - -sche (discuss) 07:19, 18 February 2014 (UTC)
Done. The entries remain to be updated. - -sche (discuss) 02:44, 22 January 2015 (UTC)
I think I've updated all affected entries. - -sche (discuss) 17:48, 22 January 2015 (UTC)

the Huave lects[edit]

Varieties of Huave are spoken in four villages in Mexico. Ethnologue gave each one its own code: San Dionisio del Mar Huave is hve, Santa María del Mar Huave is hvv, San Francisco del Mar Huave is hue, and San Mateo del Mar Huave is huv. Confusingly, we call the last of those (huv) plain "Huave".

Specialist literature, such as Yuni Kim's dissertation on Topics in the Phonology and Morphology of San Francisco Del Mar Huave, speaks of "Huave dialects", and Campbell likewise considers that the villages speak dialects of a single language isolate. "Huave languages" seem to be spoken of only in connection with the (unsupported) idea that the "Mixe-Zoque-Huave languages" form a family.

I suggest that we merge hve, hvv and hue into huv. Failing that, we need to rename huv (from plain "Huave" to "San Mateo del Mar Huave")... - -sche (discuss) 20:26, 18 February 2014 (UTC)

Category names containing "US"[edit]

I believe that the punctuated U.S. is the more formal usage, and has the advantage of not being mistaken for an all-caps instance of the word, "us". I therefore propose to move all categories containing "US" (e.g. Category:US State Capitals, Category:fr:US States, and Category:Southern US English) to titles containing "U.S.". By my count, this covers about 50 categories in total. If approved, I will be glad to do all of the renaming and recategorization. bd2412 T 21:29, 18 February 2014 (UTC)

I actually think we'd be better off renaming them to categories containing the unabbreviated "United States". --WikiTiki89 21:50, 18 February 2014 (UTC)
I would absolutely agree with that, as it eliminates all possible ambiguity. For states, we would have to change it to "States of the United States" to avoid the alliteration of "United States States". bd2412 T 22:06, 18 February 2014 (UTC)
We wouldn't have to, but I agree it would make it less awkward. Anyway, I see no problem with "States of the United States". --WikiTiki89 22:16, 18 February 2014 (UTC)
I disagree. At least part of the time, people have to type these category names by hand, and even a couple of extra characters every time can be a nuisance (I'm surprised you aren't going all the way and suggesting "the United States of America").
I fail to see how the "US" in category names could ever be mistaken for a pronoun- do you really think people are going to look at Category:US States and mistake it for a colloquial version of "we states"?
It looks very much to me like a solution in search of a problem, with no real benefit, unless you can call forcing people to do more typing a benefit. Chuck Entz (talk) 04:16, 19 February 2014 (UTC)
Our category names, being part of the visible public product, should at least look formal and professional. bd2412 T 04:24, 19 February 2014 (UTC)
Support renaming to "United States". Note that we do currently have Category:Languages of the United States of America (rather than Category:Languages of the United States); I don't know if it should be renamed for consistency. - -sche (discuss) 18:51, 19 February 2014 (UTC)
For an English-speaking audience, "of America" is indeed probably superfluous. bd2412 T 21:00, 20 February 2014 (UTC)
Is there any further comment/opinion on this? bd2412 T 00:32, 16 March 2014 (UTC)
Attributive US and noun United States. So US state capitals (caps sic) and Languages of the United StatesMichael Z. 2014-03-16 04:11 z
Is that just an opinion on whether United States should be spelled out, or is it also addressed to the question of whether we should use a punctuated U.S.? bd2412 T 18:29, 17 March 2014 (UTC)
Both. These are also the forms recommended by the Chicago Manual of Style. Michael Z. 2014-03-17 21:56 z
I see no reason to abbreviate. --WikiTiki89 21:57, 17 March 2014 (UTC)

Merge North Levantine Arabic ("apc"), South Levantine Arabic ("ajp"), and Syrian Arabic ("sem-syr") into Levantine Arabic[edit]

See also: User_talk:Stephen_G._Brown#Merging_Levantine_Arabic_dialects_into_one_language

There is absolutely no reason to have these as separate languages. Yes, it's true that there are some pronunciation differences between various dialects, but the vocabulary is largely the same (except that the Lebanese dialect uses a lot of French borrowings and the Israeli dialects use a lot of Hebrew borrowings). The grammar is identical. But the most compelling reason is that the divisions we have are completely arbitrary and there is much more variation within these regions than there is between them (not to mention that Syrian Arabic is no more than a sub-dialect of Northern Levantine, seemingly leaving Northern Levantine to refer to just Lebanese). --WikiTiki89 22:41, 19 February 2014 (UTC)

See also Category talk:Syrian Arabic language. --WikiTiki89 23:15, 19 February 2014 (UTC)
I don't know enough about it to say whether apc and ajp should be merged, but sem-syr should definitely be abolished and merged into apc. —Aɴɢʀ (talk) 16:08, 20 February 2014 (UTC)
I was actually very surprised to find that there are two separate ISO codes for North and South Levantine. They are about as different as Bostonian vs New York English. --WikiTiki89 22:54, 20 February 2014 (UTC)
I wonder what the code sem-syr was intended to represent. There is more variation between one region of Syria and the next than between one region of Syria and a neighbouring region of Iraq or Lebanon. One textbook (Sociolinguistics / Soziolinguistik, 2006, ISBN-13 978-3-11-0184181) sums it up by saying "In terms of dialectal variation, three major Arabic dialect groups are represented within Syria. In the north eastern region (bordering Iraq) dialects of the Mesopotamian group are spoken, and the rest of the Syrian desert in the east is of Najdi Peninsular Arabic type. In the rest of the country varieties of North and South Levantine Arabic are spoken, which can be distinguished from one another by a number of features. In the south western corner (bordering Jordan), a type of southern Levantine (commonly known as Haurani) is spoken..." WP suggests that "Levantine Arabic" is likewise composed of rather more than two mutually intelligible dialects, making our binary split curious. - -sche (discuss) 01:18, 21 February 2014 (UTC)
North and South are probably the most distinctive difference in the Levantine dialects mostly due to the pronunciation of the long ā. In the North, it's realized as [æː~ɛː~eː] in unemphatic contexts and [ɑː~ɒː~ɔː] in emphatic contexts, while in the South, it is realized as [aː] in unemphatic contexts and [ɑː~aː] in emphatic contexts. There are also some minor vocabulary differences such as the North preferring شو (šū) for "what?" and the South preferring إيش (ʾēš). But these hardly constitute enough of a difference to treat them as separate languages. And as I mentioned before, there are more differences within these regions than there are between them, such as regional realizations of /q/. Mutual intelligibility, however, is a tricky criterion, because if we went by that we'd have to merge all dialects of Arabic (Levantine, Gulf, Egyptian) except for Maghrebi and many small isolated ones. --WikiTiki89 01:45, 21 February 2014 (UTC)
Heck, if we went by that, we'd have to merge Bokmål and Nynorsk back into Norwegian, and Dutch Low German and German Low German back into Low German, and who knows what other mergers that would probably be a good idea. —Aɴɢʀ (talk) 09:33, 21 February 2014 (UTC)
Yeah it turns out that for a dictionary spelling is more important than intelligibility, which is one reason that I think Mandarin and Cantonese should be re-merged. But of course it makes it difficult for languages with no standard such most Arabic dialects. --WikiTiki89 18:33, 21 February 2014 (UTC)
I agree with the merge. The difference between Syrian and Lebanese dialects is more political than linguistical. In fact, by our criteria, a lot of dialectal Arabic words and forms they should go under "Arabic", without any dialect distinction, perhaps a qualifier "colloquial", "regional", "East Arabic", "Gulf", etc. Some words that we mark as Egyptian Arabic are often used in many East Arabic dialects or are just too colloquial to be considered classical or standard, especially many borrowings, also there are some relaxed spelling forms, more typical for Egypt and Sudan but absolutely not exclusive to these regions. I also disagree with inclusion of Egyptian or other Arabic entries/translations, which are only pronounced differently from the standard. Considering how few written dialectal contributions we have, we could merge a few dialects, excluding Maghrebi. Note that dictionaries, such as Hans Wehr include dialectal words, just marking them by a region/regions. I am away in Dubai, London and Brunei, only contributing a little at the moment. --Anatoli (обсудить/вклад) 19:10, 21 February 2014 (UTC)
I was also thinking that we could merge all of Arabic together, but that would be a much larger decision that would need a vote and would require figuring out how to handle major differences in grammar, such as the fact that most dialects conjugate verbs differently from MSA. Merging smaller closely related dialect groups together is a much easier task and will make it easier to add entries for them. The reason I have refrained from adding Levantine entries is because I can't be bothered to add everything three times. I would suggest that we also merge all Maghrebi dialects into Maghrebi and all Gulf dialects into Gulf, but I personally don't know as much about these dialects to feel comfortable proposing this myself. --WikiTiki89 20:05, 21 February 2014 (UTC)
Yes, more merges may require a vote, same as with merging Sinitic varieties. Grammatical differences in Arabic dialects may be marked with qualifiers as well but they can be grouped, so that we maintain less dialects, which are almost identical grammatically and lexically. Perhaps such distinction should become important ONLY if we are really going to have e.g. separate conjugation tables for Egyptian, Levantine, etc. verbs (or other inflections), e.g. so that users can find that "bitidrisu"/"byudursu" ("they write") are different in Egyptian and Levantine Arabic. --Anatoli (обсудить/вклад) 21:47, 21 February 2014 (UTC)
Another consideration. Arabic dialects are mainly spoken, not written with some exceptions. Are forms like ايمتى رحيرجع؟ (Levantine) or حيرجع امتى؟ (Egyptian) "When will he return?" attestable? Standard Arabic inflections can be confirmed by citations. Is it true for dialects? --Anatoli (обсудить/вклад) 22:09, 21 February 2014 (UTC)
Sources describing dialectal grammar use romanisation for obvious reasons. Dialects use vocalisations extremely seldom. Such inflection tables would not be very useful if they used Arabic diacritics, as e.g. there are no special symbols for "e" and "o" and Egyptians read "q" as a glottal stop and jiim as /g/, so these examples would be written as something like "eemtaa raH-yirja3" / "Ha-yirga3 imta", obviously not attestable forms. Hopefully it makes sense. --Anatoli (обсудить/вклад) 22:27, 21 February 2014 (UTC)
For Egyptian, they are probably attestable. For Levantine it might be harder, but hopefully still doable for the most common words. Also, in Levantine the future marker رح is usually written as a separate word (thus: ايمتى رح يرجع؟, ēmtā raḥ yirjaʿ). The difficulty of vowel marking will have to be resolved with transliterations, that is our only choice as far as I can see (IPA would be too specific when we don't want it to be). --WikiTiki89 23:07, 21 February 2014 (UTC)
Re the comment about Nynorsk, etc: I don't want to stray too far off topic, but I do think we should merge Nynorsk and Bokmål. And iff we merged Nynorsk and Bokmål, I would not oppose merging Dutch Low Saxon and German Low German, though I wouldn't support it, either. Dutch Low Saxon and German Low German already represent mergers of a large number of lects that SIL / Ethnologue / ISO had deemed distinct enough to grant codes to: Dutch Low Saxon is Achterhoeks (act), Drents (drt), Gronings (gos), Sallands (sdz), Stellingwerfs (stl), Twents (twd), Veluws (vel); German Low German is Westphalian (wep); frs could mean either East Frisian the Low German lect or East Frisian the Frisian lect (SIL refuses to clarify which one it was intended to mean, and I have strong but as of yet unconfirmed suspicions that it's used both ways around here); and Plautdietsch (pdt) ... well, exists. - -sche (discuss) 23:33, 21 February 2014 (UTC)
Before we can do this (assuming there will be at least a couple more people who weigh in and agree), we will need to decide on a language code. Should we use "apc", "ajp", or a new one altogether (such as "sem-lev")? Since I don't understand what "apc" and "ajp" actually stand for, I can't say whether it would be appropriate to use one of them for the entirety of Levantine (the only sort of guess I have is that "ajp" could be "Arabic Jordanian Palestinian", but I can't even make a guess for "apc"). --WikiTiki89 20:05, 21 February 2014 (UTC)
More than likely, apc stands for "Arabic" + "all the descriptive combinations are taken by other languages so we'll use pc". Chuck Entz (talk) 20:47, 21 February 2014 (UTC)
"Arabic, Phoenician Coast"? "Aarabic, Lepanese and Cyrian"? —Aɴɢʀ (talk) 22:15, 21 February 2014 (UTC)
A Perfect Circle? Wait, wrong APC...
It's probably what Chuck says. In any case, even if apc and ajp do stand for something, we can still use either one to represent point, if we want to... for "Antillean Creole", we combined the ISO's gcf ("Guadeloupean Creole French") and acf ("Saint Lucian Creole French", but presumably abbreviating "Antillean Creole French") into gcf (even though, if you think about what the codes stand for as abbreviations, it might have made more sense to merge them into acf). - -sche (discuss) 22:30, 21 February 2014 (UTC)
I think the Arabic dialects that are mutually intelligible with standard Arabic should be handled the way the Romani lects are currently handled, viz. "Only the macrolanguage is allowed an L2 header [==Romani==], but the subdivisions are allowed nested lines in translations tables." In fact, if you read the discussion about Romani, you'll note that I was under the impression that Arabic was already handled that way! If we adopt such an approach, then merging North and South Levantine seems unnecessary, especially if they have such differences as Wikitiki describes ("the Lebanese dialect uses a lot of French borrowings and the Israeli dialects use a lot of Hebrew borrowings"). That's because I think it's easier (especially with Conrad's trans-adder) to add, and also to look at as a reader, separate lines for apc and ajp, vs one line with several entries each with its own qualifier. Whereas, if we want to grant all code-having Arabic dialects their own L2s, then it would make more sense to merge apc and ajp, since I think it's easier to add {{context}} tags to sense-lines than it is to create two separate L2 sections with almost identical content. So, I think it would be best if we developed an idea of what our general policy on Arabic dialects should be before acting here... (No matter what our general policy is, I think it makes sense to abolish sem-syr, converting each of its entries into whichever of apc vs ajp it happens to be.) - -sche (discuss) 22:54, 21 February 2014 (UTC)
What you may be overlooking is that French borrowings in Lebanese do not carry over to Syrian, and Hebrew borrowings in Israel do not generally carry over to the Palestinian territories, let alone to Jordan. Also, North Levantine is spoken in the North of Israel and uses the same Hebrew borrowings that are used in the South of Israel in South Levantine. Merging all dialects with MSA will be a big process, mostly due to our large number of Egyptian Arabic entries. Merging Levantine together is quick and easy and not much is lost in doing so even if we later decide to merge it with MSA. --WikiTiki89 23:07, 21 February 2014 (UTC)
I think it's possible and advisable to merge ALL Arabic varieties into Arabic, using e. g. {{context|Egypt|Sudan|lang=ar}} labels and regional categories, such as Category:Lebanese Arabic. Even infrequent inflection tables could have regional context labels. As I mentioned, Arabic dictionaries, which include dialectal forms just label them with Morocco, Syria, etc. (my preference and we have a precedence in Hans Wehr) or Levantine, Gulf. Apart from named dialects there are differences related to specific countries. I'd prefer labels "Lebanon", "Syria" to "North Levantine" or "South Levantine", even though there are differences within countries across dialects - we can combine labels such as {{context|Hejazi|Saudi|lang=ar}}. The majority of words are identical for all dialects, despite differences in pronunciation, there's no need to duplicate information. Words that are different in dialects are quite common but their percentage is small and many words are shared by various dialects, they are often considered more colloquial, not dialectal, especially numerous borrowings, frowned at by Arabic purists but still used quite often. In any case, keeping separate dialect dictionaries is impractical, any dialect also includes the majority of Arabic words. Besides, we have kept Albanian as one language without splitting into Tosk and Ghek, English is not split into American, British, etc. merged Serbo-Croatian varieties and I think we can also merge Norwegian and Chinese. (Merging Arabic varieties is a much simpler task than merging Chinese varieties and makes even more sense). --Anatoli (обсудить/вклад) 07:08, 27 February 2014 (UTC)
The differences between Arabic dialects are similar to the differences between German dialects such as Swiss German. Swiss German is considered a dialect but it is different enough that it is not mutually intelligible with Standard German. The difference between Arabic and German, however, is that in Arabic, the spelling of individual words is largely identical across dialects, which makes it practical to have them merged. But that does not the only factor to consider. If we merge all of Arabic together, when providing usage examples, we would have to label each usage to specify which dialect it uses. The other solution would be to only use MSA for usage examples, but this would further de-emphasize dialects and make it difficult for people trying to learn them. There are already very few resources online (and even offline) for Arabic dialects (with the possible exception of Egyptian). I think that it would be beneficial to treat the dialects separately from MSA, even if we don't plan on duplicating all of the content. I only plan to add the most distinctive Levantine words as entries, I don't plan on duplicating all of the Arabic content we already have. Finally, as I've already said before, the discussion of merging all of Arabic together is entirely separate from the discussion here. The discussion here is something we can do right now, without a lot of debate and without a vote. Merging all of Arabic together is a long term project. If you want to start a discussion about it, do it at the Beer Parlour, but it does not prevent us from merging Levantine in the meantime. --WikiTiki89 07:26, 27 February 2014 (UTC)
I know it's a diversion from your original topic but if the idea of merging dialects were met positively, then your request to merge two forms of Levantine would be solved as well. I don't think the problem with the lack of emphasis and resources for dialects will be solved any time soon, including Egyptian Arabic (which is slightly more available than others) and having them under one header is not a problem for adding regional user examples, if editors are aware that we only have "Arabic". I'll consider a new discussion in BP when I'm back home. I agree it would require a vote and a more thorough analysis. --Anatoli (обсудить/вклад) 07:45, 27 February 2014 (UTC)
I understand that if the idea of merging all of the dialects were met positively that would solve this problem as well, but that would take longer. And I don't expect that the lack of emphasis or resources would be solved any time soon, but I'd rather that Wiktionary be part of the solution and not part of the problem. As for usage examples, how would a reader know which dialect is being used? Should usage examples have context labels as well? --WikiTiki89 07:56, 27 February 2014 (UTC)
Not labels but a dialect name in brackets. I understand why most dialects are not emphasised by Arabs and why we shouldn't do it either or should promote written dialectal forms, only some of which are attestable. There's no definite right and wrong in spelling, pronunciation and transliteration and by definition, no standard. That's why Arabs mix standard with dialect spellings when writing in dialects. There is a so-called "spoken MSA" or "educated colloquial Arabic" (there are textbooks available, I have two books) where some common dialectal forms are mixed with MSA to produce a new variety. It obviously differs a bit regionally. --Anatoli (обсудить/вклад) 09:04, 27 February 2014 (UTC)
But spelling is not everything, there is also morphology, syntax, agreement, vocabulary choice and other aspects of grammar that are evident even when the spellings are the same as MSA. For example, بَدِّي أَشْرَب قَهْوَة and بَحِبّ بُيُوت صُغَار, in which every word is spelled the same as in MSA, yet the sentences still differ from the MSA أُرِيدُ أَنْ أَشْرَبَ قَهْوَةً and أُحِبُّ بُيُوتًا صَغِيرَةً. The question you still haven't answered is: What is wrong with merging Levantine together right now, even if we will later merge all Arabic dialects? --WikiTiki89 19:45, 27 February 2014 (UTC)
The known differences you listed are comparable with Serbo-Croatian and Albanian variations, some regional English slang. It would make sense to keep dialectal phrasebooks as separate subsections of the Arabic phrasebook but it's a word dictionary. Do you possess Hans Wehr dictionary? It has a lot of dialectal words/regionalisms but examples are only provided for MSA. As I said before, usexes can be used on the MSA entries and specific dialectal words can be labeled/categorised accordingly. There's nothing wrong with merging Levantine now, I have already expressed my support for this. --Anatoli (обсудить/вклад) 23:54, 27 February 2014 (UTC)
Ok, I see your point. No, I don't have a Hans Wehr, but I am thinking about getting one (since I am not a professional translator or anything remotely close to one, buying expensive dictionaries is not something I do for every language I happen to be interested in; in fact the only physical dictionary at all that I personally own is the Even-Shoshan Dictionary of Hebrew; however, due the scarcity of online Arabic dictionaries, and the inconvenience of a PDF dictionary, I am considering buying a Hans Wehr). And thanks for your answer. I'm looking forward to the official merging-all-of-Arabic debate. --WikiTiki89 02:17, 28 February 2014 (UTC)
(replying to Wikitiki's comment of 23:07, 21 February 2014): That's a good point. I suppose any linguistically sound treatment of Arabic dialects is going to divide them — whether into separate code-having L2s, or simply separate {{qualifier}}-tagged varieties — along lines too different from SIL's for it to be worth retaining ajp and apc no matter what we do. Alright, merge all three codes. (I note for posterity that ajp and apc are only used by a dozen entries each, anyway, and sem-syr is not used at all in the main namespace.)
Now, to address the question of whether the unified "Levantine" should use one of the existing codes or get an exceptional code... precedent, both here (see gcf) and at the ISO (see e.g. their merge of tlw into weo), seems to be to use one of the existing codes. - -sche (discuss) 03:03, 28 February 2014 (UTC)

Since Wikitiki89 requested my comment, I would say let's remove national-based categorization of dialects and let's separate them by the ISO 639-3 categorization of dialects. It categorizes two Levantine dialects, the northern and the southern. They are close, but separate enough. They are not one and they are not comparable to Boston-New York accents. If you listened to a speaker from Gaza, you can tell the difference in many words and somewhat in grammar from what would a speaker from Lebanon would.

A separate note is that Arabic dialects are hardly mutually intelligible, even when their spoken range is geographically close. They only become intelligible under certain circumstances: 2 people are literate in Literary Arabic which affects both dialects; the same 2 people have accustomed themselves on both dialects by listening to many songs and conversations in the other dialect; when the 2 people try to use a simplified straightforward version of their dialects. --Mahmudmasri (talk) 12:35, 3 March 2014 (UTC)

Subdialects of Levantine
@Mahmudmasri: The reason Gazan Arabic is so different from Lebanese is because, as you can see on the map at right, it is at the very bottom of the continuum. What the map calls "Palestinian" is much closer to Lebanese than Gazan (what the map calls "Outer southern") is. If anything, it should be the "Outer southern" that should be broken off as a separate language, but even that would be a longshot. Anyway, I agree that the only reason many of the dialects are mutually intelligible is because of knowledge of MSA or mutual knowledge of the other's dialect. However, all variants of Levantine Arabic are mutually intelligible with each other. --WikiTiki89 16:40, 3 March 2014 (UTC)
I'm not sure to what extent the map is precise, however the dialect spoken by urban west Jordanians is not close to the Lebanese as that of northern Israel and West Bank to the Lebanese, even though in both cases the variants are spoken in a very close region. I'm also not sure whether the Gaza speech would be very much mutually intelligible with the Aleppo speech as much as you assume. --Mahmudmasri (talk) 02:10, 4 March 2014 (UTC)
@Mahmudmasri: You have valid points about differences in dialects. It doesn't mean all Arabic dialects can't have the same L2 header. Lack of templates makes harder to add dialectal contexts, e.g. شو (šū) may get an entry:


# {{context|interrogative|Palestine|lang=ar}} [[what]]?
...and be categorised under Category:Levantine Arabic. Arabic dictionaries, which include dialectal words, have a way of doing it I don't see why we cannot do it as well. Please look at Chinese discussion: Wiktionary:Beer_parlour/2014/March#A_new_format_for_Chinese_entries_.28multisyllables.29, it may give you some ideas. --Anatoli (обсудить/вклад) 03:47, 14 March 2014 (UTC)
No, please, don't just sum up all dialects under ==Arabic==. You'd better have a section ==[North/South] Levantine Arabic==. The /ʃuː/ is North Levantine, not south, but the Palestinian dialects are not one. The Gaza speech is also considered Palestinian, but they say /ʔeːʃ/. --Mahmudmasri (talk) 18:08, 16 March 2014 (UTC)
To clarify, and I know this from asking people from various parts of the Levant, North Levantine uses only /ʃuː/, while South Levantine uses both /ʃuː/ and /(ʔ)eːʃ/ interchangeably. --WikiTiki89 18:44, 16 March 2014 (UTC)
Obviously, because there are no clear boundaries where the dialect area ends. However, I never heard someone from Gaza normally saying /ʃuː/, unless he consciously tries to use the word. --Mahmudmasri (talk) 13:43, 17 March 2014 (UTC)
Maybe movies are not the best source, but I've watched a Gazan movie a long time ago (before I knew much about Arabic) and I remember hearing /ʃuː/. And just recently I watched a Palestinian movie where the same characters used both /ʃuː/ and /(ʔ)eːʃ/ interchangeably. Additionally, I have asked around Palestinians and Jordanians seem to say that they use whichever one sounds better in the sentence. --WikiTiki89 16:11, 17 March 2014 (UTC)

Rename Wangaaybuwan-Ngiyambaa → Ngiyambaa (wyb)[edit]

"Ngiyambaa" is far more common than "Wangaaybuwan-Ngiyambaa". "Wangaaybuwan" is one of the two peoples that speak the language, and hence the name of the dialect used by that people. The other Ngiyambaa-speaking people, whom the current name neglects, are the Wayilwan, who speak the (you guessed it) Wayilwan dialect. Renaming the language entails moving a few categories and updating a few pages. - -sche (discuss) 04:32, 26 February 2014 (UTC)

Renamed. Categories and entries still need to be moved. - -sche (discuss) 02:46, 22 January 2015 (UTC)
I think I've updated all effected entries and categories. - -sche (discuss) 17:48, 22 January 2015 (UTC)

Baramulla District and many like it[edit]

A while ago, a user created a large number of entries like Baramulla District using this IP and this IP. Much of the time, it seems to me that the actual lemma is "Baramulla", and "Baramulla district" or, with honorific capitalization, "Baramulla District" is merely a SOPpy descriptor like "North-Rhine-Westphalia State". That is, I think many of the entries should be moved from Baramulla District, etc to Baramulla, etc. (Compare Odessa’s "oblast" sense.) - -sche (discuss) 22:16, 27 February 2014 (UTC)

Support. —Mr. Granger (talkcontribs) 19:42, 3 March 2014 (UTC)
I've started moving entries. - -sche (discuss) 22:05, 16 March 2014 (UTC)

March 2014[edit]


Hi... perhaps it is not of my concern, but I do believe Appendix:Proto-Indo-European/leb- and Appendix:Proto-Indo-European/leh₂b- should be merged, or, rather, that the former should be supplanted by the later. Would someone verify this for me? Perhaps provide reasons for not doing so? I'm no one to say, but I understand that *leb- is an alternate form of *leh₂b-; the descendants of the former are among the descendants of the later, at least, and I'd expect leb- rather the lab- as Italic reflex if the PIE should be *leb-... I might be wrong... Any way, thank you for reading this... 02:02, 5 March 2014 (UTC)

Category:Translation requests (Norwegian)[edit]

We currently treat Norwegian Nynorsk and Norwegian Bokmål as separate languages, and yet this category has many more entries than Category:Translation requests (Norwegian Bokmål) and Category "Translation requests (Norwegian Nynorsk) combined. I understand that there may be dialectal forms that belong to neither, but it seems obvious to me that most of these were added with Bokmål in mind, and pretty much all of the rest with Nynorsk intended. After all, requesting a Norwegian translation won't get you a dialectal form unless there's some way to ask for it specifically.

The first part should be to change all the current requests to Bokmål and/or Nynorsk and try to find some way to discourage or prevent people from adding the requests. Then we can talk about deleting or deprecating the plain Norwegian category.

I would think the most painless method would be to change the code for {{ttreq}} or whatever it calls to intercept the language code "no" and replace it with "nb", or to create two categories, one for "nb" and one for "nn". This would have to be at a higher level than the language lookup, because there are are some other templates that we still no doubt want to allow to have "no"-based output.

This is bound to be a bit messy and/or controversial, so I'd like to encourage other suggestions. Chuck Entz (talk) 22:58, 9 March 2014 (UTC)

Oppose. "Norwegian" is also treated as a language; its code {{no}} is ever-present in Module:languages, and many entries use ==Norwegian== headers. I have thought for a long time that we should un-split Nynorsk and Bokmal, the opposite of what you suggest. (Alternatively, we could split US and Indian English, which are about as distinct, and put an end to the occasional bickering about whether words should end in '-our' or '-or', etc.) - -sche (discuss) 00:19, 10 March 2014 (UTC)
I think that the two language should be merged, mainly because the two forms are primarily different in writing and not actual pronunciation or vocabulary. There are some vocabulary differences, but of course plenty of people will use vocabulary present in neither standard. And I'm pretty sure that a Norwegian will pronounce a word the same in their own speech whether they write it with Bokmål or Nynorsk spelling. —CodeCat 00:36, 10 March 2014 (UTC)
The fact that "no" is not allowed as a language code, makes it difficult to use accelerated method to add translations to {{trreq|no}} or {{trreq|Norwegian}}. I support merging Nynorsk and Bokmål. We could use {{cx|Nynorsk|lang=no}}/{{cx|Bokmål|lang=no}} + subcategories of Norwegian. --Anatoli (обсудить/вклад) 02:28, 12 March 2014 (UTC)
I have removed the code that blocked the addition of 'no' translations. They should never have been blocked, even by people who want to retain Nynorsk and Bokmål as separate languages, because we as a descriptivist dictionary allow dialectal Norwegian words as translations (and these words, since they are not Nynorsk nor Bokmål, must use 'no' rather than 'nb' or 'nn'). - -sche (discuss) 01:07, 13 March 2014 (UTC)
See Wiktionary:Beer parlour/2014/March#Stop_treating_Nynorsk_and_Bokmal_as_languages_separate_from_Norwegian. - -sche (discuss) 03:57, 12 March 2014 (UTC)
Closed with no action taken one way or the other. A vote on the subject showed that there was no consensus regarding whether to have "Norwegian" or "Bokmal"+"Nynorsk", so we still have all three. - -sche (discuss) 02:48, 22 January 2015 (UTC)

Rename Old East Slavic to Old Russian (orv)[edit]

The term "Old East Slavic" must have been created to avoid offending Ukrainians and Belarusians and to please nationalists who use "Old Ukrainian" and "Old Belarusian", since "Old Russian" may imply to some that Belarusian/Ukrainian languages are derivations of Russian. However, "Old East Slavic" (Russian: древнеру́сский язы́к (drevnerússkij jazýk)) translates into Belarusian as старажытнару́ская мо́ва (staražytnarúskaja móva) and into Ukrainian as давньору́ська мо́ва (davnʹorúsʹka móva) (alternative names also exist, including "Old Ukrainian"). All three terms are literally translated as "Old/Ancient Russian/Rusian", not "Old East Slavic". Note that in Ukrainian ру́ський (rúsʹkyj) refers more specifically to Rus rather than modern Russia. (Unlike Russian and Belarusian, the Ukrainian term росі́йський (rosíjsʹkyj) means "Russian" both referring to ethnicity and the country. Cf. Russian ру́сский (rússkij) / росси́йский (rossíjskij) and Belarusian ру́скі (rúski) / расі́йскі (rasíjski)). Despite the current tensions between Russia and Ukraine, linguistically it makes much more sense to rename "Old East Slavic" to "Old Russian". Call me biased, whatever, but respectable East Slavic linguists all use "Old Russian", it's of the Ancient Rus, not modern Russia, the centre of which was in Kiev, modern Ukraine. :) --Anatoli (обсудить/вклад) 02:47, 12 March 2014 (UTC)

I don't think the names that modern speakers use should really count. They're bound to have some kind of national pride in them, like discussions on the Wikipedia article show. (And I'm hoping to avoid a straw man, but by the same logic we'd call Dutch "Netherlandish", German "Dutch", Greek "Hellenic", Armenian "Hayeric", Hittite "Neshite", and so on...) I think we should focus purely on what modern English-language scholarship calls the language. —CodeCat 03:23, 12 March 2014 (UTC)
Re: English language usage. Ngram, Ngram 2 can't even find "Old East Slavic (language)", not sure if I interpret this correctly or if it is possible to check the English usage via Google.
Being half-Russian, half-Ukrainian, I take pride in belonging to both but pride can take various ways. E.g. ру́ський (rúsʹkyj) is sometimes translated by Ukrainians as давньоукраї́нський (davnʹoukrajínsʹkyj, Old Ukrainian) and some Ukrainian nationalists claim they have nothing to do with Russian but others take pride in being the cradle of all Slavs. We all know the Serbo-Croatian language story and Israeli-Palestinian conflict doesn't make Hebrew and Arabic belong to different language families. Modern Ukrainian, Russian, Belarusian are distinct languages but they are all derived from one, so your comparison is not valid.
In any case, Belarusians (educated), considering the name of the language, are not even trying to deny that Belarusian is derived from Old Russian (=Rusian, Old East Slavic), the language of Rus, in Ukrainian, the term ру́ська мо́ва (rúsʹka móva) is also used, without "Old", since ру́ський (rúsʹkyj) has this meaning ((modern) Russian language is called росі́йська мо́ва (rosíjsʹka móva) in Ukrainian). Ukrainians also know that Украї́на (Ukrajína) is quite a new term, although there are some ridiculous claims about so-called "Ukr" tribes, derived directly from Proto-Slavic, bypassing Old Russian stage. I wonder what discussion you're referring to?
BTW, I disapprove the policy of Russian government and respect the right of Ukrainians to decide their fate but we are talking about language names and linguistics here. Bad timing for this discussion, considering the Ukrainian and Crimean crisis. --Anatoli (обсудить/вклад) 04:22, 12 March 2014 (UTC)
We should probably invite our Ukrainian editors to this discussion to get a broader picture. --Anatoli (обсудить/вклад) 04:49, 12 March 2014 (UTC)
I think this should be decided solely by the most commonly used name in English. Thus, I tentatively support "Old Russian" based on the Ngrams above, and based on a hunch that English speakers are less likely to have to look up the language if it is called "Old Russian" than if it is called "Old East Slavic". However, there needs to be a more thorough investigation into the evidence, since Ngrams are often inaccurate and/or skewed by unexpected factors. --WikiTiki89 04:55, 12 March 2014 (UTC)
Agreed but Google books count of "Old Russian language" is also significantly larger than "Old East Slavic language" (even though "Old Russian language" may not always have the same sense as "древнерусский язык"). I'm happy if someone else can analyse it better using Google or other sources. --Anatoli (обсудить/вклад) 05:02, 12 March 2014 (UTC)
Re: solely by the most commonly used name in English. We should also take into consideration the literal names in the affected languages. I think "Old East Slavic" is a result of some kind of political correctness or fairness, ignoring the fact that Ukrainian and Belarusian don't use this fairness in the name, also not note French "vieux russe", Estonian "vanavene keel", Dutch "Oudrussisch" and many Slavic names. The rest of names must have followed English Wikipedia in their namings. --Anatoli (обсудить/вклад) 05:21, 12 March 2014 (UTC)
I disagree, whatever the origin of its usage, if "Old East Slavic" became were shown to be used more commonly in English, then that is the name we should use. The only other factors we should consider are the ambiguity of the name (for example, if "That Language There" were the most commonly used term for some language, we probably still shouldn't use it), or possibly some other minor issues that I can't think of at the moment. --WikiTiki89 05:30, 12 March 2014 (UTC)
I meant it seems it was coined out of some considerations but I agree that if it were more common we should use it. I can't think of another example but in Japanese ハングル (Hanguru-go) "Hangeul language" was specifically coined, out of political correctness, to avoid giving preferences to either Korea or their languages (North and South Koreas have different names in East Asian languages, see 韓国 and 朝鮮). --Anatoli (обсудить/вклад) 05:38, 12 March 2014 (UTC)
If you agree that if it were more common then we should use it, then isn't that the same thing as only relying on which is more common? --WikiTiki89 05:43, 12 March 2014 (UTC)
--Anatoli (обсудить/вклад) 05:25, 12 March 2014 (UTC)@Mzajac:, @Alexdubr:, anyone else is active?
It is not easy to get a sense of which name is most common in English. Chaff like "an old Russian car" skews counts of "Old East Slavic" vs "Old Russian", but if "language" is added, the number of hits drops so low that it is statistically insignificant / unreliable. However, based on manual review of a search with "in", I think "Old Russian" is the more common of the two names. - -sche (discuss) 06:25, 12 March 2014 (UTC)
I support the rename to Old Russian per the following Google Scholar Data, showing that "Old Russian" is more than 10 times as common as all other names I could think of, combined. —Aɴɢʀ (talk) 19:20, 12 March 2014 (UTC)

“Old Russian” reflects systemic prejudices that go back to times of the empires, when Encyclopedia Britannica defined wrote about White Russians and Little Russians, some of whom were Ruthenians. These prejudices were still felt in academics and journalism when the Soviet Union broke up, and are only going away now. I don’t think Wiktionary is part of an establishment that tries to wilfully reinforces these backward practices.

Furthermore, the moment when the Russian regime is exploiting such ideas in its anti-Ukrainian propaganda is the shittiest possible time to start this discussion. Michael Z. 2014-03-12 19:18 z

I feel kind of the same about it. I can't motivate the choice with widespread usage, but I feel that "Old East Slavic" just is a better, more descriptive name for the language. So I oppose. —CodeCat 19:42, 12 March 2014 (UTC)
@Mzajac: I agree about bad timing and with the criticism of the Russian regime and I'm very sad about the latest events - Putin, in a short period, has created a situation, which was unimaginable for hundred years - Russians fighting Ukrainians. I wish we didn't mix politics in here, though. The political split of Yugoslavia caused the artificial language split but we all know that Serbo-Croatian is one language, despite the tensions. Jewish and Arabic are still semitic languages and Ukrainian and Russian are still derived from the same source (after a big injection of Old Church Slavonic into Russian and Polish injection into Ukrainian). I'm not stating any Russian supremacy or support any name-calling. Regarding the names, I disagree that "White Russians" and "Little Russians" were a result of prejudice, just as "Белару́сь" (Бе́лая Русь) and "Малоро́ссия" are just historical words, names among others like "Great Rus", "Red Rus", "Black Rus", "Carpathian Rus". Nikolay Gogol, native of modern Ukraine, also used "Малороссия" when referring to his homeland. The "offensive" meaning (if "Малоро́ссия" ("Little Rus(sia)" sounds offensive to Ukrainians) was acquired mistakenly in the modern times. In any case, Русь (Rusĭ) originated on the territory of modern Ukraine by people who lived there and this is where all East Slavs originate from. I don't see or Ukrainians don't see anything offensive in terms "давньору́ська мо́ва" and "ру́ська мо́ва" when referring to Old East Slavic language but I won't insist on continuing this discussion, if it hurts someone's feelings. --Anatoli (обсудить/вклад) 02:10, 14 March 2014 (UTC)
Guys, call it Old Bulgarian and that's it. Though modern Bulgarian belongs to the southern branch, the early Bulgarian and Russian texts do show their being one language. Alexdubr (talk) 14:31, 17 March 2014 (UTC)
You are confusing two different languages. Old Bulgarian, which we call Old Church Slavonic, was also a South Slavic language, but it was used even in Russia/Ukraine/etc. as the main written and liturgical language. The main spoken language, however was Old Russian or Old East Slavic, which was an East Slavic language and the ancestor of modern Russian/Ukrainian/etc. --WikiTiki89 16:14, 17 March 2014 (UTC)

Merging cbk-zam (Zamboanga Chavacano) into cbk (Chavacano)[edit]

Pretty much every source I could find referred to Zamboangueño et al. as varieties or dialects, not languages. Two of them in particular make it very clear:

“The result of the study showed that while there are observable differences in certain language features beween and among the four variants, they are nonetheless, mutually intelligible with each other even among native speakers who do not have any special language training. Thus, for the purpose of this pilot study, al four variants were identified as dialects of PCS.” Sister María Isabelita O. Riego de Dios, A Pilot Study on the Dialects of Philippine Creole Spanish

“The two variants of PCS share enough distinctive differences from regular Spanish or regular Philippine usage that they must be considered historicaly related dialects of the same language” Charles O. Frake, Lexical Origins and Semantic Structure in Philippine Creole Spanish

Ungoliant (falai) 07:19, 15 March 2014 (UTC)

Meänkieli (fit) and Kven (fkv) into Finnish (fi)[edit]

Finnish dialects

I think that linguists consider these to be dialects of Finnish, so that would make these pluricentric standards of a single language. I don't know if keeping them separate would hold any value? —CodeCat 14:05, 15 March 2014 (UTC)

Let's ping our active Finnish speakers to see if they have input: User:Hekaheka and User:Makaokalani. 23:16, 23 March 2014 (UTC) (updated - -sche (discuss) 06:09, 6 April 2014 (UTC))
The impression I get from the example at w:Meänkieli is that the differences are very minor, no more than there might be between Croatian and Serbian. I notice systematic loss of -d- and Finnish -ts- corresponds to -tt- in Meänkieli. They definitely look mutually intelligible. Kven looks a little more different, but it might also just be the spelling; I don't know how hard it would be to the average Finnish speaker. —CodeCat 23:26, 23 March 2014 (UTC)
I know maybe a dozen words of Finnish, so I can't judge for myself, but the impression I get from the Wikipedia articles is that there's an equal or greater range of variation between dialects in Finland as there is with these dialects- if these dialects were on the other side of the Finnish border, they would probably be considered just part of the normal dialectal variation (I'm sure there are some differences due to their isolation from the influence of standard Finnish, as well). They have special status because they're in Sweden and Norway surrounded by Swedish and Norwegian. Chuck Entz (talk) 23:53, 23 March 2014 (UTC)
Finnish wasn't even a single language to begin with originally. There's several dialect groups that form a continuum, but it's not easy to draw clear lines. Savonian (eastern) dialects for example might well be closer to Karelian (considered a separate language) than they are to western Finnish. —CodeCat 00:10, 24 March 2014 (UTC)
My impression is the same as Chuck's, that these could be merged. By my (quick) count, we have 11 Meänkieli entries and 14 English entries with Meänkieli translations, and 19 Kven entries and 8 entries with Kven translations. - -sche (discuss) 02:45, 24 March 2014 (UTC)
For more information see w:Finnish dialects and also w:Peräpohjola dialects. The map to the right may also help. —CodeCat 03:33, 24 March 2014 (UTC)
Blue indicates areas where Finnish is spoken by the majority, and green indictes minority. Meänkieli and Kven are considered Finnish on this map

I somehow missed this discussion when it was active, but better later than never. I have the following comments:

  • The map is outdated. There's practically no Finnish-speaking population left in the areas which were annexed by the Soviet Union during and after the WWII. The map on the right is more up-to-date.
  • There's some Ingrian population left in the St. Petersburg area, but their number and share of population (less than 0,5‰ in Leningrad oblast) is drastically reduced due to 1) inflow of Russians to St. Petersburg, 2) Stalin's terror in the 1930's and 3) emigration to Finland between 1990 and 2011.
  • I'm not sure of Kven-speakers, but the speakers of Meänkieli tend to be quite strong in their opinion that they are not Finnish-speakers. It is probably true that if the border were in another place, Meänkieli would be considered a Finnish dialect. But then again, it would hardly be the same language as it is today - it would have preserved less archaic features and there would be much less Swedish influence in it. If ISO regards it a language, how could we be wiser?
  • Meänkieli is an official minority language in Sweden, and is regarded as distinct from Finnish which also has a (separate) minority language status there.
  • "Finnish wasn't even a single language to begin with originally." -- Show me one that was!

--Hekaheka (talk) 12:27, 25 January 2015 (UTC)


"Having no beard or mustache" and "Having had facial hair completely removed." are the same thing. Renard Migrant (talk) 13:34, 29 March 2014 (UTC)

It's not obvious that they are.
I don't even know what "completely" and "facial hair" are supposed to mean when used together in this context. Does "facial hair" as people use the word normally include the follicle, the portion below the skin? If it does then "complete" removal would at least require a depilatory.
Can I be clean-shaven if I don't have a beard or mustache, but haven't shaven for three days? What if I did a bad job shaving? This seems like a case for sharpening the definitions by RfV's. Keep, cite and revise, or RfV. DCDuring TALK 13:51, 29 March 2014 (UTC)
most dictionaries seem to have only one sense, if they have the term at all, but AHD has two defs:
  1. Having the beard or hair shaved off.
  2. Having recently shaved.
These each seem better than our corresponding definitions. DCDuring TALK 13:55, 29 March 2014 (UTC)


Templates Template:grc-conj-perfect-σ and Template:grc-conj-perfect-dental are identical. ObsequiousNewt (talk) 16:41, 29 March 2014 (UTC)

Northern Uto-Aztecan language module additions[edit]

I've spent some time over the years with various California Indian languages, though I'm not an expert by any means. I've already added a good bit of material on Cahuilla, but there are a few additions I would like to make to the modules to make it easier to do etymologies as I broaden my focus a bit.

First of all, we don't show any divisions within Uto-Aztecan except Nahuan, which includes all the Nahuatl lects. Most scholars would divide Uto-Aztecan into Northern Uto-Aztecan and Southern Uto-Aztecan, with Nahuan included in the latter. The division seems to me, though, to be more of a consensus hunch: it's hard to say whether it represents areal/diffusional spread of features or the result of a split into separate proto-languages. I have no need to refer to Northern or Southern Uto-Aztecan, so I'm not asking to create either. It just happens, though, that all the languages I know much about are in the northern group. Here's my understanding of the internal structure of the group, with language codes in bold, and families, proto-languages and synonyms that I'd like to add to the modules in italics:

  1. hop Hopi, a.k.a Moqui (an obsolete term in older references)
  2. tub Tübatulabal
  3. Numic languages (descendants of Proto-Numic):
    1. Central Numic:
      1. com Comanche
      2. par Panamint, a.k.a Panamint Shoshone, Timbisha, Tümpisha, and Koso
      3. shh Shoshone, a.k.a. Shoshoni. Dialects:
        1. Western Shoshoni
        2. Gosiute
        3. Northern Shoshoni
        4. Eastern Shoshoni
    2. Southern Numic:
      1. kaw Kawaiisu
      2. ute Ute, a.k.a Colorado River Numic. Dialects:
        1. Chemehuevi
        2. Southern Paiute
        3. Ute
    3. Western Numic:
      1. mnr Mono (California), a.k.a Mono (California), Mono (United States of America), Mono, Monachi, Monache, Owens Valley Paiute. Dialects:
        1. Western Mono ("Mono" and its variations originally applied only to this dialect, but were extended to the whole language).
        2. Owens Valley Paiute, a.k.a Eastern Mono
      2. pao Northern Paiute, a.k.a Numu, Paviotso
  4. Takic languages (descendants of Proto-Takic):
    1. ser Serrano. Dialects:
      1. Serrano
      2. Kitanemuk
      3. Vanyume (maybe)
    2. xgf Gabrielino-Fernandeño, a.k.a. Tongva. Dialects:
      1. Gabrielino
      2. Fernandeño
    3. Cupan languages (descended from Proto-Cupan)
      1. chl Cahuilla, a.k.a Iviatim. Dialects:
        1. Mountain Cahuilla
        2. Desert Cahuilla
        3. Wanakik Cahuilla
      2. cup Cupeño
      3. lui Luiseño. Dialects:
        1. Luiseño
        2. Juaneño

In the Numic languages, "Ute", "Paiute" and "Shoshone" are occasionally randomly applied all over the place in older sources. There also seems to be some disagreement between Wikipedia articles about whether "Koso" refers to a group of Panamint speakers or to Northern Paiute speakers, and Owens Valley was home to not just the Eastern Mono speakers of what is known as "Owens Valley Paiute", but also to Northern Paiute speakers.

Then there's the matter of Tataviam, an extinct language represented by at least one word list, with another word list for Alliklik, which may be the same language- or not. Depending on which source you read, it's:

  1. A Takic language
  2. An independent branch of Uto-Aztecan
  3. A Chumashan language strongly influenced by its Takic neighbors

The modern-day descendents of the Tataviam have merged with the descendents of the Fernandeño into one group for purposes of recognition by the US government, so I fully expect to see references to Fernandeño as Tataviam any day now. Chuck Entz (talk) 06:16, 30 March 2014 (UTC)

I have incorporated into the modules all of the synonyms/aliases you mention except Iviatam, which seems to only be an ethnonym. "Koso" is identified with Panamint in the references I could find, so I've added it as an alias of Panamint (not of Northern Paiute). Given how freely the ISO gives out codes, I'm wary of creating exceptional codes for things known only from wordlists that the ISO hasn't even granted a code to. (I'm not sure if you were suggesting that Tataviam be given a code or not.)
I'd suggest perhaps "azc-num" as a family code for the Numic languages, "azc-tak" for Takic and "azc-cup" for Cupan. - -sche (discuss) 08:34, 6 April 2014 (UTC)
Thanks! My comments about Tataviam were more of an illustration of/rant about how murky things can get than a serious request to do anything. It wouldn't be that hard to track down the word lists, but coming up with way to synchronize the different sources would be a real challenge (I wish I could go back in time and slap C.H. Merriam for refusing to learn proper phonetic transcription...).
I think your suggestions for Numic, Takic and Cupan are fine. There are articles in the literature with reconstructions for the proto-lnguages for each, so I'll eventually include them in etymologies, too.
My main reason for this topic was to be able to create entries for Chemehuevi (I still have to work out a usable orthography, though), but I figured it would be good to deal with the other stuff while I was at it. I have some material on the Ipai dialect of Diegueño and on Havasupai, so I'll have to do something like this for the Yuman languages later. Chuck Entz (talk) 00:00, 7 April 2014 (UTC)
It looks like everyone forgot about this thread. Well, I've added Numic, Takic and Cupan to Module:families/data, and added codes for their proto-languages to Module:languages/datax. I've even added *nɨmɨ (person) and *taka (person) (feel free to move them if you feel a different orthography is preferable). @Chuck Entz: Is there anything else that remains to be done (besides adding entries in these languages)? - -sche (discuss) 22:42, 23 July 2014 (UTC)

Template:-er to Template:en-er[edit]

This is an English-only template, so the name should reflect that. —CodeCat 15:24, 30 March 2014 (UTC)

Its main advantage over {{suffix|foo|er|lang=en}} seems to be its brevity. I see little point in having it if it is renamed (or, TBH, even if it's not). It might be better to expand it to allow a lang= paramater (either adding lang=en to all current uses, or setting it to default to lang=en if no lang= is set). It could then be used for German and other languages. - -sche (discuss) 06:04, 6 April 2014 (UTC)

Template:rank to Template:en-rank[edit]

Same as above. —CodeCat 17:18, 30 March 2014 (UTC)

April 2014[edit]

Komi language[edit]

Merge Komi-Zyrian (kpv), Komi-Permyak (koi), Komi-Yodzyak (no code) with Komi (kv). Komi-Zyrian is dominating over others. Currently, they all use the same alphabet but there were differences in the past. There's very little information on the grammar differences but they are mostly considered dialects, not separate languages. Merging kv and kpv should be straightforward, Zyrian is the language of Komi Republic.-Anatoli (обсудить/вклад) 10:39, 6 April 2014 (UTC)

Actually, it has been planned as far as Komi-Zyrian and Komi-Permyak are concerned, see WT:LANGTREAT: "kv and kpv refer to the same lect; one will eventually be deleted.". Apparently, there are differences with Komi-Permyak but those can be labeled as "Permyak", similar Serbo-Croatian or Albanian varieties. --Anatoli (обсудить/вклад) 01:54, 7 April 2014 (UTC)
Added: Wiktionary:Komi transliteration, Module:kv-translit, which handles both Zyrian and Permyak. --Anatoli (обсудить/вклад) 02:22, 7 April 2014 (UTC)
Komi-Permyak has a distinct written tradition and should not and cannot be merged. Your statement that Komi-Zyrian is dominating shows your pro-Russian and anti-minority POV which should never be a basis for consensus on this wiki. Komi-Zyrian can be handled under {{kv}}, yes. -- Liliana 12:34, 7 April 2014 (UTC)
Do you have paranoia or something? I'm not Putin and not suppressing any minorities. Komi-Zyrian is a language of majority of Komi people in Komi Republic, has a much larger number of speakers and much more materials written in this variety of Komi. Komi-Permyak is used by a minority in Perm Krai and has only 63,000 speakers. By all means, I'm not forcing anyone to merge, this is only a suggestion. They are mutually comprehensible and each of them has dialects. It's possible to merge Komi varieties like it's possible to have one L2 header for Albanian, Norwegian or Serbo-Croatian, marking varieties accordingly: тӧлысь (Zyryan)/тӧлісь (Permyak), выль (Zyryan)/виль (Permyak). --Anatoli (обсудить/вклад) 12:58, 7 April 2014 (UTC)
That was completely rediculous and has no place on this wiki. It shows your anti-Russian bias more than Anatoli ever showed any pro-Russian bias. —CodeCat 13:00, 7 April 2014 (UTC)
Thanks. I can't help to have some Russian bias, though. This is my language, my culture. I can help with the Russian language and Russia-related topics, even if Russian may now be interesting perhaps as a "language of enemy" for some. I don't blame people for criticizing Russian politicians looking at Russia with suspicion. I don't support Russian politics and propaganda but I don't have to apologize for being Russian either. :) Certainly I shouldn't be blamed for being against minorities. Why would I add contents for minority languages, if I wanted to supress them? --Anatoli (обсудить/вклад) 13:19, 7 April 2014 (UTC)
Question book magnify2.svg Input needed
This discussion needs further input in order to be successfully closed. Please take a look!
There is one problem: as WT:DATACHECK reveals, "Komi-Zyrian language (kpv) has a canonical name that is not unique, it is also used by the code kv." Presumably one of the two needs to be retired (or, failing that, at least renamed). - -sche (discuss) 18:52, 2 May 2014 (UTC)
Komi-Zyrian is less ambiguous and clear. Although I favoured "Komi", perhaps we should retire it and leave Komi-Zyrian for kpv and kv and Komi-Permyak for koi. Komi-Zyrian is implied if Komi is used. --Anatoli (обсудить/вклад) 00:12, 3 May 2014 (UTC)
I switched about half of our kv entries to use kpv, and then I got distracted. I'll try to finish sometime soon. (See also User talk:-sche#kv_language_code and Category talk:Komi language.) - -sche (discuss) 04:29, 27 May 2014 (UTC)

Category:Japanese humble language[edit]

Category:Japanese humble terms

I noticed the nonexistent topical category Category:ja:Humble in Special:WantedCategories, and checked, as I often do, whether there was an existing category that already covered the subject. I found these two. The first one was created by User:Haplology, and has more information about Japanese culture, while the other one was created by User:Atitarev along with Category:Korean humble terms, and is more suited to a multi-language series of categories.

It seems to me that Category:Japanese humble terms fits our naming scheme better, so I propose we merge both into that one, and that we convert it and the Korean category to use {{lexiconcatboiler}}, which is designed for this kind of thing. That means creating a category called Category:Humble terms by language with a general description of humble language in its subtemplate. We can then add language-specific details to the Japanese and Korean categories.

I suspect that there aren't many languages that have such well-developed and institutionalized humble lexicons as these do, but I'm sure there are an awful lot of languages that have at least a few such terms- "your humble servant" comes to mind as an English example. Chuck Entz (talk) 00:13, 14 April 2014 (UTC)

It's only to do with two languages - Korean and Japanese. Note: some people mix "honorific" with "polite" or "formal" but the exact concept currently exists only in Japanese and Korean, even if other languages have similar ideas, "honorific" and "humble" are opposite and used in out- and in-group references.
I have posted on User:Haplology's page some time ago, which is now archived. You can see here: [3]. Haplology admitted that the structure wasn't perfect and needs fixing.
The current setup:
In my opinion it should be:
Which matches Japanese more closely.
@Eirikr: might add more to it. I didn't get around to fixing it but I will. It's not a big list. Korean can and should be structured the same way. --Anatoli (обсудить/вклад) 00:26, 14 April 2014 (UTC)
The suggested structure above (2) shows that honorific and humble terms are both part of the respectful formal language but honorific is used in reference to outgroup and humble - to ingroup. The concept and usage are critical in formal communication in Japanese and Korean languages. --Anatoli (обсудить/вклад) 00:31, 14 April 2014 (UTC)
We could also put them directly under Category:Japanese formal terms, if that works. —CodeCat 01:07, 14 April 2014 (UTC)
It's not the same, although if it's related. Category:Japanese honorifics should be a subcategory of Category:Japanese formal terms. "Formal" is opposed to "colloquial" but respectful language is a specific variety, which needs special training, including native Japanese students. E.g. おっしゃる (ossharu, honorific) shows respect to the 2nd/3rd person or outgroup and is never used in self-reference in the polite speech, whereas 申す (mōsu, humble) is used to self-reference or ingroup (even if one talks about own CEO!). Formal words are used regardless who/what they refer to in the formal language, like in any language. An interesting example might be that a person talking to an outsider about own general manager without polite "-san" (e.g. simply Yamada, not Yamada-san) and using humble terms. --Anatoli (обсудить/вклад) 01:19, 14 April 2014 (UTC)

May 2014[edit]

Sardinian templates[edit]

Category:Campidanese_Sardinian_language Category:Gallurese_Sardinian_language Category:Logudorese_Sardinian_language Category:Sassarese_Sardinian_language

merged into


We are not supposed to treat dialects as independent languages. How are these not dialects? --Æ&Œ (talk) 20:21, 6 May 2014 (UTC)

I support a merger of Campidanese (sro) and Logudorese (src) into Sardinian (sc), for reasons I outlined on my talk page and repeat here for others' benefit: those two lects differ from each other, quoth WP, "mostly in phonetics, which does not hamper intelligibility among the speakers". They are perhaps comparable to the dialects of Irish, with standard Sardinian (sc) existing as a unification of the dialects (again, comparable to Irish). Notably, we already include standard Sardinian (sc) — which means the additional inclusion of sro and src is quite schizophrenic.
There is some disagreement over whether Gallurese (sdn) and Sassarese (sdc) are dialects of Sardinian, dialects of Corsican, or languages separate from both Sardinian and Corsican. I would hold off on merging them for now. - -sche (discuss) 03:19, 12 May 2014 (UTC)

Category:Wiktionary:Foo → Category:Wiktionary foo[edit]

I have just finished moving Category:Wiktionary:Language considerations to Category:Wiktionary language considerations in accordance with the discussion above. But that's not the only category that's using "Wiktionary:" as a pseudonamespace. I therefore propose all of the following moves:

If there is consensus to make these name changes, I also request someone with a bot to do it, because the move I did by hand wasn't particularly big, but it sure was tedious. —Aɴɢʀ (talk) 14:28, 7 May 2014 (UTC)

Maybe some of these should have "Wiktionary" removed from the names. Not sure which though. —CodeCat 14:45, 7 May 2014 (UTC)
Category:Help already exists and it isn't clear what the difference is between it and Category:Wiktionary:Help, so those two probably really should be merged. The same goes for Category:Pronunciation and Category:Wiktionary:Pronunciation: they both exist, but seem to have the same function. Category:Statistics is a topic category covering things like Category:en:Statistics and Category:de:Statistics, so it can't be merged with Category:Wiktionary:Statistics. Category:Translation seems like a good potential topic category too, even though it isn't one yet, so I'd rather keep that one free at least. —Aɴɢʀ (talk) 14:55, 7 May 2014 (UTC)


Hello everyone. I'm curious as to how one would go about requesting an exceptional code for the standard Kichwa language? There are several SIL/Ethnologue codes for various Kichwa dialects (Imbabura (qvi), Chimborazo (qug), Cañar Highland (qxr), etc), but not one is for the standard Kichwa language that's taught in schools and used by the government in Ecuador. There is a common Quechua code (qu) is currently used for Quechua Wiktionary and Wikipedia, but both projects are exclusively written in standard Southern Quechua. Both Kichwa and Southern Quechua are part of the Quechua II branch of the Quechuan languages, but they are different dialects with different standardized grammars and different standardized writing conventions. --Dijan (talk) 18:28, 12 May 2014 (UTC)

Hmm... how mutually intelligible are Kichwa and Quechua? It wasn't that long ago that the various Quechua dialects' codes were removed from Module:languages, though I'm having trouble locating the discussion(s) that led to that.
If Kichwa is to be included, we could either (1) pick the code of one of the Kichwa dialects and use it for all of Kichwa (the way we use gcf for all of Antillean Creole), or (2) design our own code, like qwe-kch, according to the system outlined in WT:LANGCODE, point 3.3. - -sche (discuss) 04:25, 27 May 2014 (UTC)
They are mutually intelligible for the most part (similar to differences between Danish and Swedish), but they are also significantly different from each other to be considered separate. Linguistically, Kichwa belongs to a different subgroup of Quechua. The grammar of Kichwa is more simplified (loss of possissive suffixes, loss of the voiceless uvular fricative, etc) and the vocabulary is affected by native languages spoken before the Incan conquest of the territory of today's Ecuador and Colombia (meaning, Quechua was imposed as a foreign language, whereas it is a native language in the regions where Southern Quechua is spoken - in southern Peru and Bolivia).
I was referring to designing our own code and using that as an umbrella for all the Kichwa varieties - which now all use a standardized alphabet different from the Peruvian varieties (such as Southern Quechua), but I couldn't find the procedure for it.
There was an attempt to create a separate Kichwa Wikipedia, but apparently no one got around to it and it got complicated as somone pointed out that an official ISO code must be requested specifically for the standard variety. And for some the problem was that it was trying to use the Chimborazo (qug) code (which is one of the most widely spoken varieties of Kichwa). Apparently the issuing of codes is very strict on Wikipedia. --Dijan (talk) 20:57, 27 May 2014 (UTC)

Category:Middle Chinese language (ltc) and Category:Old Chinese language (och)[edit]

These two languages are being merged as the rest of Chinese topolects per Wiktionary:Votes/pl-2014-04/Unified Chinese into one L2 "Chinese" - PoS are added if there is a pronunciation for a given topolect. The reconstructed pronunciations will be updated from a reliable source and existing transliterations removed but there will be no PoS categories for them, which are applicable to modern Chinese topolects in the modern classification. See for example (expand "Pronunciation" section to see Middle Chinese, Old Chinese pronunciations). As a result, Category:Middle Chinese language (ltc) and Category:Old Chinese language (och) will have to go or be moved to appendices. --Anatoli (обсудить/вклад) 02:21, 21 May 2014 (UTC)

June 2014[edit]

Category:en:Names into Category:English names[edit]

And likewise for other languages. There is nothing particularly topical about names as such. Of course the entities that they refer to have a topical element, but that is distinct from the name used to refer to them. That is, "Canada" is both a country (as a concept; topical), and the English name for that country (as a word; lexical). So I propose that a stricter split is made between these two things. I think that since we already have another category tree for names of people, we might as well extend that category tree for names of other things as well. —CodeCat 17:43, 24 June 2014 (UTC)

After thinking about this some more, I'm not sure about this proposal. I was mainly led by the name of the top-level categories, "Names" and "Place names". These are clearly about the nature of the word rather than what it refers to. A place name is a word for a place, not a place itself. For personal names it's more practical to treat names as types of words, because there are many individuals named "Alice" or "Bob" and putting them in some category like "People" is hardly going to be useful. But at the same time, it's not so clear for things like "countries", or "cities" because by and large these terms are unique in what they refer to. Thailand is clearly the name of one unique place, not a name for many places to be assigned as one sees fit. This means that categories for "countries" would not really contain anything different from categories for "names of countries". Sure, the focus is different (topical versus lexical) but the end result would be the same. So I'm wondering what the best approach would be here. —CodeCat 12:53, 25 June 2014 (UTC)

Wiktionary:Information_desk/Archive_2013/July-December#Question_about_given_names_and_surnames is semi-relevant. Most (but not all!) people seem to agree that there's a distinction between "en:Names" (and "en:Surnames", etc) and "English names" ("English surnames", etc), but not everyone agrees on what that distinction is. - -sche (discuss) 02:10, 4 July 2014 (UTC)
Earlier today, I stumbled on a good example for discussion: Yazdegerd, which seems to be strictly used to refer to Persian emperors who died before the English language even existed. It seems odd to lump this in with names of clearly English origin and usage such as Smith. Yes, it occurs in the English language- but I somehow doubt that the average speaker of English would ever describe it as an English name. Chuck Entz (talk) 03:28, 4 July 2014 (UTC)
Most people here agree that place names are topics and personal names are parts of speech. So it doesn't matter which one you use for the top category, the topic/POS division never made sense with names anyway. Names of foreigners used in another language, like Yazdegerd, have always been a problem. I would place it in a "Category:en:Middle Persian male given names" (cf. Category:en:Persian male given names), but Anatoli always uses the from= parameter and now Vahagn has taken it up too. It might help if Template:given name and Template:surname had a parameter for transliterations. But you'd still have to decide the category name and the definition ("A Middle Persian male given name? A(n English) rendering of a Middle Persian male given name?") CodeCat, please don't make any major change before bringing it up in Beer parlour, otherwise you'll just add to the chaos. Very few people read this page. And be prepared that the discussion will go astray and there will be no consensus, as in the link given by -sche. People who never edit names often believe that there's a miraculous simple rule that will solve everything. --Makaokalani (talk) 13:53, 8 July 2014 (UTC)

July 2014[edit]

Template:U:es:false friend, Template:U:gl:false friend et al[edit]

To whatever extent it's actually worthwhile to have usage notes that amount to "hey, did you notice that none of the definitions of this word are its English homograph? whodathunkit?", it seems to me that we could have a single template that users supply a language code to, and/or invoke via language-specific shell templates, rather than having Template:U:es:false friend, Template:U:gl:false friend and potentially other templates duplicate each other's guts. So, would you all rather merge the templates into a single Template:U:false friend that would accept a language code parameter, and/or keep {{U:es:false friend|...}} et al as shortcut equivalents to {{U:false friend|es|...}}, or what? - -sche (discuss) 02:27, 4 July 2014 (UTC)

We don’t need language specific templates for this. I support merging them. — Ungoliant (falai) 15:19, 5 July 2014 (UTC)
I've created Template:U:false friend and left Template:U:es:false friend and Template:U:gl:false friend as shortcuts to it. - -sche (discuss) 20:34, 21 January 2015 (UTC)

*sъ(n)*sъ, *sъn[edit]

*kъ(n)*kъ, *kъn[edit]

*o(b)*o, *ob[edit]

I think it is bad practice to have parentheses in the entry titles. We should move these pages to one form and have the other be an alternative form. --WikiTiki89 17:33, 14 July 2014 (UTC)

I don't feel strongly about this one way or the other, but the entry titles are inherently unattested, so I don't see harm in notation that enables the content to be fully centralized on one page. And the parenthetical notation is easy to understand, IMO; certainly there are weirder naming schemes out there, like Sino-Tibetan's — it has entry titles like Appendix:Proto-Sino-Tibetan/(s/r)-ma(ŋ/k) and Appendix:Proto-Sino-Tibetan/p(r)an/t ~ b(r)an/t. - -sche (discuss) 18:47, 14 July 2014 (UTC)
Wow, that's even worse. I would say those should be moved as well, but they are also a different scenario, since they indicate different reconstructions, whereas in the cases that I nominated, they just indicate alternative forms. --WikiTiki89 19:21, 14 July 2014 (UTC)
@CodeCat: As the creator of those entries, I was hoping to get your input here. --WikiTiki89 17:23, 17 July 2014 (UTC)
I think it's ok to move them, but which one should the main lemma be on? —CodeCat 17:25, 17 July 2014 (UTC)
I'd say the one with the final consonant, since it's unpredictable. —Aɴɢʀ (talk) 18:22, 17 July 2014 (UTC)

Nyahkur → Nyah Kur[edit]

It seems to be markedly more common to call the language which has the code cbn "Nyah Kur", rather than "Nyahkur". I propose to rename it accordingly, moving its category and updating its one entry (which was notably added using the header "Nyah Kur"). - -sche (discuss) 17:06, 29 July 2014 (UTC)

Yes check.svg Done. - -sche (discuss) 20:22, 21 January 2015 (UTC)

August 2014[edit]

Template:term into Template:m[edit]

We still have both of these templates that does the same thing, but the parameters are named differently. I propose to merge them into {{m}}. The only difficulty is that there are still thousands of instances with {{term}} without a language specified, which can't be converted unless we use "und" as the code. So I will leave those alone for now, unless everyone is ok with converting them to {{m|und|...}}. —CodeCat 12:10, 2 August 2014 (UTC)

What actual good is accomplished, apart from tidying? DCDuring TALK 12:44, 2 August 2014 (UTC)
Exactly. —CodeCat 12:46, 2 August 2014 (UTC)
  • Oppose. Please create a vote, and post a meaningful rationale on the talk page of the vote. --Dan Polansky (talk) 12:56, 2 August 2014 (UTC)
    • Renaming a template doesn't require a vote. —CodeCat 13:21, 2 August 2014 (UTC)
  • Oppose. I am very concerned about continued arbitrariness of changes in templates and modules where one person's possible neuroses could cause needless inconvenience for other users. DCDuring TALK 13:37, 2 August 2014 (UTC)
  • Oppose. What harm is there in letting {{term}} stay? --WikiTiki89 20:58, 2 August 2014 (UTC)
    • Confusing new users by having two different templates, with different parameters, for the same purpose. —CodeCat 21:01, 2 August 2014 (UTC)
      • I don't think it's that incredibly confusing. --WikiTiki89 21:20, 2 August 2014 (UTC)
        • I certainly see no benefit in keeping them both, other than inertia. —CodeCat 21:24, 2 August 2014 (UTC)
          • If it ain't broke, don't fix it. --WikiTiki89 21:59, 2 August 2014 (UTC)
What you call inertia, others might call backward compatibility. For most, {{m}} is an improvement over {{term}}, but the cumulative effect of all the recent changes is bound to have an impact on a lot of users just from the sheer number of new things to keep in mind. People develop habits and "boilerplate" to streamline their workflow, and forcing changes just makes routine tasks harder. This reminds me of a scene in Monty Python's Jabberwocky, where Michael Palin's character tries to help out a blind cooper by rearranging his workshop: it's set up for a far more efficient workflow, but nothing is where the blind man thinks it is, and everything goes horribly, horribly wrong.
It's one thing to deprecate a heavily-used template like term and to replace uses of it with the new one. It's another entirely to delete it and cause problems for intermittent editors who haven't gotten the message yet and have to learn how to edit all over again. Chuck Entz (talk) 22:21, 2 August 2014 (UTC)
So would you be ok with bot-replacing the template now, and re-nominating it at some later date? —CodeCat 22:27, 2 August 2014 (UTC)
Is this really the most interesting thing you can find to do? DCDuring TALK 23:18, 2 August 2014 (UTC)
Why does it matter to you what I find interesting? —CodeCat 23:23, 2 August 2014 (UTC)
Because I would like to be able to trust you not to do things that cause me personally inconvenience and seem to put the aspects of the project at risk. DCDuring TALK 01:25, 3 August 2014 (UTC)
We both want to improve Wiktionary. We just have different ideas on how that would be achieved. My view is that reducing the number of templates also reduces the mental load of new users trying to learn how to make entries. Making sure that similar templates share the same parameters also helps, because it makes their use more intuitive. This is why {{m}} was created and why it has the same parameters as {{l}}, why I merged the category boilerplate templates, why I made this merge proposal, and why I hope that we will merge {{context}} into {{label}} one day. —CodeCat 01:47, 3 August 2014 (UTC)
I have no problem with the creation of new improved templates, just with the elimination of old ones. Can you provide any information on the number of edits made by new users vs the number of old users? DCDuring TALK 07:33, 3 August 2014 (UTC)
Even for established users, having multiple templates that do the same thing but with different parameters is confusing. When {{term/t}} was first introduced, I thought that it was only to be used with reconstructed terms (because it was primarily being used as a replacement for {{recons}}), while {{term}} was to be used with attested terms. It was a long time before I either figured out or someone told me that the two have the exact same function, just with different parameters, and it didn't matter which one you used. So then I always used {{term/t}} (and now {{m}}) so I didn't have to keep typing "lang=" all the time. —Aɴɢʀ (talk) 15:35, 4 August 2014 (UTC)
I'm with CodeCat on this one. Mulder1982 (talk) 19:58, 12 September 2014 (UTC)
  • Of the 33 million total edits ever made to Wiktionary only 6.5 million are made by registered non-bot users, also excluding AF, IW, and Keenebot2. The 67 non-bot contributors at Special:Statistics made about 4.2 million of them, about 65%.
    • Most systems (of many types) show an 80/20 effect. (80% of the work done by 20% of the people) SemperBlotto (talk) 12:52, 4 August 2014 (UTC)
      I didn't know how many people are or were contributing. That addresses one of the premises of the argument justifying the merger. But there are no statistics that justify eliminating a template that folks are accustomed to. That is simply the product of an urge-to-merge. DCDuring TALK 14:05, 4 August 2014 (UTC)
      That's a chicken-and-egg argument of course. —CodeCat 15:20, 4 August 2014 (UTC)
      You never make explicit arguments, let alone coherent ones. Others have to guess what arguments you must be trying to make. In this case do you have any evidence that deleting old templates, rather than simply deprecating them, has any favorable effect on broadening our contributor base. In particular, any evidence that one-letter template names are better for that purpose than whole-word template names? DCDuring TALK 15:37, 4 August 2014 (UTC)
      Templates will be used as long as they exist and are already present in many entries. So they have a kind of inertia behind them. If that alone is a sufficient argument against deleting them, then we would be stuck with (possibly bad) design decisions made a decade ago when Wiktionary was first created. Things need to change if Wiktionary is to improve, you can't keep things the same and improve at the same time. This is the same for all software; some changes will break things that people are used to, and they will need to adapt.
      As for arguments, Angr already gave some arguments above. And you never suggested at any point that deprecating {{term}} would be a good intermediate step, you just opposed altogether, so you shouldn't be surprised if people understand your position to be "we should keep both {{term}} and {{m}} side-by-side indefinitely". And there is no reason to do that of course, other than "we're used to it", which is hardly an argument because it doesn't improve anything as I noted above.
      And just to point out this move proposal is not about the name at all, I don't know where you got that idea from. —CodeCat 15:47, 4 August 2014 (UTC)
      Yes, we are cursed with history, users, and their habits. A successful project can never offer a tabula rasa; that's what new projects and revolutions are for. The biggest improvements to Wiktionary will always be better content to attract more users, some of whom may become registered users, contributors, etc. If I could trust that you cared in the slightest about habits and could change things without breaking them or causing loss of functionality which you often seem to not recognize or not understand, I could accept the conventional wisdom above about change and contribute some of the same: "You can't make an omelette without breaking eggs", etc. But I just don't, based on experience to date.
      YOU were the one proposing a change. I expect YOU to make more cogent arguments than someone who seemed to come to conclusions different from what he was supposed to about the other reforms you have pushed. Presumably Angr was misled by the BP and GP discussions in which you adumbrated your proposal in your customary style. In any event, he expressed only his preference for having template parameters work in a particular way for the templates he uses. Perhaps an increasing number of users will use {{m}} and competing templates will cease being added. At close to that point, and not before, it would make sense to replace all instances of {{term}} with {{m}}, unless something better comes along.
      Deprecation is simply the standard practice for pushing something into decline when the advantages of the "new way" are insufficient to win full user support. At least it was before you apparently decided more draconian measures are necessary for tidyness.
      It may not be "about" the name, but it has appropriated this name. If you think the functionality should be transferred to something with a better name for users, make the proposal. DCDuring TALK 17:47, 4 August 2014 (UTC)
      More likely, Angr simply glossed over the BP and GP discussions as being tl;dr on everyone's part, not just CodeCat's. —Aɴɢʀ (talk) 18:56, 4 August 2014 (UTC)
      It can't have been CodeCat if it was TL. CodeCat post are terse, to the point of being uncommunicative. TL is usually my department. DCDuring TALK 19:07, 4 August 2014 (UTC)
    • That bot vs. non-bot statistics is rather misleading. Since inflected forms are typically entered by bots, they easily get their "points" there. Furthermore, interwiki bots easily collect editing "points", since they iteratively add interwikis, thereby adding nothing of lexicographical value. Ditto for autoformat. Bots are useful, but they do not create the lexicographical content. --Dan Polansky (talk) 23:21, 22 August 2014 (UTC)
My experience with {{term/t}} exactly matches Angr's, lol.
Testing I undertook in investigation of a problem reported in the Grease Pit reveals that Template:term eats more resources and fails more quickly than either Template:m or Template:l. See Wiktionary:Grease pit/2014/August#Pages_Running_Out_Of_Time_and_Memory. It also requires more typing.
I oppose the notion that decisions about template usage should be made by WT:VOTE. (Der Amtsschimmel wiehert!)
If other people want to keep Template:term around, I don't have any strong feeling that it should be deleted. (Replacing it with Template:m on pages that make extensive use of it, so as to gain the time- and resource-savings mentioned in the Grease Pit, is straightforward.) - -sche (discuss) 20:26, 4 August 2014 (UTC)
I think the best course of action is to deprecate {{term}} and replace it in entries when it's used so that people who learn by copying existing entries don't have examples to learn from. My main concern is with people who've always used {{term}} and will have difficulty editing if it suddenly disappears, not with those who just like it because they're used to it. I think we're better off eventually deleting it, but only after it ceases to be widely used. I agree that DCD has some real reasons to distrust and resent CodeCat's methods in general, but in this case, the new template is actually easier to use once one becomes familiar with it- and that's even comparing it with {{term}} as it was back when one wasn't expected to always type "lang=en" for English terms. Chuck Entz (talk) 01:59, 5 August 2014 (UTC)


and all its subcategories. "Analysis" is a very vague name, and lots of fields have aspects called "Analysis" (just look at the list under w:Analysis#Applicants). This category seems to be about mathematical analysis, and so should be renamed Category:Mathematical analysis. I don't mind if the context label remains "analysis" (at least as long as no other field wants to use that word too), but it should display as "(mathematical analysis)" rather than just "(analysis)", which simply isn't specific enough. —Aɴɢʀ (talk) 16:25, 5 August 2014 (UTC)

Support. — Ungoliant (falai) 16:30, 5 August 2014 (UTC)
Support DCDuring TALK 17:33, 5 August 2014 (UTC)

Category:Chinese hanzi to Category:Chinese logograms[edit]

Category:Japanese kanji to Category:Japanese logograms[edit]

Category:Korean hanja to Category:Korean logograms[edit]

Category:Vietnamese Han tu to Category:Vietnamese logograms[edit]

All of these categories represent the same thing, except that they all use local names for them. Using a common name would probably be beneficial. —CodeCat 13:12, 7 August 2014 (UTC)

Oppose. Logograms? No, "logogram" is very generic and is not used to refer to characters in each of these languages. --Anatoli T. (обсудить/вклад) 14:04, 7 August 2014 (UTC)
Abstain. Maybe the word sinogram could do the trick? --Lo Ximiendo (talk) 14:13, 7 August 2014 (UTC)
The point is to make it generic so that it can be applied to multiple languages. What reason is there for using different terms for each of these? Is there an essential difference between Kanji and Hanja other than the language? —CodeCat 14:22, 7 August 2014 (UTC)
There are differences but the problem is with the naming. 漢字 or "Han character" is what is common for hanzi, Hán tự, hanja and kanji. I suspect there will be opposition from editors of CJKV languages. --Anatoli T. (обсудить/вклад) 01:21, 8 August 2014 (UTC)
But if we are going to include the script name, then should we have separate Category:English Latin letters, Category:Russian Cyrillic letters and so on? —CodeCat 14:32, 8 August 2014 (UTC)
We could just do this only for languages that have multiple scripts. --WikiTiki89 14:50, 8 August 2014 (UTC)
Then it would not apply to Chinese. —CodeCat 14:54, 8 August 2014 (UTC)
"Han character" is the most common and neutral translation of 漢字 from all CJKV languages without stressing "Chinese" (if it's causing any problems), even though means Han/Chinese. Sino-Xenic languages use Han (or Kan in Japanese) prefix to refer to the Chinese layer of their respective languages. @CodeCat, I don't get the joke about Category:Russian Cyrillic letters :). You seem to contradict yourself. It's you who are asking for the merger. There still will be Chinese/Japanese/Korean/Vietnamese in the cat name, it's just the 2nd part, which is currently different. "Logogram" doesn't describe well the role hanzi/kanji, etc. in these languages. "Sinogram", although uncommon is the closest equivalent. Han characters have long deviated from the original solely logographic usage. Han characters are very different from other logographic scripts. There are a lot of phonetic elements, mixed and the original meanings are often lost or unknown. Although JKV languages have their own, home-made Han characters, especially Japanese and Vietnamese, they all have Chinese origin by nature and design. Japanese also differs from other Sino-Xenic languages in the way kanji are used to write native words and attach parts of the word in kana. There is hardly an equivalent of Japanese kanji. I think Japanese editors/users will oppose referring to "kanji" as "logograms". Perhaps "kanji", more than hanzi/hanja/Hán tự has become a too common term to be replaced with something else. I think it's better to move or link this discussion in the BP to make it more visible. --Anatoli T. (обсудить/вклад) 00:12, 12 August 2014 (UTC)
Oppose, agreeing with Anatoli. User: PalkiaX50 talk to meh 00:19, 12 August 2014 (UTC)
My reasoning for calling the categories "logograms" is that they are then parallel to categories for other kinds of written symbols, like Category:English letters and Category:Japanese syllables. I'm not sure what the benefit of including the name of the script in the name is. Your proposal, to name the categories "Han characters", is parallel to having categories like Category:English Latin letters or Category:Russian Cyrillic letters. That is, a category that includes the name of the script, and contains only the characters in that one script. So what I wonder is, why do we not include the name "Latin" in Category:English letters, but we do see fit to include various language-specific names for Chinese characters in the category names? It's not very consistent. —CodeCat 00:18, 12 August 2014 (UTC)
Hmm, they are called hanzi/kanja/hanja/Hán tự (Han tu) here because they are called so in the native languages and by linguists who work with these languages. ("Hanzi" is less settled because of the variety of transliterations and topolects in Chinese, e.g. Cantonese would be "hon3 zi6" in Jyutping and "hon jih" in Yale transliteration.) I personally don't see the problem in using "Chinese" or "Han" in the category name because this is what they are normally called as. We can't call them "letters" because they are not. "Han character" is the term parallel to "letters", "symbols", "syllables" if we need a generic term for all 4 CJKV languages. You seem to dislike it simply because it contains a language name. (I'm not voting yet on "Han character" categories, I need to see a broader discussion on this, I'm just saying it's the only common and correct term for this, IMO.) --Anatoli T. (обсудить/вклад) 00:34, 12 August 2014 (UTC)
As far as I know, people don't call them "Han characters" most of the time, they just call them "characters". In the same way that people say "what letter is that" when pointing at A, they would presumably say "what character is that" when pointing at 漢. So should we call them Category:Chinese characters, Category:Japanese characters etc? That might be too broad... —CodeCat 00:41, 12 August 2014 (UTC)
Yes, characters are too broad and using "characters" may be used to refer to Chinese, since only Han characters (hanzi) are used, it's obvious and "hanzi" is rather new. For Japanese and Korean, it becomes immediately wrong to use simply "characters" because katakana, hiragana and hangeul are also characters. "Han characters" ARE quite common but less common than kanja/hanja/Hán tự and, as I said, for Chinese, people refer to hanzi as simply "characters" because it's more obvious (it's the only script for the language, unless you talk about say, mixed Min Nan text with hanzi and pe̍h-ōe-jī, then you have to be more specific) and Chinese themselves usually simply use , which is not the case with other JKV ( is also too generic and may also refer to e.g. Roman letters in different contexts). --Anatoli T. (обсудить/вклад) 01:11, 12 August 2014 (UTC)
That's why I suggested using "logograms". It's equivalent to "letters". It's not used as often, no, but for lack of a better word that generically describes the type of character like "letter" does, I'm not sure what else we could use. Maybe we should consider just what use Category:English letters is supposed to convey. Is it the fact that it's, specifically, an alphabetic character, or is its main use to hold characters used for writing words? If the latter is the case, then maybe we should move all the "letters" categories to "characters" and then, for languages written in multiple scripts, subdivide by script. So then we would have Category:Japanese Han characters and Category:Japanese Hiragana characters, and they would have the generic Category:Japanese characters as their parent. —CodeCat 01:17, 12 August 2014 (UTC)
I don't know. I'm a bit lost in your logic. The same way "Han characters" can also be subcategories of "character" categories. Why? There's no reason to invent something, which is not normally used, just to avoid the commonly used terms, which seem less politically correct(?). I liken this to inventing "Old East Slavic" term instead of "Old Russian", which even contradicts the naming in the East Slavic languages themselves and most other languages, cf. "Oudrussisch" in your native language (which didn't simply copy the term from English). --Anatoli T. (обсудить/вклад) 01:39, 12 August 2014 (UTC)
And I'm a bit lost trying to explain it, sorry. I'll try to reword it in a more step-by-step way.
  1. Right now, we have various categories with different names, which all contain the same basic thing: characters in the Han script.
  2. When we look at what categories other languages use for their characters, things are very different. For languages written in alphabetic scripts, there is only a "letters" category, with no mention of the script.
  3. Thus, my initial thought was to make the Han character categories match that, and I came up with "logograms". "Logogram" describes the type of character, just like "letter", so it is parallel and fits well alongside it.
  4. But as others have said, quite rightly, the name "logogram" itself is not widely used, and is therefore less informative. So I wondered what other ways we could change our current category names so that they are more similar across languages.
  5. And so, I suggest that for all languages, characters used for writing words in the language are placed in a generic "characters" category, which is itself a subcategory of "symbols" (the top level). The "letters" categories would thus be renamed to "characters" in all languages, including English. A#English would go in Category:English characters. Chinese characters would, appropriately, end up in Category:Chinese characters.
  6. For languages like Japanese or Serbo-Croatian, which are written in multiple scripts, a subcategory for each script is created. This would give Category:Japanese Han characters, Category:Japanese Hiragana characters, Category:Japanese Katakana characters and also Category:Serbo-Croatian Latin characters and Category:Serbo-Croatian Cyrillic characters.
Is it more clear this way? (Also, just to note, we have Oudoostslavisch too) —CodeCat 01:53, 12 August 2014 (UTC)
We already have Category:Han characters, which can be a subcategory of Category:characters. Category:Japanese hiragana sounds much better than Category:Japanese Hiragana characters and it still can be a subcat of Category:characters, even if it's missing the word "characters". I'm not sure if the community accepts renaming "letters" to "characters" for Latin, Cyrillic, etc, based languages. Category:Han characters is better than Category:Chinese characters as an umbrella term for hanzi/kanji... for CJKV languages. --Anatoli T. (обсудить/вклад) 06:45, 12 August 2014 (UTC)
The problem with trying to generalize is that Han characters are the product of the writing system evolving over thousands of years in very complex ways until the result is impossible to categorize. A character can be a word, a syllable, a morpheme, or an idea- but it's usually some combination. Unlike in most writing systems, characters are made up of recognizable parts that can be combined, so that a given character may have a parts that are phonetic and parts that are semantic. In Japanese, it gets even more complicated, with many successive borrowings of words and their native equivalents all spelled with the same characters, but pronounced differently, depending on the context. Korean, Japanese, Vietnamese and all the dialects of Chinese share enough letters that many chunks of text can be read by all, but when read aloud they can be completely unintelligible between languages. Or there can be a thread of related sounds shared between the languages for a given character. The only comparable phenomenon I can think of would be the cuneiform system, and that's been dead for millenia. Sure, you could call them logograms, but you would also have to call them syllables and/or morphemes and/or particles- it varies unpredictably. I vote for avoiding that whole tangle of intertwining possibilities and just calling them Han characters. Chuck Entz (talk) 09:07, 12 August 2014 (UTC)
That's why I think simply "characters" (preceded by the language) is the most general. But I agree that people might not like renaming Category:English letters. I'm just not sure. Are Han characters really that unique that they would deserve their own name in Module:category tree/poscatboiler/symbols? I'm not really happy with Category:Chinese Han characters standing on the same footing as Category:English letters, because the former says specifically what script the characters belong to while the latter instead specifies what class of writing system they belong to. My main aim is to make the names generic enough that they can be reused easily by many languages, but also to make the category tree internally consistent. So either all the categories specify the class (letters vs. logograms), or they all specify the script name (Han characters vs Latin characters), or do neither (just "characters"). But I suppose if there is no other sensible way to do it, we'll just have to settle for "Han characters". It's still better than all the language-specific names. —CodeCat 20:29, 12 August 2014 (UTC)
Category:Chinese Han characters can be a subcategory of Category:Chinese characters, which would be on the same level as Category:English letters. That way JKV scripts (katakana, hiragana, hangeul), including Han characters end up on the same level as Category:Chinese Han characters. --Anatoli T. (обсудить/вклад) 01:02, 13 August 2014 (UTC)
I oppose moving these categories. Virtually no one says "Japanese/Korean/Vietnamese Han characters" or "Vietnamese logograms" (search in Google Books). "Chinese Han characters" sounds redundant and contrived. Wyang (talk) 23:40, 21 August 2014 (UTC)
Could you not have said so before I did most of it already? *sigh* —CodeCat 01:18, 22 August 2014 (UTC)
In addition to opposing the moves, I also oppose you starting it when nobody has voted support. --kc_kennylau (talk) 01:43, 22 August 2014 (UTC)
Then what about the whole discussion that followed, in which the conclusion was, it seemed, that "Han characters" was ok? There was no further comment on that so I assumed it was ok. —CodeCat 01:49, 22 August 2014 (UTC)
AFAIK, people do not dislike Category:Han characters, but Category:Chinese Han characters is not brought up until 2014/08/12 20:29 (UTC), and then Anatoli says that this category can be parallel with blah blah blah, without ever mentioning his support. PostScriptum: I prefer the word "sinogram" if the categories have to be unified. --kc_kennylau (talk) 01:59, 22 August 2014 (UTC)
I personally warmed to the idea of "Chinese Han characters", which essentially means the same as "Chinese hanzi", even though "Han=Chinese=Sinetic". My preference is also hanzi/kanji/hanja/Hán tự but if we need to merge them into one category, "Han character" is a better translation of all these. Merging would also possibly allow us to eliminate cmn-hanzi, hak-hanzi, yue-hanzi. I didn't express support but just mentioned that Han characters, IMO, is a better term than logogram. "Sinogram" is also correct but it doesn't seem as common as "Han character" when referring generically to Chinese characters. --Anatoli T. (обсудить/вклад) 02:12, 22 August 2014 (UTC)

Apparently this is not happening. Closed. Keφr 13:41, 3 January 2015 (UTC)

Category:Japanese romaji to Category:Japanese romanizations[edit]

(Notifying Eirikr, Wyang, Haplology, Atitarev):

"Romaji" is just the Japanese word for romanization; it does not actually indicate a specific transliteration scheme like the name "pinyin" does for Chinese. Since we already have Category:Chinese romanizations, Category:Egyptian romanizations and Category:Gothic romanizations, I propose moving the contents of Category:Japanese romaji to Category:Japanese romanizations and deleting the former when it's empty. —CodeCat 20:16, 12 August 2014 (UTC)

There are various romanization for Japanese as well but only form was adopted. Although the word "rōmaji" is used, it's based almost entirely on Hepburn romanisation. Perhaps, like pinyin it can remain a subcategory of Category:Japanese romanizations but Category:Japanese romaji should have a description what it's based on? Adding "Hepburn romanisation" to the category name seems awkward. I don't foresee any other scheme for Japanese to be adopted but it's again about the name, "romaji" is favoured by most linguists and learners of Japanese. Will wait for more comments but I think Wyang will oppose romanisation entries. --Anatoli T. (обсудить/вклад) 00:54, 13 August 2014 (UTC)
I don't think there's a need for a subcategory if there is only one scheme. —CodeCat 00:57, 13 August 2014 (UTC)
Yes, it makes to use consistent category names. Undecided for now. (Notifying TAKASUGI Shinji, Whym, Haplology): , (Notifying Tooironic, Kc kennylau): . --Anatoli T. (обсудить/вклад) 01:10, 13 August 2014 (UTC)
Support. Japanese romaji sounds redundant because romaji practically means Japanese romanizations. — TAKASUGI Shinji (talk) 01:18, 13 August 2014 (UTC)

citing book templates[edit]

This task is within the scope of the project Citations and quotations.

{{cite book}}, {{quote-book}}, {{cite-book}} all do really similar things, but slightly differently. --Rising Sun talk? contributions 22:16, 11 March 2010 (UTC)

Support merger/standardization. --Bequw τ 21:41, 23 April 2010 (UTC)
Yeah sounds good, but difficult for relatively small benefit. Mglovesfun (talk) 21:48, 23 April 2010 (UTC)
I've made {{cite book}} redirect to {{reference-book}} (which I beefed up to handle a few extra extra parameters), since neither of these were used really with quoted passages. Their formatting styles were different so please edit it to make it more like others if possible.
Right now we usually use quote-* templates between definitions and we use cite-* for unordered lists (usually Citation: pages). Ideally one set would direct to other just with a different predefined indent. --Bequw τ 21:32, 13 July 2010 (UTC)
Or we could eliminate the whole "indent" concept: it's not actually necessary. {{grc-cite}} doesn't use it, for example. —RuakhTALK 15:20, 5 November 2010 (UTC)
  • Redirected {{quote-book}} to {{cite-book}}. Apparently that was all needed to be done. Hopefully nothing broke --Type56op9 (talk) 17:23, 18 August 2014 (UTC)
    That redirection was undone, but it would still be good to merge these templates. I've therefore moved this back to the main RFM page, out of the archive of unresolved requests. - -sche (discuss) 21:54, 18 August 2014 (UTC)
    Why bother? Some folks are accustomed to one, others prefer another. One or more could be deprecated in documentation and categorization to discourage use. Merging to combine features runs the risk of complication. If someone has a new, improved version, let it prove its superiority by outcompeting the others. DCDuring TALK 23:07, 19 August 2014 (UTC)

Appendix:Indo-Iranian Swadesh lists (extended)[edit]

split to Appendix:Iranian Swadesh lists and Appendix:Indian Swadesh lists--Kaiyr (talk) 14:36, 19 August 2014 (UTC)

The second one should be Appendix:Indo-Aryan Swadesh lists per Category:Indo-Aryan languages, but I see Appendix:Indo-Aryan Swadesh lists already exists and needs cleaning up. —Aɴɢʀ (talk) 16:14, 19 August 2014 (UTC)

Template:ja-romanization of[edit]

Above it was noted that all our Japanese romanizations follow the Hepburn scheme. But the form-of template currently just says "romaji reading of", which is not really very specific, as "romaji" just means any kind of romanization. This is not even technically correct because you can't really call something a "reading" if you're just romanizing. I believe it would be clearer if it said either "romanization of" or "Hepburn romanization of". If we include the name of the scheme used, this would remove any ambiguity that users might have. But it also opens the door to possibly introducing other schemes for Japanese if we ever desire to. Either way, being explicit about it is good. —CodeCat 21:00, 21 August 2014 (UTC)

The option "romanization of" seems good and close the door to possibly introducing other schemes for Japanese :) --Anatoli T. (обсудить/вклад) 23:18, 21 August 2014 (UTC)

German rhymes -iːʀən/-iːʁən/-iːɐ̯n[edit]

These three pages all deal with the same rhyme ending. Please check which one follows the local IPA rules for German and merge them. Cheers, Kronf (talk) 09:44, 22 August 2014 (UTC)

They should be at Rhymes:German:-iːʁən. —Aɴɢʀ (talk) 22:58, 22 August 2014 (UTC)
In this case, Rhymes:German:-eːʀən and Rhymes:German:-øːʀən should be moved, too. --Kronf (talk) 15:30, 23 August 2014 (UTC)
I thought we used /ʀ/ for German. At least, that's what I see in actual entries. Renard Migrant (talk) 11:08, 28 August 2014 (UTC)
Updated to reflect the new naming scheme of rhymes pages, the preceding links are: -iːʀən/-iːʁən/-iːɐ̯n, which Angr says should all be Rhymes:German/iːʁən, prompting Kronf to say Rhymes:German/eːʀən and Rhymes:German/øːʀən should also be moved. (I'm providing this so people can see they're all still blue links.) - -sche (discuss) 22:07, 20 September 2014 (UTC)

Category:en:Nationalities to Category:English place-name adjectives[edit]

This category, as well as the equivalents in other languages, contain many terms that are not strictly nationalities as they are not associated with actual countries. Instead, these seem to be more generally "place-name adjectives". So I think we should rename this category. —CodeCat 21:59, 22 August 2014 (UTC)

Nationalities don't have to be associated with actual countries- they can be ethnicities as well. Besides, there are cases such as Inuit where there's no place name involved. Chuck Entz (talk) 22:39, 22 August 2014 (UTC)
But I'm pretty sure that when someone says "my nationality is Inuit", that it will give some raised eyebrows. —CodeCat 22:42, 22 August 2014 (UTC)
Umm... no. In fact Inuits are one of the so-called "First Nations", so the word "nationality" naturally applies. While I agree that "nationality" is not the best term for the category, I think your proposed name is worse. --WikiTiki89 22:50, 22 August 2014 (UTC)
I've been looking for another possible term for this, but I'm struggling to find anything. Do you have any ideas? We can't use "ethnicities" because state-level nationality is not necessarily an ethnicity. Maybe we should really have two categories: one for place names and one for ethnicities that are not associated with place names. —CodeCat 22:56, 22 August 2014 (UTC)
I think a nationality does have to be an association with a country. But it doesn't mean we should rename this category, move out the bad entries and put them in Category:en:Demonyms. Renard Migrant (talk) 11:06, 28 August 2014 (UTC)
Don't rename. I agree with Chuck's comment. Not all nationality designations are derived from placename designations; "Inuit" and "Crow" are examples, but "Dutch" and "Drukpa" are also examples, aren't they? "Dutch" isn't etymologically connected to any placename that is still in use in English; it's semantically associated with "Netherlands", but then, "Crow" is semantically associated with "Crow Nation" / "Crow Reservation", "Inuit" with "Inuit territory", etc. I don't think it would make sense to label either "Crow" or "Dutch" a "place-name adjective". (Notably both "Crow Nation" and the etymological placename relative of "Dutch", the archaic "Dutchland", seem to be derived from their corresponding nationality terms.) Terms that are not nationalities in any sense can be moved to the Demonyms category as Renard suggestions. - -sche (discuss) 18:58, 28 August 2014 (UTC)
The demonyms category is for nouns for individual people. The proposed category is for adjectives. In English, the adjectives can normally be used as collective nouns for the people, but this doesn't apply to other languages of course. Compare Dutch Nederlanders pl (Dutch people, noun) and Nederlands (Dutch, adj). —CodeCat 19:14, 28 August 2014 (UTC)
I just noticed that according to both Wiktionary and Wikipedia, a demonym is the name of an inhabitant or native of a specific place. So it is not appropriate to place terms like "Inuit" there. In fact, it appears that we currently have no category at all where that word belongs. We should find a solution for this. —CodeCat 19:21, 28 August 2014 (UTC)
Oh, I had thought "demonym" meant any "term for a people" (because "democide" is generic systematic "killing of people"). You're right in your second comment that it seems to actually be limited to people from a specific place. Well, there are several possibilities for ethnic-group names, e.g. "ethnonyms", "ethnicities", "ethnic groups". If the Inuit are deemed to not even form one ethnic group (and hence one ethnonym), then WP's definition ("a group of culturally similar indigenous peoples") suggests we don't need to categorize that term at all, any more than other "cultural groups" like "Goths" (the black-clad ones, not the ones that wrote like 𐌰𐌱𐌲). - -sche (discuss) 23:59, 30 August 2014 (UTC)
Ethnicities can form a tree though. For example, Poles are a subset of Slavs. Often ethnic and linguistic trees coincide, but certainly not always. I'd say that the Inuit are a larger group even if they have smaller subgroups. The question then becomes whether "ethnonym" is suitable for a term like "Londoner" or even for "Russian". Ethnic Russians are quite different from people who live in Russia. —CodeCat 00:44, 31 August 2014 (UTC)
Good point re trees. So, "Inuit" can still be an ethnonym. "Russian" is both an ethnonym (in sense 2, "a member of the East Slavic ethnic group which constitutes the majority of the population of Russia") and a nationality (in sense 1, "a person from the Russian Federation"), with 'nationality' being a subcategory of 'demonym'. Likewise many nationalities: "German" (Aydan Özoğuz=nationality, Ernesto Geisel=ethnicity), "Brazilian", "Nepali", etc. In some analyses, "Haida" is also both an ethnonym and a nationality, but unlike "Russian" where one sense is the nationality and another sense is the ethnonym, "Haida" has a single sense that is both at once. "Londoner" is exclusively a demonym and not an ethnonym, right? Likewise most city designations. - -sche (discuss) 02:51, 31 August 2014 (UTC)
How is Haida a nationality though? I don't know of any country called that. —CodeCat 10:44, 31 August 2014 (UTC)
"Country" and "nation" are two different things. ("State" is another different thing.) Indeed, the first usex of the first sense of [[nation]] is "the Roma are a nation without a country", and the second is "the Kurdish people constitute a nation in the Middle East"; I've just added some similar citations from literature to Citations:nation. The Haida are a First Nation. Like the Kurds are associated with Kurdistan and the Ukrainians are associated with Ukraine, the Haida are associated with the Queen Charlotte Islands / Haida Gwaii. Notably, neither the Kurds / Kurdistan nor the Haida / Haida Gwaii nor the Ukrainians / Ukraine have always been a nation in sense 2 of that word, which raises a question: even if one argued that Category:Nationalities should be restricted to sense-2 nations to the exclusion of sense-1 nations, would it be only for entities that are at present sovereign states, or would it also include things which historically constituted such, e.g. would "Czechoslovak" go in the category? Most entities which are nations in sense 1 have at some point also been nations in sense 2 — including the Haida, who regardless of their status in the current period were the sovereign governors of a territory in the period before and shortly after European contact. - -sche (discuss) 17:31, 31 August 2014 (UTC)
That's a good point. But in the end the question remains: if "nationality" is not appropriate or is too misleading, what term should we use? And what can we do to ensure that only adjectives end up in the category? Including "adjectives" in the name would make it no longer a topical category, despite DCDuring's misgivings. —CodeCat 10:45, 2 September 2014 (UTC)

We can put ethnonyms like Russian sense 2, Gypsy, Inuit, Chechen etc. in Category:en:Ethnicity. Or even better, we can rename the latter to Category:en:Ethnonyms. --Vahag (talk) 21:06, 1 January 2015 (UTC)

  • Closed as not moved: No consensus to move. Purplebackpack89 22:30, 2 January 2015 (UTC)


The sense with pararlas as a headword should be at um, pararlas. Am I missing something here? Renard Migrant (talk) 11:03, 28 August 2014 (UTC)

Support. — Ungoliant (falai) 00:05, 1 September 2014 (UTC)

Template:alternative capitalization of[edit]

This template and its friends (Template:obsolete capitalization of and any similarly named templates) have been discussed before here and here, with some users objecting to the use of the templates on lowercase strings like protestant and god#Proper_noun. Would it make sense to change the display text from "alternative capitalization of" to something else, e.g. "alternative case form of"? The template names would not necessarily have to be changed, and if they were changed, the current names could be kept as redirects. - -sche (discuss) 23:30, 31 August 2014 (UTC)

‘Alternative case form of’ does sound superior. It’s misleading to call lower‐case forms ‘capitalizations.’ We should modify the wording to be more inclusive. --Romanophile (talk) 19:10, 29 September 2014 (UTC)
I agree with -sche. — I.S.M.E.T.A. 13:53, 2 October 2014 (UTC)
Moved to Template:alternative case form of, with Template:alternative capitalization of left as a redirect. - -sche (discuss) 14:29, 1 November 2014 (UTC)
Sorry for objecting so late, but recently when I see "case" in a dictionary, I tend to think of grammatical case, not letter case. I think this may cause more confusion than it solves. Keφr 14:55, 1 November 2014 (UTC)
I'd've objected as well as, while supposedly more 'inclusive', it's a lot less clear what it refers to. Seems ultimately self-defeating, perhaps replace with {{form of|alternative capitalization}} in order to be less confusing. Renard Migrant (talk) 15:22, 1 November 2014 (UTC)
What about changing what is displayed to "alternative letter-case form of word"? — I.S.M.E.T.A. 18:27, 1 November 2014 (UTC)
  • Oppose: Because it was better at the old title, because nobody uses "alternative case form" and lots of people use "alternative capitalization", because it wasn't properly tagged as an RfM, and because it should have been better publicized because this is such a high-profile template. Purplebackpack89

September 2014[edit]

"entries needing reference" categorization[edit]

This is a little strange, because all of these are redlinks at the moment, but templates have been modified to generate cats using this naming scheme, and I would like them all to go away. While it might seem nice to unify things, having diverse templates using the same cats means you have to generalize away all the useful information and you end up with mumbling and hand-waving.

I'm sorry, but "English entries needing reference" makes no literal sense, and it's impossible to tell from the cat name what's supposed to go in it- you might as well call it "English entries needing something or other". Please change it to something that makes sense before we create a lot of really lame categories that will have to be deleted. Chuck Entz (talk) 05:17, 1 September 2014 (UTC)

Entries are placed in those categories by {{rfv-etymology}} and {{rfv-pronunciation}}. Both templates specifically ask for a source, so the name seemed appropriate. Before I changed them, these templates just categorised in the generic "needing etymology" and "needing pronunciation" categories, which was not really any more helpful. —CodeCat 10:56, 1 September 2014 (UTC)
But your solution just substituted one problem for another, by eliminating any reference to etymologies or pronunciation: providing references for an etymology is quite different from providing references for a pronunciation. Also, treating reference as uncountable makes the category names look like typos- does anyone use reference that way? Can one ask, "how much reference do you need?"
A few possible alternatives (the equivalents for pronunciation are left as an exercise for the reader...):
  1. [] etymologies needing to be referenced
  2. [] etymologies needing references
  3. [] etymologies needing referencing
  4. [] etymologies needing to be sourced
  5. [] entries with etymologies needing to be referenced
  6. [] entries with etymologies needing references
  7. [] entries with etymologies needing referencing
  8. [] entries with etymologies needing to be sourced
  9. [] entries with unreferenced etymologies
Chuck Entz (talk) 01:02, 2 September 2014 (UTC)
I would prefer "entries needing etymology reference" or "entries needing etymology source". The name doesn't treat it as uncountable; it just leaves out the article as a shorthand. A plural doesn't seem appropriate as it would imply that more than one reference is needed. —CodeCat 10:43, 2 September 2014 (UTC)
I agree with Chuck about the missing article. It seems non-native or needlessly telegraphic to drop it. What do we hope to accomplish by dropping it as no human keystrokes are involved? Are we suddenly concerned with server resources, download times? As to the implications of the plural, there is no more implication than there would be using the singular. DCDuring TALK 13:47, 2 September 2014 (UTC)
  • I wholeheartedly agree with Chuck. We need more specificity of categories not less.
Whether the prefix to these types of requests should be "rfv" is another question that should be addressed while we have fewer than a hundred of these. Are we fairly sure this prefix will turn out to be adequate? DCDuring TALK 01:36, 2 September 2014 (UTC)
The template names go back 7 or 8 years, and I seem to remember discussions as to whether it was a good idea to link etymologies, which take citations in the Wikipedia sense, with rfvs, which take citations in the Wiktionary sense. Chuck Entz (talk) 01:50, 2 September 2014 (UTC)
The only alternative I know of that has some installed base is {{fact}} (45 transclusions here, and lots of pedians who have the habit), which would need to be followed by "pron" or "ety" (or "usage" etc?), but that might quickly get us part ways back to where we are now with a template likely to be overused and with an undifferentiated category. I suppose that if we made {{fact}} generate a screen that required the users to say what type of problem concerned them or could detect the previous heading in an AF-type bot run, we could make that work. Some new prefix, like "ref", could work. DCDuring TALK 02:38, 2 September 2014 (UTC)
I would add that the subject nouns are plural, so one could just as easily say that using a singular object would imply that one reference or source would do for all the entries in the categories- but that would be silly, too. Chuck Entz (talk) 14:14, 2 September 2014 (UTC)
I've created the "needing reference" categories as they were originally named. This does not mean I'm enforcing that particular state of affairs (in case someone gets the wrong idea - you know who you are), it's only so that they aren't left in a redlinked state for ages, filling up Special:WantedCategories. They will presumably be deleted again once there's an agreement on what to name them. I do want to note, though, that as far as omitting the article goes, we already have "entries needing inflection", "entries needing definition", "entries needing etymology", "entries needing pronunciation", "entries needing audio pronunciation", "entries needing quotation" and "terms needing transliteration". I think that whatever name is chosen should fit with the existing names, or else all these should also be renamed to maintain consistency in the naming. —CodeCat 20:51, 20 September 2014 (UTC)

Category:Zootomy and Category:Phytotomy[edit]

I request that these categories be moved to Category:Animal anatomy and Category:Plant anatomy respectively. The fuller names are more easily understandable and far, far more common (per b.g.c ngrams) than the terms "zootomy" and "phytotomy". Even Wikipedia uses the more understandable names for their categories. All language-specific subcategories are of course nominated too. —Aɴɢʀ (talk) 10:33, 2 September 2014 (UTC)

We now also have Category:Body. The anatomy categories are really meant for technical/medical jargon used in the field of anatomy, not for categorising simple parts of the body generally. I do support the rename, but this is something that should probably be looked at too. —CodeCat 19:50, 2 September 2014 (UTC)
Is Category:Body also for animal bodies? Would we put horn and antler and tail there? Either way it's not really an appropriate place for leaf and stem and petal, which aren't technical jargon but ought to have a home somewhere in our rather chaotic category hierarchy. —Aɴɢʀ (talk) 21:35, 2 September 2014 (UTC)
I agree. Animal bodies share many terms with humans, but the terms for plant bodies are normally entirely separate, so maybe "Animal body" and "Plant body" categories should be created. The former would be a subcategory of "Body", while the latter would be a sister category. When I rearranged many of the categories, my aim was always to split things up in the way that the average human would do. So the categories specifically reflect an anthropocentric view of the world rather than a scientific one necessarily. —CodeCat 21:43, 2 September 2014 (UTC)
I'm not sure I like the idea of having some topic categories for technical terms and other topic categories for everyday terms. When I'm deciding where to categorize a term, I often look at Wikipedia to see where they categorize something, and then try to find the closest corresponding category here. And they definitely categorize Horn (anatomy) and Antler and Tail in :Category:Animal anatomy (or a subcategory of it) and Leaf and Plant stem in :Category:Plant anatomy. (Petal is only in :Category:Plant morphology for some reason; I'm unsure what the difference is supposed to be.) —Aɴɢʀ (talk) 22:01, 2 September 2014 (UTC)
The problem is that we have many topical categories that only exist because there is a label that categorises terms in them. For example, {{label|en|anatomy}} will add things to Category:en:Anatomy. As these labels are meant to be used to indicate technical jargon, we've now ended up with a whole category tree full of science terms, including this one. We have never been very consistent in how labels are used, which has caused a proliferation of entries using labels just to categorise, rather than to indicate jargon. It doesn't help either that there has never been any kind of conclusive discussion on what topical categories are meant to achieve in the context of a dictionary, nor how they are delimited from other kinds of categories. Until we answer those more fundamental questions, issues like this will never be solvable. —CodeCat 22:13, 2 September 2014 (UTC)

Category:English locatives to Category:English location adverbs[edit]

This seems more appropriate, given that the category only contains adverbs. I can't think of anything that might belong here that is not an adverb. —CodeCat 23:18, 19 September 2014 (UTC)

To move this to some called "adverbs" makes a stronger statement than some grammarians would make. A word like home need not be treated as an adverb. Furthermore prepositional phrases can be locatives but it does some violence to their function to call them adverbs. DCDuring TALK 00:14, 20 September 2014 (UTC)
As a further illustration an expression like where the sun don't shine a clause that is obviously a locative, as are where angels fear to tread (a clause, from, but not an alt form of the proverb), every which way (a noun phrase), and where it's at (clause). If the membership criteria are not explicitly, clearly, and reviewably specified in such a way as to exclude these, the change seems simply wrong. DCDuring TALK 19:46, 20 September 2014 (UTC)
I don't see why they would need to be excluded. They are location adverbs to me. —CodeCat 20:24, 20 September 2014 (UTC)
You have confused semantic function and word class. DCDuring TALK 23:12, 2 January 2015 (UTC)
Why is it necessary to distinguish them? —CodeCat 01:21, 3 January 2015 (UTC)
Only to be nice to users by avoiding needless confusion and redundancy. In English almost any word can assume almost any function in at least some cases, often attestably so. It is not that Adverb is all that well-defined a word class in English to begin with. We use it because we need to provide hooks from our content to what users may remember from their schooling. DCDuring TALK 04:23, 3 January 2015 (UTC)
  • Oppose: Nominator has not made the case for the move IMO, at least not to my satisfaction. Purplebackpack89 22:33, 2 January 2015 (UTC)

Category:English temporal location adverbs to Category:English punctual adverbs[edit]

I think "punctual" is the more common way to describe these? —CodeCat 23:41, 19 September 2014 (UTC)

"Temporal adverb" is much, more common, though it may include a more diverse group of adverbs DCDuring TALK 00:19, 20 September 2014 (UTC)
I believe that we are making a mistake to treat all of these in subcategories of parts of speech. We can be free of the tyranny of the word classes that users are familiar with for purposes of categories of this kind, though sadly not for headings. There are nominals that are not nouns, MWEs that are not phrases of any kind. Forcing a category structure to be hierarchical is convenient in a bureaucratic kind of way, but it does a great deal of violence to the reality of things. DCDuring TALK 00:27, 20 September 2014 (UTC)
There was Category:Latvian temporal adverbs, which I renamed to Category:Latvian time adverbs while also creating Category:English time adverbs. I did this because "temporal" seems like a higher-register word, which is like the distinction between "location" and "locative" - and we already had Category:English location adverbs as noted in the discussion below. So I figured that "time" was a better lexical counterpart to "location" than "temporal". Using "temporal location" is confusing as it gives the impression that these adverbs indicate a place, which they don't of course. But it also misses the point of the category. The defining characteristic is that these refer to punctual moments in time, analogous to adverbs which denote stationary position. They contrast with adverbs like "yearly" or "for a year" which denote frequency and duration respectively. These, of course, are also temporal location adverbs, but they don't belong in this category as they have their own categories (Category:English frequency adverbs and Category:English duration adverbs), so the suggested new name is an attempt to make this more explicit. —CodeCat 21:01, 20 September 2014 (UTC)
Note that the other categories both use nouns attributively instead of adjectives, eg, not "frequent adverbs", but "frequency adverbs". The nouns are chosen because they have a different meaning than the adjectives. "Punctuality" obviously doesn't cut it. Can you think of any other one- or two-word nominal that would be better than "temporal location"? DCDuring TALK 14:04, 23 September 2014 (UTC)
  • Oppose. Ain't broke. --Dan Polansky (talk) 08:14, 20 September 2014 (UTC)
    • It is, see my reply above. —CodeCat 21:01, 20 September 2014 (UTC)
DCDuring is right that "temporal adverbs" is a lot more common than "punctual adverbs". The latter phrase gets only 50 non-redundant raw Google hits, and 47 Google Books hits; the former phrase gets at least 43 pages of Google Books hits (43x10 = 430 hits) before the hits stop actually containing the phrase. "Temporal location adverbs" is the least common of the bunch, getting only 6 Books hits, and it's a moronic / oxymoronic name, because it states that the adverbs refer to places, which they do not. So the question is whether it's sufficient to relabel these as "temporal adverbs", or necessary to give them the narrower label "punctual adverbs"? Are there enough of them that the narrow categorization is necessary? Is the narrow label one people will understand? - -sche (discuss) 22:00, 20 September 2014 (UTC)
Well, as it is now, we have Category:English time adverbs, but it's a parent category to various other types of adverbs with an aspect of time. The adverbs in question here are just one type. So it wouldn't make so much sense to have "temporal adverbs" as a subcategory of "time adverbs". But it also wouldn't make much sense to have "frequency adverbs" as a subcategory of "temporal adverbs" if the latter is meant to indicate points in time specifically. —CodeCat 17:05, 23 September 2014 (UTC)


This poorly maintained category should be combined with Category:Taxonomy. The poor maintenance arises from the overlap conceptually as well as the poor choice of name for this category. In addition, for some undocumented and unfathomable reason Category:Taxonomy was made a subcategory of Category:Systematics. I think this is symptomatic of the unmaintainablity of the category. DCDuring TALK 19:14, 20 September 2014 (UTC)

Support. —CodeCat 20:25, 20 September 2014 (UTC)
I'm not sure if we should merge the two. In the English categories, at least, the members seem to be correctly apportioned between the two, with a handful of exceptions. I do think they should be made sister categories, rather than one being under the other. Chuck Entz (talk) 20:30, 20 September 2014 (UTC)
I would support that too. —CodeCat 20:46, 20 September 2014 (UTC)
What are the criteria that distinguish membership in the categories? Many dictionaries have them as synonyms in one or more of the variously defined senses and subsenses, two of which BTW systematics lacks. DCDuring TALK 13:53, 23 September 2014 (UTC)


This is not a citations page but a full entry with etymology, pronunciation, a headword line and a definition line. It should be moved to the appendix namespace. — Ungoliant (falai) 19:01, 29 September 2014 (UTC)

Definitely. Appendix:English ghost words? Or Appendix:English dictionary-only terms/zzxjoanw? Renard Migrant (talk) 17:55, 30 October 2014 (UTC)
Appendix:English dictionary-only terms/zzxjoanw sounds good. Appendix:English ghost words would become too crowded if more words were added. — Ungoliant (falai) 18:05, 30 October 2014 (UTC)

Wiktionary:Requested entries (Japanese) and Wiktionary:Requested entries:Japanese/Non-romaji[edit]

Both pages do the same thing - request new Japanese entries Wiktionary:Requested entries (Japanese) and Wiktionary:Requested entries:Japanese/Non-romaji. The latter should be removed, IMO but the former has a lot of rubbish - rōmaji entries or English entries derived from Japanese. I suggest to disallow rōmaji entry requests. --Anatoli T. (обсудить/вклад) 05:49, 30 September 2014 (UTC)

The romaji on the Wiktionary:Requested entries (Japanese) page is there by design and intent -- users who cannot read or write Japanese might still have a valid reason for wanting to request entry creation, and romaji (i.e. the Latin alphabet) is the only script that we can safely assume that our users can read and write. As such, I must disagree with your request to disallow romaji requests.
I also noticed that you added an RFC to the Wiktionary:Requested entries (Japanese) page, apparently as an objection to the presence of romaji. I could certainly support a general call to clean up the request page in general, but the presence of romaji alone is not sufficient reason for an RFC. ‑‑ Eiríkr Útlendi │ Tala við mig 00:55, 17 October 2014 (UTC)

October 2014[edit]


Should be: -trix

While -or does seem to be a real agent suffix, -rix doesn't really exist. As it turns out, the main masculine agent suffix in Latin is -tor, and -trix is the feminine counterpart. As far as I can tell, there are no Latin agent nouns that end in -rix except those ending in -trix. That's why the Latin section at -rix was moved to -trix some time ago.

For those who might think that English is different, look at the dozens of derived terms in the -rix entry, and in Category:English words suffixed with -rix, and you will be struck by an amazing "coincidence": the last letter before the "suffix" is always "t". Chuck Entz (talk) 06:17, 16 October 2014 (UTC)

What about ambassadrix, toreadrix, and vendrix? — I.S.M.E.T.A. 20:58, 16 October 2014 (UTC)
I did miss those, but do three rare words (I doubt the last two even meet CFI) disprove the overwhelming pattern shown by everything else? I would call those modification by analogy with the all the -trix forms, which may well result in eventual reanalysis of -trix into t + -rix if the whole class of feminine agent nouns don't disappear first.
Well, those three formations are undeniably formed with -rix; but can you show me any that were undeniably formed with -trix in English (they have to be terms that definitely weren't borrowed, and in which the t was not part of the word to which the -trix was suffixed)? — I.S.M.E.T.A. 17:42, 13 January 2015 (UTC)
No foolin' about Latin, Chuck? I always assumed that, in Latin, the "t" was from the past participle. But this Lewis and Short search shows that past participles with stems ending in "s" form a female agent word by adding "-trix" to the stem, even when "-or" forms the male agent. DCDuring TALK 21:47, 16 October 2014 (UTC)
That's because the cluster -sr- is not allowed by Latin. The -t- could simply be considered an epenthetic consonant. —CodeCat 23:28, 16 October 2014 (UTC)
I thought about that too, but -sr- becomes -br- in Latin (funebris < *funesris), not -str-. —Aɴɢʀ (talk) 06:02, 17 October 2014 (UTC)
It's probably more correct to say that -tor (originally -tōr, as still in the noun stem) is originally a PIE-derived agentive suffix which is added to the same weak grade of verb as the past participle, hence it was reanalyzed as past participle + -or. This would mean that -trix is a real ending, formed from the weak grade of -tōr (-tr) + feminine ending -īk-. This would mean that the original formation would have either *-strīk- (added to a root ending in -s) or *-ttrīk- (added to a root ending in -d or -t). Unclear what the resolution of *-ttr- is in Latin but *-str- is a possibility. Even if the regular resolution is *-br-, that would have been reformed by analogy to something like *-str-; extensive analogy has applied to Latin morphology at various stages. Benwing (talk) 07:06, 17 October 2014 (UTC)
Exactly. Strange things tend to happen to dental stops in Latin around other dental stops and/or s. I think there's no question that -tor/-sor is the main source for Latin agent nouns ending in -or, including many with no explicit t, and that -trix is its feminine form. The PIE pedigree for these forms is quite solid- this isn't something I just dreamed up (see *-tōr and *-tḗr). Chuck Entz (talk) 08:13, 17 October 2014 (UTC)
The affricate -ts-, which resulted from PIE -tˢt- and -ts-, was preserved at least into post-Proto-Italic times, because different Italic languages have different outcomes of final -ns, -nts and -nt (see w:Proto-Italic). Furthermore, the combination -sr- was really -zr- (like in *swezrīnos), so there was no danger of merging. I suppose it's possible that -tsr- > -str- is a regular development, but it's also possible that the split dates to post-PIE, with -tˢt- > -ts- normally but -tˢtr- developing to -str- rather than -tsr-. —CodeCat 13:16, 17 October 2014 (UTC)

Merge Template:conjugation of into Template:inflection of[edit]

The only difference between these templates is the grammar abbreviation tags they support. Everything else is the same. But there is no conflict between the tags of one versus the other, so we could very easily merge them. Afterwards, Template:conjugation of would become a redirect, and we would encourage users to use only Template:inflection of (because its name is more universal if nothing else). —CodeCat 01:33, 23 October 2014 (UTC)

Seems sensible. Support merging. — I.S.M.E.T.A. 14:02, 23 October 2014 (UTC)
Sure why not. Keφr 06:32, 24 October 2014 (UTC)
I've started renaming now. —CodeCat 17:45, 30 October 2014 (UTC)
Support (as long as nothing gets broken, which of course, shouldn't happen). Renard Migrant (talk) 17:50, 30 October 2014 (UTC)
  • Oppose: Conjugation is the more prevalent term. Purplebackpack89 14:21, 2 November 2014 (UTC)
    • Not for nouns and adjectives, it isn't. —Aɴɢʀ (talk) 16:15, 2 November 2014 (UTC)
      • Then use inflection for those and keep conjugation for verbs. Purplebackpack89 16:28, 2 November 2014 (UTC)
        • Why? —CodeCat 16:40, 2 November 2014 (UTC)
Everybody has been doing just fine with using {{inflection of}} for nouns, even though the "more prevalent term" for that is declension. Besides, you can still use {{conjugation of}}, since it will be a redirect and {{inflection of}} should be completely backwards-compatible with {{conjugation of}}. There are actually a number of languages where the tidy distinction between nouns and verbs gets blurred: participles are verb forms with many of the characteristics of nouns, and there are languages with affixes that add pronouns to verbs and verb-specific qualities to nouns. There have been several occasions where I wished I could use the abbreviations for both templates on the same form. Chuck Entz (talk) 16:45, 2 November 2014 (UTC)
Participles can be nounal? Our entry at participle says they can, but I always thought of participles as either adjectival or adverbial. w:Participle seems to agree with me. English -ing form is called a participle and can act as a noun of course, but I consider that a coincidence. Keφr 16:55, 2 November 2014 (UTC)
Yes, Kephir, they can be nounal. It's adverbial I'd question. Purplebackpack89 17:42, 2 November 2014 (UTC)
"He went down kicking and screaming." —CodeCat 17:44, 2 November 2014 (UTC)
I'd say that's adjectival: it's describing him, not the manner in which he went down. It's like "He went shopping hungry". And participles can be turned into adjectives by adding -ly, just like adjectives (e.g. swimmingly). —Aɴɢʀ (talk) 18:09, 2 November 2014 (UTC)
I could argue that the adjective hungry is being used adverbially here: both these examples can be thought of as ellipsis of "while". Though it also reminds me of how good and well are sometimes used interchangeably, which I think cannot be explained away in such terms. Keφr 18:35, 3 November 2014 (UTC)
It's elliptical for "He went shopping while he was hungry", i.e. a predicative adjective. It's not "He went shopping in a hungry manner". —Aɴɢʀ (talk) 19:32, 3 November 2014 (UTC)
Show me a nounal participle in any language. Like I wrote, I do not consider gerunds to be participles. Keφr 18:35, 3 November 2014 (UTC)
Well, I do. Also, consider the word "happening", which can be used a noun, adjective, or verb Purplebackpack89 18:55, 3 November 2014 (UTC)
I happen not to value your opinions very highly. I was asking people with some backgrounds with linguistics (of which there are a few here) whether my intuition of what constitutes a participle agrees with professional use. Keφr 20:09, 3 November 2014 (UTC)
The only nominal uses of a participle I can think of are in languages like German where almost any adjective can be used substantively, e.g. Mitreisender (fellow traveler). And participles and gerunds are two entirely different thing, and it's just an accident of history that English present participles and gerunds happen to have the same form. —Aɴɢʀ (talk) 21:03, 3 November 2014 (UTC)
  • I'm surprised no one brought up past participles -- those are much more commonly used in English as nominals, such as the lost, the disappeared, the blessed, etc. ‑‑ Eiríkr Útlendi │ Tala við mig 18:20, 24 November 2014 (UTC)
    • That's just the nominal use of an adjective, it's the same as the green, the elderly etc. —CodeCat 18:22, 24 November 2014 (UTC)

Merged some time ago. Keφr 13:58, 3 January 2015 (UTC)

Khanty words with /ɬ/[edit]

Requesting a move of a dozen Khanty words:

These have /ɬ/, which is however written ӆ and not ԓ (this is instead, I believe, /ɭ/). Quite a few current entries are sourced from a dictionary (Kononova 2002) which uses a rather ԓ-like but regardless clearly el-with-tail glyph. --Tropylium (talk) 13:24, 19 November 2014 (UTC)

(Listed here in case anyone wants to argue that ԓ for /ɬ/ is actually a competing dialectal standard that should have precedence. --Tropylium (talk))
I think you are mostly going to talk to yourself in this section. Move, if Tropylium says so. --Vahag (talk) 14:23, 19 November 2014 (UTC)
I would say just go ahead and move them yourself. Unless there's a chance that other languages will have terms using the original spellings, the redirects that you leave will actually be useful for those who make the same mistake when searching. Given the similarity of the characters, I have a hunch scannos from online books might be a major source of these. Chuck Entz (talk) 14:38, 19 November 2014 (UTC)
According to Wikipedia, w:Khanty language uses both letters (Ӆ ӆ and Ԓ ԓ). Are you certain that these particular words are spelled with Ӆ ӆ? —Stephen (Talk) 15:04, 19 November 2014 (UTC)


Move to admiraless. A common noun. Most of the citations are capitalized as an honorific, proper noun, or part of a title. See how many of these [a]dmiralesses are accompanied by capitalized [a]dmirals. Michael Z. 2014-11-24 02:26 z

It would not be easy to attest admiraless as a common noun. The only use I found searching Books for "an admiraless" or "admiralesses" was:
  • 1907, Weymer Jay Mills, The Van Rensselaers of Old Manhattan: A Romance, page 60:
    The master wants to marry me —— he's sending me a suitor. Me, Toscin — who's been but five days in York. And the man's an Admiral—Admiral Pouffton. Oh, heavens! what a rare show I'd be as an admiraless!
Perhaps singular determiners would lead to more. DCDuring TALK 02:41, 24 November 2014 (UTC)
Why don't we just move? It's not a proper noun. --Anatoli T. (обсудить/вклад) 02:47, 24 November 2014 (UTC)
Evidence? DCDuring TALK 05:18, 24 November 2014 (UTC)
User: DCDuring There are no citations of [a|A]dmiraless as a proper noun.
Citations for admiraless 1719 and 1959 have lowercase initial. Citation 1894 is set in title case as part of an article title. Citations 1887, 1899, 1907, 1908, 1909, 1911, and 1983 are common-noun uses with capitalized initial as a matter writing style, where a noun corresponding to an honorific is capitalized, in an archaic or quaint way that modern style guides eschew. (In citations 1898, 1992, and 1993, and possibly 1983, the common noun is styled with initial cap as part of an honorific title, however this is also usage, and we do not define such a title as inherently capitalized nor as a proper noun, e.g. Admiral#English, General#English, Lance Corporal#English, Professor#English, Minister#English, Constable#English, Director#English, &c.) Michael Z. 2014-11-24 15:32 z
I accept the 1907 cite above and the 1959 cite, preceded as they are by the indefinite article. The 1719 cite seems good on semantic grounds.
But I dispute that there are not cites of Admiraless as a proper noun. A proper noun is not the same as a proper name. In several of the cases, Admiraless stands alone as a proper name of an individual. In most of the others it is a component of a proper name. In this behavior it is similar to English given names, which we present as proper nouns. I can't defend not classifying as proper nouns all titles that can be used both standalone referencing an individual and as part of a longer proper name.
As a matter of policy, I don't think that we should reason by declaring without evidence that the word to be in a word class (ie, "like" other words) and then argue from the behavior of the words in the class. For all seven of the terms in the list with which you close your comments, it is quite easy to attest to their use with the indefinite article and in the plural, probably in both upper and lower case. We did not have sufficient evidence on Admiraless when this RfV began. Admiraless could have belonged in a class of proper nouns that are not attestably ever used as common nouns and are only used to construct honorific proper names and, standing alone, as abbreviated references to the person so honored. DCDuring TALK 17:50, 24 November 2014 (UTC)
Well, now we also have 1927, a third clear citation supporting a move to l.c. common-noun entry.
I suggest we agree to move the entry, and we can discuss the merits of adding proper-noun senses for this and similar terms (President#English does exist).
I can’t agree that “Admiraless stands alone as a proper name of an individual.” It is no more a proper noun, or like a given name, than any other common noun used with the definite article: “the admiral,” “the poodle,” “the delicious Sunday breakfast,” or “the hammer I was using.” (To be fair, I have never heard a convincing argument that proper nouns are a class of word rather than a kind of usage of practically any noun.)
And I understand your point about policy, but we should not also jump to unreasonably complicated conclusions from simple absence of direct evidence for simple ones. After all, the word is formed with -ess, and no citation attests that admiraless is anything but the female counterpart of admiral. Several citations support this view with parallel constructions like the “Admiral and Admiraless,” or explanations like “honorary position of an admiral.” Michael Z. 2014-11-24 19:07 z
everything should be made as simple as possible but not simpler. We do not actually have three cites for either the "wife of an admiral sense" or the "female admiral" sense as a common noun. The "wife of an admiral" sense is not the female counterpart of an admiral. The truly simplest resolution would be to drop the common noun sense altogether, except for the citations.
I'd like to hear from someone else on this. DCDuring TALK 19:36, 24 November 2014 (UTC)
“Female counterpart of [the term] admiral” is a simpler, non-gloss, definition that encompasses both “female admiral” and “wife of an admiral.” Michael Z. 2014-11-24 19:52 z
Under which MWOnline definition of counterpart?
1 one of two corresponding copies of a legal instrument: duplicate
2   a: a thing that fits another perfectly
b: something that completes: complement
3   a: one remarkably similar to another
b: one having the same function or characteristics as another
college presidents and their counterparts in business
Feel free to find definitions from any (non-wiki) source, of course. DCDuring TALK 22:38, 24 November 2014 (UTC)
If that were true, then the husband of the person referred to in the "female admiral" sense would be an admiral. Chuck Entz (talk) 03:15, 25 November 2014 (UTC)
Counterpart in the same old-fashioned way that Mrs. John Smith is the female counterpart of her husband. I am not suggesting that that is the best definition for Wiktionary, but it is a simple explanation of the term. Incidentally, OED (2011) defines this term with a single sense that includes the meanings wife of an admiral and female admiral. Perhaps this understanding of it also assumes that the office, position, title, or rank of admiralcy is not exactly just a person. Michael Z. 2014-11-27 21:22 z

it does exactly what it says on the tin[edit]

Move to: do exactly what it says on the tin.

The single citation doesn't actually fit the pattern, since it apparently uses a noun in place of the first "it". But more importantly, "do exactly what it says on the tin", "doing exactly what it says on the tin" and "did exactly what it said on the tin" are all citable (as is the grammatically inconsistent but still logical "did exactly what it says on the tin"). This should be a verb, not a phrase, and the 'it' needs to go. Smurrayinchester (talk) 14:12, 26 November 2014 (UTC)

Shouldn't it be even briefer: what it says on the tin, with redirects from and usage examples of the most common extended variations? Just alternates with exactly and neither is essential in use. BTW, the expression is surprisingly recent, apparently with 99% of the Google Books usage being after 2000. And substituting 'can' for 'tin' does not lead to clear examples of idiomatic usage. DCDuring TALK 14:43, 26 November 2014 (UTC)
One can also find "more or less", "pretty much", etc as qualifiers and what it says on the tin as object of verbs like deliver and as part of a predicate with forms of be. In whatever form the phrase gained its initial popularity, what speakers find peripheral seems to have been discarded or substituted for in a significant portion of usage. Also, it can be found in the past tense: "Many funds proved unable to do what it said on the tin: they could not hedge effectively against volatile markets." (about 'hedge funds') DCDuring TALK 15:41, 26 November 2014 (UTC)
That would also be a good solution, although the noun is a bit more nebulous to define (as with way out of a paper bag - while I understand why the noun was split off, the definition is quite weird since people think of it as a construction, not a verb + noun phrase). The recentness is not a surprise - the Ronseal adverts that coined the phrase only started in the late 90s. Also unsurprising is the fact that it appears to be about twice as common in UK writing than US writing according to Google Ngrams, and even more UK dominant from a random sample from Google books. Smurrayinchester (talk) 16:08, 26 November 2014 (UTC)
There two kinds of definitions: gloss and non-gloss.
  1. A gloss might be: "the performance or characteristics implied by a label or name, especially for something whose characteristics cannot be otherwise immediately determined, as an item for sale in concealing packaging"
  2. A non-gloss might be: "Used in expressions that indicate that something is what it appears to be or performs as promised."
Improvements and/or suggestions welcome. DCDuring TALK 20:18, 26 November 2014 (UTC)
The words on the Ronseal tin that are legible in the YouTube are: "Ronseal Decking Stain". Doesn't it seem odd that there should be possible multiple interpretations other than that intended, eg, 1., that Ronseal stains ("soils") decks; 2., that Ronseal is a stain that decks ("knocks down") (say, the person applying it, as due to toxicity of fumes). DCDuring TALK 20:38, 26 November 2014 (UTC)
It's often shortened to "as it says on the tin". Donnanz (talk) 13:27, 15 December 2014 (UTC)


I can't decide whether to move un drôle de to well, un drôle de or to somehow define it as an adjective and move it back into the adjective section. However, it can't stay as it is. Renard Migrant (talk) 17:09, 7 December 2014 (UTC)

Category:Dance and Category:Dances[edit]

Can these two categories be merged? It can be a problem deciding which one to use, or whether to select both. Donnanz (talk) 09:21, 15 December 2014 (UTC)

For some reason we have a bias toward toward using plurals of countable nouns in Category names. Clearly there are words connected with dance that are not dances. DCDuring TALK 13:49, 15 December 2014 (UTC)
In this case having Category:Dances as a subcategory of Category:Dance seems fine to me. DCDuring TALK 15:07, 15 December 2014 (UTC)
Hmm, I'm not happy with that, it just adds needless complexity. I will use just Category:Dance for Bokmål and Nynorsk. Donnanz (talk) 15:29, 15 December 2014 (UTC)
Terms for actual dances should go in Category:Dances. —CodeCat 19:32, 26 December 2014 (UTC)
I feel that in some languages where there are few entries (at present) that can go into either category it is better to list them all under one category (Dance). Or maybe there should be a more comprehensive category named "Dancing", replacing both "Dance" and "Dances". Donnanz (talk) 13:01, 29 December 2014 (UTC)
Nobody is going to go back when there are more entries, and recategorise them all. So they should be put in the category where they should eventually be, right from the start. —CodeCat 13:55, 29 December 2014 (UTC)
It shouldn't be a problem to change the category if necessary. I'll do it my way - Frank Sinatra-style. Donnanz (talk) 14:28, 29 December 2014 (UTC)

Help:Interacting with humans[edit]

Not an RFM as such, but I figured I should bring up that User:Type56op9 moved Help:Interacting with humans to Help:Interacting with other users -- not a change I disagree with as such, but it was made without any regard to policy. ObsequiousNewt (ἔβαζα|ἐτλέλεσα) 21:17, 22 December 2014 (UTC)

What policy in particular do you feel was ignored? —Aɴɢʀ (talk) 21:54, 22 December 2014 (UTC)
I... probably shouldn't speak to policy. There wasn't any discussion I could see though, aside from a comment by Mglovesfun on the talk page five years ago. ObsequiousNewt (ἔβαζα|ἐτλέλεσα) 17:20, 23 December 2014 (UTC)


Lewis and Short do not have this. They have satin'. If you think this should be RfVed, I would not object. DCDuring TALK 19:29, 26 December 2014 (UTC)

I doubt an RFV will be helpful here. The original manuscripts will definitely not have an apostrophe on this word; modern editions may or may not depending on the editor's preference. —Aɴɢʀ (talk) 20:30, 26 December 2014 (UTC)

Happy New Year[edit]

Happy new year

January 2015[edit]

Request to transfer a page from Wikipedia[edit]

Since I am not qualified to do so, could someone please transfer this page/word to the wiktionary? Ineuw (talk) 06:58, 9 January 2015 (UTC)

@Ineuw: Sorry for the late response. Since Wiktionary already has an entry on scalenohedron (and our entry in fact seems to be more detailed than WP's), I would just delete the WP entry at this point, possibly expanding the Wiktionary entry if the WP entry is correct that the shape doesn't have to have twelve sides. - -sche (discuss) 02:25, 22 January 2015 (UTC)

Category:Probability, Category:Probability theory and Category:Statistics[edit]

The terminology of probability theory and statistics overlaps so much that there is little point in maintaining the two disciplines as separate topical categories.

I also cannot see the point of maintaining Category:Probability separately from Category:Probability theory — unless it is meant to contain terms used in informal discussions of probability (as opposed to mathematical formalisation thereof).

Also, Category:Linear algebra and Category:Vector algebra are one and the same. I would suggest deleting the latter, except I am too lazy to do a separate nomination for those.

Asking Msh210 to weigh in, just in case. Keφr 19:10, 21 January 2015 (UTC)

As far as I'm aware, w:vector algebra, q.v., and linear algebra are identical. Probability theory is a far cry, to my mind, from statistics. In particular, their uses are different: lots and lots of people use statistics, and the words that are relevant to statistics, without knowing or caring anything about probability theory. Perhaps one topcat for statistics and applied probability and another for probability theory? But they'll share quite a few words. Perhaps instead one for statistics and one for probability? They, too, will share quite a few words. So I don't know the best course of action. Maybe we should keep the three categories we have now, but rename "Probability" to "Applied probability". If we do decide to have separate topcats for applied probability and for probability theory, then perhaps merge the latter into category:Measure theory?​—msh210 (talk) 03:35, 25 January 2015 (UTC)

Merge appendix:proto-germanic/wisundaz to appendix:proto-germanic/wisundz[edit]

Most sources I found seem to reconstruct this word as a consonant stem (See talk page for *wisundaz before moving.) Some information regarding the etymology of the word may need to be looked over more (Not all the sources on the talk page agree on the etymology of this word.).Nayrb Rellimer (talk) 07:47, 24 January 2015 (UTC)

Move *kelþą to *kelþaz[edit]

Orel 2003 pg. 212 reconstructs *kelþaz as the proto-form. The z-stem reflex of the noun survives into Modern English even to the present day. Note that already a discussion has started on the talk page for *kelþą about there being two conflicting entries for the same word.Nayrb Rellimer (talk) 08:03, 24 January 2015 (UTC)