text:
Category talk:Prakrit languages

Shouldn't we have a category on the separate prakrit languages, since they obviously aren't just one language.
 * List of Some Prakrits:
 * Magadhi Prakrit, Shauraseni, Maharashtri Prakrit
 * Pracya, Bahliki, Daksinatya, Sakari, Candali, Sabari, Abhiri, Dramili, Odri, and others DerekWinters (talk) 19:26, 16 March 2013 (UTC)

Prakrit entries (contd.)
(Continuing the discussion that began here)

For Prakrit citations, I think we need to take a leaf from our Chinese editors. Even though Chinese is a macrolanguage, it is a single language header here. So they have dedicated a separate category for Chinese quotes, and in some of the citation pages under that category, they have even mentioned the Chinese variety in which the text is written (such as Classical Chinese, Beijing Mandarin, Cantonese, etc.). — inqilābī  ‹inqilāb·zinda·bād› 20:47, 9 January 2021 (UTC)
 * That seems to handle it well. You think anyone would mind the entry & the citations being on separate pages? -- Bhagadatta(talk) 02:12, 10 January 2021 (UTC)
 * (Pinging everyone here just in case.) I am in of this change. Having learned a great deal more about the historical development of the Indo-Aryan languages, it seems to me that it is very simplistic to say that e.g. Gujarati is a direct descendant of Sauraseni and Marathi is one of Maharastri, when it's clear that the two are far closer to each other then to Sauraseni-descended Hindi. There is a limitation in the tree model for describing Indo-Aryan, which has been noted by scholars since the time of Chatterji and Grierson. There's been so much contact historically between Indo-Aryan languages that a subcontinent-spanning dialectal continuum has formed. At the time of MIA the differences were even less, as evidenced by a sort of code-switching between MIA varieties we find in dramas and poetry. It seems that mutual unintelligibility is a necessity for language status on Wiktionary, and the individual Prakrits are not meeting that prerequisite--we will be dealing with a ton of entry duplication if we continue with the current structure.
 * One idea is to use something like the the Ashokan Prakrit dialect maps for Prakrit too. But that may be unnecessary given the limited number of Prakrits we are dealing with and the lack of well-organised geographical data for Prakrit. —AryamanA (मुझसे बात करें • योगदान) 04:22, 10 January 2021 (UTC)

 * I also favour a different approach to Prakrit. It would be nice to see and  making more Prakrit contributions that agree with the changed approach.

 * There's a citation for 🇨🇬 122, so that term could be considered verified since this justification was used for creating the Sauraseni entries at Special:WhatLinksHere/Template:R:hi:Misra.

 * Since R:pra:Sheth treats Maharastri as one of most attested lects (alongside Ardhamagadhi), instead of marking (Jain) Maharastri as (J)M as in R:inc:Pischel and R:inc:Woolner, the abbreviations usually refer to a text in which the term was found. For example, the abbreviation for the is गा. This is the entry for :

 * अइक्कम aikkama पुं [अतिक्रम] १ अल्लंघन (गा ३४८) २ व्रत या नियम का आंशिक खण्डन (ठा ३, ४)

 * The citation for the first sense is (गा ३४८), which refers line 348 of the . The Prakrit text for the the is here:

 * https://archive.org/details/dassaptaatakamd00webegoog
 * https://web.archive.org/web/20101110111335/http://www.sub.uni-goettingen.de/ebene_1/fiindolo/gretil/2_prakrt/halsatsu.htm

 * The translation is here:

 * https://books.google.co.in/books?id=wsizcqxoQgsC

 * = विनय-अतिक्रम-आरत.
 * Thus, the first sense for could be verified as a Maharastri term. Kutchkutch (talk) 11:09, 10 January 2021 (UTC)
 * Very good, thanks a lot for sharing the source of quotations! So the following are the proposals:
 * Merging all the Prakrits except Ashokan into the code "Prakrit".
 * Maharashtri and others will be reduced to etymology-only languages.
 * We will also have categories like so using pra will categorize a Prakrit entry as Sauraseni.
 * The descendant sections on Sanskrit entries will follow the existing pattern.
 * Also, as AryamanA said, dialect maps may be unnecessary as we are dealing with just four or five Prakrits, and also, we don't have sufficient geographical data for doing that.
 * Is this fine?-- Bhagadatta(talk) 12:11, 10 January 2021 (UTC)

 * Also, Would the implications of:

 * Proposal 1 be that this change affects languages without the text suffix such as Pali, Gandhari and Helu since they are in CAT:Prakrit languages?

 * Proposal 2 be that the etymology sections of Hindi entries can use text instead of text if that suits the entry better?

 * Proposal 4 be that the descendants section of a unified Prakrit entry such as and  would be a long list?

 * There will need to be a way to indicate dialectal differences in:
 * alternative forms: vs, hiatus-filler form of
 * declension: psu-decl-noun-a-m pmh-decl-noun, pmh-decl-noun-irregular, inc-mgd-decl-noun
 * derived terms: -क → vs, inc-extension
 * references: vs
 * other templates: pmh-g, pmh-verb set, inc-mgd-personal pronouns
 * Jain prefix: CAT:Jain Maharastri
 * AP:Middle Indo-Aryan Swadesh lists

 * CAT:Sauraseni Prakrit romanizations is not needed

 * Many of the names of the Prakrits are geographic, so perhaps a vague shape around the focal point could be of some use:

 * Saurasena, Magadha, Gandhara: c:File:Mahajanapadas (c. 500 BCE).png
 * Maharastri Prakrit: c:File:India 2nd century AD.jpg
 * Kamarupa: File:Kamarupa map.png Kutchkutch (talk) 15:21, 10 January 2021 (UTC)
 * Neither will Pali and Gandhari be affected nor they'll be included in the code "Prakrit" for the following reasons:
 * Pali and Gandhari differ from the Prakrits to the extent that their mutual intelligibility with the Prakrits is affected (this is evident looking at the word forms of Pali vs Prakrit).
 * They both have a long history of their own separate identities; we have a DSAL dictionary dedicated wholly to Pali whereas dictionaries group the Prakrit lects together. The dramas would often have different characters speaking different Prakrits, which would not be the case of they were not mutually intelligible. (But then the same dramas would also feature Sanskrit, so I would not fall back on this point alone).
 * The objective of the proposal is to make citing sources and creating Prakrit entries easier because one won't need to go looking for the exact dialect of a given Pkt. word. It's also to achieve better accuracy in our depiction of the Indo-Aryan family tree (As mentioned above by AryamanA; also to be noted are the similarities between Bengali-Assamese and Marathi-Konkani in spite of the fact that the former descends from Magadhi Prakrit and the latter from Maharashtri). When we are considering this, Pali and Gandhari are unlikely to be affected.
 * For different altforms from different Prakrits, like vs, we can do what has been done at the page : pra and vice versa.
 * Hindi (and other IA) entries CAN use text instead of text, especially in entries where the same form is attested across the Prakrit continuum.
 * What remains unresolved is how to show declension; Magadhi, Maharashtri & Sauraseni seem to have similar declensions, with Magadhi being a bit different. I would suggest, instead of writing a new template/module, what we can do instead is input the existing templates on the entry. We can make a small edit to these templates so that pmh-decl-noun will display something like "Maharastri declension of " at the top and ditto for others. Sure it'll result in multiple tables on (most) pages but they're collapsed by default, so it shouldn't be too much of an issue. I don't know if this is indeed the most desirable course of action.
 * Can't we show the references all together at the end of the page? I don't think it'll matter if a Sauraseni entry has a different reference; under the new Prakrit header, they'll all be shown together.
 * The issue of descendants in Prakrit entries now pops up. It'll certainly be a long list but that in of itself won't be a problem. I'm concerned about how we will categorize them in the descendants now. Anyone got ideas? -- Bhagadatta(talk) 16:21, 10 January 2021 (UTC)

 * For descendants, we would have to start reconstructing  (Sauraseni Apabhramsa) and other apabhramsas. For languages that are directly descended from a Prakrit, say   (Romani), which is directly from Sauraseni, we can use something like   which would give:
 * * (from Sauraseni)
 * Also, sometimes, we may use reconstructed words, but  should do it because it is obvious that Sauraseni Apabhramsa is from Sauraseni Prakrit. 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 03:19, 11 January 2021 (UTC)

 * Thanks for the clarifications. I don't disagree with anything. It's just better to make things as clear as possible before any of them become larger issues.

 * I think what you mean by
 * I don't think it'll matter if a Sauraseni entry has a different reference, under the new Prakrit header, they'll all be shown together.
 * is that if there's no need to make a distinction between the lects then pra (and the corresponding reference for each lect) does not need to be given. However, if there is a reason to make a distinction:

 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra
 * → pra

 * And the Maharastri / Ardhamagadhi verb endings aï / eï can be freely converted to Sauraseni / Magadhi adi / edi.

 * Based on your previous interaction with Inqilābī, if one does go looking for large number of quotations for a single entry, most of them can go on a separate Citations page. However, one or two quotations, could be shown on the entry rather than putting them somewhere where they'll rarely be seen.

 * The text text is from text of MOD:pra-decl/noun. Perhaps it's best to wait until AryamanA has time.

 * If you're not aware of this index for R:inc:Pischel already, hopefully this will be of some use to you:
 * https://jainqq.org/explore/032526/345

 * What to do with Apabhramsas does need to be discussed as soon as possible, but perhaps that discussion should be at CAT:Sauraseni Apabhramsa language.

 * WT:Beer_parlour/2020/September
 * Late MIA (Apabhramsha) is an important stage of I-A. Apabhramsha is often treated it as a single entity rather discrete regional entities because there was a dialect continuum like Ashokan Prakrit. In the bazaar scene of Uddyotana’s Kuvalayamālā c. 779, the narrator quotes small bits of eighteen different languages, some of which sound remarkably similar to the spoken languages of today rather than the Prakrits. Thus, the original names given to the various Apabhramshas (Nagara, Upanagara, Vracada) are like the dots in MOD:inc-ash-dial-map. Most of the Apabhramshas like are known by name only with little information about them.

 * Here are Apabhramsa references that could be looked at in more detail:
 * Historical Grammar Of Apabhramsa:
 * https://archive.org/details/in.ernet.dli.2015.505169
 * The Apabhraṃśa of Svayambhūdeva’s Paümacariu:
 * http://orient.avcr.cz/miranda2/export/sitesavcr/data.avcr.cz/humansci/orient/akce/trest/Apabhramsa-grammar-for-Paumacariu.pdf
 * A Grammar Of Apabhramsa:
 * https://jainqq.org/explore/023436/1 Kutchkutch (talk) 10:45, 11 January 2021 (UTC)
 * Obviously we can have the quotations in the entry. In that case we would just have to mention the lect beside the quote. However, it is not that the citation page is rarely seen, as there’s this templet,, that is used on entries. Yet, given that we will never have a great many Prakrit quotations, let us forget about the citation page. -⸘- inqilābī  ‹inqilāb·zinda·bād› 20:43, 11 January 2021 (UTC)
 * Yes, you're right; if a certain term is common across the Prakrit continuum, then mentioning the lects is only optional. And I agree with you about the quotations; I feel we can allow the editors some discretion with regards to whether or not to include quotations in the same entry.
 * What remains unresolved are MIA extensions, hiatus fillers and declension. In MIA extensions, the entries of New Indo-Aryan languages will not be affected; for instance will still read mr mr. For entries of Prakrit terms with these extension, there will certainly be a problem as the template does not take the codes of etymology only languages. The same goes for hiatus filler too. -- Bhagadatta(talk)  05:37, 12 January 2021 (UTC)

 * Regarding MIA extensions:
 * Wiktionary's coverage of CAT:Indo-Aryan extensions is still its infancy. AryamanA has standardised the Sauraseni outcome of Early MIA as, and I've standardised the Maharastri outcome of Early MIA  as .  suggests that the Ardhamagadhi outcome may be , and according to 209 Jain Maharastri  + Early MIA  → . However, the actual outcomes may not be so standardised. For example, the Sauraseni outcome is  for . Perhaps, a unified Prakrit entry with no lect distinctions lects can standardise one outcome, and Prakrit entries that are not unified can use a more specific outcome.

 * Regarding hiatus-filler form of:
 * The hiatus-filler is only applicable in the environments V_a and V_ā. It is sometimes transliterated as ẏ. In Jain Maharastri and Ardhamagadhi, the insertion of  in these environments appears to be compulsory. Perhaps  is a good example to understand hiatus-filler form of. There are two underlying Maharastri forms:  and . Both underlying forms can have a hiatus-filler form, which leads to four Maharastri forms. 🇨🇬 has a compulsory, and Sauraseni+Magadhi have  instead of a hiatus. Until now, I've preferred having the non-hiatus-filler form as the lemma form for Maharastri. However, for a unified Prakrit lemma, perhaps using the hiatus-filler form is more inclusive of Jain Maharastri and Ardhamagadhi. Also, MOD:pra-decl/noun produces errors word-finally (see , , Module_talk:pra-decl/noun).

 * Regarding declension:
 * Changing text of MOD:pra-decl/noun to
 * produces
 * text
 * text
 * so it could be a temporary solution before the merger.
 * Changing this text
 * text
 * at T:pmh-decl-noun-irregular is relatively simpler.
 * The data module for regular Magadhi declension is at: MOD:pra-decl/noun/inc-mgd
 * The data module for regular Maharastri declension is at: MOD:pra-decl/noun/pmh
 * Data modules for regular Sauraseni and Ardhamagadhi declension have not been created yet.
 * There is a template for romanised masculine a-stem Sauraseni declension at T:psu-decl-noun-a-m. Kutchkutch (talk) 11:37, 12 January 2021 (UTC)
 * There is a template for romanised masculine a-stem Sauraseni declension at T:psu-decl-noun-a-m. Kutchkutch (talk) 11:37, 12 January 2021 (UTC)

