text:
User talk:GianWiki

Umbrian
Hi. About this: the Italic script for Umbrian should be  entered in Unicode characters, not as images. --Vahag (talk) 14:06, 10 November 2013 (UTC)
 * Hello, Vahagn. Yes, I probably should have used Unicode characters. I just thought rendering the stylistic variants of Old Italic script (Umbrian, in this case) could be a good thing to do. Thanks for the advice.

GianWiki (talk) 14:19, 10 November 2013 (UTC)
 * The image can be shown in the page for, when it is created. --Vahag (talk) 15:15, 10 November 2013 (UTC)

五蘊/五蕴
See my changes: 五蘊 and 五蕴. Thanks. Good job by the way. Jamesjiao → T ◊ C 21:42, 10 November 2013 (UTC)

Adding dashes to separate out language sections
Make sure you add four dashes to separate out the language sections. See here: Added dashes Jamesjiao → T ◊ C 02:47, 12 November 2013 (UTC)

IPA

 * 1) Chinese languages are tonal. These IPA-notated pronunciations are therefore basically inaccurate.
 * 2) 蘊 in Beijing Mandarin is /yn51/, not /jʊn51/.
 * 3) 春 in Guangzhou Cantonese is /tsʰɵn55/3/.

Wyang (talk) 02:58, 12 November 2013 (UTC)

