text:
Wiktionary:About Contemporary Arabic

This is an attempt to standardize the documentation of "Contemporary Arabic" terms, i.e. terms in the contemporary Arabic varieties. See WT:About Arabic for considerations relating to Modern Standard Arabic, and WT:About Arabic/Egyptian for a page discussing transliteration of Egyptian Arabic.

Being a think-tank draft, some of this page's proposals are nonstandard or disagreeable. The nonstandardest, disagreeablest ones are marked with the text [DISCUSS], but everything else on the page is open for discussion and editing as well.

Note that, while the goal of "unified Arabic" on Wiktionary is a good one to work toward (compare Chinese, with only one language header for all concerned varieties), this page operates under the assumption that each individual dialect or dialect group will be listed under its own heading.

Verbs

 * In verbs' headword lines, we follow up the standard past-tense lemma (e.g. ) with the 3sg.m nonpast subjunctive (e.g. ). For varieties where the "subjunctive" is not a distinct verb form, we instead use the least-inflected 3sg.m nonpast form accordingly. (Some current entries for Levantine or Egyptian instead show the present indicative, which has an unnecessary b- prefix.)
 * A North Levantine example:
 * Verb-conjugation tables list all possible conjugations, but cross out or highlight (in red) the implausible or unused ones.
 * Verb-conjugation tables list their respective varieties' "new passives", which are typically derived from or by analogy with the old active-voice reflexive verb forms (e.g.  ), as passive-voice conjugations. (Obviously, this doesn't apply to varieties that have preserved the internal-voweling passives.)
 * In entries for verbs that are both "new passives" and fossilized MSA loans of the aforementioned verb forms, e.g., we use an Etymology 1 heading for the latter and secondary etymologies for their passive-voice meanings.

Not verbs

 * For prefixes, and for prepositions that normally require object-pronoun suffixes, the main entry shows the base form (with no suffix) alongside an inflection-table template. If morphological conditions cause the morpheme to change form, then there will be another suffixless entry for the other form with the text "[condition] form of [main entry]." (e.g. ب/في in Levantine)
 * [DISCUSS] This works fine for examples like that can function without a pronoun suffix, but it starts to get awkward at e.g., and it gets really awkward around  and . Instead, perhaps the 3sg.m form should be the default for prepositions that require a suffix, giving Levantine , , and . The entries could list these definitions along with a qualifier that this is the 3sg.m form.

Arabic script

 * We do not represent with ئ if it is the first radical or if it is word-initial but preceded by a prefix. Instead, we only use إ. This gives لإنو  for some varieties' "because" (formerly under  as the lemma, which is not preferable), متإكد  "sure of", etc., but keeps   as is.
 * We spell the 3pl subject-conjugation suffix, also 1pl in the Maghreb, as — not . This isn't necessarily any "more correct", but it's an equally- or even a more-accepted spelling in most regions, so there's nothing wrong with preferring it.
 * The 3sg.m object suffix is spelled ـو in varieties where both (1) it is pronounced and (2) it is already customary among speakers to write it as ـو. Otherwise, it is spelled ـه.
 * Regarding verb forms incorporating the t-prefix, in varieties that elide its original /ta-/ vowel: if the resulting initial consonant cluster is allowed as is, like in Levantine, then the verb should not be written with an initial alif. But if the variety in question adds a short prosthetic vowel before this new cluster, as in Egyptian , then it is written with a hamza-less ا.

Transcription
As a rule of thumb, IPA transcription enumerates all recognizably distinct pronunciations, whereas Romanization aims to represent all possible pronunciations using as few transliterations as possible (by way of polyphony), and preferably only one transliteration.

All manners of transcription

 * [DISCUSS] and  should be transcribed as "VCC" rather than as "VVC". Morphologically they're VVC, as is plainly proven by a number of things[1], but on the surface they're pronounced and analyzed as VCC. Proof/notes:
 * The Arabic suffix has shifted in Egyptian Arabic into something resembling . One would expect  were the original sequence analyzed as VVC.
 * Urban North Levantine varieties show something that very much appears to be a distinction between the two: historic and  undergo h-elision into  and, which aren't intuitively interpretable as  and , whereas historic  and  remain  and . This gives, for example,  vs. . The other explanation would be that there's a hiatus there, but hiatus has always been verboten in Arabic to my knowledge — and native speakers in Lebanon consistently Romanize these as  and , rarely as  and.
 * Lastly, writing these patterns in this way also lets us match both Wiktionary's current MSA-Romanization scheme and the Arabic-script convention of writing a shadda on the semivowel consonant.
 * [1] ...the "number of things" being:
 * Dialectal " pl. ", or " pl. ", or " pl. ", etc. — the long ā in the plural is necessarily derived from a corresponding long vowel in the singular
 * The fact that can never be stressed in a heavy syllable in Lebanese Arabic, yet the word  has no issue with the first syllable being stressed, indicating that underlyingly it's not  but
 * We DO NOT represent word-final orthographic long vowels as phonemic (or phonetic) long vowels. They are phonetically pronounced and phonemically analyzed as short vowels — heck, they're even pronounced short in MSA, but at least declining to represent MSA pronunciation has a basis in diachronics. There is zero reason to do the same for contemporary Arabic.
 * The exception is in single-syllable words such as, all of which are monosyllabic in various lects and thus free to alternate between having a long and a short final vowel.
 * We always double underlyingly geminate consonants, which some may not double when the gemination isn't obvious in speech. and  for Levantine "2pl want", for example, not  and . This also goes for morphologically-doubled word-final consonants.
 * If, in some variety, there appears to be a word-initial vowel that mysteriously isn't preceded by a glottal stop when pronounced, then it really is a semivowel and we write it as such. (Currently, the Gulf Arabic entry for is in violation of this: the imperfective is spelled ikubb rather than ykubb.)
 * Stress can still be determined automatically if a long vowel is in a word's final three syllables or if a word is monosyllabic. However, we represent stress explicitly using an accent in the absence of these conditions, as it can be unpredictable otherwise. (Current Romanizations on Egyptian Arabic entries represent stress unconditionally, which looks cluttered — especially when the accent stacks on top of a vowel-length macron — and should not be necessary.)

IPA only

 * Again, IPA transcriptions enumerate all common and phonemically distinct variants within the given dialect or dialect group, where "common" is probably best defined as "recognizably present either in more than one country or all throughout a single country". This does leave out affectations like Lebanese rounding of post-emphatic, which (although recognizable) is a minority phenomenon in the big picture.

Romanization only
Our Romanization scheme is based on Wiktionary's current MSA Romanization, with the following exceptions and notes.

 * [DISCUSS] Use IPA, not their Hans Wehr equivalents. Not only are the apostrophic Hans Wehr marks hard to see and distinguish from one another, but their use also sort of feeds the West-centric misconception that the glottal stop & pharyngeal approximant/fricative are "not really consonant sounds" not deserving of their own letters. Besides,   are derived from the same apostrophes that Hans Wehr uses.
 * If this is implemented, we can actually retain and have it serve a good purpose: representing a word-initial glottal stop that is elidible, but only in some of the varieties that the transliteration concerns. For example, some (but not all) North Levantine speakers have pronouns like  rather than, but because both variants exist, "wʾana" could be used to bridge the gap. It would replace the clunkier "wʔana or wana".
 * [DISCUSS] On this topic, something needs to be done about Hans Wehr . Maybe. It's bad enough in MSA because it suggests a false pronunciation, but it's even worse now because there's certainly a phonemic contrast between and ; there may even be varieties with minimal pairs in the two! However, introducing an unnecessary orthographic contrast violates the "as few transliterations as possible" goal of Romanization, so it's best to discuss what exactly is warranted here. If distinguishing the two is a good idea, then the standard solution is presumably to use ◌̣	 U+0323 COMBINING DOT BELOW to create, but that's quite ugly and likely not displayable in the same way everywhere, so this will need to be discussed as well. (It's currently used in the Gulf entry for , if we want to see it in action.) A better workaround may be  (combining macron below) or  (combining dot above).
 * [DISCUSS] In pursuit of transliteration-homogenization, original Arabic * and * should be represented using and, because whether or not they monophthongize varies wildly depending on region and speaker. This way,  can be read as any of , , ,  without needing to write all four possibilities explicitly.
 * If this is implemented, then and  can contrastingly be used for the same monophthongs when they don't come from historic diphthongs (e.g., not ), and specifically when said monophthongs can't diphthongize under any conditions whatsoever in any variety. (For example, the  in the loanword بنطلون "pants" (compare English pantaloons) can diphthongize in Lebanon, despite not being from a historic diphthong, and so the word might ideally be transliterated  rather than .)
 * An imaala'd (or otherwise affected) alif is still an alif, and the presence of affectations like raising can vary greatly within any given region. We therefore represent it using invariably.
 * Short vowels:
 * Certain varieties, particularly Saudi and Bedouin lects, have a phonemic distinct from  and typically corresponding to a damma. We represent it using a  in Romanization, too. Similarly, some varieties like Moroccan Arabic have a phonemic contrast between  and, and so we use the same characters appropriately in Romanization.
 * Otherwise, we use for all kasras and  for all dammas.
 * [DISCUSS] Current Gulf Arabic entries use IPA in Romanization for a kasra. Should this be kept...? Or replaced with  as below?
 * [DISCUSS] Levantine varieties have many, many words where the vowel can and often does alternate between with no semantic effect. Perhaps find a single symbol to transliterate this vowel with, e.g. a dotless.
 * Use for the epenthetic high vowel some varieties use to break up consonant clusters, not . However, this should be used sparingly. Some potentially acceptable contexts for it...
 * when the epenthetic is stressed as in Gulf Arabic (see the "ghəwa" phenomenon, although it's best-modeled here by verbs such as يشربه jəšerba(h): insertion of an epenthetic consonant followed by a stress shift to it)
 * in usage-example transliterations, to preserve the flow of a sentence (e.g. )
 * as a syllabification aid? (e.g. ; the first suggests a syllabic /s/)
 * At the end of a word, use and  for the corresponding historic long vowels. Use  for the 3sg.m suffix in varieties where it's pronounced as such.
 * [DISCUSS] The feminine suffix, historically *, varies in its modern pronunciation between and  depending on lect and phonological environment. Should a word ending in it be simply transcribed as "[...]a or [...]e"? (That seems to run counter to the goal of flattening out variation here.) Or should a single character be used to represent it, and if so, what character?  looks handy.

Dialect specifics
This section will ideally be added to, as time passes, by contributors experienced in individual dialects (which warrant more-specific considerations than the generalities above).

Egyptian Arabic

 * The conventional Egyptian spelling of Arabic is, so main entries in Egyptian Arabic go under a title with ـه. There then can be a separate page titled with the ـة spelling, containing an Egyptian Arabic definition that uses the "alternate form of" template. (We also follow the first part when determining Arabic spelling in quotes, usage examples, etc.)
 * Ditto for when it represents.

Levantine Arabic

 * The conventional Levantine spelling of Arabic ـة is not ـه. This means that Levantine entries and writings on Wiktionary do not use ـه when representing Arabic ـة.
 * Additionally, Levantine ـة is typically pronounced as when imaala applies, not as . Therefore, we never, ever transcribe or Romanize it using, particularly to avoid confusion in transliteration with word-final.
 * However, North Levantine is one of the varieties, mentioned above, where it is customary to spell the 3sg.m object suffix as ـو rather than as ـه. We therefore spell it ـو for such entries on Wiktionary.
 * Following are Levantine's "word-initial hamza" rules, which are descriptions of pronunciation that we refer to when spelling (in Arabic) and transcribing (in Romanization or IPA).
 * Imperative Form I verbs invariably start with a glottal stop when constructed on . If instead constructed on, there is never a glottal stop.
 * The past tense and imperative of any verb whose perfective starts with a kasra (namely, verbs of Form VII and higher) do not start with a glottal stop. Instead, they start with a two-consonant cluster. For example,.
 * However, the verbal nouns of such verbs do start with a glottal stop. For example,, which differs from Modern Standard Arabic . (The first-person present subjunctive does as well, of course.)
 * Any other word, if it sounds like it starts with a glottal stop, always does. This includes pronouns such as and.
 * The of the word for "what" can sometimes cause elision of a following  in common collocations, such as  and . However, this is a unique case of elision, and it's not reason enough to write the base words as, for example, اسم and especially اخبار. (What is reason enough to write اسم that way is its history, but that's another story.)

title: Wiktionary:About Contemporary Arabic


text: Category:Korean terms by script

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

title: Category:Korean terms by script


text: Category:Terms in Han script by language


text: Category:Old French terms in Hebrew script