OK, that's fair enough for a blueprint. So if I've got it right, we want the module to produce multiple tables for a single input as opposed to a single table that shows the different forms of different Prakrits. That's fine, it'll look good and more organized.
 * What do you think about how to list the descendants? Should we organize them by Sauraseni, Maharashtri etc or follow Wikipedia's model and list these dialects by families and subfamilies (Like Western, Central, Southern etc) instead of which MIA dialect they come from?
 * On one hand I think it would sort of defeat the purpose if we will again sort the descendants as Sauraseni, Maharashtri etc. As AryamanA pointed out, Gujarati is closer to Maharashtri descended Marathi than to Sauraseni descended Hindi. There are many more such cases so in my opinion we can better show the family tree if we follow Wikipedia's model. This is because we will no longer need to write Sauraseni, Maharashtri etc in the descendants if we already have pra under the noun header.
 * But on the other hand if we do that then we will need to integrate Paisaci and Khasa into the header Prakrit in order to include Nepali, Punjabi and Sindhi. -- Bhagadatta(talk) 04:50, 13 January 2021 (UTC)

 * Ok, we'll include Paisaci and Khasa Prakrits into it also. For descendants, I'd prefer they be organised according to which Middle Indo-Aryan dialect they derive from. I don't find any problem if we still have  in etymology section of Hindi entries and descendants sections of Sanskrit entries. As I suggested earlier, we may use   beside the descendant, if something is unclear, even if we already have pra. We obviously don't need that if the descendant is something like . 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 05:13, 13 January 2021 (UTC)

 * It is true that
 * It would sort of defeat the purpose if we will again sort the descendants as Sauraseni, Maharashtri etc.

 * given that the tree model is not entirely suitable for Indo-Aryan and there may several differences between the attested Prakrits and what may have actually been spoken. This is the style used at RC:Ashokan Prakrit/𑀙𑁄𑀝𑁆𑀝. There are etymologies are better characterised as being a result of 'historical mixing' with the CAT:Central Indo-Aryan languages rather than being borrowed from Modern Standard Hindi.

 * Instead of showing these words as borrowed from Modern Standard Hindi, it would be more accurate to show their relation to CAT:Central Indo-Aryan languages rather than Modern Standard Hindi. The  in Marathi words like  and  may have been  if they had been inherited normally.

 * At Talk:आहे, AryamanA noted:
 * Areal influence has created many interesting parallels across the subcontinent.
 * It has been frequently noted that Indo-Aryan is part of a with several s that are not descended from a common ancestor language.

 * This is all indicative of
 * There are many more such cases so in my opinion we can better show the family tree if we follow Wikipedia's model.

 * However, as User:शब्दशोधक has pointed out, when the tree model works, it might be fine to sort the descendants as Sauraseni, Maharashtri etc. Just like how there's flexibility regarding unified Prakrit entries vs Prakrit entries for different lects, perhaps there can be flexibility regarding whether to sort by subfamilies or by Prakrit lect on a case-by-case basis.

 * Integrating Paisaci and Khasa is fine. Kutchkutch (talk) 10:55, 13 January 2021 (UTC)
 * So what would happen with the various Apabhramsas in this organisation? Does it make sense to merge theme as well, or are their literary traditions sufficiently independent to retain separately? I believed DerekWinters asked for Gurjar Ap. separately from Sauraseni Ap. because he found them different enough to be considered different languages. But in the case of Vrachada and Takka, we have extremely limited attestation so their existence is suspect; I only really added those codes as pseudo-proto-languages for the diverging Paisachi subfamilies of Sindhi and Punjabi-Lahnda. —AryamanA (मुझसे बात करें • योगदान) 00:38, 14 January 2021 (UTC)

 * I think we can keep them separate, but we won't create reconstructed entries for them. We'll keep them in Descendants and etymology sections as hi, without linking it to the entry. 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 06:11, 14 January 2021 (UTC)

 * See this paper:
 * The Classification of Apabhraṃśa―A Corpus-based Approach of the Study of Middle Indo-Aryan by Tomoyuki YAMAHATA at
 * https://books.google.co.in/books?id=WMd9QM9ixRUC&pg=PA223
 * The paper suggests that it would make sense to merge the Apabhramsas as well unless further research indicates otherwise. Here are some excerpts:

 * 17
 * The groups and the desinences show a more complicated relationship than was expected.

 * 227
 * We will examine various classifications of Apabhraṃśa. We divide the classifications into four types corresponding to the medieval grammarians, Jacobi and Tagare

 * 228
 * It is known that five medieval grammarians are important for investigating Apabhraṃśa variances—Hemacandra, Kramadīśvara, Puruṣottama, Rāmaśarman, and Mārkaṇḍeya. [Other than Hemacandra] the other four grammarians prescribed the grammar of only three subcategories, Nāgara, Upanāgara, and Vrācaḍa. They treated Nāgara as a basic Apabhraṃśa and explained the others by describing differences with Nāgara. Their descriptions, however, are not always applicable to the Apabhraṃśa seen in existing documents. Moreover it is difficult to find a diachronic relations in the Indian classical texts these texts supply little information about historical relation of Apabhraṃśa languages.

 * 229-230
 * [Jacobi] found some differences between [two Apabhraṃśa texts], so he named the former northern Apabhraṃśa (NAp) and the latter Gurjara Apabhraṃśa (GAp) Alsdorf showed differences between these two types of Apabhraṃśa  GAp has considerably many borrowed words and desinences from Sanskrit and Prakrit languages, unlike NAp.  [Tagare] classified Apabhraṃśa documents distributed over north India into Eastern Apabhraṃśa (EAp) of Bengal, Western Apabhraṃśa (WAp) of Gujarat and Rajasthan, and Southern Apabhraṃśa (SAp) of Maharashtra. We will show the differences among them as indicated by Tagare.

 * 232
 * In the classification of Tagare, WAp and SAp are not so different, whereas he assumed EAp comparatively distant from others It is difficult to find systematic differences among the Apabhraṃśa languages. In addition, it is obscure whether the languages described on these classifications have any relation to NIA languages  Dolci pointed out, ‘Prakrit grammarians classified the languages not by linguistical characteristics, but by literal usages.’  Hence, the classifications are not explanations of linguistic characteristics of Apabhraṃśa. Jacobi suggested that there were regional differences among the Apabhraṃśa texts. However, there were not enough edited texts for an analysis of the differences. Tagare made use of many edited texts, and he classified them into three varieties of Apabhraṃśa, which are Eastern, Western, and Southern. Because there are considerable differences among them regarding the phonology and morphology, it is valid that he classifies them in this way. However, it is unclear why such differences exist.
 * I do not accept that ‘Apabhraṃśa languages’ as local languages that correspond to NIA languages, but as a literal language that originated from a region like Mahārāṣṭrī, and so on, because differences among the Apabhraṃśa categories put forth by Tagare do not correspond to differences among NIA languages.

 * 233
 * This study examines variations of texts written in Apabhraṃśa. The corpus consists of eight texts:
 * Eastern Apabhraṃśa (EAp.): Dohākoṣa of Kāṇha, Dohākoṣa of Saraha
 * Southern Apabhraṃśa (SAp.): Paumacariu, Hariseṇacariu
 * Western Apabhraṃśa (WAp.): Sanatkumāracarita, Vikaramorvaśīya, Tantrasāra, Āgamadambara
 * Kashmiri Apabhraṃśa (KAp.): Tantrasāra

 * 238
 * There is no proof that these variations of Apabhraṃśa have relation to the NIA languages of each region Therefore it is supposed in this paper that all of four Apabhraṃśa groups are originated from a MIA language that was probably spoken at Rajasthan or Gujarat in the western India. Because the western India brought forth copious texts of Apabhraṃśa  Hence we can assume this language prevailed over north India as a literal language temporally  [There is insufficient evidence for the subclassification of Apabhraṃśas].

 * Perhaps DerekWinters' request was based on this statement on page 229:
 * [Jacobi] found some differences between [two Apabhraṃśa texts], so he named the former northern Apabhraṃśa (NAp) and the latter Gurjara Apabhraṃśa (GAp) Alsdorf showed differences between these two types of Apabhraṃśa  GAp has considerably many borrowed words and desinences from Sanskrit and Prakrit languages, unlike NAp.  Kutchkutch (talk) 09:23, 14 January 2021 (UTC)

 * What's the conclusion of this discussion? Are we actually going to make some changes or we're just continuing as it is - R:CDIAL and R:pra:Sheth are by default and there's no real need for Sauraseni Prakrit entries? 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 16:49, 17 January 2021 (UTC)
 * Both AryamanA and Bhagadatta haven't been active for a few days, so they must be busy with other activities. Implementing the changes that are being discussed will require input from everyone, so we'll just have to wait until they have time to resume the discussion. While the discussion is stalled, we can continue as it is. Kutchkutch (talk) 08:44, 18 January 2021 (UTC)

 * Yeah, we can wait for some time. But I'm not gonna create any entry for Prakrits until we reach any conclusion. 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 16:56, 18 January 2021 (UTC)

