Hello, you have come here looking for the meaning of the word Wiktionary:Requests for moves, mergers and splits. In DICTIOUS you will not only get to know all the dictionary meanings for the word Wiktionary:Requests for moves, mergers and splits, but we will also tell you about its etymology, its characteristics and you will know how to say Wiktionary:Requests for moves, mergers and splits in singular and plural. Everything you need to know about the word Wiktionary:Requests for moves, mergers and splits you have here. The definition of the word Wiktionary:Requests for moves, mergers and splits will help you to be more precise and correct when speaking or writing your texts. Knowing the definition ofWiktionary:Requests for moves, mergers and splits, as well as those of other words, enriches your vocabulary and provides you with more and better linguistic resources.
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.
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}}.
Note that discussions for splitting, merging, and renaming languages, once held here, are now held at WT:Language treatment requests.
I'm a little confused about what's going on here. Are you RFV-ing every entry in this category? Or are you just looking for evidence that Khitan was written using this script? —Mr. Granger (talk • contribs) 12:45, 13 August 2016 (UTC)Reply
I understand that, but I don't understand what your goal is with this discussion. If you want to RFV every entry in the category, then I'd like to add {{rfv}} tags to alert anyone watching the entries. If you want to discuss what writing systems Khitan used, maybe with the goal of moving all of these entries to different titles, then I'm not sure RFV is the right place for the discussion. (Likewise with the Buyeo section below.) —Mr. Granger (talk • contribs) 17:55, 13 September 2016 (UTC)Reply
{{jiajie}} should be merged with {{liushu}}, which could be renamed as {{Han liushu}}, following {{Han compound}} and {{Han etym}}. It might not be a good idea to use a particular language code because these templates are intended for use in multiple languages now. They used to be used under Translingual, but we have decided to move the glyph origin to their respective languages. — justin(r)leung{ (t...) | c=› }20:22, 17 May 2017 (UTC)Reply
Support merging {{jiajie}} with {{liushu}}, this template only has a few uses and would be trivial to replace, I'm not sure why this discussion died out. The jiajie template does have functionality liushu is missing (e.g. at 云, where all the extra text produced by jiajie there is absent in liushu) though, but that also shouldn't be hard to add. - saph ^_^⠀talk⠀14:42, 3 February 2025 (UTC)Reply
Latest comment: 1 year ago5 comments2 people in discussion
sense: Noun: "(aviation) A large multi-engined aircraft.
The term heavy normally follows the call-sign when used by air traffic controllers."
In the aviation usage AA21 heavy ("American Airline flight 21 heavy") the head of the NP is AA21, heavy being a qualifying adjective indicating a "wide-bodied", ergo "heavy", aircraft.
I don't know what I meant 5 years ago, but that's what I mean now: move it to adjective. Though it would be good to confirm that there is not sufficient attestation of heavies and/or heavy. DCDuring (talk) 12:48, 18 October 2022 (UTC)Reply
I can find the plural in reference to large (sometimes restricted to widebody) commercial aircraft and heavy bombers (sometimes 2-engine, always at least 4-). Also "heavy" motor vehicles (eg. large trucks, esp semis). I'm not entirely sure what heavy refers to when used by the pilot of a Cessna. DCDuring (talk) 12:57, 18 October 2022 (UTC)Reply
Entries for Japanese prefecture names that end in 県(ken, “prefecture”)
Latest comment: 7 years ago11 comments6 people in discussion
I would like to request the move of the content of entries like 茨城県(Ibaraki-ken, literally “Ibaraki prefecture”) to simply 茨城(Ibaraki, “Ibaraki”), cf. Daijisen. 県 is not an essential part of the name.
(edit conflict) It seems like a two-word phrase to me. I am not a native speaker, but I think that if someone asked "水戸市は何県？" ((in) What prefecture is Mito?) then "茨城です。" (It's Ibaraki) would be a correct answer. Entries such as 奈良 and 広島 should have both the city and the prefecture. (I see that 奈良 currently does.) Cnilep (talk) 04:01, 19 April 2018 (UTC)Reply
Yes, 茨城県 is also correct. And if someone asked どこの出身？ (Where are you from?) the answer would probably be 奈良県 rather than 奈良, or else expect a follow-up question. But I don't think that is necessarily a matter of word boundaries. Compare Pittsburgh, Pennsylvania and Pittsburgh, Kansas; the fact that it is usually necessary, and always acceptable to specify the latter doesn't mean that Pittsburgh on its own is not a proper noun. By same token, I think that 茨城 (et alia) is a word. That's the point I had in mind. I will say nothing about what is more common. I don't even have good intuitions about frequency in my native language. Cnilep (talk) 04:54, 19 April 2018 (UTC)Reply
A lot (maybe all?) of the prefecture names minus the 県(-ken) suffix are polysemous. Listing a few from the north to the south, limiting just to geographical senses, and just in the same regions at that:
Generally support. Less duplication is good, and it is not much different from Chinese etc. for which we generally delemmatise, if not completely hard-redirect, these forms. Wyang (talk) 04:49, 19 April 2018 (UTC)Reply
Support. For a dictionary, I think we don't need to keep entries with both prefecture name and prefecture, despite the usage but it's always helpful to provide usage notes (e.g. normally used with 県: ~県) and usage examples, e.g. 奈良県(Nara ken, “Nara (prefecture)”). --Anatoli T.(обсудить/вклад)05:45, 19 April 2018 (UTC)Reply
Mecayapan Nahuatl saltillos
Latest comment: 1 year ago4 comments3 people in discussion
A number of Mecayapan Nahuatl words are currently written with U+0027 APOSTROPHE, which is a punctuation mark and not a letter. And a couple are using U+02BC MODIFIER LETTER APOSTROPHE, which is the wrong shape for this language. They should all be written with U+A78C LATIN SMALL LETTER SALTILLO instead.
Latest comment: 3 months ago32 comments15 people in discussion
Some years ago, there was an RFM to rename all these pages, the discussion of which is archived at Wiktionary talk:English entry guidelines#RFM discussion: November 2015–August 2018. The original nomination mentions "and likewise for other languages", meaning that the intent was to rename these pages in parallel for every language. In the end, only the English page was moved, so that now the English page has a name different from all the others. User:Sgconlaw suggested starting a new discussion instead of moving the pages after the RFM has long been closed.
My own opinion on this is to rename the pages in other languages to match the English one. That was the original intent of the first RFM, and the new name better describes what these pages are for. The name "about" instead suggests something like a Wikipedia page where you can write any interesting fact about the language, which is of course not what they're actually for. Some discussion may be needed regarding the shortcuts of all these pages. They currently follow the format of WT:A(language code), so e.g. WT:AEN but also WT:ACEL-BRY with hyphens in the name. The original shortcuts should probably be kept, at least for a while, but we may want to think of something to match the new page name as well. —Rua (mew) 13:00, 29 April 2019 (UTC)Reply
@Metaknowledge FYI, this may take a little while. Lots of these pages have redirects to them and MediaWiki doesn't handle double redirects, so I have to find all the links to these pages (at least, those in redirects) and fix them. Benwing2 (talk) 01:19, 29 March 2021 (UTC)Reply
@Benwing2: 1. I don't think we need the word "languages". 2. The second option sounds more grammatically correct. 3 & 4. I would go with subpages, but you may want to hold off on those, as some of the pages are heavily used and links to them will have to be fixed. Opinions solicited: @Justinrleung, suzukaze-c, Atitarev, Tibidibi 5. It should be moved somewhere very inconspicuous; we could even delete it and nobody would miss it. 6. I guess the former? 7. The first one is now fine, the second can stay where it is, and the third seems somewhat useless (but @-sche may have an opinion). —Μετάknowledgediscuss/deeds02:29, 29 March 2021 (UTC)Reply
I think there's nothing on Wiktionary:About Algonquian languages that requires that page to exist, anyway, and am just going to make it a hard redirect it to the About Proto-Alg. page instead of the soft redirect which is currently its entire contents, keeping the old edit history and old talk page comments. - -sche(discuss)18:58, 26 July 2021 (UTC)Reply
Support in general. The "About" in titles is confusing per OP. I have no feedback on the trickier cases (language family, subpages, script, etc. listed by Benwing) but suggestions above sound sensible. The few edge cases should not be a blocker to moving the clear cases. Hftf (talk) 06:19, 20 February 2025 (UTC)Reply
@Globins Wiktionary's category structure only follows the first definition, which is the more common meaning. We shouldn't mix up the two definitions. —Rua (mew) 17:52, 13 May 2019 (UTC)Reply
Not really. An eponym is derived from a name. A toponym is a name. So a term derived from a toponym is derived from a name, but a term derived from an eponym is derived from another word that is then derived from a name. They're not equivalent. —Rua (mew) 21:18, 14 May 2019 (UTC)Reply
I think "eponymic terms" would be better if you want to preserve the "name that a term is derived from" sense of eponym (as opposed to the "term derived from a name" sense). "Terms derived from eponyms" seems odd, maybe tautological, to me because a name is not inherently an eponym, but only when we are discussing the fact that a term is derived from it. — Eru·tuon21:35, 14 May 2019 (UTC)Reply
As I see it, have isn't part of the metaphor, but it is part of an expression that is not in turn a form of tie someone's hands. The passive (one's) hands are/were/being/been tied are such forms, though none make for a good lemma entry or likely searches. DCDuring (talk) 13:38, 25 June 2019 (UTC)Reply
Indeed. Unless the active form is very uncommon, I'd prefer it as the lemma. I don't think that we would be wrong have both the active-voice expression and the have and/or get expressions, even though we could argue that it is a matter of grammar that one can transform certain expressions in the way Lambian describes. DCDuring (talk) 22:31, 25 June 2019 (UTC)Reply
I was going to redirect this to the active form per the discussion above, but I notice it has interesting translations, and so perhaps a case for existing as a THUB. - -sche(discuss)22:32, 23 July 2025 (UTC)Reply
January 2020
'Cities in Foo' and 'Towns in Foo'
Latest comment: 4 years ago8 comments7 people in discussion
@Donnanz, Fay Freak, Rua I'm not sure what the real difference is between a city and a town, and I suspect most people don't know either. For this reason I think we should maybe merge the two into a single 'Cities and towns in Foo' category. Benwing2 (talk) 03:54, 17 January 2020 (UTC)Reply
I oppose this merger. I would not think to look for a category with such an unintuitive name, and I do not know of any examples where this is problematic. Wikipedia seems to be able to choose which word to use without trouble, so why can't we? —Μετάknowledgediscuss/deeds05:36, 17 January 2020 (UTC)Reply
Eliminating one of them is a good idea where there is no meaningful distinction between cities and towns. But that's going to be a country-specific decision: England makes the decision, the Netherlands does not. I think in cases without a distinction, we should keep "cities" and eliminate "towns". —Rua (mew) 10:15, 17 January 2020 (UTC)Reply
I wouldn't recommend merging them. It's a complex subject though, and the rules defining cities and towns can differ from country to country, and from state to state in the USA; I have come across "cities" with a population of less than 1,000 in the USA, sometimes around 50, but apparently they have that status. Cities in the UK have that status as granted by a monarch, towns can be harder to define in metropolitan areas, and villages can call themselves towns if they have a town council. Some villages large enough to be towns prefer to keep the village title. DonnanZ (talk) 10:34, 17 January 2020 (UTC)Reply
The odds that editors will accurately/consistently distinguish these categories when adding (the template that generate) them ... seems low. However, even if the categories are merged, that problem will remain on the level of the displayed definitions. And, apparently some users above want to keep them distinct. So, meh. - -sche(discuss)05:36, 18 January 2020 (UTC)Reply
I can see arguments for both sides, actually. The idea needs a lot more thought, as you would probably have to drag in villages etc. as well. DonnanZ (talk) 14:15, 19 January 2020 (UTC)Reply
Could merge them into Municipalities in Foo and have the various alternatives point to that category. Of course there are some "cities" which contain several municipalities, but I don't think there is a word which comprises every form of village/town/hamlet/city/urban area. - TheDaveRoss12:47, 21 January 2020 (UTC)Reply
In New York State alone, we have cities, towns, villages (which are subdivisions of towns), and unincorporated places, all of which exist within counties, except NY City, which is coextensive with 5 counties, each of which is coextensive with a borough of the City. The identities and borders of these places in NYS are generally fairly stable, though subject to occasional revision. Legislative and judicial districts are separate, with legislative districts changing after each decennial census. Census-designated places form a parallel structure with relationships to the state systems. The census system has the virtue of being uniform for the entire US, but the borders of many census places do not necessarily correspond to the borders of larger governmental units such as states and counties. Within New York State there are lists of each type of jurisdiction. In principle each US state has its own names for classes of jurisdictions. Finally, in popular practice, place names for inhabited place can differ from the names of governmental units and tend to have different boundaries even when the names are the same.
In light of the lack of homogeneity even within the US, let alone between countries, I think we need to respect national and state and provincial naming systems. If there is a worldwide system for categorizing places, we could also follow that, but I have not heard of such a system. Does the EU have some uniform system?
In the absence of any generally accepted uniform universal or near-universal system for categorizing places, I think we need to accept the fact that nations and semi-sovereign parts of nations (eg, US states, Canadian provinces) each have their own naming systems, which are accepted within their boundaries. I think it would be foolish for us to attempt to have our own system for categorizing places and derelict for us to fail to use the various national and subnational categories.
Oppose: Even though "out on a limb" can be used without "go", I think "go out on a limb" =/= "go" + "out on a limb", so I think we should keep them separate after all. — excarnateSojourner (ta·co)02:14, 7 April 2024 (UTC)Reply
In addition of all the tense, person, and number variants (also contractions) of the current entry one can find variants omitting the pronoun, adding adverbs, using till or 'til instead of until; oneself blue in the face; go|become|turn blue in the face; and blue-in-the-face and blue in the face as adjectives outside any of these expressions. The unchanging core of these is the set phrase blue in the face. It also has medical use (synonym cyanotic), which renders the figurative sense evolution and meaning obvious. DCDuring (talk) 17:39, 15 April 2020 (UTC)Reply
@Metaknowledge: I agree, and I don't think it's needed for any purpose, at least not for Azerbaijani. There was a user (or anon?) who insisted on adding those "underlying" verbs and creating templates for them, but I never understood the linguistics behind this reasoning. Allahverdi Verdizade (talk) 23:42, 8 March 2021 (UTC)Reply
Sense 3 of state should cover it. I think if 3(a) doesn't cover it, then "Never do anything against conscience even if the state demands it." is not an appropriate citation thereof; I think Einstein would consider national, state, and city governments all part of "the state".--Prosfilaes (talk) 07:04, 17 August 2020 (UTC)Reply
Latest comment: 5 months ago12 comments4 people in discussion
I wonder if these all ought to be merged into some entry akin to "play the ____ card" or something. There appear to be other words substituted aside from victim, race, and gender. Tharthan (talk) 22:09, 21 May 2020 (UTC)Reply
I lament that our way of handling snowclones is not optimal, banishing them to appendix-space, such that the choices here amount to 'have these multiple similar entries in the mainspace where users find them' or 'banish them to a tidy but less-findable appendix'. However, I see that we have a sense at card for this (although the definition could use some work), and between putting a link there and redirects from these entries, I suppose we could get by with migrating these to the snowclone appendix. Centralizing them does seem sensible since there are so many. ("Play the religion card" also exists.) - -sche(discuss)23:56, 21 May 2020 (UTC)Reply
Interesting idea. Perhaps there would be an extensive entry for play the (something) card, but with full entries for the main attestable instances (eg, race/gender and perhaps victim, derived terms, and a usage note about "(something)". Play the X card seems to be something that would be highly productive, unless its use in too many cases would be deemed a microaggression. Attestation for play the (something) card would have to be limited to "somethings" other than the forms that have their own attestation. Other instances that I can readily find are disability, oppression, and queer. The uses of feminist and bully don't fit the "victim" semantics, which might warrant a second figurative definition for play the (something) card in addition to a {{&lit}} "definition". DCDuring (talk) 15:10, 4 September 2022 (UTC)Reply
Besides those, there's "play the poverty card", "play the gay card", "play the abuse card", "play the disabled card", "play the rape card", etc., as well as ones which, as you say, seem like they may have different semantics (e.g. some uses of "play the Muslim card" in reference to legislation ?to get Muslim support?, and some uses of "play the Holocaust card"?) ... it seems too productive to have entries for every attested X (it becomes SOP). Should this be in the mainspace as play the something card, or at Appendix:Snowclones/play the X card like Appendix:Snowclones/X is the new Y? For snowclones like this that require placeholders other than "someone"/"one" in the title, we seem to in recent years prefer to put them in Appendix:Snowclones/ rather than in mainspace, but I do see a handful of mainspace titles where "something" is a placeholder, like give something a go. If we redirect all the variations people might search for, add usexes to the relevant sense we list at card, and maybe add a usex to whichever sense of play is relevant, it should be sufficiently findable. - -sche(discuss)16:48, 4 September 2022 (UTC)Reply
I'd favor having a full entry for any term (presumably they would be attestable) that another dictionary had. It is unfortunate that our basic search engine searching for "play the disabled card" (with or without quotes) does not take a user to any of our existing play the X card entries. (I have added test entries for play the card and play the something card.) That would imply that we could use hard redirects for as many attestable instances of the snow clone as seem likely to help users. It may well be that the hard redirects should go to the snowclone appendix subpages, but there is no particular reason to do so in preference to a mainspace entry. Concern about the aesthetics of headwords with a placeholders seem misplaced. And (who knows?) someone might actually search for the expression using a placeholder and find it if it were in principal namespace. DCDuring (talk) 20:27, 4 September 2022 (UTC)Reply
Also, as the MWOnline entry shows play is not strictly essential; it can be replaced by use, among other verbs, such as deploy. So, perhaps a sense of card is an appropriate target for redirects. But I doubt that the entry for card is the right place for an intelligible presentation. For one thing, any etymology (sense derivation), usage notes, and derived terms or collocations (eg, race card) would necessarily be separated from the relevant definition for the polysemous noun, so as not to appear on the same screen. And, even if they did, that they belonged together would not be at all obvious. I realize that this kind of argument, if applied, might make for some inconsistency in our presentation of snowclones and might violate a strict reading of idiomaticity, but cases like this may merit exceptional treatment. DCDuring (talk) 21:05, 4 September 2022 (UTC)Reply
Onelook finds "play the race card" and "play the gender card" in various dictionaries, but "play the victim card" only in us, and it seems unlike the others in other ways, too: card seems unnecessary, as the same meaning is expressed by play the victim. As you note, all of these can also be found with other verbs, like "use". I am inclined to redirect play the victim card to either card's relevant sense or play the something card. It has a Swedish translation; if there are others, I would think play the victim would be the better THUB location. I'm not sure what to do about play the gender card and play the race card; on one hand, each is in other Onelook dictionaries; OTOH, you can swap out "play" for "use", "gender" for other things ("sexism", "sex", "woman", and with different meaning other things like "religion", etc), it's not a set phrase and the kernel of idiomaticity is obviously some smaller part, maybe just card, not the whole phrase. - -sche(discuss)17:03, 7 September 2023 (UTC)Reply
As to card, we may need two additional definitions, one for the general metaphorical sense, another (subsense?) for the more specific sociopolitical use. As Equinox observed elsewhere, the metaphor of a competitive card game must be understood for the expression to make any sense at all.
(figuratively) A ploy of potentially advantageous use in a situation viewed as analogous to a card game.
The only card left for him to play was playing dumb.
An invocation of an emotionally or politically charged issue or symbol, as in a political competition.
Latest comment: 10 months ago5 comments5 people in discussion
I don't think this is a special phrase with "you're", it sounds like a phrasal verb be on. They want a fight? They're on! She issued a challenge, so she's on!. You can also use it in reference to the fight itself, e.g. the fight is on. 76.100.241.8918:51, 23 May 2020 (UTC)Reply
Hmm, perhaps. But the IP is right that "on" can be used with other pronouns. I suppose the question is whether this is better viewed as someone is on, be on, or just on: we already have a sense for this at on, "(informal) Destined, normally in the context of a challenge being accepted; involved, doomed. "Five bucks says the Cavs win tonight." ―"You're on!"Mike just threw coffee onto Paul's lap. It's on now." - -sche(discuss)04:25, 1 August 2020 (UTC)Reply
I have never heard the they're on or she's on examples given by OP, and the second one doesn't even fit, since it's about acceptance of a challenge. I've heard it's on, but that's slightly different. Theknightwho (talk) 02:43, 6 September 2024 (UTC)Reply
@PUC: I have no objections to the move, however, I'm not entirely sure that *vьlkodlakъ was the primary form. Semantically, it makes sense to analyze the lemma as Proto-Slavic*vьlkodolkъ = *vьlkъ(“wolf”) + *dolka(“skin”) + *-ъ with -ol- > -la- metathesis or possible *vьlkodьlakъ (less likely in view of East Slavic forms with *-olo-, e.g. Russianвурдала́к(vurdalák, “vampire”) /first recorded in written form in 18-19 cent./). You should consult with User:Rua in regard to which form should be created - *vьlkodlakъ or *vьlkodolkъ. I'm not so familiar with the style that Wiktionary likes to follows. Безименен (talk) 12:25, 10 July 2020 (UTC)Reply
If the original form had -dl-, why do we not see it in the other languages that preserve it, such as Polish? —Rua (mew) 13:25, 10 July 2020 (UTC)Reply
Not sure, but looking again at the entry, it seems not only Czech but also Serbo-Croatian and Slovene preserve the -dl- as well. --108.20.184.1916:51, 10 July 2020 (UTC)Reply
I'd bet that you couldn't come up with definitions on the merged entry that were both complete and subsitutable as both adjective and adverb in such definitions. Also I'd expect that synonyms might need to be distinguished by PoS. DCDuring (talk) 16:22, 5 January 2021 (UTC)Reply
Hmm. I think the adjective is normally all-out. The adverb seems to mostly be "all out". So it seems like each POS is best situated where it is, on its own page...? - -sche(discuss)05:14, 31 March 2024 (UTC)Reply
Latest comment: 4 years ago4 comments3 people in discussion
Not synonyms, of course, but certain senses overlap almost entirely (except people have edited one and not the other without realising). Equinox◑04:12, 14 February 2021 (UTC)Reply
An approach would be to put all and only the true definitions that are most commonly use a given spelling in that spelling and also have a definition in each saying that it is a synonym of the other spelling. That might not be exactly true, but would be close. To rely on the other term appearing in related terms seems a bit weak. DCDuring (talk) 04:19, 14 February 2021 (UTC)Reply
Yeah, I think that's what we may have to do, with glosses in the {{synonym of}}s to make clear that each entry being a {{synonym of}} the other is not (just) circular. Like egoist vs egotist (we are not the only dictionary to have a sense line defining each of those terms as the other, in addition to other definitions). - -sche(discuss)19:45, 14 February 2021 (UTC)Reply
Latest comment: 4 years ago1 comment1 person in discussion
The definitions are different (I think fight shy is better; the other is too vague) and it seems that the entries should be merged anyway. Note that fight shy can occur alone, without of. Equinox◑02:45, 12 April 2021 (UTC)Reply
In this case (spitting) it should be "someone's", because "one" spits in "someone" else's face. We use "one" where the phrase is constructed so that it happens to oneself. Equinox◑20:27, 23 May 2021 (UTC)Reply
On the other hand, it's conceivable that someone says, "How dare you spit in my face?", meaning that the person addressed has treated the speaker disrespectfully. — SGconlaw (talk) 17:44, 4 June 2021 (UTC)Reply
Ah I see now, the distinction is that one's constructions are supposed to be reflexive. The distinction in titling however is not obvious and I wish it were made clear somewhere. — 69.120.64.1503:57, 5 June 2021 (UTC)Reply
Latest comment: 4 years ago3 comments1 person in discussion
All of the other Proto-Tocharian entries so far use ⟨y⟩ for this phoneme */j/, equivalent to Adams' ⟨i̯⟩. This is also the letter used on the Wikipedia article for Proto-Tocharian and in the standard romanization of Tocharian languages, which we use, not to mention for the corresponding phoneme in PIE, *y. It would be nonsensical and confusing to use ⟨j⟩ instead for the Proto-Tocharian stage only. The page was created recently (April), so presumably its creator just forgot to check the existing entries. — 69.120.64.1503:37, 5 June 2021 (UTC)Reply
Wait, apparently there is a distinction in how Adams uses ⟨i̯⟩ versus ⟨y⟩ for Proto-Tocharian, but I have no clue what it is. (It has nothing to do with PIE *d versus *y, for instance, and nothing to do with laryngeals.) — 69.120.64.1504:18, 5 June 2021 (UTC)Reply
Ok, it seems to be non-phonemic and have to do with the following vowel. */jä/ (⟨ä⟩ ≈ IPA /ɨ/) and */jē/ are written ⟨i̯ä⟩ and ⟨i̯ē⟩ respectively, but /jV/ for all other vowels seem to use ⟨y⟩. I doubt this is a necessary distinction for Wiktionary to make, since it seems entirely predictable from environment, but I'm still unsure what purpose it is meant to serve. @GabeMoore, might you be able to weigh in? — 69.120.64.1504:34, 5 June 2021 (UTC)Reply
Latest comment: 4 years ago1 comment1 person in discussion
A bit fiddly: one entry is a verb and the other a noun, and they both have multiple senses with slight distinctions that should be ironed out. Equinox◑13:13, 25 July 2021 (UTC)Reply
User:Kwamikagami has moved a few Rapa Nui pages en masse from a straight apostrophe (U+0027) to a saltillo (U+A78C)
The reason they give for this is that, since unicode classifies the apostrophe as a punctuation mark, rather than a letter, it shouldn't be used as a letter, and thus the visually similar saltillo should be used.
The counter-reason given is that Unicode's classification is arbitrary and has little to do with actual usage in the language, which we as Wiktionary want to follow.
There is one mention of the saltillo being open to usage, in Kieviet (2007).
There is yet to be found at least one usage of the saltillo for Rapa Nui in the wild. since both Kieviet (2007) and schoolbooks published by the Chilean government use either a straight apostrophe (U+0027) , or a curly apostrophe (U+2018) provided with a font that renders it similar to a prime (U+2032). Other grammar books and dictionaries use any of the three characters.
I believe we should move these pages back to a straight apostrophe, and set the use of the straight apostrophe in stone at WT:ARAP. What do others think? Thadh (talk) 10:53, 3 September 2021 (UTC)Reply
We have four sources:
We have Du Feu, who used a special font because the usual fonts available to her were inadequate for Rapa Nui, which required two special letters (the glottal stop and the engma). If the ASCII apostrophe were adequate for glottal stop, there would've been no need for a special letter.
We have Kieviet, who states that, now that Unicode provides for the saltillo, there is no longer a need for a special font.
We have the ministry dictionary, which uses an apostrophe letter -- not ASCII input with smart quotes, because it has the '9' shape at the beginning of a word.
We have the ministry educational material, which uses a hodgepodge of ASCII apostrophes, curly apostrophes and curly quotation marks -- that is, sometimes '1' shaped, sometimes '9' shaped and sometimes '6' shaped, with little consistency. Presumably we wish to aim for better than that, even if it is common.
In most languages that use an apostrophe-like letter for glottal stop, it's common to substitute a keyboard <'>, but that doesn't mean we should do the same. When writing Chechen, it's common to use a digit <1> for palochka, but again that doesn't mean we should do the same. When writing Ossetian, it's common to use a Latin rather than Cyrillic æ, but if you did that in a domain name, it would likely be tagged as phishing. The shortcuts people take with typography may be common, but a dictionary is expected to be more professional. kwami (talk) 15:10, 3 September 2021 (UTC)Reply
To briefly summarise the important points of what I said on Thadh's Kwamikagami's talk page: This move should have been raised here first, so the weight of the evidence should have to point to the saltillo for us not to move it back. Kwami is from Wikipedia, and believes that we should be "more professional", even at the cost of ignoring all actual usage in a language community. (He has not, to the best of my knowledge, taken me up on my suggestion that he should go to the Wikipedias of languages like Rapa Nui and Hausa that use the apostrophe, and tell them that they're doing it wrong — just us.) I was open to the possibility that the saltillo might see actual use, but the fact that it doesn't makes this seem to be all about the Unicode specifications, which are not relevant to a descriptive dictionary. As I result, I support moving back to the apostrophe. —Μετάknowledgediscuss/deeds16:15, 3 September 2021 (UTC)Reply
There are several recent cases where @Mahagaja has advocated a particular Unicode character instead of a the straight apostrophe in such cases, but I don't remember the specifics off the top of my head. Chuck Entz (talk) 16:18, 3 September 2021 (UTC)Reply
We do need to use Unicode correctly. The straight apostrophe (U+0027) and curly apostrophe (U+2018) are punctuation marks and should not be used as letters. That's what the saltillo (U+A78C) and modifier letter apostrophe (U+02BC) are for. If using punctuation marks as letters were acceptable, Unicode wouldn't have bothered creating those characters. Using punctuation marks for letters is as bad as mixing Latin and Cyrillic (which is something we used to do for Montenegrin Serbo-Croatian, but don't anymore), as Kwami points out, and just because other sources do it doesn't mean we should. We can, of course, have hard redirects from spellings with the more easily typable straight apostrophe, or put the correct page name in {{also}} if the spelling with the straight apostrophe exists (as a punctuation mark) in another language. But Kwami was quite right to move these Rapa Nui pages to the spelling using the correct character, and they should not be moved back. —Mahāgaja · talk16:39, 3 September 2021 (UTC)Reply
@Mahagaja: So if nearly everyone writing text in a given language (say, tens of millions of people) use a character that you consider "wrong", we should still avoid it because it doesn't respect Unicode? Whatever happened to descriptivism? (And if you think this is a silly hypothetical, it's not — I just described the situation with the apostrophe in Hausa.) —Μετάknowledgediscuss/deeds21:56, 3 September 2021 (UTC)Reply
It reminds me of when I started adding entries in the Cupeño language and had to figure out how to deal with a letter that the (pre-Unicode) main source defends as being very easy to replicate by filing bits off the $ key on a typewriter. People work with what they have available, and it doesn't always fit neatly into the right categories. Chuck Entz (talk) 23:00, 3 September 2021 (UTC)Reply
@Metaknowledge: If tens of millions of people used Rapa Nui, it would have its own keyboard layout and the saltillo would be easy to type for them. Descriptivism applies to language, not orthography. It's not anti-descriptivist to say that recieve is a misspelling, and using an apostrophe as a letter is also a misspelling. The only difference is that using an apostrophe instead of a saltillo isn't a mistake that can be made when writing by hand or by typewriter or that can be detected in a photocopy or a scan, so it's more subtle (like mixing Latin and Cyrillic), but it's still a mistake. —Mahāgaja · talk06:49, 4 September 2021 (UTC)Reply
@Mahagaja: As I said, my example wasn't a hypothetical. There are somewhere around 60 million native speakers of Hausa per WP. Mac offers lots of keyboards for lots of languages, including one for Hawaiian complete with ʻokina, but it doesn't provide a Hausa one. When I search for Hausa keyboards on Google, they provide the apostrophe and quotation marks, but no character designated by Unicode as a letter. So are you really maintaining that nearly all typed material in Hausa is misspelt? —Μετάknowledgediscuss/deeds07:11, 4 September 2021 (UTC)Reply
Yes, though of course that's not the Hausa users' fault, it's the fault of the software companies that care more about providing support for a minority language spoken by 24,000 people in the United States than about providing support for a language spoken by tens of millions of people in Africa (i.e. systemic racism). I don't blame Hausa users for doing the best they can with the materials available to them, and I know it's unrealistic to expect them all to type ʼ instead of just hitting the apostrophe key, but as a dictionary it's our responsibility to do things the right way rather than the easy way. —Mahāgaja · talk07:29, 4 September 2021 (UTC)Reply
@Mahagaja: Systemic racism is the root cause of lots of annoying things, but some of those things are set in stone. At this point, Hausa users have no reason to follow Unicode rules even when they can. I'm sure the editors at Hausa Wikipedia can figure out how to get the "correct" character if they wanted to, but I see that you too have no interest in going over there and telling them they're doing it wrong. I have a radical idea: let's respect their choices. —Μετάknowledgediscuss/deeds17:57, 4 September 2021 (UTC)Reply
I have a better idea. We'll let Hausa Wikipedia worry about Hausa Wikipedia, and we'll worry about Wiktionary, which, as I said, has a responsibility to use Unicode correctly, even when other Wikimedia projects use it wrong. —Mahāgaja · talk18:11, 4 September 2021 (UTC)Reply
If Wikitionary or our browsers represent the languages incorrectly, because they follow the Unicode definition that punctuation marks are punctuation marks, then we are not documenting the languages correctly. If a language commission chooses a specific Unicode point that is one thing, but that's seldom the case. Since we by necessity choose a Unicode point for each letter regardless, we might as well choose one that represents the language well. kwami (talk) 01:17, 11 September 2021 (UTC)Reply
Just to jump in quickly, as someone who is Nigerian and has had to go through the process of creating my own keyboards to be able to type properly in Yorùbá and as someone who is learning Hawaiian, while there definitely is systemic racism when it comes to African languages, I really would not pit them against Hawaiian. Hawaiian still lacks a ton of support, sometimes even less than Hausa, Igbo, & Yorùbá (see: spellcheck on PC Microsoft Word or language packs for Windows), and people are still trying to get more support for it. At the same time, Hawaiian is more than just "a minority language spoken by 24,000 people in the United States", it is an indigenous language that currently is the product of tons of effort gone towards revitalizing it and making sure that it's well-supported. And so, please do not pit them against each other saying that Hawaiian having more support (even though it doesn't) is systemic racism. The communities are aiming for very similar goals and are all dealing with racism in our own ways, not from each other.
Re: the main issue at hand. I would go with what the speakers of the language use. It's similar to what we do for Hausa, Igbo, & Yorùbá tones. No matter how annoying it can be, since the majority of speakers don't write tones out, we don't put them in page titles and only in headword lines, since we want people to be able to find words that they see "in the wild", which will often not be tone-marked. So it's a similar issue here, if the majority of speakers and majority of texts don't use the special character and it's not hard prescribed, then the page title shouldn't change, and the special character can be put in the headword line. That's my personal take on that issue. AG202 (talk) 13:48, 11 September 2021 (UTC)Reply
┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ This isn't a case of leaving out elements like tone marks. All RS's for Rapa Nui use the glottal stop. It's a matter of deciding which Unicode point to use for it, not whether to include it.
Re. the poor support for W. African languages, that's not racism so much as bias in the interests of the people developing Unicode. When Unicode decided they would no longer accept precomposed Latin, there was a call for people to get what they needed in before the deadline. But the respondents were all working on European languages. After West Africans started complaining that Unicode didn't adequately support their languages, the Unicode people realized they'd fucked up. At least, the ones I've talked to say they wished they'd realized what was going to happen, and spent more time on major African languages than on minor European languages.
Now that there are supplemental planes, there's room for more precomposed Latin. But as computers improve, there's less and less need for it, so I doubt they'll start accepting precomposed letters again.
I find it amazing that you could write Yoruba without tone. I mean, you can write it without vowels as long as you include the tone! kwami (talk) 23:06, 18 October 2021 (UTC)Reply
There are many reasons that folks don't write Yoruba with tones, partly because of a lack of solid education, partly because of a lack of technological support, partly because you can (usually) tell what you mean from context, and a ton more. There was a solid seminar done last year at the British Library about it actually, but yea it's complicated. I wish that precomposed characters could be brought back, but that's a pipe dream. I don't think that you can write it without vowels as long as you include the tone though, as Yoruba is very vowel-heavy, and it'd get confusing quickly.
In terms of the question at hand though, I brought up the comparison more of a way to show how proscribed writing & everyday writing can interact on Wiktionary. If the majority of speakers type/write one way in informal & formal registers, that way should be the way that should be primarily reflected on Wiktionary, while the proscribed way can be shown in the headword line or an alternative form or whatever. However, I don't know the specifics of the situation with Rapa Nui, so I won't comment directly on the specifics of addressing it. AG202 (talk) 23:15, 18 October 2021 (UTC)Reply
My impression of Yoruba, from the very very little I think I know of it, is that in fluent colloquial speech the vowels tend to assimilate to each other, and even consonants sometimes drop out, so that you might be left with a long with a bunch of tones and just a few consonants. It's the tone that makes it comprehensible. But that's by ear; I guess it wouldn't work well in writing.
But Hausa, yeah, I can see omitting the tone without any problem, except maybe the need to dab an occasional word. You might learn to write those few words with tone, the way accent marks distinguish homonyms in Romance languages, and otherwise ignore it. And some languages mark changes in tone, rather than the tone of each syllable. But I doubt that would work for Yoruba either. kwami (talk) 23:23, 18 October 2021 (UTC)Reply
Input needed
This discussion needs further input in order to be successfully closed. Please take a look!
I have a suggestion that might be able to square this circle, but it's a bit awkward to explain so bear with me:
There are situations when it makes sense to remember the difference between the orthographic character a person intends to write, and the Unicode character which they actually use. A good example of this is the full stop "." (U+002E), which is also used in English (and Translingually) to represent the decimal point. We all agree that a full stop and decimal point are two different things, because any competent French translator would have to treat them differently, but the important thing is that that remains true regardless of which Unicode codepoints we happen to use. Indeed, it's true whether or not we're even encoding the characters at all. The same is true in French with the decimal point and the comma, too. Equally, nobody who receives "A-" on their homework is receiving "A dash" or "A hyphen".
Conversely, ｊｕｓｔ ｂｅｃａｕｓｅ Ｉ ｗｒｉｔｅ ｉｎ ｆｕｌｌ－ｗｉｄｔｈ doesn't mean that any of us actually think "ｊ" has a distinct identity to "j" etc. There might be technical, historical and/or stylistic reasons why we have both, but the point is that we consider them to have the same orthographic identity.
However, none of this prevents us from having a particular manual of style when it comes to certain characters. If we want to start using the en dash "–" (U+2013) or minus sign "−" (U+2212) in places where people intended to use them (i.e. intended characters with those orthographical identities), then that's fine. It would be no more of a problem than our choice to use a clear, black, legible font on white by default, when the original might be scrawled on a barely legible manuscript. Obviously there are no codepoints to interpret in cases such as that. Hell, a lot of the time the codepoints "used" are actually just whatever the OCR software vomited up anyway. Just like with misspellings, there needs to be some genuine intention, and it needs to be considered with respect to the orthographical identity of the characters, and not the codepoints they happened to pick.
A final point is that writers of a language don't necessarily know their own language perfectly, or they might not perceive a conscious distinction between two characters that does actually exist, because the context usually makes it so obvious (e.g. the full stop and the decimal point). It's not enough to say "yes, they intended to write an apostrophe because that's what they used". Are they really treating it as one?
I don't know enough about Rapa Nui to know whether the saltillo is the most appropriate character, but I hope that's a framework that makes it easier to determine the answer. Theknightwho (talk) 16:00, 7 July 2022 (UTC)Reply
This Turkish suffix entry is probably the same as -i, and possibly -ı, due to vowel harmony. While I don't know much about Turkish, the fact that this was created as the only Turkish edit ever by this contributor and the other two were created by a veteran contributor who is a native speaker has to count for something. Chuck Entz (talk) 05:45, 18 September 2021 (UTC)Reply
-u is a harmonized form of -i, as are -ü and -ı. The canonical forms of suffixes are those with i and e. I disagree with the current policy of essentially providing the same definition 4 (or 2) times, see for instance the situation with -im, -ım, -um, -üm where only one contains all meanings and etymological information. I'm in favor of keeping the harmonized realizations of the suffixes as separate articles but I'm strongly in favor of converting the non-canonical forms into simple referral pages (see -dük). --Fytcha (talk) 09:59, 18 September 2021 (UTC)Reply
This would almost certainly not survive on Wikipedia. I have mixed feelings about the Appendix namespace here, as it seems a lot of things go there that would never be acceptable in the main dictionary, but that appendix pages are so hard to find for the casual user that it doesn't really bring us down. —Soap—11:36, 13 April 2023 (UTC)Reply
If we do end up deleting this, i'd hope we could try to contact the editor who wrote most of it (see User_talk:DKThel). There are other wikis that could host content like this where they wouldn't be pushed into the background like our appendix pages are. Admittedly the trade-off for that is having ads and using a site that is itself harder to find. —Soap—11:47, 13 April 2023 (UTC)Reply
There's definitely no point in moving it to Wikipedia, since it was originally moved here from Wikipedia, so they already decided they don't want it and foisted it on us. That's why it's written so encyclopedically. If anyone's interested in it, they should clean it up to make it more dictionarian; otherwise we should just delete it. —Mahāgaja · talk12:34, 13 April 2023 (UTC)Reply
Sfacimma is an alternative spelling of sfaccimma, which is how the word has been mostly written in the past years; the IPA pronunciation of the word is nowadays always /ʃfat͡ʃˈt͡ʃimmə/, with the voiceless postalveolar affricate having always the gemination, hence the spelling cc. Antomanu14 (talk) 13:59, 10 December 2022 (UTC)Reply
I think it's been an alternative form of guarantee for a couple of centuries. Only recently (this decade) has it become much less common than guarantee. DCDuring (talk) 17:39, 13 November 2021 (UTC)Reply
I'm in favour of moving this page to *én. As {{R:ine:LIPP|page=221|vol=2}} shows, there is no evidence that points to an initial laryngeal and Greek and Vedic speak against it.
We reconstruct all PIE terms with an initial laryngeal on the project, per current PIE theory, so *én = *h₁én. Sidenote, {{R:ine:LIPP}} is an embarrassment in the academic community, and should never be used as a primary source. --Sokkjo (talk) 02:24, 8 February 2023 (UTC)Reply
I have elaborated to why accademics largely reject {{R:ine:LIPP}}, and referred you to this unfavorable review, DOI:10.1515/zcph-2019-0009. That's all neither here nor there, as on this project, we subscribe to larygeal theory, which also calls for word-intitial larygeals before vowels. If you wish to make an arugment for why we should do away with that standard, feel free to start a discussion in the WT:Beer parlour, but as is, your move request is unwarranted. --– Sokkjō08:52, 27 March 2023 (UTC)Reply
You seem to have not read that review. If you did you'd see that it is overwhelmingly positive:
"Ce sera un ouvrage de référence pour longtemps."
"Ces remarques ne retirent rien à l’importance de l’ouvrage, qui peut servir de base tant à une recherche synchronique éclairée consacrée à tel ou tel groupe de langues qu’à une étude proprement comparative."
The other review I'm aware of is also overwhelmingly positive:
"In this massive, and truly monumental, two-volume work that was years in the making, author George Dunkel (henceforth D) draws on the extensive research, and the literally dozens of articles, that he has done throughout his distinguished career as an Indo-Europeanist, investigating the uninflected bits and pieces – the ἄπτωτα (áptota), the indeclinabilia¹ – of the Indo-European lexicon that are so indispensable to the phrasal and sentential syntax and to discourse and text structure in all the family’s languages." https://www.jbe-platform.com/content/journals/10.1075/dia.33.4.05jos
Nothing about this thing takes away from laryngeal theory.
Since I'm guessing you don't have academic access to the second page:
Reste une réserve. Malgré la prudence de l’auteur, les processus de formation des grammèmes qu’il étudie relèvent, par définition, de la reconstruction, et l’ouvrage n’étudie pas de manière détaillée les processus qui ont lieu à date historique. Parfois le lecteur peut avoir l’impression que le système titué est d’une complexité qui le rend typologiquement invraisemblable; ainsi, vol. 1, pp. 24–26, l’auteur pense pouvoir reconstruire pour l’indo-européen quatre thèmes pronominaux qui relèvent de l’exophore proximale, deux qui relèvent de l’exophore distale, et quatre thèmes anaphoriques (George Dunkel écrit que les thèmes liés à l’exophore proximale et distale ne sont pas en contraste sémantique les uns avec les autres, mais seulement avec l’absence de déixis; ce point est obscur aux yeux du recenseur).Une telle richesse en thèmes démonstratifs nécessiterait une explication. Au demeurant l’opposition entre exophore proximale et distale n’est pas nécessairement suffisante pour couvrir tous les thèmes de l’indo-européen, qui a pu posséder par exemple trois degrés d’exophore. En fait il peut sembler que la reconstruction des grammèmes indo-européens est vouée au flou, faute de données permettant d’étudier, notamment, la sémantique exacte des éléments concernés aux différents stades chronologiques et dans les différentes aires géographiques à prendre en compte.
Again, I'm not here to agrue about LIPP -- that's beside the point. The point is that the established convention we follow on the project for reconstructioning PIE is that #VC- only possibly exists in pronouns, if even there. See {{R:ine:IEL|52}}. – Sokkjō23:03, 27 March 2023 (UTC)Reply
@Sokkjo, I read the whole review. I even quoted from the second page. As I said before, a reservation does not equal a invalidation.
The validity of LIPP is very much on point. I would like to mention an alternative reconstruction *én (and if others agree move the page), which is supported by evidence instead of on some misplaced assumption. You preclude any discussion by rejecting the evidence out of hand.
In addition, I would like to continue citing LIPP, so your violent objection to it ("embarrassment to the academic community") is relevant to me. I think it is fair to say that if you could back up your objection you would have done so by now.
I am of course aware that roots had a CₓVCₓ structure. There are good reasons for assuming this. However, this is not the case for suffixes, it is not the case for pronouns, it is not the case for adverbs and it is, indeed, not the case for particles.
Your "established convention" that #VC- entries aren't allowed, doesn't exist. If you think otherwise please point to it. WT:AINE does not mention the phonotactics of entries. And at any rate, WT:RECONS clearly says that "variants and disputed forms can then be addressed in great detail within the text of the pages themselves". If you don't want *én on the page, you need to have (at the very least) substantive arguments why the evidence supporting it is wrong.
But I'd ask you to please be more careful about your references. You keep quoting things which don't support your position. {{R:ine:IEL|52}}: "It seems that onsetless initial syllables (#VC-) were rare" ie not nonexistent. LIPP, the first systematically study of Indo-European particles, documents evidence for a substantial number of exactly these. —Caoimhin ceallach (talk) 01:23, 29 March 2023 (UTC)Reply
I'm aware of what I cited, "rare" meaning they are limited to pronouns, and to continue on to the following sentence, "It is common practice now to reconstruct initial laryngeals even when not strictly provable". You seem to be under the impression that I, created this "common practice" and I set that convention here on the project. I'm honored you think I have that seniority, but despite contributing here for over a decade, it long preceeds me. If you want to argue against the status quo, not just on this project, but in academia at large, the weight is on you to do so. – Sokkjō03:51, 29 March 2023 (UTC)Reply
Latest comment: 3 years ago1 comment1 person in discussion
The art/literature senses are defined very differently at the two entries, which seems like a problem. One is already tagged for cleanup, so, good luck! Equinox◑00:21, 1 February 2022 (UTC)Reply
Latest comment: 3 years ago1 comment1 person in discussion
The conjunction وَ(wa) is not part of the phrase really. The phrase does occur frequently with it, but this is mainly owing to the "idiomaticness" of conjunctions in Arabic, mostly in prose. It is a sentence in itself, roughly "There is no(thing) equal to", not like the English adverbials that have comparable meanings (such as particularly and especially or above all). The entry should therefore be moved لَا سِيَّمَا(lā siyyamā), with the "variant" with وَ(wa) deleted. Roger.M.Williams (talk) 18:11, 24 February 2022 (UTC)Reply
Latest comment: 2 years ago2 comments2 people in discussion
There still seems to be a lot of overlap here, e.g. the chandelier sense. Is there any sense of the word that cannot be spelled both ways? Equinox◑03:47, 4 March 2022 (UTC)Reply
Any English word ending with -er occassionally shows up as -re. It doesn't seem like this needs a tag and discussion, though. Some editor at lustre was just wrong: There's no reason to say "alternate form of luster" + 3 repeated senses that're already at luster. Maybe add a usage note if some American speakers tend to still use re unexpectedly more often in some cases.
That said, the luster entry is currently a bit off. 'Shininess', '5-year period', and 'den' all get spelled with an -re in standard British English but using it for 'one who lusts' would still seem like a misspelling. The alt form needs to be with each etym that uses it and not headlining like it is now. — LlywelynII23:40, 13 June 2023 (UTC)Reply
I think I was trying to show that the open form was used more commonly for some definitions and the closed for others. Is there pure circularity remaining? DCDuring (talk) 17:18, 9 March 2022 (UTC)Reply
I have tried to make clearer the differences and have simplified the "Further reading" sections. I don't see why they should be moved, merged, or split, whichever it is that you are seeking. DCDuring (talk) 18:08, 9 March 2022 (UTC)Reply
It's not, just a doublet that came into the language by a different (rather convoluted) route. Serynga is listed as an alternative form at English seringa, but it looks like it's really a borrowing from French, where it's an alternative form of French seringa. The spelling is no doubt influenced by the taxonomic name.
From what I can gather, Latin syringa developed into Dutch sering, which was borrowed into Portuguese as the name for rubber plants in the genus Hevea and into French for the syringa, Philadelphus coronarius, both with an "a" added. English borrowed Portuguese seringa for the rubber plant and French serynga for the syringa.
So, are the definitions in both entries correct? Because they currently claim to both have the same first two definitions... in which case we should either have {{syn}} crosslinks between them or reduce both senses on one to {{synonym of}} (+gloss) of the other. - -sche(discuss)08:07, 28 March 2022 (UTC)Reply
@Biolongvistul: On the contrary- one of these should be made the main entry and the other an alternative form (if you can call it that: it's really just two slightly different ways of writing the exact same thing). Chuck Entz (talk) 08:02, 22 August 2023 (UTC)Reply
This is only an English entry, and on English Wikipedia it is not capitalized inside the middle of sentences. The rationale for capitalizing it in 2007 was that it is a German language entry, except there has never been a German language section on this page. -- 65.92.246.14203:20, 13 May 2022 (UTC)Reply
I definitely agree that all of the headwords mentioned should be at "a few ...". Unfortunately there are probably more (attestable?) alternatives besides what -sche has found. Redirects from "few ..." are especially useful because many with beginning knowledge of English seem to have problems with English determiners. DCDuring (talk) 19:23, 29 May 2022 (UTC)Reply
This is a good issue to raise. I've mentioned before that, with proper nouns, we don't seem to have (or at least we don't consistently use) anything about the determiner/article: I mean it's theEiffel Tower and theCold War, but ∅ Dijkstra's algorithm and ∅ Greenpeace. Proper nouns aside, I usually drop the determiner/article from entry titles unless it seems absolutely 100% necessary all the time. But that's pretty vague and comes out of my wacky head. Equinox◑01:53, 4 June 2022 (UTC)Reply
Maybe. Yeah. I would imagine "some few..." etc. might be possible. But even I have better things to do than attest them. Just an observation. Equinox◑02:17, 4 June 2022 (UTC)Reply
It's a snowclone with many possible variants. I dont think many people are going to look up few or short of expecting to find this full phrase. And those words arent in every variant anyway ... one can also say "two cards shy of a full deck" which uses neither of them.
What would be nice is if the Appendix namespace was in the default search space so that the snowclone page might at least turn up in a search. As it stands, I don't think we need all these mainspace pages since they are all exact synonyms of each other, but if we delete them there will be no way for a naive user to find the snowclone pages unless they somehow know that it's tucked away in the Appendix. —Soap—20:05, 30 June 2023 (UTC)Reply
@Dohqo: Because there's already a Persian entry on the same page, and the character is correct for Persian, it doesn't make sense to move the page. Just delete the Old Anatolian Turkish section from this page and create it on the correct page. You can do it all yourself, no admin rights needed. —Mahāgaja · talk08:36, 18 June 2022 (UTC)Reply
These were recently moved by @Apisite from their own user namespace to the Wiktionary namespace under "Requested entries (Chinese)". All of these pages are not requested entries but pronunciation requests. I'm not entirely sure where these should be moved instead, but I don't think they're in the right place currently. — justin(r)leung{ (t...) | c=› }16:59, 23 June 2022 (UTC)Reply
@Fytcha: A word of caution: anything involving pondian variation should be handled carefully. There are good arguments for going either way on most of these, and we don't want to start any kind of conflict. Our general practice has been to arbitrarily go with whichever version was first, though it's been a while since one of these came up. Chuck Entz (talk) 20:17, 26 June 2022 (UTC)Reply
In this case, fibre is older, but by only 14 hours. Also, the translation tables are all already at fibre, so I feel like making fibre the primary spelling and fiber the alternative spelling will be less work. —Mahāgaja · talk21:09, 26 June 2022 (UTC)Reply
Also, since 2016 fiber has been more common in Google's British English N-Gram corpus andsix times more common in American English corpus. DCDuring (talk) 21:54, 26 June 2022 (UTC)Reply
@Chuck Entz: I see. If that is de facto policy then the meat should go to fibre. However, if I could have devised the policy, I would have made it so that it always aligns with the frequency because that way the users land on the non-redirecting spelling more often. — Fytcha〈 T | L | C 〉 22:26, 26 June 2022 (UTC)Reply
We actually had an attempt by a Russian internet troll (geolocating to Crimea) to get us arguing about UK vs. US issues, but it went nowhere. At the time I just thought it was odd, but with the revelations after Trump was elected I finally put two and two together and realized what was going on. I still have no idea why they even bothered, since our discussion forums aren't exactly the center of the universe. I do know that the mutual respect between our US and UK editors, helped by this kind of practice, was the main reason it was such a non-issue. Chuck Entz (talk) 23:20, 26 June 2022 (UTC)Reply
@Chuck Entz I have it on my to-do list to build a template that duplicates the material from the "primary" entry, which should hopefully circumvent issues like this anyway. I've done something similar with Tangut already (e.g. see 𗁘(*rjijr²), 𗁩(*tẽ¹), 𗀏(*par²)), though the implementation would need some tweaking. Theknightwho (talk) 00:18, 27 June 2022 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
One is tagged as obsolete and defined as A kind of furnace used in refining, to separate the metal from cinders and other foreign matter., another not obsolete defined as A furnace in which slags of litharge left in refining silver are reduced to lead by being heated with charcoal.. Good luck to the potential merger Dunderdool (talk) 18:06, 29 July 2022 (UTC)Reply
Latest comment: 2 years ago5 comments4 people in discussion
This idiom is far more versatile than the specific and somewhat informal phrasing we have here (which doesn't even match the quotation we have), it's a fully fledged verb phrase — see the examples at Teaching grandmother to suck eggs.
Two points: there is such a wide range of familiar terms for grandmother that can be used in this phrase so I think it's best to stick with "grandmother". However I think it's worth investigating if it's more common with or without the possessive pronoun (here "one's"); to me it sounds more natural with it but there are citations both ways. 86.145.59.12018:42, 14 August 2022 (UTC)Reply
I'm somewhat inclined to pick a most common or general negative form to lemmatize like not teach grandmother how to suck eggs, and also have the positive form (maybe teach grandmother to suck eggs since a possessive doesn't seem required? or if a pronoun is more common, then redirect the pronounless form to the pronouned form, either works). This is both because it's unclear how many translations can have the negative removed and because in general, as I said in the discussion of all it's cracked up to be further up this page, when we redirect a negative expression to a positive one or vice versa there's a risk that a reader who doesn't notice they were redirected will come away thinking the phrase means the opposite of what it actually means. To avoid duplication we could make the negative form almost a soft redirect, defining it like "To not teach grandmother to suck eggs(“presume to give advice to someone who is more experienced”)" or even "To not teach grandmother to suck eggs(see that entry)"; I don't know, I don't like splitting content across multiple pages, but I also think it's risky to silently strip away the negative polarity with a seamless little redirect and expect IPs who sometimes don't even notice they're on Wiktionary and not Wikipedia to notice and understand that the polarity of the headword has changed and thus that the definition of the term they looked up is the opposite of the one we're giving them. - -sche(discuss)15:20, 19 August 2022 (UTC)Reply
Negative polarity is "licensed" in many forms, starting with the negative being separated from the rest of the expression: conditionals, questions, infinitives with certain verbs (eg, try to) or other expressions (eg. hard to). These might lead someone to look up the positive form. I think that a "negative-polarity item" label (with link to WP or our Glossary), usage examples with adjoining and disjoint not and n't, and redirects would enable us to use the positive form as the lemma. I don't see how to use redirects in the other direction. Even usage examples would be problematic with not in the headwords. DCDuring (talk) 21:07, 19 August 2022 (UTC)Reply
What I mean is, I'm somewhat inclined to have both "not teach grandmother to suck eggs" defined as "not give advice to someone more experienced", and then also "teach grandmother to suck eggs" defined as "give advice to someone more experienced", redirecting all the various negative forms to the first one and the positive forms to the second one. But I'm not opposed to only having the positive form and redirecting everything to it; I do dislike splitting content across multiple pages, I just also think there's always a danger when someone types "not teach grandmother to suck eggs" into the search bar and as seamlessly sent to "teach grandmother to suck eggs" where they read a definition that's inverted from that of the term they typed in and which they think they looked up. - -sche(discuss)21:46, 19 August 2022 (UTC)Reply
Latest comment: 2 years ago4 comments4 people in discussion
Plenty of overlap, spesh with translations. Maybe there's just one species called this, maybe two... something for the animal nerds here... you know who you are Almostonurmind (talk) 00:48, 8 September 2022 (UTC)Reply
Formally, that's probably true, though I doubt most people make the distinction consistently colloquially. But that wouldn't be particular to bighorn. I think people who didn't make the distinction would be just as likely to use bighorn sheep when describing Dall's sheep. Andrew Sheedy (talk) 15:18, 21 October 2022 (UTC)Reply
I have split both into two subsenses and RfVed the O. dalli subsenses. I have not yet found any evidence that either term is applied to O. dalli. I would include O. dalli and thinhorn sheep under See also at both of these entries. DCDuring (talk) 15:57, 21 October 2022 (UTC)Reply
Latest comment: 2 years ago3 comments2 people in discussion
Are these the same? The Kiowa language does not appear to be related to Shoshone, nor does the Wikipedia article on the Kiowa people claim that they are from North Platte, Nebraska. I have a hunch that Kioway is an alt form of something, and this seems like the most obvious answer, but someone should check and try to make sense of this before merging them. 98.170.164.8807:56, 14 October 2022 (UTC)Reply
Shoshonean is an old term for the northern part of the Uto-Aztecan languages, from Shoshone. Many of the names for the Numic languages are only loosely correlated with linguistic reality, so terms like "Shoshone", "Paiute" and "Ute" are kind of hard to pin down without qualifiers. There is a Shoshoni language, but peoples like the Timbisha and the Bannock are also called Shoshone.
Kiowa is part of the Tanoan languages, which may very well be related to Uto-Aztecan as the Aztec–Tanoan languages, but linguists have yet to completely connect the dots. It was speculative in 1913, and it's still not definitively established in 2022. It reminds me of the Achilles and the Tortoise paradox.
It's all part of the confusion that results from early efforts to classify wide-ranging nomadic peoples who have moved into different regions and adopted different cultural patterns and lifestyles. Just as the Comanche were Great Basin Numic people who moved to the Great Plains and adopted a Plains Indian culture, The Kiowa also moved from the pueblos into the Great Plains and adopted a similar culture.
Latest comment: 2 years ago3 comments2 people in discussion
The definitions we give for all three terms are essentially identical, but the forms differ because they are borrowed from different Chinese lects (Mandarin, Cantonese, and Taishanese itself, respectively). Should these use {{alt form}} or {{syn of}}? 98.170.164.8823:08, 14 November 2022 (UTC)Reply
Merged into the first form which, per ngrams, is the most common. (For the place rather than the -ese, Taishan is particularly lopsidedly more common than the alternatives.) - -sche(discuss)07:26, 6 March 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
These two are essentially the same phrase sharing the same meaning, with the more common 食花生 being derived from the other. – Wpi31 (talk) 12:00, 18 November 2022 (UTC)Reply
Latest comment: 2 years ago4 comments3 people in discussion
Requesting to move snowsquall to a space-separated form snow squall. The unspaced form doesn't appear to have been used purposefully or frequently, if at all, in the past or present. It also does not appear to be used by either the US-American NWS or the Canadian MSC, and hasn't appeared in any online news coverage. Bailmoney27 (talk) 19:14, 19 November 2022 (UTC)Reply
I support this. I've never seen the bunched spelling before and I've been following winter weather for many years. It does seem to be in use, but distinctly less common. Wikipedia's favoring of the bunched spelling seems to be largely a matter of the article having been created early in Wikipedia's lifetime, and with a radar scan from 2004 featuring that bunched spelling. Essentially, we had a model to follow and we stuck to it, but it happens that most people, including the national weather services of both the US and Canada, prefer the two-word form. —Soap—21:22, 10 December 2022 (UTC)Reply
Well, I decided to just move the page myself, as it's been up here unopposed for six months, and because I want to fill in the usual "see also" hatnote which would require that both spellings exist. Since this would make a non-admin move impossible, I moved the page before I put in the hatnote. —Soap—11:19, 13 April 2023 (UTC)Reply
No, the two have different etymologies (one from Latin missa and another from Latin Massa), and obviously the two have different meanings too איתן קרסנטי (talk) 05:55, 31 July 2024 (UTC)Reply
They look like alternative case forms to me, with almost identical etymologies and definitions. It may be difficult to tease out whether the upper- or lowercase form is more common, based on collocation searches. As a start, since 1870 Holy Mass has been more common than than holy mass, holy Mass, and Holy mass (probably mostly sentence initial) at Google N-Grams and much more common since 1940. (Is Holy Mass SoP???) And o'clock mass and o'clock Mass have been roughly equal since 1900. DCDuring (talk) 14:30, 31 July 2024 (UTC)Reply
@Sgconlaw: I meant that “Etymology 1” and “Etymology 2” (but not “Etymology 3”) in one entry should be merged with the respective etymologies in the other entry. J3133 (talk) 19:02, 5 January 2023 (UTC)Reply
@J3133: ah, ha ha! I take it you mean that etymology 1 in haha and ha-ha duplicate each other, so one entry should be made the main lemma and the other converted to an alternative form; and likewise for etymology 2 in those entries. — Sgconlaw (talk) 19:19, 5 January 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
Shouldn't this be in the Reconstruction namespace? Tbh I'm not sure why we need an entry for this at all, even granting that the suffixes -iġ and -eġ are alternative forms of each other. If this specific non-attested form were mentioned in secondary literature then I could see a case for it, but I can't find anything. To be generous, it's plausible that a version with an /e/ vowel existed in Anglo-Saxon speech, if the versions of the suffix were interchangeable. For now at least, I'll just leave this at RFM, but feel free to send this to RFD if desired. 98.170.164.8810:49, 11 December 2022 (UTC)Reply
Latest comment: 11 months ago7 comments5 people in discussion
Currently this redirects to arsed and, further to the discussion in the Tea Room, I propose that we undo the redirect. After all we aren't currently redirecting can't be fucked or can't be bothered. It seems better to have stub entries for all synonyms of can't be bothered listing them as alternative forms only, with all the synonyms and translations listed on the same page. Though I'm not suggesting creating be arsed and be fucked, we should probably keep be bothered as a translation hub and for the purpose of distinguishing it from the rare word bebothered as we currently do. --Overlordnat1 (talk) 01:49, 14 December 2022 (UTC)Reply
I agree. I hate these redirects to single words - they rarely make sense without the rest of the term, and they're unintuitive even for experienced users. Theknightwho (talk) 23:39, 4 January 2023 (UTC)Reply
I don't know whether there are any other uses of fuck to mean "bother", nor of arse with that meaning.
Why wouldn't we RfV arse#Verb "To make, to bother" if the redirect doesn't seem right? If virtually the only usage with the "bother" sense is can't be arsed there is no reason for this not to be a lemma. DCDuring (talk) 23:44, 15 August 2023 (UTC)Reply
Latest comment: 2 years ago2 comments2 people in discussion
The capitalization of these entries is inconsistent, even though they are all coordinate terms for different views on the same issue. Note that Miaphysite and dyophysite don't (currently) exist, while both capitalizations of monophysite do. Also, some of these have adjective senses and some don't. Not technically a request for a move, merger, or split, but it's a similar issue to what often comes up here, so this seemed like a fitting venue. 70.172.194.2511:37, 19 December 2022 (UTC)Reply
IMHO, at the very least, one foul swoop needs explanation and therefore needs a full entry. Also, it has a distinct pronunciation and ] and foul are not close cognates, so they don't seem to be alternative forms of one another. One foul swoop seems to refer to (be derived from) one fell swoop. If one foul swoop gets the main entry I think it deserves, then in one foul swoop should redirect thereto. DCDuring (talk) 16:59, 5 January 2023 (UTC)Reply
Agreed. As in one fell swoop redirects to one fell swoop, redirecting in one foul swoop to one foul swoop would seemingly be the only logical and consistent course of action. --Overlordnat1 (talk) 11:43, 6 January 2023 (UTC)Reply
Latest comment: 2 years ago3 comments3 people in discussion
parlez vous, parleyvoo, and parley-vous whilst having the exact same meanings and roughly the same pronunciation, all have their own pages and the others are listed as synonyms. Two have the meaning of “a Frenchmen, one has “the French language” and all of them have “to speak a foreign language, especially French”. Are these all not the word, with differing spellings? -CanadianRosbif (talk) 10:37, 7 January 2023 (UTC)Reply
We should probably merge them into parlez vous but list the other two spellings as alternative forms. There is also the song 'Mademoiselle from Armentieres' aka 'Hinky Dinky Parley Voo' which has the form parley voo, the spaced version of parleyvoo, though I don't think this bawdy WW1 song would be a good example to include in our entry, fun though it is, as it's not clear what the final refrain of parley voo at the end of each line is actually supposed to mean. There is also a version that appears in the final credits of Peter Jackson's film They Shall Not Grow Old which can be found on YouTube and which is where I first came across the song. --Overlordnat1 (talk) 02:21, 8 January 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
Merge into Reconstruction:Proto-Indo-European/(s)mel-. Most modern sources agree these are part of one and the same root. The only descendant that (traditionally) requires PIE *a is Latin malus, which fits semantically better with the gloss at *(s)mel- anyway. In fact it is unnecessary to reconstruct *a at all, in light of *mo > *ma unrounding in an open syllable with coda resonant (see de Vaan:2011 p. 8: 7.1; p. 360), the same process that resulted in mare(“sea”) < *móri. In any case the reconstruction of the vowel is irrelevant to whether the Latin, Slavic and Germanic words are cognate, despite the last sentence of the Latin etymology 1 described at malus. — 69.121.86.1319:31, 3 February 2023 (UTC)Reply
Latest comment: 2 years ago3 comments2 people in discussion
English.
As the entry says "capitalization varies". I see no compelling reason that this shouldn't be a noun sense at boot with "always with 'the'", or something of the sort. Chuck Entz (talk) 23:43, 18 February 2023 (UTC)Reply
The Boot meaning the Saatse Boot should be somewhere uppercase, I think, whether Boot or the Boot or The Boot I'm not entirely sure, because it functions as a proper noun place name. I'm not familiar with how the (b/B)oot meaning Louisiana is used; in the one cite in the entry, or others I can image like referring to LA as America's boot, it seems like a metaphorical general sense for something or somewhere boot-shaped. So it may be an RFV question, does Saatse-style use as a proper noun place name exist (for either place ... I can't actually find the Saatse one in books, either, only online). - -sche(discuss)17:51, 24 April 2023 (UTC)Reply
Latest comment: 4 months ago8 comments8 people in discussion
The forms with noses are pretty dated at this point and not in widespread use. I think it'd be better if the noseless forms were the main entries, perhaps with a note on the older forms indicating that they were used first. Binarystep (talk) 20:24, 25 February 2023 (UTC)Reply
Noseless variants are also more common in East Slavic languages, albeit eyeless-and-noseless variants are more frequent. However I can’t find data regarding this, I am speaking solely from my experience. БудетЛучше (talk) 20:11, 6 September 2024 (UTC)Reply
I'm not sure these should be merged. Nowadays, the nosed forms carry a (context-sensitive) marked nuance beyond our usage note of "used by older people", just as do =) or (: – compare to 🙃 – or :^) – which has no entry. Maybe unhelpfully, I don't know exactly how we would define it, but they at least do not seem interchangeable. Compare the slightly smiling vs. smiling emojis on many platforms, 🙂 and ☺ and see here, or :o) (can't link our entry, I've never associated this with a clown nose) and :0) or :O). Hftf (talk) 12:03, 19 February 2025 (UTC)Reply
Latest comment: 2 years ago10 comments5 people in discussion
We have two different entries for the same thing, while links generated with {{m}} or {{l}} like *vьśegъda link to the latter (vьsegъda) as they seem to ignore ś in Proto-Slavic reconstructions which IMO is unexpected. This makes the former (vьśegъda) being ignored and forgotten recently. I guess both entries should be merged and the language modules should be tweaked to make Proto-Slavic stuff ś-aware? // Silmeth@talk12:28, 15 March 2023 (UTC)Reply
@Silmethule Converting ś to s seems intentional, and asserts that there's no separate ś phoneme in Proto-Slavic. Reconstructing ś seems ahistorical to me; it's rather that the third (and second ...) palatalizations occurred post-Proto-Slavic. Benwing2 (talk) 06:27, 16 March 2023 (UTC)Reply
@Benwing2: but it has different reflexes in different branches. So, either those palatalizations happened post-Proto-Slavic and *ś is a valid dia-phoneme projected back and reconstructing *s in those places for Proto-Slavic is wrong, or it was an actual Proto-Slavic phoneme with some value separate from both *s and *š that merged with those at a later stage – in which case we’re justified to reconstruct *ś and *s is wrong. In either case, unless we undo all progressive and 2nd regressive palatalizations of *x (and all the other sounds? there are traces of non-palatalization in *otьcь in the east too), we need to treat *ś as a (dia)phoneme of its own and *s is wrong. Also WT:About Proto-Slavic seems to treat *ś as a separate phoneme (and even ascribes a specific IPA value to it). // Silmeth@talk10:00, 16 March 2023 (UTC)Reply
@Benwing2: What primary sources? Proto-Slavic is a reconstructed, not directly attested, language.
If you mean etymological dictionaries and historical linguistic papers – depends, you get all sorts of things (*vьšь in Polish dictionaries, *vьsь in some southern ones, non-palatalized *vьxъ in Vasmer, etc.) – although in general progressive and 2nd regressive palatalizations are commonly marked. But *x is problematic as it has different reflexes in the west vs south+east; hence Derksen’s notation with *ś, as he puts it:
The introduction of *ś, on the other hand, could not be avoided, cf. *vьśь ‘all’ vs. *vьsь ‘village’
I already agreed that we should use ś. Third palatalisation is only absent in Old Novgorodian and most of our entries already do apply the sound law to stops, so I don't see why we should treat the sibilant any differently. Thadh (talk) 22:23, 16 March 2023 (UTC)Reply
I don't think this would normally be spelled with a hyphen, at least not as a verb. heave-to with a hyphen looks like a noun, probably meaning "the act of heaving to", though as a landlubber I don't know if such a noun exists. —Mahāgaja · talk10:47, 24 March 2023 (UTC)Reply
You may be right as kaffir seems to be slightly more widely used than kafir, though oddly enough we (and Wikipedia) have an entry for Kafiristan and not Kaffiristan (which is a far more prevalent form on GoogleBooks). Though on a raw Google search 'Kafir' is twice as popular as 'Kaffir' and 'Kafiristan' is a lot more popular than 'Kaffiristan' and there does seem to be a slight tendency of late to differentiate the 2 words so that 'kaffir' is the Souh African insult and 'kafir' is the Islamic one. --Overlordnat1 (talk) 09:06, 13 April 2023 (UTC)Reply
My perception (which seems to agree with yours) is that, when it's used in the sense of "infidel ," in contemporary "Western" English, the word is almost always spelled with one "f." (I have few or no observations of how it's spelled in, say, Nigeria, or Pakistan.) That's true both of use as a self-description/reclaimed slur, and use by Muslims.
I'd guess that the two-to-one ratio in Google search results is a severe underestimate of this tendency, given that it will also include racial and ethnic uses, references to "kaffir corn" and "kaffir limes," uses in much older documents, etc.
Notably, all of the news articles I've seen talking about Hegseth's tattoo are using a single-f spelling. That's anecdotal, but probably could be quantitatively analyzed fairly easily (compared to a far greater difficulty for "all uses in which it means 'infidel'").184.75.151.21322:10, 5 April 2025 (UTC)Reply
As an extra data point and excluding terms like kaffir corn and kaffir lime, Google NGrams shows kafirs to have been more common before 1940 (much more common from 1900), then neck and neck with kaffirs from the mid-1940s to the present, but leading by a nose in this millennium.
I suspect this means that some uses occur with one spelling and others with the other, perhaps more or less following our current entries. This would need to be verified for the non-slur definitions, I suppose. DCDuring (talk) 14:23, 6 April 2025 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
So from doing a lot of research and hearing testimonies from elders who speak this North African Judeo-Spanish language, I think there should be a separate list and code for Haketia. It has been associated as just a dialect of Ladino but that is not the case. Haketia has consonants and words directly from Arabic that are never used in Ladino as well as an array of different phrases and spellings. It is a separate language. Let me know if this can be done. I have a lot of words, pronunciations and phrases ready for adding to it after it is set up. Shukur/thanks. Nevermiand. (talk) 18:43, 16 April 2023 (UTC)Reply
IMO these are usually uncapitalised in later use, though it's quite hard to tell because it's usually the first thing in a sentence so gets a capital anyway. And older texts, pre-mid-19th century, would capitalise nouns fairly commonly anyway. But conventionally ods bodikins, od rat it, odzooks etc. are written with small Os. The OED and Chambers both lemmatise od and derivatives uncapitalised. Ƿidsiþ13:32, 18 September 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
“akrasia” is currently listed as the alternative spelling of “acrasia”, which contradicts Wikipedia, as well as the fact that “acratic” is (correctly) listed as the alternative of “akratic”. Also, “akrasia” has 4.5× as many Google results as “acrasia” does. (There’s probably a better metric I could cite, but oh well.) IMO we should swap the two and make “akrasia” the main one. —Will • B23:30, 5 May 2023 (UTC)Reply
Other static copulas can replace be. Should we consider be a generic static copula as we might consider do a generic transitive verb and something a generic NP? DCDuring (talk) 01:17, 18 September 2023 (UTC)Reply
@76.100.240.27 How is the idiomatic meaning of trust someone to used in a sentence? Would one say, "I trust her to spend all day reading" to mean "It is predictable for her to spend all day reading"? If so that makes our current gloss unsubstitutable. Is it ever used without any words between trust and to? If not I think we should not move it. — excarnateSojourner (talk · contrib)16:34, 22 May 2023 (UTC)Reply
I agree that trust to is a worse location for the expression than trust someone to, though both are worse than trust + to, IMHO.
Doesn't whip it on require a person (or personified object) as complement? I suppose we could handle that with a label. Also. it is possible that there might be another meaning involving inanimate objects or other expressions. I would probably then be easier on users to be able to compare meanings. DCDuring (talk) 00:42, 23 May 2023 (UTC)Reply
I would not move this entry. People say "I put it behind me" and "You need to put it behind you and move on", not *"I put it behind myself" and *"You need to put it behind yourself and move on". —Mahāgaja · talk06:48, 23 May 2023 (UTC)Reply
Latest comment: 2 years ago1 comment1 person in discussion
molly-mawk is given as an alternative form of mollemoke, and not of mollymawk. The etymologies given for those two are half-different too, while both mention fulmars. There's probably some obsolete taxonomy in there too, so a taxo-specialist's eyes would be more than welcome. Skisckis (talk) 20:40, 11 May 2023 (UTC)Reply
@Elevenpluscolors Per the OED entry, no, it shouldn't be split but geological senses (and probably the cuckold sense too) should be separately listed as appearing with a lower-case initial letter. Whichever is currently the more common form should be the main entry. The other one should still have those senses but use the template for alternative case form of. — LlywelynII22:04, 9 June 2023 (UTC)Reply
I am familiar with the similar queer the deal, defined by "NetLingo" as "To ruin a potential business deal or arrangement despite all favorable odds. For example, 'They are a liberal company, so don't queer the deal by letting them know our conservative tactics.'" The "deal" version is more common with "the" than with possessive pronouns. But I wonder whether the right approach isn't to make both the "the"" and the "someone's" versions redirect to the right sense of queer#Verb, adding usage examples there. DCDuring (talk) 20:15, 28 June 2023 (UTC)Reply
It looks like the only quotations for cotton could be moved to one of the other two. Unless someone has a quote without a preposition/with other prepositions, that would seem to be the best solution. Then the verb entry at cotton could simply be deleted. Mazzlebury (talk)
The meaning embodied in the various expressions, as well as that in take a cotton to, clearly needs its own entry. I'd argue it is at least as sensible to delete the various cotton + PREP entries. We also need a noun PoS section for this etymology of cotton. DCDuring (talk) 13:57, 25 March 2025 (UTC)Reply
It would be better if we had some evidence for all similar cases. OTOH, if we think new normal users are able to use the failed-search page, then they would find ], even if they searched for "the bee's knees" (and vice versa). I personally think that normal users can't be assumed to make good use of that page. DCDuring (talk) 12:53, 8 August 2023 (UTC)Reply
We are quite inconsistent about whether we include the or not, e.g. cat's pyjamas redirects to the cat's pyjamas, contrary to the direction of the the shits → shits redirect. It would be better to try to decide on a general approach rather than move entries piecemeal. DCDuring, you argued in favor of redirecting verb oneself to verb even when it's never attested other than with a reflexive pronoun; it seems to me the same logic would make it better to centralize content at bee's knees, too. "The" is dropped from constructions like this when they're used attributively and in certain other cases (peruse the cites at google books:"and bee's knees"), and in headlinese ("Mayor Says New Parks Are Bee's Knees"). I pointed this out about Talk:The Rock, too. - -sche(discuss)16:15, 16 August 2023 (UTC)Reply
@Benwing2: it seems like {{circa}} and {{circa2}} serve different purposes. The template {{circa}} (and {{ante}} and {{post}}) appear to have been created for quotations in entries that do not use quotation templates. That is why the year appears in bold and there is a comma after the year. On the other hand, {{circa2}} is for adding circa or c. before a year in other contexts, such as in etymology sections or image captions. I suppose {{circa}} and {{circa2}} could be merged, but then some parameter would have to be added to allow for switching between the two formats. Alternatively, if all quotations using {{circa}}, {{ante}}, and {{post}} were replaced with quotation templates, then {{ante}} and {{post}} could be eliminated and {{circa2}} could be renamed as {{circa}}. — Sgconlaw (talk) 05:55, 2 August 2023 (UTC)Reply
@Sgconlaw I have eliminated the aftercomma from {{circa}}, {{ante}} and {{post}}. What differences remain? Just the boldface? That seems a pretty small thing to have two templates for, esp. given the horrible naming. Benwing2 (talk) 06:17, 2 August 2023 (UTC)Reply
{{quote-book|en|year={{ante|1597}}|first=William|last=Shakespeare|authorlink=William Shakespeare|title={{w|The Merry Wives of Windsor}}|section=Act 3, Scene 5|passage=No, Master Brook, but the peaking '''cornuto''' / her husband, Master Brook, dwelling in a continual / 'larum of jealousy, comes me in the instant of our / encounter, after we had embraced, kissed, protested, / and, as it were, spoke the prologue of our comedy}}
I am cleaning all of them up to use e.g. a. 1597 instead. Note that |origyear=, |year_published=, etc. now support a., c. and p. prefixes. Benwing2 (talk) 08:22, 13 August 2023 (UTC)Reply
Hmm. I would not merge these as things stand now, with them having the differences re bolding that they do, and the differences in where they're used: they currently serve different purposes. (Since we don't normally bold years in etymologies, descendants lists, etc, a template used in etymologies to qualify a year as circa shouldn't bold the year either, whereas we do normally bold years at the start of quotation metadata, so a template that supplies circa there should bold the year.) However, if we replace all of the relatively few (~680) uses of {{circa2}} with just the spelled-out word "circa" — formatted however: "circa", "c.", whatever we decide — rather than a template, we could just delete {{circa2}}. And/or if we made sure all uses of {{circa}} were inside quotation templates (not manually-formatted quotations), then we could presumably have the quotation templates know that if year={{circa|####}}, then format #### in bold (but don't bold circa?), and then if {{circa}} and {{circa2}} stopped differing in the formatting they apply, they could be merged. - -sche(discuss)16:06, 16 August 2023 (UTC)Reply
Was the ping specifically to this discussion? Fascinating. (If it was just to this general page, I might speculate that my recent removal-then-readdition of a bunch of discussions pinged people somehow, even though it shouldn't because I think you have to add four tildes at the same time as linking someone's username to ping them.) Pings seem to be wonky lately; AG202 pinged me in an edit summary on this entry recently and I didn't get the ping, only noticing that it existed because I had the entry in my watchlist and was looking at the edit history. - -sche(discuss)14:59, 29 March 2024 (UTC)Reply
@-sche @Sgconlaw I just got a bunch of pings that claim to be from -sche but were actually old responses of mine *TO* -sche. Strange. As for {{circa2}}, I am not sure anymore; I think when I looked into this awhile ago, I concluded they indeed serve slightly different purposes, although the naming is definitely bad. Benwing2 (talk) 19:32, 29 March 2024 (UTC)Reply
I notice all the pings are from 6 hours ago and are in WT:RFM specifically, so I think they are indeed related to your removal/readdition of discussions at that time. Benwing2 (talk) 19:38, 29 March 2024 (UTC)Reply
@-sche: when I clicked on the notification I was led to this discussion. Anyhoo, about this discussion, @Benwing2: what about changing {{circa}} to {{circa-quote}}, and {{ante}} and {{post}} similarly since they are all intended only for use with quotations (though they should be phased out in favour of the {{quote-*}} templates), and then renaming {{circa2}} to {{circa}}? Would that be confusing? — Sgconlaw (talk) 19:43, 29 March 2024 (UTC)Reply
All three -- {{lj}}, {{jaru}}, and {{ruby/ja}} -- were the creations of Fumiko Take. They did very little to document any of the templates or aliases they created, and if dim memory serves, they were even aggressively oppositional when asked to provide documentation.
Stepping back -- what is the use case for this infrastructure? Do we not already have functional ruby text provided by {{ja-r}}?
Granted, {{ruby/ja}} offers the ability to specify arbitrary ruby text -- but I struggle to think of when we'd actually want that. It's used to great effect in manga, when authors will not uncommonly spell a word to convey a particular sense, and gloss it with ruby to indicate a different word entirely -- but for a dictionary, this is aberrant behavior outside of direct quotes of such texts. I suspect that, in most cases, {{ja-r}} would do just fine for our needs.
Stepping back a bit further -- do we need ruby text at all?
Serious question. Tiny kana over the kanji is something that only provides value to people who can already read kana, and is otherwise likely to confuse anyone unfamiliar with Japanese typography (which is probably the greater part of our user base). If a given user can already read kana, they are likely to be savvy enough to be able to match up any provided romanized string to the kanji, much as we get when using {{m|ja|TERM|tr=romanization}}.
I argue that kana ruby text over kanji is snazzy, but it also presents usability issues.
@Eirikr I'm in full agreement that these are superfluous to {{ja-r}} (and {{ryu-r}}), but I disagree that we should be getting rid of rubytext. I think the aim should be to incorporate rubytext into {{l}}, {{m}} (et al). The infrastructure for language-specific formatting in links already exists (and is already used by Chinese and the Chinese lects to generate simplified forms), so we could add something for the Japonic languages that essentially reimplements {{ja-r}} (for the relevant language). Theknightwho (talk) 22:09, 15 August 2023 (UTC) Forgot to ping Benwing2. Theknightwho (talk) 22:12, 15 August 2023 (UTC)Reply
Just to add a bit further to this - I'd also like to automate much of the kanji/kana mapping which is currently necessary with {{ja-r}}. It won't be possible to do away with it entirely, due to redlinks or when there are multiple possibilities, but {{ja-pos}} (and all the other headword templates) are able to do this already by looking at the input for {{ja-kanjitab}}, so there's no reason why link templates shouldn't be able to do this as well.
This would greatly simplify a lot of the complexity encountered when adding Japanese links, which would help with the usability issues Eirikr mentions. Theknightwho (talk) 22:17, 15 August 2023 (UTC)Reply
Blah. So much crappy East Asian code (and templates) out there. Even if the conversion is possible auomatically in only say 80% of the cases, that would probably be good enough, as we can do the remainder by hand or just leave them. If for example there are cases that can be handled using {{ruby}} and not with {{ja-r}} that is probably fine, but we should not have two ways of doing the same thing and randomly use one or the other. Benwing2 (talk) 23:31, 15 August 2023 (UTC)Reply
@Benwing2 Yeah, I suspect a conversion is possible, and as a last resort 1,000 uses is doable manually if a few of us handle it.
@Theknightwho, my usability concern is not about editing, it's about reading, and about accessing the text as it is rendered in the browser.
On the reading side, things like 漢方(kanpō) are visually unclear to anyone not already somewhat familiar with Japanese typography -- it looks like the entire block of kanji + furigana together is the Japanese "word", ruby and all, when in fact the Japanese term is 漢方. Even if a reader understands that the ruby text is not actually part of this term, the kana are only useful for someone who already knows how to read kana. The kana are also superfluous, as we already include a romanization, which provides the same information just in a different script.
In terms of the accessibility of the rendered text, for reasons obscure to me, the <ruby> element in the HTML seems to render the Japanese term un-copyable. If I select the text "things like 漢方(kanpō) are" as rendered, and hit CTRL+C and then try to paste that somewhere, I only get "things like (kanpō) are" -- the Japanese text itself is missing entirely. Meanwhile, if I select the text "the Japanese term is 漢方." and do the same, I get "the Japanese term is 漢方." -- the pasted text includes everything I expected.
@Eirikr I think realistically, most Japanese entries are going to be used by people already familiar with Japanese enough to know what the function of the rubytext is. Although we’re a dictionary in English, that doesn’t change the reality that most dictionary entries are of little use to a complete novice.
You’re right about there being an issue from a copy and paste point of view, and it’s something that it would be good to solve if at all possible. I’m sure there is a solution, but I’d need to look into it. Theknightwho (talk) 23:07, 15 August 2023 (UTC)Reply
Also, just adding that the rubytext does actually serve an additional purpose to the romanisation, as it shows the reading for each kanji; romanisation can’t do that (unless we used rubytext for that instead, which I don’t think would be very helpful as it wouldn’t show semantic word breaks). Theknightwho (talk) 23:14, 15 August 2023 (UTC)Reply
If folks are familiar enough with Japanese to where they understand both kana and how furigana (kana used as ruby text) work, then they also have some idea of how Japanese phonemes break down, and how kanji readings work -- so again, furigana wind up largely superfluous to the only audience that knows how to use them.
I really think we (speaking generally) get too caught up in technical details and the coolness factor, and lose sight of usability and usefulness. Outside of those manga-esque cases were the spelling and the intended reading are really orthogonal, like 騎士(naito), I honestly don't think that furigana are useful enough to offset the negative impacts on usability.
... One idea occurs to me. Is there any easy way of toggling ruby display on and off? Thinking further, would there be any way of indicating in the wikicode if ruby is really needed (as in the 騎士(naito) example, otherwise anyone who can read Japanese that looks at 騎士 would expect to read it as kishi), or if the ruby is optional (such as when the ruby just indicates the regular reading of a given spelling)? ‑‑ Eiríkr Útlendi │Tala við mig19:51, 16 August 2023 (UTC)Reply
@Eirikr I know next to nothing about Japanese but I can see how ruby text is useful. For example, I can read Cyrillic but I don't know the ins and outs of irregular pronunciations in Russian; in cases like that we show a respelling in Cyrillic as well as give the IPA, and I think the Cyrillic respelling is useful. I imagine there are plenty of Japanese learners who will be able to read Hiragana (it's probably one of the first things taught) but have difficulty with Kanji (keep in mind it takes around 10 years for native speakers to learn to read and write Kanji, and probably only a few weeks to learn Hiragana). Benwing2 (talk) 20:30, 16 August 2023 (UTC)Reply
I was afraid of some confusion, and indeed, here we have it. :)
Speaking specifically about ruby for Japanese -- I grant that there are plenty of other use cases in other languages. By no means do I advocate for getting rid of {{ruby}}. I'm looking solely at the use case for {{ruby/ja}} and redirects.
@Eirikr The ruby text seems to allow for convenient markup of running Japanese text without interrupting the flow; putting romanizations in parens in the middle of a sentence would interrupt the flow, which is why it gets added at the end. I could imagine putting romanization in ruby text but it seems that isn't conventional. Benwing2 (talk) 21:05, 16 August 2023 (UTC)Reply
{{usex|ja}} and {{ja-usex}} put romanization afterwards, not mid-text. I can't think of any case where a romanization would be inserted in the middle of an otherwise-running Japanese text.
{{usex|ja|これは見本です。|This is an example.|tr=Kore wa mihon desu.}} →
これは見本です。
Kore wa mihon desu.
This is an example.
{{ja-usex|これは見本です。|これ は みほん です。|This is an example.}} →
{{ja-r|これは見本です。|^これ は みほん です。|This is an example.|linkto=-}} →
これは見本です。(Kore wa mihon desu., “This is an example.”)
In terms of the wikicode used to call the templates, I'd argue that {{ruby/ja}} is more of a mess, and the syntax is confusingly different from the rest of our Japanese infrastructure.
From the markup example on the Module:ja-ruby page (what {{ruby/ja}} actually invokes):
(ふ)り]](が)(な)]]
Yuck. Granted, part of the problem here is borderline link abuse, but by way of comparison, we could use {{ja-r}} to similar effect, with a more straightforward syntax:
Separately, in looking for examples of {{lj}} just now, I'm finding cases where {{lj}} seems to have been used as a replacement for {{lang|ja}} -- there are no ruby characters provided. See this snippet of the wikicode source at 会う#Japanese, for instance:
@Eirikr For reference, on MacOS, using Chrome, when I copy the text with Ruby in it and paste it into TextEdit I get this:
things like 漢方
かんぽう
(kanpō) are
The same thing happens using Safari, which suggests it's an OS issue, although possibly there are carriage returns in the underlying text that are leading to this. Benwing2 (talk) 23:10, 15 August 2023 (UTC)Reply
Geez. I asked this one in February and again in March to update the documentation of Module:languages/data/2 for the "generate_forms" stuff that is otherwise largely unexplained. With the promise "I'll add it shortly" half a century passed and the documentation is still nowhere to find. Now he suddenly jumps out and complains how Japanese does not follow the Chinese model... -- Huhu9001 (talk) 01:54, 16 August 2023 (UTC)Reply
@Huhu9001, Eirikr My original proposal was to rewrite {{lj}} and {{jaru}} into {{rja}} as a shortcut for {{ruby/ja}}, but given what Eirikr says, maybe we don't need either of them, or {{ruby/ja}} for that matter. It sounds like maybe the best thing is for {{ruby}} to take a language code and use it to wrap the generated text appropriately, and to simply use {{ruby|ja|FOO}} when you really need to display arbitrary ruby that can't be handled by {{ja-r}}. Then we can get rid of {{ruby/ja}} and its shortcuts. Thoughts? Benwing2 (talk) 19:42, 15 August 2023 (UTC)Reply
T:ruby sometimes serves to prevent double wrapping of language HTML classes, mainly in |title= or |chapter= of quotation templates, like this one |title={{lw|ko|s:님의 침묵/생의 예술|{{ruby|(생)의 (예)(술)}}|tr=Saeng-ui yesul}} in 열.
@Huhu9001 We seriously need to avoid having to wrap one template in another. Maybe we need to make {{ruby}} smarter so that it can handle cases like the one above. Can you enumerate other cases where {{ruby}} gets wrapped in another template, or vice-versa, that can't simply be replaced by the equivalent of {{lang|FOO|{{ruby|...}}}}? Benwing2 (talk) 03:43, 16 August 2023 (UTC)Reply
There are some cases when you want to ruby only a part of text. Then it can be done like: {{lang|LANG|unrubied text, blahblah, {{ruby|somehow rubied text}}, more blahblah}}. One such usage is in 閣下. -- Huhu9001 (talk) 04:14, 16 August 2023 (UTC)Reply
Sometimes wrapping the whole text produces repetition. It may become:
{{lang|LANG|unrubied text, blahblah, {{furigana|text to be rubied|ruby}}, more blahblah}} vs
{{furigana|LANG|unrubied text, blahblah, text to be rubied, more blahblah|unrubied text, blahblah, ruby, more blahblah}}
Sometimes the wrap is not t:lang. It may be t:quote, like when you have {{quote|ja|text=(ruby text)...}}. How do you "wrap the whole text" for this one?
@Huhu9001 You need to think outside the box a bit. For #1, we're talking for the moment about {{ruby}} not {{furigana}}, but {{furigana}} can be made smarter like {{ruby}} is, so that you can annotate part of the text. For #2, {{quote}} should be modified not to language-tag text that already is language-tagged, so it's OK to write {{ruby|ja|...}} inside of {{quote}}; and/or we make a ruby-quote template, similar to how we already have {{ja-x}}; and/or we add built-in support to {{quote}} for ruby text. In general, having to manually wrap using both {{lang}} and {{ruby}} inside of each other is super ugly and should be avoided. Benwing2 (talk) 05:22, 16 August 2023 (UTC)Reply
@Huhu9001 What I'm probably going to do is modify {{ruby}} so it takes a language param, but you can write {{ruby|-|...}} to force no language wrapping, so that if you really want to embed one template in another, you can do it without fear. Benwing2 (talk) 05:27, 16 August 2023 (UTC)Reply
I don't see any real need for {{lj}} or {{jaru}}, but I haven't looked at any current uses. It seems to me that {{ruby|ja|}} should suffice. As regards e.g. {{ja-r}}, it makes sense to me to use hiragana ruby with kanji, as this is fairly commonly done in Japanese-learning materials. It seems to me (again naively, without having done any specific research into the question) that users are likely to include a fair number of Japanese language learners. Cnilep (talk) 01:49, 16 August 2023 (UTC)Reply
@J3133Done. Multiple official sites indicate that the official name is Commonwealth of The Bahamas with capital T. I've cleaned up the entries accordingly. Benwing2 (talk) 20:24, 1 June 2025 (UTC)Reply
Latest comment: 1 year ago5 comments3 people in discussion
Translingual.
Asked to request a move because this is not attested as 'translingual', being so far found only in Northern Thai. I don't know why we'd want to request a move rather than just fixing the section header. kwami (talk) 14:14, 27 August 2023 (UTC)Reply
Latest comment: 1 year ago2 comments2 people in discussion
The same sense is in both places; it shouldn't be. Either leave it at hinge where it has a usage note about the "(up)on", or move it to hinge upon and reduce the relevant sense-line at hinge to a {{used in phrasal verbs|en|hinge on}} pointer. - -sche(discuss)01:16, 7 September 2023 (UTC)Reply
'Druther have a redirect from hinge on to hinge. Personally, I am loath to assert that hinge onis a phrasal verb. If it really is one, we should have an entry for it.
I would vote for putting the sense under the top one, because that's where people will look for it. Additionally, even if the true etymology is from Latin, it's certainly not widely seen that way, since people will say "I second this" ... "I thi0rd this", and so on, rather than using whatever the appropriate Latin word would be. —Soap—16:53, 9 September 2023 (UTC)Reply
All senses are from Latin, displacing native twoth. The problem here is that the "agree" sense is partly (and originally) from Etymology 3, and partly rederived from Etymology 1. Rather than reduplicating the sense a better solution would probably be to stick to one section and note the reinforcement in the etymology. —Al-Muqanna المقنع (talk) 18:24, 9 September 2023 (UTC)Reply
Rather, it muscled in on the territory of native other, for which at Wiktionary we have to go back to Old English ōþer. I can only find twoth as part of a compound ordinal, which is a new function for the meaning 'second'. --RichardW57 (talk) 23:44, 9 September 2023 (UTC)Reply
Latest comment: 1 year ago1 comment1 person in discussion
There are two senses which are probably the same. Etymology 3 - A hollow; a valley, especially the upper end of a narrow mountain valley when it is nearly encircled by smooth, green slopes; a combe. and Etymology 4 - A sloping plain between mountain ridges Jewle V (talk) 18:48, 14 September 2023 (UTC)Reply
Latest comment: 1 year ago10 comments4 people in discussion
English. To be moved to be going to. Most modern grammars and some dictionaries treat be going to (" ~ will") as an idiom. The inflection line for ] has long been "(be) going to". Edit summaries show that contributors here have thought the expression included be. I can't think of another copula that could substitute for be. I also can't picture anything other than adverbials like yet, still, later, and some other short temporal adverbs (with or without not) appearing between be and going to. IOW, it's close to being a set phrase. The adverbial insertions would look good in some of the usage examples. DCDuring (talk) 18:51, 14 September 2023 (UTC)Reply
Yeah, I did wonder about that after writing the above and apparently in Early Modern usage (according to the chapter I cited as a source for the etymology) it appears without be as well. So I'm not sure. It might be worth first collecting attestations without "be" to verify how to treat the elided use (e.g. it could be moved and the elided version turned into an informal altform). —Al-Muqanna المقنع (talk) 18:08, 19 September 2023 (UTC)Reply
Aren't are our normal users better off with a main entry at an unelided form with redirects from any elided forms. In this case, were we to have an additional entry at going to, we should have at least three definitions at going to, to wit, 1., "elided form of be going to; 2. Used other than figuratively or idiomatically: seegoing, to.; 2.1 "moving toward" (subsenses for 2.1.1 progressive verb, 2.1.2, for gerund?); and, possibly, 2.2, et seq. DCDuring (talk) 22:11, 19 September 2023 (UTC)Reply
I think I'm thinking of the "be elision" kind of as "be elision" in other cases, such as with "be" + adjective. In other words, the "be" is not core to the construction. But perhaps this is debatable. — justin(r)leung{ (t...) | c=› }02:49, 20 September 2023 (UTC)Reply
Surface comparisons can be misleading. English has lots of collocations that seem word-by-word analogous, but behave differently. I think supposed to is a false parallel. Supposed to can (infrequently) be used with other copulative verbs. I'd like to see evidence that going to is used without be in recent (~200 years) English. The few (2) other OneLook dictionaries (MWOnline, Collins) that cover (be) going to cover it at be going to. DCDuring (talk) 11:58, 19 July 2024 (UTC)Reply
Latest comment: 1 year ago1 comment1 person in discussion
English. I have moved senses (and their translations) between on the way and on one's way, making on the way a lemma with most of the definitions from on one's way rather than an alternative form. It occurs to me that there might be a pondian difference that would account for the previous arrangement. In any event, please review the changes. DCDuring (talk) 15:00, 23 September 2023 (UTC)Reply
October 2023
Articles with national anthems
Latest comment: 1 month ago5 comments3 people in discussion
Well if some national anthems are referred to with an article and some without I think it would be more helpful for us to document these differences (as we seem to be doing) rather than creating and imposing an artificial consistency. Besides, isn't The in The Call of South Africa part of the official title of the song? Wouldn't removing it be like removing The from The Lion, the Witch and the Wardrobe? — excarnateSojourner (ta·co)20:22, 15 January 2025 (UTC)Reply
@ExcarnateSojourner: The in The Star-Spangled Banner is also part of the official title of the song. Wiktionary has the wrong titles instead of, as you assumed, differences that we are documenting instead of imposing an artificial consistency. J3133 (talk) 07:22, 25 March 2025 (UTC)Reply
Oppose – The citations for both senses almost exclusively feature the hyphenated form. Google Trends results shouldn't be the guidepost here. This would also create unnecessary asymmetry with the antonym anti-shipper. WordyAndNerdy (talk) 23:00, 29 May 2024 (UTC)Reply
@WordyAndNerdy: The citations for the second sense are from print media, which doesn't reflect common usage of the term. If we included social media citations (which we could, per current policy), proshipper would outnumber pro-shipper 10-to-1. As for the asymmetry, this assumes that anti-shipper is more common than antishipper, which isn't necessarily true either. Hyphens in general are becoming increasingly uncommon in English, and slang terms like proshipper are naturally some of the first to reflect this trend. Incidentally, this is why I don't think the citations for the first sense should be counted in this discussion – that sense is rather dated, and not really used anymore in fandom spaces. I don't think it benefits readers to have the lemma form be at a spelling that they're unlikely to even encounter in the first place. Binarystep (talk) 10:48, 30 May 2024 (UTC)Reply
Unhyphenated forms may occur more in online spaces less for orthographic reasons and more as a product of often-poorly-punctuated informal Internet speech. We wouldn't have entries for hannigram or dni based on Internet-speak all-lowercase tweets like "proshippers dni, hannigram sucks" (the links are to the standard forms). This seems like a solution in search of a problem. The current weight of evidence supports the prevalence of the hyphenated form. I don't think we should set out to tip the balance in the other direction for prescriptive reasons. Readers can easily locate the current lemma through the unhyphenated redirect. WordyAndNerdy (talk) 11:15, 30 May 2024 (UTC)Reply
@WordyAndNerdy: There's a difference between all-lowercase typing (which is inconsistent with standard English orthography) and using prefixes without hyphens (which isn't grammatically incorrect). You're right, we wouldn't have entries for hannigram or dni – but we do have an entry for proshipper, because it's an equally valid spelling, not a mere error resulting from informal speech. Further proof is the fact that one can easily find plenty of uses from people who use standard spelling and punctuation. I also find it rather ironic that you'd characterize my reasoning as prescriptive, given that my argument is based solely on frequency of use; if anything, it's more prescriptive to invalidate proshipper on the basis of it being "a product of often-poorly-punctuated informal Internet speech". Binarystep (talk) 19:13, 31 May 2024 (UTC)Reply
Something I discovered while attesting comship/comshipper is that a not-insignificant number of people seem to regard proshipper (unhyphenated) as a blend of problematic + shipper. This strikes me as a rather unlikely folk etymology. Forgive the prescriptiveness but I now favour retaining the hyphenated form to avoid creating confusion over which etymology is more likely to be accurate. The pro- + shipper interpretation is better supported by evidence. WordyAndNerdy (talk) 08:14, 1 June 2024 (UTC)Reply
Oppose based on the cites. Google results are notoriously unreliable (they'll say a search finds X hits, but only display far less); I don't know if Trends are any better. - -sche(discuss)04:54, 30 May 2024 (UTC)Reply
Oppose (provisionally) - I have never seen or used the word, but I do see that Teen Vogue used the unhyphenated version at least once- see . I would like to see more citations on the unhyphenated version before a final analysis be made. I am always wary of downplaying of hyphenated words in favor of unhyphenated words because of what I dimly perceive to be a "systemic bias" (accidental or intentional) against hyphenated words on Wiktionary caused by various factors. --Geographyinitiative (talk) 10:09, 30 May 2024 (UTC)Reply
English slang terms whose usage is typically restricted to users of the website Reddit.
However, I am not sure that "Reddit slang" is a particularly viable subcat of "Internet slang"; a lot of these terms didn't originate on Reddit and aren't actually restricted to Reddit. It probably only seems that way because of the prominence of Reddit as a site where people use Internet slang heavily.
Even if "Reddit" isn't enough for a category, isn't it enough for its own label. And if a usage or, at least, a term originated in Reddit, shouldn't there be an etymology saying so? DCDuring (talk) 22:13, 6 April 2024 (UTC)Reply
I found 460 hits for "CBSテレビ", versus only one hit for "シービーエス・ソニーグループ" (CBS/Sony Group), in archives for Mainichi Shimbun. I would say the romaji is the common form, and should be used, if the proper name is kept. Cnilep (talk) 04:37, 9 September 2024 (UTC)Reply
Still not sure about Murex pecten's vernacular names.
The main issue here is strictly a matter of orthographic rules: how do you spell the combination of the possessive clitic, 's, with a word that ends in "s" in the singular? I was taught " s' ", but it looks like professionally edited works have used " s's " as well, or just avoided the issue by omitting the clitic. There's variation along those lines for both the plant and the mollusk. I suspect the differences in occurence of the spellings has as much to do with time and place of publication as with any difference between usage of the plant name vs. the animal name. Chuck Entz (talk) 02:17, 31 December 2023 (UTC)Reply
This seems like a cleanup operation, covering several entries and potential entries.
No other OneLook dictionary has open-pit mine. MWOnline, Oxford, Dictionary.com, and Collins have open-pit, Collins having it as a noun. (Attestable as noun, but SoP?) Also we have some of opencast, open-cast, open cast. We should use GoogleNGrams to determine the most common for each of the -pit, -cast, and -cut forms, use Google Books/News to determine which are attestable, include all attestable forms as alt forms, and make sure that at least the main forms show the main form of the other groups as synonyms. There is also the possibility that some of these are used adverbially. DCDuring (talk) 15:18, 19 January 2024 (UTC)Reply
Agreed. As a general rule we don't change the spelling of terms with Pondian differences once the entry has settled on one spelling or another. (There are exceptions, e.g. if British spelling allows both A and B equally and American spelling prefers B, I think it would be reasonable to move a term spelled as A to B.) Benwing2 (talk) 02:53, 27 January 2024 (UTC)Reply
If we check frequency, we should be ready to change which is the main entry. Google NGrams makes it easy, though it covers books (only?). Whether the criterion should be recent usage or all usage is a matter of judgment, at least for now. One can also search in News for usage by location (nation, province/state?) of the source. DCDuring (talk) 16:06, 27 January 2024 (UTC)Reply
Latest comment: 1 year ago3 comments3 people in discussion
I understand that the distinction between 's and -'s is that the former is a contraction of is, was or has and the latter is a possessive, but I think this distinction is likely to be lost on the majority of Wiktionary users and is better made by merging both pages to 's and making the distinction using different Etymology sections. As it is, there is some duplication between these two entries. Benwing2 (talk) 22:44, 31 January 2024 (UTC)Reply
(Oppose unless it can be demonstrated that we don't normally lemmatize suffixes like this at titles with hyphens.) I'm very sympathetic to the fact that content being somewhere that some people don't expect is a problem, and to need to prominently flag when content is on a different page than some people expect, not just in this kind of case, but also e.g. when we usually lemmatize singulars but occasionally put some senses at the plural, or usually lemmatize without the but occasionally have some senses at separate the X entries, or when we lemmatize phrasal verbs outside the main verb entry. I'm a big fan of Template:used in phrasal verbs and "See..." links like at message. But if lemmatizing the possessive at -'s is technically correct and is consistent with how we treat other suffixes, then we should continue lemmatizing at -'s and just take whatever other measures we can to obnoxiously prominently crosslink it to and from the other page... because if we make an exception and lemmatize this page at an incorrect title, it's inconsistent with other entries... do we also move -'#English? What about -'s#German and -'#German? What about -s? And that inconsistency confuses other users and editors who do understand our system, and look in the right/expected place, only to find that the content isn't there because we moved it to an incorrect/inconsistent place to try to outsmart them. I think we have to do things consistently (e.g. if suffixes usually start with hyphens, do so here too), and use prominent "See also..." links where necessary. For verbs linking to phrasal verbs, and for things like message, such links can just be on definition lines; here, I'd be fine with the link taking the form of a big T:LDL-esque yellow box or something if people want, if people feel a ===See also=== link is insufficient. Obviously, any incorrect duplication should be cleaned up. - -sche(discuss)14:31, 29 March 2024 (UTC)Reply
Latest comment: 4 months ago3 comments3 people in discussion
I can't find anyone reconstructing *kwh₂et-. Most sources seem to have trouble deriving the Slavic, Latin, and Armenian words from the same root. They probably don't belong here, but I don't know enough about these languages to decide. —Caoimhin ceallach (talk) 17:02, 23 March 2024 (UTC)Reply
Latest comment: 1 year ago1 comment1 person in discussion
English. Move/convert to Appendix. Any red-linked item included in this automatically causes that page to be "wanted" thereby clogging Special:WantedPages with pages almost all or all of the "wants" for which are created the template. There are now 13 such redlinks.
Latest comment: 1 year ago10 comments5 people in discussion
We give this as a noun, but our cite shows it's a verb that can occur in other tenses. Do we move it to tail wag the dog? Or do we consider it too awkward to find a tail-containing title for the verb to live at, leave the verb on wag the dog, and make this entry a phrase "the tail is wagging the dog"? Either way, it needs to be moved and re-POSed, no? - -sche(discuss)06:33, 19 May 2024 (UTC)Reply
As worded it is clearly and correctly an NP headed by tail.
The lexicographic issue is the appropriate headword, which, in our case, is influenced by our avoidance of the idiom PoS, MWOnline has "the tail wagging the dog" as an idiom. Most OneLook dictionaries don't seem to cover this at all. DCDuring (talk) 14:21, 19 May 2024 (UTC)Reply
@Benwing2 I think we should have a policy for phrases in English which can take multiple tenses, as this comes up relatively often and it would be nice to have something to point to (e.g. time stand still was recently moved to time stands still after quite a long thread at WT:RFDE). As with other parts of speech, I’d prefer we had a consistent lemma format, even if it’s not usually said that way (e.g. lemmatising at kiss one's ass goodbye, which I can only find one durable use for with the pronoun one, despite being relatively common). Theknightwho (talk) 11:58, 6 June 2024 (UTC)Reply
What should be the lemma? Should there be entries, redirects, or nothing for classes of the often-numerous alternative forms (variations in verb inflection, number, pronoun, determiners, grammatical structure, licensed adjective or adverbs, etc)? Do we have to research relative frequency of the forms to make these decisions? How should the variations be acknowledged on the lemma entry? What differences by language type or individual language? DCDuring (talk) 13:16, 6 June 2024 (UTC)Reply
This is the kind of thing that, I believe, other dictionaries cover in a style guide. We could use Wiktionary:Style guide as a location for a set of subpages on relatively narrow lexicographic issues, so that they would be easy to find. Entry types, like this one, that recur would benefit from some principles inferred from examples and will probably generate disagreement, but not major conflict. We could have votes and make individual subpages policy, but that should not be necessary. DCDuring (talk) 12:48, 6 June 2024 (UTC)Reply
@Theknightwho I totally agree. Sometimes I've moved pages to try to make them more consistent, which sometimes led to complaints, so I think a style guide or whatever would be very helpful. For example:
Those seem like good rules to me. There is an interaction with what I think is our preference not to have headwords with leading the. Also, to clarify, when you say infinitive you mean the 'bare infinitive', not the 'to infinitive'. When should something be used instead of someone? (Does it depend on the relative frequency of use of the expression with non-gendered things? Threshhold?) Are there circumstance in which we would go with a different lemma headword? Should we have alt form entries for some of the inflected and other variant forms or just hard redirects. I don't know how complete we should try to be. To much detail might delay implementation and course correction. DCDuring (talk) 01:53, 7 June 2024 (UTC)Reply
@DCDuring These are good questions. You are right that I mean "bare infinitive" rather than "to-infinitive". As for something vs. someone, I think if it can reasonably occur with both, one should be a soft redirect to the other. Generally I prefer soft redirects over hard redirects, although I understand that hard redirects are easier to enter. Another issue is, what's the inanimate equivalent of one's? Is it its? I will bring these rules to the BP and see what people say. Benwing2 (talk) 03:01, 7 June 2024 (UTC)Reply
Latest comment: 3 days ago6 comments3 people in discussion
It seems like this is just a capitalization of the lowercase common noun peraia when referring to a specific one. See Citations:peraia (one cite explicitly says ""The peraia" is not a place name but a common noun"). Should Peraia be moved to lowercase and redefined as a common (rather than proper) noun, maybe with the capitalized form left as an {{altcase}}? (Or, compared to e.g. "the boundaries of the (City|County|State|Province|Duchy|Kingom) in the area of the river", does the Greek-ness or some other factor make the meaning of the capitalized entry different or unintuitive enough that we should have both?) - -sche(discuss)18:46, 23 May 2024 (UTC)Reply
OK, I have moved it. The Latin (and modern Greek) translation is still capitalized because when I searched for that Latin word (albeit not exhaustively), I only spotted capitalized occurrences. - -sche(discuss)22:19, 23 July 2025 (UTC)Reply
While we’re at it, could we add an experimental parameter (to this and {{altform}}) that disables “standard” categorisation (like POS, gender, etc) and dumps words into a “ alternative forms and spellings” category? Nicodene (talk) 04:04, 29 May 2024 (UTC)Reply
@Nicodene There would have to be an extra setting passed to full_headword() in Module:headword that indicates that the term is an alt form, which would change the categorization to Category:Franco-Provençal alternative forms and spellings (or whatever) and would disable all the normal categorization into lemmas, by gender, etc. You'd then need to thread a param for this through the various frp-* templates. This is assuming you want whatever inflections/etc. get auto-generated by Module:frp-headword; if not, you could just say {{head|frp|alt form}} or whatever. Benwing2 (talk) 08:16, 6 June 2024 (UTC)Reply
I guess admins should still decide which languages (like Chinese) shouldnt be merged but have borrowed terms of a child language must be a subcategory of the parent language. Already working in derived terms, just need to be implemented with borrowed terms as well. 𝄽ysrael214 (talk) 20:59, 7 June 2024 (UTC)Reply
I don't understand why you want to treat these alternative forms differently than other alternative forms that have their own entries.... Kiwima (talk) 18:04, 8 June 2024 (UTC)Reply
Latest comment: 1 year ago18 comments5 people in discussion
"Aphetic form" is just a fancy way of saying "clipping at the beginning". I doubt we need to make such a fine distinction, and using opaque linguistic jargon is IMO not helpful. I propose eliminating "aphetic form (of)" in favor of "clipping (of)". Pinging User:PUC (creator of {{aphetic form of}}, with only 60 uses) and User:Adam78 (creator of {{aphetic form}}, with only 71 uses). Benwing2 (talk) 00:13, 9 June 2024 (UTC)Reply
‘Clipping’ covers all of these, is a proper term used in linguistics, and is much more comprehensible to the average person. Nicodene (talk) 01:36, 9 June 2024 (UTC)Reply
To me, clipping has a slightly different connotation. Aphesis, apocope, and syncope suggest that the word was reduced slightly by rapid speech or "laziness" whereas a clipping has been shortened in a much more substantial way, like favourite > fave or unprofessional > unprofesh (where an entire chunk of the word has been "clipped" off). Ioaxxere (talk) 21:26, 9 June 2024 (UTC)Reply
@Ioaxxere: They are, formally, subsets of clipping. The following are synonymous (confirmable by searching them):
It's not strictly incorrect to call them clipped forms, but it's not how people actually think of them. Anyone seeing the Ancient Greek forms labeled "clippings" in a dictionary would be baffled by it, and would want to correct what they would perceive as either mistaken or laughably pedantic. I'm trying to think of a parallel case where something that's technically accurate falls so short of common sense that we can't realistically expect anyone to do it. The best I can think of right now off the top of my head is the fact that we categorize CAT:Birds directly under CAT:Vertebrates and not under CAT:Theropods < CAT:Dinosaurs < CAT:Reptiles. Yes, birds are technically theropod dinosaurs, but classifying them as such here would fly in the face of how people actually think. —Mahāgaja · talk07:28, 10 June 2024 (UTC)Reply
I don't know where you got this impression? I do think of them as clipped forms, because that is what they are. And of the two words clipping and apocope, the latter is infinitely more pedantic– the average person wouldn't even recognize it.
If it's useful to have a specific subcategory for forms produced by regular final clipping in Greek (or Italian), that's fine. Nicodene (talk) 07:44, 10 June 2024 (UTC)Reply
Hmm, the average person wouldn't recognize the term "apocope"? That doesn't make it pedantic, that makes it unfamiliar. If only there were a website that provided definitions of words so that people who were unfamiliar with them could look them up and find out what they mean. Something like a free online dictionary, maybe. —Mahāgaja · talk07:51, 10 June 2024 (UTC)Reply
I don't know what definition of pedantic we're supposed to be operating with, then, because in my world, insisting on fine-grain distinctions and the usage of unnecessarily obscure terminology is in fact more pedantic than not doing so.
The technical terms are used for phonologically-induced changes. Most of what I would call clippings are more a matter of style than necessity. There's no phonological process that changes "brother" and "sister" to "bro" and "sis"- otherwise we'd be calling parents "mo" and "fa". Chuck Entz (talk) 08:42, 10 June 2024 (UTC)Reply
There is nothing about phonological regularity (nor for that matter style or necessity) in the actual definition of apocope. Likewise syncope, aphesis, and clipping. Nicodene (talk) 09:32, 10 June 2024 (UTC)Reply
@Mahagaja There is already a problem with editors having a hard time keeping apart ellipses from clippings, and having three more subvarieties of clippings just adds to the confusion, not to mention the opaqueness of using Greek-origin terms that few people have ever heard of. Possibly we could keep apocope of referring specifically to loss of a single final vowel, since this occurs frequently in Greek and Italian, but I would be definitely opposed to keeping aphesis and syncope, which are underused and I would posit are even more obscure than apocope (since apocope is somewhat well-known specifically in the context of the languages where it is a regular process). Benwing2 (talk) 07:16, 10 June 2024 (UTC)Reply
@Benwing2: "There is already a problem with editors having a hard time keeping apart ellipses from clippings." Actually, by a cursory scroll through User:Ioaxxere/ellipses I couldn't find a single instance where {{ellipsis of}} was used improperly. Also, I would like to note that not all syncopic forms are "clippings" by our definition ("a short form created by removing syllables"), since (for example) collard and its etymon colewort have the same number of syllables. Ioaxxere (talk) 20:52, 10 June 2024 (UTC)Reply
My understanding is that Han script forms are typically only used by Chinese researchers for convenience; while they can be defensible for Sinitic morphemes under our current "unified Chinese" scheme, keeping them for loanwords seems forced and unnecessary. —Fish bowl (talk) 23:04, 13 June 2024 (UTC)Reply
@Fish bowl: Super late reply, but I think they can be kept, maybe as alternative forms. 耶提目 is used in some varieties of Lanyin Mandarin / Central Plains Mandarin beside Dungan, I believe, so that should all the more be kept. — justin(r)leung{ (t...) | c=› }05:05, 30 January 2025 (UTC)Reply
The question is not whether an alternative term page is necessary (It is.) but which form is more common. We also need an English L2 for logatom. DCDuring (talk) 12:47, 12 July 2024 (UTC)Reply
Poking around briefly in online search results, it looks like the katakana form is amply confirmable for this sense of reverse-"Amazon OK". The hiragana, however, appears to be just the straightforward SOP of この(kono, “this”) + ざま(zama, “pitiful appearance / situation / state”), and as SOP should probably not have an entry.
Rather than outright moving, I'd suggest keeping コノザマ(konozama) as an alt form and having the lemma at konozama(konozama). (Can anyone explain why the heck {{m|ja|konozama}} is outputting romanization on a romanized term? Not wanted.) For instance, compare:
Latest comment: 3 days ago2 comments1 person in discussion
The current title is awkward (IMO). I would tentatively suggest moving to dogs are barking with redirects from any other commonly-attested forms like dogs were barking. Perhaps someone has a better idea, or even wants to defend the current name as best. - -sche(discuss)03:23, 30 July 2024 (UTC)Reply
Agree with महागज. Latin spellings of Faliscan are more rare here, so it's better to move it to the original spelling i guess. Or do you find it problematic? Tollef Salemann (talk) 21:35, 8 August 2024 (UTC)Reply
Let's give Mellohi! a chance to explain why he moved it from *Wenikaros to *Uenicaros in the first place before moving it back. And why do we need a separate page for the Gaulish reconstruction at all when we have RC:Proto-Celtic/Wenikaros? The latter can list a Gaulish reconstruction without a link and then put Latin Venicarus under that. Having a whole separate entry for the Gaulish reconstruction feels unnecessary. —Mahāgaja · talk07:21, 10 August 2024 (UTC)Reply
I was basically moving all the Gaulish reconstructed entries to match up with the orthography of actual Gaulish inscriptions (many Latin-script Gaulish inscriptions exist). Latin-script Gaulish inscriptions basically used U for /w/ (and rendered with the letter U in scholarly mentions of words with the glide) and C for /k/. — Ceso femmuin mbolgaig mbung, mellohi! (投稿) 07:58, 10 August 2024 (UTC)Reply
Strong oppose. It's still officially known as Wi-Fi and that's the spelling you're more likely to see in official, formal, and careful writing (followed by WiFi). It's also the exclusive spelling used by the Wi-Fi Alliance which owns the trademark. wifi remains a largely colloquial spelling. Merriam-Webster, the OED, and Dictionary.com all lemmatize at Wi-Fi as well. If anything, I could see noun sense 3 being moved, since it's already informal, but then that'd put us at a weird juncture. AG202 (talk) 22:11, 23 January 2025 (UTC)Reply
If we are talking "careful writing", then Google Ngram Viewer has Wi-Fi about twice as common as all others combined. WiFi is about a third as common with wi-fi and wifi about equal making up the balance.
I didn't know that we prescribed "careful writing" or gave such sources more weight. As all of these spellings are pronounced the same, "colloquial" doesn't seem the right term to apply to the less formal uses in books. Using durably attested sources naturally gives a major edge to any spelling backed by a plausible legal threat, eg, trademark infringement. DCDuring (talk) 22:38, 23 January 2025 (UTC)Reply
The problem of division of pearlash has been observed. The following is from Riddles and Conundrums (1924):
My first's a precious stone;
My next a well known tree;
Or call my first a fruit,
The next a thong will be.
Whichever way you choose:
This puzzle to divide,
You still will find my whole
A powder will abide.
Pearl-ash, or Pear-lash.
Ash is used in combination to form names of a range of natural alkalis (made from vegetable ash), refined versions, and their synthesized replacements, soda ash, kelp ash, potash.
My hypotheses:
pearl ash may have gotten its name not from the product being derived from mollusk shells but by being a refined (white, shiny?, more valuable?) form of potash; hence, pearl-ash, then pearlash
I have yet to find any discussion of mollusc shells being used in the manufacture of potassium carbonate. Therefore, I am skeptical of the definition in our entry for pearl-ash, which is sourced from "Universal Dictionary of the English Language , 1896; under snuff.". Looking it up I found a use of pearl-ash in a discussion of the adulteration of snuff. UDE's definition of pearl-ash did not mention shells or molluscs, just plant ashes. I wondered a jesting or naive folk-etymologist contributor is responsible for the entry.
Latest comment: 10 months ago7 comments4 people in discussion
There is only a single word suffixed with -ferous that doesnt have a preceding i (indigoferous); it especially bothers me how many pages have "|-i-|-ferous}}" (which also clutters up the category of -i-interfixed terms). Could somebody make a bot replace all "|-i-|-ferous}}" and all other "|-ferous}}" (except indigoferous) with "|-iferous}}" if thats possible?
-form could also be moved to -iform along with most of its derivations (there are about 17 latinate adjectives in -form without i I think) but i dont think its as pressing.
"|-i-|-stan}}" could also be replaced by a new entry -istanSuryaratha03 (talk) 22:06, 5 September 2024 (UTC)Reply
In general a policy would be useful about whether or not to add -i- to etymologies of the structure "Latin lemma + English suffix" because a linking -i- is something of a default but there are enough exceptions Suryaratha03 (talk) 22:33, 5 September 2024 (UTC)Reply
Your first sentence is false. MWOnline has isidioferous "bearing isidia".
That there are also several at Urban Dictionary suggests that -ferous is productive.
I just feel its relevant that none of these words have entries on here. Like we might as well keep -ferous as an alternative form of -iferous, but all the "-i- + -ferous" are still unjustified in my perspective, just from a lexicographical view. Suryaratha03 (talk) 14:19, 7 September 2024 (UTC)Reply
Ok, but as I said in my second sentence, we can keep -ferous but is there any argument against changing -i- + -ferous to -iferous in all these pages? And potentially also -ferous to -iferous in all these lemmas that do end in -iferous? Suryaratha03 (talk) 12:56, 9 September 2024 (UTC)Reply
Latest comment: 10 months ago3 comments2 people in discussion
Several Gaulish pages were recently renamed last month without consultation. And since this discussion regarding reconstructions, specifically regarding Gaulish, received enough votes in favour of Romanising reconstructions (including in Gaulish), I am formally requesting for moving:
Latest comment: 3 months ago38 comments6 people in discussion
@DCDuring, JeffDoozan, Theknightwho AFAICT, the only difference between {{taxfmt}} and {{taxlink}} is that the former is intended for when we do have a Translingual entry for the taxon in question and the latter for when we don't, and {{taxlink2}} seems to be a failed experiment to replace {{taxlink}}. Whether there's a Translingual entry can easily be autodetermined, so I propose merging all three into a new {{taxlink}} template that autodetermines whether there's a Wiktionary entry and acts accordingly. If necessary, we can add a flag to override the autodetermination. Benwing2 (talk) 05:10, 27 September 2024 (UTC)Reply
Support replacing {{taxlink2}} with {{taxlink}}, Abstain merging {{taxlink}} and {{taxfmt}}. There's no technical reason to keep them separate, but I understand that doing so would break an important process used by the biggest contributors of taxon stuff, although now that wantedpages has been cleaned up, it might be possible to use that instead. See the first few posts at Template_talk:taxlink#Convert_to_Lua for more details. JeffDoozan (talk) 10:34, 27 September 2024 (UTC)Reply
@JeffDoozan: Wantedpages is worthless for "Translingual" and English and probably many other reasonably well-covered languages because it is limited to 5,000 items. The least "wanted" page is wanted on 53 pages. The most wanted taxonomic name is usually wanted at most 20 times and necessarily fewer pages than that. DCDuring (talk) 15:12, 27 September 2024 (UTC)Reply
I have a couple of questions:
How will I be able to collect lists of taxonomic names that do not have entries and the counts of their uses? Such lists don't have to be available in real time.
Are we now a point where Moore's Law has brought the cost of checking for the existence of entries down so far that we can have lists of hundreds of species without appreciable burden? That was one of the reasons for the existing arrangement. I do not add lists of hundreds of species, but some genus entries have lists of such size, sometimes commented out completely or in part. DCDuring (talk) 15:00, 27 September 2024 (UTC)Reply
@DCDuring As for #2, according to @Theknightwho there are Chinese-language pages that scrape over 1,000 other pages for transliterations without problem, so I don't expect this to be a major issue. I'm pretty sure fetching page contents is not considered an "expensive" operation so we aren't limited by the limit of 500 expensive operations per page. As for #1, there will be categories automatically generated in real time that list all the wanted taxonomic names. For a specific nonexistent taxonomic name, you can check the transclusions in real time using Special:WhatLinksHere to see how many other pages are using the nonexistent taxon, but I don't think it's possible to generate a real-time sorted list of pages by use. However, this can definitely be done offline. It's very similar to the weekly lists already generated by User:This, that and the other, and I imagine if they don't already have a list that will suffice for this purpose, they can easily modify their scripts to generate such a list. Benwing2 (talk) 07:26, 28 September 2024 (UTC)Reply
@Benwing2 is the intent for the new {{taxlink}} to do an existence check on the target entry every time it is invoked? If it also adds something that gets stored in the database link tables (like a WT:Tracking transclusion or even an external link to a fake domain) upon finding a nonexistent target entry, then DCD can manually navigate to WhatLinksHere or Special:LinkSearch to find transclusions of a specific name (although basic search would probably suffice in that case), and I can easily create a new weekly SQL-based todo list. Without the special transclusion or link, I would have to do it by parsing dumps, which is more tedious. This, that and the other (talk) 07:39, 28 September 2024 (UTC)Reply
@This, that and the other Yes, the intent is to merge {{taxfmt}} (which is intended for the case where the target entry exists) with {{taxlink}} (which is intended for the case where the target entry doesn't exist) and check automatically for existence (which means there should be a Translingual section with the appropriate name, and maybe also checking that it has a {{taxoninfl}} header — which BTW we should rename to {{taxonhead}}). I was planning on adding a category for the taxonomic term uses that link to nonexistent entries but I can easily add a tracking page as well. Would it suffice to have a single tracking page for all nonexistent entries or do you want one tracking page per nonexistent entries? If it's easy for you to create essentially a list of nonexistent but tracked Translingual entries on a weekly basis, sorted by number of uses, that would be great. Benwing2 (talk) 08:20, 28 September 2024 (UTC)Reply
As it is now, pages often have multiple instances of {{taxlink}} for a given taxon, because multiple languages can use the same spelling for the vernacular name for the taxon and the taxon ought to be part of the definition. That seems like something that will be lost using categorization, which is page-oriented, not L2-oriented.
The lists generated by Special:WantedPages, sorted by incoming links were flooded by links from User pages. I commented out most of such pages that were from my user pages, but there are many others that have been run periodically that repeatedly show the same entry, even when blue-linked. The value of the capability to sort ANY searchbox results by the number of incoming links is obviously compromised when User pages and indeed any pages outside principal namespace are included by default.
It is amazing to me that everyone is so solicitous of me wasting my time, without asking me whether I thought I was wasting my time. I actually found that the erroneous uses of {{taxlink}} led me to L2s that had other problems, both errors of commission and of omission. But, obviously others know better whether and how I am wasting my time. Dare I say that perhaps others are wasting their time worrying about me wasting mine. DCDuring (talk) 14:34, 28 September 2024 (UTC)Reply
@DCDuring This isn't just about you - it's about the fact that having completely manual infrastructure for taxonomy makes it very difficult for anyone else to get involved unless they want to dedicate as much time as you do. I also don't understand your point anyway: what exactly would be lost on pages where multiple languages point to the same taxon with {{taxlink}}? The thing it would be checking for is whether the taxon page exists, so the entry's language isn't relevant. Theknightwho (talk) 00:03, 30 September 2024 (UTC)Reply
@Theknightwho: The only reason we have "manual" elements of the taxon infrastructure is that nobody seemed to care enough to actually understand, 1., the process I think Wiktionary needs to follow with respect to adding taxonomic name, 2., taxonomic name formatting, and desirable style for taxonomic name entries. I think the number of "wants" is good for prioritizing taxa, so we avoid having too large a proportion of orphan taxonomic name entries. At present we have, almost always, the right formatting if the person adding the taxon has the right taxonomic rank (or equivalent) for the taxon. I don't see how we can usefully automate definitions very much.
I am interested in the number of "wants" from languages, not pages. If five languages use the same spelling for a vernacular name of a taxon, I count that as being worth as much as five pages that refer to the taxon once. DCDuring (talk) 03:45, 30 September 2024 (UTC)Reply
I don't need to differentiate by language in which the entry exists, so I don't do that with the script that tallies the number of {{taxlink}} (not {{taxfmt}}) occurrences for a given taxonomic name. Once the list is compiled, I add the taxa from the list in decreasing order and change {{taxlink}} to {{taxfmt}} for the taxon in question, reviewing the L2 sections as I go, sometimes adding vernacular names, derived terms, incoming and outgoing links, images, etc.
@DCDuring I agree with @Theknightwho. You're not the only one who uses these templates. In particular I've been using {{taxlink}} and {{taxfmt}} myself to clean up formatting on several pages and find it very awkward to have to manually look up each term. You will need to explain to me what benefits the current system provides that are lost when making it automatic. How does the current system distinguish languages? I doubt it does. (For that matter, it's possible to automatically fetch the current section's language and use it in categorization if so desired.) Benwing2 (talk) 00:25, 30 September 2024 (UTC)Reply
@Benwing: I am not sure what it is that you manually look up for each term. If an ordinary wikilink for a taxon is red, then it needs {{taxlink}}; if it is blue, we have lately decided it needs to be formatted using {{taxfmt}} to remove the need for anyone other than module programmers to master taxonomic formatting. DCDuring (talk) 03:45, 30 September 2024 (UTC)Reply
@DCDuring It is possible to automatically check (a) whether the page exists, (b) if so, whether a Translingual entry exists and (c) if so, whether that entry is a taxonomic entry. The check would be whether all of those conditions are satisfied. It may be possible to make it even more specific, if necessary. Theknightwho (talk) 03:52, 30 September 2024 (UTC)Reply
@Theknightwho: I assumed that (a), (b), and (c) would be possible. I assume that you are talking about real time.
Please tell how the single template will differentiate between names with Wiktionary entries and names missing them in a way that yields a list of missing taxonomic names ordered by the number of occurrences of the taxon enclosed in the template. Can that be done in real time? Does it need to be done by dump-processing (as it is done now)? DCDuring (talk) 18:40, 30 September 2024 (UTC)Reply
@DCDuring Okay, how about you tell me how you're achieving that now? Plus, going by your comment above, you only need to compile that list in order to manually change the template, which would no longer be necessary anyway! Theknightwho (talk) 18:43, 30 September 2024 (UTC)Reply
You miss the point. I add taxa in order of descending number of instances of occurrence of the taxon enclosed in {{taxlink}}. I do a run occasionally of a perl script against a dump that picks out occurrences of {{taxlink}}, groups them by taxon, and orders the taxa by the number of taxlink instances for each taxon. I add entries for the most "wanted" taxa when I have the enthusiasm to do so. DCDuring (talk) 14:13, 1 October 2024 (UTC)Reply
I admit that I selfishly assumed responsibility for taxonomic entries and use of {{taxlink}} when its creator seemed to cease being interested. I was (and perhaps am?) the only one who regularly removed redundant {{taxlink}} and, now, who converts them to {{taxfmt}}. I also seem to be the only one adding taxa based on the number of "wants", though I have advertised User:DCDuring/MissingTaxa a few times over the past dozen or more years. I have offered help to any users who come to my talk page.
The 'workflow' for adding taxa is dispersed among a small number of people who add {{taxlink}} when a bare link (or {{taxfmt}}) is red. We apparently want either {{taxfmt}} or {{taxlink}} to be added for the taxon formatting. {{taxlink}} also provides a means to meliorate over our very modest coverage of taxa by referring people to Wikispecies. It also provides a way to count "wants" for a taxon. In the absence of an explicit proposal (not hand-waving) for dump-processing to identify missing taxonomic names by their number of wants with the merged templates, I don't see how combining these templates offers any reduction in workload to anyone. DCDuring (talk) 03:45, 30 September 2024 (UTC)Reply
@DCDuring I'm completely confused as to how having two templates the choice of which depends on manually checking for a red vs. blue link is superior to doing the same automatically. Maybe you're not understanding my technical proposal, because what you're saying doesn't make a lot of sense to me. If {{taxlink}} does A, and {{taxfmt}} does B, my proposal is simply to have a combined template that automatically does A when the link is red and B when it's blue. How does {{taxlink}} allow us to count "wants" for a taxon that a combined template won't? This doesn't make any sense technically to me so I will need a detailed technical explanation of how this works. Thanks! Benwing2 (talk) 03:52, 30 September 2024 (UTC)Reply
@DCDuring BTW you explicitly mention that some people (not you) use the wrong template, and you have to then go and clean this up. This is exactly the sort of work that will vanish by having only one template. With only one, there's no way to use the wrong one. Benwing2 (talk) 03:53, 30 September 2024 (UTC)Reply
Please tell how the single template will differentiate between names with Wiktionary entries and names missing them in a way that yields a list of missing taxonomic names ordered by the number of occurrences of the taxon enclosed in the template. If this can been done, why not do it for {{l}} (and {{m}}, and all the column templates and make ordered lists of missing entries in order of "want" for all of our languages? DCDuring (talk) 17:58, 30 September 2024 (UTC)Reply
@DCDuring I do think this is possible offline. However, the more pertinent question is, can you do this currently? If so, please explain how it's done currently and I will explain how to do the same in the new system. If you can't do this currently, why are you insisting on it when you can't do it in any case? Benwing2 (talk) 18:58, 30 September 2024 (UTC)Reply
@DCDuring I created WT:Todo/Lists/Wanted taxa, which seems similar to your existing list in your userspace, but may be of use to you nonetheless. (Note this is a dump-based list just like yours, so the todo list infrastructure will automatically regenerate it twice a month.) If it is, please let me know and I will try to fix the problems currently present in the list. Otherwise I will retire it. This, that and the other (talk) 12:23, 5 October 2024 (UTC)Reply
If it matches mine, having it outside of user space is better. It's also a little quicker to use because one can scan the 'wanting' pages to get an English vernacular name or other indication of a part of a potential definition. Adding items from these lists at least means that the added items are not orphans, which are often a waste of contributor time. DCDuring (talk) 14:58, 5 October 2024 (UTC)Reply
Redirects to taxonomic entries may be desirable and thus should be excluded, though they may meet the selection criteria currently implemented.
Furthermore, if the availability of this list depends, as a practical matter, on certain specific individuals running and maintaining code not accessible to me, I would not be very happy to lose my ability to run my simple Perl scripts. I have outlasted, even outlived, most of Wiktionary's technical adepts. Perhaps simply redirecting {{taxlink}} to {{taxfmt}} would be sufficient to allow me a fallback should our current excellent adepts, especially TT&O, find other interests. DCDuring (talk) 22:39, 29 March 2025 (UTC)Reply
The is available and runs on a collaborative wikimedia hosted server (ToolForge) so it runs automatically and is not dependent on any single editor. Looking at the code, it makes no distinction between {{taxfmt}}, {{taxlink}}, or {{taxlink2}}. Any |1=taxon+|2=rank pair found in any of those templates without a corresponding pagename+{{taxon|rank}} is counted as Wanted. In the case of Mysticeti, {{taxon}} has |1=parvorder but the Wanted items refer to |2=suborder. JeffDoozan (talk) 23:50, 29 March 2025 (UTC)Reply
I now appreciate the benefits of the listing as you have it. It has surfaced various problems, such as failure to use {{taxon}} and simple errors in rank in use of the {{taxlink}} family of templates. I am not sure how to deal with "real"-world (taxonomic) inconsistencies in the ranks (including use of clade) of taxa. Open Tree of Life, a relatively new database, tags taxa as 'inconsistent' when it fails to find a consensus among the authorities it uses. (I hope this US NSF-funded resource does not degrade (or worse) in the current budgetary climate.) I sometimes have used multiple {{taxon}} templates as subsenses where there seemed to be rank (or other) differences that I could not otherwise resolve. DCDuring (talk) 21:32, 30 March 2025 (UTC)Reply
Latest comment: 9 months ago1 comment1 person in discussion
Hello there, fellow wiktionarians. This page was tagged for moving with the reason given being "This is a terrible StarLing reconstruction that needs to be moved, but I don't know what the correct form is". So I have been digging around through the Internets and found this paper from Maarten Kossman which gives the reconstructed root as √swʔ, the Aorist as *ăswəʔ, the Imperfective as *săssăʔ, and the Verbal Noun as *-săs(s)eʔ; I couldn't find a reconstruction for the lemma, perhaps because of too much variability in the daughter languages? - I don't know. I don't know what's the current policy/preference for reconstructions with just the root consonants; most proto-semitic ones have the full word instead of the root; I did find one with just the root - Reconstruction:Proto-Semitic/w-r-d- (which, however, seems to me to be relatively easy to reconstruct as *warad-, but I'm just an amateur)
Latest comment: 8 months ago2 comments1 person in discussion
I propose to move the relevant forms at *ǵʰrem- to *gʰrem- insofar as they aren't there already. In practice this means moving the Sogdian forms, but only after correction. Then the forms at *ȷ́ʰárati and subpages would need to be disentangled as different roots are given for those by Cheung (and others).
Latest comment: 8 months ago3 comments2 people in discussion
Ancient Greek. The page already says "The present is used only as a participle", but according to Beekes ἔθων is not related to εἴωθᾰ. I suggest both get their own pages. If there is to be a page for 'ἔθω', I think it should be as reconstruction *ἔθω, like Beekes gives under 'εἴωθα' (p.395). (moved from rfv) Exarchus (talk) 19:37, 28 October 2024 (UTC)Reply
Hello M @Exarchus. I tried to concentrate on attested forms and expressions as we would do at our exams. I do not do Etymologies. Participles have their own pages in en.wikt anyway. (Most of the many quotations seen are for participles, not for the verb). εἴωθα(eíōtha) may have its own page (without repetitions of material) with its own Etymology. The unattested ἔθω(éthō) may have in front of it an asterisk (lemmatised or just added in-page, according to en.wikt's policy for such cases, perhaps with a little template for * with tooltip). Admin @Mahagaja could review. Thank you. ‑‑Sarri.greek♫I21:18, 28 October 2024 (UTC)Reply
Latest comment: 8 months ago2 comments1 person in discussion
To be moved to what is reconstructed by the references (hint: they don't reconstruct 'fellō'), or to be removed altogether as a Frankic etymon is just one of several etymologies for Latin fellō(“criminal”). I already explained why the Dutch 'descendant' shouldn't be there. Exarchus (talk) 22:14, 29 October 2024 (UTC)Reply
Latest comment: 8 months ago1 comment1 person in discussion
After I removed a few terms, there are only nouns now (as there were originally). Rastorgueva & Edelman reconstruct *xʷāpa- for those, so maybe the page should be moved to *hwāpa (possibly related to Sanskrit स्वाप(svāpa), but maybe independent creations as the Sanskrit term occurs fairly late). The verb that should be reconstructed for Proto-Iranian is rather a verb on -sati: R. & E. give "*hufsa-, *xʷafsa-", LIV gives the zero grade as original. Exarchus (talk) 22:49, 29 October 2024 (UTC)Reply
Latest comment: 8 months ago3 comments2 people in discussion
These are basically two competing reconstructions for the same thing. I'm inclined to think the reconstruction should be *krā́mHti. Exarchus (talk) 11:13, 9 November 2024 (UTC)Reply
Latest comment: 6 months ago2 comments1 person in discussion
I think this should be moved to an athematic deponent verb. Sanskrit ओहते(ohate) is given by Lubotsky as sometimes 3pl.ind. and sometimes 3sg.subj., see {{R:inc:IAIL|page=352}}. The Avestan verb is pretty clearly athematic, see for example {{R:ira:Cheung|page=169}}. This means {{R:grc:Beekes|page=486}} is simply wrong when suggesting those are thematic verbs.
This verb is generally reconstructed to come from a reduplicated present and {{R:ine:HCHIEL|1879}} happens to reconstruct the following: "PIIr. *Ha(H)ugʰžʰa,*Ha(H)ugʰdʰa 2,3sg.inj.med." Exarchus (talk) 18:24, 15 November 2024 (UTC)Reply
Latest comment: 27 days ago6 comments4 people in discussion
Yiddish. If this does exist it's in the wrong script. The third quote suggests it's actually a Hebrew word (it's on Hebrew Wikisource...), but I'm not sure. -saph668 (user—talk—contribs) 22:46, 27 November 2024 (UTC)Reply
The English quote uses it as a nonsense word parallel to "dinglebop". The "Yiddish" has links to what seem to be rabbinical texts in some variety of Aramaic or a mixture of Hebrew and Aramaic, of which the first two use שליימ״ל or שלימל with an extra syllable at the end, and the other uses what looks like Yiddish שלײַם(shlaym), which is closer to slime than membrane. I'm far from fluent in Hebrew, Aramaic or Yiddish, but at best they're sprinkling Yiddish terms into running text in other languages (though the first labels שליימ״ל as ""Ashkenazic", which no doubt means Yiddish), and two out of the three aren't even the right number of syllables. I could be wrong, but I don't think any of them are evidence for a Yiddish word that can be transliterated as "schleem" rather than something like "schlaim" or "schlaimel". Chuck Entz (talk) 00:51, 28 November 2024 (UTC)Reply
I created it on EN wiki because the term (or at least a homograph) also appears in English, in "Rick and Morty". Secondly, this word is a possible etymology for English "slim" =thin, which has never been convincing traced to the cognates meaning "bad" or "crooked". See the struggle of Anatoly Liberman, Word Origins p. 200. Also this wiki is much more active that Yiddish, and easier for me to edit.
Editors who are not familiar with these languages should not be wildly speculating here. There is no question that these three Rabbinic Hebrew quotations use a Yiddish word. The first explicitly describes it as "בלשון אשכנז"=in the language of Germany. This is the normal way for books of the period to cite Yiddish, and it does not seem to have existed in other German dialects, so far as I can tell from dictionaries. The second describes the word as "בל"א" which is an acronym for the same phrase. The third spells it with a diacritical mark known as "gershayim" which is the equivalent of English italics, used here to mark the word as foreign. Admittedly, there is nothing explicitly to say that it is Yiddish as opposed to Polish here, except for its connection to the previous quotations.
It cannot possibly mean slime. I have translated the Hebrew in each of the three quotes into English on the page, leaving the loanwords in transliteration, so anyone should be able to see that "slime" is an impossible translation in context. The first reference tells you that it is a type of "membrane" (Hebrew קרום) and that it is equivalent to French teile, which is what French rabbinic texts use for "membrane". The second and third references give the nearest Hebrew equivalent as "thin skin" (Hebrew עור דק). I don't know what the modern anatomical terms for these exact bits of flesh are, but it seems to be a general term because it's used for 3 different bits in the 3 different quotes.
As for the pronunciation, we can't be certain, and schleim is possible. But schleem or schlim is much more likely, because the normal way of spelling the ei vowel in Rabbinic Hebrew transliterations is with a double yodh. The printer of the version of Sirkis's book I linked to has seen fit to insert a second yodh into his text (שלימ"ל in the first edition) so I assume that he recognized the word and thought it should be pronounced schleimel. By contrast, the third quotation is spelled שלי"ם, with only a single yodh.
I don't know of any book in Yiddish which uses this term. Yiddish printing until the modern era was restricted to certain genres, and did not include technical anatomical works or Rabbinic studies of anatomical subjects. I couldn't find any modern work in any language which uses it. The use of loanwords with survive in Rabbinic Hebrew is a completely standard practice for reconstructing historical dialects. Old French dictionaries, for example, are deeply indebted to Rabbinic Hebrew works of the period (anatomical teile seems to have been missed). GordonGlottal (talk) 21:10, 2 December 2024 (UTC)Reply
I wasn't contending your transliteration. The script it's in is objectively wrong, no 'wild speculation,' and nothing you said in that comment addresses the concern I brought up at all. Our Yiddish entries are in the Hebrew script. -saph668 (user—talk—contribs) 21:14, 6 December 2024 (UTC)Reply
@GordonGlottal: more to the point: our entries are organized by spelling: schleem, Yiddish שלײַם(shlaym), Yiddish schleimel, Yiddish שליימ״ל(shleym"l), Yiddish שלימל(shliml), etc. belong on different pages, though a case could be made for ignoring the vowels that are only present as diacritics, and perhaps the variation in yods- though I think Yiddish is less permissive in that respect than Hebrew (I would have to read through WT:AYI (and maybe WT:AHE) to be sure. Some of the entries would be "alternative form of" soft redirects, but having the main form at a spelling that's different from anything in the quotes supporting it would only work if the editors for the language in question had decided to organize things that way. What you did there would be like having a Hebrew entry at shalom with quotes like "יִשָּׂ֨א יְהוָ֤ה פָּנָיו֙ אֵלֶ֔יךָ וְיָשֵׂ֥ם לְךָ֖ שָׁלֽוֹם".
While I'm at it, I might as well point out that most of the early Rabbinical writings such as the Talmud are written in what we treat as Jewish Babylonian Aramaic: though the writing system is the same as Hebrew and they discuss a lot of Hebrew texts and the concepts in them, so there's lots of overlap. Chuck Entz (talk) 23:11, 6 December 2024 (UTC)Reply
@Saph668: We already have שלײַם(shlaym) and שליים(shleym), these should cover this entry, no? I'm not sure Anglophones can be trusted with transcribing the Yiddish term faithfully to the pronunciation. Thadh (talk) 07:36, 30 June 2025 (UTC)Reply
Latest comment: 6 months ago5 comments2 people in discussion
These two templates for Danish verb conjugations could hardly be more different. Not only is the visual appearance completely inconsistent, but the structure doesn't match either: {{da-conj}} has present/past across the top, while {{da-conj-reg}} has active/passive. They don't even have all the same forms.
To add to the confusion, we have some Danish verbs that don't even have a conjugation box at all, like smile.
Okay, I have read some Danish grammar books and now I am less confused. It seems that we need to show:
infinitive and imperative (trivially related)
present tense
past tense (five types: add -te; add -ede; vowel change and add -ede; strong verbs; irregulars)
passive infinitive, passive present, passive past
Note: {{da-conj}} shows the active infinitive but not the passive infinitive. This seems counterintuitive. Putting active/passive as the columns of the table allows space for this form.
present participle
past participle
the auxiliary verb to be used (missing from {{da-conj-reg}})
We also need a table for deponent verbs like enes.
The grammar books I looked at don't mention a gerund, but both our templates identify this form. Is it obsolescent?
Anyway here's my first draft of a replacement, merged Danish verb template, using {{inflection-table-top}} to get the benefits of a sensible width and dark mode support:
@This, that and the other Yes, I agree, quite a mess... I started drafting an Appendix to gather my thoughts on the matter before revamping the templates but life got in the way and I'm not sure I'll get back to it in the immediate future.
The situation with the -s form (probably better referred to as middle voice than passive, as elaborated by the pdf linked below. Mediopassive is also occasionally used in the literature and I would prefer either to passive since many are not at all passive and it's also not even the only passive in North Germanic) is further complicated by the fact that the -s forms actually have several different functions, depending on verb, and it can be difficult to tell when a given usage is being used in a passive, anticausative or reciprocal function even when one knows the language well. For instance, see the examples here and at Mediopassive voice. I don't remember off the top of my head but have a vague feeling that some verbs also do not have an -s form, though we should probably confirm that with a native speaker or someone more qualified before acting on that hunch. Additionally, as you mentioned there are a handful of deponent verbs (such as enes, synes), which occur only in the -s forms. Depending on dictionary, -s forms may get their own independent entries, or they may be subsumed under the active form, where possible (for instance Den Danske Ordbog has redirecting to se, but with its own entry; in the Politikens Nudansk Ordbog, both get their own entry). So, what do we call them and should we automatically generate them for all verbs?
Regarding what might be described as the gerund, the so-called centaur constructions or centaur nominals, this seems to be a topic deserving of more academic research (which is obviously beyond our scope here). I believe they are theoretically possible for many (all?) verbs, although I cannot comment on the actual frequency of their usage in the contemporary language. They are certainly very rarely covered by grammar books, with at least one large English work outright denying the existence of a gerund. Full disclosure, I was the one who translated that wikipedia page on centaur nominals from Danish. Helrasincke (talk) 22:38, 5 December 2024 (UTC)Reply
@Helrasincke I picked red because it's on the Danish flag! I'll go with brown for now, as it is more muted, but still distinct from Swedish blue. You are, needless to say, welcome to change the palette parameter at {{da-conj}} to whatever you wish!
The situation of the gerund seems rather odd to me - in general I would say we should follow grammar books and dictionaries, but clearly some form like this does exist, and since my knowledge of Danish is extremely limited I would naturally defer to you.
Latest comment: 7 months ago4 comments3 people in discussion
The two dictionaries I could find which gave a time frame for this word – besides OED, which just calls it obsolete and Scottish – attribute it to "Old Scots":
Slang and Its Analogues Past and Present: "BARLA-FUMBLE! intj. (old Scots)"
Google Books also says it's found in A Dictionary of the Older Scottish Tongue: From the Twelfth Century to the End of the Seventeenth, volume 1, but I don't have access to it.
The earliest use is in Christis Kirk on the Green, from around 1500 and which is in Middle Scots. And James Maidment's A Book of Scottish Pasquils has a quote for it dating from between 1568-1715 (or maybe he authored it himself? I can't really tell, but if it's not him quoting it then it's from 1868), firmly in the range for Middle Scots. The latest use I could find, in the form barley, was in Walter Scott's Waverley, in 1814, which I think would place it in Scots. It should probably be under Middle Scots. -saph668 (user—talk—contribs) 16:20, 6 December 2024 (UTC)Reply
Latest comment: 4 months ago5 comments2 people in discussion
There should be a separate reconstruction for forms like Sanskrit हृद्(hṛd) (with Vedic nominative/accusative हार्दि(hārdi)) and Avestan 𐬰𐬆𐬭𐬆𐬛(zərəd). In {{R:inc:IAIL|page=230}} Lubotsky gives "j́ʰārd-/j́ʰard-/j́ʰrd-; j́ʰrdaia-". I guess most Iranian forms come from the form without -aya-, one example that does come from the latter is Ossetian зӕрдӕ(zærdæ) (says Lubotsky). Exarchus (talk) 09:59, 11 December 2024 (UTC)Reply
Latest comment: 6 months ago1 comment1 person in discussion
As far as I know, Cumbric is not attested directly. It seems that the following terms are only either mentioned in documents in other languages or deduced from things like place names and personal names, so they should probably be moved to Reconstruction: space:
Latest comment: 6 months ago1 comment1 person in discussion
Merge with I don't speak English § Translations (“I don't speak (fill with the name of the current foreign language)”), as both serve the same purpose (instead of duplicating the content in two places). J3133 (talk) 06:00, 4 January 2025 (UTC)Reply
Portuguese pre-reform spellings with accents
Latest comment: 5 months ago35 comments10 people in discussion
A summary of the proposal is below. The rest of the proposal, as well as the first comment in the thread, comprise rationale, examples, and detailing.
Spellings like accôrdo, appêllo, máo shall be mentioned in usage notes under accordo and appelo, mao rather than in entries of their own.
Spellings like pessôa, vêr, and most* of words where, if you take the accent away, you just get the normal spelling shall be kept.
*Spellings like espêlho, as well as inflections like almôços, arrôtos are more commonly — if not exclusively, to the point of otherwise not passing WT:ATTEST — seen as misspellings from 1911–1945 or 1943–1971. I'm proposing their deletion.
This request for merge concerns Portuguese entries in ] and ] — and anything currently listed as “archaic” or “obsolete” that gets put in that category in the future — that contain accents.
The proposal is, generally, to merge entries for accented pre-reform spellings with the equivalent entries without accents, (if one exists), where a usage note will be added.
Examples of changes:
appêllo shall be merged with appello (and thus deleted).
Use of accents prior to the spelling reforms of 1911 (in Portugal) and 1943 (in Brazil) varied greatly between authors. The spelling appêllo, with an explanatory accent, was occasionally seen.
Conversely, words that were more commonly spelled with an accent than without it will be merged under the accented form. A usage note will be added. These are chiefly spellings that use ⟨é⟩ as an etymological way to write the diphthong /ɛj/.
In this pre-reform spelling, the letter ⟨é⟩ represented a diphthong sound. The unaccented spelling idea may be occasionally seen, especially in older texts.
Compare also pellings that end in stressed ⟨á, é, ê, ô, ó⟩, commonly spelled with accents.
Words ending in ⟨as, es, is, os, us⟩, with or without accents, were also written ⟨az, ez, iz, oz, uz⟩ prior to the reforms. This and other factors make it that very few spellings of this type differ at all from the word’s modern spellings (as such, there are few such entries).
Spellings ending in ⟨í, ú⟩, which were less common, are often categorized instead with {{pt-1931|mis=1}} or as general misspellings.
Additionally, some spellings are excepted from any changes. If a corresponding unaccented spelling did not exist, the words shall be kept.
Derivates of the word á, such as áquelle (which have an accent for different reasons) shall be kept.
Words that, aside from their accents, do not differ from the modern spelling. These entries shall be kept so as not to remove them entirely from the dictionary, and they shall employ (uncommon), especially when listed in Alternative forms sections.
Excepted from this criterion are words which are significantly more frequently attested as misspellings from the 1911–1971 period; it is pointless to keep misspellings from a bygone era.
Use of accents prior to the spelling reforms of 1911 (in Portugal) and 1943 (in Brazil) varied greatly between authors. The spelling with no accent, ver, was significantly more frequent overall.
@MedK1 and I are convinced that use of accents was entirely up to an author’s whims. For any and all pre-reform spellings with stressed a, e, o, you can attest spellings that clarify the the stressed syllable and its height by writing á, ê/é, ô/ó — however, the two of us have, without fail, found the unaccented forms to have been much more common. These "clarifying" accents were often employed even when there were no homographs (such as with ceo, or even any possible ambiguity in reading (such as with pessoa); see the common spelling of João Pessoa’s name as João Pessôa. There is precedent that supports this proposal — how we handle languages with inconsistent (i.e., optional) or frequently unmarked diacritics — but it stands alone even without drawing the connection.
Our reason for this change in handling is to not give the wrong idea about what was the norm in pre-reform Portuguese spelling, because accents were not it. We also aim to greatly reduce the size of "alternative forms" sections for words like apelo — note that, if that section were complete, it would also include some of apélo, appélo, appéllo, apéllo...
It’s worth clarifying that currently the only entries that get classified under the 1911 and 1943 categories are spellings that were still in use immediately prior to the reforms being enforced, so nothing that had long fallen out of use — we’ve been counting those as obsolete. Spellings that were used right before 1911/1943, but then stayed in use up to later reforms (or are still used today), are not listed under such categories either — this means that words like espêto are not counted in this proposal because they were the correct spelling up until 1945/1971. However, spellings like espêtos, azêdos were not standard during the same time period and are mainly attested in pre-1911/1943 texts: in order for them to receive an entry, they would need to be attested in works using post-1911/1943 orthography.
To address the exception from the proposal: unlike most former uses of accents, marking oxytone words with ⟨á, é, ê, ô, ó⟩ was indeed the norm; funnily enough, putting aside verb forms, a majority of these are just the same as the modern spellings of the words. It’s worth noting, however, that this was not the case with using ⟨í, ú⟩ — such words are instead marked as 1931-prescribed spellings if they have more than two syllables, or as misspellings if not.
Examples of two authors’s writing. Just because I wanted to talk about this.
Maria Amália Vaz de Carvalho used bountiful accents in her writing; however, her choice between accentuating or not may be inconsistent within seemingly equivalent words.
She would always mark the pluperfect tense with -êra, -ára, etc.
She would always accentuate the diphthongs -áo, -éo.
She would accentuate most oxytones ending in a, e, o, like lá, má, pé, dá, avô, but notably not the verb há (spelled ha)
She would write some infinitives with -êr, and some with -er: verem but revêrem.
She would write fóra and fôra, but also côr.
Graciliano Ramos comparatively used very few accents in his writing.
Of course, he would accentuate all oxytones ending in a, e, o.
He would accentuate to distinguish some homographs: fóra and fôra, pêlo from pelo...
Right. I considered, for a moment, making a usage note template — something like that could be used on pre-reform pages like appello, but we couldn’t place one on a page such as pessoa. I think the best idea is to include this on the Appendix to-be we’re working on over at WT:Aliança Galego-Portuguesa/Reforms of Portuguese orthography.
I think we could move that to the Appendix namespace already, but before finishing the page, we’d need to figure out what format makes it easiest to digest all the information (because I know what we have now isn't very good). Polomo47 (talk) 02:23, 12 January 2025 (UTC)Reply
Support. However, I must say I'd be hesitant about implementing the last bullet point (concerning pessôa, corôa, etc.) alongside this merger as it is possible that those still existed as misspellings decades after standardization (somewhat akin to pêras). Otherwise, 100% agreed. MedK1 (talk) 05:51, 12 January 2025 (UTC)Reply
I must clarify that we should still include the spellings I mentioned if they are thrice-attested in works that otherwise follow the reforms. If pessôa remained a common misspelling after 1911/1943, then it would still be a worthy inclusion. If it did not, then that just shows the use of the accent was just as a reading aid.
Note, however, that we need to distinguish quotes not by date, but rather by the general orthographic choices in the work. There are many books published well into the 1910s that refused to implement the reformed spelling — just like there are many Portugal news outlets today that refuse to implement the 1990 reform, lol. Polomo47 (talk) 20:00, 12 January 2025 (UTC)Reply
Oppose. I see no benefit in deleting pages with obsolete/superseded spellings. If ] becomes red, and someone searches for it, they'll be taken to the search results page and have to decide whether the word they're looking for is ] or ], which is a waste of their time for no benefit. And if the Portuguese section of ] gets deleted, but the Chinese section remains, then someone looking for the Portuguese word ] will land on a page with no Portuguese entry, which will disappoint and annoy them, and may even incite them to create a Portuguese section saying that it's an {{obsolete spelling of}}mau, without realizing the page used to say that until it was deleted. Keeping these entries as they currently are, soft redirects using {{obs sp}}/{{sup sp}}, certainly does no harm, while deleting them would do harm. —Mahāgaja · talk14:43, 13 January 2025 (UTC)Reply
Consider that, at the moment, Wiktionary has entire languages with this search problem. If someone sees the Yorubá word dára, they’ll search for it and have to decide between Dara, dara, dará...
I think that yours is a valid concern, but the problem extends much further than these Portuguese words.
Further consider that these pages have very few views. In the past four years, the average page seems to have around 80 views. This is the case for Hyrcânia. Some pages, like Bósphoro, have less than 40. Further compare how Zéphyro received 80, while Zephyro got 170, and Zéfiro got 512.
These word are actually readily recognizable, so there's not much reason for someone to look them up unless they wanna know about the spelling itself. I imagine most of these pages are found by clicking on "See also", because carthaginez has very few views.
I totally support doing something about the "Diacritic" languages in WT:LOL, but I don't see any development on that front. This change to Portuguese pages harms very little and helps way more: I did point out how such entries make Alternative forms sections harder to navigate (and would even more if they were complete) — I hold the section precious, after all, because it is the place to documents how a word’s spelling developed.
As mentioned in my comment below, the situation with Yoruba is different from the one you're proposing. And yes, it is a bit frustrating that someone has to go to dara to find the Yoruba entry, and it's too much effort to try and move them now. (Though I'm not sure why they'd need to go to Dara or dará) We have proposed creating soft redirects so that there's a Yoruba entry at dára that points to dara, but I have not followed up on it yet. AG202 (talk) 19:07, 13 January 2025 (UTC)Reply
Getting very few views is also not a reason to delete anything. And while these words may be readily recognizable to someone with a very good knowledge of Portuguese, someone with a beginning level may genuinely not know whether ] is an old spelling of ] or of ]. —Mahāgaja · talk20:10, 13 January 2025 (UTC)Reply
I did not mention the amount of page views as a reason for deletion, but rather to show that these pages are not useful in the way you are hypothesising. I mentioned in my opening comment that these spellings are considerably rarer than the equivalent spellings with no accents, such that I consistently manage to find just over 3 citations for the accented forms, while the forms with no accents have hundreds. The data I got was just to support that (1) there really aren't many people looking for these words in the first place and (2) the words people do look for are the ones without accents (by almost double?). Polomo47 (talk) 20:25, 13 January 2025 (UTC)Reply
Oppose for now. We should aim to have every word in every language. Since these forms aren't "misspellings", which would put them under the misspellings policy in WT:CFI, they should be subject to the same WT:ATTEST rules like any other word. They must be cited in 3 different texts from 3 different authors spanning at least a year; if they do not, then they would not pass WT:RFV under the normal rules. We are not limited by space on Wiktionary, and plenty of languages, including English, include obsolete spellings all the time. There is no harm in including them.
"There is precedent that supports this proposal - how we handle languages with inconsistent (i.e., optional) or frequently unmarked diacritics."
This isn't really accurate or the full picture. For languages where we strip diacritics from the entry title, we still include the diacritics in the headword line, and this proposal doesn't propose that. That also makes this more of a WT:RFD issue than a WT:RFM issue. On the other hand, there is precedent of direct precedent for maintaining older obsolete spellings like English cœnæsthesis, Spanish ántes, French extraördinairement, and Italian ànno. Again, if these are misspellings then that's another thing (and would go through RFD), but if not, these should just be subject to the normal WT:RFV guidelines per WT:ATTEST. AG202 (talk) 19:02, 13 January 2025 (UTC)Reply
"I must clarify that we should still include the spellings I mentioned if they are thrice-attested in works that otherwise follow the reforms." I just saw this comment. Why not just have these forms go through the normal RFV process? AG202 (talk) 19:10, 13 January 2025 (UTC)Reply
I wrote that comment considering the words’ inclusion as misspellings post-1911/1943. I wrote this RFM precisely because subjecting most of these to RfV would end up with them passing, because for every weird use of accents, there was a very small minority of authors who wrote with them. Note that I’m not really trying to delete the spellings, but rather combine them under a single page aiming to maximize the usefulness of the dictionary. It is not useful for readers to see equivalent forms máo and mao listed separately and taking up double the space in Alternative forms sections — space is a concern for sections like the one in apelo. While I'm, sadly, unacquainted with Yorubá, I'm not ignorant to how Russian works, and this accent usage is very close to the situation with Russian-language acutes to mark stress.
I did not initially propose changing the headword on these entries because the most common spellings did not use accents. My impression is that part of the reason we include optional diacritics in other languages’s headword lines is to clarify the pronunciation (even though we have the Pronunciation section, we do it because dictionaries do it; though I'd appreciate if you could tell me more reasons), and since these Portuguese words are listed for the spelling and not any other content, then I don't see a value to including them.
I am open to ideas about how to clarify that every single Portuguese word had, at some point, a spelling that used weird accents. I plan to make a usage note template like I mentioned to Davi above, but that would unfortunately not work for all entries. Polomo47 (talk) 19:22, 13 January 2025 (UTC)Reply
Space is really not a concern for Wiktionary. Someone seeing an additional word or two on a line is frankly not really a justification for deleting entries and historically reduces our usefulness. Plenty of entries have many more alternative forms, and the alternative forms section is not the section that takes up the most space on average. I don't think you'd advocate for limiting the pronunciation section to just two standard pronunciations for space reasons or limiting the etymology section to just one ancestor. Space optimization really only becomes a concern with super long lists, and even then, we have collapsible tables for a reason and compression methods, way before we get to the point of deleting entries. I've never seen entries get deleted for the purpose of "saving space", and I don't want to see it start now. We're an dictionary on the internet for a reason; we don't need to save paper. Ideally we want to have as much information as reasonably possible as a wiki.
Nonetheless, if they are actually misspellings, then they should be sent to RFD under our existing misspelling policy. There's no need for an RFM. If they are not, then they deserve to have their own entries like the ones I mentioned above, following WT:ATTEST, with another example being English coöperate.
Optional diacritics are not just for clarifying pronunciation. Some languages like Yoruba require diacritics in the standard orthography for disambiguation, but the reason why they're not in the entry title is that they're not often used by the general populace. Additionally, Yoruba does have archaic diacritics like in ẽrú; we simply have not created all of the entries yet, as we have other things we're focusing on right now. But we wouldn't outright eliminate them. AG202 (talk) 19:51, 13 January 2025 (UTC)Reply
Clarifying: the reason for deletion is not to save space — I worded it poorly. The reason is that it is not useful for a reader to see, in an Alternative forms section, two entries for what is really the same spelling: appêlo and appelo; appello and appêllo; apello and apêllo. My thinking is that the only reason for someone to click on that is if they want to know more about the word’s historical spelling, and for that purpose it’s only convenient to consolidate in that page information about how accents were occasionally used (by means of a usage note).
Note that the situation is different for this from how it is with things like English coöperate, in that there really are people who want to know about the spelling with diereses. Not the case with Portuguese, for a variety of reasons I mentioned previously.
Some data: coöperate has >6700 views in the past four years; English cooperate has 10k views (i.e., the alternative spelling gets 2/3 as many views). In comparison, apelo has 1540 views while appêllo has 170, which is closer to 1/10.
The diacritics are also different from the Yorubá diacritics in that there was no standard orthography prior to 1911/1943. At least these diacritics were used to clarify pronunciation, which is why I drew the comparison with Russian. And, in Russian, I am under the impression that one of the reasons we include the diacritics is for learners of the language, which does not apply for such Portuguese words. Polomo47 (talk) 20:21, 13 January 2025 (UTC)Reply
We really should not base things on views. Obviously more archaic spellings are going to get fewer views. More minority languages are going to get fewer views. I work on Jeju and I'm sure that -으키여(-eukiyeo) & -으키어(-eukieo) get similar amounts of views that appêllo gets (mostly from myself), but that doesn't mean that it devalues the entry or that I should delete one of them. No, the goal of Wiktionary is to describe and document a language, regardless of how popular an entry is. An accurate entry will always be useful. If we based our work on popularity, then 95% of the languages covered would simply not exist on this site.
For Yoruba, there was no official standard orthography before 1966, so entries like ẽrú do give a somewhat parallel situation (it was replaced by eérú in that orthography). The tilde was used by some authors to show the long vowel. AG202 (talk) 21:10, 13 January 2025 (UTC)Reply
I don't think you get it. These variations aren't comparable to English naïve/naive or fœtus/foetus/fetus. They're analogous to Latin mensa/mēnsa/ménsa in that albeit helpful for learners, the variants with the diacritics are rarely used (due to a feeling that its presence should be obvious for any user of the language), not considered 'more correct' than the accentless version and the matter of 'what accent to use' being actually fairly contentious. Indeed, we don't mention "ménsa" at mensa, even though some people employ it on purpose because acutes look closer to apices on Classical inscriptions than macrons do.
I actually can agree with putting accent marks in the headword for all these pre-standardization forms as, like with Latin, that's what people would do when teaching the language (see my user page for evidence of this). Plus it's what the plan is for Old Galician-Portuguese, so that's nice too.
I don't think these points should be ground for an entire 'oppose' vote though. Accents back then did not constitute new words — unlike in the modern day — and so there's no real reason to treat them as such, especially since the treatment for Latin is so much closer to the reality of the day.
It might be worth noting that the didactic value an altered obsolete headword can bring — informing a word's pronunciation — is severely diminished when chances are those pages' readers came from the page for the modern-day spelling, which already gave them the pronunciation. In the case they didn't, then the modern spellings (with all the information they could need) are just one click away.
Polomo's point about page views is to drive home the idea that unlike with Latin or with superseded/antique English spellings, nobody really hops into the Portuguese L2 hoping to learn about the etymological spellings, especially not beginner learners. The people who do tend to know a thing or two about the language. This is to say, although I see where you come from when you bring up accenting all these headwords, there's really no reason to find these accents' presence a big deal at all — again, they're of a different nature from the modern-day obligatory accent marks. MedK1 (talk) 04:00, 14 January 2025 (UTC)Reply
My concern centers around removing attested spellings in running text without putting them somewhere in the mainspace, whether in the headword line or in their own entries. I've already given the caveat for misspellings. And FWIW, you and Polomo have given two very different situations. Are they spellings to mark pronunciation or are they misspellings? I also gave more examples in other Romance languages that are more analogous, not just English. If the spellings were obsolete and rare, but attested, then we could easily use {{lb|pt|rare}}{{obsolete form of|pt|...}}. It's also possible to put labels in the headword line, if folks would prefer that over full entries, as with roof. CC: @Benwing2 for more on that. I simply do not want attested spellings to disappear. AG202 (talk) 04:30, 14 January 2025 (UTC)Reply
I never addressed what you said about misspellings because I didn't recall mentioning misspellings in the context of the proposed merges. So, to elucidate: no, they are not misspellings; the misspellings I mentioned are different types of entry.
Also, I was mentioned employing usage notes (mentioning that the use of accents did exist), which would still mean mentioning the accented spellings in mainspace — I indeed do not wish to remove all mentions of the spellings.
If this is the one point of contention, then it applies only to terms for which the only thing setting them apart is the accent: vêr, pessôa, propôr, etc. I didn’t feel that strongly about deleting those anyway, so I think what could be done is, for these words, to keep the entry and add a usage note stating the converse (that the form without an accent was more common).
Yes, I would personally support that option that you mentioned at the end of your comment. Sorry that this took so long to resolve. AG202 (talk) 05:07, 14 January 2025 (UTC)Reply
@Polomo47 I am generally sympathetic to the idea of not including loads of obsolete spellings and especially not misspellings. One thing to keep in mind is the |altform= flag to {{head}} and corresponding internal flag in Module:headword; this takes alternative forms out of Category:Portuguese lemmas and the corresponding POS category and puts them in Category:Portuguese alternative forms (which doesn't yet exist; there isn't yet a split by POS in this category but it could easily be implemented). I would recommend using this flag for obsolete alternative spellings, so they don't clog up the lemma categories. As for the proposal itself, I had some difficulty following it; would a form like espêlho and rapôsa (which I suspect was relatively common pre-reform) go in the ==Alternative forms== of espelho and raposa, or go nowhere? Benwing2 (talk) 00:17, 27 January 2025 (UTC)Reply
The Latin analogy actually takes away from your point: if the disambiguation issue were as pervasive as in Latin and the orthographic situation comparable to that of Latin, noting these forms on every Portuguese entry would be of utter importance. That's why the citation form of a Latin word in just about any dictionary includes the diacritics, and why we display the headwords that way (in {{head}} or a language-specific variant). That same practice exists for Russian and various Slavic languages, among others, hence Wiktionary's adoption of the headline form with diacritics. I am not proposing we do this with Portuguese, but based on this discussion I would say the situation with Portuguese is far more akin to that with Italian. — 2600:4808:9C30:C500:5472:3DDE:ACC3:B69220:25, 4 February 2025 (UTC)Reply
The point was that while Latin entries have diacritics in their headwords for clarification, it doesn't make sense to do it for Portuguese non-lemmas (these are alternative spellings; pre-reform spellings) when the feature of interest is precisely the spelling quirks. Did you understand that this is not modern-day Portuguese, but Portuguese from ~120 years ago?
Indeed my comparison are flawed because I don't believe any other language — as currently implemented on Wiktionary — has the same scenario as Portuguese pre-reform spellings. Polomo47 (talk) 20:33, 4 February 2025 (UTC)Reply
Please enlighten me as to how other languages’ pre-reform spellings are treated, and how those correspond with Portuguese and the accent trouble I mentioned. Having “the same treatment” would mean there is a same a scenario. Polomo47 (talk) 10:32, 7 February 2025 (UTC)Reply
{{Latin personal pronouns}} should be reoriented to give the cases down the side, which matches the other Latin declension templates.
I also don't like the way it implies "possessive" is a separate case form - it should be treated as part of the other axis, since each of the possessive determiners has its own declension paradigm. It should be possible to do this without cluttering things too much.
It's wrongly stating that eius is a possessive determiner, when it isn't - there is no third-person, non-reflexive possessive determiner; the genitive of the third-person pronoun is used instead (which is what eius is). I suspect this is because eius resembles meus, tuus and suus, but it doesn't decline in agreement with its referent (e.g. for an accusative referent, meus → meum, tuus → tuum, suus → suum, but not eius → *eium). Same goes for eōrum and eārum in the plural.
@Theknightwho thanks for your input. I think I will go ahead with remodelling {{la-decl-ppron}} into a per-pronoun template.
As for your other comments:
From looking at many of our Cat:Personal pronoun boxes, I've formed the view that, when there's a choice between making the template "landscape" (wider than it is tall) or "portrait" (vice versa), "portrait" is the better option, because it gives a better experience to mobile users and is more likely to avoid horizontal scrolling on Vector 2022. Here, the "portrait" option involves keeping the orientation of {{Latin personal pronouns}} - persons down the side, cases across the top. Yes, this would be inconsistent with {{la-ndecl}}, but I think the inconsistency is worth it for the other benefits. Moreover, it is how most of our personal pronoun boxes for other declining languages are currently arranged. (Admittedly, a few were transposed by me, but most were already like that before I came along.)
At minimum, the "possessive" column should be set off by a separator (narrow gap, as seen in {{la-adecl}}. Doing what you suggest may make the template too large.
@This, that and the other I'm happy to do the work for {{la-decl-ppron}}, as I've been working on the Latin inflection modules quite a bit at the moment. In terms of the size issue: we could incorporate selective expansion for different parts of the template, which might be a way to have it both ways. Theknightwho (talk) 13:01, 3 February 2025 (UTC)Reply
@Grande1900: I think you have it backward: it doesn't matter how it's transliterated or mistransliterated. Presumably this word is attested, and we should go by the attested spelling(s). We need to find out how it's spelled in actual inscriptions, and then decide where to move it based on that. If it's not attested, we'll need to move it to the Reconstruction namespace. Chuck Entz (talk) 05:49, 6 February 2025 (UTC)Reply
After looking further, an inflected form 𐤮𐤱𐤠𐤭𐤷 as well as multiple adjectival forms (namely 𐤮𐤱𐤠𐤭𐤣𐤶𐤫𐤴) appear twice on this inscription that we (thankfully) have here on commons. This is the exact same inscription Gusmani references for his entry on the word. So unless there is an attestation for either 𐤳𐤱𐤠𐤭𐤣 or 𐤮𐤱𐤠𐤭𐤣 (which we don't know of since the article is completely unsourced), it should be at least moved to Reconstruction:Lydian/𐤮𐤱𐤠𐤭𐤣.
These three lists of English rhymes, for their Phonetic Transcription, are inaccurate for dialects of English, broadly, outside of the United Kingdom. Words like bang, dangle, thanks, and thang are given the IPA and enPR to suggest they are said as -æŋ(-), while the accompanying audio file, whether it is AuE or GA/US, dramatically raises the vowel from /æ/ to /eɪ/. These pronunciations are accurate! /æ/ and /eɪ/ are not allophones in these dialects! One can only assume they are native speakers faithfully representing their national dialect, while audio sources which are phonetically identical are all over the web. Sang even has /seɪŋ/ written for its US English pronunciation, which I think is very appropriate.
Unfortunately, most dictionaries, even chiefly American ones, don't reflect this difference properly. I know that it must be a gradual change for every pronunciation of <a> before <ng> to be altered on Wiktionary. But, I still think an important change is in order.
If this petition fails, the next most appropriate step would be to add an alternative pronunciation to pages like Rhymes:English/æŋ. Most appropriate after that would be to add ambiguity to enPR. but here are my listed reasons as to why a Split would be better.
Giving a rhymes page two different broad transcriptions is kinda silly. Broad transcription should be informative of a general way things are pronounced. It is normal and common for two distinct pronunciations to exist, but being distinct, they themselves would not rhyme. They do not have the same rhyme. I think that's very silly, almost comical. But it's better than the alternative, Inaccuracy:
the grouping of sounds /æŋ/ is not present in many and representative dialects of English. Wiktionary should seek to accurately represent these dialects to aide in informing curious people.
RP should not be prioritized or treated as a default. People who are learning English are not always, and I am inclined to say but cannot numerically prove are not usually, learning Standardized, Prestige-Dialect, British English. Numbers are, of course, not everything and the Standard British English language should be given equal preference to all other standard dialects. For this cause, both Rhymes should get their own pages.
Rhymes exist in a network. Rhymes:English/æŋ is connected to Rhymes:English/æ-, and Rhymes:English/eɪŋ would connect to Rhymes:English/eɪ-. In my dialect of English, the Onset and Coda of "Sang" and "Safe" are definitively identical, and so should go together on Rhymes:English/eɪ-.
There may exist a word used in English that you and I are not aware of, or that may exist in the future, which rhymes with an /-eɪŋ.../ word and not an /-æŋ.../ word, or vise-versa. Not only that, but rhyme pages also often include near-rhymes, which I think Rhymes:English/eɪŋ would already have different from -/æŋ (perhaps even as a pure rhyme); ginseng!
So, for all these reasons and more, please support to begin the work of differentiating these different pronunciations. Because they're different! Cam0mac (talk) 05:04, 11 February 2025 (UTC)Reply
Completely oppose. The point of Rhymes pages is to group together words that rhyme with each other. Regardless of whether you pronounce hang and rang/hæŋ/ and /ɹæŋ/ or and (the accents with raising still don't have the ɪ-offglide), the point is that they rhyme with each other and it would be redundant to have two sets of Rhymes pages with identical lists of words. If there are accents in which ginseng also rhymes with these, that can be marked with a note like {{q|in some accents}}, which is already widely done on Rhymes pages. The contrast between the phonemes /æ/ and /eɪ/ is neutralized before /ŋ/, so it doesn't matter from a linguistic point of view which symbol we pick to represent the underlying vowel, but /æ/ has the weight of tradition behind it, not to mention the fact that even in the U.S. a whole lot of people (myself included) really do pronounce these words with , maybe raised slightly to but certainly not raised as high as . —Mahāgaja · talk08:31, 11 February 2025 (UTC)Reply
I agree that there’s no need to split these, due to the lack of minimal pairs. Americans may say rang as ‘reng’ or ‘raing’ but those aren’t actual words. The only exceptions I can think of is pang becoming peng and peng becoming ping. Overlordnat1 (talk) 10:55, 11 February 2025 (UTC)Reply
I hear you, and I'm softened to the prospect of leaving things be (though I don't lay too much weight on my changes or suggestions). I'm still bothered by the fact there is less information about this pronunciation. Mostly I'd bring it to anyone's attention because I think record should be kept of this vowel change which I know is present. Cam0mac (talk) 11:31, 11 February 2025 (UTC)Reply
I don't know if I should make this comment here, on this (doomed) Rhymes-pages-centric proposal. But: in our {{IPA|en|...}}s (not Rhymes pages), I support acknowledging the /-eɪŋ/ (or at least the ) pronunciations of bang, sang etc, because as you say, bang and BAME share a vowel and bang and ban do not, for a lot of Americans. Rhymes pages, however — as others have noted above — intentionally overlook differences in transcription wherever these don't actually create splits; we don't have separate /əʊ/ and /oʊ/ pages, either, because the same list of words would be duplicated on each page. The traditional argument against acknowledging /-eɪŋ/ anywhere is of course that there are supposedly not minimal pairs for /æ/ and /eɪ/ in this exact position, preceding ŋ. But when it comes to {{IPA|...}}s (again, not Rhymes pages), I am of the opinion that once two phonemes are distinct somewhere in a language/dialect and we're notating them as separate phonemes there, they should be notated consistently—represented wherever else they occur in that dialect. (This is also why I support our practice of notating that e.g. German Rad ends in /-t/, instead of notating it as /-d/ and expecting casual readers to 'just know somehow' that "the phoneme /d/ means /d/ most of the time, but it secretly means the separate phoneme /t/ sometimes, but we only notate /t/ as /t/ some of the time and at other times notate it as /d/": that approach, which a few people have wanted over the years, seems to me quite hostile to readers. I similarly appreciate that our Russian pronunciations reflect its various vowels, instead of collapsing them all into one vowel as some theorists would like to.) So, because ban and BAME/bane show that /æ/ and /eɪ/ are different sounds, I am inclined to agree that we should acknowledge that both of them, not only one of them, can be found in bang. Or else we might as well notate the pronunciation of bang as /bæh/, since after all, many linguists have claimed there are no minimal pairs for /h/ and /ŋ/ either! (Those linguists are mistaken, there are /h/-/ŋ/ minimal pairs, but that's getting off-topic.) - -sche(discuss)20:58, 11 February 2025 (UTC)Reply
The uppercase version seems better because it has a smaller displaying box: it should be the survivor IMO. The lower case spelling should also be the survivor. I don't know which of the two has better internal logic, consistency with our ways of doing templates, and documentation. DCDuring (talk) 14:51, 12 February 2025 (UTC)Reply
I avoid this kind of project box in taxonomic and vernacular organism name entries. There seem to be fewer than 500 transclusions of each. DCDuring (talk) 14:56, 12 February 2025 (UTC)Reply
I use the inline template {{comcatlite}} (and {{pedia}} and {{specieslite}}). Some people like the big box project links though. Those big rhs boxes appear in the wrong places for someone, like me, who uses rhs ToC. Even the reduced-size project boxes are unsatisfactory, for the same reason. DCDuring (talk) 02:44, 13 February 2025 (UTC)Reply
We need the best features of all: appearance in dark mode, category linking, smaller box, lower-case title, and consistency with our code and documentation standards. DCDuring (talk) 23:36, 12 February 2025 (UTC)Reply
Okay, I've merged these, with a special styling rule for the classic Vector skin allowing the template to display on two lines when the category name is short enough. This isn't possible in Vector 2022 because the default font size is slightly larger, leaving insufficient space - and in any event, all the sister project boxes (except Wikivoyage) run onto three lines anyway on Vector 2022. This, that and the other (talk) 04:31, 19 February 2025 (UTC)Reply
While we're on this, could we also look into merging these two? This has been brought up before. I don't really know the difference between them, though @ExcarnateSojourner says they are useful for different purposes. Could we combine the boxes, and use parameters to modify any features found in one template but not in the other? I use {{Navbox}} for quotation navigation boxes. — Sgconlaw (talk) 22:05, 12 February 2025 (UTC)Reply
@Sgconlaw yes, these should indeed be merged - there's a bit of work involved here though. {{navbox}} (lowercase) has very few transclusions and can probably be phased out in favour of {{Navbox}}, but the latter is a totally undocumented Wikipedia import, and these are notoriously tedious to tidy up. I'll get to it some day. This, that and the other (talk) 00:52, 20 February 2025 (UTC)Reply
Latest comment: 5 months ago2 comments2 people in discussion
Duplicated information. I am not sure that a productive distinction is really made via alternatively lettercased forms in general usage between a hypothetical and the actual scented release system invented in the '50s (see inconsistency in quotes on the page itself!). If there is, I feel it should still be handled at a single canonical entry with labels or usage notes about casing. There are also a variety of missing forms (smellavision, etc.), and we relatedly also need smell-o-phone (and variants). Hftf (talk) 09:06, 19 February 2025 (UTC)Reply
@Hftf: I'm unsure. Based on the quotation data, it appears the uncapitalized form smell-o-vision was coined first, and then in 1959 Mike Todd Jr. used the form Smell-O-Vision for the specific invention. It's probably impossible to know whether he was aware of the pre-existing uncapitalized form of the term. The capitalized form seems to be used largely to refer to the invention. As for the uncapitalized form, it is occasionally used to refer to the invention, but mostly for the general concept. I would imagine that after the 1950–1960s uses of the uncapitalized form were influenced by the name of the invention. — Sgconlaw (talk) 19:31, 19 February 2025 (UTC)Reply
@Graearms: IIRC we have sometimes had Latin (and Ancient Greek?) entries for the lemma form in mainspace rather than reconstruction space when enough of the inflected forms are attested to assure us that the lemma form must have existed and that we know what it should have been, but it didn't happen to have been in any texts that survived. I believe the idea was that we use the lemma entry to house all the information about the term as a whole, and having it hidden off in reconstruction space makes it harder on our readers.
Of course, Latin is much better attested and there have been lots of dictionaries over the centuries that have given the principal parts for terms even when not all of them are actually attested. I don't know if we want to do that for this language, but I thought I would mention the practice. Chuck Entz (talk) 02:56, 24 February 2025 (UTC)Reply
For Gothic (better attested than Oscan, I believe, but nowhere near Latin and Greek) we allow entries in the main namespace under the lemma form even when only inflected forms are actually attested. I suggest we do the same for Oscan: if this word is attested only in the accusative and genitive, we can still have an entry for the nominative in the main namespace. —Mahāgaja · talk08:06, 24 February 2025 (UTC)Reply
Now that this has been soft-moved (out of process?), can someone fix all the incoming links and really any instances of the string? To my understanding, all two-L'd variants should probably be purged outright and are likely to be misspellings or Wiktionarisms (due to ruinous citogenesis), but even if not, I think it's better to completely start over here and require serious attestations of two-L'd variants. Hftf (talk) 00:51, 17 March 2025 (UTC)Reply
It depends on whether you treat it as a lect or as a sociolinguistic stratum. Searching on Google for "talk joual" or "speak joual" turns up some "Joual", but mostly "joual". Apparently a lot of Canadians see it as the same sort of thing as "slang": a less-educated, informal variant of the same language, not a separate lect. People outside of Canada who view it as an academic subject are more likely to capitalize it. Also, as long as we have it as a common noun, it doesn't seem right to capitalize it. If we're going to capitalize it, we should also move it to the proper noun POS. Chuck Entz (talk) 03:38, 24 March 2025 (UTC)Reply
Latest comment: 4 months ago1 comment1 person in discussion
There's a strong case for merging these two boxes, as if you want to know about the pronouns, you likely also want to learn about the suffixes, and vice versa.
Latest comment: 2 months ago5 comments2 people in discussion
Here we have two more archaic right-aligned declension-type tables, with all the accompanying issues (interrupts the flow of the entry on mobile, non-standard look, etc). I would merge them and place the merged template under the "See also" L3 header, which is the standard location for personal pronoun boxes:
To be honest I have always been on the fence about whether we should include transclusions in Greek-script inflection tables, which applies equally to Modern Greek. Of all the scripts out there, Greek script is arguably the one which least needs transliteration into Latin script. But that's just a relative argument: perhaps our readers who are less versed in Greek script (non-STEM folk for instance) do find the transliteration useful. This, that and the other (talk) 11:04, 1 April 2025 (UTC)Reply
I don't know whether STEM people are more likely to read the Greek script than humanities people (STEM people know the individual letters, but that's not the same as reading whole words), but I do tend to think that the people who will want to use the templates are people who can already read Greek. At any rate, if you do use transliterations, maybe make them gray, like {{grc-decl}} and {{grc-adecl}}, whose transliterations are so unobtrusive I forgot about them when making the comment above. —Mahāgaja · talk16:05, 1 April 2025 (UTC)Reply
@Mahagaja sorry, I missed this. The transliterations in the first proposed version above actually are grey; in fact they are as grey as they can be without falling out of compliance with Web accessibility guidelines. Specifically, the WCAG AA guideline recommends a contrast ratio of 4.5, and the grey transliterations in {{grc-decl}} only achieve a ratio of 3.25. However, I am not really sure of the merits of this ratio when it comes to shades of grey. To me, the black-on-dark-grey text in the header rows and columns of {{grc-decl}} is harder to read than the transliterations, yet it achieves an excellent contrast ratio of 11.25!
1 relevant result when searching for КАЕН (all other results are related to the sense "birch tree"): Тсинон 1999 КАЕНИГӘЧ → (старшая сестра мужа или жены) → игәч; каен игәч; кайнигәч;
4 results when searching for КАЕНИГӘЧ: Таңлат 2015-2021 Хатынга ирнең апасы. ("To a woman, her husband's sister")
Maybe I just didn't really understand how appendices work. If this move request is closed as not moved, the proposed target should remain a redirect instead of being deleted. 67.209.130.4306:42, 18 April 2025 (UTC)Reply
Latest comment: 3 months ago1 comment1 person in discussion
Ancient Greek. Modern dictionaries have μειδιάω as lemma, as the present μειδάω is unattested (though can be reconstructed on the basis of μείδημα and μειδάμων, see Chantraine). So I'd suggest to move this. Exarchus (talk) 19:36, 24 April 2025 (UTC)Reply
They mean the same thing (in order to, so (that)); they are simply using different syntax.
"In modo da" takes an infinitive mood verb inflection and can be used when the subject of this infinitive verb would be the same as the subject of the main clause:
in modo da fartelo vedere
in order to let you see it("so that subject lets you see it")
(in most uses, its meaning is similar to per + infinitive which is more common colloquially, similar to Englishto: per fartelo vedere ― to let you see it)
"In modo che" takes any finite verb inflection, and, especially when using a subjunctive mood verb inflection, che can be omitted:
in modo che lo puoi vedere
so that you can see it
in modo (che) lo possa vedere
so (that) I/you/he/she/it can see it
in modo io lo possa vedere
so I can see it
This is similar to subordinate clauses introduced by che being replaceable by di + infinitive if the subject of their parent clause is the same as theirs, in other contexts in Italian.
penso di aver capito
I think I understood
penso che capirà
I think that he will understand
penso (che) abbia capito
I think that he understood
But, for in modo che, with da instead of di. (Though, people do also use "in modo di" instead of "in modo da" without knowing it is actually supposed to be da.)
Also note that fare in modo (fare in modo che ― make it so that) already exists as a single page, and behaves the same way:
Latest comment: 1 month ago3 comments3 people in discussion
English.
I couldnt find a section for this on the page and it's difficult to search for so maybe I missed it. But we already have this listed at ( ), translingual, as a Symbol. Unless we need the dashes for some reason i dont understand, i think this should just be deleted. —Soap—23:30, 28 May 2025 (UTC)Reply
On second thought, the section should probably be deleted as an Insular Celtic–only etymon with no PIE precursor, with the etymological information moved to Old Irish lie. The "related terms" at *līwos can get separate Gaulish reconstructions which briefly mention the relevant etymological theory, but no such Proto-Celtic entries warrant inclusion. The reconstruction *līwos serves only to explain one case form of one word, based on etymological presumptions that are highly disputed (e.g. by both Nikolaev and Zair, for completely different reasons), and Matasović doesn't even mention *līwos overtly, just implies it (or athematic *līus) based on his etymology almost as an afterthought. — Ganjabarah (talk) 18:12, 21 June 2025 (UTC)Reply
The second sense of bombsite is not in bomb site. I wanted to make sure it survived a merge, rather than be carelessly deleted. All three definitions need support and some effort to determine which of the three spellings (including bomb-site is most common for each meaning. You could chip in some of the effort required. DCDuring (talk) 23:08, 2 July 2025 (UTC)Reply
Latest comment: 1 day ago4 comments4 people in discussion
Judeo-Hamadani is not Persian (not even in the same branch of Iranic), but I'm not sure that we have a language code for it.--Saranamd (talk) 23:49, 7 July 2025 (UTC)Reply
Latest comment: 3 days ago2 comments2 people in discussion
Google Ngrams (thanks @Soap!) says that usage of "gharials" in English had overtaken "gavials" since before the founding of Wikipedia. (English) Wikipedia itself also uses w:gharial. If no one objects, I'll move the main English entry to gharial, and leave "gavial" as an alternative form of "gharial", essentially swapping the two English entries.
Personally, this is the first I've even heard of "gavial" being used to refer to those crocodilians; I've only ever seen "gharial". Vampyricon (talk) 22:49, 12 July 2025 (UTC)Reply
Latest comment: 8 days ago4 comments3 people in discussion
Should this be moved to that's what I call something per the reference? What is our policy on including something in the title? J3133 (talk) 17:23, 15 July 2025 (UTC)Reply
I always thought we should limit something/someone/oneself etc. to occurrences among the words of the idiom rather than at the end (or beginning). This expression changes my mind. I'd move it. DCDuring (talk) 21:02, 18 July 2025 (UTC)Reply
Would it be upsetting to enclose a pure placeholder in parentheses in headword? Some lexicographers do that, like MWOnline, Oxford Learner's and Fairlex Idioms. Collins puts an abbreviated placeholder (eg, sb) in the headword. I'm not sure how that would affect search box searches done by normal folks. DCDuring (talk) 00:04, 19 July 2025 (UTC)Reply
For both this and the one above, "English terms for..." might be better, otherwise there's a risk that "English" will be taken as referring to England rather than the English language. —Mahāgaja · talk19:55, 18 July 2025 (UTC)Reply
Latest comment: 7 days ago2 comments2 people in discussion
I propose they are different spellings of the same word, I see no difference in usage between the examples or my experience. Kreuner (talk) 18:41, 19 July 2025 (UTC)Reply
Support move Wiktionary:English entry guidelines --> Wiktionary:About English. Taylor 49 (talk) 22:13, 12 April 2024 (UTC)
Oppose: Even though "out on a limb" can be used without "go", I think "go out on a limb" =/= "go" + "out on a limb", so I think we should keep them separate after all. — excarnateSojourner (ta·co) 02:14, 7 April 2024 (UTC)
Abstain While the noseless variant seems to be used more frequently in English, I am not sure whether it is similarly common in other languages. Maybe we could have a proper definition line for both forms and add 
Done They're synonyms. 2A00:23C5:FE1C:3701:2581:80AA:C256:937C 17:31, 4 April 2025 (UTC)
Strong support, but it'd also be good to give information on the usage of accents before 1911 or 1943 somewhere. Davi6596 (talk) 02:17, 12 January 2025 (UTC)
resolved. This, that and the other (talk) 04:48, 24 July 2025 (UTC)
Support from me in any event. This, that and the other (talk) 01:04, 24 July 2025 (UTC)