text: Category:Old French terms by script

title: Category:Old French terms by script


text: Category:Terms in Hebrew script by language


text: high-tails it

title: high-tails it


text: high-tailing it

title: high-tailing it


text: high-tailed it

title: high-tailed it


text:
Nullarbor

Etymology
From, as the area is nearly treeless.

Proper noun

 * , Australia.
 * 1)  and.
 * 1)  and.
 * 1)  and.
 * 1)  and.

title: Nullarbor


text: Category:Lü terms in New Tai Lue script

title: Category:Lü terms in New Tai Lue script


text: Category:Terms in New Tai Lue script by language


text: Category:Lü terms by script

title: Category:Lü terms by script


text: Category:Lü terms by orthographic property


text:
dewrinkle

Verb

 * 1)  To remove the wrinkles from; to smooth.
 * 2)  To become unwrinkled or less wrinkled.
 * 1)  To become unwrinkled or less wrinkled.
 * 1)  To become unwrinkled or less wrinkled.
 * 1)  To become unwrinkled or less wrinkled.

title: dewrinkle


text: dewrinkles

title: dewrinkles


text: dewrinkling

title: dewrinkling


text: dewrinkled

title: dewrinkled


text: はつひので

title: はつひので


text: Hatsu Hinode

title: Hatsu Hinode


text:
กังหัน

Etymology
From.

Noun

 * 1) turbine; windmill; pinwheel.

title: กังหัน


text: dermabrasing

title: dermabrasing


text: dermabrased

title: dermabrased


text:
กังหันลม

Etymology
From 🇰🇲,.

Noun

 * 1) wind turbine.

title: กังหันลม


text:
กังหันน้ำ

Etymology
From 🇰🇲. .

Noun

 * 1) water turbine.

title: กังหันน้ำ


text:
กังหันไอน้ำ

Etymology
From 🇰🇲. .

Noun

 * 1) steam turbine.

title: กังหันไอน้ำ


text: zòuzhé

title: zòuzhé


text: Yōngzhèng

title: Yōngzhèng


text:
swap partition

Etymology
So called because data can be swapped between memory and this partition.

Noun

 * 1)  A disk partition designated as auxiliary memory, used primarily on Unix and Linux systems.

title: swap partition


text:
เครื่องจักรไอน้ำ

Etymology
From 🇰🇲. .

Noun

 * 1) steam engine.

title: เครื่องจักรไอน้ำ


text:
swap space

Etymology
So called because data can be swapped between memory and this space.

Noun

 * 1)  Space on a hard disk used as auxiliary memory.

title: swap space


text:
file association

Noun

 * 1)  The association of a file type with a program, so that the chosen program is the default for opening files of that type.

Translations

 * Chinese:
 * Mandarin: 文件關聯
 * Finnish: tiedostokytkentä
 * Japanese: 拡張子の関連付け, ファイルの関連付け, 関連付け

title: file association


text: ocupao

title: ocupao


text: ocupaos

title: ocupaos


title: Template:R:trk:Dybo:2007


text: ocupaes

title: ocupaes


text: gòujià

title: gòujià


text:
鄂倫春

Etymology
Borrowed from.

Proper noun

 * 1) Oroqen
 * 2)  Oroqen nationality
 * 3)  Oroqen Banner

title: 鄂倫春


text:
전역

Etymology 1
.

Noun

 * 1) military campaign

Etymology 2
.

Noun

 * 1) the entire area; the entire territory

title: 전역


text: Template:table:zodiac/nl

title: Template:table:zodiac/nl


text:
수질

Etymology
.

Noun

 * 1) water quality

title: 수질


text:
夷務

Noun

 * 1)  foreign affairs

title: 夷務


text: 夷务

title: 夷务


text: Dàoguāng

title: Dàoguāng


text:
會典

Noun

 * 1) collected statutes ; records of imperial laws and regulations

title: 會典


text: 会典

title: 会典


text: huìdiǎn

title: huìdiǎn


text:
tetramethylcyclopropane

Noun

 * 1)  A chemical compound with four methyl groups connected to a cyclopropane ring.

title: tetramethylcyclopropane


text: Category:Terms by script subcategories by language


text:
ไซเรน

Etymology
From.

Noun

 * 1)  siren.
 * 2) siren: device creating a loud wailing sound, especially as a warning or signal.

title: ไซเรน


text: Category:Okinawan verb forms

title: Category:Okinawan verb forms


text:
godt gået

Etymology
🇰🇲

Adverb

 * 1) well done

title: godt gået


text:
mi o vuku a vuk na vrata

Etymology
Literally, “we(’re talking) about the wolf and the wolf is at the door”, with the verb implied but left unexpressed.

Proverb

 * 1) speak of the devil and he shall appear

title: mi o vuku a vuk na vrata


text:
प्रभाकर

Etymology
From 🇰🇲.

Noun

 * 1) ‘light-maker’, the sun (du. sun and moon)
 * 2) the moon
 * 3) fire

Proper noun

 * 1) a name of Siva
 * 2) the name of a class of deities under the 8th Manu
 * 3) the name of a serpent-demon
 * 4) the name of a sage of the race of Atri

title: प्रभाकर


text:
Module:User:Benwing2/accel

local export = {}

local rsplit = mw.text.split local u = mw.ustring.char local MARK_CONJOINED_SHORTCUT = u(0xFFF0) local split_term_regex = "%*~!"

local m_table = require("Module:table") local form_of_module = "Module:User:Benwing2/form of"