Conclusion
OK, so we have agreed so far to incorporate the Apabhranshas and the ancestors of Nepali, Punjabi etc and possibly Elu. How do we deal with situations where the Paisaci/Elu/Khasa term is not available (Because they are almost never available)? So which Prakrit lemma will the Punjabi descendants be shown on? For instance- what Prakrit entry will have listed as a descendant? What we can do is assume Paisaci for a Prakrit lemma in spite of not having the Paisaci attestation at hand or we can create the Prakrit entry, mark it as Sauraseni, Maharashtri etc and show only Hindi, Marathi etc and show Punjabi at the actual Sanskrit page. So if we follow the first method, then will be shown as a descendant of 𑀪𑁃𑀡𑀻 or 𑀪𑀇𑀡𑀺. If it's the second method, then the Punjabi term will be directly at. As for Apabhranshas, I do not mind incorporating them too, but the question now is, how will the etymologies be shown? Right now we say a Sauraseni Apabhransha term is from Sauraseni Prakrit; with both of these lects being Prakrit now, it will result in a Prakrit lemma linking to another Prakrit lemma. It is true that on the surface it will still say "from Sauraseni Prakrit" because of text continuing as an etymology only language but it will still result in a lemma, with the L2 header "Prakrit", saying that it is derived from Sauraseni Prakrit. A possible solution to this would be to use "From an earlier ". Once we have worked out what to do in the above two cases, it is a Go ahead from me and I merging the different Prakrit and Apabhransha lects under a single code. -- Bhagadatta(talk) 06:00, 19 January 2021 (UTC)

 * I feel we do not need to merge Apabhramsas with Prakrit and neither do we need Apabhramsa entries - they should be in etymologies of entries with  in order to show how words changed over time. No need to link them also. For attested Apabhramsa terms also, we'd not link them with their entries. Not adding apabhramsa entries would reduce the work of Middle-Indo-Aryan editors. For the descendants thing - I think first method is better (assuming Paisaci term if there is is a Punjabi term which has been most probably inherited from it) than directly showing Punjabi terms in the descendants section of a Sanskrit entry.  🔥 𑀤𑁆𑀯𑀺𑀰𑀓𑀸𑀭 🔥 06:28, 19 January 2021 (UTC)

 * Regarding Apabhramsa:
 * When AryamanA asked:
 * So what would happen with the various Apabhramsas in this organisation? Does it make sense to merge theme as well...I believed DerekWinters asked for Gurjar Ap. separately from Sauraseni Ap. because he found them different enough to be considered different languages.
 * I thought he was referring the possible merger of CAT:Sauraseni Apabhramsa language, CAT:Gurjar Apabhramsa language etc. as 'Apabhramsa' by analogy with the Prakrit merger. Although it says at :
 * some scholars use the term [Prakrit] for the entire Middle Indo-Aryan period
 * Apabhramsa appears to be a separate stage from Prakrit (see Talk:قنبيل). The paper above claims that since all Apabhramsa texts are based on late MIA lects spoken in Rajasthan and Gujarat there is not enough evidence to subclassify Apabhramsa as 'Gurjar Apabhramsa' 'Sauraseni Apabhramsa' etc.
 * Where I disagree with शब्दशोधक regarding Apabhramsa is:
 * not being able have links to attested Aprabramsha terms in etymology/descendants sections
 * we do not need Apabhramsa entries...not adding Apabhramsa entries would reduce the work of Middle-Indo-Aryan editors
 * I think what शब्दशोधक means by 'not having Apabhramsa entries' is that improving coverage of Apabhramsa can wait until there is more coverage of Prakrit.
 * I think what शब्दशोधक means by 'not having Apabhramsa entries' is that improving coverage of Apabhramsa can wait until there is more coverage of Prakrit.

 * Regarding Paisaci/Elu/Khasa:
 * For Prakrit entries that are unified, the [Paisaci/Elu/Khasa] term could be assumed to exist as well. For Prakrit entries that distinguish lects, perhaps it would be better to put the [Punjabi/Sinhala/Nepali etc.] term at the Sanskrit entry for until our understanding about [Paisaci/Elu/Khasa] has improved. Kutchkutch (talk) 10:29, 19 January 2021 (UTC)

 * Yeah, I don't exactly mean that we should never have Apabhramsa entries, but just that right now, at least, we should focus on improving the coverage of Prakrits. But still, I am not supporting mixing Apabhramsas with Prakrits - that'll create confusion. 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 11:20, 19 January 2021 (UTC)
 * Oh I thought we were considering merging Apabhransha and Prakrit. I agree that merging the Apabhranshas into one is also a good idea.
 * And I support the suggested solution of assuming Paisaci et al only for Prakrit terms that are the same across the continuum; so will be under a Prakrit 𑀧𑀺𑀉 but  will in the descendants section of its Sanskrit ancestor's entry. -- Bhagadatta(talk)  13:47, 19 January 2021 (UTC)
 * Since there are no CAT:Helu language entries yet, I created User:Kutchkutch/elu-prk. Kutchkutch (talk) 10:53, 20 January 2021 (UTC)
 * Yeah, I am also against merging Apabhramsa into Prakrit. It seems merging Elu => Prakrit makes sense. I am for placing descendants under Prakrit entries even if we don't have the exact form (e.g. in Paisaci) attested, because of the little variation between Prakrits. We could also reference unlinked reconstructions if an ancestor doesn't match up exactly. —AryamanA (मुझसे बात करें • योगदान) 15:42, 20 January 2021 (UTC)

 * Is the conclusion merging all the different Prakrits into one and we'll use labels like pra to put them specifically into categories like on labelling sa, the word is categorised into CAT:Vedic Sanskrit? I am supporting such a change. As for the Apabhramsas, I say again that we'll think about this later, let them be separate - and . We can, obviously, have some discussion on merging them as well later on, and as it is, we aren't really creating a lot of Apabhramsa entries right now, which is also one of the reasons for stalling it and thinking of it later on. Anyways, how are we going to implement this? Will that require changing all Maharashtri Prakrit and Sauraseni headings to simply Prakrit?  🔥 शब्दशोधक 🔥 17:14, 24 January 2021 (UTC)
 * I am of opinion that even while merging all Prakrits under a single language header, we can preserve the status quo of our etymologies and descendants. That means, for example, in the Etymology section, a Punjabi/Sinhala/Nepali word will be shown to be descended from a Paisaci/Elu/Khasa term, which in turn be shown to be from our unified Prakrit term, to enable proper categorization; and in the Descendants section, a Punjabi/Sinhala/Nepali descendant will be put beneath a Paisaci/Elu/Khasa term, which in turn be beneath our unified Prakrit term. If the particular dialectal Prakrit term be attested, we can provide it, and if not, we can keep it empty (or later maybe even reconstruct it?). (Also informing about this development, who has created Kamarupi Prakrit entries.)
 * As for Apabhramsas, we may as well conveniently consider them as part of the earliest NIA stage (i.e., including them under the languages of Old Hindi, Old Marathi, Old Bengali, etc.). -⸘- inqilābī  ‹inqilāb·zinda·bād› 18:04, 24 January 2021 (UTC)

 * Kamarupi Prakrit is mostly an Apabhramsa for attested vocabulary. Msasag (talk) 19:22, 24 January 2021 (UTC)
 * Then why is it called a Prakrit? Should it not be called “Kamarupi Apabhramsa”? -⸘- inqilābī  ‹inqilāb·zinda·bād› 19:07, 25 January 2021 (UTC)

Wait, so you mean that Prakrit will be kind of similar to Ashokan Prakrit, in which, under, we'll have something like:
 * and so on ? 🔥 शब्दशोधक 🔥 03:29, 25 January 2021 (UTC)
 * Yea, you got me. -⸘- inqilābī  ‹inqilāb·zinda·bād› 19:07, 25 January 2021 (UTC)

 * Regarding implementation:

 * This might be obvious, but just as a reminder:
 * We have to be careful about exactly how we implement the merger because an inefficient manner could lead to to widespread issues.
 * User:Aryamanbot could possibly change the language headers from text to text, but if the entry is not unified, but pra would have to be added manually.

 * Regarding Apabhramsa:
 * It's true that no one's creating a large quantity Apabhramsa entries, so deciding what to do with Apabhramsa is less of a priority compared to Prakrit.

 * User:Msasag's statement suggests that Kamarupi may be an Apabhramsa rather than a Prakrit, so without additional data it could possibly remain separate from text. Your suggestion would prevent the potential inconsistencies that would be caused by too much flexibility. The Prakrit tree with Assamese would look like this:

 * Prakrit: [Term?]
 * Prakrit: [Term?]

 * with four instances of ʻPrakritʼ preceding Assamese and a large quantity of: [Term?].

 * The difference between this and Ashokan Prakrit is that each of the Ashokan Prakrit lects don't have individual codes (which was discussed here: User_talk:DerekWinters). Kutchkutch (talk) 10:51, 25 January 2021 (UTC)

 * Oh wait, we will have to fix something else also - this change will not be possible if the language code  is an etymology only language code. If we have Prakrit entries, we should be able to use pra and pra.  🔥 शब्दशोधक 🔥 13:31, 25 January 2021 (UTC)
 * When Prakrit gets finally unified, then  is obviously going to get its new status implemented. Our discussion is still ongoing. -⸘-  inqilābī  ‹inqilāb·zinda·bād› 19:07, 25 January 2021 (UTC)
 * The display of [Term?] is no issue inasmuch as these can be hidden using ; in fact, this is how we need to deal with unattested dialectal Prakrit terms so as not to make the page ugly. -⸘- inqilābī  ‹inqilāb·zinda·bād› 19:07, 25 January 2021 (UTC)
 * Sure thing; I agree. We can keep the status quo in the descendant sections. -- Bhagadatta(talk) 00:40, 26 January 2021 (UTC)

 * Yes Kamarupi Apabhramsa is a better term. Msasag (talk) 10:20, 26 January 2021 (UTC)
 * Speaking of bot implementation, User:Aryamanbot will be able to handle the merger. I'll parse the definitions from each entry on the page and merge identical definitions. Each definition will have appropriate tags based on the languages it was originally present in. There will likely be some manual cleanup required. —AryamanA (मुझसे बात करें • योगदान) 15:15, 26 January 2021 (UTC)

Implementation
The implementation would include:
 * 1) Changing L2 headings from " Prakrit" to simply "Prakrit".
 * 2) Making the language code   fully-fledged for templates like pra and pra to work. (I haven't got a clue how to do this)
 * 3) Merging Sauraseni, Maharashtri, Magadhi, Paisaci, Khasa, Helu (Elu doesn't seem to be a descendant of Ashokan Prakrit, so should we?) and not Ashokan and Kamarupi (we will deal with Kamarupi Apabhramsa vs Prakrit later).
 * 4) Using pra for categorising by lect.
 * 5) Arranging descendants under "Prakrit" by lects.
 * 6) Not changing the etymologies of descendants of Prakrit from " Prakrit" to "Prakrit".
 * 7) Making Prakrit declension templates show the name of the lect on top.
 * Anything else? 🔥 शब्दशोधक 🔥 03:40, 27 January 2021 (UTC)

 * Perhaps Aryamanbot will be able to make the necessary changes in accordance with the new arrangement defined at CAT:Language data modules, MOD:families/data, MOD:etymology languages/data, etc for  to be a fully-fledged code.
 * Perhaps Aryamanbot will be able to make the necessary changes in accordance with the new arrangement defined at CAT:Language data modules, MOD:families/data, MOD:etymology languages/data, etc for  to be a fully-fledged code.

 * Analyses of Helu Prakrit suggest that it is descended from speakers of Ashokan Prakrit that migrated from the mainland. Since we have no data on Khasa Prakrit, its status is the most unclear.
 * The labels are managed here: MOD:labels/data/subvarieties. text already has a label.

 * text would include the templates, categories and appendices mentioned above. Kutchkutch (talk) 09:49, 27 January 2021 (UTC)
 * Okay, so that's good, if Aryamanbot will be able to do that. Also, will the language codes of other Prakrits be reduced to etymology-only codes? 🔥 शब्दशोधक 🔥 13:39, 27 January 2021 (UTC)

 * There’s a basic guide at Help:Adding and removing languages. My understanding is that text will first become a full-fledged language, all entries belonging to  will move to that language using the algorithm outlined above using the bot, and after the cleanup, the language codes of other Prakrits will become etymology-only. Kutchkutch (talk) 18:48, 27 January 2021 (UTC)

 * If everything is clear and we know what has to be done and all are supporting this change, then I guess can go ahead and make the required changes with his bot. 🔥 शब्दशोधक 🔥 16:23, 3 February 2021 (UTC)
 * ? 🔥 शब्दशोधक 🔥 05:55, 8 February 2021 (UTC)

Merging of Prakrits to a single language header *should* absolutely go to a vote. -- 06:14, 15 March 2021 (UTC)
 * AryamanA seems very busy, which is why we have been stuck here since about 2 months. We all here feel the same way so why wait? 🔥 शब्दशोधक 🔥 06:27, 15 March 2021 (UTC)
 * You few aren't the only people who work in PIA and a big change like that deserves more eyes and a vote. -- 06:34, 15 March 2021 (UTC)
 * As a matter of fact, this is just about the Prakrits of MIA not PIA. And it does seem like we few people are the only ones who are currently working on improving the coverage of Prakrits. 🔥 शब्दशोधक 🔥 07:33, 15 March 2021 (UTC)
 * Obviously. I was speaking of people that work in that family. -- 07:35, 15 March 2021 (UTC)
 * It won't change much (or anything at all) for them. A Hindi editor would still use hi and the current Sanskrit editors are just us all who are aware of the new descendants' style. 🔥 शब्दशोधक 🔥 08:49, 15 March 2021 (UTC)
 * I'll repeat, such a change requires a vote. -- 08:53, 15 March 2021 (UTC)
 * 🔥 शब्दशोधक 🔥 09:14, 15 March 2021 (UTC)
 * Great, but then don't go asking Benwing to create a code for you. -- 09:17, 15 March 2021 (UTC)

If wouldn't have been so busy, this change would've taken effect till now. Since that doesn't seem possible now, I am asking for help. Now also says that we should have a vote, so I'm fine with it. But I don't know how to do so. 🔥 शब्दशोधक 🔥 10:04, 15 March 2021 (UTC)
 * See Help:Creating a vote. Kutchkutch (talk) 10:19, 15 March 2021 (UTC)
 * : WT:Votes/2021-03/Merging Prakrit lects into one - Here's the vote. Please help improve its description. 🔥 शब्दशोधक 🔥 10:46, 15 March 2021 (UTC)

Bot runs

 * Can User:WingerBot do this merger? AryamanA seems to be busy (50 > edits this month by him), so this isn't getting implemented. Your help would be appreciated. Thanks. 🔥 शब्दशोधक 🔥 08:38, 27 February 2021 (UTC)
 * This looks to be a lot of work. I may be able to get to it but I can't guarantee anything right now. Benwing2 (talk) 08:04, 1 March 2021 (UTC)
 * No worries. 🔥 शब्दशोधक 🔥 08:08, 1 March 2021 (UTC)

Descendants
Is it ok to have a Punjabi and Nepali descendant under Sauraseni Prakrit, which I see in so many Sanskrit and entries - like मुष्टि? 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 17:10, 12 January 2021 (UTC)

 * That was the style used before WT:Beer_parlour/2020/September. Now, Nepali is under CAT:Khasa Prakrit language, and Punjabi is under CAT:Takka Apabhramsa language, which is under CAT:Paisaci Prakrit language. Kutchkutch (talk) 17:19, 12 January 2021 (UTC)

 * Ok, so I'll replace it wherever I see so. 🔥 𑀰𑀩𑁆𑀤𑀰𑁄𑀥𑀓 🔥 17:22, 12 January 2021 (UTC)

 * Yes, please do so. Kutchkutch (talk) 17:44, 12 January 2021 (UTC)

Late Brahmi variants
Hello! I am a fairly new user on Wiktionary and directed me here for questions I might have about Prakrit entries. My issue is that I want, if possible, to create entries for some terms in Kushan and Gupta Brahmi, which are not Unicode-encoded, and I'd like to know how to do that. Antiquistik (talk) 20:52, 7 April 2021 (UTC)

 * Here, on Wiktionary, I think you should use the Ashokan Brahmi only for any entry in Brahmi script. Even there is an uttara Devanagari which has some differences from the Devanagari we have. For example अ of uttara Devanagari looks like [[File:Devanagari a old.svg]]. Earlier Sanskrit was written in it. Even Monier-Williams uses it in his dictionary. But we don't use that and only have Devanagari. 🔥 शब्दशोधक 🔥 05:54, 8 April 2021 (UTC)

 * Thanks. Antiquistik (talk) 10:20, 8 April 2021 (UTC)

