text:
karš

Etymology
From, from , from. Cognates include 🇨🇬, dialectal, 🇨🇬 (misspelled as kragis in the 16th-century text), (i.e., “war path”), 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬 (< *koiros < ).

Noun

 * 1) war organized armed conflict between two or more countries, peoples, ethnic or social groups
 * 2)  war; relating to war
 * 3)  war, military relating to the armed forces or to military service
 * 4)  war serious conflict, struggle, fight, clash between enemies
 * 5)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war; relating to war
 * 2)  war, military relating to the armed forces or to military service
 * 3)  war serious conflict, struggle, fight, clash between enemies
 * 4)  war disagreement, dispute, quarrel
 * 1)  war, military relating to the armed forces or to military service
 * 2)  war serious conflict, struggle, fight, clash between enemies
 * 3)  war disagreement, dispute, quarrel
 * 1)  war, military relating to the armed forces or to military service
 * 2)  war serious conflict, struggle, fight, clash between enemies
 * 3)  war disagreement, dispute, quarrel
 * 1)  war, military relating to the armed forces or to military service
 * 2)  war serious conflict, struggle, fight, clash between enemies
 * 3)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war serious conflict, struggle, fight, clash between enemies
 * 2)  war disagreement, dispute, quarrel
 * 1)  war disagreement, dispute, quarrel
 * 1)  war disagreement, dispute, quarrel
 * 1)  war disagreement, dispute, quarrel
 * 1)  war disagreement, dispute, quarrel
 * 1)  war disagreement, dispute, quarrel

title: karš


text:
sweard

Etymology
From ; akin to 🇨🇬.

Noun

 * 1) skin, rind

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: sweard


text:
sviests

Etymology
Originally the (adjectival) past passive participle of an old verb (cf. 🇨🇬); the original meaning of  was thus “(something) smeared (on something else), (something) used for smearing”; cf. 🇨🇬 and, or 🇨🇬 and. The verb would in turn come from, from , from  (whence also 🇨🇬 q.v.); its original meaning would have been “to make something shine” > “to smear with oil, so that it shines” > “to smear” (cf. its descendant , originally the iterative form of ). Cognates include 🇨🇬.

Alternatively, Pokorny (Indogermanisches Etymologisches Wörterbuch, p. 1043) considers this word and 🇨🇬 from (cf. Middle Indo-Aryan kṣvira, 🇨🇬).

Noun

 * 1) butter a dairy product, obtained from cream, with a high fat concentration
 * 2)  butter; containing butter, made with butter
 * 3) butter, spread any food paste generally used as spread
 * 4)  nonsense; something that is bizarre
 * 5)  something that has poor quality, is not successful
 * 1)  butter; containing butter, made with butter
 * 2) butter, spread any food paste generally used as spread
 * 3)  nonsense; something that is bizarre
 * 4)  something that has poor quality, is not successful
 * 1)  butter; containing butter, made with butter
 * 2) butter, spread any food paste generally used as spread
 * 3)  nonsense; something that is bizarre
 * 4)  something that has poor quality, is not successful
 * 1) butter, spread any food paste generally used as spread
 * 2)  nonsense; something that is bizarre
 * 3)  something that has poor quality, is not successful
 * 1)  nonsense; something that is bizarre
 * 2)  something that has poor quality, is not successful

Participle

 * 1) thrown, flung, slung;

title: sviests


text:
swelgan

Etymology
From, from. Cognate with 🇨🇬, 🇨🇬.

Verb

 * 1) to swallow
 * 2) to eat up, devour

Etymology
From. Cognate with Old English sƿelgan, Old Norse svelga.

Verb

 * 1) to swallow
 * 2) to eat up, devour

title: swelgan


text:
svelga

Etymology
From, whence also Old English , Old High German swelhan.

Verb

 * 1) to swallow

Descendants
Note that many of these forms are descended from svelgja.

title: svelga


text:
svelgja

Etymology
From.

Verb

 * 1) to swallow

title: svelgja


text:
swealwe

Etymology
From, related to 🇨🇬, 🇨🇬.

Noun

 * 1) swallow bird

title: swealwe


text:
swapan

Etymology
, from. Cognate with 🇨🇬.

Verb

 * 1) to sweep

title: swapan


text:
Talk:travesty

add see also for satire?EunuchOmerta 13:13, 16 June 2006 (UTC)

Filetype?
Travesty might also refer to the .trv and .trav filetypes. 216.99.219.120 18:46, 12 May 2009 (UTC)

 * So, you are referring to Cut-up technique. A travest is the product of this type of software. We have file extensions: com, txt, asc. I don't know whether trv or trav should be included. DCDuring TALK 14:34, 8 June 2009 (UTC)

title: Talk:travesty


text:
swæþ

Etymology 1
From, from , from. Cognate with 🇨🇬.

Noun

 * 1) track, trace
 * 2) footprint

Etymology 2
From. Compare 🇨🇬, 🇨🇬,.

Noun

 * 1) bandage; swathe

Usage notes

 * The exact gender and nominative form are unknown, as the word is attested once in the dative plural form swaþum.

title: swæþ


text:
swearm

Etymology
From, whence also 🇨🇬, 🇨🇬. Ultimately from.

Noun

 * 1) swarm

title: swearm


text:
svarmr

Etymology
From, whence also 🇨🇬, 🇨🇬. Ultimately from.

Noun

 * 1) swarm

Descendants

 * Norwegian: ,
 * Norwegian: ,
 * Norwegian: ,

title: svarmr


text:
dead rubber

Noun

 * 1)  In a series of sporting fixtures, a match of which the result is irrelevant, the winner of the series having already been determined by earlier results.

title: dead rubber


text:
betons

Noun

 * 1)  concrete (building material)

title: betons


text:
svelta

Etymology
Derived from.

Etymology 1
From (strong verb), from.

Verb

 * 1)  to starve

Etymology 2
From (weak verb), from.

Verb

 * 1)  to starve (someone, or figuratively something)

Etymology 1
From.

Verb

 * 1)  to starve, to have hunger

Etymology 2
From.

Verb

 * 1)  to starve

title: svelta


text:
User talk:Visik

Hi there. This dictionary has words in every language, so every entry MUST start with a ==language== entry. Here is our standard welcome. SemperBlotto 13:25, 16 June 2006 (UTC)

Welcome!

Hello, and welcome to Wiktionary. Thank you for your contributions. I hope you like the place and decide to stay. Here are a few good links for newcomers:
 * Wiktionary Tutorial
 * How to edit a page
 * How to start a page
 * Our format guidelines
 * Criteria for inclusion
 * Wiktionary Sandbox (a safe place for testing syntax)
 * What Wiktionary is not
 * FAQ

I hope you enjoy editing here and being a Wiktionarian! By the way, you can sign your name on Talk (discussion) and vote pages using four tildes, like this: ~~~~, which automatically produces your name and the current date. If you have any questions, see the help pages, add a question to the beer parlour or ask me on my Talk page. Again, welcome!

title: User talk:Visik


text:
आज़ाद

Etymology
, from, from , from. Compare 🇨🇬, 🇨🇬.

Adjective

 * 1) free; independent
 * 2) unrestrained
 * 1) unrestrained

title: आज़ाद


text:
sweorfan

Etymology
From, whence also 🇨🇬, 🇨🇬, 🇨🇬.

Verb

 * 1) to scour, polish, file, rub

title: sweorfan


text:
areo-

Etymology
From.

Prefix

 * 1)  Relating to Mars.

Translations

 * French:
 * Italian: areo-
 * Polish: areo-
 * Russian: арео-

Etymology
.

Prefix

 * 1) soft; less dense

Etymology
From.

title: areo-


text: denationalisation

title: denationalisation


text:
sverfa

Etymology
From, from.

Verb

 * 1)  to file (smooth with a file)

title: sverfa


text:
Moctezuma

Etymology
From, from +  +.

Proper noun

 * 1) Aztec emperor from 1440 to 1469.
 * 2) Aztec emperor from 1502 to 1520, during which time the Spanish conquest of Mexico began.

Usage notes
The second Moctezuma is the one most commonly referred to. The two may be distinguished as M— I and M— II, as M— the Elder and M— the Younger, or as M— Ilhuicamina and M— Xocoyotzin, respectively.

Alternative forms

 * 17th C.:
 * 19th C.:
 * 17th C. to 19th C.:
 * 20th C.:
 * 20th C. to 21st C.:, ,
 * 19th C. to 21st C.: Moctezuma,
 * 18th C. to 21st C.:

title: Moctezuma


text:
areocentric

Adjective

 * 1)  Having the planet Mars at the center.

Translations

 * Asturian: areocéntricu
 * Catalan: areocèntric
 * Czech: areocentrický
 * Danish: areocentrisk
 * Dutch: areocentrisch
 * French:
 * Galician: areocéntrico
 * German: areozentrisch
 * Italian: areocentrico
 * Polish: areocentryczny
 * Portuguese: areocêntrico
 * Romanian: areocentric
 * Russian:
 * Spanish: areocéntrico
 * Swedish: areocentrisk

title: areocentric


text:
denidation

Noun

 * 1) The breakup and expulsion of the endometrium during menstruation.

title: denidation


text:
endometrium

Etymology
From +, from. Compare.

Noun

 * 1)  The mucous membrane that lines the uterus in mammals and in which fertilized eggs are implanted.

Translations

 * Arabic:
 * Basque: endometrio
 * Catalan:
 * Chinese:
 * Mandarin:
 * Dutch:
 * Finnish: kohdun limakalvo
 * French:
 * Galician:
 * German: ,
 * Irish: inmheitriam
 * Italian:
 * Korean: 자궁내막
 * Kurdish:
 * Northern Kurdish: navpoşê malzarokê
 * Polish:
 * Portuguese:
 * Russian:
 * Spanish:

title: endometrium


text:
barbarisation

Noun

 * 1) An act which causes people to revert to a state which is primitive and uncivilized.

Translations

 * Belarusian: варварыза́цыя
 * Czech: barbarizace
 * French:
 * German: Barbariesierung
 * Italian: barbarisazione
 * Polish: barbaryzacja
 * Portuguese: barbarização
 * Russian:
 * Serbo-Croatian:, барбариза́ција
 * Spanish: barbarización
 * Swedish: barbarisering
 * Turkish: barbarizasyon
 * Ukrainian: варвариза́ція

title: barbarisation


text:
dermatome

Noun

 * 1) An instrument used surgically to remove a thin slice of skin for grafting
 * 2) An area of skin which is innervated by afferent nerve fibers coming to a single posterior spinal root.
 * 3) The dorsal part of an embryonic somite contributing in part to skin development.

title: dermatome


text:
dermatoplastic

Adjective

 * 1) Of or relating to dermoplasty

title: dermatoplastic


text:
dermoplasty

Noun

 * 1)  The use of skin grafts in plastic surgery.

title: dermoplasty


text:
desaturation

Noun

 * 1)  the conversion of a saturated compound to an unsaturated one by removing hydrogen or other atoms to form a double bond
 * 2)  a decrease in the level of oxygen saturation in a patient's haemoglobin

title: desaturation


text:
diagenetic

Adjective

 * 1)  of, or relating to diagenesis

Related terms

 * syndiagenetic

Translations

 * French:
 * Greek:
 * Irish: carraig-ghiniúna
 * Persian: دیاژنزی

Etymology
.

title: diagenetic


text:
diakinetic

Adjective

 * 1)  of, relating to, or produced by diakinesis

title: diakinetic


text:
diathetic

Adjective

 * of, relating to, or as a result of diathesis

title: diathetic


text:
fantascienza

Etymology
From.

Noun

 * 1) science fiction

title: fantascienza


text:
diathesis

Etymology
Borrowed from, from , from.

Noun

 * 1)  A hereditary or constitutional predisposition to a disease or other disorder.
 * 2)  Voice (active or passive).
 * 1)  Voice (active or passive).
 * 1)  Voice (active or passive).

title: diathesis


text:
Template talk:third-person singular of