--[=[ The purpose of the acceleration code is to auto-generate pages for non-lemma forms (inflections) of a given lemma. The way it works is approximately as follows:

1. When you have the accelerator gadget in MediaWiki:Gadget-AcceleratedFormCreation.js enabled, and you click on a  green link, the JavaScript code gathers all the green links on the page that have the same language and pagename as   the clicked-on green link and sends them to the generate_JSON function in this module, which is a thin wrapper around the generate function. Each individual green link maps to an "entry" and has associated accelerator properties that were specified by the `accel` object passed into full_link in Module:links. Note that there can -- be multiple entries passed to a single generate call for various reasons, e.g.: (1) Inside of a single inflection table there is syncretism, with two different inflections having the same form; e.g. the same Latin form bonī occurs in three different inflections of the lemma bonus: the masculine genitive singular, neuter genitive singular and masculine nominative plural. Hence there will be three entries. (2) Inside of a single inflection table there are inflections that are spelled differently but map to the same pagename due to diacritic removal; e.g. Latin bona (occurring in five different inflections: the feminine	  nominative and vocative singular and the neuter nominative, accusative and vocative plural) and Latin bonā (the feminine ablative singular) will be merged together into a single call to generate with six entries. (3) There are two or more inflection tables, partly or completely duplicative. E.g. if a given lemma has Etymology 1 and Etymology 2 sections, and the inflection of each separate etymology is the same and associated with its own table, then clicking on any green link will result in (at least) two entries.

2. The generate function is invoked like a template call, meaning all its arguments come as strings and need to be  parsed. It does the following steps:

(1) Parse its arguments. (2) Convert each set of per-entry parameters into a `params` object. (3) For each `params` object, generate a default entry, then, if there is a language-specific accelerator submodule, call that module to customize the entry. (4) Merge duplicate entries. This not only looks for completely duplicated entries but tries to merge entries that differ only in the definition. In general, this will result in multiple definition lines under a single entry, but definition lines that consist of calls to will be further merged. For example, for the example above with bona and bonā, the five inflections of bona will be merged into a single entry with a single call to that looks something like this: # 	  In other words, not only are the inflections combined into a single call to, but inflections with partly shared tags are further merged. (5) Generate the Pronunciation and Etymology sections that go at the top, above all the entries. This is done either by calling custom generate functions in the language-specific accelerator submodule, or (if those aren't given) by merging the individual pronunciation and etymology lines, removing duplicates. Note that the default entry generated in step (3) has no pronunciation or etymology (which are generated only by a language-specific	  submodule), so by default there will be no Pronunciation or Etymology section. (6) Assemble the parts of each entry into a string and paste all the strings together, along with any combined Pronunciation and Etymology sections, to form the text of the entire per-language L2 section. Note that if you have enabled the OrangeLinks gadget, accelerator entries can be created on already-existing pages, as long as there's no L2 section for the language of the entries. ]=]

-- A simple implementation of an ordered set. local function create_ordered_set return { array = {}, set = {}, } end

-- Add an item to the ordered set. `squashed_item` is a representation of the item as a string or number, so that we -- can use it as the key in a set. `orig_item` is the original item and can be omitted if it's the same as -- `squashed_item`. local function add_item(ordered_set, squashed_item, orig_item) if not ordered_set.set[squashed_item] then table.insert(ordered_set.array, orig_item or squashed_item) ordered_set.set[squashed_item] = true end end

-- Generate the default entry function export.default_entry(params) local function make_head(pos, default_gender) local gender = params.gender or default_gender local genderspec = "" if gender then local genders = rsplit(gender, ",") for i, g in ipairs(genders) do				if i == 1 then genders[i] = "|g=" .. g				else genders[i] = "|g" .. i .. "=" .. g				end end genderspec = table.concat(genders) end local parts = {} table.insert(parts, "") return table.concat(parts) end

local function make_def(tempname, extra_params) local parts = {} table.insert(parts, "") return table.concat(parts) end

local function no_rule_error(params) -- FIXME, verify the 2 below (number of stack frames to pop off); may be wrong now that we moved this function -- underneath default_entry. return error(('No rule for "%s" in language "%s" ("%s").')			:format(params.form, params.lang:getCode, params.lang:getCanonicalName), 2) end

local entry = { etymology = nil, pronunc = nil, pos_header = mw.getContentLanguage:ucfirst(params.pos), head = make_head(params.pos .. " form"), def = make_def("infl of", "||" .. params.form), inflection = nil, declension = nil, conjugation = nil, mutation = nil, altforms = nil, -- also pass in functions make_head = make_head, make_def = make_def, no_rule_error = no_rule_error, }

-- Exceptions for some forms local templates = { ["p"] = "plural of", ["f"] = "feminine of", ["f|s"] = "feminine singular of", ["m|p"] = "masculine plural of", ["f|p"] = "feminine plural of", ["pejorative"] = "pejorative of", }

if params.form == "comparative" or params.form == "superlative" or params.form == "equative" then entry.head = make_head(params.form .. " " .. params.pos) entry.def = make_def(params.form .. " of", params.pos ~= "adjective" and "|POS=" .. params.pos or "") elseif params.form == "diminutive" or params.form == "augmentative" then entry.head = make_head(params.pos) entry.def = make_def(params.form .. " of", params.pos ~= "noun" and "|POS=" .. params.pos or "") elseif params.form == "f" and params.pos == "noun" then entry.head = make_head(params.pos, "f") entry.def = make_def("female equivalent of") elseif (params.form == "past|part" or params.form == "past|ptcp") and params.pos == "verb" then entry.pos_header = "Participle" entry.head = make_head("past participle") elseif (params.form == "pres|part" or params.form == "pres|ptcp") and params.pos == "verb" then entry.pos_header = "Participle" entry.head = make_head("present participle") elseif (params.form == "abstract noun" or params.form == "verbal noun") and params.pos == "noun" then entry.head = make_head(params.pos) entry.def = make_def(params.form .. " of") elseif templates[params.form] then entry.def = make_def(templates[params.form]) end

return entry end

-- Canonicalize multipart shortcuts (e.g. "123" -> "1//2//3") and non-conjoined list shortcuts (e.g. "1s" -> -- {"1", "s"}); leave others alone, including conjoined shortcuts. The purpose of canonicalizing list shortcuts is so -- that e.g. we can combine '1s|pres|ind' with '2|s|pres|ind'. However, conjoined shortcuts like "e-form" -> -- {"pl", ";", "def", "s", "attr"} would require significantly more logic to handle correctly, and it's highly unlikely -- we could find another similar enough tag to combine with (if it even makes sense to do so at all). local function canonicalize_multipart_and_list_shortcuts(tags, lang) local result = {} for _, tag in ipairs(tags) do		local expansion = require(form_of_module).lookup_shortcut(tag, lang) if type(expansion) == "string" and not expansion:find("//", nil, true) then expansion = tag end if type(expansion) == "table" then if m_table.contains(expansion, ";") then table.insert(result, tag) else m_table.extendList(result, expansion) end else table.insert(result, expansion) end end return result end

-- Split a multipart tag into component tags, normalize each component, and return the resulting list. If -- MAP_TO_CANONICAL_SHORTCUT is given, attempt to map each normalized component tag to its "canonical shortcut", i.e. -- the first shortcut listed among its shortcuts. -- -- If given a two-level multipart tag such as "1:sg//3:pl", the resulting return value will be {"first:singular", -- "third:plural"}, or {"1:s", "3:p"} if MAP_TO_CANONICAL_SHORTCUT is given. local function split_and_normalize_tag(tag, lang, map_to_canonical_shortcut) local m_form_of = require(form_of_module) local normalized = m_form_of.normalize_tag_set({tag}, lang) if #normalized > 1 then -- Tag is a conjoined shortcut. We leave these in their non-canonicalized form; see comment above -- canonicalize_multipart_and_list_shortcuts. But we mark them with a special character so we know that -- they are non-normalized conjoined shortcuts, and later remove the mark. return {tag .. MARK_CONJOINED_SHORTCUT} end normalized = normalized[1] assert(#normalized == 1, "Internal error: Encountered list tag " .. tag .. ", which should have been canonicalized earlier") local multipart = normalized[1] if type(multipart) == "string" then multipart = {multipart} end if map_to_canonical_shortcut then local function get_canonical_shortcut(tag, lang) local tagobj = m_form_of.lookup_tag(tag, lang) local tag_shortcuts = tagobj and tagobj[m_form_of.SHORTCUTS] if tag_shortcuts and type(tag_shortcuts) == "table" then tag_shortcuts = tag_shortcuts[1] end return tag_shortcuts or tag end for i, mpart in ipairs(multipart) do			if type(mpart) == "table" then -- two-level multipart for j, single_tag in ipairs(mpart) do					mpart[j] = get_canonical_shortcut(single_tag, lang) end multipart[i] = table.concat(mpart, ":") else multipart[i] = get_canonical_shortcut(mpart, lang) end end else for i, mpart in ipairs(multipart) do			if type(mpart) == "table" then -- two-level multipart multipart[i] = table.concat(mpart, ":") end end end return multipart end

-- Given a normalized tag, return its tag type, or "unknown" if a tag type -- cannot be located (either the tag isn't recognized or for some reason -- it doesn't specify a tag type). local function get_normalized_tag_type(tag, lang) -- Make sure to return 'unknown' for non-normalized conjoined shortcuts as well as URL's and parts of two-level -- multipart tags (both of the latter two have colons in them). NOTE: In practice, the presence of the -- MARK_CONJOINED_SHORTCUT means we won't find a normalized tag having the same name even if one would exist in the -- absence of this mark, so this is more of an optimization. if tag:find(MARK_CONJOINED_SHORTCUT) or tag:find(":") then return "unknown" end local m_form_of = require(form_of_module) local tagobj = m_form_of.lookup_tag(tag, lang) return tagobj and tagobj[m_form_of.TAG_TYPE] or "unknown" end

--[=[ Combine multiple semicolon-separated tag sets into multipart tags if possible. We combine tag sets that differ in only one tag in a given dimension, and repeat this until no changes in case we can reduce along multiple dimensions, e.g.

`tag_sets` is a list of objects of the form {tags = {"TAG", "TAG", ...}, labels = {"LABEL", "LABEL", ...}}, i.e. of the same format as `data.tag_sets` as passed to tagged_inflections in Module:form of. Also accepted is an "old-style" list of strings, one element per tag, with tag sets separated by a semicolon, the same as in.

The return value is in the same format as was passed into `tag_sets`. If an old-style tag list was passed in, and labels are present, they are attached to the last tag in a tag set using an inline modifier. ]=]

function export.combine_tag_sets_into_multipart(tag_sets, lang, POS) if type(tag_sets) ~= "table" then error("`tag_sets` should be a table but is a(n) `" .. type(tag_sets) .. "`") end if not tag_sets[1] then error("Expected at least one item in `tag_sets`") end local old_style_tags = false if type(tag_sets[1]) == "string" then old_style_tags = true end

-- First, as an optimization, make sure there are multiple tag sets. Otherwise, do nothing. if old_style_tags then local found_semicolon = false for _, tag in ipairs(tag_sets) do			if tag == ";" then found_semicolon = true break end end if not found_semicolon then return tag_sets end elseif #tag_sets == 1 then return tag_sets end

local m_form_of = require(form_of_module)

-- If old-style tags (list of strings), convert to list of tag set objects. if old_style_tags then tag_sets = m_form_of.split_tags_into_tag_sets(tag_sets) for i, tag_set in ipairs(tag_sets) do			tag_sets[i] = m_form_of.parse_tag_set_properties(tag_set) end else -- Otherwise, make a copy as we may modify the list in-place. tag_sets = m_table.deepcopy(tag_sets) end

-- Repeat until no changes can be made. while true do -- First, determine the auto-generated label for each tag set and append to any user-specified labels. -- Best to do this on the raw tag sets, before canonicalize_multipart_and_list_shortcuts. Then canonicalize -- 1s etc. into 1|s. for i, tag_set in ipairs(tag_sets) do			tag_set.labels_with_auto = m_table.deepcopy(tag_set.labels or {}) local normalized_tag_sets = m_form_of.normalize_tag_set(tag_set.tags, lang) for _, normalized_tag_set in ipairs(normalized_tag_sets) do				local this_categories, this_labels = m_form_of.fetch_categories_and_labels(normalized_tag_set, lang, POS) m_table.extendList(tag_set.labels_with_auto, this_labels) end tag_set.tags = canonicalize_multipart_and_list_shortcuts(tag_set.tags, lang) end

local canonicalized_tag_sets = tag_sets local old_canonicalized_tag_sets = canonicalized_tag_sets

-- Try combining in two different styles ("adjacent-first" = do two passes, where the first pass only combines		-- adjacent tag sets, while the second pass combines nonadjacent tag sets; "all-first" = do one pass combining		-- nonadjacent tag sets). Sometimes one is better, sometimes the other. --		-- An example where adjacent-first is better: --		-- 		--		-- all-first results in		-- -- 		--		-- which isn't ideal. --		-- If we do adjacent-first, we get --		-- 		--		-- which is much better. --		-- The opposite happens in		-- -- 		--		-- where all-first results in		-- -- 		--		-- which is better than the result from adjacent-first, which is		-- -- 		--		-- To handle this conundrum, we try both, and look to see which one results in fewer "combinations" (where a		-- tag with // in it counts as a combination). If both are different but have the same # of combinations, we -- prefer adjacent-first, we seems generally a better approach.

local tag_sets_by_style = {}

for _, combine_style in ipairs({"adjacent-first", "all-first"}) do -- Now, we do two passes. The first pass only combines adjacent tag sets, while the second pass combines -- nonadjacent tag sets. Copy canonicalized_tag_sets, since we destructively modify the list. local this_tag_sets = m_table.deepcopy(canonicalized_tag_sets) local combine_passes if combine_style == "adjacent-first" then combine_passes = {"adjacent", "all"} else combine_passes = {"all"} end for _, combine_pass in ipairs(combine_passes) do				local tag_ind = 1 while tag_ind <= #this_tag_sets do					local from, to					if combine_pass == "adjacent" then if tag_ind == 1 then from = 1 to = 0 else from = tag_ind - 1 to = tag_ind - 1 end else from = 1 to = tag_ind - 1 end local inner_broken = false for prev_tag_ind = from, to do						local cur_tag_set = this_tag_sets[prev_tag_ind] local tag_set = this_tag_sets[tag_ind] if #cur_tag_set.tags == #tag_set.tags and m_table.deepEquals(cur_tag_set.labels_with_auto, tag_set.labels_with_auto) then local mismatch_ind = nil local innermost_broken = false for i = 1, #tag_set.tags do								local tag1 = split_and_normalize_tag(cur_tag_set.tags[i], lang) local tag2 = split_and_normalize_tag(tag_set.tags[i], lang) if not m_table.deepEquals(m_table.listToSet(tag1), m_table.listToSet(tag2)) then if mismatch_ind then innermost_broken = true break end local combined_dims = {} for _, tag in ipairs(tag1) do										combined_dims[get_normalized_tag_type(tag, lang)] = true end for _, tag in ipairs(tag2) do										combined_dims[get_normalized_tag_type(tag, lang)] = true end if m_table.size(combined_dims) == 1 and not combined_dims["unknown"] then mismatch_ind = i									else innermost_broken = true break end end end if not innermost_broken then -- No break, we either match perfectly or are combinable if not mismatch_ind then -- Two identical tag sets table.remove(this_tag_sets, tag_ind) inner_broken = true break else -- Combine tag sets at mismatch_ind, using the canonical shortcuts. tag1 = cur_tag_set.tags[mismatch_ind] tag2 = tag_set.tags[mismatch_ind] tag1 = split_and_normalize_tag(tag1, lang, true) tag2 = split_and_normalize_tag(tag2, lang, true) -- Combine the normalized tags and remove the special MARK_CONJOINED_SHORTCUT mark -- on conjoined shortcuts so we have normal tags again. local combined_tag = table.concat(m_table.append(tag1, tag2), "//"):gsub(MARK_CONJOINED_SHORTCUT, "") local new_tag_set = {} for i = 1, #cur_tag_set.tags do										if i == mismatch_ind then table.insert(new_tag_set, combined_tag) else local cur_canon_tag = split_and_normalize_tag(cur_tag_set.tags[i], lang) local canon_tag = split_and_normalize_tag(tag_set.tags[i], lang) assert(m_table.deepEquals(m_table.listToSet(cur_canon_tag), m_table.listToSet(canon_tag))) table.insert(new_tag_set, cur_tag_set.tags[i]) end end this_tag_sets[prev_tag_ind].tags = new_tag_set table.remove(this_tag_sets, tag_ind) inner_broken = true break end end end end if not inner_broken then -- No break from inner for-loop. Break from that loop indicates that we found that the current -- tag set can be combined with a preceding tag set, did the combination and deleted the -- current tag set. The next iteration then processes the same numbered tag set again (which is						-- actually the following tag set, because we deleted the tag set before it). No break -- indicates that we couldn't combine the current tag set with any preceding tag set, and need -- to advance to the next one. tag_ind = tag_ind + 1 end end end tag_sets_by_style[combine_style] = this_tag_sets end

if not m_table.deepEquals(tag_sets_by_style["adjacent-first"], tag_sets_by_style["all-first"]) then local function num_combinations(group) local num_combos = 0 for _, tag_set in ipairs(group) do					for _, tag in ipairs(tag_set.tags) do						if tag:find("//") then num_combos = num_combos + 1 end end end return num_combos end

local num_adjacent_first_combos = num_combinations(tag_sets_by_style["adjacent-first"]) local num_all_first_combos = num_combinations(tag_sets_by_style["all-first"]) if num_adjacent_first_combos < num_all_first_combos then tag_sets = tag_sets_by_style["adjacent-first"] elseif num_all_first_combos < num_adjacent_first_combos then tag_sets = tag_sets_by_style["all-first"] else tag_sets = tag_sets_by_style["adjacent-first"] end else -- Both are the same, pick either one tag_sets = tag_sets_by_style["adjacent-first"] end

if m_table.deepEquals(tag_sets, old_canonicalized_tag_sets) then break end -- FIXME, we should consider reversing the transformation 1s -> 1|s, -- but it's complicated to figure out when the transformation occurred; -- not really important as both are equivalent end

if old_style_tags then local retval = {} for _, tag_set in ipairs(tag_sets) do			if tag_set.labels and #tag_set.labels > 0 then tag_set.tags[#tag_set.tags] = tag_set.tags[#tag_set.tags] .. ""			end if #retval > 0 then table.insert(retval, ";") end m_table.extendList(retval, tag_set.tags) end return retval else for _, tag_set in ipairs(tag_sets) do			tag_sets.labels_with_auto = nil end return tag_sets end end

-- Test function, callable externally. function export.test_combine_tag_sets_into_multipart(frame) local iparams = { [1] = {list = true, required = true}, lang = {required = true}, }

local args = require("Module:parameters").process(frame.args, iparams) local lang = require("Module:languages").getByCode(args.lang, true) local combined_tags = export.combine_tag_sets_into_multipart(args[1], lang) return table.concat(combined_tags, "|") end

-- Check whether `entry` (an object describing a given non-lemma form, with properties such as `pronunc` for -- pronunciation, `def` for definition, etc.) can be merged with any of the existing entries listed in `candidates`. -- "Can be merged" means that all relevant properties (basically, everything but the definition) can are the same. -- Return the first such candidate found, or nil if no candidates match `entry`. local function find_mergeable(entry, candidates) local function can_merge(candidate) for _, key in ipairs({"pronunc", "etymology", "pos_header", "head", "inflection", "declension", "conjugation", "altforms"}) do			local val1 = entry[key] local val2 = candidate[key] local is_equal -- `pronunc` and `etymology` could be tables; the default code for merging pronunciation and etymology can -- handle tables of strings. if type(val1) == "table" and type(val2) == "table" then is_equal = m_table.deepEquals(val1, val2) else is_equal = val1 == val2 end

if not is_equal then return false end end

return true end

for _, candidate in ipairs(candidates) do		if can_merge(candidate) then return candidate end end

return nil end

-- Merge multiple entries into one if they differ only in the definition, with all other -- properties the same. The combined entry has multiple definition lines. We then do -- further frobbing of lines: -- -- 1. Convert lang= param to param 1 (there shouldn't be any remaining cases of accelerator --   modules generating  templates with lang=, but we do this just in case). -- 2. Combine adjacent lines that differ only in the tags, e.g.: -- --   # --    # --    # --    # -- --    becomes -- --   # -- -- 3. Further group  lines with multiple tag sets (as may be generated b y --    the previous step) using multipart tags, e.g. for the Latin entry bonum, -- --   # -- --    becomes -- --   # -- --    This grouping can group across multiple dimensions, e.g. for the Latin entry bonīs, -- --   # -- --    becomes -- --   # -- --    Another complex real-world example, for the Old English weak adjective form dēorenan: -- --   # -- --    becomes -- --   # -- --    Here, 17 separate tag sets are combined down into 3. local function merge_entries(entries_obj) local entries_new = {}

-- First rewrite to 	for _, entry in ipairs(entries_obj.entries) do		local params = entry.def:match("^$") if not params then params = entry.def:match("^$") end if params then params = rsplit(params, "|", true) local new_params = {} for _, param in ipairs(params) do				local lang = param:match("^lang=(.*)$") if lang then table.insert(new_params, 1, lang) else table.insert(new_params, param) end end entry.def = "" end end

-- Merge entries that match in all of the following properties: -- "pronunc", "etymology", "pos_header", "head", "inflection", "declension", "conjugation", "altforms" -- This will merge any two mergeable entries even if non-consecutive. -- The definitions of the merged entries do not have to match, but any matching -- definitions will be deduped. for _, entry in ipairs(entries_obj.entries) do -- See if this entry can be merged with any previous entry. local merge_entry = find_mergeable(entry, entries_new)

if merge_entry then local duplicate_def = false -- If we can merge, check whether the definition of the new entry is -- the same as any previous definitions. for _, def in ipairs(merge_entry.defs) do				if def == entry.def then duplicate_def = true break end end

if not duplicate_def then table.insert(merge_entry.defs, entry.def) end else entry.defs = {entry.def} table.insert(entries_new, entry) end end

-- Combine the definitions for each entries, merging all calls -- into one such call with multiple tag sets. for _, entry in ipairs(entries_new) do		local existing_defs = {} for _, new_def in ipairs(entry.defs) do			local did_merge = false local new_params = new_def:match("^$") if not new_params then new_params = entry.def:match("^$") end if new_params then -- The new definition is. See if there is an -- among the definitions seen so far. for i, existing_def in ipairs(existing_defs) do					local existing_params = existing_def:match("^$") if not existing_params then existing_params = existing_def:match("^$") end if existing_params then -- Merge the existing and new calls. -- Find the last unnamed parameter of the first template. existing_params = rsplit(existing_params, "|", true) local last_numbered_index

for j, param in ipairs(existing_params) do							if not param:find("=", nil, true) then last_numbered_index = j							end end

-- Add grammar tags of the second template new_params = rsplit(new_params, "|") local tags = {} local n = 0

for k, param in ipairs(new_params) do							if not param:find("=", nil, true) then n = n + 1

-- Skip the first three unnamed parameters, -- which don't indicate grammar tags if n >= 4 then -- Now append the tags table.insert(tags, param) end end end

-- Add the new parameters after the existing ones existing_params[last_numbered_index] = existing_params[last_numbered_index] .. "|;|" .. table.concat(tags, "|") existing_defs[i] = "" did_merge = true break end end end

if not did_merge then table.insert(existing_defs, new_def) end end

entry.def = table.concat(existing_defs, "\n# ") end

-- Now combine tag sets inside a multiple-tag-set call for i, entry in ipairs(entries_new) do		local infl_of_params = entry.def:match("^$") if not infl_of_params then infl_of_params = entry.def:match("^$") end if infl_of_params then infl_of_params = rsplit(infl_of_params, "|", true)

-- Find the last unnamed parameter local last_numbered_index

for j, param in ipairs(infl_of_params) do				if not param:find("=", nil, true) then last_numbered_index = j				end end

-- Split the params in three: -- (1) Params before the inflection tags, and any named params mixed in with the tags -- (2) The tags themselves -- (3) Named params after the tags local pre_tag_params = {} local tags = {} local post_tag_params = {} local n = 0

for j, param in ipairs(infl_of_params) do				if not param:find("=", nil, true) then n = n + 1

-- Skip the first three unnamed parameters, which don't indicate grammar tags if n >= 4 then table.insert(tags, param) else table.insert(pre_tag_params, param) end elseif n >= last_numbered_index then table.insert(post_tag_params, param) else table.insert(pre_tag_params, param) end if not param:find("=", nil, true) then last_numbered_index = j				end end

-- Now combine tag sets. tags = export.combine_tag_sets_into_multipart(tags, entries_obj.lang)

-- Put the template back together. local combined_params = m_table.append(pre_tag_params, tags, post_tag_params) entry.def = "" end end

entries_obj.entries = entries_new end

local function merge_field(entries, field) local seen_fields = create_ordered_set for _, entry in ipairs(entries) do		local fieldval = entry[field] if fieldval then if type(fieldval) == "table" then -- already a table else fieldval = rsplit(fieldval, "\n") end for _, val in ipairs(fieldval) do				if val ~= "" then -- skip newlines, including if there's a final newline when split add_item(seen_fields, val) end end end end return seen_fields.array end

local function default_merge_pronunciation(entries_obj) local pronuncs = merge_field(entries_obj.entries, "pronunc") if #pronuncs > 0 then return table.concat(pronuncs, "\n") else return nil end end

local function generate_merged_pronunciation(entries_obj) if entries_obj.lang_module and entries_obj.lang_module.generate_pronunciation then entries_obj.pronunciation = lang_module.generate_pronunciation(entries_obj) else entries_obj.pronunciation = default_merge_pronunciation(entries_obj) end end

local function default_merge_etymology(entries_obj) local etyms = merge_field(entries_obj.entries, "etymology") if #etyms > 1 then -- Hack! If multiple etymology entries, put a * before each one so they don't run together. -- In such a case we may be better off using a custom merge function. for i, item in ipairs(etyms) do etyms[i] = "* " .. item end end if #etyms > 0 then return table.concat(etyms, "\n") else return nil end end

local function generate_merged_etymology(entries_obj) if entries_obj.lang_module and entries_obj.lang_module.generate_etymology then entries_obj.etymology = lang_module.generate_etymology(entries_obj) else entries_obj.etymology = default_merge_etymology(entries_obj) end end

local function entries_to_text(entries_obj) for i, entry in ipairs(entries_obj.entries) do		if entry.override then entry = "\n" ..(entry.override or "") else entry = "\n\n" .. "===" .. entry.pos_header .. "===\n" .. entry.head .. "\n\n" .. "# " .. entry.def .. (entry.inflection and "\n\n====Inflection====\n" .. entry.inflection or "") .. (entry.declension and "\n\n====Declension====\n" .. entry.declension or "") .. (entry.conjugation and "\n\n====Conjugation====\n" .. entry.conjugation or "") .. (entry.altforms and "\n\n====Alternative forms====\n" .. entry.altforms or "") .. -- FIXME, if there are multiple entries, there should either be only one merged L3 Mutation or several -- L4 Mutation sections. Not yet implemented. (entry.mutation and "\n\n===Mutation===\n" .. entry.mutation or "") end entries_obj.entries[i] = entry end return "==" .. entries_obj.lang:getCanonicalName .. "==" ..		(entries_obj.etymology and "\n\n===Etymology===\n" .. entries_obj.etymology or "") .. (entries_obj.pronunciation and "\n\n===Pronunciation===\n" .. entries_obj.pronunciation or "") .. table.concat(entries_obj.entries) end

local function split_and_zip_term_and_translit(encoded_term, encoded_translit) local terms = rsplit(encoded_term, split_term_regex) local translits = encoded_translit and rsplit(encoded_translit, split_term_regex) or {} if #translits > #terms then error(("Saw %s translits, which is > the %s terms seen: encoded_term=%s, encoded_translit=%s"):			format(#translits, #terms, encoded_term, encoded_translit)) end local result = {} for i, term in ipairs(terms) do		local translit = translits[i] if translit == "" then translit = nil end table.insert(result, {term = term, translit = translit}) end return result end

local function paste_term_translit(termobj) if termobj.translit then return termobj.term .. "//" .. termobj.translit else return termobj.term end end

function export.generate(frame) local fparams = { lang           = {required = true}, origin_pagename = {required = true}, target_pagename = {required = true}, num            = {required = true, type = "number"},

pos                   = {list = true, allow_holes = true}, form                  = {list = true, allow_holes = true}, gender                = {list = true, allow_holes = true}, transliteration       = {list = true, allow_holes = true}, origin                = {list = true, allow_holes = true}, origin_transliteration = {list = true, allow_holes = true}, -- I'm pretty sure this is actually required and must have args.num entries in it. target                = {list = true, allow_holes = true}, }

local args = require("Module:parameters").process(frame.args, fparams, nil, "accel", "generate") local lang = require("Module:languages").getByCode(args.lang, "lang")

-- Try to use a language-specific module, if one exists. local success, lang_module = pcall(require, "Module:accel/" .. args.lang)

local entries = {}

-- Generate each entry local seen_origins = create_ordered_set local seen_targets = create_ordered_set local params_list = {} for i = 1, args.num do		local params = { lang = lang, origin_pagename = args.origin_pagename, target_pagename = args.target_pagename,

pos = args.pos[i] or error("The argument \"pos\" is missing for entry " .. i), form = args.form[i] or error("The argument \"form\" is missing for entry " .. i), gender = args.gender[i], origin = args.origin[i] or error("The argument \"origin\" is missing for entry " .. i), origin_transliteration = args.origin_transliteration[i], target = args.target[i], transliteration = args.transliteration[i], num_entries = args.num, }

params.form = params.form:gsub("|", "|") params.targets = split_and_zip_term_and_translit(params.target, params.transliteration) params.origins = split_and_zip_term_and_translit(params.origin, params.origin_transliteration)

for _, origin in ipairs(params.origins) do			add_item(seen_origins, paste_term_translit(origin), origin) end

for _, target in ipairs(params.targets) do			add_item(seen_targets, paste_term_translit(target), target) end

table.insert(params_list, params) end

-- Generate entries. for _, params in ipairs(params_list) do -- Add overall stats to all params objects. params.seen_origins = seen_origins params.seen_targets = seen_targets

-- Make a default entry. local entry = export.default_entry(params)

if success then lang_module.generate(params, entry) end

-- Add it to the list. table.insert(entries, entry) end

local entries_obj = { entries = entries, lang = lang, lang_module = lang_module, seen_origins = seen_origins, seen_targets = seen_targets, }

-- Merge entries if possible. merge_entries(entries_obj)

-- Now generate merged pronunciation and etymology, either using a custom generation function or by merging the -- individually specified pronunciation and etymology lines. generate_merged_pronunciation(entries_obj) generate_merged_etymology(entries_obj)

return entries_to_text(entries_obj) end

function export.generate_JSON(frame) local success, entries = pcall(export.generate, frame)

-- If success is false, entries is an error message. -- It appears we need to specify `messages` or nothing will be displayed. local ret = { [success and "entries" or "error"] = entries, messages = require("Module:array")}

return require("Module:JSON").toJSON(ret) end

return export

title: Module:User:Benwing2/accel


text: 无知无识

title: 无知无识


text:
User:Benwing2/test-accel

 * production-module tests

 * sandbox-module tests

title: User:Benwing2/test-accel


text:
Reconstruction:Proto-Germanic/furibudą

Etymology
From.

Noun

 * 1) A prohibition, forbidding

title: Reconstruction:Proto-Germanic/furibudą


text:
無知無識

Idiom

 * 1) to be devoid of the commonest knowledge

title: 無知無識


text:
angamia

Verb

 * 1) to sink
 * 2) to drown
 * 3) to be destroyed