Renaming
I propose that this cat be moved to CAT:Middle Indo-Aryan languages, similar to CAT:Old Indo-Aryan languages, especially since "Prakrit" is now also a language. Then perhaps can be changed to. Also, can anyone explain the point of CAT:Sauraseni Prakrit languages? 🔥 शब्दशोधक 🔥 06:40, 16 July 2021 (UTC)

 * 'Prakrit languages' ≠ 'Middle Indo-Aryan languages'. 'Prakrit languages' is a subset of 'Middle Indo-Aryan languages' with the exclusion of Apabhraṃśas (late Middle Indo-Aryan). Therefore, the proposed action would have to replace the current category with a differently defined category containing even more languages. Instead of deleting 'Prakrit languages', should a superset category 'Middle Indo-Aryan languages' be created instead?

 * 'Sauraseni Prakrit languages' was probably created as a result of User_talk:Victar so that 'Pahari languages' is not placed under 'Old Indo-Aryan languages'. However, now it only serves to group 'Romani languages', 'Central Indo-Aryan languages ' and 'Western Indo-Aryan languages' into a single category. Kutchkutch (talk) 07:44, 16 July 2021 (UTC)

 * Then let the proposed action [be] to replace the current category with a differently defined category containing [all languages of Middle Indo-Aryan stage]. Can we get rid of CAT:Sauraseni Prakrit languages? 🔥 शब्दशोधक 🔥 16:25, 16 July 2021 (UTC)

 * 🔥 शब्दशोधक 🔥 05:01, 18 July 2021 (UTC)
 * I agree with removing CAT:Sauraseni Prakrit languages since text is misleading. All the categories within Category:Terms derived from Sauraseni Prakrit languages would have to be deleted.

 * Are there any MIA languages besides Category:Gurjar Apabhramsa language and Category:Sauraseni Apabhramsa language that are not in Category:Prakrit languages. Kutchkutch (talk) 13:14, 22 July 2021 (UTC)

 * CAT:Vracada Apabhramsa language, CAT:Takka Apabhramsa language 🔥 शब्दशोधक 🔥 13:57, 22 July 2021 (UTC)
 * What about "New Indo-Aryan languages" category, for the placement of some other categories in Sauraseni Prakrit languages cat? Svārtava2 • 10:02, 22 August 2021 (UTC)

Since there are numerous "New Indo-Aryan languages" compared to MIA, this category may require some additional planning. Kutchkutch (talk)
 * ok. How about I list them? —Svārtava2 • 13:36, 6 September 2021 (UTC)

title: Category talk:Prakrit languages


text:
User:Asierog

__NOINDEX__

es:Usuario:Asierog eu:Lankide:Asierog fr:Utilisateur:Asierog

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

title: User:Asierog


text:
mazturība

Etymology
From.

Noun

 * 1) poverty, indigence the state of one who has little or no possessions, little or no money

title: mazturība


text:
cosmagrafaíocht

Etymology
From +. .

Noun

 * 1) cosmography

title: cosmagrafaíocht


text: mazturības

title: mazturības


text: mazturībā

title: mazturībā


text: mazturību

title: mazturību


text:
drôt

Etymology
.

Noun

 * 1) wire thin thread of metal

title: drôt


text: mazturībai

title: mazturībai


text: backvelds

title: backvelds


text:
cealgaire

Etymology
From. .

Noun

 * 1) guileful person; beguiler, deceiver

title: cealgaire


text:
backvelder

Noun

 * 1) A native or inhabitant of the backveld.

title: backvelder


text: backvelders

title: backvelders


text:
horribleté

Noun

 * 1) horribleness

title: horribleté


text:
Talk:burnt

What about burnt as an adjective - "burnt toast", "burnt ocher"? KaryAnca (talk) 19:47, 16 March 2013 (UTC)
 * Participles are often used that way- think of constructions like "half-eaten toast". That doesn't make them adjectives. Chuck Entz (talk) 22:38, 16 March 2013 (UTC)
 * I think this would meet some tests for being a true adjective: modification by "too" and "very", use in "more burnt than" as a comparative, coordination with adjectives. DCDuring TALK 14:01, 3 April 2013 (UTC)

title: Talk:burnt


text: meagred

title: meagred


text: meagring

title: meagring


text: meagered

title: meagered


text: meagering

title: meagering


text: meagers

title: meagers


text:
Vatican City State

Translations

 * Arabic: دولة مدينة الفاتيكان
 * Armenian: Վատիկան Քաղաք-Պետություն
 * Azerbaijani: Vatikan Şəhər Dövləti
 * Belarusian: Дзяржава-горад Ватыкан
 * Bulgarian: Държава град Ватикан
 * Catalan: Estat de la Ciutat del Vaticà
 * Chinese:
 * Mandarin: 梵蒂岡城國
 * Czech:
 * Danish:
 * Dutch: Staat Vaticaanstad
 * Esperanto: Vatikanurbo aŭ Vatikano
 * Estonian: Vatikani Linnriik
 * French:
 * Georgian: ქალაქი-სახელმწიფო ვატიკანი
 * German:
 * Greek: Κράτος της Πόλης του Βατικανού
 * Hebrew: מְדִינַת קִרְײַת הָװַתִיקָן
 * Hungarian: Vatikánvárosi Állam
 * Indonesian: Negara Kota Vatikan
 * Irish: Stát Chathair na Vatacáine
 * Italian: Stato della Città del Vaticano
 * Japanese:
 * Korean: ^바티칸 시국
 * Latin: Status Civitatis Vaticanæ
 * Latvian: Vatikāna Pilsētvalsts
 * Lithuanian: Vatikano Miesto Valstybė
 * Macedonian: Ватикански Град
 * Malay: Negara Kota Vatican
 * Maltese: Stat tal-Belt tal-Vatikan
 * Norwegian:
 * Persian: دولت‌شهر واتیکان
 * Polish:
 * Portuguese: Estado da Cidade do Vaticano
 * Romanian: Statul Cetății Vaticanului
 * Russian: Государство-город Ватикан
 * Serbo-Croatian:
 * Cyrillic: Град-држава Ватикан
 * Latin: Grad-država Vatikan
 * Slovak: Vatikánsky mestský štát
 * Slovene: Vatikanska mestna država
 * Spanish: Estado de la Ciudad del Vaticano
 * Swedish:
 * Thai:
 * Turkish:
 * Ukrainian: Держава-Місто Ватикан
 * Vietnamese: Thành quốc Vatican

title: Vatican City State


text:
bring over

Verb

 * I'll bring over some sandwiches to the school.
 * 1)  To cause to change allegiance or point of view.
 * 1)  To cause to change allegiance or point of view.

title: bring over


text:
جهانگیر

Etymology
From.

Adjective

 * 1) world-conquering
 * 2) prevailing throughout the entire world

Noun

 * 1) world-conqueror

Proper noun

 * , Mughal emperor (lived 1569—1627, r. 1605—1627)
 * , Mughal emperor (lived 1569—1627, r. 1605—1627)

title: جهانگیر


text:
criostal

Etymology
From, from , from , from , from ,.

Noun

 * 1) crystal array of atoms; mineral; glassware

title: criostal


text: Category:en:Vatican City

title: Category:en:Vatican City


text: Category:Vatican City

title: Category:Vatican City


text:
جهانگیری

Etymology
From.

Proper noun

 * , Jahangiri

title: جهانگیری


text:
بهاری

Etymology
From.

Adjective

 * 1) vernal, pertaining to spring

title: بهاری


text: carpalia

title: carpalia


text:
سفارت‌خانه

Etymology
A compound of 🇰🇲.

Noun

 * 1) embassy, the official residence of an ambassador

Etymology
From.

Noun

 * 1) embassy

title: سفارت‌خانه


text: elçin

title: elçin


text: elçim

title: elçim


text: elçisi

title: elçisi


text: elçiyi

title: elçiyi


text: Wörterbüchern

title: Wörterbüchern


text:
elçi

Etymology
From.

Noun

 * 1) one who goes to an unmarried woman's house in order to ask her parents for her hand on a close relative's behalf
 * 2) envoy
 * 3)  ambassador
 * 4) representative, delegate
 * 5) messenger, someone who brings good news
 * 1) messenger, someone who brings good news
 * 1) messenger, someone who brings good news

Etymology
From, equivalent to +. Cognate with 🇨🇬.

Noun

 * 1) ambassador
 * 2) delegate
 * 3) envoy
 * 4) legate
 * 5) messenger
 * 6)  minister
 * 7) prophet

title: elçi


text: Wörterbuche

title: Wörterbuche


text: elçiler

title: elçiler


text:
elçiye zeval olmaz

Etymology
Literally “for the ambassador no doom exists”. Compare 🇨🇬.

Proverb

 * 1)  the bearer of bad news should not be held accountable for the bad news

title: elçiye zeval olmaz


text:
безграничный

Adjective

 * 1) infinite, boundless, limitless

title: безграничный


text: elçiye

title: elçiye


text:
Üllo

Etymology
From pre-Christian, cognate with 🇨🇬, latinised as in the. Revived through 19th-century literature and by folk etymology associated with and.

title: Üllo


text:
Vatikāns

Etymology
A translation of 🇨🇬, itself translated from 🇨🇬, referring to the Vatican Hill where the Vatican City is located. The name of the hill is believed to come from 🇨🇬, apparently because there were prophets in that area. It is also possible, though, that comes from a presumable nearby Etruscan settlement, possibly called Vatica or Vaticum.

Proper noun

 * 1) the Vatican; the Holy See
 * 1) the Vatican; the Holy See

title: Vatikāns


text:
Nigul

Etymology
From Swedish/Old Swedish, from the saint's name , ultimately from.

title: Nigul


text: Category:lv:Vatican City

title: Category:lv:Vatican City


text:
Nigulas

Etymology
From Swedish/Old Swedish, from the saint's name , ultimately from.

title: Nigulas


text:
тату

Etymology 1
.

Noun

 * 1) tattoo an image made in the skin with ink and a needle

Etymology
From. Cognate with 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, 🇨🇬, /, etc.

Adjective

 * 1) sweet

Etymology 1
.

Noun

 * 1) tattoo an image made in the skin with ink and a needle

title: тату


text: elçinin

title: elçinin


text:
cripteagrafaíocht

Etymology
From.

Noun

 * 1) cryptography

title: cripteagrafaíocht


text:
Mihaela

Proper noun

 * 1) Michaela;

title: Mihaela


text:
cripti-

Etymology
From.

Prefix

 * 1) crypto-

title: cripti-


text:
Aussprachewörterbuch

Etymology
From. Akin to 🇨🇬.

Noun

 * 1) pronunciation dictionary

title: Aussprachewörterbuch


text:
Talk:woo woo

Finnegans Wake
Joyce uses the word "woo-woo" in Finnegans Wake, p. 36: "I am woo-woo willing to take my stand, sir, upon the monument," etc. I don't know what it means in this case. Maybe just referring to the tribal scream "woo-woo"? W.D. Sparling (talk) 20:54, 16 March 2013 (UTC)
 * Joyce can be pretty annoying sometimes. It could be an ad hoc onomatopoeic intensifier, a way to indicate stuttering or a sudden impediment of fluid speech, or just one of his countless nonce words. —Μετάknowledge discuss/deeds 21:01, 16 March 2013 (UTC)

Etymology
I always though that it's meant to represent a mocking ghost sound. Like in: 92.99.182.24 16:33, 2 January 2014 (UTC)
 * Person A: I think I saw a ghost
 * Person B: A ghost? Woooooowooooo!!!!

 * The ghost sound is usually whoo. Equinox ◑ 23:54, 17 September 2014 (UTC)

woo-woo much more common spelling
See all the references and http://www.onelook.com and this. --Espoo (talk) 11:58, 20 January 2017 (UTC)

title: Talk:woo woo


text: Aussprachewörterbuchs

title: Aussprachewörterbuchs


text: Aussprachewörterbuches

title: Aussprachewörterbuches


text: Aussprachewörterbuche

title: Aussprachewörterbuche


text: Aussprachewörterbücher

title: Aussprachewörterbücher


text: Aussprachewörterbüchern

title: Aussprachewörterbüchern


text:
crómatagrafaíocht

Etymology
From.

Noun

 * 1)  chromatography

title: crómatagrafaíocht


text:
crómata-

Etymology
From.

Prefix

 * 1) chromato-

title: crómata-


text:
pāvests

Etymology
Borrowed from (compare 🇨🇬), from an earlier  (with an intrusive final t), borrowed from, also borrowed from  (in use for the bishop of Rome since the 5th century), itself borrowed from  (< “father”). In Latvian, this loanword is first mentioned in 17th-century dictionaries.

Noun

 * 1) Pope the bishop of Rome, the head of the Catholic Church and ruler of the Vatican City State

title: pāvests


text: pāvestu

title: pāvestu


text:
zeval

Etymology
From, from.