Why doesn't language default to English?
It seems like the  parameter should default to English if it's not specified. —RuakhTALK 17:19, 27 February 2007 (UTC)
 * Probably because the template was used for non-English words before the language parameter was added. You would have to investigate all these occurrences and fix them first. SemperBlotto 17:21, 27 February 2007 (UTC)

title: Template talk:third-person singular of


text:
fango

Etymology
Borrowed from.

Noun

 * 1) Mud from the thermal springs at Battaglia in Italy, used to treat certain medical complaints such as gout and rheumatism.

Etymology
Borrowed from and. Contrast 🇨🇬.

Noun

 * 1) mud, mire

Etymology
From of  origin, see there for more. Compare 🇨🇬 and 🇨🇬.

Noun

 * 1) mud
 * 2)  sludge

Etymology
.

Etymology
.

Noun

 * 1) mud

title: fango


text:
Template talk:present participle of

Verbal noun?

 * Moved to WT:BP — Vildricianus 08:45, 17 July 2006 (UTC)

The nocap and nodot parameters need to be added
Can someone make the same changes I made to the template to this template please? Thanks in advance. †  ﴾(u):Raifʻhār (t):Doremítzwr﴿ 17:41, 26 October 2007 (UTC)

link "present participle"
Couldn't there be a link to present participle ? Shouldn't there be ? --Jerome Potts 10:40, 5 October 2009 (UTC)

Link to Verb section
This template could yield a link straight to "<verb>#Verb", i.e.. --Jerome Potts 10:45, 5 October 2009 (UTC)

Include the translation
For non-English languages it would make peoples lives easier if we added a translation parameter for the the verb.--Dixtosa (talk) 18:58, 3 April 2015 (UTC)
 * I prefer for people to click on the link to the verb. Imagine a verb like the French verb which has six definitions. Many verbs have lots, lots more definitions. Do we list them all or just pick one at random because we like it the most? Renard Migrant (talk) 19:10, 3 April 2015 (UTC)
 * What are the odds of choosing a def at random will be the def we like the most? --Dixtosa (talk) 19:17, 3 April 2015 (UTC)

Named parameters include nocat, but it is not explained in the documentation
Perhaps something to do with suppressing a default handling at Category:Present participles by language, but it is not explained. Would be good if someone who knows the details with certainty could add it to the documentation. Quercus solaris (talk) 04:10, 13 August 2021 (UTC)

title: Template talk:present participle of


text:
Template talk:en-past of

Documentation
Use this template to show the simple definition for an entry that is the past tense or past participle inflection of a primary entry.

For most past tense entries, use in the definition line: # E.g., on "lionized":
 * Verb
 * Verb
 * Verb

Note that users can customize how the output of this template displays by modifying their monobook.css files. See “Form of” templates for details.

Parameters
This template is not language specific, but, if used with the lang parameter the relevant category can be applied to the article in which the template is included.

 * = used to specify the langauge i.e. English, Scots etc.

An example:

For the English word clamored (simple past and past participle of clamor):

This would place the article clamored in category:English simple past forms & category:English past participles

Past participle
This shouldn't be included in this template. {past and past participle of} would be better, but the past participle should be listed on a separate line anyways. DAVilla 01:15, 14 August 2006 (UTC)

inflected form
As some point in the deep dark past history of this template, I remember it using the inflected form, if the target exists. Is there some reason someone took out the "to " from this template? Perhaps I should have checked first - I hope it wasn't me. Admittedly, it seems very hard to have the "to " also be part of the wikified text (which it should?) --Connel MacKenzie 02:30, 29 January 2007 (UTC)

 * Yes the to should be there always in English as should the a for Romanian, and I forget what word for Icelandic. The whole lot including the to should be italicized but the to should not be wikified. I was just about to add it myself but despit being a good computer programmer I can't figure out this template wizardry at all! )-: — Hippietrail 20:15, 20 April 2007 (UTC)
 * Example of to wikify

no dot parameter
Some templates like this (I don't remember which) have a no dot parameter, which can be set to suppress the closing period. This enables the template to appear in a sentence, which I have found useful for entries that need some clarification, for example, which etymology the lemma form is. If someone has the time and knowledge, I'd be obliged. DCDuring TALK 16:33, 13 March 2008 (UTC)

 * Hmmm. It seems to have a nodot parameter. Time to clean my screen and recheck. DCDuring TALK 16:35, 13 March 2008 (UTC)

Parameter for pointing into a page
Is there a parameter for pointing into a page? Example: template past of is used in deserted to generate "Simple past tense and past participle of desert.". The link is to the page for desert, http://en.wiktionary.org/wiki/desert, but it would be better if the output from the template could point to the section for the verb on that page, http://en.wiktionary.org/wiki/desert#Verb --Mortense 16:13, 21 May 2011 (UTC)

 * Perhaps it should always point to the #verb section, even if there is no other section. Then you wouldn't need to change anything. SemperBlotto 16:50, 21 May 2011 (UTC)

 * Yeah, some 3 years later, how about it ? That is, point to the #Verb anchor, instead of to the #English one ? Pretty please ? Or else remove the edit protection restriction and let us commoners edit the source ourselves. --Jerome Potts (talk) 02:50, 25 April 2014 (UTC)
 * There is no guarantee that #Verb will lead to the right section. #English always will, on the other hand. 03:11, 25 April 2014 (UTC)
 * Is there much of an argument for staggering the anchor names to reflect indentation, so that it would be #EnglishVerb, #EnglishNoun, #FrenchVerb, etc? Equinox ◑ 21:02, 18 June 2014 (UTC)
 * If the software supported it, sure. Then we could do that for any language. 21:07, 18 June 2014 (UTC)
 * In what circumstances would #Verb not point to the English Verb section? According to About_English for words in multiple languages, English will always be listed first (except for Translingual), so #Verb will always point to the English one. See, for example man. I've opened a discussion on this at the Grease pit. JesseW (talk) 02:09, 5 July 2016 (UTC)

Not only past tense but also present and future passive voice!
Will any administrator please amend this
 * simple past and past participle of

into a more accurate and rarelier misleading
 * simple past and passive and past participle of?

Thanks 2003:44:CE18:4D00:89:4A52:6178:20CF 20:59, 18 June 2014 (UTC)
 * In English grammar, the past participle is understood to be passive for some verbs. However, it's not necessarily always passive. For example, there is no passive meaning in or in .  21:09, 18 June 2014 (UTC)

RFDO discussion: June 2014–June 2015
Per WT:RFDO. This is the same principle, just the template is more widely used. Two definitions, two lines. Not combined onto one line.

It would be very easy to replace this by bot. Quick, no; easy, yes. Renard Migrant (talk) 16:25, 5 June 2014 (UTC)
 * Keep. Common practice for language-specific templates is very different from general ones. Language-specific templates can and should cater to the specific needs of that one language, that's why we have them. 17:07, 5 June 2014 (UTC)

 * Keep: per CodeCat
 * KEEP per me too. Ready Steady Yeti (talk) 01:54, 6 June 2014 (UTC)

 * Kept but admin needs to remove RFD tag --Type56op9 (talk) 23:14, 2 June 2015 (UTC)

Recent change
I'm not sure what you've been working on, but could you return this template to the old style? Ioaxxere (talk) 21:11, 6 July 2023 (UTC)
 * What is wrong with the change I made? It is logically two separate inflections, and normally we list them separately in such cases. Benwing2 (talk) 21:40, 6 July 2023 (UTC)
 * For one thing, no one calls them "inflections"; most English speakers probably wouldn't even recognize the word. Second, having three lines bloats the page for no obvious benefit. Third, it's inconsistent with our headword template which groups "simple past and past participle" together. Finally, the template doesn't work at all with quotations, usage examples, etc. (see left). Ioaxxere (talk) 22:11, 6 July 2023 (UTC)
 * I brought this up in the BP. Benwing2 (talk) 22:23, 6 July 2023 (UTC)
 * Give the BP discussion a couple of days for people to respond and then I'll put it back if the consensus leans that way. Benwing2 (talk) 07:43, 7 July 2023 (UTC)

title: Template talk:en-past of


text:
fazzoletto

Etymology
Diminutive of, , itself from , from. Compare 🇨🇬,, Swiss-German Fazaneetli, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬.

Noun

 * 1) handkerchief, square
 * 2) neckerchief
 * 3) facial tissue, tissue paper
 * 1) facial tissue, tissue paper

title: fazzoletto


text:
Template talk:alternative spelling of

Another parameter?
The major complaint (in Wiktionary history) about a heading/template such as this, is that it is slightly too generic. I think there should be another parameter here, indicating what region or dialect the term is used in. Simply following the template with another sentence would leave it formatted correctly, but many people are confused by such a layout. And the information is more than slightly relevant; I'd say required. --Connel MacKenzie 16:49, 20 October 2006 (UTC)

 * Agreed, given that very many of these are Commonwealth/US variants (such as "haemoglobin"/"hemoglobin" and "foetus"/"fetus"). I've requested this in the Beer parlour. — Paul G 09:54, 18 March 2007 (UTC)

 * Has this been implemented? I think that should also categorize in Category:U.S. alternative spellings or Category:U.S. English alternative spellings instead of Category:English alternative spellings.—msh210 18:53, 27 August 2007 (UTC)

Yet another parameter
Shouldn't we indicate the gloss (in most cases) whenever this template is used? Would another (required) parameter help to this end? For example. Existing uses of the template without a "gloss" parameter could then be added to a category, or have a visible warning that the gloss is missing. Glossless cleanup category would be better, I think. --Connel MacKenzie 03:37, 31 December 2006 (UTC)

lang=
This needs the lang in the same format as. Would the lang= parameter adding person do the honors please? --Connel MacKenzie 04:58, 7 April 2007 (UTC)

 * Like this? -- Beobach972 18:19, 7 April 2007 (UTC)
 * No, that doesn't do the trick. Rather more like this. Unfortunately this change requires administrator privileges. -- Gauss 00:03, 7 August 2008 (UTC)

 * I'm not sufficiently code literate (or patient) to understand what your tweak examples do, but I was looking for the  to direct the wikilinked term to the appropriate language section. __meco 10:00, 28 February 2009 (UTC)

Why do we have to wikilink the required parametre?
...the first one, the entry pointed to. Why isn't the wikilinking hardcoded in the template code? --Jerome Potts (talk) 18:16, 26 January 2013 (UTC)
 * It is... the documentation just wasn't updated. I've done that now. 18:18, 26 January 2013 (UTC)

Please add validation
There should be some red text printed such as "Error: Cannot be an alternative spelling of itself", for examples such as this (which I just fixed).--Greenrd (talk) 06:44, 12 December 2013 (UTC)

Is - a letter?
It says "Spelling is the way words are formed with letters" but the example give is second-guess where the difference is - Perhaps this could be clarified with more examples? General Vicinity (talk) 12:22, 31 December 2021 (UTC)

title: Template talk:alternative spelling of


text:
Template talk:comparative of

Language anchor wanted
It should be easily implemented when the lang= parameter is supplied to also link the main word as e.g. blyg#Norwegian|blyg instead of merely blyg (for the word blygere). __meco 20:44, 30 April 2008 (UTC)

Link to Glossary
Shouldn't this link to Appendix:Glossary, not to the entry comparative? 75.212.217.187 (really, w:en:User:JesseW/not logged in 06:39, 16 June 2008 (UTC)

 * Yes. There is a strong case for the dictionary terms wiktionary uses to be defined in the specific sense we use them as defined in the internal glossary. DCDuring TALK 10:20, 16 June 2008 (UTC)

 * I have made the change. I don't think anything should break. DCDuring TALK 10:25, 16 June 2008 (UTC)