Avestan, Middle Persian, etc.
Hi. Thanks for adding those scripts. Do you look up the exact spellings in dictionaries or do you "detransliterate" yourself from a given romanization? --Vahag (talk) 19:52, 13 November 2013 (UTC)
 * I "detransliterate" after looking up the script's characteristics (e.g. vowel omission) and checking if the given spelling is plausible according to the script transliteration.
 * Please don't do that. We need the exact spellings as attested in extant manuscripts, which are capable of passing WT:CFI, not hypothetical detransliterations. Also, I have to revert most of your recent edits to Armenian and Persian entries, because they are wrong, e.g. is not derived from Middle Persian *vitang. --Vahag (talk) 20:02, 13 November 2013 (UTC)
 * My apologies. Reading that is related to, I think I inadvertently assumed the two to be cognates (a silly mistake, I have to say). With this assumption, I went further and assumed the Etymology entry for  could be applied for  as well (I mainly thought so because, sometimes, etymological information is included in an entry yet missing in a 'cognate' entry, as far as I've seen. I just thought this was one of those cases). Again, I apologize: I will try to not to rush things the next time.
 * GianWiki (talk) 20:34, 13 November 2013 (UTC)
 * Don't worry, I made many similar mistakes when I started editing Wiktionary. --Vahag (talk) 20:56, 13 November 2013 (UTC)

A Welcome, and a Note
Please pay special attention to our Criteria For Inclusion. We go by usage, not whether it can be found in a dictionary. Some of your recent Latin entries for modern technology seem unlikely to exist in actual use, though Latin is still used by the Vatican, so I could be wrong. Chuck Entz (talk) 00:21, 17 November 2013 (UTC)
 * I myself do not know how widespread their usage may be, but I believe that the very existence of these terms, and to the fact that someone took the time to plan and construct them in order to somewhat revitalize the language by expanding its lexicon (see the |Lexicon Recentis Latinitatis found at the | Holy See website or the 2007 |Auxiliary Spanish-Latin Dictionary for a Modern Usage of Latin) is reason enough for their inclusion.on Wiktionary. I might be wrong, but I believe this should be taken into consideration.

GianWiki (talk) 01:37, 17 November 2013 (UTC)
 * I forgot to mention that some of your entries have been challenged at WT:RFV. There's some debate as to whether modern Latin is covered by the partial exemption in the CFI for languages with little documentation. Classical Latin is, but modern usage is a separate issue. Chuck Entz (talk) 16:35, 17 November 2013 (UTC)

Chinese, Korean and Vietnamese
The pages you created (戰國, 战国) were full of errors. Please stop adding languages you are not familiar with. Wyang (talk) 00:50, 16 December 2013 (UTC)

Latin proper noun forms
Could you please add to these entries under the ===Proper noun=== header? It provides a bold headword and categorizes. Thank you. Mglovesfun (talk) 17:07, 16 December 2013 (UTC)

Reversion of your 大麻 edit
Hi,

Please read Votes/pl-2014-04/Unified Chinese and related discussions, which affect the new policy for entries in Chinese topolects. --Anatoli (обсудить/вклад) 13:09, 5 May 2014 (UTC)

Ancient v Modern Greek
Thanks for trying to help - but the pronunciation sections which you added belong in an Ancient Greek entry. — Saltmarsh απάντηση 17:46, 15 June 2014 (UTC)

aeque atque
(might as well post it here) I don't see how this is not sum-of-parts. --Fsojic (talk) 14:01, 4 January 2015 (UTC)
 * Could you be more specific as to what you mean by that? GianWiki (talk) 14:22, 4 January 2015 (UTC)
 * It's just that I don't see how there is a need for this entry when we already have and . There isn't some special meaning to this locution that couldn't be deduced from the two words that compound it. At least that's what I think. --Fsojic (talk) 14:32, 4 January 2015 (UTC)
 * I took the liberty of creating the page after seeing it was one of the | Requested entries for Latin. GianWiki (talk) 14:43, 4 January 2015 (UTC)

Grazie!
Grazie per le tue contribuzioni! Nonostante sia irreligioso, in realtà preferisco la fonologia ecclesiastica perch’è più italiana. ☺ --Romanophile (talk) 14:11, 4 January 2015 (UTC)

indigent
Most Romance nouns and adjectives derive from the Latin accusative form, so saying it derived from is technically correct. Showing that form also makes it much more obvious how the modern form came to be (the nominative has no final -t in it after all). So maybe something like ? That way it shows the actual form it derived from, but still links to the right lemma. —CodeCat 14:32, 17 January 2015 (UTC)
 * I'm not quite sure to what extent lemma forms are to be preferred in such cases, but your proposal seems reasonable - GianWiki (talk) 14:55, 17 January 2015 (UTC)
 * I don't know either. I've seen entries linked in the way it was originally, in the way I suggested above, and also just with the lemma alone. It also seems to differ for different words; first and second declension words are always linked directly from what I've seen, but third declension ones sometimes not. For verbs most entries link to the first principal part, some to the infinitive, and some link to the first part but show the infinitive (like I did above). So I don't really know what the preferred practice is. —CodeCat 15:49, 17 January 2015 (UTC)
 * For verbs, I remember reading somewhere that the present first-person singular form is preferred; I don't recall ever finding such clues about nouns, though. - GianWiki (talk) 15:54, 17 January 2015 (UTC)

etrusco
Extra heading levels are only used when there are multiple etymology sections. — Ungoliant (falai) 16:47, 17 January 2015 (UTC)
 * I see. Thank you very much for the information. GianWiki (talk) 16:50, 17 January 2015 (UTC)

aurum
Right now, both pronunciations are listed as Classical ( produces a Classical pronunciation, and the other pronunciation is tagged ). Was one of them supposed to be Ecclesiastical? - -sche (discuss) 03:48, 21 February 2015 (UTC)
 * Yes, you are right: I forgot to rename the template. Thanks for letting me know. GianWiki (talk) 19:53, 22 February 2015 (UTC)

Thank you for your additions
... but please be careful!  —Μετάknowledge discuss/deeds 22:05, 22 February 2015 (UTC)
 * You're right. I will be more careful. GianWiki (talk) 23:21, 22 February 2015 (UTC)

Latin Ecclesiastical pronunciation
Hi GianWiki. I see you add a lot of Latin Ecclesiastical pronunciatory transcriptions. Do you think it's possible to automate the generation of Ecclesiastical pronunciatory transcriptions similarly to the way Classical pronunciatory transcriptions are currently generated for Latin terms by ? — I.S.M.E.T.A. 22:23, 17 March 2015 (UTC)

 * I've been thinking about this myself, and my guess is that a template - similar to the already existing or  for Classical pronunciation - might be the solution. I've also thought about doing it myself, but I'm afraid I don't know the first thing about writing a template from scratch; otherwise, I probably would have already done it. If you happen to have any advice in regard to this, please feel free to share it. GianWiki (talk) 12:41, 18 March 2015 (UTC)

 * I was thinking more or less the same thing. (BTW, there is no difference between and ; the actual template is, whilst  just redirects to .) Ideally, what we would do is edit  and Module:la-pronunc in such a way that  would end up generating both the current Classical transcriptions and the desired Ecclesiastical transcriptions (perhaps with presentation like , but without the collapsibility feature); that should be possible as long as the input text used to generate Classical transcriptions (e.g.,  ) is sufficient for generating Ecclesiastical transcriptions, too. AFAICT, the editors that have developed this template and module are CodeCat, Keφr, and kc_kennylau. I don't have the Lua-coding ability to make the necessary changes myself, but as long as we get the help of one or more of those editors (That would be greatly appreciated, CodeCat, Keφr, and/or kc_kennylau.) and you can provide the principles of Ecclesiastical pronunciation, I'd be more than willing to do what I can to develop Latin Ecclesiastical pronunciatory autotranscription. — I.S.M.E.T.A. 20:33, 20 March 2015 (UTC)

 * I can help. Basically what's the rule for stressed syllables in Ecclesiastical Latin? Is it the same as Classical Latin? --kc_kennylau (talk) 00:14, 21 March 2015 (UTC)

 * There are only a few differences from the existing Classical Latin pronunciation template(s):
 * give when preceding, and  elsewhere ( phonetically geminated when intervocalic:  → ).
 *  gives when preceding a vowel, and  elsewhere.
 *  gives ; give regardless of position.
 *  gives (phonetically geminated when intervocalic:  → );  gives.
 * give (maybe  can be arranged to phonetically give an  in order to avoid ambiguity).
 * Stress accent is exactly the same as in Classical Latin. No phonemically long vowels (but vowels in open, stressed syllables are phonetically long ( → ). GianWiki (talk) 01:13, 21 March 2015 (UTC)

 * Please refer to caelum, the first test of the new feature. --kc_kennylau (talk) 01:00, 21 March 2015 (UTC)

 * Thanks for your help. According to the description, should give.

 * Done. --kc_kennylau (talk) 09:23, 21 March 2015 (UTC)

 * Vowels in open, stressed syllables are only lengthened in phonetic pronunciation, not in the phonemic one . GianWiki (talk) 09:41, 21 March 2015 (UTC)
 * Also, I forgot to add that  should give . GianWiki (talk) 09:45, 21 March 2015 (UTC)

 * Thanks for working on this, guys. Is there anything you need me to do to help with this? @GianWiki: Re " give when preceding ", I assume that this "softening" also occurs when those consonants precede ⟨y⟩, yes?  — I.S.M.E.T.A. 10:15, 21 March 2015 (UTC)
 * You are right, thanks. I forgot to mention it earlier. GianWiki (talk) 11:13, 21 March 2015 (UTC)
 * Would you please provide me words to test? I'll send you the test results and you can help me to point out where's wrong. --kc_kennylau (talk) 13:26, 21 March 2015 (UTC)
 * Sure. Here's a few:, , , , , , , , . They should cover all the aforementioned points. --- GianWiki (talk) 14:23, 21 March 2015 (UTC)
 * Template:la-IPA/documentation. --kc_kennylau (talk) 16:35, 22 March 2015 (UTC)
 * Thanks for your work.
 * Long vowels are not phonemes in Ecclesiastical Latin, so no lengthening is needed in the phonemic trascription (e.g. ). If - simlarly to the Classical pronunciation - a phonetic pronunciation is also going to be shown (e.g. ), that's where it belongs.
 * Labialized velars are to be rendered in Ecclesiastical as simple velar-labiovelar sequences . For example: →  ;.
 * Also, for some reason, Ecclesiastical rendering of got the stress accent wrong.
 * I again thank you very much for your effort, and apologize for my pedantry. --- GianWiki (talk) 17:13, 22 March 2015 (UTC)
 * Accordingly modified. What about the "o" vowel? What is its value in short vowel and in long vowel? --kc_kennylau (talk) 13:53, 23 March 2015 (UTC)
 * You're doing a really great work. There's only one last thing about vowel rendition: phonemic should give phonetic, maintaning the same values when lengthened . About the : I usually render it as , unless the vowel of the preceding syllable is closed (i.e. ), in which case I render it as . I have no idea how difficult it could be to do something like that, but  can do just as good. -- GianWiki (talk) 15:44, 23 March 2015 (UTC)
 * Done. scio returns /ˈʃi.o/, [ˈʃiː.o]. --kc_kennylau (talk) 16:17, 23 March 2015 (UTC)
 * Perfect. On the other hand, I tested the template on the word, and I can't help noticing that ⟨sc⟩ is rendered as (, while it should be ), which should only happen when it is followed by ⟨e i y ae oe⟩. -- GianWiki (talk) 17:02, 23 March 2015 (UTC)
 * Careless mistake. Fixed. Would you like to provide more words for testing? --kc_kennylau (talk) 15:53, 24 March 2015 (UTC)
 * Sure., , , , , , , , . About , I believe it could be rendered as , and I think (long: ) is a better default rendition of  than . Also, I've noticed the presence of nasalized vowels (e.g.  → ;  → ): those only belong in Classical pronunciation (the words can simply give vowel-nasal sequences  and ; the "velarized l"  can also give way to a simple ). Thanks for your noticeable patience, by the way. -- GianWiki (talk) 16:54, 24 March 2015 (UTC)
 * Template:la-IPA/documentation. --kc_kennylau (talk) 13:11, 25 March 2015 (UTC)
 * Increasingly satisfactory. Also, I think I've figured out a way around the issue: phonemically, there should only be  (I'm only specifying because I think I might've worded my previous suggestions badly, since  and  now seem phonemically distinctive), while the phonetic rendering can be based on the orthography: ⟨o⟩ can give  (thence  when accented in open syllable), while ⟨ō⟩ can give  ( when accented etc.). For example:  → ;  → . Everything else is great. -- GianWiki (talk) 20:05, 25 March 2015 (UTC)

Changed accordingly. Please give your opinion on Template_talk:la-IPA. --kc_kennylau (talk) 15:23, 26 March 2015 (UTC)

PIE *kel-
May I ask what source you used for this? All sources I can find include a final laryngeal. —CodeCat 00:14, 1 May 2015 (UTC)
 * It was merely a careless mistake on my part; I'm going to have to be a bit more careful. Also, thanks for the editing. -- GianWiki (talk) 00:30, 1 May 2015 (UTC)

gelo
Come si dice gelo nell’italiano antico? --Romanophile (talk) 14:51, 10 May 2015 (UTC)
 * Cercando - su tuo suggerimento - ho trovato la forma (e mi sono permesso di aggiungerla a Wiktionary). --- GianWiki (talk) 15:14, 10 May 2015 (UTC)

lindo si usa nell’italiano antico? --Romanophile (talk) 15:53, 16 May 2015 (UTC)
 * Ho trovato un'attestazione del suo uso, quindi immagino si possa dire di sì. --- GianWiki (talk) 17:42, 18 May 2015 (UTC)

 * Che significava? Era eguale alla parola italiana? --Romanophile (talk) 17:54, 18 May 2015 (UTC)
 * Fondamentalmente, sì: l'ho letto - in riferimento ad indumenti - nella tipica accezione di “pulito, ordinato”. --- GianWiki (talk) 21:34, 18 May 2015 (UTC)

About Italian
Could you add a cutoff date for Italian/Old Italian please? Cheers. Renard Migrant (talk) 21:19, 10 May 2015 (UTC)

hyphens in IPA
Hi! The hyphens in and  aren't pronounced. They are silent. So there is no need to put them into the IPA template. Additionally, edits like this one add the page to these two hidden categories: Category:IPA pronunciations with invalid representation marks and Category:IPA pronunciations with invalid IPA characters. --MaEr (talk) 17:31, 20 July 2015 (UTC)

Interwikis
Hey Gian. Thanks for your work on the obsolete Italian. Please try to be careful to keep interwiki links at the bottom of the page (as I did in this edit). For more information on how to format things, please see WT:EL or feel free to ask me. Grazie! —Μετάknowledge discuss/deeds 02:33, 20 December 2015 (UTC)
 * Thanks for noticing: you are right. I'll be more careful. — GianWiki (talk) 10:45, 20 December 2015 (UTC)
 * No worries. Thanks! —Μετάknowledge discuss/deeds 17:48, 20 December 2015 (UTC)

Reconstruction:Proto-Indo-European/wóyh₁nom
This entry as it currently stands could unfortunately mislead by implication, since this is a classic early Mediterranean word (also occurring in early Semitic etc.) which was almost certainly borrowed into Indo-European branches from non-Indo-European languages (not the reverse). Neither the word nor the physical object is at all likely to have existed on the Pontic-Caspian steppe ca. 3000 B.C. The laryngeal may be purely theoretical (and historically spurious), since the word may not yet have existed in various Indo-European branches at a time when laryngeals still existed... AnonMoos (talk) 08:21, 18 July 2016 (UTC)

 * Currently being discussed on Etymology scriptorium if you have any thoughts... AnonMoos (talk) 13:36, 17 September 2016 (UTC)

Declined forms of decibilis
I had to clean up all the non-lemmata you created. If you're going to create entries for the declined forms of and, please don't make the same mistake again. — I.S.M.E.T.A. 19:14, 4 November 2016 (UTC)

 * Thanks for the heads-up, I didn't notice I forgot to add the headers. - GianWiki (talk) 19:29, 4 November 2016 (UTC)

 * No worries; mistakes happen. Note, too, that the first parameter of is obligatory; if it isn't specified, the page gets added to Category:Latin adjective forms needing attention (which is how I noticed your mistakes), even if the form has no macra. As a more minor point, in future, please list declined forms by case, then number, then gender (rather than number, gender, case, as you have been doing) for consistency with bot-generated entries for Latin non-lemmata. — I.S.M.E.T.A. 19:37, 4 November 2016 (UTC)

Regarding inheritance and borrowings in Italian
Hi GianWiki, and thanks for all the great contributions you've made. Just had a quick comment to make on some edits, however. Being a native speaker, you of course know the Italian language itself much better than myself and other users, but regarding the etymology of some words, I have to note that it is erroneous to call many of the ones you have "inherited". I understand that it is tempting to view modern Italian as being almost entirely inherited from Latin, but as with all the other Romance languages, a considerable part of it was actually borrowed in a learned fashion by scholars and such in the Middle Ages and Renaissance. The core part of the language and basic vocabulary (a few thousand words) is largely inherited but many of the ones you've added were almost surely not, from a linguistic point of view. It may be surprising to find that there are probably more borrowed terms than inherited in all the Romance languages. Now that Wiktionary is making distinctions between the two, it's important to note this. For example, most of the mythological figures deriving from Classic Greco-Roman antiquity can't have been inherited, because that implies they were part of the day to day speech of the common people, and surely they were not for most of the Middle Ages (that was the realm of scholars, elites, and learned people, and they usually took it directly from Classical Latin or Greek texts). In linguistics, inherited means they were passed down primarily orally, originally from the largely undocumented Vulgar Latin, and not through literary texts (and thus would have changed much more over time). Also, just because a word seems fairly common now in modern Italian doesn't necessarily mean that it wasn't borrowed at some point in the past. Certain common words, like those ending in '-zione', were taken from Latin or were later constructions. However these borrowings happened pretty deep in the past, so by now they've become normal, commonplace, and well-ingrained in the language, so they don't always seem noticeable. Others were purposely adapted to existing Italian phonological characteristics to make them "fit into" the language better, like Latin 'ct' > Italian 'tt' or Latin 'ae' > Italian 'e'.

Unfortunately, I haven't been able to find an Italian etymological dictionary that distinguishes between inherited and later borrowed or learned terms like I have for French and Spanish, but we can infer with fairly good probability based on what we know of linguistic rules, phonetic shifts, and changes in meaning. A lot of the borrowed terms were also borrowed in other Romance languages, or have doublets that were inherited. With Italian, it can be trickier since it is naturally closer to Latin than the other languages. But I avoid using the 'inh' tag on certain words that are overly intact and similar to the original Latin, especially if it is a rare or literary word or one that normally should have looked different and undergone more changes into Italian, based on what we know of sound shifts. If uncertain whether it is inherited or borrowed, I usually just slap the more general (and ambiguous) 'der' tag on there for now until someone else decides how to deal with it. I just wanted to bring this up since when periodically looking at the lists of inherited terms in Italian, I find I have to remove certain ones that are clearly not. But other than that, keep up the good work! Word dewd544 (talk) 18:39, 7 November 2016 (UTC)

niuno
The IPA has 3 syllables but the hyphenation has 2. Not sure which is correct. Ultimateria (talk) 20:38, 18 December 2016 (UTC)

Share your experience and feedback as a Wikimedian in this global survey
Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. To say thank you for your time, we are giving away 20 Wikimedia T-shirts to randomly selected people who take the survey. The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this project. This survey is hosted by a third-party service and governed by this privacy statement. Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email to surveys@wikimedia.org.

Thank you! --EGalvez (WMF) (talk) 22:25, 13 January 2017 (UTC)

instead. —Rua (mew) 21:03, 17 September 2017 (UTC)

template:etyl
Hello. Could I ask you to stop using ? It's being phased out in favour of (or / when appropriate), and adding it in new places is interfering with the cleanup job. Thank you! --Barytonesis (talk) 21:21, 13 October 2017 (UTC)
 * I was not aware of that: I'm sorry. -- GianWiki (talk) 21:25, 13 October 2017 (UTC)
 * No worries! --Barytonesis (talk) 07:54, 14 October 2017 (UTC)

zêro
I added templates to the numbers after zêro, notably doî. --Lo Ximiendo (talk) 17:05, 8 November 2017 (UTC)
 * Thank you for your help! -- GianWiki (talk) 17:10, 8 November 2017 (UTC)

Ligurian
Hi Gian. I just wanted to say thanks for all the Ligurian content you’re adding. — Ungoliant (falai) 10:48, 16 November 2017 (UTC)

 * I wonder, what made you change a link from *oegia to oêgia? (An official orthography, perhaps?) --Lo Ximiendo (talk) 17:31, 22 November 2017 (UTC)
 * Yes, I'm using the official orthography promoted by the Académia Ligùstica do Brénno (whose specifics, albeit explained in Genoese, can be found here) -- GianWiki (talk) 17:41, 22 November 2017 (UTC)
 * Thank you; therefore, that orthography may have to be mentioned at the policy Wiktionary:About Ligurian. --Lo Ximiendo (talk) 21:59, 22 November 2017 (UTC)
 * Also, could you check the spelling of the term öo? --Lo Ximiendo (talk) 00:08, 15 December 2017 (UTC)
 * AFAIK, öo is spelled correctly. -- GianWiki (talk) 11:00, 15 December 2017 (UTC)

Ligurian Swadesh list
Hello. I see you're working strenuously on our Ligurian coverage, so I want to let you know that we have a Ligurian Swadesh list at Appendix:Swadesh lists for Italian languages; there's still a fair amount of red links in there. No obligation of course, but it would be nice if you could take care of them! --Per utramque cavernam (talk) 18:12, 11 December 2017 (UTC)

nux
I added the Ligurian term nôxe to the list of descendants in the entry nux. --Lo Ximiendo (talk) 12:25, 23 December 2017 (UTC)
 * Thank you for the addition! -- GianWiki (talk) 14:44, 23 December 2017 (UTC)
 * Off topic, but which spelling ought to be proper, tomata or tomâta? --Lo Ximiendo (talk) 12:27, 23 December 2017 (UTC)
 * I believe the proper one is tomâta, since the vowel is long -- GianWiki (talk) 14:44, 23 December 2017 (UTC)

ezercìçio
If the entry ezercìçio is spelled properly, then what is its plural form? --Lo Ximiendo (talk) 01:57, 28 December 2017 (UTC)
 * I believe it should be spelled esercìçio, with esercìççi as the plural. -- GianWiki (talk) 18:44, 28 December 2017 (UTC)
 * Thanks for replying. --Lo Ximiendo (talk) 12:17, 29 December 2017 (UTC)

muda
This now has two Italian sections.

Could you look at please - can the two verb sections be combined? SemperBlotto (talk) 11:40, 10 January 2018 (UTC)
 * I hadn't noticed the bottom section. Thanks for pointing it out for me. As for, I've tried combining the sections and adding a "Usage notes" section to explain the use of the auxiliary. -- GianWiki (talk) 11:54, 10 January 2018 (UTC)

Ligurian in the Portuguese Wiktionary
I updated a lot of the entries on Ligurian month names at the Portuguese Wiktionary. Their coverage of Ligurian looks like it needs a face-lift. --Lo Ximiendo (talk) 18:37, 26 January 2018 (UTC)
 * Here's what I mean. --Lo Ximiendo (talk) 16:01, 31 January 2018 (UTC)

Ligurian for Universe
How would the Ligurian word for "universe" be spelled? --Lo Ximiendo (talk) 11:35, 12 February 2018 (UTC)

I mean, is "universo" spelled properly, or does it need a facelift? --Lo Ximiendo (talk) 12:02, 12 February 2018 (UTC)
 * If the accent were to be made explicit, it should be spelled univèrso. -- GianWiki (talk) 13:16, 12 February 2018 (UTC)
 * So should I fix the listed link to the translation? --Lo Ximiendo (talk) 13:36, 12 February 2018 (UTC)
 * I don’t think there’s any need to do that until the Ligurian editing community decides on lemmatisation criteria. — Ungoliant (falai) 18:32, 17 March 2019 (UTC)

Italian rhymes
Hi there. Have you considered creating "Rhymes:Italian/..." entries for use by all the -are, -ere and -ire verbs? I realise that there would be very many instances, especially of -are. SemperBlotto (talk) 08:51, 31 July 2018 (UTC)

Italian SOPs
Hi. I'm concerned by what these IP, who I think are the same person as , are doing. Several entries sound SOP to my French ears, and it was already a recurrent problem with that user a few years ago. Could I ask you to have a look at threir contributions, and tell me what you think? Also. Per utramque cavernam 16:43, 4 August 2018 (UTC)

Ligurian orthography
Hi! Well done on adding so many Ligurian terms. Is the consensus to use the contesto didatico rules of the Académia Ligùstica do Brénno? Perhaps with see also links from the unaccented headwords? How about longer pieces of text, such as image captions? Before I start contributing Ligurian terms myself, I would like to write this all down in Wiktionary:About Ligurian to avoid having a confusing mix of orthographies.

Also, I've just added a template for  users which you may be interested in.

Scignoria! -- Jean (t·c) 16:18, 17 March 2019 (UTC)
 * may be interested in this discussion. —Μετάknowledge discuss/deeds 17:10, 17 March 2019 (UTC)

 * You seem to be the ones most interested in the subject of Ligurian. I would like to propose the Grafîa ofiçiâ (in the ‘didactic context’, where all the accents are specified) be adopted as the standard for Ligurian orthography. What do you think? – GianWiki (talk) 18:10, 21 January 2020 (UTC)
 * The orthography looks interesting. --Lo Ximiendo (talk) 13:40, 28 January 2020 (UTC)

 * Hi! Thanks for bringing up the subject. The question of Ligurian orthography is, sadly, a touchy one. The one standard you link to is promoted by an admittedly fairly exhaustive website, but it is far from having been adopted by the community of native speakers. The website is essentially a one-man show by a retired physicist. He's a very nice and knowledgeable gentleman, but this orthography was thought up fairly recently without consulting language experts or writers. It is not in wide use other than by a small circle of people who happen to be fairly visible online, and has very limited use in print outside of some self-published materials. The other possible route is to use traditional orthography. The big advantage is that it would give people access to the same language used for the very long Ligurian literary tradition – and I assume many users of a dictionary would be mainly interested in this. It's also the same orthography used by the largest print newspaper of Liguria (Il Secolo XIX, which publishes weekly in Ligurian), as well as the only – as far as I know – print newspaper that's entirely in Ligurian (O Stafî). I am happy to provide further references if you're interested – I do my best to stay up-to-date on these topics. Worst case scenario, I suppose both orthographies could be used. Jean (t·c) 17:19, 28 January 2020 (UTC)
 * My two cents is that we should have entries in any orthography that is or has been in use. The question is whether we should pick one to be the orthography of Ligurian lemmas, with the others relegated to being listed as alternative spellings. I don’t really know enough about the orthographic situation of Ligurian to make this decision; nearly all Ligurian entries I added came straight from A Compagna magazine, which has articles in standard Italian, ALB’s orthography and what seemed to be ALB’s orthography without certain diacritics. — Ungoliant (falai) 01:59, 8 February 2020 (UTC)
 * On the Ligurian Wikipedia, it says that the orthography employed by the newspaper Il Secolo XIX (the grafia unitäia) is not the same as the so-called "traditional orthography". That said, I personally wouldn't be against employing the grafia unitäia as the standard for Ligurian entries (even though I'm not sure whether or not long vowels should be marked at all times, or just – as said in the Ligurian Wikipedia – when it helps avoid ambiguity). As for the other orthographies, they could very well be listed as alternative spellings. — GianWiki (talk) 11:50, 29 March 2020 (UTC)

 * Hi! I was wondering if anyone had given any thought to the idea of employing the grafia unitäia for Ligurian lemmas. Has there been any development on the subject? — GianWiki (talk) 16:43, 7 October 2020 (UTC)
 * Do you mean as the sole lemma orthography, or for the creation of entries in general (whether lemmas or alt-spellings)? — Ungoliant (falai) 19:20, 9 October 2020 (UTC)
 * : I mean for the lemma orthography. Since the grafia unitäia is also used on the Ligurian newspaper Il Secolo XIX, it has a sufficient degree of recognizability (and, dare I say, authority). Also, it would be pretty good for avoiding ambiguity in spelling, unlike - for example - the traditional orthography (I'm mainly thinking about the lack of distinction between and, both indicated as ⟨û⟩). — GianWiki (talk) 20:07, 9 October 2020 (UTC)
 * Of course, other orthographies – like the grafîa ofiçiâ, or the "u-orthography" – could be listed as alternative spellings. – GianWiki (talk) 20:48, 9 October 2020 (UTC)
 * Apologies for the delay in getting back to you. That sounds reasonable to me, especially seeing how that's the orthography used by the press and the academic community. I'd be happy to set up Wiktionary:About Ligurian and provide IPA transcriptions and perhaps even some recordings. Jean (t·c) 18:41, 11 November 2020 (UTC)
 * Sorry I took so long to answer. I somehow lost track of your message. Yours would be a very welcome contribution. Once the ground rules are laid down, we could start adding new lemmas and/or properly categorize the existing ones. Perhaps there should be a couple of ad-hoc templates for the forms using alternative spellings (the grafîa ofiçiâ, or the "u-orthography", I'm not sure which ones will end up being included). — GianWiki (talk) 21:54, 15 March 2021 (UTC)

Small formatting fix
Hi, I fixed up an edit you made:. You shouldn't include multiple terms in the same parameter like that. If there are multiple terms, there should be an equal number of parameters or templates. —Rua (mew) 18:30, 25 March 2019 (UTC)
 * Thank you very much for the information, I will make sure to do that from now on. – GianWiki (talk) 19:50, 25 March 2019 (UTC)

Community Insights Survey
Share your experience in this survey

Hi ,

The Wikimedia Foundation is asking for your feedback in a survey about your experience with and Wikimedia. The purpose of this survey is to learn how well the Foundation is supporting your work on wiki and how we can change or improve things in the future. The opinions you share will directly affect the current and future work of the Wikimedia Foundation.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. [mailto:surveys@wikimedia.org Email us] if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely, RMaung (WMF) 14:34, 9 September 2019 (UTC)

Reminder: Community Insights Survey
Share your experience in this survey

Hi ,

A couple of weeks ago, we invited you to take the Community Insights Survey. It is the Wikimedia Foundation’s annual survey of our global communities. We want to learn how well we support your work on wiki. We are 10% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! Your voice matters to us.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. [mailto:surveys@wikimedia.org Email us] if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely, RMaung (WMF) 19:14, 20 September 2019 (UTC)

Italian etymologies
I think you are the right user whose help may be sought in this matter. I often find it hard to understand whether Italian words such as, , , , , can be considered to have been inherited from Vulgar Latin, or to be learned borrowings from Classical/Late/etc. Latin. Can the phonology of such words give any hint to this, or is it tough to discern the etymon accurately? Thanks for the heed! —Lbdñk (talk) 14:47, 3 October 2019 (UTC)
 * Hi! I have a very hard time trying to figure it out myself: I usually consider terms who haven't undergone any unusual sound change to be learned borrowings ("usual" sound changes being →,  → ,  → ,  →  and the like). I'm afraid I can't be of much help in this regard. – GianWiki (talk) 22:06, 3 October 2019 (UTC)
 * That help was considerable! Well, do you know of any Romance etymological dictionary that, by distinguishing between learned borrowings and inherited words, shows accurate etymons of the words of Romance languages? —Lbdñk (talk) 20:18, 4 October 2019 (UTC)
 * (The TLFi does that, but that's for French.) See also . Canonicalization (talk) 20:58, 4 October 2019 (UTC)

Reminder: Community Insights Survey
Share your experience in this survey

Hi ,

There are only a few weeks left to take the Community Insights Survey! We are 30% towards our goal for participation. If you have not already taken the survey, you can help us reach our goal! With this poll, the Wikimedia Foundation gathers feedback on how well we support your work on wiki. It only takes 15-25 minutes to complete, and it has a direct impact on the support we provide.

Please take 15 to 25 minutes to give your feedback through this survey. It is available in various languages.

This survey is hosted by a third-party and governed by this privacy statement (in English).

Find more information about this project. [mailto:surveys@wikimedia.org Email us] if you have any questions, or if you don't want to receive future messages about taking this survey.

Sincerely, RMaung (WMF) 17:04, 4 October 2019 (UTC)

Sardinian verb conjugation templates
Hey I was just looking at your edits to the Sardinian verb conjugation templates, and was wondering if there's a strong reason to require a stem-stressed and a conjugation-stressed parameter, especially since that already interferes with several established entries. Is it possible to make the second parameter optional and automatically replaced by the first parameter? Would it be necessary to require a second stem-changing-exclusive template? Thank you in advance for your work here. Qwed117 (talk) 09:06, 6 December 2019 (UTC)
 * : The orthographic rules of the Limba Sarda Comuna (which is the main object of my contributions on Sardinian) say that, anytime a word is stressed on the antepenultimate syllable or vowel, the accent is to be indicated, and that's something that tends to happen with the rhizotonic forms of verbs. – GianWiki (talk) 10:44, 6 December 2019 (UTC)
 * Thanks for the clarification. Based on my (admittedly not advanced) understanding of Sardinian grammar, however, all regularly conjugating verbs in the first (-are) and third (-ire) conjugation do not have any antepenultimate stressed syllables, and it's only second conjugation (-ere) verbs that maintain rhizotonic stress in antepenult. This, I believe, is confirmed in the source provided. In the case of irregular verbs (like tennere), I'd imagine that using the previous overrides would be sufficient. Given that should we revert the -are, -ire conjugation templates to require only the arrhizotonic stem? Thank you for your comment Qwed117 (talk) 04:22, 7 December 2019 (UTC)
 * Yes, I suppose you're right. The overrides will do. I have eliminated the need for the second stem from the templates. Thank you for your help. -- GianWiki (talk) 10:52, 7 December 2019 (UTC)

Ligurian piemonteise
What diacritics would the Ligurian word piemonteise have, if any? --Apisite (talk) 00:50, 29 March 2020 (UTC)
 * Hi. In the orthography I employ (the Grafîa ofiçiâ in the didactic context), the word would be written as piemontéize. Also, I believe there's an ongoing discussion about which orthography to adopt for Ligurian lemmas. – GianWiki (talk) 09:26, 29 March 2020 (UTC)

Taxonomic categories
Do you think you are able to categorize plants more fine-grained than Category:Plants? I saw that you have recently created a lot of plant names and since you as an old user are probably firm in the other things I wanted to inform you because you could make even more use of plant name additions. If you enter a taxon into Wikipedia or Wikispecies it will give you a stemma where the plant is situated, or else you will always find the relation if you search the taxon on the web as there are many expert-made databases for organisms; we mostly sort by  and, sometimes tribe or genus if there are many species with vernacular names for it. Of course the categories cannot be arbitrarily named but need to exist already; you can look into English entries to see how they are named, else search the category name space (starting a search beginning with “Category:”), or the names are of course found in the module data. Here you see that Physalis alkekengi (, see the “References” links on the Wiktionary page for the taxon to see Wikispecies and other databases) is in Category:Nightshades, which is the family Solanaceae, a famous family everyone should know; some categories have easy English names some the Latin names used by botanists. Then you also should not add the label “botany” because the category becomes full of things not only used by botanists but most Italians. See also. He also learned to categorize plant names more exactly and thus had even more fun adding plants and animals. Fay Freak (talk) 14:16, 11 April 2020 (UTC)
 * Thank you very much for your suggestion, and sorry for not having been more specific in categorizing my entries. – GianWiki (talk) 16:49, 11 April 2020 (UTC)
 * I've gone through the Category:it:Plants and fixed up the categories (I enjoy doing this sort of thing). Some of the smaller categories are a bit thin, but Italian is a major world language that has terms for everything, so they'll fill up in time. Some of the regional languages don't have attestation at the same scale, so for those it's better to use a broader category rather than the very specific ones used in English (they're needed because the categories for English get too full). That's not to say that someone speaking a regional language doesn't know or talk about everything a monolingual Italian speaker would, but my impression is that they're likely to use their own local language for more local and personal things and switch to Italian for more technical and international types of things.
 * The main thing I've noticed that was inflating the count in Category:it:Plants was the unnecessary use of it. It's convenient to use, but it's easy to forget that it adds a category as well as displaying on the definition line. There's really not much point in having a definition that starts with "it A plant...", and there are other ways of giving the same information that don't add the category even when the information is useful.
 * A tool that I find very useful is HotCat, which you can enable in the Gadgets tab in your Preferences. The auto-fill-in feature let's you see if a category already exists, and it saves typing/potential for misspelling (Category:Malpighiales order plants may be obvious to Italians, but I sometimes forget which letter gets the "h").
 * Having said all of that, it's better to use a broad category than no category at all: at least there's a way to find all the entries that need their categories changed. Thanks for all you do! Chuck Entz (talk) 16:03, 12 April 2020 (UTC)

Pronunciation 1
Hi. Please avoid using headers like ===Pronunciation 1=== and ===Pronunciation 2=== (e.g. in ingobbi). Instead, use ===Etymology 1=== and ===Etymology 2=== and put a separate level-4 ====Pronunciation==== header under each. Thanks! Benwing2 (talk) 05:53, 2 July 2021 (UTC)
 * Ok, thank you very much for the tip, I'd been kinda wondering about how to proceed in such cases. — GianWiki (talk) 15:24, 2 July 2021 (UTC)

Rhymes
Hi. Just a note to be careful with adding rhymes. If a given word has two pronunciations corresponding to different meanings, each meaning and pronunciation (including the call) should go under a separate ===Etymology N=== section. I've also found several places where the rhyme you added was wrong, e.g. the latest one I found is apozema, where you gave the rhyme -ɛma (and similarly in the plural apozemi) even though the word has the stress apòzema hence the correct rhyme is -ɔddzema). Benwing2 (talk) 07:47, 5 July 2021 (UTC)
 * I'm sorry. Sometimes I seem to forget to make the right edits (as in the case of ). I'll be more careful. — GianWiki (talk) 09:48, 5 July 2021 (UTC)
 * Thanks! Benwing2 (talk) 13:41, 5 July 2021 (UTC)

pronunciations from DiPI
Hi. When you add rhymes, can you check the pronunciation in Canepari's Dizionario di Pronuncia Italiana? The pronunciations you're adding, and those found in most dictionaries, are "traditional", prescriptive pronunciations that often no longer reflect modern usage. Wiktionary is a descriptive rather than prescriptive dictionary, so we should reflect modern usage, which Canepari's dictionary does. Benwing2 (talk) 05:07, 8 August 2021 (UTC)

Romagnol language
Hello can you fix my template rgn-IPA?--BandiniRaffaele2 (talk) 12:49, 30 September 2021 (UTC)

 * To be honest, I don't know the first thing about Romagnol. GianWiki (talk) 12:51, 30 September 2021 (UTC)

The phonology is the same as Italian, I only ask you to fix the Template if you want because it doesn't work at the moment. Otherwise where or to who can I ask ?--BandiniRaffaele2 (talk) 13:06, 30 September 2021 (UTC)

 * I'm not really knowledgeable about templates. I see @Erutuon created the template. Perhaps you could try asking them? GianWiki (talk) 13:09, 30 September 2021 (UTC)

Lombard Wiktionary and Ligurian
Recently, Lombard Wiktionary has been created. You may add Ligurian entries over there. --Apisite (talk) 13:11, 10 December 2021 (UTC)

What do you think? --Apisite (talk) 17:31, 10 December 2021 (UTC)

Rhymes:Italian/aɲɲolo
I'm confused, is this really correct pronunciation? I don't speak Italian, but combination of sounds /ɲɲ/ or the like seems utterly bizarre and hard to pronounce, and I would think, for example, "agnolo" would be pronounced as something like /aɲolo/ not /aɲɲolo/. Acolyte of Ice (talk) 11:15, 28 April 2022 (UTC)
 * As far as I know, in Italian, is always geminated when in intervocalic position. – GianWiki (talk) 14:19, 28 April 2022 (UTC)
 * GianWiki is correct, is one of the sounds that's always pronounced geminated between vowels in Italian. Other examples are . If you think  is hard to pronounce then you're probably misinterpreting what this means. It means the sound  is held longer than normal before being released; it doesn't mean that you articulate the sound twice (i.e. with two onsets and two releases). Consider for example English coat check, which has a lengthened  sound in the middle, vs. coach check, which has a doubly-articulated  in the middle. Benwing2 (talk) 03:39, 12 June 2022 (UTC)

rhymes vs Template:it-pr
Hi GianWiki. I notice you're adding a whole lot of rhymes to Italian pages, without adding the actual pronunciation. If possible, please use to add the actual pronunciation; it also includes the rhyme and hyphenation, and it's hardly more work to add it vs. adding just the rhyme. Thanks! Benwing2 (talk) 03:41, 12 June 2022 (UTC)

changed Template:it-verb
Hi. I changed the syntax of a bit so that it matches the new  syntax, which allows all forms of a verb to be generated. The old syntax sits at and I renamed all existing uses of  except those taking no parameters. I'm going to gradually put things back to with the new syntax. Note that the syntax doesn't change for verbs in -are (except for andare, dare, fare and derivatives) and generally not verbs in -ire either. I'm going to be documenting the new syntax shortly. Please use the new for -are verbs with the same syntax as before. Thank you! Benwing2 (talk) 17:05, 12 June 2022 (UTC)

New quotation templates
Salve! Mi son divertito a creare, oltre a RQ:it:Commedia, RQ:it:Decameron, RQ:it:Canzoniere, RQ:it:Orlando furioso, RQ:it:I promessi sposi e RQ:it:I Malavoglia. Non esitare a migliorarne il funzionamento, o a pingarmi con le tue proposte. Ho trascurato il problema delle edizioni, buttando tutto nell'edizione che tiene Wikisource: dimmi se ritieni necessario che ci sia un qualche parametro (per esempio, ed) per specificare un'edizione diversa per un qualche specifica parola. Ho anche trascurato gli anni, scrivendo solo il secolo, perché mi ci stavo un po' perdendo. Anche la dicitura dei template, l'ho scelta arbitrariamente. Saluti! Catonif (talk) 19:04, 22 December 2022 (UTC)

Use of l to link English words
It is preferable to use raw links for English words in definitions, rather than linking every English word using en as you've been doing e.g. at. Also, please try to use short glosses rather than long definitions whenever possible, and write the definitions gloss-style, i.e. beginning with a lowercase letter and not ending in a period. Do not use full-sentence style for foreign terms. Thanks! Benwing2 (talk) 06:39, 1 January 2023 (UTC)

 inline modifier and tag= param
Hi, I notice you've been using the tag param and/or inline modifier in syn, ant and/or desc. These are changing to be lb and now that dialect tags have been unified with labels; the values of these parameters are handled just like labels in the lb template. Benwing2 (talk) 20:54, 16 April 2024 (UTC)

 * Thank you very much for the heads-up —— GianWiki (talk) 11:00, 17 April 2024 (UTC)

title: User talk:GianWiki


text:
telewizyjny

Etymology
From.

Adjective

 * 1)  televisual

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

title: telewizyjny


text:
vishkull

Etymology
Possibly from Romance *viscula (cf. 🇨🇬).

Noun

 * 1) birch, rod, cane, withy, lash
 * 2) sapling, young tree
 * 3)  naked
 * 1)  naked
 * 1)  naked