Noun

 * 1)  decadence
 * 2)  dissolution
 * 3)  doom
 * 4)  midday, noon

title: zeval


text: zevali

title: zevali


text: zevaller

title: zevaller


text:
breischéim

Etymology
From.

Noun

 * 1)  comparative

title: breischéim


text:
User:Soardra

Etymology
that first appeared late in 2006 as a username created by a Michiganian Troll.

Pronunciation
*

Proper noun

 * 1) A shapeshifting, digital dragon.

Alternate forms

 * (username) Soaring Dragon, SoaringDragon, DragQueen, FangQueen469
 * (email) srngdrgn
 * (blend) SoarDra, SrngDrgn
 * (nickname) Soar, Soaring, Draggy, Soda, Soda Pop, Soard

title: User:Soardra


text:
skāł

Etymology
Borrowed from.

Noun

 * 1) rock

title: skāł


text:
comparáideach

Etymology
From.

Adjective

 * 1)  comparative

title: comparáideach


text: pāvestam

title: pāvestam


text: pāvestā

title: pāvestā


text: pāvesta

title: pāvesta


text: pāvesti

title: pāvesti


text: pāvestus

title: pāvestus


text: pāvestiem

title: pāvestiem


text: pāvestos

title: pāvestos


text:
comparáid

Etymology
Borrowed from, from , perfect passive participle of.

Noun

 * 1)  comparison

title: comparáid


text:
uitspraakwoordenboek

Etymology
. Akin to German.

Noun

 * 1) pronunciation dictionary

title: uitspraakwoordenboek


text:
cotillage

Noun

 * 1) joint tillage; the act of plowing land jointly with others
 * 2) the land so tilled

Usage notes
This term is particularly applied to historic Welsh practice, where cyfar (cotillage) of some lands was required by law among the taeog (serf) class before they were permitted to cultivate their own private plots.

Translations

 * Old Welsh: kyuar, kaueyr
 * Welsh: cyfar

title: cotillage


text: Vatikānā

title: Vatikānā


text: Vatikāna

title: Vatikāna


text:
זלאָטע

Etymology
.

Noun

 * 1) zloty the currency unit of Poland

title: זלאָטע


text: זלאָטעס

title: זלאָטעס


text: Vatikānu

title: Vatikānu


text: co-tillage

title: co-tillage


text: Vatikānam

title: Vatikānam


text: uitspraakwoordenboeken

title: uitspraakwoordenboeken


text: uitspraakwoordenboekje

title: uitspraakwoordenboekje


text: hecks

title: hecks


text: counterfeitings

title: counterfeitings


text: co-aration

title: co-aration


text:
turnstiled

Adjective

 * 1) Fitted or equipped with turnstiles.

title: turnstiled


text: uitspraakwoordenboekjes

title: uitspraakwoordenboekjes


text:
cyfar

Etymology
From.

Noun

 * 1)  cotillage; land cultivated jointly within a  or

title: cyfar


text:
Vatikāna Pilsētvalsts

Proper noun

 * 1) Vatican City State official name of the Vatican or Vatican City

title: Vatikāna Pilsētvalsts


text:
crostagairt

Etymology
From.

Noun

 * 1) cross-reference

title: crostagairt


text:
kyuar

Noun

 * 1)  cotillage; land cultivated jointly within a tref or taeogtref

title: kyuar


text:
crosdiabhal

Etymology
From.

Noun

 * 1) Devil's imp, mischievous person

title: crosdiabhal


text: kaueyr

title: kaueyr


text:
cubanelle

Noun

 * 1) A particular sweet pepper, a cultivar of the species.

title: cubanelle


text: Cubanelle

title: Cubanelle


text: cubanelles

title: cubanelles


text: Cubanelles

title: Cubanelles


text:
pilsētvalsts

Etymology
From.

Noun

 * 1) city state economically and politically sovereign city, often including its surrounding territory, e.g., Ancient Greece

title: pilsētvalsts


text:
okey-dokey, Smokey

Etymology
okey-dokey extended with a further arbitrary rhyme; Smokey is a nickname.

Phrase

 * 1)  okey-dokey; OK; alright.

title: okey-dokey, Smokey


text:
sióg

Etymology
From.

Noun

 * 1) fairy

title: sióg


text:
fasin

Etymology
From.

Noun

 * 1) fashion
 * 2) manner
 * 3) custom
 * 4) behavior

title: fasin


text:
blufærdig

Adjective

 * 1) modest, bashful; shy or timid in matters of a sexual nature; reluctant to being fully or partially nude

title: blufærdig


text: okey-dokey, smokey

title: okey-dokey, smokey


text:
síog

Etymology
From.

Noun

 * 1) streak, stripe
 * 2)  seam, lode, vein

Verb

 * 1)  streak
 * 2)  to strike out, cancel

title: síog


text: okey dokey, Smokey

title: okey dokey, Smokey


text:
shishito

Etymology
Borrowed from.

Noun

 * 1) A sweet Japanese pepper, a cultivar of the species.

title: shishito


text: shishitos

title: shishitos


text: Module:ru-translit/documentation

title: Module:ru-translit/documentation


text:
pronunciation dictionary

Noun

 * 1) A dictionary that provides pronunciation of words, usually in the International Phonetic Alphabet.

Translations

 * Afrikaans:
 * Chinese:
 * Mandarin: 发音词典, 發音詞典
 * Danish: udtaleordbog
 * Dutch:
 * Finnish: ääntämissanakirja
 * French: dictionnaire de prononciation
 * German:
 * Hungarian: kiejtési szótár, kiejtésszótár
 * Norwegian:
 * Bokmål: uttaleordbok
 * Nynorsk: uttaleordbok
 * Polish: słownik wymowy
 * Portuguese:
 * Romanian: dicționar de pronunțare
 * Spanish: diccionario de pronunciación
 * Swedish: uttalsordbok
 * West Frisian: útspraakwurdboek

title: pronunciation dictionary


text: okey dokey, smokey

title: okey dokey, smokey


text: komplementärer

title: komplementärer


text: komplementäre

title: komplementäre


text: komplementäres

title: komplementäres


text: komplementären

title: komplementären


text: komplementärem

title: komplementärem


text:
Komplexometrie

Noun

 * 1) complexometry

title: Komplexometrie


text: Category:nb:Trees

title: Category:nb:Trees


text: pilsētvalsti

title: pilsētvalsti


text:
komplexometrisch

Adjective

 * 1) complexometric

title: komplexometrisch


text: pilsētvalstī

title: pilsētvalstī


text: pilsētvalstij

title: pilsētvalstij


text: Category:fj:Pathology

title: Category:fj:Pathology


text:
Kristallgefüge

Noun

 * 1) crystal structure

title: Kristallgefüge


text: Category:nb:Milk

title: Category:nb:Milk


text: Category:nb:Dairy products

title: Category:nb:Dairy products


text: pronunciation dictionaries

title: pronunciation dictionaries


text: Category:nb:Beverages

title: Category:nb:Beverages


text: Category:ur:Archery

title: Category:ur:Archery


text:
Category talk:English noun forms

Contents
Should only contain categories, right? Mglovesfun (talk) 22:21, 16 March 2013 (UTC)

RFDO discussion: April 2014–June 2016
I removed all the non-English ones (mostly Volapük) and then moved all the English plurals to Category:English plurals and lo and behold it's empty. I think it was once a parent category for Category:English plurals but now it isn't. So delete, or keep as a parent category only and create a template. Renard Migrant (talk) 19:03, 20 April 2014 (UTC)
 * I proposed some time ago that Category:English plurals should be moved to Category:English noun plural forms. We don't need two different categories for noun plurals, after all. Are there any other noun forms in English, perhaps archaic case forms that are no longer in use? 19:07, 20 April 2014 (UTC)
 * The only other form is the possessive, which is now more of a morpheme than a case. --WikiTiki89 19:09, 20 April 2014 (UTC)
 * But is it possible that we can cite other noun forms in old texts, like Shakespeare for example? 19:14, 20 April 2014 (UTC)
 * No, because they disappeared phonologically. The last remnants were the presence or lack of a final schwa and by Shakespeare's time it was already entirely silent. --WikiTiki89 19:20, 20 April 2014 (UTC)
 * Well in any case, I still think this should be kept as a parent category for Category:English noun plural forms. Or we could place the plurals straight in Category:English noun forms, if those are the only noun forms that exist anyway. 20:20, 20 April 2014 (UTC)
 * Category:English noun plural forms wasn't a very popular idea, pure and simple. Nor was moving Category:English plurals to Category:English noun forms. I doubt the consensus has changed, but feel free to give it a go. Renard Migrant (talk) 20:44, 20 April 2014 (UTC)
 * Convert to . Renard Migrant (talk) 12:49, 13 November 2014 (UTC)
 * With changes to the overall category structure, I consider this debate obsolete and should be closed with no further actions taken. Renard Migrant (talk) 22:26, 14 January 2016 (UTC)

Closed as no consensus and as obsolete: Pur ple back pack 89  05:31, 19 June 2016 (UTC)

RFM discussion: March–May 2019

 * See Category talk:English noun plural forms.

title: Category talk:English noun forms


text: Category:is:Quantum mechanics

title: Category:is:Quantum mechanics


text:
urghabháil

Noun

 * 1)  seizure
 * 1)  seizure

title: urghabháil


text:
Kunstgegenstand

Noun

 * 1) art object, objet d'art
 * 2) antique
 * 3) artifact

title: Kunstgegenstand


text: Category:nb:Fire

title: Category:nb:Fire


text: Category:nb:Combustion

title: Category:nb:Combustion


text: Category:nb:Chemical processes

title: Category:nb:Chemical processes


text:
очертание

Noun

 * 1) outline line marking the boundary of an object figure

title: очертание


text:
Kunsthandwerk

Noun

 * 1) handicraft
 * 2) crafts

title: Kunsthandwerk


text:
контур

Etymology
.

Noun

 * 1) contour, outline
 * 2) circuit

Etymology
, from.

Noun

 * 1) contour, outline
 * 2)  circuit
 * 1)  circuit

title: контур


text:
urghabh

Etymology
From, from. .

Pronunciation

 * }}
 * }}

Verb

 * 1)  seize

title: urghabh


text: vertaalwoordenboeken

title: vertaalwoordenboeken


text: vertaalwoordenboekje

title: vertaalwoordenboekje


text: Category:tyv:Foods

title: Category:tyv:Foods


text: vertaalwoordenboekjes

title: vertaalwoordenboekjes


text: Category:tyv:Food and drink

title: Category:tyv:Food and drink


text: pilsētvalstis

title: pilsētvalstis


text: Category:tyv:Nature

title: Category:tyv:Nature


text:
㗂

Definitions

 * 1)  to be taciturn and speak cautiously

title: 㗂


text: pilsētvalstīs

title: pilsētvalstīs


text: Category:tyv:Biology

title: Category:tyv:Biology


text: pilsētvalstu

title: pilsētvalstu


text: Category:tyv:Earth sciences

title: Category:tyv:Earth sciences


text: pilsētvalstīm

title: pilsētvalstīm


text: Category:fa:Alaska, USA

title: Category:fa:Alaska, USA


text: Category:nb:Agriculture

title: Category:nb:Agriculture


text: Category:pt:Theater

title: Category:pt:Theater


text: Category:es:Places of worship

title: Category:es:Places of worship


text: okey dokey smokey

title: okey dokey smokey


text: Category:tk:Canids

title: Category:tk:Canids


text: Category:hy:Dances

title: Category:hy:Dances


text: Category:pt:Genealogy

title: Category:pt:Genealogy


text:
Taschenwörterbuch

Etymology
.

Noun

 * 1) pocket dictionary

title: Taschenwörterbuch


text: Category:hi:Malaysia

title: Category:hi:Malaysia


text: Category:ms:Networking

title: Category:ms:Networking


text: Category:pt:Ceramics

title: Category:pt:Ceramics


text: Category:gv:Spain

title: Category:gv:Spain


text:
Module talk:ru-translit/documentation

Bad example
The example: as "mnóvo" is exactly what should be avoided. It's "mnógo", not "mnóvo". The letter "г" (g) is pronounced as expected in this word. --Anatoli (обсудить/вклад) 22:46, 16 March 2013 (UTC)

title: Module talk:ru-translit/documentation


text: Category:mhn:Liquids

title: Category:mhn:Liquids


text: Category:mhn:Beverages

title: Category:mhn:Beverages


text: Übersetzungswörterbuche

title: Übersetzungswörterbuche


text: Vatikāna Pilsētvalstī

title: Vatikāna Pilsētvalstī


text: Vatikāna Pilsētvalsti

title: Vatikāna Pilsētvalsti


text: Category:pt:Alchemy

title: Category:pt:Alchemy


text: Übersetzungswörterbüchern

title: Übersetzungswörterbüchern


text: Vatikāna Pilsētvalstij

title: Vatikāna Pilsētvalstij


text: Taschenwörterbuchs

title: Taschenwörterbuchs


text: Category:gv:Bodily fluids

title: Category:gv:Bodily fluids


text: Taschenwörterbuches

title: Taschenwörterbuches


text:
مربوط به آینده