Include "more ugly"
Would there be any support of changing the wording to the following, or a similar idea to remove the necessity of understanding "comparative" from the template entirely. Conrad.Irwin 10:57, 17 June 2008 (UTC)
 * 1) Comparative form of ; more.

 * I like the idea. There would then be some maintenance to remove the extra "more X" that would appear on many entries. It would be a minor appearance improvement for such entries, once dupes were removed, because the inserte "more X" looks ugly with the period that follows the templated text. DCDuring TALK 11:47, 17 June 2008 (UTC)

 * Good idea! A colon might be better than a semicolon, though, since the two definitions are equivalent. —Ruakh TALK 12:08, 17 June 2008 (UTC)

 * Glad it's here. Looks good. I've already added it a few places in the course of failed attempts to use search to find instances of the template and following text with "more", to eliminate duplicated text. How might getting such a list be possible, through better use of search, another search tool, or otherwise? DCDuring TALK 01:22, 30 June 2008 (UTC)

 * I estimate that it would take me only another hour to finish using a manual scan of the 592 entries in the comparative category that I have not already scanned (6 instances of dupe text in first 200). IOW, it would not be worth anything custom unless it it is very quick. I wouldn't mind learning any search tricks that would have enabled me to better use search. DCDuring TALK 01:49, 30 June 2008 (UTC)

 * I have eliminated all the duplicate text I could find by reviewing all of the entries that use this template using popups. C. 25 in all.
 * Now we could use the same for . DCDuring TALK 15:10, 1 July 2008 (UTC)

More eläimellinen. Not good. If the lang parameter is defined, that should not be visible.--Jyril 20:16, 30 June 2008 (UTC)

 * Is it possible to suppress the "more [headword]" in English using something simple like "nomore=1"? I don't know how many instances there are, but more is not handled well, yielding "more more". If this really is the only possible instance, then I guess I should handcraft the senses that have this. DCDuring TALK 21:46, 24 May 2009 (UTC)

Colon vs. Semicolon
For the Comparative of and Superlative of templates, currently entries read as follows:

Comparative form of glassy: more glassy.

I feel a semicolon may make more sense than a colon.

Comparative form of glassy; more glassy.

I changed the templates but had the edits rolled back.

I recommend changing the templates to have a semicolon rather than a colon. Agree? Disagree? sewnmouthsecret 13:57, 17 October 2008 (UTC)

 * I disagree. A semicolon usually suggests two slightly different senses, whereas a colon usually conveys that what precedes is equivalent to what follows. When we describe something and then gloss it, I think the colon is the best and clearest punctuation mark to indicate that the description and the gloss are trying to convey the exact same thing. (Compare ordinary English: "Glassier is the comparative form of 'glassy': it means 'more glassy'" vs. "Glassier is the comparative form of 'glassy'; it means 'more glassy'." The latter sounds like two separate but related statements about 'glassier', whereas the former makes clear that only one statement is being made, but in two different ways.) —Ruakh TALK 14:23, 17 October 2008 (UTC)

 * From our definition on colon: "The punctuation mark ":" introducing a quotation or a series of items, or separating clauses."

 * The template in its current state doesn't fit this definition. I don't purport to be an expert in punctuation, but I just don't think this looks right. sewnmouthsecret 15:32, 17 October 2008 (UTC)

 * It falls under the "separating clauses" clause. (They're really clause fragments, a.k.a. phrases, because it's a definition and not a real sentence; but then, we'd have the same issue with a semicolon.) For a fuller explanation of the uses of the colon, see [[w:Colon (punctuation)]]; the use I'm describing is what's there called appositive, and it's the same category as what are there called syntactical-deductive and syntactical-descriptive. Now, colons and semicolons aren't mutually exclusive, and I'm not saying a semicolon would be wrong; but I do think that in a definition, a semicolon indicates a shift in sense, which in this case is not what we're trying to indicate. —Ruakh <i >TALK</i > 00:27, 18 October 2008 (UTC)

Split off English versions of Template:comparative of and Template:superlative of
These templates currently contain code that displays additional information in the definition when the language is English. I don't think that a general, language-independent template like this should contain code that caters to a specific language in this way, so I propose splitting off all English uses of these templates to and. 19:43, 22 April 2013 (UTC)
 * Support per nomination. Mglovesfun (talk) 11:16, 23 April 2013 (UTC)
 * Weak support. - -sche (discuss) 20:33, 1 May 2013 (UTC)

 * ✅ —Μετάknowledge discuss/deeds 22:18, 14 August 2013 (UTC)

is_lemma not working
needs to be categorized as comparative adverb and not a comparative adverb form, but  isn't not working. Also, I wish the parameters were simpler to use. For instance, making "lemma" or "adverb" in the fourth or fifth parameter trigger the appropriate behavior. But I don't know much about Module coding. — Eru·tuon 01:49, 25 March 2016 (UTC)
 * You can use  and add the appropriate category some other way. —CodeCat 02:17, 25 March 2016 (UTC)

title: Template talk:comparative of


text:
Template talk:feminine of

category sort key
I'd say please use instead of

--Jerome Potts 04:12, 29 May 2009 (UTC)

Link to language section
Currently this template doesn't link to the appropriate language section, even when lang= is provided. Could this be fixed please? —CodeCat 11:12, 4 October 2010 (UTC) One difference between this approach and yours is that yours will show the transliteration in boldface, while this will not. On the other hand, your approach will support gloss and gender(s), while this one will not, but if we want that in, then it seems like we'd want it at , too. —Ruakh TALK 13:10, 19 August 2012 (UTC)
 * I agree this should be done. It seems it can be done by changing it to, but someone should confirm that. —msh210℠ (talk) 06:57, 19 August 2012 (UTC)
 * How about ? (As you know, I'm not exactly a fan of, but  already has most of the same problems, so I don't think it'll make  any worse.)
 * Sounds good to me. —msh210℠ (talk) 05:45, 20 August 2012 (UTC)
 * Done. —msh210℠ (talk) 08:15, 13 January 2013 (UTC)

title: Template talk:feminine of


text:
SDR

Derived terms

 * , SDR RAM

title: SDR


text:
Template talk:past participle of

extra parameter
I reckon that someone should fiddle this, so that the link goes straight to eg. word, if you understand? --Keene 21:02, 10 April 2007 (UTC)

 * I agree, it probably should. --Connel MacKenzie 13:52, 16 April 2007 (UTC)

 * I forget at the moment, how to insert a "|" character while nested three deep in #ifeq:s, though. --Connel MacKenzie 13:58, 16 April 2007 (UTC)

 * Fixed. Not hard in this particular case, since we have lang always defaulting to English (don't need another #if) Robert Ullmann 14:03, 16 April 2007 (UTC)

title: Template talk:past participle of


text:
Category talk:Form of templates

untitled
For consistency, these templates should call . How? — Vildricianus 14:18, 16 June 2006 (UTC)
 * No longer applicable. DAVilla 20:31, 15 August 2006 (UTC)

Output change
I propose changing the output of these templates to include the word "form", where needed, to improve clarity. – Quoth 08:34, 29 June 2006 (UTC)

 * FYI, you'd get more feedback posting this proposal to WT:BP. Rod (A. Smith) 02:24, 30 June 2006 (UTC)

 * OK, thanks. I've created the discussion. – Quoth 06:34, 6 July 2006 (UTC)

 * I've created the template which can be adjusted with css to turn off this difference, for those who prefer it. DAVilla 05:00, 2 September 2007 (UTC)

RFM
To Category:Form-of templates. I don't see why Category:Form-of templates by language has a hyphen and this doesn't. Mglovesfun (talk) 11:15, 22 March 2013 (UTC)
 * I agree, I was going to suggest this myself. But I've been kind of trying to sort out and clean up that category anyway, and one thing I would like to do is to create subcategories for the different types of template. In particular, there would be a category for inflectional form-of templates like and another for alternative forms, spellings and such.  13:53, 22 March 2013 (UTC)
 * I've created the new category and moved the page contents over, but the templates themselves will need to be fixed by hand. 22:38, 27 April 2013 (UTC)
 * ✅ 23:00, 21 May 2013 (UTC)

As a copy-editing pedant, I’d like to say that you are all awesome. —Michael Z. 2013-05-22 02:39 z

title: Category talk:Form of templates


text:
Semite

Etymology
From, , from , from , from. Compare 🇨🇬, 🇨🇬, 🇨🇬.

Noun

 * 1) A member of a modern people that speak a Semitic language.
 * 2) A member of any of a number of peoples of ancient southwestern Asia and East Africa such as the Akkadians, Assyrians, Arameans, Phoenicians, Canaanites, Hebrews, Arabs, or Aksumites.
 * 3) A descendant of any of these peoples.
 * 4) A descendant of the biblical Patriarch Shem.
 * 5)  A Jew.

Translations

 * Czech:
 * Finnish:
 * Icelandic: semíti
 * Irish: Seimíteach
 * Polish: ,
 * Portuguese:

 * Arabic: ,
 * Armenian: սեմիտ
 * Chinese:
 * Mandarin: 閃米特人
 * Czech:
 * Dutch:
 * Finnish:
 * French:
 * German:, Semitin
 * Hebrew: שמי, שמית
 * Icelandic: semíti
 * Irish: Seimíteach
 * Italian:
 * Japanese:, セム族の人
 * Kazakh: семит
 * Polish: ,
 * Portuguese:
 * Russian: ,
 * Spanish: semita
 * Ukrainian: семі́т, семі́тка
 * Volapük:,  hisemitan,  jisemitan

title: Semite


text: Template:misspelling of

title: Template:misspelling of


text:
Wiktionary:Grease pit/Problems displaying IPA + Classes for support of Unicode ranges

Problems displaying IPA in edit & special chars boxes
These items broken out of the thread on UK/US spellings, for convenience:

I should like to know how to display all the IPA characters everywhere -- the notes in Help don't work for me -- I can see the characters in the finished product, but not in the Special Characters box or Edit box on edit pages). Can anyone help?

 * . I've never had any problems. —Vildricianus 15:54, 31 May 2006 (UTC)

 * I had assumed that it was a problem with the fixed width font used in my edit box (Courier New). However, I have just realised that the Special Characters box seems to have the ordinary PS font, and I can't see them there either (in fact there are only nine I can see (øəœæŋβθðχ and ħ). Any ideas (other than using Firefox)? In the main areas I can see all the IPA characters on English pronunciation key, though there are a few near the bottom of International Phonetic Alphabet which I can't see. --Enginear 07:07, 6 June 2006 (UTC)

 * It would be easier if you started a new topic on this. It would also help if you specified your browser and OS. — Vildricianus 10:06, 6 June 2006 (UTC)

 * Done. I am using IE 6.0.2900.2180 with service packs 1 & 2, under Windows XP Home Edition version 5.1.2600 with SP1 & SP2. --Enginear 23:08, 6 June 2006 (UTC)

 * Many months ago while I was crafting or extending the special characters box, I put a lot of work into finding a way to use the template - it required tricky stuff that I believe Connel or somebody helped me with. But months later I noticed somebody took that all out and I never knew why. Now on most of the computers I use I see just boxes for almost all of the IPA characters even though in the articles where IPA or IPAchar is used they work fine. Somebody needs to hunt through the history and find what I did and who and why it was removed. It may have been removed before this magic was even in Mediawiki:Edittools — Hippietrail 23:49, 6 June 2006 (UTC)

 * I just rolled back the apparent vandalism to of January 19th, that got lost in the shuffle of (Karmosin's and Peter Isotolo's opinions) vs. (Wiktionary) pissing contest.  It should be working now.  --Connel MacKenzie T C 05:26, 7 June 2006 (UTC)
 * But adding that to both and  did not seem to fix it for IE.  --Connel MacKenzie T C 05:32, 7 June 2006 (UTC)

 * Neither nor  would affect this, for neither is called from Mediawiki:Edittools. I tried editing a copy of Mediawiki:Edittools in the sandbox and I found I could get the IPA character to display if I delete "font-family /**/:inherit;" from the IPA span tags. (This of course is undesirable, because it applies  to all browsers not just IE6. But it show that the problem is the sensitive nature of the style parameters in Mediawiki:Edittools.)
 * A clean solution is described in the next section: Define font-family with appropriate fonts into class="IPA"; specify class="IPA" in Mediawiki:Edittools (it turns out it is already there); and delete the style="font-family...;" from Mediawiki:Edittools.
 * Wikipedia has the same problem with IPA display in Mediawiki:Edittools. I was able to fix it (with a copy in the sandbox) by applying class="IPA" to a span containing the IPA characters. --teb728 06:58, 7 June 2006 (UTC)

 * Say what? What sandbox was that?  The inherit thing is only for the IPA characters in  IE.  IE is the only one that isn't displaying them correctly, to begin with!  --Connel MacKenzie T C 14:05, 7 June 2006 (UTC)

 * I refered to two sandboxes: I did my experiment with Wiktionary:Mediawiki:Edittools at Sandbox, and I did my experiment with Wikipedia:Mediawiki:Edittools at w:Wikipedia:Sandbox. (Last night I created a semi-permanent copy of the latter experiment in a personal sandbox.)
 * I believe you are wrong about the "inherit thing." The way it is supposed to work is exploit a known bug in IE: First it tells all browsers to use the font list; then the inherit thing tells browsers to override the font list and inherit the font(s) from the surrounding scope. But due to a bug in IE the inherit thing is ignored by IE; so IE (and only IE) is left with the font list. What my first experiment shows is that for some reason (presumably related to the complicated HTML in Wiktionary:Mediawiki:Edittools) IE does not ignore the inherit thing there. My second experiment shows that much simpler HTML works as intended. See w:Template talk:IPA. --teb728 04:29, 8 June 2006 (UTC)

 * Oh, OK. I think I see now.  Hippietrail, did you follow this too?  Shall we flip a coin then, to decide which of us should put TEB's changes in place?  --Connel MacKenzie T C 05:09, 9 June 2006 (UTC)