title: angamia


text: kuangamia

title: kuangamia


text:
殺滅

Verb

 * 1) to kill; to exterminate; to eliminate

title: 殺滅


text: 杀灭

title: 杀灭


text: 时起时伏

title: 时起时伏


text:
angamiza

Verb

 * : to cause to sink, to destroy

title: angamiza


text: kuangamiza

title: kuangamiza


text:
時起時伏

Idiom

 * 1) to rise and fall in a wavelike manner

title: 時起時伏


text:
ลิ่วล้อ

Etymology
From.

Noun

 * 1)  minion, henchman; follower, supporter, sidekick; servant, attendant; subordinate, inferior.

title: ลิ่วล้อ


text:
hiushoide

Noun

 * 1) hair conditioner

title: hiushoide


text:
hiushuokoinen

Adjective

 * 1) capillary

title: hiushuokoinen


text:
hiushuokoisuus

Noun

 * 1) capillariness

title: hiushuokoisuus


text: hiushygrometri

title: hiushygrometri


text:
hiuskiehkura

Noun

 * 1) lock of hair

title: hiuskiehkura


text:
hiuskiinne

Noun

 * 1) hair lacquer, hair spray

title: hiuskiinne


text:
hiuskuontalo

Noun

 * 1) messy hair

title: hiuskuontalo