Adjective

 * 1) futuristic
 * در گونه علمی‌تخیلی فناوری یا علوم امروزی یا مربوط به آینده دستمایهٔ هنرمند و آفرینشگر قرار می‌گیرد.
 * Dar gune 'elmi-taxeyli fannâvari yâ 'olum-e emruzi yâ marbut be âyande dast-mâye-ye honarmand o âfarinešgar qarâr mi-girad.

title: مربوط به آینده


text: Category:lt:Nonverbal communication

title: Category:lt:Nonverbal communication


text: Category:lt:Face

title: Category:lt:Face


text: Taschenwörterbuche

title: Taschenwörterbuche


text: Taschenwörterbücher

title: Taschenwörterbücher


text: Taschenwörterbüchern

title: Taschenwörterbüchern


text: Category:pl:Jewelry

title: Category:pl:Jewelry


text: Category:grc:Ancient Greece

title: Category:grc:Ancient Greece


text: Category:grc:Greece

title: Category:grc:Greece


text: Category:grc:Europe

title: Category:grc:Europe


text: Category:grc:Eurasia

title: Category:grc:Eurasia


text: dropped ceilings

title: dropped ceilings


text: Category:pal:Trading

title: Category:pal:Trading


text: Bildwörterbuche

title: Bildwörterbuche


text: Category:pal:Finance

title: Category:pal:Finance


text: Bildwörterbüchern

title: Bildwörterbüchern


text: Category:sk:Directions

title: Category:sk:Directions


text: Template:kk-verb

title: Template:kk-verb


text: Wikiwörterbuchs

title: Wikiwörterbuchs


text: Wikiwörterbüchern

title: Wikiwörterbüchern


text: Category:dlm:Family

title: Category:dlm:Family


text: Category:dlm:Human

title: Category:dlm:Human


text: Template:kk-proper noun

title: Template:kk-proper noun


text: Category:nl:Reference works

title: Category:nl:Reference works


text: Category:fy:Reference works

title: Category:fy:Reference works


text: Category:gd:Racquet sports

title: Category:gd:Racquet sports


text: Category:nl:Books

title: Category:nl:Books


text: Category:fy:Books

title: Category:fy:Books


text: Indijā

title: Indijā


text: Category:af:Books

title: Category:af:Books


text: okey-dokey-smokey

title: okey-dokey-smokey


text: Category:nrn:Mammals

title: Category:nrn:Mammals


text: Category:sah:People

title: Category:sah:People


text: Category:sah:Human

title: Category:sah:Human


text: Category:ga:Indonesia

title: Category:ga:Indonesia


text: índios

title: índios


text: Category:nn:Sexuality

title: Category:nn:Sexuality


text: Category:nn:Sex

title: Category:nn:Sex


text: Category:rup:Meals

title: Category:rup:Meals


text: Category:rup:Food and drink

title: Category:rup:Food and drink


text: Category:ba:Divination

title: Category:ba:Divination


text: Category:ba:Pseudoscience

title: Category:ba:Pseudoscience


text: Category:ba:Occult

title: Category:ba:Occult


text: Category:ba:Forteana

title: Category:ba:Forteana


text: pŕs

title: pŕs


text: Indiju

title: Indiju


text: Indijai

title: Indijai


text: Indijas

title: Indijas


text: jazier

title: jazier


text:
kíl

Noun

 * 1) voice
 * 2) language

Noun

 * 1) elbow

title: kíl


text:
drošinošā

Participle

title: drošinošā


text:
nedrošinošā

Participle

title: nedrošinošā


text:
bagātinošā

Participle

title: bagātinošā


text:
nebagātinošā

Participle

title: nebagātinošā


text:
nabadzinošā

Participle

title: nabadzinošā


text:
nenabadzinošā

Participle

title: nenabadzinošā


text:
turpinošā

Participle

title: turpinošā


text: Büchern

title: Büchern


text:
neturpinošā

Participle

title: neturpinošā


text:
sargošā

Participle

title: sargošā


text:
nesargošā

Participle

title: nesargošā


text:
sargājošā

Participle

title: sargājošā


text:
nesargājošā

Participle

title: nesargājošā


text: Büchleins

title: Büchleins


text: drošinošas

title: drošinošas


text: nedrošinošas

title: nedrošinošas


text: bagātinošas

title: bagātinošas


text: nebagātinošas

title: nebagātinošas


text:
Template:Kazakh personal pronouns

Kazakh personal pronouns

title: Template:Kazakh personal pronouns


text: nabadzinošas

title: nabadzinošas


text: nenabadzinošas

title: nenabadzinošas


text: turpinošas

title: turpinošas


text: neturpinošas

title: neturpinošas


text: sargošas

title: sargošas


text: nesargošas

title: nesargošas


text: sargājošas

title: sargājošas


text: nesargājošas

title: nesargājošas


text:
drošinošās

Participle

title: drošinošās


text:
nedrošinošās

Participle

title: nedrošinošās


text:
bagātinošās

Participle

title: bagātinošās


text:
nebagātinošās

Participle

title: nebagātinošās


text:
Standardaussprache

Etymology
.

Noun

 * 1) standard pronunciation

title: Standardaussprache


text:
nabadzinošās

Participle

title: nabadzinošās


text:
nenabadzinošās

Participle

title: nenabadzinošās


text:
turpinošās

Participle

title: turpinošās


text: Standardaussprachen

title: Standardaussprachen


text:
neturpinošās

Participle

title: neturpinošās


text:
sargošās

Participle

title: sargošās


text:
nesargošās

Participle

title: nesargošās


text:
sargājošās

Participle

title: sargājošās


text:
nesargājošās

Participle

title: nesargājošās


text: Citations:drygulch

title: Citations:drygulch


text:
сіз

Pronoun

 * 1) you second-person singular polite subject pronoun

title: сіз


text: drošinošam

title: drošinošam


text:
Thread:User talk:CodeCat/Mewbot has misbehaved

Special uncategorized pages shows about 10 items that Mewbot seems so have messed up. The report is run only every four days or so, and the problem is not widespread so I didn't think blocking was right. I will correct them by my lights.


text:
біз

Pronoun

 * 1) we first-person plural subject pronoun

title: біз


text: nedrošinošam

title: nedrošinošam


text: bagātinošam

title: bagātinošam


text: nebagātinošam

title: nebagātinošam


text:
сендер

Pronoun

 * 1) you, thou second-person plural familiar subject pronoun

title: сендер


text: nabadzinošam

title: nabadzinošam


text:
сіздер

Pronoun

 * 1) you second-person plural polite subject pronoun

title: сіздер


text: nenabadzinošam

title: nenabadzinošam


text:
олар

Pronoun

 * 1) they third-person plural subject pronoun

Pronoun

 * 1) they third-person plural personal pronoun

Etymology
From +.

Pronoun

 * 1) they

Etymology
From. Compare to 🇨🇬, 🇨🇬.

Pronoun

 * 1) they third-person plural personal pronoun

Etymology
. Cognate to 🇨🇬.

Pronoun

 * 1) they (third-person plural personal pronoun)
 * 2)  those

title: олар


text: turpinošam

title: turpinošam


text: neturpinošam

title: neturpinošam


text: sargošam

title: sargošam


text: nesargošam

title: nesargošam


text: sargājošam

title: sargājošam


text: nesargājošam

title: nesargājošam


text: drošinošām

title: drošinošām


text: nedrošinošām

title: nedrošinošām


text: bagātinošām

title: bagātinošām


text: Template:ky-pronoun

title: Template:ky-pronoun


text: nebagātinošām

title: nebagātinošām


text: nabadzinošām

title: nabadzinošām


text: nenabadzinošām

title: nenabadzinošām


text: turpinošām

title: turpinošām


text: neturpinošām

title: neturpinošām


text: sargošām

title: sargošām


text: nesargošām

title: nesargošām


text: sargājošām

title: sargājošām


text: nesargājošām

title: nesargājošām


text:
chiltepe

Noun

 * 1) A chiltepin.

title: chiltepe


text: chiltepes

title: chiltepes


text: chiltepins

title: chiltepins


text:
силер

Pronoun

 * 1) you second-person plural familiar personal pronoun

Etymology
From +. Cognate to 🇨🇬.

Pronoun

 * 1) you

title: силер


text:
сиздер

Pronoun

 * 1) you second-person plural polite personal pronoun

title: сиздер


text:
алар

Pronoun

 * 1) they third-person plural personal pronoun

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

Verb

 * 1) to take

Pronoun

 * 1) they third-person plural personal pronoun

Noun

 * 1)  woods, grove

title: алар


text:
nicht-

Etymology
See. Akin to 🇨🇬 and 🇨🇬.

Prefix

 * 1) non-, un-

title: nicht-


text:
drošinošos

Participle

title: drošinošos


text:
nedrošinošos

Participle

title: nedrošinošos


text:
bagātinošos

Participle

title: bagātinošos


text:
nebagātinošos

Participle

title: nebagātinošos


text:
nabadzinošos

Participle

title: nabadzinošos


text:
nenabadzinošos

Participle

title: nenabadzinošos


text:
turpinošos

Participle

title: turpinošos


text:
neturpinošos

Participle

title: neturpinošos


text:
sargošos

Participle

title: sargošos


text:
nesargošos

Participle

title: nesargošos


text:
sargājošos

Participle

title: sargājošos


text:
Nichtmuttersprachler

Noun

 * 1) non-native speaker

title: Nichtmuttersprachler


text:
nesargājošos

Participle

title: nesargājošos


text: Category:German terms prefixed with nicht-


text: Template:ky-proper noun

title: Template:ky-proper noun


text: drošinošiem

title: drošinošiem


text:
pennur

Etymology
From late, from , from , from , from. Cognate to 🇨🇬.

Noun

 * 1) pen

title: pennur


text: nedrošinošiem

title: nedrošinošiem


text: bagātinošiem

title: bagātinošiem


text: nebagātinošiem

title: nebagātinošiem


text: nabadzinošiem

title: nabadzinošiem


text: nenabadzinošiem

title: nenabadzinošiem


text: turpinošiem

title: turpinošiem


text: neturpinošiem

title: neturpinošiem


text: sargošiem

title: sargošiem


text: nesargošiem

title: nesargošiem


text: sargājošiem

title: sargājošiem


text: nesargājošiem

title: nesargājošiem


text: drošinoši

title: drošinoši


text: nedrošinoši

title: nedrošinoši


text:
Nichtmuttersprachlerin

Etymology
or

Noun

 * : female non-native speaker

title: Nichtmuttersprachlerin


text: bagātinoši

title: bagātinoši


text: nebagātinoši

title: nebagātinoši


text: nabadzinoši

title: nabadzinoši


text: nenabadzinoši

title: nenabadzinoši


text: turpinoši

title: turpinoši


text: Nichtmuttersprachlers

title: Nichtmuttersprachlers


text: neturpinoši

title: neturpinoši


text: sargoši

title: sargoši


text: nesargoši

title: nesargoši


text: sargājoši

title: sargājoši


text: nesargājoši

title: nesargājoši


text: drošinošus

title: drošinošus


text: drošinošai

title: drošinošai


text: nedrošinošus

title: nedrošinošus


text: nedrošinošai

title: nedrošinošai


text: bagātinošus

title: bagātinošus


text: bagātinošai

title: bagātinošai


text: nebagātinošus

title: nebagātinošus


text:
Muttersprachlerin

Noun

 * 1) native speaker (female)

title: Muttersprachlerin


text: nebagātinošai

title: nebagātinošai


text: nabadzinošus

title: nabadzinošus


text: nabadzinošai

title: nabadzinošai


text: nenabadzinošus

title: nenabadzinošus


text: nenabadzinošai

title: nenabadzinošai


text: turpinošus

title: turpinošus


text: turpinošai

title: turpinošai


text: neturpinošus

title: neturpinošus


text: Nichtmuttersprachlerinnen

title: Nichtmuttersprachlerinnen


text: neturpinošai

title: neturpinošai


text: Caribs

title: Caribs


text: sargošus

title: sargošus


text: sargošai

title: sargošai


text: nesargošus

title: nesargošus


text: nesargošai

title: nesargošai


text: sargājošus

title: sargājošus


text: sargājošai

title: sargājošai


text: nesargājošus

title: nesargājošus


text:
🔈

Etymology
A speaker.


text: nesargājošai

title: nesargājošai


text:
Thread:User talk:CodeCat/Mewbot has misbehaved/reply

I'm not sure why that happened. I have been using a regular expression that doesn't match on closing braces, so it should have stopped on the first one and then failed to match the rest, not making any changes...


text:
User talk:Ahls23

Tie bars on affricates
This the new standard notation? --Ivan Štambuk (talk) 19:34, 4 August 2013 (UTC)
 * Not so much of a standard notation, but when the language contrasts affricates and sequences of stop+fricative, the tie bar should be present in order to avoid confusion. --Ahls23 (talk) 20:04, 4 August 2013 (UTC)
 * That's what the hyphenation part just below is for. --Ivan Štambuk (talk) 20:50, 4 August 2013 (UTC)

title: User talk:Ahls23


text: drošinošais

title: drošinošais


text: nedrošinošais

title: nedrošinošais


text: bagātinošais