title: vishkull


text:
Talk:back to square one

Folk etymology: BBC football commentary
A common folk etymology derives this from BBC football commentaries of the 1920s, but there is no evidence for this.

For detailed discussion, see:

In brief:

In 1927 the BBC began live radio commentary of football in the UK, and divided the field into eight rectangles to allow the commentator to describe the ball’s location. The folk etymology posits that when one of the teams passed the ball from midfield to the left back (or equivalent defensive position) it would be sent “back to square one”, hence the phrase. However:
 * “back to square one” is not recorded in any recording of the commentary;
 * the system was dropped soon after inception;
 * there is an over 2 year gap between the use of the system and the first attestation of the phrase; and
 * there was nothing special about the rectangle numbered one (play did not restart from there).

On the contrary, the earliest attestation (1952) specifically cites snakes and ladders, so I see no reason to not give this as the clear primary source. Other games may have played a part, but this seems unambiguous.

 * —Nils von Barth (nbarth) (talk) 14:30, 10 November 2013 (UTC)

 * While Martin notes that most games of snakes and ladders don’t in fact return the player to square one, this seems a clear metaphorical use, and in fact many games do include a snake going back to square one, as in the attached image (this revision).
 * Martin also notes that presumably the phrase originated earlier, noting hearsay mentions decades earlier. Please add any further information you may find!
 * —Nils von Barth (nbarth) (talk) 14:46, 10 November 2013 (UTC)