text:
hiuslaskos

Noun

 * 1)  pin tuck

title: hiuslaskos


text:
hiusmuoti

Noun

 * 1) hair fashion, hairstyle

title: hiusmuoti


text:
hiusmuotoilija

Noun

 * 1) hairdresser, hair stylist

title: hiusmuotoilija


text:
hiusmuotoilu

Noun

 * 1) hairdressing, hair styling

title: hiusmuotoilu


text:
hiusnauha

Noun

 * 1) hair band, hair ribbon

title: hiusnauha


text:
hiuspalmikko

Noun

 * 1) hair plait

title: hiuspalmikko


text: hiuspilli

title: hiuspilli


text:
hiuspohja

Noun

 * 1) scalp

title: hiuspohja


text:
hiusravinne

Noun

 * 1) hair food

title: hiusravinne


text:
hiusristikko

Noun

 * 1) crosshair, reticle

title: hiusristikko


text:
hiustöyhtö

Noun

 * 1) foretop, erect tuft of hair
 * 2) cowlick

title: hiustöyhtö


text:
hiusöljy

Noun

 * 1) hair oil

title: hiusöljy


text:
hiussuonisto

Noun

 * 1) capillary bed

title: hiussuonisto


text:
hiussuortuva

Noun

 * 1) wisp of hair, strand of hair

title: hiussuortuva


text:
hiusvoide

Noun

 * 1) hair cream, brilliantine, pomade

title: hiusvoide


text:
hiustupsu

Noun

 * 1) lock of hair, tuft of hair

title: hiustupsu


text:
hulter til bulter

Etymology
🇨🇬

Adverb

 * 1) helter-skelter

Adverb

 * 1) higgledy-piggledy

Adverb

 * 1) higgledy-piggledy

title: hulter til bulter


text: hiussykerö

title: hiussykerö


text:
hiustuppi

Noun

 * 1) hair follicle

title: hiustuppi


text:
hiustukku

Noun

 * 1) tuft of hair

title: hiustukku


text:
kidekone

Noun

 * 1) crystal radio

title: kidekone


text: fèngtiān

title: fèngtiān


text:
judicial remedy

Noun

 * 1)  The legal means to recover a right or to prevent or obtain redress for a wrong

Synonyms

 * judicial relief
 * legal remedy

Translations

 * Finnish: oikeussuojakeino
 * German: Rechtsmittel
 * Kurdish:
 * Northern Kurdish: çareya huqûqî
 * Swedish: rättsmedel

title: judicial remedy


text:
judicial relief

Noun

 * 1)  The legal means to recover a right or to prevent or obtain redress for a wrong

Synonyms

 * judicial remedy
 * legal remedy

Translations

 * Finnish: oikeussuojakeino
 * German: Rechtsmittel
 * Kurdish:
 * Northern Kurdish: çareya huqûqî
 * Swedish: rättsmedel

title: judicial relief


text:
legal remedy

Noun

 * 1)  The legal means to recover a right or to prevent or obtain redress for a wrong

Synonyms

 * judicial relief
 * judicial remedy

Translations

 * Finnish: oikeussuojakeino
 * German: Rechtsmittel
 * Kurdish:
 * Northern Kurdish: çareya huqûqî
 * Macedonian: правен лек
 * Swedish: rättsmedel

title: legal remedy


text:
retriza

Etymology
.

Noun

 * 1) chain or strap which connects both cancís in some Galician yokes

title: retriza


text:
pioga

Etymology
. Related to its synonym, both appear to be diminutives ( with a frequent epenthetic [ɣ], and ) of a common term.

Noun

 * 1) chain or strap which connects both  in some Galician yokes

title: pioga


text:
無識

Verb

 * 1)  to have no knowledge; to be ignorant

Etymology 2
is a character of.

Verb

 * 1)  to have no sign; to have no trace

title: 無識


text: 无识

title: 无识


text:
倘來之物

Idiom

 * 1) unexpected or undeserved gain; windfall

title: 倘來之物


text: 倘来之物

title: 倘来之物


text: 儻來之物

title: 儻來之物


text: 傥来之物

title: 傥来之物


text:
tvehövdad

Etymology
From.

Adjective

 * 1) two-headed (having two heads)

title: tvehövdad


text:
ajalactli̱

Etymology
Cf. 🇨🇬.

Noun

 * 1)  ( spp.)

title: ajalactli̱


text:
böca

Etymology
Borrowed from.

title: böca


text: Category:nhg:Female animals

title: Category:nhg:Female animals


text: böcajte

title: böcajte


text:
Reconstruction:Proto-Germanic/frikį̄

Etymology
From.

Noun

 * 1) avarice, greed

title: Reconstruction:Proto-Germanic/frikį̄


text:
tvedräkt

Etymology
From, from , nominalization of , see , i.e. ”to pull in two directions”. Compare 🇨🇬 and 🇨🇬.

Noun

 * 1) discord, strife

title: tvedräkt


text:
bi̱csi̱c

Etymology
Cf. 🇨🇬 ; 🇨🇬; 🇨🇬, 🇨🇬, 🇨🇬.

title: bi̱csi̱c


text: zuòjià

title: zuòjià


text: 七言绝句

title: 七言绝句


text:
七言絕句

Noun

 * 1) heptasyllabic quatrain; seven-syllable quatrain

title: 七言絕句


text:
七言律詩

Noun

 * 1) heptasyllabic regulated verse; seven-syllable regulated verse

title: 七言律詩


text: 七言律诗

title: 七言律诗


text:
五言律詩

Noun

 * 1) pentasyllabic regulated verse; five-syllable regulated verse

title: 五言律詩


text: 五言律诗

title: 五言律诗


text:
tveeggad

Etymology
From.

Adjective

 * 1) double-edged, two-edged (of a blade)
 * 2)  both positive and negative

title: tveeggad


text:
bentli̱

Etymology
Cf. 🇨🇬.

title: bentli̱


text: Category:nhg:Religion

title: Category:nhg:Religion


text:
七死八活

Idiom

 * 1) almost dead; half dead; on the verge of death

title: 七死八活


text:
tvegifte

Etymology
From.

Noun

 * 1) bigamy

title: tvegifte


text:
User:Urszag/Latin-noun-categories

Ideas for new, more detailed system for categorizing Latin noun lemmas according to their inflection class.

The lowest category levels will be systematically split by gender and declension, as in the current setup, but also by further splits for morphological subcategories of declensions and for common vs. proper nouns.

1st declension
User:Urszag/first-declension-categories

2nd declension
User:Urszag/second-declension-categories

3rd declension
User:Urszag/third-declension-categories

4th declension base-level categories

 * Latin masculine nouns in the fourth declension (~420)
 * common nouns: e.g. actus, apparatus
 * very small number of proper nouns: Iesus, which is quite irregular (also Iesus Christus), some compound terms/names like Argous Portus, Geraesticus portus, Spiritus Sanctus, Status Uniti Americae (plural-only)
 * Latin feminine nouns in the fourth declension with nominative singular in -us (18)
 * Complete list: acus, anus, cryptoporticus, manus, nurus, porticus, pronurus, prosocrus, quercus, socrus, tribus;    sometimes specus;
 * variable declension: colus, domus (irregular), domus equestris, ficus, penus, pinus, spinus
 * Latin feminine plural-only nouns in the fourth declension (2)
 * only īdūs/ Īdūs and Quīnquātrūs
 * Latin feminine nouns in the fourth declension with Greek-type nominative singular in -o (1)
 * echo only common noun, it seems; proper nouns Aello, Argo, Callisto, Calypso, Clio, Dido, Enyo, Io, Manto, Pytho, Sappho, Themisto
 * Categorizing these as fourth declension is somewhat questionable.
 * Latin neuter nouns in the fourth declension (~6):
 * only 6: cornu, gelu, genu, pecu, testu, veru? (some sources also mention tonitru)

4th declension supercategories

 * Latin masculine nouns in the fourth declension
 * Latin feminine nouns in the fourth declension
 * Latin neuter nouns in the fourth declension (only one subcategory)

5th declension base-level categories

 * Latin masculine common nouns in the fifth declension (~1)
 * pretty much just dies, along with derived phrases like dies Iovis which could be argued to be proper nouns
 * Latin masculine proper nouns in the fifth declension (~1)
 * only Hercules?
 * Latin feminine common nouns in the fifth declension
 * res and various -ies nouns such as acies, superficies...
 * Latin feminine proper nouns in the fifth declension
 * only Fides?

Splitting out proper nouns isn't very useful for the fifth declension.

5th declension supercategories

 * Latin masculine nouns in the fifth declension
 * Latin feminine nouns in the fifth declension

masculine base-level categories

 * Latin masculine indeclinable common nouns
 * few examples, but e.g. corban, seraphim
 * Latin masculine indeclinable proper nouns
 * e.g. Aaron

feminine base-level categories

 * Latin feminine indeclinable common nouns
 * e.g. de and other letter names
 * Latin feminine indeclinable proper nouns
 * e.g. Chanaan

neuter base-level categories

 * Latin neuter indeclinable common nouns
 * e.g. alcali
 * Latin neuter indeclinable common nouns defective in all but the nominative and accusative singular
 * e.g. fas, instar, hir, nihil
 * Latin neuter indeclinable proper nouns
 * e.g. Aruci

title: User:Urszag/Latin-noun-categories


text:
escopieta

Etymology
Borrowed from.

title: escopieta


text: escopietajte

title: escopietajte


text:
fiebes

Etymology
Borrowed from.

title: fiebes


text:
gösto

Etymology
Borrowed from.

title: gösto


text: göstos

title: göstos


text:
daaiman

Etymology
Borrowed from. .

Noun

 * 1)  diamond gem

title: daaiman


text: daaimans

title: daaimans


text: estöcacuabi̱tl

title: estöcacuabi̱tl


text: estöcacuajme

title: estöcacuajme


text:
Template talk:contraction of

Glossary
What changes are needed to link to the glossary? Looks like something needs to be added to Module:form of/data? – Jberkel 09:52, 11 November 2019 (UTC)

title: Template talk:contraction of


text: 少年袂曉想，食老毋成樣

title: 少年袂曉想，食老毋成樣


text: 少年袂晓想，食老毋成样

title: 少年袂晓想，食老毋成样


text:
huöqui̱

Etymology
Cf. 🇨🇬.

title: huöqui̱


text:
i̱lfi̱cac

Etymology
Cf. 🇨🇬.

title: i̱lfi̱cac


text: iú-hàu

title: iú-hàu


text: Wiktionary:Word of the day/2020/January 2


text: xonacame

title: xonacame


text:
dommie

Etymology
Borrowed from.

Noun

 * 1)  A piece of mining equipment on rollers used to sieve out valuable materials.

title: dommie


text:
spraakvryheid

Etymology
From, likely a.

Noun

 * 1) freedom of speech

title: spraakvryheid


text:
xelöso

Etymology
Borrowed from (modern ).

title: xelöso


text: xelösojte

title: xelösojte


text:
uittog

Etymology
From. Equivalent to.

Noun

 * 1) exodus

title: uittog


text:
karkó

Etymology
From in the meaning of "chalk".

Noun

 * 1) great edible sea snail
 * 2) queen conch, rooster conch

title: karkó


text: uittogte

title: uittogte


text: uittochten

title: uittochten


text:
vigeren

Etymology
Borrowed from.

Verb

 * 1)  to be in force, to be valid, to be current
 * 2)  to be influential, to dominate

title: vigeren


text: vonkje

title: vonkje