title: bagātinošais


text: nebagātinošais

title: nebagātinošais


text: nabadzinošais

title: nabadzinošais


text: nenabadzinošais

title: nenabadzinošais


text: turpinošais

title: turpinošais


text:
💉

Description
A syringe, often with blood or medication in it (but see the usage note).

Symbol

 * 1) blood draw, blood donation
 * 2) vaccine, vaccination

Usage notes
Originally used for the representation of blood donation, and displayed with blood in the barrel. In 2021 most platforms are switching to a more general-purpose empty syringe.


text: neturpinošais

title: neturpinošais


text: sargošais

title: sargošais


text: nesargošais

title: nesargošais


text: sargājošais

title: sargājošais


text:
fuckumentary

Noun

 * 1)  A documentary featuring or focusing on explicit sexual conduct.

title: fuckumentary


text: nesargājošais

title: nesargājošais


text: fuckumentaries

title: fuckumentaries


text: drošinošo

title: drošinošo


text: nedrošinošo

title: nedrošinošo


text: bagātinošo

title: bagātinošo


text: nebagātinošo

title: nebagātinošo


text:
💯

Design
Depicts one hundred points (out of a possible one hundred)

Symbol

 * 1) excellent, perfect
 * 2)  keep it one hundred


text:
بیهوده

Etymology
.

Adjective

 * 1) ineffective, useless, futile, pointless, trivial

title: بیهوده


text: slovenskí

title: slovenskí


text:
User talk:151.226.237.80

Thank you for looking for a reference for 祭宮, but Wikis do not count as reliable reference sources, especially Wikia where anybody can set up a wiki, no matter how much or little they know. It's just as good as saying "somebody told me..." Also
 * Please stop adding links to pages that don't exist. 祭宮 does not have a page on Chinese Wikipedia.  In fact, links to Wikipedia pages from non-English entries are discouraged in general, even when they do exist.
 * Please stop adding links to other Wiktionaries when they do not have pages either. It looks almost as if you're trying to trick other editors into thinking that the words you add exist by adding support from other Wiktionaries or Wikipedia.

Perhaps I'm wrong and 祭宮 is a real word, but it's hard to verify (i.e. not in my dictionary) so you have to provide a reference to a real dictionary.

As far as I'm concerned, you're still blocked for a while, no matter how many times you get a new IP. Please do something else with your time. --Haplology (talk) 01:28, 17 March 2013 (UTC)

title: User talk:151.226.237.80


text:
Module:Geor-translit

local m_str_utils = require("Module:string utilities")

local codepoint = m_str_utils.codepoint local gsub = m_str_utils.gsub local u = m_str_utils.char local upper = m_str_utils.upper

local export = {}

-- Keep synchronized with Module:sva-translit and Module:Geok-translit local tt = { ["ა"]="a", ["ბ"]="b", ["გ"]="g", ["დ"]="d", ["ე"]="e", ["ვ"]="v", ["ზ"]="z", ["ჱ"]="ē", ["თ"]="t", ["ი"]="i", ["კ"]="ḳ", ["ლ"]="l", ["მ"]="m", ["ნ"]="n", ["ჲ"]="y", ["ო"]="o", ["პ"]="ṗ", ["ჟ"]="ž", ["რ"]="r", ["ს"]="s", ["ტ"]="ṭ", ["ჳ"]="wi", ["უ"]="u", ["ფ"]="p", ["ქ"]="k", ["ღ"]="ɣ", ["ყ"]="q̇", ["შ"]="š", ["ჩ"]="č", ["ც"]="c", ["ძ"]="ʒ", ["წ"]="c̣", ["ჭ"]="č̣", ["ხ"]="x", ["ჴ"]="q", ["ჯ"]="ǯ", ["ჰ"]="h", ["ჵ"]="'", ["ჶ"]="f", ["ჷ"]="ə", ["ჸ"]="ʾ", ["ჺ"]="ʿ", ["ʻ"]="ˢ", };

function export.tr(text, lang, sc) -- Transliterating vowel nasalization in Bats text = gsub(text, 'ჼ', '̃') text = gsub(text, 'ნ', '̃') -- Transliterate uppercase characters from the Georgian Extended block as	-- the uppercase version of the transliteration of the lowercase characters -- from the Georgian block. -- U+10D0: start of Georgian block -- U+1C90: start of Georgian Extended block text = gsub(		text,		'[' .. u(0x1C90) .. '-' .. u(0x1CBF) .. ']',		function (char)			local translit = tt[u(codepoint(char) - 0x1C90 + 0x10D0 )]			return translit and upper(translit)		end) text = gsub(text, '.', tt) return text end

return export

title: Module:Geor-translit


text:
Module talk:Geor-translit

Testing ქართული ენა:. --Anatoli (обсудить/вклад) 01:37, 17 March 2013 (UTC)

Implementation suggestion
Could we give it a use that's similar to ? --Lo Ximiendo (talk) 02:53, 29 May 2013 (UTC)

title: Module talk:Geor-translit


text: Nichtmuttersprachlern

title: Nichtmuttersprachlern


text: Muttersprachlern

title: Muttersprachlern


text: Muttersprachlerinnen

title: Muttersprachlerinnen


text:
Module:Armn-translit

local export = {} local gsub = require("Module:string utilities").gsub

local mapping = { ["ա"]="a", ["բ"]="b", ["գ"]="g", ["դ"]="d", ["ե"]="e", ["զ"]="z",["է"]="ē", ["ը"]="ə", ["թ"]="tʻ", ["ժ"]="ž", ["ի"]="i", ["լ"]="l", ["խ"]="x", ["ծ"]="c", ["կ"]="k", ["հ"]="h", ["ձ"]="j", ["ղ"]="ġ", ["ճ"]="č", ["մ"]="m", ["յ"]="y", ["ն"]="n", ["շ"]="š", ["ո"]="o", ["չ"]="čʻ", ["պ"]="p", ["ջ"]="ǰ", ["ռ"]="ṙ", ["ս"]="s", ["վ"]="v", ["տ"]="t", ["ր"]="r", ["ց"]="cʻ", ["ւ"]="w", ["փ"]="pʻ", ["ք"]="kʻ", ["և"]="ew", ["օ"]="ō", ["ֆ"]="f", ["Ա"]="A", ["Բ"]="B", ["Գ"]="G", ["Դ"]="D", ["Ե"]="E", ["Զ"]="Z", ["Է"]="Ē", ["Ը"]="Ə", ["Թ"]="Tʻ", ["Ժ"]="Ž", ["Ի"]="I", ["Լ"]="L", ["Խ"]="X", ["Ծ"]="C", ["Կ"]="K", ["Հ"]="H", ["Ձ"]="J", ["Ղ"]="Ġ", ["Ճ"]="Č", ["Մ"]="M", ["Յ"]="Y", ["Ն"]="N", ["Շ"]="Š", ["Ո"]="O", ["Չ"]="Čʻ", ["Պ"]="P", ["Ջ"]="J̌", ["Ռ"]="Ṙ", ["Ս"]="S", ["Վ"]="V", ["Տ"]="T", ["Ր"]="R", ["Ց"]="Cʻ", ["Ւ"]="W", ["Փ"]="Pʻ", ["Ք"]="Kʻ", ["Օ"]="Ō", ["Ֆ"]="F", ["ﬓ "]="mn", ["ﬔ"]="me", ["ﬕ"]="mi", ["ﬖ"]="vn", ["ﬗ"]="mx", ["ՠ"]="ä", ["ֈ"]="hª", -- punctuation ["՝"]=",", ["։"]=".", ["․"]=";", ["՛"]="́", ["՜"]="!", ["՞"]="?",	["՟"]=".", ["֊"]="-", ["՚"]="’", ['«']='“', ['»']='”', ['ՙ']='ʻ' }

local replacements = { -- desirable, but doesn't work: ['յ'] = 'ʸ', ['յ̵'] = 'hª', --keep synchronized with ֈ ['ղʻ'] = 'q', ['Ո[ւՒ]'] = 'U', ['ու'] = 'u', ['Ո՛[ւՒ]'] = 'Ú', ['ո՛ւ'] = 'ú', ['Ո՜[ւՒ]'] = 'U!', ['ո՜ւ'] = 'u!', ['Ո՞[ւՒ]'] = 'U?', ['ո՞ւ'] = 'u?', ['ո̈ւ'] = 'ü', ['Ո̈[ւՒ]'] = 'Ü', ['օ̈'] = 'ö', ['Օ̈'] = 'Ö', }

function export.tr(text, lang, sc) if sc and sc ~= "Armn" then return nil end

if lang == "xcl" then mapping["ղ"]="ł" mapping["Ղ"]="Ł" end

for regex, replacement in pairs(replacements) do		text = gsub(text, regex, replacement) end

text = gsub(text, '.', mapping) return text end

return export

title: Module:Armn-translit


text: nabadzinošo

title: nabadzinošo


text: native Speaker

title: native Speaker


text: nenabadzinošo

title: nenabadzinošo


text: turpinošo

title: turpinošo


text: native Speakers

title: native Speakers


text: neturpinošo

title: neturpinošo


text: sargošo

title: sargošo


text:
Native Speaker

Etymology
(in the 20th century).

Noun

 * 1)  a native speaker

title: Native Speaker


text: Native Speakers

title: Native Speakers


text: nesargošo

title: nesargošo


text: sargājošo

title: sargājošo


text: nesargājošo

title: nesargājošo


text: drošinošajam

title: drošinošajam


text: nedrošinošajam

title: nedrošinošajam


text: bagātinošajam

title: bagātinošajam


text: nebagātinošajam

title: nebagātinošajam


text: nabadzinošajam

title: nabadzinošajam


text: nenabadzinošajam

title: nenabadzinošajam


text: turpinošajam

title: turpinošajam


text: neturpinošajam

title: neturpinošajam


text:
Kaguya

Etymology
Borrowed from.

Proper noun

 * 1)  The protagonist of, a mysterious girl from the moon, discovered as a baby inside the stalk of a glowing bamboo plant.

Translations

 * Chinese:
 * Mandarin:
 * Japanese: かぐや姫

title: Kaguya


text: sargošajam

title: sargošajam


text: nesargošajam

title: nesargošajam


text: 赫映

title: 赫映


text: sargājošajam

title: sargājošajam


text: nesargājošajam

title: nesargājošajam


text: drošinošajām

title: drošinošajām


text: nedrošinošajām

title: nedrošinošajām


text: bagātinošajām

title: bagātinošajām


text: nebagātinošajām

title: nebagātinošajām


text: nabadzinošajām

title: nabadzinošajām


text: nenabadzinošajām

title: nenabadzinošajām


text: turpinošajām

title: turpinošajām


text: neturpinošajām

title: neturpinošajām


text: sargošajām

title: sargošajām


text: nesargošajām

title: nesargošajām


text: sargājošajām

title: sargājošajām


text: nesargājošajām

title: nesargājošajām


text: drošinošie

title: drošinošie


text: drošinošajiem

title: drošinošajiem


text: drošinošajā

title: drošinošajā


text: nedrošinošie

title: nedrošinošie


text: nedrošinošajiem

title: nedrošinošajiem


text: nedrošinošajā

title: nedrošinošajā


text: bagātinošie

title: bagātinošie


text: bagātinošajiem

title: bagātinošajiem


text: bagātinošajā

title: bagātinošajā


text: nebagātinošie

title: nebagātinošie


text: nebagātinošajiem

title: nebagātinošajiem


text: nebagātinošajā

title: nebagātinošajā


text: nabadzinošie

title: nabadzinošie


text: nabadzinošajiem

title: nabadzinošajiem


text: nabadzinošajā

title: nabadzinošajā


text:
Module:ko-translit

local export = {}

local m_str_utils = require("Module:string utilities")

local gsub = m_str_utils.gsub

function export.tr(text, lang, sc) if (not text) or text == "" then return text end local HaniChars = require("Module:scripts").getByCode("Hani"):getCharacters text = gsub(text, "%<%/?r[pt]%>", "") text = gsub(text, "%<%/?ruby%>", "") -- remove hanja from (ex.) 사전(辭典) and 辭典(사전) and 온돌(溫突/溫堗) text = gsub(text, "%([" .. HaniChars .. "/]+%)", "")	text = gsub(text, "%([" .. HaniChars .. "]*'''[" .. HaniChars .. "]+'''[" .. HaniChars .. "]*%)", "")	text = gsub(text, "[" .. HaniChars .. "]+%((.-)%)", "%1") -- transform em-dash to plain hyphen-minus text = gsub(text, "—", "-") local HangChars = require("Module:scripts").getByCode("Hang"):getCharacters local m_pron = require("Module:ko-pron") text = gsub(text, "[" .. HangChars .. "%s%p􀀀-􏿽]+", function(m1) return m_pron.romanise(m1, 2, {}, true) end) return text and text :gsub("(%a)%-%'(%a)", "%1-%2") :gsub("%-%-", "-") :gsub("%-%-", "-") end

export.tr_revised = export.tr

return export

title: Module:ko-translit


text: nenabadzinošie

title: nenabadzinošie


text: nenabadzinošajiem

title: nenabadzinošajiem