Mediawiki software change
I just discovered what happened: On about 2005-10-02 the Mediawiki software was changed to no longer allow comments in inline style sheets (because they can be used for cross-site scripting attacks). See Wikimedia bug no. 3588. As a result of this change "font-family /**/:inherit;" affects IE6 the same as other browsers (except in css). There are 3 possible responses: --teb728 18:08, 8 June 2006 (UTC)
 * Leave IPA display broken for IE6. (IMO unacceptable)
 * Remove "font-family /**/:inherit;" several places from Mediawiki:Edittools. This will have the side effect of applying the font list to all browsers, not just IE6. (IMO marginally acceptable)
 * Move the font-family specifications (including "font-family /**/:inherit;") to CSS (to which the Mediawiki change does not apply). This is the response chosen by Wikipedia. See the section "Font declaration has been moved to Common.css" at w:Template_talk:IPA.

Classes for support of Unicode ranges
I would like to propose that we borrow an idea from Wikipedia. There they define classes in Mediawiki:Common.css specifying fonts giving optimal support for various Unicode ranges: /* Support for Template:IPA, Template:Unicode and Template:Polytonic. The inherit declaration resets the font for all browsers except MSIE6. The empty comment must remain. Please copy any changes to Template:IPA fonts and Template:Unicode fonts. */ .IPA { font-family: Chrysanthi Unicode, Doulos SIL, Gentium, GentiumAlt, Code2000, TITUS Cyberbit Basic, DejaVu Sans, Bitstream Vera Sans, Bitstream Cyberbit, Arial Unicode MS, Lucida Sans Unicode, Hiragino Kaku Gothic Pro, Matrix Unicode; font-family /**/:inherit; } .Unicode { font-family: TITUS Cyberbit Basic, Code2000, Doulos SIL, Chrysanthi Unicode, Bitstream Cyberbit, Bitstream CyberBase, Bitstream Vera, Thryomanes, Gentium, GentiumAlt, Visual Geez Unicode, Lucida Grande, Arial Unicode MS, Microsoft Sans Serif, Lucida Sans Unicode; font-family /**/:inherit; } .latinx { font-family: TITUS Cyberbit Basic, Code2000, Microsoft Sans Serif; font-family /**/:inherit; } .polytonic { font-family: Athena, Gentium, Palatino Linotype, Arial Unicode MS, Lucida Sans Unicode, Lucida Grande, Code2000; font-family /**/:inherit; } .mufi { font-family: Alphabetum, Cardo, LeedsUni, Junicode, TITUS Cyberbit Basic, ALPHA-Demo; }

Having done that the various templates IPA (equivalent to IPAchar here), Unicode, latinx, and polytonic specify only the class; they no longer specify the font-family, saving a transclusion.

If we do that, we could also modify Mediawiki:Edittools to specify appropriate classes for various ranges. For example on my browser (IE6) most IPA characters display as boxes, as do various Latin extended characters, including Old English ǢǣǷƿȲȳȜȝ.

 * Unsigned comment by USer:TEB728

While I agree that that is an interesting approach, I detest putting things into the site-wide Javascript and CSS files that are not needed on every page. (I've done it, but I'm not happy about it.)

The template approach is highly superior, in that it is not overwhelming every single page on en.wiktionary, but instead, only the pages that need it. --Connel MacKenzie T C 05:10, 7 June 2006 (UTC)

 * I would say just the opposite is the case: With the css approach the class definitions do not cause the file to be downloaded more often than otherwise. (And I suspect it is cached anyway.) With the template approach and/or  and/or  may be transcluded several times per page.
 * I didn't realize when I created this section that the previous section described a problem to which my section provided a solution. If you use IE6, compare w:Mediawiki:Edittools with w:User:TEB728/My Edittools. --teb728 07:25, 7 June 2006 (UTC)

 * I don't see any difference, but that's probably because I haven't updated my IE6 for a while. I'm wondering, though, is IE7 going to improve on that? — Vildricianus 17:33, 8 June 2006 (UTC)

 * Not sure how the CSS works here, but caching is the argument that makes the most sense to me. The CSS files aren't dynamic links, are they? Davilla 17:19, 8 June 2006 (UTC)

 * I spotted a fallacy in your comment, Connel: every page is supposed to have IPA somewhere in the future :-). — Vildricianus 09:12, 7 June 2006 (UTC)

 * Every Talk: page? Every Image: page?  Every Wikisaurus: page?  Every Transwiki: page?  etc.  No.  Not even Main Page.  --Connel MacKenzie T C 13:59, 7 June 2006 (UTC)

 * Including that crap on every single page (try "View HTML source") is a Bad Thing. --Connel MacKenzie T C 13:59, 7 June 2006 (UTC)

 * Right. Non-main namespace pages are not the "pages" I was talking about. They're only there to support the real "pages". And tell me what's wrong with the page sources. The only argument I see for not using Common.css is that it's not editable for non-admins. — Vildricianus 15:11, 7 June 2006 (UTC)

 * Page load time/size, as you often point out to me. I'm sorry, but having it only where needed seems to be a highly superior solution.  --Connel MacKenzie T C 15:20, 7 June 2006 (UTC)

 * I'm not so sure anymore of the page load differences for the various CSS and JS files that need to be loaded. That is, they have to be loaded anyway. I doubt whether their sizes really matter (perhaps in terms of milliseconds). Having defined classes for a couple of things could be superior to templates, if used sparingly. — Vildricianus 15:23, 7 June 2006 (UTC)

 * OK, I tried "View HTML source" on this page. I don't see any part of Mediawiki:Common.css. I don't think it appears in the HTML source of any page (except Mediawiki:Common.css itself).

 * Conversely, trying "View HTML source" on beon-wesan, I get 1 transclusion of, 4 of , 1 , and 1 of the fonts in.

 * Does it bother you that Mediawiki:Common.css defines (for example) classes for wikitable and prettytable even though neither is used on most pages? --teb728 05:43, 8 June 2006 (UTC)

 * Looking at the comments far above: Ahhh. And BTW, yes, it bugs me that CSS doesn't work the way my brain does.  :-)     --Connel MacKenzie T C 04:44, 9 June 2006 (UTC)

 * I disagree with Connel and I am pretty sure the Wiki devs would too. The CSS pages are precisely where site-wide CSS is supposed to be and it's the reason CSS exists in the first place. Inline styles are generally considered bad. If you watch the dev list or Recent changes over on the English Wikipedia you'll see people are actively replacing inline CSS with CSS classes and IDs which are in their site-wide CSS. Neither the CSS nor the JS pages are downloaded every time you look at a page. They have some kind of timestamp which specifies how often they are downloaded in case of changes - that's why you have to hit CTRL+F5 every time you edit a CSS or JS page.
 * Anyway classes like this are a good idea and I have made several based on and  over the past year or so:, , , , , etc. By the way, the inherit/comment hack for MSIE seems to now be discouraged. — Hippietrail 23:06, 9 June 2006 (UTC)
 * Exactly. One big argument against them is that they can't be edited by non-admins. But then, they actually don't have to be very often. — Vildricianus 23:11, 9 June 2006 (UTC)
 * Actually, the inherit/comment hack in not mearly discouraged, it is disabled. Specifically the wiki software now replaces comments in inline styles with a single non-breaking space. This applies, however, to inline styles but not CSS; if you should implement my suggestions, be sure to include the hack. BTW did you notice Connel's latest comment at ? He seems to agree that you or he should implement my suggestions. --teb728 03:53, 10 June 2006 (UTC)

Specific proposal
If I understand correctly, there is consensus that my proposal should be implemented. So I propose specifically that the following be appended to Mediawiki:Common.css (just ahead of "/*
 */"). /* Support for script templates. The inherit declaration resets the font for all browsers except MSIE6. The empty comment must remain. */ .IPA { font-family: DejaVu Sans, Segoe UI, Lucida Grande, Lucida Sans Unicode, Charis SIL, Doulos SIL, Code2000, Gentium, Gentium Alternative, TITUS Cyberbit Basic, Arial Unicode MS; font-family /**/:inherit; } .Unicode { font-family: TITUS Cyberbit Basic, Code2000, Doulos SIL, Chrysanthi Unicode, Bitstream Cyberbit, Bitstream CyberBase, Bitstream Vera, Thryomanes, Gentium, GentiumAlt, Visual Geez Unicode, Lucida Grande, Tahoma, Arial Unicode MS, Microsoft Sans Serif, Lucida Sans Unicode; font-family /**/:inherit; } /* Arabic */ .AR { font-family: Tahoma, Arial Unicode MS, Code2000, Traditional Arabic; font-family /**/:inherit; font-size: 125%; } /* Bengali */ .BN { font-family: UniBangla, Arial Unicode MS, Code2000, Likhan, UT Bengali Dhaka, Vrinda; font-family /**/:inherit; font-size: 130%; } /* Persian */ .FA { font-family: Tahoma; font-family /**/:inherit; font-size: 125%; } /* Kashmiri */ .KS { font-family: Tahoma; font-family /**/:inherit; font-size: 125%; } /* Kurdish */ .KU { font-family: Tahoma; font-family /**/:inherit; font-size: 125%; } /* Latin Extended-B .latinx { font-family: TITUS Cyberbit Basic, Code2000, Microsoft Sans Serif; font-family /**/:inherit; } /* Polytonic Greek */ .polytonic { font-family: Athena, Gentium, Palatino Linotype, Arial Unicode MS, Lucida Sans Unicode, Lucida Grande, Code2000; font-family /**/:inherit; } /* Russian and other Cyrillic */ .RU { font-family: Arial Unicode MS, Gentium, Code2000, Lucida Sans Unicode; font-family /**/:inherit; } /* Sindhi */ .SD { font-family: MB Sindhi, MBSarang Sattar, MB Bhitai Sattar, MB Lateefi, Ayaz Gul, Tahoma; font-family /**/:inherit; font-size: 125%; } /* Thai */ .TH { font-family: Arial Unicode MS, Code2000; font-family /**/:inherit; font-size: 125%; } /* Urdu */ .UR { font-family: Tahoma; font-family /**/:inherit; font-size: 125%; }

Also that the style specifications be removed from the  tags in the "IPA" paragraph of Mediawiki:Edittools, thus:  Vowels: ··· Other: Consonants: Also that a  be added to the "Old English" paragraph of Mediawiki:Edittools, thus:  --teb728 15:29, 13 June 2006


text:
Wiktionary:Grease pit/User CSS vs. real MediaWiki preferences

User CSS vs. real MediaWiki preferences
One of the major hurdles facing our customization efforts is that most users want nothing to do with "monobook.css". We need a way to let users select CSS options through Special:Preferences. I think we need a developer liaison to help us with that task, right? Rod (A. Smith) 17:23, 29 May 2006 (UTC)
 * See User talk:Hippietrail. Had this page existed back then, I could have asked here :-). —Vildricianus 18:20, 29 May 2006 (UTC)
 * Thanks. My summary of that conversation follows. Please fix any mistakes in my paraphrasing:

[It would be ideal to make customization easy without fiddling with CSS or JS, something like Special:Preferences, or something that can be made via a small developer intervention.] —Vildricianus 21:01, 21 May 2006 (UTC)

 * Like, having separate skins? :-)  --Connel MacKenzie T C 21:16, 21 May 2006 (UTC)

 * [...] Without opening a gateway between the Wiktionary hackers[...] and the actual MediaWiki hackers, there is no way for us to add features or customize besides Javascript, CSS, templates, and connecting via those to offline sites such as Connel's site where the random code is. It's true this is not user-friendly for non-hackers but there are several things we can do:
 * We can use JS to add extra prefs pages which generate the code which can then be copied and pasted into the users's CSS and JS pages.
 * We can coordinate a group of JS/CSS/Template hackers, possibly some of us can start hacking MediaWiki on our own machines or on a public site with CVS access for us, with another group of nonhacker Wiktionarians who can use and promote our changes to the MediaWiki devs etc, thereby opening a dialog so that when we have patches we want added to just en.wiktionary.org that we won't be ignored and won't be just 2 or 3 lonely voices
 * There may be a lot more we can do with JS if the devs give us just the power to define a few cookies of our own - that would make possible adding JS/CSS customization directly from a new prefs page to the user's custom JS and CSS pages, among many other things.
 * I think we need to continue with what we're doing, provide much more documentation and encouragement for non-hacker Wiktionarians to use our work, accept it, get used to communicating with us on improving it, help them to understand how we are held back by not having developer access to our own project, and getting such users to support our efforts on the way to either some of us becoming MediaWiki devs, or sustaining a reliable open chanel with the MediaWiki devs, or getting MediaWiki to split off to a certain degree en.wiktionary.org in some way that allows some of us to be devs just on it so that we can develop it into a dictionary-specific MediaWiki with our own extensions, etc.
 * I think that's the short-term and long-term visions[...]. — Hippietrail 00:14, 23 May 2006 (UTC)

Excellent. Now if "preload" could be allowed to work with existing pages, we could enable finely-detailed, easy configuration of Special:Mypage/monobook.css, e.g. by having JS in Special:Preferences expose something like http://en.wiktionary.org/w/index.php?action=edit&preload=Template:custom-monobook-mentionBold-inflectionTable-serialcommaHidden&title=Special:Mypage/monobook.css, based on users selecting preference options. Rod (A. Smith) 20:04, 29 May 2006 (UTC)

 * Even nicer, would be to have the "Preferences tabs" (and content therein) modifyable in Special:SystemMessages. The dev's might think that is a bit heretical, as all preferences would need corresponding software/extensions.  --Connel MacKenzie T C 20:26, 29 May 2006 (UTC)
 * This might not solve all the problems. It will give us the tabs but how will it let us invoke the actions that fiddling with the tabs should invoke? What might work is a feature request specifically for Preference tabs which manipulate only CSS - perhaps with a new CSS page that is not editable by hand - there are already several levels of CSS. I encourage you to talk to the devs on IRC which I cannot do, or file a feature request, and I will join in. — Hippietrail 21:25, 29 May 2006 (UTC)

 * As a first step, I have posted Bug 6134, "The possibility of creating and manipulated cookies via JavaScript". — Hippietrail 22:38, 29 May 2006 (UTC)
 * Sad to say, Brion has closed this one as invalid with only the comment "You might want to check a general JavaScript reference". I don't find that helpful at all. Is there anybody here who knows enough JavaScript to explain the problem? — Hippietrail 23:09, 29 May 2006 (UTC)
 * Don't know Javascript but enough to know that you can add cookies via Javascript. That would require adding Javascript to a page, and the MediaWiki where it allows it I don't know well enough, but I suppose it must if e.g. TOC is collapsible. Davilla 16:04, 31 May 2006 (UTC)
 * I take that as encouragement that they are allowed (via Javascript.) I'll have to try soon.  --Connel MacKenzie T C 23:58, 29 May 2006 (UTC)

 * I'm on a roll so I also posted Bug 6135, "A way to manipulate CSS-based preferences via the GUI". Please participate in these bugs reports if you can. I fear a lone voice may well be ignored. — Hippietrail 23:03, 29 May 2006 (UTC)
 * Shouldn't we ask if these things are already possible before writing them as requested features? Or maybe this is just my reaction to seeing these and requests from other folks labeled as "bugs". If it's odd to me, it's a form of dialogue anyways. Davilla 16:33, 31 May 2006 (UTC)
 * I try to file a request before I'm pretty certain there's not a way to solve it already. If there is a way it's only a minor embarassment and the request will be closed. Bugzilla covers bugs and feature requests, each item is marked as one or the other but for Bugzilla purposes only, feature requests are a subtype of bug. Nothing to worry about, just jargon. — Hippietrail 17:19, 31 May 2006 (UTC)

I haven't followed all this, and I don't have my head fully wrapped around CSS and skins yet, so pardon me if I misstate, but let me see if I've got the basic picture. I don't think it would be out of the question to devise a mechanism which would allow such extensions, and if implemented reasonably, I doubt the MediaWiki devs and WikiMedia admins would object.
 * 1) We need a way to set our own (per-project) cookies, to affect behaviour in our per-project CSS. (I presume we're already in charge of our per-project CSS and that there's no other big problem there.)
 * 2) The right way to get those cookies set would involve new questions and checkboxes on the Preferences page.
 * 3) Therefore, what we need is a way to add per-project extensions or other customizations to the Preferences page.

If this is a reasonable track to go down, I'll look into the feasability of such an extension mechanism (I'm becoming somewhat familiar with the mediawiki software), and ask on the Wikitech mailing list whether they think this is a reasonable track to go down. –scs 21:34, 31 May 2006 (UTC)

 * Unless I've missed something, I don't think cookies have anything to do with the challenge. Instead, I think we need the ability for users to modify their Special:Mypage/monobook.css file through selections in Special:Preferences. Rod (A. Smith) 21:46, 31 May 2006 (UTC)

 * "Users to modify their monobook.css file"? What user monobook.css file?  I don't have my own monobook.css file, do I? (/me finally gets around to trying that special link) Oh!  Lookit that!  I do potentially have my own monobook.css file, and pretty easy to get to, at that!

 * Anyway, all the talk about cookies (here in this subthread, that is) made me think someone was talking about having the site-wide CSS script adjust its own behavior, based on simple cookies, so that users wouldn't have to mess with per-user CSS at all (which, convenient though I now see the Special/Mypage link is, is still pretty far from what we'd want the average user to have to mess with). But come to think of it, there probably isn't a way to have CSS look at cookies.  (Now where did I get the idea someone was saying there was?) –scs 22:56, 31 May 2006 (UTC)

 * I was wondering whether you are still considering devising a temporary solution via preload templates? —Vildricianus 22:00, 31 May 2006 (UTC)

 * The "preload" solution would probably be a single line of code for developers and flexible for us, so I hoped that would be easy for us to get. I don't know whether they will approve that request, though. Rod (A. Smith) 23:11, 31 May 2006 (UTC)

 * I don't get the "preload" business to solve this - can somebody explain it a little? — Hippietrail 02:11, 1 June 2006 (UTC)

 * My proposal is to use JS on Special:Preferences to create CSS and to preload it over Special:Mypage/monobook.css. The user would then preview and save the generated css. Each Special:Preference option would correspond to a display preference like "bolded mention" or "gender period visibility". Rod (A. Smith) 04:16, 1 June 2006 (UTC)

 * If you type in a non-existant term in the search box, and press [Go], you are given a table of various "preload" templates that can be preloaded when you edit that entry. Once an entry exists, the preload capability no longer functions.  So the "Buttons" concept is, IMHO, quite superior...see User:Vildricianus/monobook.js for examples.  Using Javascript, we could be completely evil, and shrink the edit box size down to very small (or hide it entirely) when editing Monobook.js/monobook.css...and fill the screen with button options.  That would be very evil though.  And the Javascript would have to be pretty advanced, to be able to check and uncheck boxes.  Additionally, since we can tack on goofy no-op parameters onto the URL, we could still enable raw editing under certain conditions.  Of course, these ideas go far beyond "klugy" into the realm of "sinister" and I would not be comfortable doing such a hideous thing.  Didn't I say something like that about the LC/UC redirects?  --Connel MacKenzie T C 22:35, 1 June 2006 (UTC)


text:
Wiktionary:Grease pit/Tricky templates

Tricky templates Part I
What's going on with the entire italbrac and cattag stuff? These templates are becoming ever more complicated, each one calling another couple of templates. Are you guys sure that's all necessary? Keep in mind to keep it as simple as possible; people who come after us should still be able to understand what we're doing. If it's really necessary, then please document it thoroughly. I'm afraid saying "documentation is on meta" is not sufficient.

Here's the list of templates called for the simple tag :
 * Template:cattag
 * Template:cattag/category
 * Template:cattag/pass1
 * Template:cattag/standard
 * Template:chemistry
 * Template:foreach
 * Template:foreach/pass1
 * Template:italbrac
 * Template:italbrac/pass1
 * Template:x0