text: vonkie

title: vonkie


text:
ulutetzontetl

Etymology
.

Noun

 * 1)  tool for removing kernels from corncobs

title: ulutetzontetl


text:
bagskid

Noun

 * 1) hangover

title: bagskid


text: ανέθετα

title: ανέθετα


text: αγγαρευόμουν

title: αγγαρευόμουν


text:
koncha

Etymology
From and  and.

Noun

 * 1) great edible sea snail
 * 2) queen conch, rooster conch
 * 3) lobatus gigas, strombus gigas

title: koncha


text:
Talk:envelop

2. hide something or somebody
2. to conceal something or somebody (often passive Microsoft® Encarta® 2009 --Backinstadiums (talk) 10:47, 11 November 2019 (UTC)

title: Talk:envelop


text:
hvalvákn

Etymology
From.

Noun

 * 1) A spear formerly used for whale hunting on the Faroe Islands but now illegal to use.

title: hvalvákn


text:
olotera

Etymology
Borrowed from, from.

Noun

 * 1) A traditional Mexican tool consisting of bound, shortened corncobs, against which ears of corn are scraped against to remove their kernels.

Translations

 * Nahuatl:
 * Tetelcingo: ulutetzontetl
 * Spanish: olotera,

Etymology
From.

title: olotera


text:
tsäänssi

Etymology
From.

Noun

 * 1) chance, possibility

title: tsäänssi


text:
kabaron

Etymology
From and  and.

Noun

 * 1) shrimp

title: kabaron


text:
Reconstruction:Proto-Germanic/snillį̄

Etymology
From.

Noun

 * 1) mobility, braveness

title: Reconstruction:Proto-Germanic/snillį̄


text: 胡坐をかく

title: 胡坐をかく


text:
tabrat

Etymology
, from.

Noun

 * 1) letter

Etymology
, from.

Noun

 * 1) letter, post, mail

title: tabrat


text:
Citations:macies

 * 1612, Julius Caesar Chiodini, De Ingressu Ad Infirmos : Libri Duo, page 129:
 * Huius enim generis maciebus, frustrà impinguantia medicus admouerit.

 * 1667, Johann Theodor Schenck, Ehrenfried Hagendorn, Disputationem Inauguralem De Macie Puerorum Ex Fascino, page 3:
 * Strictè tamen et in specie nostram hîc volumus eam maciei speciem, quae fascini ope introducitur: minimè interim nega[...]s, posse antehàc aegrum ex quadam specie macierum modò dictarum aegrotare, et fascinum tamen unà concipere.

 * 1835, Carolus Beccalossi, De rachitide, page 21:
 * Et sane quandonam inter expositas affectiones omnia haec symptomata simul conjuncta invenimus, nempe abdominis tumescentiam, corporis gravitatem adauctam, spinae flexiones varias, ossium deformationes, acmen ingenii et fuscum rachiticorum colorem, lucidum contra in reliquis maciebus?

title: Citations:macies


text:
ಪತ್ರ

Etymology
From.

Noun

 * 1) letter

title: ಪತ್ರ


text: 本该

title: 本该


text:
本該

Adverb

 * 1) should have … from the beginning

title: 本該


text:
Talk:hvalvákn

Nice.

Entry
An IP contributor created this without formatting. I've added formatting, but can't add basic lexical information for Faroese. Could you update it? ←₰-→ Lingo Bingo Dingo (talk)  12:34, 11 November 2019 (UTC)
 * Done. BigDom 09:24, 14 November 2019 (UTC)

title: Talk:hvalvákn


text:
pristanoyl-

Etymology
From pristanic + -oyl.

Prefix

 * 1)  Derivative such as an ester, of pristanic acid

title: pristanoyl-


text:
tage fat

Verb

 * 1) grab
 * 2) work on something

title: tage fat


text:
бежов

Etymology
, ultimately from.

Adjective

 * 1) beige

title: бежов


text:
glycinuria

Noun

 * 1)  A kidney condition that causes too much glycine in urine.

title: glycinuria


text:
Moorgate

Proper noun

 * , named after a former gate in London's wall.

title: Moorgate


text:
бозав

Etymology
+, ultimately from 🇨🇬.

Adjective

 * 1) grayish brown color
 * 2) pale hue

title: бозав


text:
atenshon

Etymology
From.

Noun

 * 1) attention

title: atenshon


text:
presies

Etymology
From, from , from , from.

Adjective

 * 1) exact, precise
 * 2) accurate, careful

Adverb

 * 1) exactly, just, right

title: presies


text:
теңдік

Etymology
.

Noun

 * 1) equality
 * 2)  equality, parity

title: теңдік


text:
nesesario

Etymology
From and.

Adjective

 * 1) necessary

title: nesesario


text:
теңіз

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

Noun

 * 1) sea

title: теңіз


text:
aeroball

Noun

 * 1) A sport, somewhat like volleyball, in which the players compete while on a trampoline

title: aeroball


text: Fishlake

title: Fishlake


text:
groak

Verb

 * 1)  To stare at people who are eating in the hope that they will offer to share their food

title: groak


text:
neggez

Etymology
From, from.

Verb

 * 1) to jump, leap

title: neggez


text:
брязък

Etymology
Archaic term for light gray/faint. .

Adjective

 * 1)  light, fair, faint color tone
 * 2)  having a light spot (of animals)
 * 1)  having a light spot (of animals)

title: брязък


text:
djis

Etymology
From.

Adverb

 * 1) just, only
 * 2) soon, later

title: djis


text: contesas

title: contesas


text:
лачен

Etymology
From, compare 🇨🇬.

Noun

 * 1) falcon

Etymology 1
From, from or.

Adjective

 * 1) luminary, glimmering

Etymology 2
From.

title: лачен


text:
User talk:94.209.199.137

←₰-→ Lingo Bingo Dingo (talk)  12:34, 11 November 2019 (UTC)

title: User talk:94.209.199.137


text:
搖擺舞

Noun

 * 1) swing dance

title: 搖擺舞


text: 摇摆舞

title: 摇摆舞


text: yáobǎiwǔ

title: yáobǎiwǔ


text:
Talk:in very deed

very, deed
what are the meanings of very and deed here? --Backinstadiums (talk) 12:39, 11 November 2019 (UTC)

title: Talk:in very deed


text: Stainforth

title: Stainforth


text:
optenibel

Etymology
From and.

Adjective

 * 1) obtainable

title: optenibel


text:
смѣдъ

Etymology
From.

Adjective

 * 1) dark, dim color tone
 * 2) bronze, dim brown color

title: смѣдъ


text:
karîn

Verb

 * 1) can, be able
 * 2) may, be allowed/permitted
 * 1) may, be allowed/permitted

title: karîn


text:
Reconstruction talk:Proto-Indo-European/preg-

This verb is onomatopoeic meaning to fry, to burst. The proposed meanings to yearn, to covet are all secondary. The meaning of the Slavic data in particular has emerged quite recently - even after the split of Common Slavic. In South Slavic 🇨🇬 still means to fry, to roast, to burst. A similar semantic shift like in 🇨🇬 has happened with (originally to bake). Bezimenen (talk) 12:52, 11 November 2019 (UTC)


text:
piraputanga

Noun

 * 1) The South American fish

title: piraputanga


text:
metaflammatory

Adjective

 * 1)  Relating to metaflammation

title: metaflammatory


text: metallocenter

title: metallocenter


text: metallocenters

title: metallocenters


text:
alaki

Adjective

 * 1) formal, relating to (the) form, of/in (the) form

title: alaki


text:
microaxial

Adjective

 * 1) Both very small and axial
 * A microaxial pump

title: microaxial


text:
minyak bumi

Etymology
Compound of,.

Noun

 * 1) petroleum-based liquid.
 * 1) petroleum-based liquid.

title: minyak bumi


text:
microcerebral

Adjective

 * 1) Both very small and cerebral
 * A microcerebral aneurism

title: microcerebral


text:
microengine

Noun

 * 1) A very small engine

title: microengine


text: microstellate

title: microstellate


text: Brading

title: Brading


text:
microtenotomy

Noun

 * 1)  Very small-scale tenotomy

title: microtenotomy


text:
microthread

Noun

 * 1)  A thread (typically one executed in parallel) in a microprocessor

title: microthread


text: microthreads

title: microthreads


text:
kerosin

Etymology
From, from.

Etymology
.

Noun

 * 1) kerosene

title: kerosin


text:
резедав

Etymology
From, from probably via. Ultimately from.

Adjective

 * 1) yellowish green, lime green color

title: резедав


text:
高威

Proper noun

 * 1) Galway

title: 高威


text:
mitotoxin

Noun

 * 1) Any mitotoxic substance

title: mitotoxin


text: mitotoxins

title: mitotoxins


text:
戈爾韋

Proper noun

 * 1) Galway

title: 戈爾韋


text: 戈尔韦

title: 戈尔韦


text:
Wiktionary:Northern Thai transliteration

We have not yet established a standard Northern Thai romanisation. See discussion page for ideas.

Writing Systems
There are three major writing systems:

 * 1) Writing in the Thai alphabet, basically using the orthographic conventions of Siamese, including the sound values of the stop consonants.  This system may be called 'thap sap' (ทับศัพท์), at least in Siamese.  It is used in the recent translation of the New Testament.
 * 2) Writing in the Thai alphabet, basically using the vowel and tone conventions of Siamese, but with the consonant values from the Lanna script (script code Lana).  This is close to being a transliteration of the Lanna script consonant system.  This system may be called rup pariwat (รูปปริวรรต).
 * 3) Writing in the Lanna script.  It is used in the recent translation of the New Testament.

Dependent Vowels
Because of grave deficiencies in Tai Tham rendering, the Lanna script vowels are shown on ᨠ or, where more appropriate, ᨣ or ᨠᩖ. For greater clarity, implicit vowels are shown by the dotted circle for both scripts.

Dependent Vowels plus Coda
This does not list predictable combinations, such as ◌าย/ᨠᩣ᩠ᨿ/aai.

No. 32 generalises to the combination of mai sat with vowels above or below.

Tone marks
NOTE: This page is currently being created by adapting the policy for Thai. This section has yet to reach the level of an initial draft. The other sections may be considered ready.

Diatonemes
Although the presence of six tones across Northern Thai is widespread, there are differences in realisation across the region. To establish the diatonemes of the language, it is helpful to go back to the Gedney Box and give concrete examples. The standard four-fold division of initials is more than adequate to encompass Northern Thai, Thai and Lao. Examples are given in the tables in the form (Chiang Mai) thap sap / Lanna script / (Siamese cognate).

The mapping of the cells of the Gedney box is shown in the coloured table. The identification of the tones on short dead syllables with tones on live syllables is not necessarily consistent across accents. NOTE TO EDITORS: Please ensure that there is a comparable set of tone descriptions across dialects. There is a confusing tendency for descriptions to vary from researcher to researcher - perhaps because of variations in informants! By all means supplement consistent descriptions with alternative descriptions. Northern Thai has six tones on live syllables (tone classes A, B and C) and four tones on dead syllables (tone class D).

Lexical Ordering
For the Thai script, the Thai lexical ordering should be used.

For the Lanna script, we need evidence. The following principles appear to be widely agreed:
 * 1) Ordering is done syllable by syllable (this can be hard to implement), and there might be some difference between phonetic and alphabetical syllables.
 * 2) Differences of tone mark have the lowest priority.
 * 3) Consonants and vowels count equally.
 * 4) Short vowels precede long vowels.

There is not necessarily agreement on the positional of the additional consonants, i.e. those not used for Pali. Additionally, do the vowel letters come first or (almost) last? Are consonants split according to sound (as in the MFL)?


text:
minyak tanah

Etymology
Compound of , .

title: minyak tanah


text:
monoguttulate

Adjective

 * 1) Having a single guttule

title: monoguttulate


text:
Wiktionary talk:Northern Thai transliteration

Disorganised Thoughts
For Northern Thai in the Thai script using Bangkok conventions, there is a case for basing the Romanisation on the Paiboon system. However, I for one loather the system of t/dt/d, and would prefer th/t/d. The aspirates are much rarer in Northern Thai than in Central Thai. --RichardW57m (talk) 13:33, 11 November 2019 (UTC)

Transliterated Words
This list was extracted on Saturday 16 November 2019

51 words:

--RichardW57 (talk) 02:27, 17 November 2019 (UTC) --RichardW57 (talk) 14:19, 17 November 2019 (UTC)

Untransliterated Words
The totality of lemmas on 16 November was was 88 words, so 88 - 51 leaves 37 words. As not adding a transliteration may be significant, I have also recorded the original authors of these documents. The overwhelming majority of entries with transliterations were assigned their final transliteration at creation.