text: nenabadzinošajā

title: nenabadzinošajā


text: turpinošie

title: turpinošie


text: turpinošajiem

title: turpinošajiem


text: turpinošajā

title: turpinošajā


text: neturpinošie

title: neturpinošie


text: neturpinošajiem

title: neturpinošajiem


text:
gelivable

Etymology
From. Perhaps a back-formation from, which was modelled on.

Adjective

 * 1)  Awesome, incredible, amazing, extraordinary.

title: gelivable


text:
Module talk:ko-translit

Keep original
What would that be used for? 03:16, 17 March 2013 (UTC)

 * I dunno — I imagine it made more sense in whatever Anatoli used his C# program for — but anyway, I've removed it now. (I actually removed it even before seeing your comment here.) —Ruakh TALK 07:32, 17 March 2013 (UTC)

 * Hi. Thank you for the conversion, Ruakh! Sorry for not replying earlier. Yes, that variable was used to append the converted text to the original. I should have removed it from my example. Good that you figured it out. I'll come back with some tweaks or requests to tweak. Will look at something that looks a bit simpler - Module:hy-translit. --Anatoli (обсудить/вклад) 09:47, 17 March 2013 (UTC)

Oops
It's not working. Getting "Script error" --Anatoli (обсудить/вклад) 10:04, 17 March 2013 (UTC)

 * That's expected behavior. For information on how to use Scribunto, see Scribunto. —Ruakh TALK 16:09, 17 March 2013 (UTC)

 * Thanks. Maybe I misunderstand something but it's expected behaviour if something doesn't work. The module compiles but I haven't seen it converting Korean hangeul (not the current or the original version). I have created Module:ko-translit-test for debugging/testing (will remove or rename later) and found out that the call fails on the function "len". --Anatoli (обсудить/вклад) 22:25, 17 March 2013 (UTC)

Do we want this function to actually be called directly from outside Lua? Like, do we want templates to be able to #invoke it directly? If so, then we should probably either add a dedicated function for that, or modify the function to support the possibility of receiving a frame rather than a string. —Ruakh TALK 22:50, 17 March 2013 (UTC)
 * It's just that nothing in the module was designed to be called directly from outside Lua. I've now added a general-purpose wrapper called main that you can use to test the module's functions, so you can write e.g.   (which produces ).

 * (before edit conflict) Got it, thank you! I actually tested without the second parameter yesterday, now I see that you need "|" to separate params. Testing "" without delimiter: "", with delimiter: "".
 * (after edit conflict), Yes, calling directly would be good, like other transliteration modules. Are you open for enhances, fixes of the module? I'd like to bring as close as possible to the standard Korean transliteration (called "revised"). The changes are consistent (depends on the positions of consistent - what precedes and what follows, beginning or end of word), there are no exceptions as such. --Anatoli (обсудить/вклад) 22:57, 17 March 2013 (UTC)

Re: "Are you open for enhances, fixes of the module?": Are you asking if I'm willing to make changes, or are you asking if it's O.K. if you make changes? In the former case — I can try. In the latter case — by all means, go ahead. I just created this as a starting-point. It's not actually used anywhere yet. —Ruakh TALK 23:08, 17 March 2013 (UTC)
 * Re: "like other transliteration modules": I wasn't aware of any others, which I guess is why this one differs from those. Can you point me at one, so I can see what kind of API they offer?
 * Category:Transliteration modules. This is why we have a categorisation system :) —Μετάknowledge discuss/deeds 23:15, 17 March 2013 (UTC)
 * Ew, it looks like those all require a frame, so they are really designed to be called only from outside Lua. If someone wants to do that to this module, please warn me in advance so I can remove it from my watchlist first. :-P  —Ruakh TALK 23:24, 17 March 2013 (UTC)
 * The original standards Anatoli and I have been following were designed by, and as I'm admittedly inept, I've needed his help a lot. If you want to change it (although I don't see why), you ought to discuss it with him, and because we still don't have that many modules, it can be changed relatively easily. —Μετάknowledge discuss/deeds 23:28, 17 March 2013 (UTC)

 * @Ruakh. I meant both, you, me or any other to change it. I'll change basicRomanization to tr match other modules. --Anatoli (обсудить/вклад) 01:03, 18 March 2013 (UTC)

 * To me <tt>tr</tt> implies that it's the actual romanization scheme we're using, but your description of it at GP implied that it's not, and your comments since then have reinforced that implication (by, e.g., talking about your desire to create something closer to Revised Romanization). —Ruakh TALK 01:09, 18 March 2013 (UTC)

 * The Revised Korean Romanization is one of the standards, and according to About_Korean, it's the main one, McCune-Reischauer is only mentioned as "another in use". I don't think it will contradict any our current policy, besides the Revised version is more straightforward, easier to implement and has more one to one correspondences than any previous transliterations. Our entries also follow revised but there are inconsistencies, many are due to the lack of knowledge of the standard. --Anatoli (обсудить/вклад) 01:22, 18 March 2013 (UTC)

 * In other words <tt>tr</tt> should produce the actual romanization scheme we're using (if possible) and entries/translations not following could/should be changed to match the current standard. User:KYPark had disagreements with some parts of the revised system because it wasn't phonetic enough but there's no perfect system. --Anatoli (обсудить/вклад) 01:27, 18 March 2013 (UTC)
 * I would prefer a more descriptive name than just two letters, though. Same for all the other modules. 01:48, 18 March 2013 (UTC)

 * You're maybe right (before it's too late) but it will be a lot of typing when you have to add a call to the function to each inflection form for quite a lot of templates. I saw people have already started using it. <tt>tr</tt> is also the parameter name used in many other templates. --Anatoli (обсудить/вклад) 02:19, 18 March 2013 (UTC)
 * Already quite widely used, intuitive to Wiktionary editors, and way shorter. Let's stick with <tt>tr</tt>. —Μετάknowledge discuss/deeds 02:44, 18 March 2013 (UTC)

Debugging
Is there an easy way to debug modules - walk trough the code to see the values of variables? --Anatoli (обсудить/вклад) 10:20, 17 March 2013 (UTC)

 * No, I don't think so. You should be able to use <tt>mw.log</tt> to write messages to the debug console, but nothing like a "debugger" like you might be used to from Visual Studio. —Ruakh TALK 22:53, 17 March 2013 (UTC)

Rewritten
I've rewritten this module using a different romanisation approach, and it appears to be less buggy now. Wyang (talk) 13:56, 12 April 2014 (UTC)
 * Unit tests say otherwise. And reading this code makes me cringe. — Keφr 18:17, 12 April 2014 (UTC)

Special:Contributions/184.148.173.136

 * Hi. I have reverted and protected the module but please review if it was justified. BTW, why did you change your name, your previous was much better!--Anatoli T. (обсудить/вклад) 02:41, 18 January 2022 (UTC)
 * No particular opinion on this particular edit. —Fish bowl (talk) 02:49, 18 January 2022 (UTC)
 * I was talking about "used as marker to represent the last consonant " (in pages such as 乭), not a syllable ending in ㄹ (such as ). --184.148.173.136 02:50, 18 January 2022 (UTC)
 * OK, thanks. I have undone my edit but prefer to keep the protection on highly used modules. Have you considered registering? --Anatoli T. (обсудить/вклад) 03:08, 18 January 2022 (UTC)

Is suppressing hyphens a good idea in 100% of cases?
Is this an exception where the Korean term shouldn't hide the hyphen:. It currently does, displays as "오스트리아헝가리", not "오스트리아-헝가리". Anatoli T. (обсудить/вклад) 05:53, 13 February 2023 (UTC)

Hanja is transliterated again?
Hi. It looks like hanja is being "transliterated" again. Pls check. It shows the suffix like this: "的 (的)". Anatoli T. (обсудить/вклад) 05:55, 24 February 2023 (UTC)

 * —Fish bowl (talk) 06:18, 24 February 2023 (UTC)
 * This should be fixed. Theknightwho (talk) 07:02, 24 February 2023 (UTC)

translit of words in T:head includes "page target + pipe + link text"
ko

말 • ( mal ) (foo 할 ( hada|hal ) )

as in 爲.

—Fish bowl (talk) 19:06, 5 March 2023 (UTC)

 * @Fish bowl This should be fixed. Theknightwho (talk) 20:28, 5 March 2023 (UTC)

title: Module talk:ko-translit


text: neturpinošajā

title: neturpinošajā


text: sargošie

title: sargošie


text: sargošajiem

title: sargošajiem


text: sargošajā

title: sargošajā


text: nesargošie

title: nesargošie


text: nesargošajiem

title: nesargošajiem


text: nesargošajā

title: nesargošajā


text: sargājošie

title: sargājošie


text: sargājošajiem

title: sargājošajiem


text: sargājošajā

title: sargājošajā


text: nesargājošie

title: nesargājošie


text: nesargājošajiem

title: nesargājošajiem


text: nesargājošajā

title: nesargājošajā


text: drošinošajos

title: drošinošajos


text: drošinošajās

title: drošinošajās


text: drošinošajai

title: drošinošajai


text: nedrošinošajos

title: nedrošinošajos


text: nedrošinošajās

title: nedrošinošajās


text: nedrošinošajai

title: nedrošinošajai


text: Module:ko-translit/documentation

title: Module:ko-translit/documentation


text: bagātinošajos

title: bagātinošajos


text: bagātinošajās

title: bagātinošajās


text: bagātinošajai

title: bagātinošajai


text: nebagātinošajos

title: nebagātinošajos


text: nebagātinošajās

title: nebagātinošajās


text: nebagātinošajai

title: nebagātinošajai


text: nabadzinošajos

title: nabadzinošajos


text: nabadzinošajās

title: nabadzinošajās


text: Module:Armn-translit/documentation

title: Module:Armn-translit/documentation


text: nabadzinošajai

title: nabadzinošajai


text: nenabadzinošajos

title: nenabadzinošajos


text: nenabadzinošajās

title: nenabadzinošajās


text: nenabadzinošajai

title: nenabadzinošajai


text: turpinošajos

title: turpinošajos


text: turpinošajās

title: turpinošajās


text: turpinošajai

title: turpinošajai


text: neturpinošajos

title: neturpinošajos


text: neturpinošajās

title: neturpinošajās


text: neturpinošajai

title: neturpinošajai


text: sargošajos

title: sargošajos


text: sargošajās

title: sargošajās


text: sargošajai

title: sargošajai


text: nesargošajos

title: nesargošajos


text: sargājošajos

title: sargājošajos


text: sargājošajās

title: sargājošajās


text: sargājošajai

title: sargājošajai


text: nesargājošajos

title: nesargājošajos


text: nesargājošajās

title: nesargājošajās


text: nesargājošajai

title: nesargājošajai


text: Category:Japanese terms spelled with 廬

title: Category:Japanese terms spelled with 廬


text:
bagātināms

Participle

 * 1) which can or should be enriched;

title: bagātināms


text:
nebagātināms

Participle

 * 1) which cannot or should not be enriched;

title: nebagātināms


text: Citations:anus

title: Citations:anus


text:
nabadzināms

Participle

 * 1) which can or should be impoverished;

title: nabadzināms


text: Citations:shitpost

title: Citations:shitpost


text:
nenabadzināms

Participle

 * 1) which cannot or should not be impoverished;

title: nenabadzināms


text: Category:Japanese terms spelled with 苺

title: Category:Japanese terms spelled with 苺


text:
turpināms

Participle

 * 1) which can or should be continued;

title: turpināms


text:
shitpost

Noun

 * 1)  A worthless or superficially meaningless post on a message board, newsgroup, or other online discussion platform. Often with the intended effect of derailing or otherwise distracting from relevant conversation.
 * 2)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.
 * 1)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.
 * 1)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.
 * 1)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.
 * 1)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.
 * 1)  A seemingly worthless or superficially meaningless image, video or piece of text posted to a social media platform that is intended to be humorously or ironically enjoyed.

Translations

 * Chinese:
 * Mandarin: 廢文
 * Esperanto: fekafiŝo
 * Finnish: paskapostaus
 * German: Scheißpfosten
 * Japanese: クソカキコ
 * Korean: 뻘글
 * Polish: kupost
 * Portuguese: merdapostagem

Verb

 * 1)  To make such a post.

Translations

 * Chinese:
 * Mandarin:
 * Finnish: paskapostata
 * Portuguese: merdapostar

title: shitpost


text: shitposts

title: shitposts


text: shitposting

title: shitposting


text: shitposted

title: shitposted


text:
neturpināms

Participle

 * 1) which cannot or should not be continued;

title: neturpināms


text:
sargāms

Participle

 * 1) which can or should be protected;

title: sargāms


text:
sargājams

Participle

 * 1) which can or should be protected;

title: sargājams


text: nesargošajās

title: nesargošajās


text: nesargošajai

title: nesargošajai


text:
nesargāms

Participle

 * 1) which cannot or should not be protected;

title: nesargāms


text:
nesargājams

Participle

 * 1) which cannot or should not be protected;

title: nesargājams


text: Category:Japanese terms spelled with 戌

title: Category:Japanese terms spelled with 戌


text: drošināmu

title: drošināmu


text: nedrošināmu

title: nedrošināmu