Although it's an amazing job what you guys are doing there, I'm sure this can be simplified. — Vildricianus 15:06, 5 June 2006 (UTC)

 * It could be simplified ten times if the wiki syntax had some basic functionality built in that it doesn't. The template foreach is documented on meta but it should really be a built-in construct, avoiding some of the hacking that has been done with special symbols and resulting in less literal evaluation. In fact on meta it's carried out to 150 arguments, which I considered to be a ridiculously excessive means to approach the problem. Recursion is also problematic because it isn't allowed explicitly, but it is allowed if you use redirects. In fact these were not implemented with forward thinking because some limited recursion is not necessarily evil and could be accomplished much more cleanly. As it is they've tried to avoid problems by limiting capability, which doesn't do anyone any favors. Nonetheless I think I may have discovered a way to perpetually slow down the servers that of course I don't want to test. That would perfectly exemplify why it's better to use a clean approach.
 * Then it's difficult to keep the code itself looking clean because extra spaces are often translated into the output. In general there is a confusion of code and data that produces too many special cases. In fact I'm taking advantage of this as the only way in my case to know the level of recursion. If there were a simpler construct such as a static variable or a way to check the call history then this would not be necessary. Of course I'm not asking for that functionality because it would just make the whole system that much more of a mess. All of this in fact is jumping through hoops to get around a bug that reassigns passed variables when undeclared variables are checked for. This system of variable passing is itself a rather nasty concoction, relying on old call by name (rather than value) and text replacement principles that have been eliminated in modern languages, whatever the meta site might claim. Davilla 07:00, 6 June 2006 (UTC)

 * I empathize with you, Davilla. Since we are building increasingly tall large towers from our stone knives and bear claws, it is becoming increasingly important to be able to verify template functionality after even minimal changes.

 * To that end, I've drafted a rudimentary functional testing pattern (with use instances at Template talk:en-infl-verb/test and Template talk:en-infl-noun/test) about which I'd appreciate any comments. The pattern is to create a test suite as one or more subpages of the template's talk page that exercise the template's functionality in a human-verifiable format. Each test obviously needs to show both expected behavior and actual results.

 * Immediately obvious deficiencies include caveats about namespace and pagename evaluation as well as the need for manual verification. The former is ugliness we can probably cope with and the latter can be addressed via external tools. In any event, if we improve and follow a template testing pattern, we should simplify the maintenance tasks for ourselves and for those who follow us. Rod (A. Smith) 08:17, 6 June 2006 (UTC)

 * It could be simplified ten times if the wiki syntax had some basic functionality built in that it doesn't.
 * There's a good reason MediaWiki doesn't allow much of this sort. Recursion, passes, variables and loops are beyond me I'm afraid - maths has never been my thing - but I'm talking about a general idea here.
 * There's also a good reason why has been deleted from Wikipedia. These things do pose a strain on the servers, not yet for us, but for bigger sites with more visitors. Perhaps we get better servers, or better software before we're big enough to have problems, though. Please continue with experimenting and expanding the templates, but also keep in mind some of this stuff. — Vildricianus 18:33, 6 June 2006 (UTC)

 * Server strain is a perfectly good reason why foreach should be a language construct rather than a text-based evaluation. Ideally a single parameter would be treated as a single parameter and not 150 like the foreach on meta requires. When I copied it I doubted we'd ever have need for more than nine arguments to any template, so that should avoid some of the overload that Wikipedia experienced. But that could create an arbitrarily low limit as well. I'll take a look at foreach and see if there's any way to streamline it.
 * Unfortunately cattag is rather complicated and there's not much I can do to eliminate the extra templates. In fact I would like to create more because there's so much shared code which would be easier to read as subroutines, but I've refrained as per your request. I'll see if I can reduce the number of calls to category from four or five down to two, which will make inlining that template feasible, but that's about all that can be done. A higher priority right now is making sure that the categorization is completely functional.
 * As for italbrac and italbrac-colon, they seem simple enough to be rolled into cattag and other functions once they've been proven and weather tested. In fact I sort of had to do that already, but opted to split italbrac into several parts (first, inner, separator, and last, in addition to pass1) to allow them to be customized. If I had hard-coded it into cattag I don't think anyone would have wanted to touch it. But I'll roll them in eventually. Davilla 19:13, 6 June 2006 (UTC)

 * Thanks for considering it. I'm merely concerned with 1/ complexity of things (i.e. if the few people here that understand it decide to leave all of a sudden, everyone else is stuck); 2/ server strain (per below); 3/ possible vandalism targets (see also below). Other nuisance is the list of templates used on a page getting ever bigger, making it harder to find out which are actually used.

 * Also of note, if we're going to keep this the way the tag templates work, all their meta-templates will have to be protected, if not fully, then at least semi. Once these templates become more widespread, any change to any of their meta-templates will create a job queue of a couple of hundred thousand articles. — Vildricianus 09:42, 7 June 2006 (UTC)

 * Agreed, agreed, agreed. I'm afraid though that once cattag is established the only way to make any changes will be to replace the system in full. The reason it has to be so complicated is that it relies on the existence of other templates to know what the parameters should expand to. Because of language limitations this isn't an easy task. I'll take a fresh look at cattag to see if it can't at least be simplified, maybe reducing the strength of some of the error checking. I'm used to the typical input/compute/output model and there's a strange way of looking at wikicode that allows functions to be inserted mid-sentence. In some cases if it's done right then separate sections can be combined, avoiding duplicity or eliminating the need for subroutines, and making the code more readable and therefore editable. I'm also open to suggestion on how to format without stripping out all extra whitespace. Davilla 15:58, 7 June 2006 (UTC)

 * Have you considered Rod's trick ? That allows spaces and blank lines. — Vildricianus 19:31, 7 June 2006 (UTC)

 * I feel pretty strongly that Rod's suggestion above is most relevant. cattag should not be doing all this verification - that should be done offline.
 * I am alarmed to see so many separate calls. Even if the optimization is as good as people say it is (which I can believe, but choose to doubt) there are still that many recursive calls for each page edited.  This should be subst:'ed up into their parent template(s) wherever possible.  Where not possible, offline verification should be considered.
 * On the other hand, I do like the clever features I see being added. It is a pretty tough call, but I think we can get this back into one single template if we put our collective intelligence to it.  --Connel MacKenzie T C 05:45, 9 June 2006 (UTC)

cattag
I've been trying to get cattag to work so that if produces  then  produces {{ italbrac|lexicography|dated}. Right now I use at template:lex and have a magic list at cattag/standard that substitutes lexicography for the parameter lex. But the magic list I think is troublesome because it has to be maintained. What I'd like to do is use the label templates themselves as magic lists. That is, if a template exists, for instance, and if the content is different from the template name, in this case mathematics, then use the content of the template rather than the abbreviated parameter. But the content of the template is actually unevaluated and (mathematics) evaluated, and I don't know how to strip the parenthesis or any of that other junk off. Davilla 17:05, 3 June 2006 (UTC)
 * added two SA words, kaalgat and gatvol with the catagory, but it hasn't shown up on the catagory page. Any ideas why? Andrew massyn

 * Categories take up to five minutes to refresh, some times. Also, kaalgat does not seem to use the cattag template.  --Connel MacKenzie T C 19:14, 4 June 2006 (UTC)

 * If you use cattag, as you should for more than one label, or if you use any of the label templates that (should) call cattag, then the category will not be added if the category does not exist! This is meant to avoid the creation of categories that might duplicate ones alternatively worded, such as Category:South African English instead of Category:South Africa. I am working out some kinks with abbreviations as in the above text, and then I will document how to indicate categories when the name differs. Davilla 14:31, 5 June 2006 (UTC)

 * Okay I've found a crazily complex work-around and rolled in this new version. Using will produce the same result as  +  +  whenever the templates exist, provided they call cattag themselves, and just the plain text otherwise. Oh, plus categories when they exist as well. Try out the new system and see how well it works and if there are any special considerations that should be addressed. Davilla 19:26, 6 June 2006 (UTC)

This is a crazy thing, I'm tellin' ya. What's the difference between and ? — Vildricianus 19:28, 14 June 2006 (UTC)

Tricky templates Part II
This is the list of templates "in use" when I use one of the new verb templates (in the form of ). Page tested is User:Vildricianus/PageX/4, which has only said template.

 * es
 * itemiz
 * valid
 * Template:,
 * Template:ARchar
 * Template:Arabic font size
 * Template:Arabic fonts
 * Template:bottom
 * Template:en-infl-verb/getPast
 * Template:en-infl-verb/getPastP
 * Template:en-infl-verb/getPres3rdSg
 * Template:en-infl-verb/getPresP
 * Template:en-infl-verb/isValidPageName
 * Template:en-verb
 * Template:gender period
 * Template:isValidPageName
 * Template:m
 * Template:mid
 * Template:n
 * Template:see
 * Template:seeCites
 * Template:serial and
 * Template:top

This is not to criticize the work that has be done, hardly so. On the contrary, I'd like to find out how we can preserve it by making the above list shrink. "Shrink", that is, both physically and visually.
 * 1) Physically: how the heck do I get ARchar, m, mid, seeCites and friends used by ?
 * Already found: because of es. Why is es said to be a template here? It's a parameter. Is there any way they could be excluded from that list?
 * 1) Visually: could there be any way that the "templates in use on this page" is trimmed, displaying only the templates primarily used on the page, so not the secondary ones like /getPast etc.? Should I attempt this at bugzilla? — Vildricianus 21:39, 17 June 2006 (UTC)

 * Yes, that's an annoyingly long list of templates. The "es" and "itemiz" seem stange. It looks like they could be the result of some bug in . I will look into that. As for the others, I split up the functionality of into subroutines because I think that makes the template itself easier to read, but if the editor community desires, I could flatten the subroutines into the top level template. Rod (A. Smith) 22:40, 17 June 2006 (UTC)

 * What would be a real solution is if there were a software-based enhancement for it. If it's not going to happen (likely), I don't think it's really necessary to re-include the subtemplates into the main one. It's up to you. — Vildricianus 23:00, 17 June 2006 (UTC)

 * The easiest way to do this would be to give templates subpages, and simply not list the subpages if the template itself is listed. Davilla 12:07, 18 June 2006 (UTC)

 * That's the reaction I've gotten as well, which is unfortunate because subroutined do make the code easier to read. A lot of your calls are only made once, so they would be very easy to roll in. What does isValidPageName do? I don't see any comments in the code. Davilla 12:07, 18 June 2006 (UTC)
 * I really like the suggestion that the MediaWiki software not list sub-templates.
 * I should have commented "isValidPageName". FYI, it determines whether its argument is a valid page name. It fills a gap missing from our lacking StringFunctions. The inflection templates use "isValidPageName" (or they would use "StringFunctions" if they were available) to determine whether an argument includes markup. They then wikilink valid page names and do not wikilink others. So, " " automatically links "having" and "had" but leaves the " " text unadorned. Rod (A. Smith) 17:41, 18 June 2006 (UTC)

 * I recommend filing a feature request aksing for different CSS classes around directly included template names and indirectly included template names. That way we can for example globally hide the indirect ones and people who want them all can have them all and other wikis which don't want anything changed won't see any changes. Somebody could even trivially come up with a JS extension that provides a button to hide/show the various levels. — Hippietrail 02:38, 20 June 2006 (UTC)

 * For this situation I think there's probably a more direct solution. The cattag mess will also be completely revamped when string functions are available to extract a tag from its parenthesis. Davilla 04:05, 20 June 2006 (UTC)

title: Wiktionary:Grease pit/Tricky templates


text:
cinéma

Etymology
.

Noun

 * 1) cinema (the art of making films and movies)
 * 2)  cinema (the film and movie industry)
 * 3) cinema (film or movies as a group)
 * 4) cinema (movie theatre)
 * 5)  playacting, drama, fuss
 * 1)  playacting, drama, fuss
 * 1)  playacting, drama, fuss

title: cinéma


text:
couler

Etymology
, from.

Verb

 * 1)  to sink
 * 2)  to cast (metal); to pour (liquid)
 * 3)  to sink
 * Le bateau de croisière MV Explorer a commencé à couler après avoir heurté un iceberg.
 * 1)  to flow, to run; to slip, to skid
 * 2)  to shed (i.e. shed blood)
 * 3)  to go bankrupt
 * 4)  to fail, flunk (a course, test, etc.)

Etymology
From, from.

Verb

 * 1) to flow

title: couler


text:
herbe

Etymology
,, from , ultimately from.

Noun

 * 1) grass (the plant)
 * 2)  weed; marijuana; ganja; cannabis

Etymology
From, from.

Noun

 * 1) A herbaceous plant:
 * 2) A plant as an ingredient.
 * 3) A plant as used in alchemy, magic or medicine.
 * 4) Herbage plants, especially grass
 * 5)  A woody plant; a tree.

title: herbe


text:
autant

Etymology
From *, earlier * (compare with ), corresponding to Classical. Compare with 🇨🇬, probably evolved from this form, along with Italian.

Adverb

 * 1) so much
 * 2) just as well, might as well/may as well
 * 3) the same, as much
 * 1) the same, as much
 * 1) the same, as much

title: autant


text:
User:Sangwal~enwiktionary

Sunil Sangwal, a wikipedia user! He may be contacted at s.sangwalATyahoo.com (please change AT with @).

title: User:Sangwal~enwiktionary


text: trouvait

title: trouvait


text: jouait

title: jouait


text: quittait

title: quittait


text: trichait

title: trichait


text: crachait

title: crachait


text: touchait

title: touchait


text: buvait

title: buvait


text: changeait

title: changeait


text: expliquait

title: expliquait


text: assistait

title: assistait


text: blessait

title: blessait


text: lavait

title: lavait


text: mangeait

title: mangeait


text: écoutait

title: écoutait


text:
º

Description
A small letter, to be placed at the top of the line, often underlined.

Symbol

 * 1º, 2º, 3º
 * 1º, 2º, 3º

title: º


text:
projet

Etymology
From. See.

Noun

 * 1) A plan proposed; a draft of a proposed measure; a project.

Etymology
From.

Verb

 * 1) to drive through, ride through
 * 2) to tour, drive around
 * 3)  to take a ride
 * 4)  to lose

Etymology
From proiectus.

Noun

 * 1) project
 * 2) plan
 * 3)  draft constitution

Etymology
From, from , perfect passive participle of.

Noun

 * 1)  project

title: projet


text: seraient

title: seraient


text:
patrie

Etymology
, from (whence 🇨🇬).

Noun

 * 1) homeland, home country, country of origin, fatherland

Etymology 1
From.

Adverb

 * 1) paternally

Etymology
.

Noun

 * 1) fatherland, motherland, homeland, birthplace, native country

title: patrie


text:
croit

Etymology
From.