title: Talk:back to square one


text: papoila

title: papoila


text: aîsiement

title: aîsiement


text:
veth

Etymology
Diminutive of ;.

Noun

 * 1) flyblow

title: veth


text:
Heliconius

Hypernyms

 * ; - subfamily;  - tribe

Hyponyms

 * - type species;, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

title: Heliconius


text:
rumpty

Interjection

 * 1) A nonsense word, especially in simple or childish songs.

Adjective

 * 1)  Of a quality below standard; in a state of disrepair.

title: rumpty


text:
Rumpty

Noun

 * 1)  A  airplane.

title: Rumpty


text:
autocontrarsi

Etymology
From.

Verb

 * 1)  to self-contract, to contract by itself

title: autocontrarsi


text:
veshël

Etymology
From.

Adjective

 * 1) fruitful

title: veshël


text:
rumpty-tumpty

Adjective

 * 1) With a lively beat and strong, non-syncopated rhythm; upbeat and bouncy.
 * 2) * 2004, Marion Arnott, "Dollface", in Ed Gorman, Martin H. Greenberg (editors), The World's Finest Mystery and Crime Stories, Fifth Annual Collection, page 238
 * It's a right rumpty-tumpty tune anyway.

Interjection

 * 1) A nonsense word, especially in simple or childish songs.

Noun

 * 1) Nonsense.
 * 2)  Sex.
 * 1)  Sex.