--RichardW57 (talk) 13:50, 17 November 2019 (UTC)

Test/Draft Templates etc.
& documentation Module:User:RichardW57/nod-pron & documentation Module:User:RichardW57/nod-pron/files & documentation Module:User:RichardW57/nod-translit & documentation Module:User:RichardW57/nod-translit/testcases & documentation page Module:User:RichardW57/nod-hom/data Module:User:RichardW57/nod-hom/data & documentation


text:
daqq

Etymology 1
From.

Verb

 * 1)   to play (an instrument, a song)
 * 2) to beat
 * 3) to give money

Etymology 2
From.

title: daqq


text:
morphokinetics

Noun

 * 1) Changes in form over time

Related terms

 * morphokinetic

title: morphokinetics


text:
цикламен

Etymology
From, from.

Adjective

 * 1) magenta, glimmering pink color

Noun

 * 1) cyclamen

title: цикламен


text:
gas bumi

Etymology
Compound of, a.

title: gas bumi


text:
gas alam

Etymology
Compound of, a.

title: gas alam


text:
multicatheter

Adjective

 * 1) Involving multiple catheters

title: multicatheter


text:
multimetabolite

Adjective

 * 1)  Relating to multiple metabolites

title: multimetabolite


text:
回中

Verb

 * 1)  to return to the central base position

title: 回中


text:
myotubulin

Noun

 * 1)  A tubulin present in muscle tissue.

title: myotubulin


text:
lugá

Etymology
From and  and.

Noun

 * 1) place
 * 2) location

title: lugá


text:
Citations:illuvies

 * 1647, Jacobus Laurentius, Petri Epistola Catholica Prior, Perpetuo Commentario Explicata, page 215:
 * Dei virtute ad illam illuvierum exundantiam generandam, quam in ipso aëre genuerunt, et in terram miserunt.

 * 1768, Georg Friedrich Sigwart, De me ipso olim varioloso et morbilloso, page 20:
 * ...et vel ipsae catarrhales defluxiones ab aliis serosis illuviebus distinguendae sint

 * 1791, Carolus Ludovicus Petif, Dissertatio Medica Nova Quædam Circa Phthisium Therapiam, page 12:
 * Cognoscenda sese praebet haec phthisis tussi sicca inani, habituali, respiratione difficillima, simul existentibus in collo, axillis etc. scrophulis, atque exspuitione globulorum subpinguium, subatrorum plerumque, vel crudiorum, tubercula constituentium illuvierum

 * 1835, Gottlieb Wilhelm Bischoff, De hepaticis inprimis tribuum Marchantiearum et Ricciearum, page 36:
 * Habitat ad terram in illuviebus limosis, paludibus exsiccatis, in stagnorum fossarumque marginibus, cum priore varietate. Autumno fructus maturat.

title: Citations:illuvies


text:
лазурен

Etymology
From, from , itself borrowed from , via. Akin to 🇨🇬, 🇨🇬, 🇨🇬 where the initial #l- is reinterpreted as the definite article l'- and consequently dropped.

Adjective

 * 1) clear, sunny, cloudless (for sky)
 * 2) azure color

title: лазурен


text:
syltrygg

Noun

 * 1)  someone who is spineless; someone who is afraid to voice or defend their opinions

title: syltrygg


text:
亞舍拉

Proper noun

 * 1) Asherah

title: 亞舍拉


text:
ġeraħ

Etymology
From.

Verb

 * 1) to wound; to injure seriously and bloodily

title: ġeraħ


text: 亚舍拉

title: 亚舍拉


text:
ملمس

Etymology
From.

Noun

 * 1) texture

title: ملمس


text:
寒冬臘月

Idiom

 * 1) the coldest period of winter

title: 寒冬臘月


text:
glase

Etymology
From.

Verb

 * 1) to freeze

title: glase


text:
nèshi

Etymology
From.

Pronoun

 * 1) nest
 * 2) bird's nest

title: nèshi


text: 寒冬腊月

title: 寒冬腊月


text:
Wiktionary talk:Votes/pl-2019-11/CFI policy for foreign given names and surnames

Latin
What would this mean for the names from various languages that are only attested in Latin text, but clearly are not of Latin origin? E.g. most early medieval Germanic given names. — Mnemosientje (t · c) 14:18, 11 November 2019 (UTC)
 * Depends on their spelling, I suppose. If they're just written as is, they're not really Latin, are they? — surjection ⟨?⟩ 15:46, 11 November 2019 (UTC)
 * Well, usually they're adapted to Latin orthography and have an -us or -a to turn them into respectively second or first declension proper nouns, and they're then inflected depending on case etc. like any other Latin name. We add such names as Latin entries currently, which then can serve as basis for the reconstruction of the corresponding Germanic language entry (as at ). — Mnemosientje (t · c) 15:59, 11 November 2019 (UTC)
 * I would argue that the former might place it in the "consistently used ... spelling ... that is markedly different", although the Latin entries might be hapax legomena, which makes it less clear. — surjection ⟨?⟩ 16:43, 11 November 2019 (UTC)
 * Yes. Alaricus definitely isn't a hapax, but I have no doubt that a significant amount of names like it are indeed only attested once. — Mnemosientje (t · c) 17:02, 11 November 2019 (UTC)

Comment
I think the purpose of this vote is to narrow down the scope of words accepted as lemmas in categories such as Category:Portuguese surnames from Japanese (396 entries). See also Talk:Hong where an editor wanted to add Tagalog surnames based on Facebook profiles.

I think the "oppose" section can be split into two groups:
 * 1) editors that want all names attestable in language X to be accepted as lemmas, and are hence opposed to the more restrictive criteria.
 * 2) editors that want other criteria (e.g. completely ban such words that are borrowings) regarding the policy for Wiktionary names. KevinUp (talk) 01:58, 14 November 2019 (UTC)
 * I think the entire concept of assigning a language to a name is questionable. But this is Wiktionary so everything has to be categorized as belonging to a particular language. Coming up with convoluted and artificial rules for doing so (this vote) is coming at it from the wrong side. And "Translingual" is not a solution either. DTLHS (talk) 03:00, 14 November 2019 (UTC)
 * Anything is better than the status quo that permits editors to create entries for names of e.g. state leaders in 50+ languages, flooding the reader with useless information when the name entry has basically every major language written in the same script. Hell, I'm almost even more for completely removing coverage on given names and surnames than for how the situation is right now. — surjection ⟨?⟩ 08:51, 14 November 2019 (UTC)
 * I think a per-language consideration will be needed regarding the coverage/removal of given names and surnames.
 * For example:
 * Category:Chinese given names does not exist because in theory, any Chinese character(s) can be used as a given name.
 * However, we do have Category:Chinese surnames, because the definition of some words such as is just "surname" and nothing else. If surnames are banned then the entry for  would have no definition.
 * 2. Category:Tamil surnames does not exist because the surname is the father's given name. See also Patronymic.
 * The current vote limits the CFI for given names/surnames. In future, we could have another vote such as "no entry is allowed for given names/surnames that can be spelled out using any sequence/combinations of letters".
 * Meanwhile, are the words in these categories legit entries?
 * Category:Proto-Germanic given names (64 entries)
 * Category:Proto-Brythonic given names (32 entries)
 * Category:Proto-Celtic given names (30 entries)
 * I would like to see given names/surnames listed only in Category:Surname appendices and Category:Given name appendices. Although information such as those found in Category:Egyptian given names would become lost the information can be migrated to an appendix. KevinUp (talk) 15:08, 14 November 2019 (UTC)
 * Bit late this and I can't speak for Proto-Brythonic/Celtic, but afaik the Proto-Germanic ones all have at least 2 descendants, thus warranting a reconstruction. — Mnemosientje (t · c) 11:57, 2 December 2019 (UTC)
 * For now, this vote is a good place to start towards the cleanup and eventual removal of given names/surnames on Wiktionary. KevinUp (talk) 15:08, 14 November 2019 (UTC)

More explanation, please
Given the volume of oppose votes, I suspect that I'm either not reading the proposal correctly or not understanding its implications. Could you give some specific examples (made up, if that's easier) of problems that would arise if this vote passes, please? -Stelio (talk) 12:07, 4 December 2019 (UTC)


text:
skucha

Etymology
From.

Verb

 * 1) to listen

Etymology
+.

Noun

 * 1)  failure, debacle

title: skucha


text:
nifiká

Etymology
From and  and.

Verb

 * 1) to mean, to signify

title: nifiká


text: Míngzhì Wéixīn

title: Míngzhì Wéixīn


text:
ħabbat

Etymology
From.

Verb

 * 1)  to knock, to strike
 * 2)  to beat, to throb
 * 3)  to whisk
 * 4)  to bother
 * 5)  to shake
 * 1)  to shake

title: ħabbat


text:
skedel

Etymology
From, from , from , , from.

title: skedel


text: skedels

title: skedels


text:
係唔係

Conjunction

 * 1)  whether or not
 * 2)  no matter what

title: 係唔係


text: 系唔系

title: 系唔系


text:
flash flooding

Noun

 * 1)  Flooding that occurs during a.

title: flash flooding


text:
beosztás

Etymology
From, from.

Noun

 * 1) scale unit of measuring
 * 2) rota, allocation, management, schedule of allocating tasks
 * 3) position, assignment, duty, function a position to which someone is assigned
 * 1) position, assignment, duty, function a position to which someone is assigned

title: beosztás


text:
Talk:how's that

how so
what're the differences with "how (is that) so?" --Backinstadiums (talk) 15:08, 11 November 2019 (UTC)

title: Talk:how's that


text:
tambú

Etymology
From the Bantu word "ntambu" as used in the Congo.

Noun

 * 1) Antillean drum
 * 2) Antillean dance
 * 3) Antillean beat
 * 4) Antillean music
 * 5) Antillean feast

title: tambú


text: Egoismusses

title: Egoismusses


text:
mwaasi

Etymology
From.

Noun

 * 1) rebel

title: mwaasi


text: waasi

title: waasi


text: Machtlosigkeiten

title: Machtlosigkeiten


text:
kifyonzavumbi

Etymology
From.

Noun

 * 1) vacuum cleaner

title: kifyonzavumbi


text: vifyonzavumbi

title: vifyonzavumbi


text: Pontrilas

title: Pontrilas


text:
galgenhumoristisch

Etymology
From.

Adjective

 * 1)  Displaying or pertaining to gallows humour

title: galgenhumoristisch


text:
Reconstruction:Proto-West Germanic/galiuhtijan

Etymology
From.

Verb

 * 1) to shine, illuminate


text:
tefa'

Etymology
From with regular assimilation of  to  in inflected forms and subsequent generalisation of the unvoiced consonant.

Verb

 * 1) to throw
 * 2) to assign
 * 3) to post, mail
 * 4) to submit
 * 5) to place, to put
 * 1) to post, mail
 * 2) to submit
 * 3) to place, to put
 * 1) to place, to put
 * 1) to place, to put

title: tefa'


text:
Talk:see fit

etymology
is it derived form "see it fit to..."? --Backinstadiums (talk) 15:46, 11 November 2019 (UTC)

title: Talk:see fit


text: Category:Early Scots

title: Category:Early Scots


text:
tefgħa

Etymology
From with  after the underlying verb, which see.

Noun

 * 1) a throw; instance of throwing

title: tefgħa


text:
Alban Arthan

Etymology
From, "the solstice of the Little Bear".

Proper noun

 * 1)  the winter solstice

title: Alban Arthan


text:
Alban Hefin

Etymology
From, "the solstice of summer".

Proper noun

 * 1)  the summer solstice

title: Alban Hefin


text:
Alban Elfed

Etymology
From, "the solstice of autumn".

Proper noun

 * 1)  the autumnal equinox

title: Alban Elfed


text:
Alban Eilir

Etymology
From, "the solstice of spring".

Proper noun

 * 1)  the vernal equinox

title: Alban Eilir


text:
Talk:بسلامة

This entry is misspelled. The correct spelling is بالسلامة. --Fenakhay (talk) 12:31, 13 November 2019 (UTC)
 * Thanks, I'll delete it. Please remember to leave an explanation in next time. — Eru·tuon 17:40, 13 November 2019 (UTC)

title: Talk:بسلامة


text:
arthan

Noun

 * 1) little bear
 * 2)  the Little Bear, Ursa Minor

title: arthan


text: sajnáljuk

title: sajnáljuk


text: sajnáljátok

title: sajnáljátok


text:
Alban Cyntefin

Etymology
From, "the solstice of spring".

Proper noun

 * 1)  the vernal equinox