Adjective

 * 1) raw

Noun

 * 1) croft

Etymology
Past participle of.

Noun

 * 1) planning

Etymology 1
Borrowed from.

Noun

 * 1) croft enclosed piece of land

Noun

 * 1)  hump on the back
 * 2)  hunchback
 * 3)  hillock

title: croit


text: murs

title: murs


text: rues

title: rues


text:
sentit

Etymology
From.

Noun

 * 1) sense as in sight, hearing etc.
 * 2) sense, meaning
 * 3) consciousness
 * 4) aftertaste
 * 1) consciousness
 * 2) aftertaste
 * 1) consciousness
 * 2) aftertaste
 * 1) aftertaste

Adjective

 * 1)  sensitive

title: sentit


text:
dipterocarp

Noun

 * 1) any member of the family  of tropical rainforest trees having two-winged fruits

title: dipterocarp


text:
noms

Verb

 * 1)  (nominate)

Etymology 2
Onomatopoeic

Verb

 * 1)  (eat with noisy enjoyment)

Noun

 * 1)  Food, especially tasty food.

Etymology
From, from Pre-Hlai (Norquest, 2015).

Noun

 * 1) water

Etymology
From. Cognates include 🇨🇬 and 🇨🇬.

Noun

 * 1) house

title: noms


text:
certaines

Adjective

 * Certaines filles veulent me toucher, mais c'est rare.
 * Certain girls want to touch me, but it is quite rare.
 * Certain girls want to touch me, but it is quite rare.

title: certaines


text:
reçu

Etymology
Borrowed from.

Adjective

 * 1) accomplished

Noun

 * 1) receipt

title: reçu


text:
Dipterocarpaceae

Hyponyms

 * , - subfamilies
 * ,, , , , , , , , , , , , , , - genera

title: Dipterocarpaceae


text:
colère

Etymology
Borrowed from.

Noun

 * 1)  anger, rage

Related terms

 * woede
 * woedeuitbarsting

Etymology
Old borrowing from, itself a borrowing from , from. .

Noun

 * 1) anger, rage
 * 2) wrath

title: colère


text: demandait

title: demandait


text:
Dionysiac

Adjective

 * Of, or relating to Dionysus or to the Dionysia.

title: Dionysiac


text:
Damon

Etymology
From, a name famous for the story of ; derivative of.

title: Damon


text: laissant

title: laissant


text:
dionysiac

Adjective

 * 1) wild and ecstatic

title: dionysiac


text:
disafforestation

Etymology
From post-classical Latin (13th cent.), from the participial stem of.

Noun

 * 1)  The change in the legal status of an area from forest to that of normal land, entailing the loss of forest laws.
 * 2)  Deforestation.
 * 1)  Deforestation.

title: disafforestation


text:
tomba

Etymology 1
, inherited from, from.

Noun

 * 1) tomb

Etymology
.

Noun

 * 1) patch, reparation (on a shoe, boot...)

Etymology
From, from.

Noun

 * 1) tomb, grave
 * 2)  a very narrow and gloomy habitation or room (such as a basement or cellar)
 * 3)  cave or vault
 * 1)  cave or vault

Noun

 * 1) tomb, grave

Etymology
From.

Verb

 * 1)  to fuck, to have sex with

title: tomba


text:
disclamatory

Adjective

 * 1) being in the nature of a disclamation

title: disclamatory


text:
disclamation

Noun

 * 1) The act of disclaiming or something disclaimed.
 * 2) A renunciation.

title: disclamation


text:
gagner

Etymology
, from, itself inherited from , ultimately from.

Verb

 * 1) to win
 * 2) to earn
 * 3) to gain; to obtain
 * 4) * 1902, M. Netter, "Efficacité de l'argent colloïdal (collargol) dans le traitement des maladies infectieuses; multiplicité de ses indications", in "Séance du 12 décembre 1902", Bulletins Et Mémoires de la Société Médicale Des Hôpitaux de Paris, third series, volume 19, Masson et Cie, page 1093:
 * "fr"
 * 1) to gain; to obtain
 * 2) * 1902, M. Netter, "Efficacité de l'argent colloïdal (collargol) dans le traitement des maladies infectieuses; multiplicité de ses indications", in "Séance du 12 décembre 1902", Bulletins Et Mémoires de la Société Médicale Des Hôpitaux de Paris, third series, volume 19, Masson et Cie, page 1093:
 * "fr"

- Le malade a gagné beaucoup de poids et est sorti le 31 décembre 1901.

title: gagner


text: disgenic

title: disgenic


text:
désir

Etymology
Derived from the verb, possibly corresponding to.

Noun

 * 1) desire

title: désir


text:
dysgenic

Etymology
, produced from from   and.

Adjective

 * 1)  of or relating to, or causing degeneration or deterioration in offspring
 * 2)  of or relating to dysgenics

title: dysgenic


text:
User talk:Scsbot

[You may leave comments pertaining to scsbot here, or on my talk page if you wish. —scs]

discussion archive

title: User talk:Scsbot


text:
vielen Dank

Etymology
lit. 'many thanks'.

Phrase

 * 1) thank you very much

title: vielen Dank


text:
User:Vildricianus/PageX/8

Empty page.

title: User:Vildricianus/PageX/8


text:
garðr

Etymology
From.

Cognate with 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬.

Noun

 * 1) a fence, wall
 * 2) * Grágás, in 1829, J. F. W. Schlegel, Hin forna lögbok islendinga sem nefnist Gragas, Volume II. Copenhagen, page 264:
 * "non"

- Ef þar er garðr of þioþbraut þvera,

 * 1)  an enclosed space, yard
 * 2) * Konungs skuggsjá 10, in 1848, R. Keyser, P. R. Munch, C. R. Unger, Speculum regale. Konungs-skuggsjá. Konge-speilet. Christiania, page 23:
 * "non"

- heldr eru þeir reistir umhverfis kirkjuna við kirkjugarðinn,

 * 1) a courtyard, court
 * 2) * Óláfs saga Tryggvasonar 1, in 1835, F. Magnússon, C. C. Rafn, Fornmanna sögur, Volume X. Copenhagen, page 218:
 * "non"

- er hann com heim í þorpit, oc geck um garðinn,

 * 1) a house, dwelling
 * 2) * Egils saga 62, in 1809, Guðmundur Magnússon, Egils-saga: sive Egilli Skallagrimii vita. Copenhagen, page 407:
 * "non"

- Egill spurdi hvar garðr sá veri í borginni er Arinbiörn átti

 * 1)  a stronghold, castle, hold
 * 2) * Vǫluspá, verse 4, lines 3-4, in 1860, T. Möbius, Edda Sæmundar hins fróða: mit einem Anhang zum Theil bisher ungedruckter Gedichte. Leipzig, page 1:
 * "non"

- þeir er miðgarð / mœran skópu;

title: garðr


text:
gerd

Etymology 1
. Per GDLC, possibly from. .

Noun

 * 1) raspberry

Etymology 2
, but possibly different in origin from Etymology 1.

Adjective

 * 1)  tender and fresh

title: gerd


text:
hjalmr

Etymology
From, whence also 🇨🇬 (whence 🇨🇬), 🇨🇬 (whence 🇨🇬), 🇨🇬 (whence 🇨🇬), 🇨🇬 (whence 🇨🇬), 🇨🇬.

Noun

 * 1) helmet

title: hjalmr


text:
User talk:Vildricianus/PageX/8

.portlet { display:none }
 * empty page for Monobook
 * 1) footer { display:none }
 * 2) siteNotice { display:none }

body { background:white }
 * 1) content { margin:0; border:none; background:transparent }

.portlet { display:none } .printfooter { display:none }
 * empty page for MySkin
 * 1) footer { display:none }
 * 2) siteNotice { display:none }
 * 3) jump-to-nav { display:none }
 * 1) siteSub { display:none }

title: User talk:Vildricianus/PageX/8


text:
swifan

Etymology
From, from. Cognate with 🇨🇬,, 🇨🇬, 🇨🇬.

Verb

 * 1) to move in a course, revolve
 * 2) to sweep
 * 3) to intervene

title: swifan


text:
swin

Etymology
From. Cognate with 🇨🇬, 🇨🇬.

Noun

 * 1) pig
 * 2) * unknown date, unknown author,, riddle 40
 * "ang"
 * 1) * unknown date, unknown author,, riddle 40
 * "ang"

- Māra iċ eom and fǣtra þonne āmæsted swīn.

 * 1) pork
 * 2) * 9th century,
 * "ang"

- Ne et nīewne ċīese, ne fersċe gōs, ne fersċne ǣl, ne fersċ swīn.

title: swin


text:
swinc

Etymology
.

Noun

 * 1) hard work: toil, labor
 * 2) hardship, travail

Synonyms

 * (much more common)

title: swinc


text:
swincan

Etymology
From, from ,. A parallel form to.

Verb

 * 1) to work hard: toil, labour
 * 2) * late 9th century, King Alfred's translation of Boethius'
 * "ang"

- Nū ðū þæt swā openlīce onġiten hæfst, ne þearfe ic nū nauht swīþe ymbe þ swincan þæt ic þē mā be gode recce.

 * 1) to strive
 * 2) * late 10th century, Ælfric, "Saint George, Martyr"
 * "ang"

- Nāst þū lā Geori þæt ūre godas swincað mid þē and ġit hī synd ġeþyldiġe þæt hī þe miltsion. Nū lǣre ic ðē swā swā lēofne sunu þæt ðū þæra cristenra lāre forlǣte mid ealle and tō mīnum rǣde hraðe ġebūge swā þæt ðū offriġe þām ārwurðan Appoline and þū mycelne wurðmynt miht swā beġitan.

title: swincan


text:
swingan

Etymology
From.

Verb

 * 1) to swinge, flog, beat, scourge
 * 2)  to chastise, afflict, plague
 * 3) to give a blow with the hand
 * 4) to whip a top, cream, etc.
 * 5) * "ang"

- Mid ġelǣredre handa hē swang ðone top.

 * 1) to strike, dash
 * 2) * "ang"

- Hē swang ðæt fýr on twá.

 * 1) (of wings) to beat, flap
 * 2) * "ang"

- Se fugel liċġeþ lonnum fæst swīþe swingeþ.

Etymology
From.

Verb

 * 1) to swing

title: swingan


text:
swogan

Etymology
From.

Verb

 * 1) to resound, sound, rush, roar
 * 2) to move with violence, enter with force, invade

Descendants

 * (past participle)
 * (past participle)
 * (past participle)
 * (past participle)

title: swogan


text: swilc

title: swilc


text:
svá

Etymology
From, from.

Adverb

 * 1)  so

Etymology
From, whence also 🇨🇬, 🇨🇬.

Adverb

 * 1) so

title: svá


text:
sierce

Etymology
From ; related to 🇨🇬.

Noun

 * 1) shirt, chemise

title: sierce


text:
tacan

Etymology
A late borrowing (c. 1100), from.

Verb

 * 1) to take
 * 2) to touch, make contact with

title: tacan


text: tacen

title: tacen


text:
teikn

Etymology
From, from. Doublet of.

Noun

 * 1) omen
 * 2) sign
 * 3) icon

Etymology
From or.

Noun

 * 1) a sign
 * 2) a character

title: teikn


text:
taumr

Etymology
From, whence also Old English , Old High German.

Noun

 * 1) bridle

title: taumr


text:
imputable

Adjective

 * 1) That may be imputed
 * 2)  Accusable; culpable; chargeable with fault.
 * 1)  Accusable; culpable; chargeable with fault.
 * 1)  Accusable; culpable; chargeable with fault.

Translations

 * Afrikaans: toegereken
 * Spanish:

 * Afrikaans: torekeningsvatbaar

Etymology
From.

Adjective

 * , attributable, ascribable, chargeable

Adjective

 * 1) attributable; imputable

title: imputable


text:
Talk:nice guy