title: rumpty-tumpty


text:
aaheiy

Verb

 * 1) reelect, reshuffle

Noun

 * 1) reelection, reshuffle
 * 1) reelection, reshuffle

title: aaheiy


text: floatsticks

title: floatsticks


text: はりねずみ

title: はりねずみ


text:
dripstick

Noun

 * 1)  A thin hollow tube installed vertically in the bottoms of fuel tanks of many large aircraft, used to check fuel levels; now mostly superseded by the floatstick.

title: dripstick


text:
vepër

Etymology
From.

Noun

 * 1) piece (artistic), deed, creation

title: vepër


text: dripsticks

title: dripsticks


text: langfingrer

title: langfingrer


text: ハリネズミ

title: ハリネズミ


text:
arco da velha

Etymology
Possibly a shortening of, a reference to the Old Testament and Genesis 9:12-17. Compare 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬.

Noun

 * 1) rainbow

title: arco da velha


text: arco-da-velha

title: arco-da-velha


text:
sukeraĵo

Etymology
From.

Noun

 * 1) sweet sugary confection

title: sukeraĵo


text: sukeraĵoj

title: sukeraĵoj


text: sukeraĵon

title: sukeraĵon


text: sukeraĵojn

title: sukeraĵojn


text: langfingrar

title: langfingrar


text: posthistories

title: posthistories


text: Template:R:SDM

title: Template:R:SDM


text: langfingrane

title: langfingrane


text:
subtopical

Adjective

 * 1) Relating to a subtopic.

title: subtopical


text:
squatch

Etymology
Shortening.

Noun

 * 1)  sasquatch

title: squatch


text:
squatchy

Adjective

 * 1)  Characteristic of the sasquatch.

title: squatchy


text: håndflata

title: håndflata


text: håndflaten

title: håndflaten


text:
afrancesar

Etymology
From.

Verb

 * 1)  to frenchify

Etymology
From.

Verb

 * 1)  to frenchify

Etymology
From.

Verb

 * 1)  to frenchify

title: afrancesar


text:
vegsh

Etymology
From with  suffix.

Noun

 * 1) clay pot

title: vegsh


text: håndflater

title: håndflater


text: håndflatene

title: håndflatene


text:
𐌖𐌄𐌓𐌚𐌀𐌋𐌄

Etymology

 * possibilities include:
 * from, from , and cognate to 🇨🇬;
 * from, from , thus formally equivalent to 🇨🇬.

Noun

 * 1) temple

title: 𐌖𐌄𐌓𐌚𐌀𐌋𐌄


text:
Module:User:Njardarlogar/nn-noun-common-irreg

local export = {}

local m_headword = require("Module:headword") local lang = require("Module:languages").getByCode("nn")

function export.main(frame) args = frame:getParent.args PAGENAME = mw.title.getCurrentTitle.text length = PAGENAME:len t5 = PAGENAME:sub(length-4, length) t4 = PAGENAME:sub(length-3, length) t3 = PAGENAME:sub(length-2, length) t2 = PAGENAME:sub(length-1, length) if t4 == 'mann' then p1 = PAGENAME:gsub(t4, '') gender = 'm' definite_singular = p1 .. 'mannen' indefinite_plural = p1 .. 'menn' definite_plural = p1 .. 'mennene' else return "'The noun " .. PAGENAME .. " is not supported by this template.' Use instead" end

local inflections = { {label = 'definite singular', definite_singular}, {label = 'indefinite plural', indefinite_plural}, {label = 'definite plural', definite_plural}} return m_headword.full_headword(lang, nil, nil, nil, {gender}, inflections) end

return export


text:
Talk:youth

RFD
Rfd-sense (Pointed out by a poster in Feedback):
 * 1)  young Muslim
 * 2) * 2013, Malin Rising, Associated Press, Riots in Stockholm Spread to More Suburbs:
 * Groups of youth have smashed shop windows, set cars ablaze and burnt down a cultural center as the riots that started in one Stockholm suburb after a fatal police shooting spread to other low-income areas of the Swedish capital.

This is entirely determined by the context: in Stockholm, the youths that were causing trouble happened to be Muslims, but somewhere else, it could be any of a number of different religious/racial or even economic groups. The only reason it's used without a qualifier here is because everyone who's reading the article already knows who's rioting. Chuck Entz (talk) 05:11, 29 October 2013 (UTC)

 * I agree, delete (speedily, even). The given citation is using "youth" to refer to "young person/people". In this specific case, they may be Muslim in addition to young, but that doesn't cause "youth" to mean "Muslim" any more than a citation saying this is a picture of "a senator" causes "senator" to have "Indianan" as one of its definitions. - -sche (discuss) 08:35, 29 October 2013 (UTC)
 * And delete. Mglovesfun (talk) 08:48, 29 October 2013 (UTC)
 * Delete per nom. Speedily would be fine with me.
 * I disagree about context providing the ethnic identification. There was no mention in the text or the accompanying YouTube of the ethnicity of the rioters. The face of only one civilian was shown, one who claimed to have tried to prevent the arson of a police station. So someone like me could not be sure from the context about ethnicity. This seems more likely to be a policy of avoiding ethnic identification in a negative context by using a broad, non-ethnic term.
 * Any hyponym can be used to withhold more specific identification of an individual or group.DCDuring TALK 11:20, 30 October 2013 (UTC)

 * Speedily deleted. —Aɴɢʀ (talk) 23:27, 30 October 2013 (UTC)

youth everywhere is rising in revolt
Collins BrE plural youths 6. young people collectively youth everywhere is rising in revolt OED (also the youth) [plural] young people considered as a group Many people think the youth of today are not taught proper standards of behaviour.

Webster's 2a: a young person; especially : a young male between adolescence and maturity b: young persons or creatures —usually plural in construction

Cambridge [Uncountable, + sing/pl verb] young people, both male and female, considered as a group [Uncountable]: a noun that has no plural. [+ sing/pl verb]: A noun that refers to a group of people acting collectively. When used in the singular it can be followed by either a singular or a plural verb in BrE. In AmE a singular verb is preferred. --Backinstadiums (talk) 14:06, 4 March 2020 (UTC)

title: Talk:youth


text: User:Njardarlogar/nn-noun-comireg

title: User:Njardarlogar/nn-noun-comireg


text:
دوران

Etymology
From +

Noun

 * 1) rotation, circulation
 * 2) giddiness
 * 1) giddiness

Etymology
Both ultimately from.

Noun

 * 1) circulation, rotation
 * 2) giddiness

Noun

 * 1) time, period, era
 * 2) cycle
 * 1) cycle
 * 1) cycle
 * 1) cycle

title: دوران


text:
handflate

Etymology
From.

Noun

 * 1) palm

Etymology
From.

Noun

 * 1) palm

title: handflate


text:
neiekļūt

Verb

 * 1) to not get into, to not enter;

title: neiekļūt


text:
nekļūt

Verb

 * 1) to not become;

title: nekļūt


text:
nekustēt

Verb

 * 1) to not move;

title: nekustēt


text: User:Njardarlogar/test-veidemann

title: User:Njardarlogar/test-veidemann


text:
nekustēties

Verb

 * 1) to not move;

title: nekustēties


text:
nenazalizēt

Verb

 * 1) to not nasalize;

title: nenazalizēt


text:
netelefonēt

Verb

 * 1) to not phone, to not call by phone;

title: netelefonēt


text:
francesidade

Noun

 * 1) Frenchness

title: francesidade


text:
nežestikulēt

Verb

 * 1) to not gesticulate;

title: nežestikulēt


text:
podatkowy

Etymology
From.

Adjective

 * 1)  tax, taxation

title: podatkowy


text: vëth

title: vëth


text:
Module:nn-noun-common-irreg

local export = {}

local lang = require("Module:languages").getByCode("nn") function export.main(frame) local args = frame:getParent.args PAGENAME = mw.title.getCurrentTitle.text local length = mw.ustring.len(PAGENAME) local t5 = mw.ustring.sub(PAGENAME, length-4, length) local t4 = mw.ustring.sub(PAGENAME, length-3, length) local t3 = mw.ustring.sub(PAGENAME, length-2, length) local t2 = mw.ustring.sub(PAGENAME, length-1, length) if t4 ~= 'mann' then return "'The noun " .. PAGENAME .. " is not supported by this template.' Use instead" end local data = {lang = lang, pos_category = "nouns", categories = {}, genders = {"m"}} local p1 = mw.ustring.sub(PAGENAME, 1, length-4) definite_singular = p1 .. 'mannen' indefinite_plural = p1 .. 'menn' definite_plural = p1 .. 'mennene' data.inflections = { {label = 'definite singular', definite_singular}, {label ='indefinite plural', indefinite_plural}, {label = 'definite plural', definite_plural} } return require("Module:headword").full_headword(data) end

return export

title: Module:nn-noun-common-irreg


text: Template:nn-noun-comireg

title: Template:nn-noun-comireg


text:
Template:nn-noun-comireg/documentation

Usage
This template is used for Norwegian Nynorsk nouns that are used in many noun compounds (such as, from + ); though it also supports the nouns themselves, outside of compounds.

The template currently supports the following nouns and any compound of them:

The template takes no parameters.

title: Template:nn-noun-comireg/documentation


text:
dodatkowy

Etymology
From.

Adjective

 * 1) additional, supplementary
 * 2)  appendant

title: dodatkowy


text: vingroju

title: vingroju


text: handflaten

title: handflaten


text: nevingroju

title: nevingroju


text: vingrinu

title: vingrinu


text: vingrināju

title: vingrināju


text: nevingrinu

title: nevingrinu


text:
vorr

Etymology
Gheg variant of.

Noun

 * 1) grave

Etymology
From.

Noun

 * 1) moraine, ridge
 * 2) stonework on either side of a boat landing, which can be used to moor a boat; a sloping stone pier
 * 3) a wake in the water after a boat
 * 4) the distance which a boat moves forth as a result of a pull of the oar

Etymology 1

From.

Noun

 * 1) moraine, a ridge of stone or gravel
 * 2) stonework on either side of a boat landing, which can be used to moor a boat; a sloping stone pier
 * 1) stonework on either side of a boat landing, which can be used to moor a boat; a sloping stone pier

Etymology 2
From and.

Noun

 * 1) a movement, whirl or other disturbance in the water surface
 * 2)  a wake
 * 3) a stroke of the oar
 * 4) the distance which a boat moves forth as a result of a pull of the oar
 * 5) noise, unrest

Etymology 3
From, from.

Noun

 * 1) loud speech, a blending of voices, murmur
 * 2) babbling, chatter

title: vorr


text: nevingrināju

title: nevingrināju


text: iekļūstu

title: iekļūstu


text: iekļuvu

title: iekļuvu


text: handflater

title: handflater


text: neiekļūstu

title: neiekļūstu


text: neiekļuvu

title: neiekļuvu


text: kļūstu

title: kļūstu


text: kļuvu

title: kļuvu


text: nekļūstu

title: nekļūstu


text: nekļuvu

title: nekļuvu


text: brannmenn

title: brannmenn


text: brannmannen

title: brannmannen


text: brannmennene

title: brannmennene


text: kustēju

title: kustēju


text: handflatene

title: handflatene


text:
Thread:User talk:CodeCat/WT:RFV rignbuga

I would appreciate your input on this- it's from a French IP, and I vaguely seem to remember previous problems with unattested Gothic added by an IP using a similar IP range.


text: copulatores

title: copulatores


text: copulatoris

title: copulatoris


text: copulatoribus

title: copulatoribus


text: copulatorem

title: copulatorem


text:
vargër

Etymology
Possibly from, or related to the compound Greek (Hes.).

Noun

 * 1) uncastrated ram or goat

title: vargër


text:
solena

Adjective

 * 1) ceremonious, solemn, ceremonial

Etymology
Borrowed from, , , and.

title: solena


text: solenaj

title: solenaj


text: solenan

title: solenan


text: solenajn

title: solenajn


text:
copulatrix

Etymology
From.

Noun

 * 1) connector (female)

title: copulatrix