title: Alban Cyntefin


text: sajnálják

title: sajnálják


text:
Alban Hyfed

Etymology
From, "the solstice of the time of reaping".

Proper noun

 * 1)  the autumnal equinox

title: Alban Hyfed


text: sajnálod

title: sajnálod


text: sajnálja

title: sajnálja


text:
Reconstruction talk:Proto-Germanic/þreskwaþluz

Labiovelar
West Germanic regularly delabialises all medial labiovelars. The fact that a labial is attested in this word suggests that the sequence was not -kw- but something else. —Rua (mew) 16:24, 11 November 2019 (UTC)
 * It's possibly a compound *þreskwa- + *waþluz. Could that possibly make a difference ? Leasnam (talk) 02:38, 12 November 2019 (UTC)
 * It's possible, but then so would without any labiovelar. —Rua (mew) 08:22, 12 November 2019 (UTC)


text:
Kerzenhalter

Noun

 * 1) candlestick

title: Kerzenhalter


text: Kolonialmächte

title: Kolonialmächte


text: Besatzungsmächte

title: Besatzungsmächte


text: Übermächte

title: Übermächte


text: Θρῃκῶν

title: Θρῃκῶν


text: Category:Bulgarian terms suffixed with -ав


text:
ꜥbw

Etymology 1
.

Noun

 * 1) cleanness, purity
 * 2) purification, cleaning
 * 3) cleaning agent

Etymology 2
.

Noun

 * 1) something wicked or bad
 * 2) dirt, filth, pollution

Noun

 * 1) lettuce

title: ꜥbw


text: ἀπάνευθεν

title: ἀπάνευθεν


text: δοῦπον

title: δοῦπον


text: neo-fascism

title: neo-fascism


text: Nerds

title: Nerds


text: ζώειν

title: ζώειν


text: Kleinmuts

title: Kleinmuts


text: Kleinmutes

title: Kleinmutes


text: Ἥρῃ

title: Ἥρῃ


text:
Talk:enarch

Etymology might require splitting; I am not sure about the origin of. Equinox ◑ 16:57, 11 November 2019 (UTC)

title: Talk:enarch


text: 電話聰明

title: 電話聰明


text:
silinda

Etymology
.

Noun

 * 1) cylinder

title: silinda


text: beosztások

title: beosztások


text: Backpfeifengesichts

title: Backpfeifengesichts


text: Backpfeifengesichtes

title: Backpfeifengesichtes


text: Backpfeifengesichter

title: Backpfeifengesichter


text: riever

title: riever


text: rievers

title: rievers


text:
rieve

Etymology
From, from , northern variant of , from , from. Middle Ripuarian still regularly retained the wr-onset, which was later either reduced or merged with fr-.

Verb

 * 1)  to rub
 * 2)  to grate

title: rieve


text: rieves

title: rieves


text: rieving

title: rieving


text: rieved

title: rieved


text: 忠彰

title: 忠彰


text: rievings

title: rievings


text: reavings

title: reavings


text:
herriment

Noun

 * 1)  harassment; depredation

title: herriment


text: herriments

title: herriments


text:
tufe

Noun

 * 1) sphere

title: tufe


text:
spreath

Etymology
, from, , from , (plus mobile s-), borrowed from , thus a. Per one hypothesis, also a doublet of.

Noun

 * 1)  A raid in order to steal cattle.

title: spreath


text: spreaths

title: spreaths


text: éjjelik

title: éjjelik


text: Category:Lega-Binja languages

title: Category:Lega-Binja languages


text:
Talk:Dick

Dick and Jane
plural noun: stereotypical white Americans: the stereotypes of middle-class white Americans (informal) (hyphenated when used before a noun) Microsoft® Encarta® 2009 --Backinstadiums (talk) 17:17, 11 November 2019 (UTC)

title: Talk:Dick


text:
keménység

Noun

 * 1) hardness

title: keménység


text: 十六分

title: 十六分


text: skálák

title: skálák


text: Richtschnüre

title: Richtschnüre


text: napellenzők

title: napellenzők


text:
Talk:duration

for the duration
for the duration 1. for the entire period of time something is going on or will continue to go on 2. for the foreseeable future: The house is yours for the duration; stay as long as you like. Microsoft® Encarta® 2009 --Backinstadiums (talk) 17:21, 11 November 2019 (UTC)

title: Talk:duration


text:
Arabophilia

Noun

 * 1) An affection for, or interest in, things related to Arabs.

title: Arabophilia


text:
Arabophilic

Etymology
From.

Adjective

 * 1) Having or relating to Arabophilia; fond of Arabs or their culture.

title: Arabophilic


text: 直朗

title: 直朗


text:
englanninlakritsi

Noun

 * 1) liquorice allsorts

title: englanninlakritsi


text:
fázisceruza

Noun

 * 1)  voltage tester, mains tester, test light, test lamp

title: fázisceruza


text:
mirakuliini

Etymology
(see 🇨🇬).

Noun

 * 1) miraculin

title: mirakuliini


text: Schlitzaugen

title: Schlitzaugen


text:
kamarazenekar

Noun

 * 1) chamber orchestra an orchestra of modest size, to play chamber music

title: kamarazenekar


text: Schlitzauges

title: Schlitzauges


text:
عاص

Etymology
Active participle of the verb, from the root.

Adjective

 * 1) disobedient
 * 2) sinner

title: عاص


text:
θηλυφόνον

Etymology
Neuter form of.

title: θηλυφόνον


text: najinteligentniejszego

title: najinteligentniejszego


text: najintymniejszego

title: najintymniejszego


text: kamarazenekarok

title: kamarazenekarok


text: najjaśniejszego

title: najjaśniejszego


text:
kamarazenekari

Adjective

 * 1)  (of) chamber orchestra

title: kamarazenekari


text:
User talk:Saltmarsh/Sandbox

a
, some ideas -excuse my writing here, at your personal page-: 1. imperfect + past too are both needed for 2nd conjug class A. 2. Is the space after every bullet needed? Here is an extreme example, with lots of imaginary doubles. 3. with pres2= instead of head2 for better control Perhaps with params like: passive lemmata have only one extra: «see active». In the passive, imperfect is rare. The parameters (with dash possible) are all double, pasts triple (needed) 4. Plus one exceptional passive past: when only 3rd person exists. |past-3rd= gives
 * / αγαπώ • imperf: αγαπούσα • / αγάπαγα • past: αγάπησα • (pass: αγαπιέμαι • / αγαπώμαι • past: αγαπήθηκα • ppp: αγαπημένος •)
 * |head=αγαπάω|pres2=αγαπώ|imperf=αγαπούσα|imperf2=αγάπαγα|past=αγάπησα|pass=αγαπιέμαι|pass2=αγαπώμαι|p-past=αγαπήθηκα|ppp=αγαπημένος
 * / αγαπώμαι • past: αγαπήθηκα • ppp: αγαπημένος • (see active: αγαπάω • / αγαπώ •)
 * |head=αγαπιέμαι|pres2=αγαπώμαι|past=αγαπήθηκα|ppp=αγαπημένος|act=αγαπώ|act2=αγαπάω
 * |pres2=|imperf=|imperf2=|past=|past2=|past3= |pass= opens parenthesis|pass2=|p-imeprf=|p-imperf2=|p-past=|p-past2=|p-past3=|ppp= |ppp2= closes parenthesis if there is one |act= opens parenthesis|act2= closes parenthesis
 * past: (συνεθλίβη3rd •)

PS I promise to fix all the real red links! Do not worry: imperfect rarely does appear. sarri.greek (talk) 13:25, 11 November 2019 (UTC)

 * Too much to deal with at one go!!
 * I thought that you agreed (at Template talk:el-verb) that we could omit "alternative forms", if we are to restrict o/p (output) to less than one line (except in exceptional circumstances). But, I had forgotten about the 2nd lemma form (-άω/-ώ).
 * I have been assuming that we were restricting ourselves to the forms generally shown in dictionaries — ie lemma/past(or imperf)/pass/pass-past(or pass-imperf)/ppp (ie not past PLUS imperfect)
 * The extra space after the bullet is to clarify which term the bullet belongs to (I removed the commata). I think further punctuation makes the line more "busy"/messy/…
 * So I based what I have done on the Template talk:el-verb one

 * , simple past tense or aorist: (passive voice:    simple past tense or aorist:    perfect passive participle: )
 * — Salt  marsh . 17:59, 11 November 2019 (UTC)

Nov 14
Can we discuss the issues one at a time please, addressing more in this medium leads to confusion (with me at least). I designed the template to produce a clear, simple single line — bearing in mind that verbs will have an inflection table with the full monty.
 * So: other than the a single form in each case even when there is more than one, in which case it will be the most common or correct.
 * Is this an impossible condition? — Salt  marsh . 10:48, 14 November 2019 (UTC)
 * , it is fine! I have just shown the full line, as it is done in dictionaries. If not, I would rather have it as it is today. It is fine. No changes needed. All forms are included, but split in 2 pages (active and passive). Personally, I would rather have the main.lemma.HWL carry all the info but I understand that aesthetically it can become ugly, and too long. sarri.greek (talk) 12:39, 14 November 2019 (UTC)

title: User talk:Saltmarsh/Sandbox


text:
zsírkő

Noun

 * 1) talc, soapstone

title: zsírkő


text: najkonkretniejszego

title: najkonkretniejszego


text: fázisceruzák

title: fázisceruzák


text: najkoszmarniejszego

title: najkoszmarniejszego


text:
Kleinlibelle

Etymology
From.

Noun

 * 1) damselfly

title: Kleinlibelle


text:
User:AyushValvi

Noun

 * MSFTS

Other spellings

 * msfts

Pronunciation

 * IPA

Abbreviation

 * 1) "Musicians Scoring Famous Talks Speeches".

title: User:AyushValvi


text:
κανδυτάνη

Etymology
According to Beekes, from

Noun

 * 1) clothes-press

title: κανδυτάνη


text:
monifate

Etymology
. Likely related to. Cognate with 🇨🇬.

Noun

 * 1) puppet
 * 2) straw doll
 * 3)  wimp
 * 1)  wimp
 * 1)  wimp

title: monifate


text:
monicreque

Etymology
. Likely related to. Compare 🇨🇬 and 🇨🇬.

Noun

 * 1) puppet
 * 2) straw doll
 * 3) stickman
 * 4)  wimp
 * 1) stickman
 * 2)  wimp

title: monicreque


text:
gipsz

Etymology
Borrowed from, also via , from.

Noun

 * 1) gypsum, plaster
 * 2) cast a supportive and immobilizing device used to help mend broken bones

title: gipsz


text:
στρωματόδεσμον

Etymology
From.

Noun

 * 1) leathern or linen sack in which slaves had to tie up bedclothes

title: στρωματόδεσμον


text: najkrąglejszego

title: najkrąglejszego


text:
fiziológia

Etymology
From scientific, from , from. With ending.

Noun

 * 1) physiology a branch of biology that deals with the functions and activities of life or of living matter (as organs, tissues, or cells) and of the physical and chemical phenomena involved

title: fiziológia


text:
kalcit

Etymology
Borrowed from, from.

Noun

 * 1) calcite

title: kalcit


text:
Libellenflügel

Etymology
From.

Noun

 * 1) dragonfly wing

title: Libellenflügel


text: najkrótszego

title: najkrótszego


text:
kímélő

Adjective

 * 1)  light, easy to digest, easily digestible, special
 * 2)  gentle
 * 3)  -efficient, -saving, -cutting

title: kímélő


text:
βεττονική

Etymology
Borrowed from.

Noun

 * 1) ironwort of subspecies  (syn. )

title: βεττονική


text: najkruchszego

title: najkruchszego


text: najkwaśniejszego

title: najkwaśniejszego


text: 忠存

title: 忠存


text: なおあきら

title: なおあきら


text: ただあきら

title: ただあきら


text:
Ῥεῦνος

Proper noun

 * 1) Rheunus, Arcadia, Greece

title: Ῥεῦνος


text:
pauvre de

Phrase

 * 1) poor old

Usage notes
Can agree or not with the pronoun: pauvre de nous or pauvres de nous.

title: pauvre de


text:
írtok

Etymology
From the verb.

title: írtok


text:
petites gens

Noun

 * 1) the little people the lower class

title: petites gens


text:
Talk:montaraz

De monte y -araz
Etymology of DRAE: De monte y -araz --Backinstadiums (talk) 18:40, 11 November 2019 (UTC)

title: Talk:montaraz


text: のぶえ

title: のぶえ


text: 伸恵

title: 伸恵


text: 信恵

title: 信恵