Claims that the term can be used as an idiom meaning "an adult male who seeks sexual attraction and romantic intimacy, but only finds cordial friendship and platonic love." Is this the case? I doubt it. It should be deleted. Fark 14:28, 15 May 2006 (UTC)
 * I don't doubt that it's used very specifically in this way, but I'd first like to know, assuming it is, if it deserves an entry. Davilla 20:22, 15 May 2006 (UTC)
 * Response to own question: passes the rocky chair test, so yes. Davilla 16:20, 25 May 2006 (UTC)
 * Cited. 59.112.52.124 17:00, 28 May 2006 (UTC)
 * rfv-passed. Andrew massyn 18:36, 16 June 2006 (UTC)

title: Talk:nice guy


text:
tæcan

Etymology
From, from.

Verb

 * 1) to show, point out
 * 2) to show (someone) the way; to direct, guide
 * 3) to teach

title: tæcan


text:
tellan

Etymology
.

Noun

 * 1) tellane, tellurane, hydrogen telluride H2Te

Etymology
From, from , whence also 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬. Related to 🇨🇬.

Verb

 * 1) to count, calculate
 * 2) to tell, narrate, recount
 * 3) to regard, consider
 * 4) * c. 990, , John 15:15
 * "ang"
 * 1) to tell, narrate, recount
 * 2) to regard, consider
 * 3) * c. 990, , John 15:15
 * "ang"

- Ne telle iċ ēow tō þēowum. Iċ telle ēow tō frēondum.

 * 1) to attribute
 * 2) * late 10th century, Ælfric, "Saint Agnes, Virgin"
 * "ang"

- Þæt fyr wearð þa acwenced þæt þær an col ne gleow and þæt folc tealde þæt to drycræfte...

title: tellan


text:
togian

Etymology
From, see also 🇨🇬, 🇨🇬.

Verb

 * 1) to tow

title: togian


text:
imputability

Noun

 * 1) The character of being imputable.

Translations

 * Afrikaans: toerekeningsvatbaarheid
 * Tagalog: kapamintangan

title: imputability


text:
imputably

Adverb

 * 1) In an imputable manner; by imputation.

title: imputably


text:
imputableness

Noun

 * 1) The quality of being imputable; imputability.

title: imputableness


text:
tæsan

Etymology
From.

Verb

 * 1) to tease (fibres)
 * 2) to tear apart
 * 3) to rip apart or wound (with a weapon)

title: tæsan


text:
tamr

Etymology
From.

Adjective

 * 1) tame

title: tamr


text:
zam

Etymology
From, from. Cognate with 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬.

Adjective

 * 1) tame, gentle
 * 2)  mild

Etymology
From.

Noun

 * 1) weapon, arm

Etymology
From, from. The vowel may be influenced by cognate 🇨🇬. Luxembourgish zam(m) is the expected outcome of the uninflected stem, but one might expect *zuem, *zumm from the inflected forms instead. Also cognate with 🇨🇬, 🇨🇬.

Adjective

 * 1) tame

Etymology
From, see also Old English , Old Norse.

Adjective

 * 1) tame

Etymology
From, from.

Noun

 * 1) surcharge
 * 2) increase in price
 * 3) salary raise
 * 1) salary raise
 * 1) salary raise
 * 1) salary raise

title: zam


text:
tagl

Noun

 * 1) tail of a horse or cow

Etymology
From, from.

Noun

 * 1)  tail
 * 2)  ponytail
 * 3) rope
 * 4) a low jutting slope at the foot of a mountain, edge of a lava field, etc.

Etymology
From, whence also 🇨🇬.

Noun

 * 1)  tail

title: tagl


text: journeyed

title: journeyed


text:
teld

Etymology 1
From, , , from , from , from , from. Cognate with 🇨🇬,, 🇨🇬, 🇨🇬, 🇨🇬. .

Noun

 * 1)  A tent.

Etymology 2
From, from. See above.

Verb

 * 1)  To lodge in a tent.
 * 2)  To set up (a tent); pitch a tent;  to set up.

Verb

 * I teld you what happened.
 * I teld you what happened.

Etymology
From, from. Cognate with 🇨🇬.

Noun

 * 1) tent

title: teld


text:
impurely

Adverb

 * 1) In an impure manner.

Translations

 * Catalan:
 * Esperanto: malpure
 * French:
 * Italian:
 * Portuguese: impuramente
 * Spanish:

title: impurely


text:
impureness

Noun

 * 1) The quality or condition of being impure; impurity.

Translations

 * German:
 * Romanian:

title: impureness


text:
impuration

Noun

 * 1)  The act of making impure; defilement; obscuration.

title: impuration


text:
impulsiveness

Noun

 * 1) The quality of being impulsive.

title: impulsiveness


text:
Talk:sodomy

In the sense "an inhospitable person" - claimed to be a new sense due to reinterpretation of the Biblical story of Sodom and Gomorrah. Any evidence it is actually used in this way? I'd be loath to call someone inhospitable a sodomite... — Paul G 05:56, 19 October 2006 (UTC)

 * Similarly for sodomy. — Paul G 06:06, 19 October 2006 (UTC)

 * The exact definition for this new sense would be "an inhospitable man who attempts to get intimate with his male guest by force or coercion." For verification see Genesis. Dart evader 07:52, 19 October 2006 (UTC)

 * Dart Evader, I presume you're being tongue in cheek? (A quick look at the Bible (King James)/Genesis makes it seem that way.)
 * Depends which cheek.
 * There's definitely a discussion on various blogs (try googling "sodomite inhospitable") about what sodomite should mean...things along of the lines of "so and so called me a sodomist...but I see here that this Biblical translation focuses more on inhospitableness than buggering...so he just called me inhospitable; he's the one who started it, which is inhospitable, ergo he's really the sodomist here!!" I'm not sure that this kind of citation passes the WT:CFI use vs. mention distinction.

 * I added an rfv-sense for the "An immoral person." definition as well. A quick look did not show instances where it was not being used to mean (often as an insult, whether substantiated or not) one who engages in anal sex or homosexuality in general.  I also added a specific definition as "one who practices sodomy" as this probably be there somewhere :-)  --Jeffqyzt 14:52, 19 October 2006 (UTC)

 * Jeffqyzt, I was deadly grave. I daresay that what we are dealing with is nothing more than just another example of the Newspeak. The easiest way to stuff an old word with new meaning is to put that new sense on some authoritative dictionary. Then, if someone questions the legitimacy of the new usage, he or she would be referred to the dictionary definition. Voilà! --Dart evader 15:22, 19 October 2006 (UTC)
 * I agree with Dart evader. The discussion is merely a discussion without verification. I am removing the senses. it is purile sophistry. Unless we are directed to the "new interpretation" mentioned it goes. Besides, this word is supposed to be English. English never used it in the senses described. It may be so in Hebrew, but I doubt it. Andrew massyn 15:23, 18 November 2006 (UTC)

Disputed senses and discussion
 * 1) An immoral person.
 * 2) An inhospitable person [see Usage Notes below].

 * The usage of the term in the literal sense, inhabitant of Sodom, dates back as far as the Bible. The usage of the term to mean an immoral person dates back to at least the first century BCE.  The usage of the term by English-speaking peoples to mean a homosexual dates back to the 14th century CE.  Historically, many translators substituted the word in place of various Hebrew words (all with the basic meaning of immoral person) when translating the Bible into other languages.  However, the precise substitution varied in different languages, and thus the term can carry starkly different connotations in different languages.  For example, in Norwegian and German, a sodomite is a person who has sexual intercourse with animals; in contrast, many English-speaking people use the term as a synonym for homosexual.  A further dissertation of the word can be found  here.
 * Recent re-interpretations of the Biblical fable of Sodom and Gommorha echo the earliest understanding of them: that the cities were destroyed because of their inhabitants' inhospitality, not their homosexuality. This would explain why the word sodomite is beginning to be used to designate an inhospitable person.

 * The usage of the term Sodomy to mean immorality dates back to at least the first century BCE. Originally, the term was used by Jewish rabbis with the meaning of inhospitality.  The term did not acquire sexual connotations until after the first century CE, when it was substituted for the Hebrew word for temple prostitute in Christian translations of the Bible.  Historically, many translators substituted the word in place of various Hebrew words (all with the basic meaning of immoral person) when translating the Bible into other languages.  However, the precise substitution varied in different languages, and thus the term can carry starkly different connotations in different languages.  The usage of the term by English-speaking peoples to mean male homosexuality dates back to the 14th century CE.  In German, the term Sodomie refers to a person who has sexual intercourse with animals.  In Norwegian, the term sodomi carries both the original and the sexual connotations, and refers to inhospitality or to a male who has sexual intercourse with animals.  A further dissertation of the word can be found  here.}}

sodomy
RFV-sense "immorality in general". - -sche (discuss) 01:54, 10 March 2013 (UTC)
 * In Turkish, we use the word "puştluk". It means both "sodomy" and "immorality". --Furious (talk) 05:27, 10 March 2013 (UTC)
 * But the disputed definition is English.--Dmol (talk) 08:43, 10 March 2013 (UTC)
 * I think that sense reflects what many young children (to whom the other definitions have not been explained) are told or gather from the way the word is used. It reminds me of the explanation my father gave me for SNAFU: "situation normal all fouled up". I was perfectly happy with that explanation until early adulthood. DCDuring TALK 15:02, 10 March 2013 (UTC)

 * RFV failed: no quotations provided. As an auxi check, the sense is absent from MWO and AHD. --Dan Polansky (talk) 18:27, 21 August 2013 (UTC)

title: Talk:sodomy


text:
impulsor

Etymology
From.

Noun

 * 1) One who or that which impels; an inciter, an instigator.

Etymology
.

Adjective

 * 1) impulsive

Noun

 * 1) promoter

Noun

 * 1) inciter, instigator

Etymology
.

Adjective

 * 1) impulsive; impellent which impels, drives

Noun

 * 1) ; inciter; instigator

Etymology
.

Noun

 * 1) impeller

Etymology
From.

Adjective

 * 1) driving
 * 2) impulsive

Noun

 * 1) impeller

title: impulsor


text:
impulsively

Adverb

 * 1) In an impulsive manner; with force; by impulse.

Translations

 * Catalan:
 * Finnish: äkkipikaisesti, impulsiivisesti
 * French:
 * Galician: impulsivamente
 * Italian:
 * Polish:
 * Portuguese: impulsivamente
 * Spanish: impulsivamente

title: impulsively


text:
impulsion

Etymology
From, from , from.

Noun

 * 1) The act of impelling or driving onward, or the state of being impelled; the sudden or momentary agency of a body in motion on another body; also, the impelling force, or impulse.
 * 2) Influence acting unexpectedly or temporarily on the mind; sudden motive or influence; impulse.
 * 1) Influence acting unexpectedly or temporarily on the mind; sudden motive or influence; impulse.

Etymology
.

Noun

 * 1) impulse
 * , drive, impetus
 * 1)  electric pulse, momentum

title: impulsion


text:
inaction

Etymology
From.

Morphologically.

Noun

 * 1) Lack of action or activity or labor

Translations

 * Armenian: անգործություն
 * Belarusian: бяздзе́йнасць, нячы́ннасць, бясчы́ннасць
 * Bulgarian:
 * Catalan:
 * Czech: nečinnost
 * Esperanto: senagado
 * Finnish:
 * French:
 * German:, , ,
 * Greek: ,
 * Ancient: ἀπραξία
 * Hungarian:
 * Italian:
 * Polish:
 * Portuguese:
 * Romanian:
 * Russian:
 * Slovak: nečinnosť
 * Slovene: nedejavnost, nedelavnost
 * Spanish:
 * Swedish:
 * Ukrainian: ,

Noun

 * 1) inactivity

title: inaction


text:
inertness

Noun

 * 1) Lack of activity or exertion; habitual indisposition to action or motion
 * 2) Absence of the power of self-motion; inertia.
 * 3)  Quality of being unreactive with other chemical compounds or elements.
 * 1)  Quality of being unreactive with other chemical compounds or elements.

Translations

 * French:
 * German:
 * Italian: ,
 * Latin:
 * Polish:
 * Spanish:

 * Italian:
 * Polish:
 * Spanish:

 * Italian:
 * Polish:, , ,
 * Spanish: inercia química

title: inertness