text: engelskmennene

title: engelskmennene


text: engelskmenn

title: engelskmenn


text: engelskmannen

title: engelskmannen


text:
crossvein

Etymology
From.

Noun

 * 1) A vein of ore that intersects another.
 * 2) A vein in an insect's wing that connects others transversely.

title: crossvein


text:
désinfecteur

Noun

 * 1) disinfector

title: désinfecteur


text: désinfecteurs

title: désinfecteurs


text:
autolaveur

Etymology
From.

Noun

 * 1) dishwasher for laboratory glassware

title: autolaveur


text: autolaveurs

title: autolaveurs


text:
varrjesht

Etymology
A prefixed derivative;.

Noun

 * 1) swath

title: varrjesht


text:
declivous

Adjective

 * 1) sloping downward

Related terms

 * declivity

title: declivous


text:
איזבל

Etymology
From and. Sense Uncertain. Seemingly "not exalted" or "not husbanded" in the sense of shame or lawlessness, likely an intentional alteration of a Punic name attested 𐤁𐤏𐤋𐤀𐤆𐤁𐤋 (b‘l’zbl), ('Ba'al is exalted'.) Formerly it was thought to bear the sense, through "not husbanded", of "chaste" or "modest". The European name Isabel is similar in transliteration but is unrelated.

An alternative explanation is from and  (’ēyze ba’al) meaning "Where is Ba'al?" Perhaps was a ritualistic chant during Ba'al worship.

title: איזבל


text:
nyrpeä

Adjective

 * 1) irritated, annoyed, displeased, indignant
 * 2) sullen, sulky

title: nyrpeä


text:
edmontonicus

Adjective

 * 1) Edmontonian

title: edmontonicus


text: nekustu

title: nekustu


text: nekustēju

title: nekustēju


text:
epipodophyllotoxin

Noun

 * 1)  Any of a group of complex lignans extracted from the root of the  plant

title: epipodophyllotoxin


text: kustējos

title: kustējos


text: epipodophyllotoxins

title: epipodophyllotoxins


text: nekustos

title: nekustos


text: nekustējos

title: nekustējos


text: nazalizēju

title: nazalizēju


text: nenazalizēju

title: nenazalizēju


text: telefonēju

title: telefonēju


text: netelefonēju

title: netelefonēju


text: žestikulēju

title: žestikulēju


text: nežestikulēju

title: nežestikulēju


text:
epipophysis

Noun

 * 1) Any of a series of bony projections of the cervical vertebrae found in dinosaurs

title: epipophysis


text: epipophyses

title: epipophyses


text: nevingro

title: nevingro


text:
glaciogenic

Adjective

 * 1)  That give rise to glaciers.
 * 2)  That seed ice crystals in the upper atmosphere.

title: glaciogenic


text: vingrini

title: vingrini


text: vingrina

title: vingrina


text: nevingrini

title: nevingrini


text: nevingrina

title: nevingrina


text:
gonapophysis

Noun

 * 1) A modified tubular appendage of the anal region in insects that functions in copulation, oviposition, or stinging

title: gonapophysis


text: gonapophyses

title: gonapophyses


text: krēslo

title: krēslo


text: nekrēslo

title: nekrēslo


text: regimet

title: regimet


text: iekļūsti

title: iekļūsti


text: iekļūst

title: iekļūst


text: neiekļūsti

title: neiekļūsti


text: neiekļūst

title: neiekļūst


text:
hadrosauroid

Noun

 * 1) Any dinosaur of the superfamily

title: hadrosauroid


text: kļūsti

title: kļūsti


text: kļūst

title: kļūst


text: nekļūsti

title: nekļūsti


text:
جنازة

Etymology
The whole root is from  and, compare 🇨🇬 and old 🇨🇬, , potentially the same  word as.

Noun

 * 1) funeral
 * 2) bier, with a corpse on it
 * 3) corpse

title: جنازة


text: nekļūst

title: nekļūst


text:
jenazah

Etymology
From, from , from.

Noun

 * 1)  corpse.

Etymology
Borrowed from.

Noun

 * 1) corpse (of a Muslim)

Synonyms

 * (applicable to non-Muslims too)

title: jenazah


text:
varesë

Etymology
Derivative of.

Noun

 * 1) chain
 * 2) necklace

title: varesë


text:
gara d'appalto

Noun

 * 1)  tender

title: gara d'appalto


text:
iliofibularis

Noun

 * 1) A hindlimb muscle used by frogs and lizards for locomotion

title: iliofibularis


text:
interclutch

Adjective

 * 1) Between clutches of eggs

title: interclutch


text:
vanë

Etymology
A derivative of.

Noun

 * 1) rabbet, rebate
 * 2) a wall surrounding the opening of a well, wellhead

title: vanë


text:
kijevensis

Etymology
From +.

Adjective

 * 1)  Kijevo

Derived terms

 * (syn. of )

title: kijevensis


text: տուքան

title: տուքան


text:
kriegsteini

Etymology
Named in a pseudo-Latin manner for any of several naturalists named Kriegstein, especially Roman Kriegstein

Adjective

 * 1) Kriegstein (attributive); used in taxonomic names for organisms having English names of the form "Kriegstein's ..."

title: kriegsteini


text: kusti

title: kusti


text: regimene

title: regimene


text: nekusti

title: nekusti


text: nekust

title: nekust


text: kusties

title: kusties


text: kustas

title: kustas


text: nekusties

title: nekusties


text: nekustas

title: nekustas


text:
lamboys

Etymology
Unclear. Perhaps from, or perhaps a misreading of jamboys,.

Noun

 * 1)  Bases skirts made of armour

title: lamboys


text: nazalizē

title: nazalizē


text: nenazalizē

title: nenazalizē


text: telefonē

title: telefonē


text:
wavecut

Adjective

 * 1) Formed by the action of waves.

title: wavecut


text:
elteni

Etymology
From.

Verb

 * 1) to endure

title: elteni


text: netelefonē

title: netelefonē


text:
stab stitch

Noun

 * 1) A stitch in which the needle is first driven through the fabric from the right side, then pushed back up through the material from the wrong side.

title: stab stitch


text: stab stitches

title: stab stitches


text: žestikulē

title: žestikulē


text: nežestikulē

title: nežestikulē


text:
ekdormi

Etymology
From.

Verb

 * 1)  to fall asleep

title: ekdormi


text:
pick stitch

Noun

 * 1)  A simple running stitch that catches only a few threads of the fabric, showing very little of the thread on the right (outer) side of the garment.

title: pick stitch


text: pick stitches

title: pick stitches


text: running stitches

title: running stitches


text:
Reconstruction:Proto-Slavic/potьběga

Etymology
Possibly a compound of otherwise unattested, from , from ) and from.

Noun

 * 1) divorced wife

Descendants

 * Church Slavonic: (Russian)

 * East Slavic:
 * South Slavic:
 * Old Church Slavonic:
 * Cyrillic: ,
 * Glagolitic: ,
 * Middle Bulgarian: ,
 * Old Serbo-Croatian:
 * West Slavic:
 * (dialectal)
 * (archaic)
 * (archaic)
 * (archaic)

title: Reconstruction:Proto-Slavic/potьběga


text:
vingrojam

Participle

 * 1) exercising, doing gymnastics;

title: vingrojam


text:
nevingrojam

Participle

 * 1) not exercising, not doing gymnastics;

title: nevingrojam


text:
Antichthones

Noun

 * 1)  Those peoples who inhabit the antipodes, regions on opposite sides of the Earth.

title: Antichthones


text:
videble

Etymology
From.

Adverb

 * 1) visibly

title: videble


text:
Vitis labrusca

Hypernyms

 * - order; - family;  - subfamily;  - genus;  - subgenus

Hyponyms

 * For varieties see

title: Vitis labrusca


text:
Lobodon carcinophagus

Etymology
From the mistaken belief that they eat crabs. (They eat krill.)

title: Lobodon carcinophagus


text: prìomh-bhailtean

title: prìomh-bhailtean


text: Category:Japanese terms spelled with 址

title: Category:Japanese terms spelled with 址


text:
elfr

Etymology
From.

Noun

 * 1) river

title: elfr


text:
ごうん

Noun

 * 1)   the five skandhas

title: ごうん


text:
Niedlichkeit

Noun

 * 1) cuteness

title: Niedlichkeit


text: User:Hirabutor

title: User:Hirabutor


text:
baile contae

Noun

 * 1) county town

title: baile contae


text:
príomhbharr

Noun

 * 1) main crop

title: príomhbharr


text:
steppen

Etymology
From, , from , from.

Verb

 * 1) To step; to place one's foot down.
 * 2) To step onto; to lift one's foot onto a higher place.
 * 3) To go; to walk or move:
 * 4) To go to a specified location; to travel or take oneself.
 * 5)  To move onwards; to keep doing something.

Usage notes
This verb tends to become weak in later Middle English.

title: steppen


text:
五蘊

Etymology
Translation of.

Noun

 * 1)  the five skandhas (aggregates)

Etymology
From, itself a translation of  or.

Noun

 * 1)  the five skandhas (aggregates):

title: 五蘊


text:
tuladi

Etymology
From Canadian, from an Eastern language. (The fish is sometimes said to take its name from the where some spawn, but the river more likely takes its name from the fish.)

Noun

 * 1) A large lake trout,, found mainly in Canada and northern areas of the US.
 * 2) * 1894, Karl Baedeker (Firm), The Dominion of Canada: With Newfoundland and an Excursion to Alaska. Handbook for Travellers, Leipsic [i.e. Leipzig] : K. Baedeker, page 64:
 * a narrow sheet of water, about 22 M. long, abounding in large-sized trout and 'tuladi', a heavy fish of the salmon family.
 * a narrow sheet of water, about 22 M. long, abounding in large-sized trout and 'tuladi', a heavy fish of the salmon family.

title: tuladi


text: 五蕴

title: 五蕴


text:
wheel of death

Noun

 * 1)  A hollow wheel larger than a person, attached to and suspended from an axle, and inside of which an artist performs.

Translations

 * Spanish: rueda de la muerte

title: wheel of death


text:
verbalización

Etymology
From.

Noun

 * 1) verbalization (act, process of verbalizing)

Etymology
From.

Noun

 * 1) verbalization (act, process of verbalizing)

title: verbalización


text:
οὐδέ

Etymology
From +.

Conjunction

 * 1)  but not
 * 2)  and not, nor
 * 1)  and not, nor
 * 1)  and not, nor
 * 1)  and not, nor
 * 1)  and not, nor

Adverb

 * 1) not even, not at all

Usage notes
When is repeated at the beginning of two clauses, the first is often adverbial and the second is a conjunction. It may also follow, as an anacoluthon.

title: οὐδέ


text:
shopbot

Noun

 * 1) shopping bot

title: shopbot


text: shopbots

title: shopbots


text:
yealing

Noun

 * 1) Someone who is the same age as oneself.

title: yealing


text: cõello

title: cõello


text:
Category talk:Chinese place names

These seem to be invalid, we don't categorize 'place name' as a part of speech category; for topical categorization, we have Category:cmn:China. Category:Chinese place names is futhermore invalid because we don't class Chinese as a single language, so it would be like Category:Germanic place names, and Category:Mandarin place names only contains pinyin anyway, so can be legitimately emptied of its current content, regardless of whether it later passes RFD or not. Mglovesfun (talk) 00:24, 18 May 2012 (UTC)

 * Delete. The category currently serving the role per current naming convention for topical categories is Category:cmn:Place names. --Dan Polansky (talk) 19:01, 14 July 2012 (UTC)

 * Emptied, now needing to be speedied. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

title: Category talk:Chinese place names


text:
Category talk:Mandarin place names

These seem to be invalid, we don't categorize 'place name' as a part of speech category; for topical categorization, we have Category:cmn:China. Category:Chinese place names is futhermore invalid because we don't class Chinese as a single language, so it would be like Category:Germanic place names, and Category:Mandarin place names only contains pinyin anyway, so can be legitimately emptied of its current content, regardless of whether it later passes RFD or not. Mglovesfun (talk) 00:24, 18 May 2012 (UTC)

 * Delete. The category currently serving the role per current naming convention for topical categories is Category:cmn:Place names. --Dan Polansky (talk) 19:01, 14 July 2012 (UTC)

 * Emptied, now needing to be speedied. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

title: Category talk:Mandarin place names


text:
Category talk:cmn:Variant Pronunciations in traditional script

These have been in Special:WantedCategories for ages, but I don't think we do want them. The capitalization needs to be changed at the very least, but I don't think that 'Variant pronunciation' is a topical category. I don't know quite what this even means, does it mean each of these terms has at least two pronunciations, or rather than they have a variant, less common pronunciation than another more common term? Can we just remove all the categories please, and delete these two when empty? Mglovesfun (talk) 10:09, 25 May 2012 (UTC)
 * Um, what? No and no. This kind of information is extremely valuable and cannot be found in any other dictionary. Do not delete. But you're right about the capitalisation - feel free to change "Pronunciations" to lower case - but ONLY IF you can do so without creating a huge mess. ---> Tooironic (talk) 21:08, 17 November 2012 (UTC)
 * What sort of information is it? Mglovesfun (talk) 21:19, 17 November 2012 (UTC)
 * In Mandarin, readings for combinations of characters (i.e. words - 詞) are extremely fixed - the vast majority have one pronunciation. But there are a small minority of words which have more than one reading and that's what this category is supposed to cover. I wrote about this on my blog a few years ago, take a look. ---> Tooironic (talk) 22:29, 19 November 2012 (UTC)
 * Right, I think we need a better title, such as one starting with 'Mandarin' not 'cmn'. Mglovesfun (talk) 10:41, 20 November 2012 (UTC)
 * Keep per Tooironic but move to Category:Mandarin variant pronunciations in simplified script. —Μετάknowledge discuss/deeds 07:12, 4 February 2013 (UTC)

 * Kept by default, due to no discussion. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)


text:
Category talk:cmn:Variant Pronunciations in simplified script

These have been in Special:WantedCategories for ages, but I don't think we do want them. The capitalization needs to be changed at the very least, but I don't think that 'Variant pronunciation' is a topical category. I don't know quite what this even means, does it mean each of these terms has at least two pronunciations, or rather than they have a variant, less common pronunciation than another more common term? Can we just remove all the categories please, and delete these two when empty? Mglovesfun (talk) 10:09, 25 May 2012 (UTC)
 * Um, what? No and no. This kind of information is extremely valuable and cannot be found in any other dictionary. Do not delete. But you're right about the capitalisation - feel free to change "Pronunciations" to lower case - but ONLY IF you can do so without creating a huge mess. ---> Tooironic (talk) 21:08, 17 November 2012 (UTC)
 * What sort of information is it? Mglovesfun (talk) 21:19, 17 November 2012 (UTC)
 * In Mandarin, readings for combinations of characters (i.e. words - 詞) are extremely fixed - the vast majority have one pronunciation. But there are a small minority of words which have more than one reading and that's what this category is supposed to cover. I wrote about this on my blog a few years ago, take a look. ---> Tooironic (talk) 22:29, 19 November 2012 (UTC)
 * Right, I think we need a better title, such as one starting with 'Mandarin' not 'cmn'. Mglovesfun (talk) 10:41, 20 November 2012 (UTC)
 * Keep per Tooironic but move to Category:Mandarin variant pronunciations in simplified script. —Μετάknowledge discuss/deeds 07:12, 4 February 2013 (UTC)

 * Kept by default, due to no discussion. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)


text:
Category talk:Substrate languages

Apparently supposed to serve as a parent for Category:Terms derived from substrate languages. This should be solved in another way instead of this ugly hack. -- Liliana • 19:25, 6 June 2012 (UTC)
 * I agree, but where should it go? 21:03, 6 June 2012 (UTC)
 * Into category:Etymologies by language perhaps? —msh210℠ (talk) 23:05, 6 June 2012 (UTC)

 * Kept for no consensus or discussion. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

title: Category talk:Substrate languages


text:
Template talk:dlc

This is an invented code which doesn't exist according to SIL. -- Liliana • 17:17, 22 June 2012 (UTC)
 * I fail to see your point; isn't the question 'does the language Elfdalian exist'? Mglovesfun (talk) 17:43, 22 June 2012 (UTC)
 * Both are questions, actually. Do we want to treat the lect as a separate language? If so, what code should we use for it? If "dlc" isn't a valid code, we need to create a code following our "exceptional code"-creation pattern: so, "gmq-elf" or similar. This is because "dlc" could later be assigned by ISO to some other language. - -sche (discuss) 18:07, 22 June 2012 (UTC)
 * Yes, I should've said that. Mglovesfun (talk) 18:24, 22 June 2012 (UTC)
 * I have to agree with this sentiment. dlc is an invented code and as such, should either be moved or deleted because of that. Razorflame 18:27, 22 June 2012 (UTC)
 * is the LINGUIST List code for the Dalecarlian dialects, of which Elfdalian is one. The LINGUIST List code specifically for Elfdalian is, so I would recommend either using   for Elfdalian or lumping all of Dalecarlian together as a single language and using   for it. (I would prefer the second option myself.) —Angr 19:50, 22 June 2012 (UTC)
 * Incidentally, "dlc" for Dalecarlian was in a draft version of ISO 639-3, but was removed (along with "scy" for Scanian) before publication under pressure from the Swedish government, who wanted those two languages to be considered dialects of Swedish rather than separate languages (see Requests for new languages/Wikipedia Elfdalian and GerardM's blog). GerardM also says, "According to the rules of the ISO-639 standard, the code dlc will not be used for anything but Dalecarlian", so we don't have to worry about it being assigned to something else. —Angr 17:50, 25 June 2012 (UTC)
 * The second link says According to the rules of the ISO-639 standard, the code dlc will not be used for anything but Dalecarlian. If that's true, then we can safely use that code as there is no danger of a conflict with another language that is later assigned the code 'dlc'. Whether or not it's not valid ISO-639 is not really that important, as we can use any code we like as long as it conforms to the rules for the HTML lang= attribute (which allows codes other than ISO-639). A few days ago I did some researching about Elfdalian and added some entries and even without knowing Swedish too much I can already tell this language is almost as close to Old Norse as it is to Swedish, and much less like Swedish than standard Danish or Norwegian are. There is no way a Swedish speaker would understand it. As for the other varieties of Dalecarlian... well I don't know too much about them and they aren't very well documented, so I suppose we could use the name 'Dalecarlian' with the assumption that it will primarily be Elfdalian, but also allow other varieties if attested. 17:56, 25 June 2012 (UTC)
 * Re: "the HTML lang= attribute (which allows codes other than ISO-639)": I believe you're mistaken, or rather, irrelevantly correct. The HTML specification defines valid language tags by pointing to 1766 or BCP47. 1766 required the first part of a language tag to be either i, <tt>x</tt>, or a two-letter code assigned per ISO 639. BCP 47 (currently 5646) allows a few more possibilities, but it still forbids a language tag from starting with a two- or three-letter code that is not a "shortest ISO 639 code", unless the tag is one of a very short list of grandfathered tags (such as <tt>sgn-CH-DE</tt> and <tt>zh-min-nan</tt>). So while it's true that it's possible to construct a valid HTML <tt>lang=</tt> attribute that is not an ISO 639, <tt>dlc</tt> is not an example of this possibility. —Ruakh TALK 19:15, 25 June 2012 (UTC)
 * Nevertheless, Wiktionary does have language templates that don't correspond to ISO 639, and indeed we recognize languages that ISO 639 does not, such as Jèrriais and (among North Germanic languages) Gutnish . I do think our best bet is to move this template to  and change the content of it from "Elfdalian" to "Dalecarlian" so that other Dalecarlian varieties (to the extent they're attested in written form) can be subsumed under it. (On the other hand, we also have a precedent for calling a language by the name of its best known dialect: we call  "Cantonese" even though the code covers all Yue dialects, not just the Cantonese standard dialect. So in principle we could get away with calling  "Elfdalian" as well.) —Angr 20:51, 25 June 2012 (UTC)
 * I think it's fine to recognize languages that ISO 639 does not, but I think our use of nonstandard-language-codes-that-look-like-real-ones is a mistake. (And CodeCat seems to agree with me, since she says that "we can use any code we like as long as it conforms to the rules for the HTML <tt>lang=</tt> attribute"; she was mistaken about how to do that, but acknowledged that it's something we should do.) Fortunately, it's a mistake that we can rectify, once we acknowledge that it is a mistake worth rectifying. In the case of Dalecarlian, we should use (or similar): <tt>gmq</tt> is a valid language subtag, but <tt>dlc</tt> is not a valid extension code, so we need to mark it as "Private Use" by using the <tt>x</tt> prefix. —Ruakh TALK 21:19, 25 June 2012 (UTC)
 * Part of me disagrees with this on principle, I don't feel right with the idea that a standards body like ISO can tell us what codes to use, especially not when a national government has influence on it. What basically happened is that the Swedish government told us we can't use 'dlc'. It's a bit crazy... :/ 21:23, 25 June 2012 (UTC)
 * Ruakh, if you say  is better than , I'll take your word for it, and if there's consensus that you're right then we should move the other non-ISO code templates to names with an "-x-" in them as well. CodeCat, I understand your frustration and agree that it sucks that ISO caved in to political blackmail, but HTML uses the ISO codes for better or for worse, so we can't just start making up codes that influence the HTML of our pages. —Angr 21:35, 25 June 2012 (UTC)
 * I do say so, but I don't ask you to take my word for it. I encourage you, and other editors, to look through the relevant standards (W3C technical reports on HTML/XML/XHTML; IETF RFCs on language codes; the IANA language-code registry), or perhaps this informal guide by the W3C if you prefer a less technical document, and form your own opinions. —Ruakh TALK 21:43, 25 June 2012 (UTC)
 * One thing I see in the informal guide is that we have another option for picking a code:  using the ISO 3166-2 country and subdivision name as an extension will get us a properly defined "Swedish as spoken in Dalarna County". The drawback to using that is that there may be a local variety of Standard Swedish spoken there in addition to Dalecarlian. —Angr 22:10, 25 June 2012 (UTC)
 * No, that's not allowed, because subtags are separated by hyphens, and can't contain hyphens, so <tt>SE-W</tt> is two separate subtags: <tt>SE</tt> would mean Sweden, but <tt>W</tt> would be an invalid extension subtag (invalid because unregistered, and because extension subtags always have to be followed by one or more additional subtags). But if we're O.K. with treating Dalecarlian as a form of Swedish, as <tt>sv-*</tt> implies, then we may be able to register a "variant" subtag with IANA, such as <tt>dalec</tt>, such that Dalecarlian would be publically defined as <tt>sv-dalec</tt>. (I think. I've never really looked into how variant codes work.) —Ruakh TALK 22:30, 25 June 2012 (UTC)
 * Well, it wasn't supposed to be more than a kludge, so if it isn't allowed anyway, I'd rather use  for linguistic reasons (Dalecarlian linguistically isn't just a dialect of Swedish, whatever Stockholm says). —Angr 09:07, 26 June 2012 (UTC)

 * [@CodeCat, after e/c] Well, but the main purpose of these codes is interoperability with other standards-compliant systems. I don't like that political factors play a role in the assignment of codes, but we don't really accomplish anything by silently subverting it. We can fight the injustice by expanding our Dalecarlian coverage and treating its words as ==Dalecarlian==, but assigning Dalecarlian its own pseudo-code <tt>dlc</tt> will not help and should play no part. (Imagine that your corrupt local government was bribed to split up your telephone area-code into two, and you don't like the new area-code you've been assigned. Does that mean you'll continue to give out your phone number as using the old area-code, even though it won't actually enable long-distance callers to reach you?) —Ruakh TALK 21:43, 25 June 2012 (UTC)

 * I think I get it, dlc was removed as Wikipedians put it 'with prejudice'. Since we keep because although ISO 639-1 retired the code, we still find it useful, and we should aim to make use of ISO 639, but not to be a slave to it. So I'm fine keeping this per the KISS principle; why use a seven or nine character code well three will do. Mglovesfun (talk) 21:39, 25 June 2012 (UTC)
 * There is a difference: sh used to be valid. dlc never was. -- Liliana • 21:41, 25 June 2012 (UTC)

 * @Ruakh: can the codes Wiktionary uses in its HTML be different from the template titles/codes, or are the template-values automatically the HTML values? I.e., can we (per our current naming scheme) name the template, but set the HTML to "gmq-x-dlc"? What HTML codes are currently associated with our other exceptional codes, such as ; do they include "-x-"? When the WMF creates exceptional codes for new wikis in languages without ISO codes, what naming scheme do they follow? - -sche (discuss) 22:35, 25 June 2012 (UTC)
 * Re: first two questions: I guess it depends what you mean by "can" and "automatically". Currently, we design templates under the assumption that these will be identical; we don't have any mechanism in place for mapping from language-template-name to HTML-language-tag. If is <tt>Dalecarlian</tt> and  is <tt>Latn</tt>, then  will be <tt> foo  </tt>. But there's no technical reason that we can't institute such a mapping.
 * Re: third question: As I'm sure you can guess from the answers to your first two questions, the answer to this one is "e.g. <tt>roa-jer</tt>; no, no <tt>-x-</tt>".
 * Re: last question: They no longer do that — see Language proposal policy — but back when they did do it, their naming scheme was basically "invent something realistic-looking". Needless to say, this eventually led to problems. The Swiss German Wikipedia is <tt>als.wikipedia.org</tt>, but ISO/SIL assigns <tt>als</tt> to Tosk Albanian and <tt>gsw</tt> to Swiss German. Our scheme, inventing codes like <tt>roa-jer</tt>, is not nearly so bad as that, IMHO; but it's still far from ideal.
 * —Ruakh TALK 23:11, 25 June 2012 (UTC)

Sorry if this is a stupid question but, who forces us to use syntactically valid language codes? As long as browsers can parse them, everything should be fine? -- Liliana • 23:27, 29 June 2012 (UTC)

 * If they aren't syntactically valid, then browsers can't necessarily parse them. I don't trust them not to give out dlc. (For example, Romania found rom to be troublesome, as it imply the Roma in their eyes, so they demanded a new country code and got rou, even though that was reserved, as the Republic of Uruguay has apparently used it in some context.) And if it's given to say a language written in China in the Chinese script, indicating the text is in dlc may make a browser preemptorily change to a Simplified Chinese font.--Prosfilaes (talk) 00:44, 10 October 2012 (UTC)

 * Tagged to be speedied as a deprecated template. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

title: Template talk:dlc


text:
Template talk:kpv

Redundant to Template:kv. 18:12, 20 October 2012 (UTC)
 * Sure. Do delete. -- Liliana • 19:43, 20 October 2012 (UTC)
 * Delete. Mglovesfun (talk) 10:08, 22 October 2012 (UTC)
 * I just did some researching on this. It seems that kv is the code for Komi language while kpv and koi are codes for two subdivisions of that, Komi-Zyrian language and Komi-Permyak language. I'm not quite sure what the difference is, but the articles about the subdivisions state that Komi is pluricentric and that kpv and koi are two standards based on different dialects of the same "language". This sounds very familiar somehow... 17:18, 9 November 2012 (UTC)

 * So, should we delete kv instead, and use kpv? - -sche (discuss) 18:34, 16 June 2013 (UTC)

 * FWIW, see also Requests for moves, mergers and splits. - -sche (discuss) 18:34, 16 June 2013 (UTC)

 * Kept for no consensus or discussion. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

title: Template talk:kpv


text:
Category talk:Apple Inc.

For the same reasons as Category_talk:Sony, which led to deletion (though Category_talk:Microsoft, which is similar to both, was kept.) Equinox ◑ 20:18, 2 November 2012 (UTC)

D  —Michael Z. 2013-02-02 23:02 z
 * Delete. — Ungoliant (Falai) 07:47, 3 February 2013 (UTC)

 * Kept for no consensus or discussion. --ElisaVan (talk) 21:02, 3 November 2013 (UTC)

RFM discussion: October–November 2017
Much clearer and it's the proper name of the company. —Rua (mew) 13:33, 16 October 2017 (UTC)
 * Support. --Daniel Carrero (talk) 17:38, 20 October 2017 (UTC)

 * Support. Equinox ◑ 17:40, 20 October 2017 (UTC)

Moved. —Rua (mew) 22:00, 8 November 2017 (UTC)

title: Category talk:Apple Inc.


text:
Template talk:ydd

WT:AYI says, and practice is, that Yiddish is treated as one language. That being the case, Template:ydd and Template:yih should be deleted (like Template:hbo). - -sche (discuss) 09:35, 17 November 2012 (UTC)
 * First of all: WT:AYI is just me rambling on, and "practice" is just me and about three other editors, none of whom speak better Yiddish than Wikitiki89 (who is yi-1). If someone comes up with evidence I haven't seen, I'll be glad to consider it. However, in the mean time I'd advocate deletion of these, because the vast majority of our entries are in standard Litvish Yiddish, and I don't know the extent of dialectal variation, but I think it can't be too great (considering that Poylish dialect speakers don't seem to far off standard, at least in writing). —Μετάknowledge discuss/deeds 16:13, 17 November 2012 (UTC)
 * "Practice" is that neither of these templates are used, which is probably an indicator that deletion is the best option. Mglovesfun (talk) 12:32, 18 November 2012 (UTC)

 * Note that there is only one Yiddish Wikipedia and only one Wiktionary, both using the code . - -sche (discuss) 18:49, 19 November 2012 (UTC)
 * Well that's because there is only one standard orthography and the non-standard orthographies don't depend on dialect. Regardless, unless we want to split English into American and British, then there is no reason to split Yiddish. Delete. --WikiTiki89 19:03, 19 November 2012 (UTC)

 * Deleted (merged into 'yi'). - -sche (discuss) 05:11, 4 November 2013 (UTC)

title: Template talk:ydd


text:
Template talk:yih

WT:AYI says, and practice is, that Yiddish is treated as one language. That being the case, Template:ydd and Template:yih should be deleted (like Template:hbo). - -sche (discuss) 09:35, 17 November 2012 (UTC)
 * First of all: WT:AYI is just me rambling on, and "practice" is just me and about three other editors, none of whom speak better Yiddish than Wikitiki89 (who is yi-1). If someone comes up with evidence I haven't seen, I'll be glad to consider it. However, in the mean time I'd advocate deletion of these, because the vast majority of our entries are in standard Litvish Yiddish, and I don't know the extent of dialectal variation, but I think it can't be too great (considering that Poylish dialect speakers don't seem to far off standard, at least in writing). —Μετάknowledge discuss/deeds 16:13, 17 November 2012 (UTC)
 * "Practice" is that neither of these templates are used, which is probably an indicator that deletion is the best option. Mglovesfun (talk) 12:32, 18 November 2012 (UTC)

 * Note that there is only one Yiddish Wikipedia and only one Wiktionary, both using the code . - -sche (discuss) 18:49, 19 November 2012 (UTC)
 * Well that's because there is only one standard orthography and the non-standard orthographies don't depend on dialect. Regardless, unless we want to split English into American and British, then there is no reason to split Yiddish. Delete. --WikiTiki89 19:03, 19 November 2012 (UTC)

 * Deleted (merged into 'yi'). - -sche (discuss) 05:11, 4 November 2013 (UTC)

title: Template talk:yih


text:
Template talk:tnv

To quote Ethnologue, "90% intelligibility of Chakma [ccp]". Looks like a dialect to me; I can't get any data on whether it's written in the same idiosyncratic script, though. If not, it might be easier in the future to separate them. —Μετάknowledge discuss/deeds 05:02, 21 February 2013 (UTC)
 * Are you proposing deletion of the template only or a change in how we treat the lect? If the former, how would that work technically? And if the latter, it should be in the BP, not here. (Same for Shelta, above.) —msh210℠ (talk) 17:38, 21 February 2013 (UTC)
 * A dedicated page for "Requests to change the treatment of lects" might be useful... I have noticed that our discussions are spread out across three pages. When I want to merge lects+codes+templates, I usually post on WT:RFM (the page for merging things), which there's precedent for. Metaknowledge posts here on WT:RFDO (the page for deleting templates), which there's precedent for. On occasion, people post in the BP. The majority of discussions take place on WT:RFM, in part because I am the most prolific starter of them. - -sche (discuss) 20:12, 21 February 2013 (UTC)
 * Please see further conversation on this topic below at [[]]. —msh210℠ (talk) 07:45, 24 February 2013 (UTC)

= March 2013 =
 * Kept for no consensus. --ElisaVan (talk) 21:13, 3 November 2013 (UTC)

title: Template talk:tnv


text: דׄלך

title: דׄלך


text: lacrimals

title: lacrimals


text: lachrymals

title: lachrymals


text: stepperne

title: stepperne


text:
necrotrophy

Noun

 * 1)  The condition of being necrotrophic.

Translations

 * Italian: necrotrofia, necrotrofismo

title: necrotrophy


text:
neopteran

Noun

 * 1) Any winged insect of the infraclass Neoptera

Translations

 * Italian:

title: neopteran


text:
neotheropod

Noun

 * 1) Any dinosaur of the clade

title: neotheropod


text: steppene

title: steppene


text: neotheropods

title: neotheropods


text:
osmoregulator

Noun

 * 1) Any organism that practices osmoregulation

title: osmoregulator


text:
kopernikium

Etymology
(see 🇨🇬).

Noun

 * 1) copernicium

Noun

 * 1) copernicium element

title: kopernikium


text:
osteodysplasia

Noun

 * 1)  Any abnormal development of bone

title: osteodysplasia


text: paleodiversity

title: paleodiversity


text:
paleoecologic

Adjective

 * 1) paleoecological

Etymology
.

Adjective

 * 1) paleoecological

title: paleoecologic


text:
berýlium

Noun

 * 1) beryllium element

title: berýlium


text:
Template:ka-proper noun/documentation

Takes only one optional unnamed argument which is term's plural if it has any.

title: Template:ka-proper noun/documentation


text:
gullasj

Etymology
From, from , from.

Noun

 * 1) goulash

title: gullasj


text:
vingrinām

Participle

 * 1) exercising, making stronger;

title: vingrinām


text:
nevingrinām

Participle

 * 1) not exercising, not making stronger;

title: nevingrinām


text:
iekļūstam

Participle

 * 1) getting into, entering;

title: iekļūstam


text:
neiekļūstam

Participle

 * 1) not getting into, not entering;

title: neiekļūstam


text:
kļūstam

Participle

 * 1) becoming;

title: kļūstam


text:
nekļūstam

Participle

 * 1) not becoming;

title: nekļūstam


text:
kustam

Participle

 * 1) moving;

title: kustam


text:
nekustam

Participle

 * 1) not moving;

title: nekustam


text:
kustamies

Participle

 * 1) moving;

title: kustamies


text:
krækiber

Etymology
From.

Noun

 * 1) crowberry

Noun

 * 1) crowberry

Descendants

 * Norwegian:
 * Bokmål:
 * Norwegian:
 * Bokmål:
 * Bokmål:
 * Bokmål:

title: krækiber


text:
nekustamies

Participle

 * 1) not moving;

title: nekustamies


text:
nazalizējam

Participle

 * 1) nasalizing;

title: nazalizējam


text:
nenazalizējam

Participle

 * 1) not nasalizing;

title: nenazalizējam


text:
telefonējam

Participle

 * 1) phoning, calling by phone;

title: telefonējam


text:
netelefonējam

Participle

 * 1) not phoning, not calling by phone;

title: netelefonējam


text:
žestikulējam

Participle

 * 1) gesticulating;

title: žestikulējam


text:
nežestikulējam

Participle

 * 1) not gesticulating;

title: nežestikulējam


text: vingrojat

title: vingrojat


text: nevingrojat

title: nevingrojat


text: גׄמיע

title: גׄמיע