सदस्य:कन्हाई प्रसाद चौरसिया/प्रयोगपृष्ठ

प्रतिभाग करें

15 अगस्त से 31 अगस्त तक चल रहे

हिन्दी विक्षनरी संपादनोत्सव अगस्त 2021 में भाग लें और पुरस्कार जीतें।

विक्षनरी विक्षनरी हिन्दी विक्षनरी संपादनोत्सव अगस्त 2021 परिचय हिन्दी विक्षनरी पर 15 अगस्त से 31 अगस्त, 2021 के बीच आयोजित की जाने वाली एक संपानोत्सव है। इसका मूल्य उद्देश्य हिन्दी विक्षनरी को बेहतर बनाना या बढ़ावा देना रहा है। अतः इस संपानोत्सव में आपका बढ़-चढ़कर हिस्सा लेना हिन्दी विक्षनरी को आगे बढ़ाने में मददगार साबित हो सकती है। नियम इस प्रतियोगिता में भाग लेने सम्बन्धित कुछ महत्वपूर्ण बिंदुए हैं जिन्हें आपको ध्यान रखना हैं- 1) इस प्रतियोगिता में भाग लेने के लिए सदस्य का एक पंजीकरण खाता होना अनिवार्य है। 2) यह प्रतियोगिता भारतीय समयानुसार 15 अगस्त 6.00 पूर्वाह्न से 31 अगस्त 2021 को 12.00 अपराह्न तक चलेगी। अतः इस अवधि के बीच संपादन कार्य ही मान्य होंगे। 3) आपको ध्यान रखना हैं कि शब्दों के निर्माण या सुधार में किसी भी प्रकार का काॅपी-पेस्ट पन्नो को हटा दिया जाएगा। 4) सुझाव 1) आप किसी भी संपादन से सम्बंधित जानकारी के लिए सदस्य के वार्ता पृष्ठ या उस पृष्ठ से सम्बंधित वार्ता पन्ने पर ही करिएगा। जिससे की आपके संपादन सम्बंधित कार्यों पर विचार करके हल करना का प्रयास किया जाएगा। 2) ध्यान रखें कि प्रतियोगिता के दौरान प्रत्येक सदस्य का सम्मान करें। किसी भी तरह की हतोत्साहित करने, अमानवीय व्यवहार करने या पृष्ठ सम्बन्धित बर्बरता करने पर उसे तीन चेतावनी के बाद कुछ समय के लिए प्रतिबंधित किया जा सकता है। 3) प्रत्येक प्रतिभागी से अनुरोध किया जाता हैं कि जहां तक सम्भव हो सके अलग-अलग शब्दों पर ही कार्य करें जिससे किसी सदस्य को मनमुटाव का सामना ना करना पड़े। 4) प्रत्येक प्रतिभागी को अपना हस्ताक्षर करना अनिवार्य है। विक्षनरी सम्बंधित संक्षिप्त जानकारी यह पहली बार संपादनोत्सव का आयोजन होने जा रहा है। अतः नये सदस्यों के लिए विक्षनरी की संक्षिप्त जानकारी स्पष्ट कर देना बहुत ही आवश्यक हो जाता है। अक्सर लोग यह भ्रमवंश में पड़कर लेखों का निर्माण करने लगते हैं- मैं उन्हें बता दूं यह तथ्यात्मक जानकारी, या स्थानों और लोगों के बारे में डेटा का गहन संग्रह नहीं है। बल्कि एक शब्दकोश (dictionary} है। जिसमें भाषा और शब्द निर्माण सम्बंधित वर्तनी, उच्चारण, व्युत्पत्ति, अनुवाद, अवधारणा, उपयोग, उद्धरण से है। विक्षनरी विभिन्न शब्दों का निर्धारित या निषेध नहीं करता है। बल्कि एक दस्तावेजीकरण के रूप में विभिन्न भाषाओं में क्या उपयोग हो रहा; यह दर्शाता है। विक्षनरी अनुमान की चीजें नहीं हैं कि कौन से नए शब्द प्रयोग में लाए जाए। यह आमतौर पर कई वर्षों में प्रयोग में लिया जा रहा उसपर निर्भर करता है। विशनरी विभिन्न भाषाओं से संबन्धित एक शब्दकोश है। अतः प्रत्येक विक्षनरी सभी भाषाओं के सभी शब्दों को अपनी भाषा में परिभाषित करने का प्रयास करता है; ताकि पाठक सभी भाषाओं को अपनी भाषा में ज्ञान प्राप्त कर सकें। इसमें आपको विभिन्न भाषाओं से संबन्धित शब्दावली में विभिन्न क्षेत्रों से जुड़ी जैसे कि हिन्दी, अंग्रेजी, इतिहास, भूगोल, विज्ञान, गणित, इत्यादि और व्याकरण से सम्बंधित मुहवारे, पर्यायवाची शब्द, विपर्रातक शब्द और ना जाने कितने अनगिनत उसके उपभाग से सम्बंधित उदाहरणस्वरूप भोजन से सम्बंधित आदि शब्दों की शब्दावली उपलब्ध मिलेगी। इसमें आपको शब्दकोश से सम्बंधित शब्दावली का निर्माण, शब्दों का सुधार, चित्र जोड़ना, ऑडियो जोड़ना आदि कार्य कर सकते है। अपवाद आपको यह कुछ बिन्दुए ध्यान रखने की जरूरत हैं- आपके नये शब्द निरर्थक ना हो, वह प्रयोगयुक्त होनी चाहिए। नये शब्दों को निमार्ण से पहले आप खोज स्थान पर जाकर एक बार सुनिश्चित जरूर कर लें। कहीं वह शब्द पहले से बना तो नहीं है। आपके संपादन शब्दावली में शब्दों, चित्रों और ऑडियो का सही स्थान पर प्रयोग करें। अंक प्रणाली अंक प्रणाली की गणना सदस्यों के द्वारा योगदान के अनुसार निर्धारित किए जाएंगे। पुरस्कार प्रतियोगिता के कार्य के अनुसार चार प्रकार की पुरस्कार निर्धारित किए जायेंगे। प्रथम पुरस्कार = 2000 उपहार कूपन और स्मृति चिन्ह द्वितिय पुरस्कार = 1500 उपहार कूपन और स्मृति चिन्ह तिसरा पुरस्कार = 1000 उपहार कूपन और स्मृति चिन्ह चतुर्थ पुरस्कार = 500 उपहार कूपन और स्मृति चिन्ह पुनरीक्षक प्रतिभागी अपना योगदान यहां जमा करें यहां जमा करें प्रतिभागी <translate> What do you want to do?</translate> सदस्य:कन्हाई प्रसाद चौरसिया<translate>This page describes categorization practices specific to Wiktionary as opposed to, say, Wikipedia. To find out about how to use categories in MediaWiki, the software that runs Wiktionary and Wikipedia, see Help:Category. Before you start to assign pages and subcategories to categories and create new categories, please check the conventions described in this page, and make yourself familiar with the categories already in use. Each page is typically in at least one category. It may be in more, but entries in topical categories should rarely—if ever—be put into a more narrow category and also a more general category. Each category should be in at least one higher-level category, except for the highest-level category: Category:Fundamental. For category names the usual rules for case-sensitivity of page names apply: they are case-sensitive for all characters, but in most projects the first character is case-insensitive. So be aware that you create a new category if the capitalization beyond the first character is not the same. All topical categories begin with a capital letter: there is "Category:Foods" rather than "Category:foods". However, the language-specific prefix such as "fr" in "Category:fr:Foods" is in lowercase. Main branches The root category of Wiktionary is Category:Fundamental. This category contains several main categories. Categories are used in Wiktionary for the following main purposes: Grouping words by part of speech Grouping words by language Grouping words by topic Grouping words by etymology Grouping words by style of usage Grouping words by their common properties Grouping pages for purposes internal to Wiktionary A complete dictionary entry will be in at least one, and usually in more than one, category. A word can also be categorized in many branches of the category tree, allowing it to be found in different ways. For example: mare is in the category Category:English nouns, as well as in the topic Category:en:Horses. It can quickly be found by readers looking for an English noun in particular. Likewise, 馬 is in Category:Japanese nouns as well as in Category:ja:Horses. Part of speech Each word should be in the appropriate category for language and part of speech. For example: mare is a word in English, Latin, Italian, and Romanian, and has sections for each of those languages. It thus belongs to language categories of each branch, specifically, Category:English nouns, Category:Latin nouns, Category:Italian nouns, and Category:Romanian nouns. The assignment of an entry to a part-of-speech category is usually done automatically by an inflection-line template, such as {{en-noun}}, {{es-adj}}, or the generic {{head}}, so you don't need to worry about it. Parts of speech have the root category of Category:Lemmas subcategories by language, a subcategory of Category:Fundamental. The root category for parts of speech includes the category of Category:Nouns by language, which in its turn includes the category of Category:Russian nouns. Some terms are not strictly parts of speech, such as affixes, or only stand in for other terms that have, like acronyms. These terms have their own categories and are kept separate from the part of speech hierarchy. Language The Category:Fundamental contains Category:All languages, which in its turn contains categories named like Category:English language. Each language category contains subcategories for parts of speech, described in the section #Part of speech, and some other categories related to the language. Languages are also categorised by various other means, such as their relationship to other languages (Category:Languages by family), script (Category:Languages by script) or the places where they are spoken (Category:Languages by country). See also Wiktionary:Language categories. Topic Where useful, words are categorized by topic such as "Animals" or "Chemistry". The root of topical categories is Category:All topics. This root category contains only some major subcategories, such as Category:Communication or Category:Sciences; further categories on a more fine-grained level such as Category:Horses are located somewhere else, deeper in the subcategory tree. There is also Category:List of topics, which lists all topics alphabetically no matter where in the category tree they are located. Each name of a topical category refers to the objects or meanings referred to by words that are members of the category; the name does not refer to the member words themselves. Thus, there is "Category:Chemistry" rather than "Category:Chemical terminology" or "Category:Chemical terms", or there is "Category:Animals" rather than "Category:Animal names". In other words, the names of topical categories denote what the terms are about, not what they are. Each name of a topical category has a prefix that indicates the language of the terms belonging to the category. Thus, the English category for horses is Category:en:Horses, while the Japanese one is Category:ja:Horses. The prefix consists of the language code followed by a colon. Names and subcategory structures of categories should be matched between languages. Thus, if Category:Horses is a subcategory of Category:Equids, then also Category:en:Horses should be a subcategory of Category:en:Equids. If there exists the category Category:fr:Cryptozoology, there should also exist the category Category:Cryptozoology. The subcategory structure of topical categories is technically maintained in "topic cat parents", such as Template:topic cat parents/Social sciences. This subpage tells the template {{topic cat}} what the parents of the topical category are, regardless of the language. This technique ensures consistent categorization across languages, guaranteeing the matching mentioned in the previous paragraph. "Names" are proper nouns, and are categorized by part of speech: Category:Japanese proper nouns Etymology Each language that has terms for which the origin is known has a category of the form "Category:(language) terms by etymology‎". This category contains terms categorised by the way in which they first entered the language. This includes words that were formed with certain affixes or words that were formed by compounding them with another word, but also terms that have unusual or notable origins. The root of etymology categories is Category:Terms by etymology by language. In particular, languages that are known to have acquired some of their words from other languages have a subcategory named "Category:(language) terms derived from other languages", such as Category:English terms derived from other languages. Languages that in turn are the source of words in other languages have a subcategory named "Category:Terms derived from (language)", for example Category:Terms derived from English. This category lists non-English words derived from English, rather than listing English words. When adding the etymology section to an entry, please categorize the word into the appropriate derivation categories, using templates such as {{der}}. If known, include all of the languages through which the word has come. For example: An English word derived originally from Ancient Greek via Latin and then French would use all three of the templates {{der|en|fr}}, {{der|en|la}} and {{der|en|grc}}, which in turn would add the word to Category:English terms derived from French, Category:English terms derived from Latin and Category:English terms derived from Ancient Greek respectively. Style of usage Many words in a language are not used in all situations, or have certain connotations that are not obvious. This style of usage categorized under Category:Terms by usage by language, with a category for each language. This category contains subcategories for terms that are stilted or formal, old-fashioned, offensive, humorous and so on. Purposes internal to Wiktionary Categories such as the following are special categories used for maintenance purposes, and reside outside of the main category tree: Category:Requests for deletion Category:Requests for cleanup Category:Requested entries — definitions that have been requested Category:Requests for translations by language Category:Requests for review of translations by language In addition, many templates are used on Wiktionary to help in creating and maintaining entries. These are located under Category:Templates. Many languages also have templates that are specific to that language, which are contained in categories such as Category:English templates. Category browsing Categories only list 200 entries at a time. This can be an inconvenience to the user when a category contains more than 200 entries. To alleviate this, add an A-Z table of contents to the category by editing the category page and adding {{CategoryTOC}} to it. 4==Wiktionary:Discussion rooms== Wiktionary > Discussion rooms Wiktionary discussion rooms (edit) see also: requests Information desk new | archives Newcomers’ questions, minor problems, specific requests for information or assistance. Tea room new | archives Questions and discussions about specific words. Etymology scriptorium new | archives Questions and discussions about etymology—the historical development of words. Beer parlour new | archives General policy discussions and proposals, requests for permissions and major announcements. Grease pit new | archives Technical questions, requests and discussions. All Wiktionary: namespace discussions 1 2 3 4 5 – All discussion pages 1 2 3 4 5 Other places to congregate News for editors  (history) Changes in how to edit pages, for established editors. Requested entries The place where you can request entries to be made. Requests for verification  (history) Verification process. Requests for moves, mergers and splits  (history) Renaming, splitting and merging pages and lects. Requests for cleanup  (history) Cleanup process. Administrators  (history) Requests and votes for adminship. Requests for deletion  (history) Deletion process. Vandalism in progress  (history) Report vandalism and request blocks. Requests for deletion (others)  (history) Deletion process for non-article pages. Feedback  (history) Check for comments on feedback questions. 5 ==Wiktionary:IRC channel== For discussion channel:#wiktionary on server:irc.freenode.net is for general chat and (sometimes topical) discussion. channel:#wiktionary-gfdl on server:irc.freenode.net is publicly logged. The logs are published under the GFDL but are not currently available. For monitoring channel:#en.wiktionary on server:irc.wikimedia.org (browne.wikimedia.org) contains all recent changes, as they happen. channel:#cvn-wt-en on server:irc.freenode.net contains only the suspicious recent changes. Further Information The IRC instructions for all wikimedia projects. The list of all the IRC channels related to the wikimedia projects. A few Wikipedia:Scripts you can look at to improve your IRC client. If you want to chat with other Wiktionary users, you may find some of them at #Wiktionary. Feel free to pop in and say hello; there is normally someone who will answer. If no-one does, it is probably because they are all away or asleep. Remember that everyone is in different timezones, so try again after a couple of hours. In order to access these channels, you will need an IRC client. Some of the more popular ones are ChatZilla and mIRC, though there are many others. If you don't wish to install a client, then you can get to the channels through webchat.freenode.net #wiktionary-gfdl has its logs published under the GFDL and so discussion there should remain on topic. Often, if a discussion on #wiktionary seems to be getting important and involved, the participants will migrate to #wiktionary-gfdl so that they can refer to the discussion, should the need to arise later. See also Wiktionary:Discord server 6 ==Wiktionary:Languages== यह एक विक्षनरी नीति, दिशानिर्देश, अथवा आम विक्षनरी परंपरा जानकारी पृष्ठ है। विशेष रूप से यह नीति विचार मंथन है, औपचारिक एवं आधिकारिक नीति का रूप लेने की प्रक्रिया में है। नीतियाँ – प्रविष्टियाँ: CFI - EL - NORM - NPOV - QUOTE - REDIR - DELETE. भाषाएँ: LT - AXX. अन्य: BLOCK - BOTS - CON. For a list of all language codes, see Wiktionary:List of languages. For information on how to add or remove a language from Wiktionary, see Wiktionary:Guide to adding and removing languages. Wiktionary includes many words in many languages. This page details the conventions and practices relating to the variety of languages on Wiktionary. Criteria for inclusion मुख्य लेख: Wiktionary:Criteria for inclusion#Languages to include Language information To distinguish languages, Wiktionary gives each a unique name and a unique code, which identify it. Other information is also collected. Language names Wiktionary calls each language it includes by a distinct name. This name is used in headers, translation tables, categories, appendices, and some other places. Most languages only have one name, but some may be known by multiple names. In this case, one of the language's names is chosen for use in Wiktionary. This name is referred to as the canonical name of the language. Canonical language names are chosen by consensus. Whenever possible, common English names of languages are used, and diacritics are avoided. Attested names (names which meet WT:CFI) are strongly preferred. Canonical names must be unique, meaning that a name must refer to at most one language. When two or more languages are commonly known by the same name, Wiktionary distinguishes them by choosing different canonical names for each one, using a variety of means: In many cases, the languages are also known by other names. One of those other names is then chosen so that it is unique. For example, the language of the Pyu city-states, though called "Pyu" by some scholars, is called "Tircul" (code: pyx) on Wiktionary, to distinguish it from the language of Papua New Guinea which is called "Pyu" (code: pby). Alternative spellings of the same name can also be used to distinguish languages with otherwise identical names. For example, the Riang language of India and Bangladesh (code: ria) goes by the name "Reang" on Wiktionary, to distinguish it from the "Riang" of Burma/Myanmar (code: ril). If languages cannot be distinguished by alternative names, the place where each language is spoken is appended in parentheses after its name, as in the case of "Buli (Ghana)" (code: bwu) and "Buli (Indonesia)" (code: bzq). If languages go by the same name and are spoken in the same place, they can be disambiguated by their linguistic families. For example, "Mor (Austronesian)" (code: mhz) and "Mor (Papuan)" (code: moq), both of which are spoken in Indonesia. Language codes Each language on Wiktionary also has a unique code assigned to it, usually consisting of two or three letters. This code is used to identify languages when including templates in entries. Language names are not used in this case because they are longer and less precise, as the above section illustrates. Topical categories also use the language code as part of their names. The list of standard language codes can be found at Wiktionary:List of languages and a the list of special language codes, including etymology-only languages, can be found at the subpage Wiktionary:List of languages/special. Wiktionary chooses codes for languages as follows, in order of priority: If the language has a two-letter code in the ISO 639-1 standard, then that code is used. Wikipedia has a list of ISO 639-1 codes. A few languages are represented on Wiktionary by 639-1 codes the ISO has deprecated. This is generally the case when the ISO has come to consider a lect to be a group of languages, but Wiktionary still considers it a single language. Serbo-Croatian, for example, is represented by sh. If the language has a three-letter code in the ISO 639-3 standard, then that code is used. Wikipedia has a list of ISO 639-3 codes. For translingual terms the code mul is used. If the language has a three-letter code in the ISO 639-2 standard, then that code is used. This is quite rare. An example is Nahuatl, which is represented by the ISO 639-2 code nah. Any language which does not have an ISO code, but which is to be included in Wiktionary, has a new Wiktionary-specific "exceptional" code devised for it. This code consists of two parts. The first part is the nearest three-letter (ISO) family code from ISO 639-5; it is followed by a hyphen. The second part is a series of three lowercase letters which approximate the language name. (No digits, upper case letters, etc are used: IANA tags allow these, case independent, but Mediawiki software is more restrictive.) For example, Gallo is roa-gal: "roa" is the ISO 639-5 code for Romance languages, "gal" abbreviates "Gallo". In a very few cases, the Wikimedia Foundation Language Committee has already devised a code of this form to represent the language, using it in the subdomain part of the URL of the language's wiki projects; in that case, we use the Wikimedia code. For example, the WMF uses map-bms for Banyumasan (the Banyumasan Wikipedia is map-bms.wikipedia.org), so Wiktionary also represents Banyumasan using this code. If the Wikimedia code is of a different form, it is not used by Wiktionary; for example, Tarantino has the Wikimedia code roa-tara, but the Wiktionary code roa-tar. If no family to which the language belongs has an ISO code, or it is not known which family the language belonged to, the prefix und is used: for example, Kassite is represented by the code und-kas. Ancestor or "proto-" languages (which are generally reconstructed, though some are directly attested, like Proto-Norse) are assigned exceptional codes consisting of the language family's code with "-pro" added to the end: Proto-Germanic, for example, is represented by the code gem-pro. Because the entire family code is used as the first part of the code, the code may be longer than seven characters: for example, Proto-Mixe-Zoque is nai-miz-pro. Not all lects which have been assigned codes by the ISO are assigned codes or included by Wiktionary. This is the case for some constructed languages, for example. There are also many lects which the ISO has assigned codes which are not treated as distinct languages on Wiktionary. For example, the ISO assigned Moldovan/Moldavian the 639-1 code mo, but Wiktionary regards it as a form of Romanian and represents it and Romanian by the same code ro. See Wiktionary:Language treatment for more information. Mismatch with Wikimedia codes In a small number of cases, there is a mismatch between the (typically ISO-derived) code used by Wiktionary to represent a language and the code used by the Wikimedia Foundation. For example, Aromanian is represented on Wiktionary and in ISO 639-3 by the code rup, but the WMF uses the code roa-rup and locates the Aromanian Wikipedia at roa-rup.wikipedia.org. The templates such as Template:wikipedia which Wiktionary uses to link to its sister projects accept only Wiktionary codes. To enable linking to projects (such as the Aromanian Wikipedia) for which the WMF uses special codes, Module:wikimedia languages maps Wiktionary codes to Wikimedia codes, and Module:languages performs the reverse mapping. Language families मुख्य लेख: Wiktionary:Families Wiktionary sorts languages into families. Most families are related through descent from a common ancestor, but a few are merely categories, such as "creoles and pidgins". Wiktionary records which family a language belongs to in the data modules of Module:languages. Like languages, families are represented by unique codes and have unique canonical names. English belongs to the West Germanic languages (code: gmw). Serbo-Croatian belongs to South Slavic languages (code:zls). Abenaki belongs to the Algonquian languages (code: alg). Nahuatl belongs to the Nahuan languages (code: azc-nah). Some languages are not naturally descended from other languages, but show other origins. These use special types of families: The widely-used constructed language Esperanto is an artificial language (code: art). Chavacano, a creole language, is grouped under the creole or pidgin languages (code: crp). Scripts used by a language मुख्य लेख: Wiktionary:Scripts Wiktionary records which script(s) (writing systems) a language is written in as well. This information is primarily used by modules to be able to automatically detect and format non-Latin-alphabet text appropriately. Scripts, too, have unique codes and canonical names. English is written in the Latin script (code: Latn). Serbo-Croatian is written in both the Latin and the Cyrillic scripts (codes: Latn and Cyrl). Finding and organising terms in a language मुख्य लेख: :Category:All languages Every language has a main category which contains all terms that the English Wiktionary has for that language. This category is named using the canonical name of the language, followed by the word "language". For example, the main category for English is Category:English language. If the canonical name of the language already ends in the word "language", nothing is added (hence Category:American Sign Language). The main category for a language will have a variety of subcategories, which organise terms in various ways. The most important is the "lemma" category tree, which organises all lemmas in a language by their part of speech. As Wiktionary is always being expanded and improved upon, not all languages have their own categories yet, and certain subcategories may still be empty or missing. Categories are created as needed, when new entries are added to them. When content is added in a language lacking a category, it can simply be created using the {{auto cat}} template, as long as the name follows the standard format used by other languages. Languages generally also have a page which contains information that is useful to users who want to create or edit entries in that language. This page is named "Wiktionary:About (canonical name of language)", for example Wiktionary:English entry guidelines or Wiktionary:About Spanish. These pages contain a wide variety of information, depending on what other editors have found useful to note. They may explain which templates to use, specific conventions regarding spelling, pronunciation or transliteration, and more. By convention, a shortcut redirect is created to these pages for easy access, named WT:A(language code). For example, WT:AEN redirects to Wiktionary:About English (for which the code is en). Storing and retrieving language information मुख्य लेख: Wiktionary:List of languages Templates and modules use a system for storing and retrieving the various pieces of information that may be associated with a language. The module Module:languages is used to retrieve all language-related information from other modules. This module cannot be used directly in a template, so instead there is another module named Module:languages/templates, which allows templates to access the information. An overview of all basic information about a language, such as its canonical name, alternative names, code, family or scripts, can be looked up at Wiktionary:List of languages (or WT:LL for short). This is useful if you need to look up the code for a particular language, or need to know what the canonical name of a language is. The data itself is not stored in Module:languages, but instead is contained in a number of data modules (see Category:Language data modules). These are organised as follows: Module:languages/data2 contains information for all languages whose code consists of two letters. Thus, information for English (code: en) is stored here. Module:languages/data3/a through Module:languages/data3/z contain information for all languages whose code consists of three letters. There are 26 submodules, divided by the first letter of the code. Thus, information for Old English (code: ang) is located in Module:languages/data3/a, while information for Old Norse (code non) is in Module:languages/data3/n. Module:languages/datax contains all remaining languages, which have so-called "exceptional" codes. 7 ==Wiktionary:Policies and guidelines== यह एक विक्षनरी नीति, दिशानिर्देश अथवा आम विक्षनरी परंपरा जानकारी पृष्ठ है। यह एक मसौदा (ड्राफ़्ट) प्रस्ताव है। यह आधिकारिक नहीं है, यह ज्ञात नहीं कि यह विक्षनरी संपादकों द्वारा व्यापक रूप से स्वीकृत है अथवा नहीं; हालाँकि, यह संबंधित विषय पर मददगार साबित हो सकता है। Wiktionary is a collaborative project and its founders and contributors have common goals. Wiktionary policies and guidelines help us to work toward those common goals. These policies are continually evolving, and need some effort to maintain their evolution. You can contribute to the effort. Key policies You don't need to read every Wiktionary policy before you contribute! However, the following principles are key to a productive, collaborative Wiktionary experience, and should always be borne in mind. Wiktionary is a dictionary, thesaurus, and phrasebook. Wiktionary is multi-lingual in that it has entries for words from any language. It aims to cover Every Word from Every Language. This Wiktionary is the English-language Wiktionary. That means the texts of entries, including those for words from other languages, are written in English. Wiktionaries in other languages give definitions of these words in their own languages. See also the developing policy on foreign words and translations. Respect copyrights. Wiktionary is a free dictionary licensed under the terms of the GNU Free Documentation License and the Commons Attribution-ShareAlike License. Submitting work which infringes copyrights threatens our objective to build a truly free dictionary that anyone can redistribute, and could lead to legal problems. See Wiktionary copyrights for more information. Avoid bias. Entries should be written from a neutral point of view, representing all usages fairly and sympathetically. Respect other contributors. Wiktionary contributors come from many different countries and cultures, and have widely different views. Treating others with respect is key to collaborating effectively in building this Wiktionary. For some guidelines, see Wiktionary:Civility and Wiktionary:Dispute resolution. A former alphabetical list of policies was at Wiktionary:Index to Policies, but is no longer maintained. How are policies decided? Wiktionary policy will be formulated for the most part by consensus. Consensus can be reached through open debate over difficult questions, or it may simply develop as a result of established practice. The statements on this and other pages about Wiktionary policy are intended to describe community norms that are developing over time. Initial ideas might be discussed in the Beer parlour. As controversial or important policy issues are identified, someone will decide that we should think about having a policy related to this matter and create a vote that the entire community assesses. If a supermajority is reached for a certain opinion, that opinion becomes policy. Policies that result from established practice are sometimes harder to identify. If there is no objection to the practice, it may be difficult to sustain community attention long enough for a formal process of adopting it as policy. In this situation, the best solution may be to document existing practice on a language's "About" page (see here the "About" page for Latin, as an example) if necessary. How are policies enforced? You are a Wiktionary editor! Wiktionary has no editor-in-chief or any central, top-down mechanism whereby the day-to-day progress on the dictionary is monitored and approved. Instead, active participants add new articles, improve others, and make corrections to the content and format problems they see. So the participants are both writers and editors. Most policies and guidelines are thus implemented by individual users editing pages, and discussing matters with each other. There are some administrators appointed that will tackle the problems of vandalism and housekeeping, for which they need extra privileges. Anyone with a fair track record of contributions can apply for administrator status. For instructions on how to edit this information, see the documentation of any of the data modules. 8 ==Wiktionary:Picture dictionary== चित्र शब्दकोश कन्हाई प्रसाद चौरसिया/प्रयोगपृष्ठ In progress {Random entry) body body organism organism color color Solar System Solar System To do building building clothing clothing instrument instrument sport sport tool tool vehicle vehicle etc etc Participants HenkvD HenkvD Purpose Create a database of visual lexical entries comprising all words and expressions in common use, in all languages. This database must be readable both by humans and computers, so that it may be used by language learning applications, such as flashcards and other. Justification There are many words that cannot be properly conveyed by their description or translation alone. Additionally, visual representation greatly reinforces assimilation. The Picture Dictionary is of special interest for those interested in "translation-free" language learning. Translation-free language learning is still a self-defeating endeavor nowadays, due to the fact that there is no practical way for a beginner student to find out the meaning of a new word without relying on bilingual dictionary. We already have a huge image bank at Wikimedia Commons that could be incorporated on this project in a partially automated way. This project could also be used to add missing images to Wikipedia articles and to illustrate the main Wiktionary entries. Tasks 1 - Create thematic lists of vocabulary entries. This would be best done by using the Wiktionary category list, but if it's not found to be adequate, it should be improved based on other sources, such as the main Wikipedia categories, Wordnet, and other works. 2 - Select the relevant entries by accessing their frequency. This can be done by using a frequency list, searching within a corpus, or a web search. 3 - Get some representative pictures from Wikimedia Commons, upload if necessary. For added cultural authenticity the picture should from a place where the language is primarily spoken, if available. But missing pictures should be added from the English picture list until a better one is found. Templates usable in four different ways Over the past days I created a few templates that can be used to build a Picture dictionary in 4 different ways. The templates are Template:picdic Template:picdicimg Template:picdiclabel Four different ways to use Template:picdic: Solar System examples with comparable links. See also Template:picdic#Examples for these examples with coding as well. Picture dictionary with clickable images Picture dictionary with legend and wikilinks Picture dictionary with image map Picture dictionary with labels चित्र शब्दकोश Solar System heavenly body heavenly body the Sun the Sun Mercury Mercury Venus Venus Earth Earth Moon Moon Mars Mars Jupiter Jupiter Saturn Saturn Uranus Uranus Neptune Neptune comet comet asteroid belt asteroid belt orbit orbit चित्र शब्दकोश Solar System heavenly body heavenly body Legend (1): 1=the Sun 2=Mercury 3=Venus 4=Earth 5=Moon 6=Mars 7=Jupiter 8=Saturn 9=Uranus 10=Neptune 11=comet 12=asteroid belt 13=orbit 14=terrestrial planets or inner planets 15=outer planets Legend (2, in table): 1=the Sun 2=Mercury 3=Venus 4=Earth 5=Moon 6=Mars 7=Jupiter 8=Saturn 9=Uranus 10=Neptune 11=comet 12=asteroid belt 13=orbit 14=terrestrial planets or inner planets 15=outer planets चित्र शब्दकोश Solar System Click on parts of the image heavenly body heavenly body चित्र शब्दकोश Solar System the Sun Mercury Venus Earth Moon Mars Jupiter Saturn Uranus Neptune comet asteroid belt orbit Click on labels in the image heavenly body heavenly body What can be improved in these templates? I am not 100% pleased with the way to add clickable image(s) describing a hypernym of the entry. Any suggestion is welcome. HenkvD 18:13, 15 July 2010 (UTC) See also Help:Images Subpages 9 ==Wiktionary:Shortcut== Compact list of shortcuts used This list is a trimmed-down one of main shortcuts. There is also a generated list. A large number of shortcuts are like WT:AEN => Wiktionary:About English where "WT:A" is followed by a two- or three-letter code for a language. WT:-) Wiktionary:Bad jokes and other deleted nonsense WT:ADMIN (WT:A) Wiktionary:Administrators WT:AN Wiktionary:Announcements WT:BOOK Wiktionary:Bookmarklets WT:BP Wiktionary:Beer parlour WT:CAT Special:Categories WT:CFI Wiktionary:Criteria for inclusion WT:COW Wiktionary:Collaboration of the week WT:DR Wiktionary:Discussion rooms WT:DW Wiktionary:Administrators/Dishwashing WT:STYLE (WT:ELE) Wiktionary:Entry layout WT:FAQ Help:FAQ WT:GP Wiktionary:Grease pit WT:GPA Wiktionary:Grease pit/timeline WT:ID Wiktionary:Information desk WT:LOP Appendix:List of protologisms WT:RA Wiktionary:Requested entries WT:RFC Wiktionary:Requests for cleanup WT:RFCA Wiktionary:Requests for cleanup/archive WT:RFD Wiktionary:Requests for deletion WT:RFDA Wiktionary:Requests for deletion/Archives WT:RFV Wiktionary:Requests for verification WT:RFVA Wiktionary:Requests for verification/archive WT:RT Category:Request templates WT:TAT Help:Tips and tricks WT:TADDER MediaWiki talk:Gadget-TranslationAdder.js WT:TRREQ Wiktionary:Translation requests WT:TR Wiktionary:Tea room WT:VIP Wiktionary:Vandalism in progress WT:WARN Wiktionary:Warning WT:WOD (WT:WOTD) Wiktionary:Word of the day WT:SC This page, Wiktionary:Shortcuts WT:WS (WT:WSI) List of Thesaurus pages What is a Wiktionary shortcut? “Shortcuts” in Wiktionary, derived from their counterparts in Wikipedia, are a specialized type of redirection page that can be used to get to a commonly used Wiktionary reference page more quickly. How to use Wiktionary shortcuts A Wiktionary shortcut can be be entered into the Wiktionary search box to quickly bring you to a reference page. For example, you can type “WT:BP” into the search box and click the “Go” button to get to the Wiktionary:Beer parlour page, instead of having to type “Wiktionary:Beer parlour”. Alternatively, you can use the shortcut in the URL (web address). For example, you are currently viewing the Wiktionary:Shortcut page in English. The URL is http://en.wiktionary.org/wiki/Wiktionary:Shortcut You could get from here to the Wiktionary:Beer parlour page by replacing “Wiktionary:Shortcut” with “WT:BP” in the URL (web address) field (followed by “Enter”). Shortcuts are presented in all capital letters (“All-Caps”), but the search box is case-insensitive. For example, in the search box, you can type “wt:bp” instead of “WT:BP”. However, using the URL method typically requires that you match the capitalization of the shortcut. Adding shortcut link boxes in the destination pages You can add a “shortcut link box” in a shortcut destination page, in order to educate the users about the shortcuts available. A shortcut link box (the “shortcut template”) is added to the entry source (“Editing” page) using {{shortcut|WT:xxx}}. Examples {{shortcut|WT:BP}} {{shortcut|WT:WS}} 10== Wiktionary:Templates== A template is a page in the Template: namespace, which contains special wiki code that allows it to be reproduced ("transcluded") on== many different pages. Templates can either be transcluded directly, or you can pass on additional information (through "parameters") to the template that controls or modifies its behaviour. The advantage of using templates is that when the template itself is changed, all pages that transclude the template will automatically be updated as well. This helps in reducing the duplication of identical content, and templates are a powerful tool for keeping the appearance of certain parts of a dictionary entry consistent. For example, a single template to generate a table of inflected forms of a verb can be used on hundreds of different pages, but will look and function the same on each one. Generally speaking, if you find yourself having to add more or less the same thing on several pages, it's probably better to write a template instead and transclude it onto the pages. Wiktionary makes heavy use of templates, so it is a good idea to familiarise yourself with how they work and how to use them, even if you don't write your own. Templates can be found in Category:Templates and its subcategories. Writing templates Templates may either use a Scribunto module as underlying mechanism, or be written directly in template code. Although Scribunto is strongly preferred for templates with complex logic, a straightforward string-assembly template probably doesn't need a module. Some templates may also mix both, calling on Scribunto for some parts while using template/wiki code for the remainder. Here are some good guides for using and writing templates: Meta:Help:Template Meta:Help:A quick guide to templates Meta:Help:Advanced templates MediaWikiWiki:Help:Extension:ParserFunctions – template functions such as #if and #switch Meta:Help:Editing sections of included templates Meta:Help:Parameter default Meta:Help:Variable Meta:Help:Array If you want to create a new template, but you're still inexperienced with them or with Wiktionary in general, it's probably best to ask first (at the WT:Grease Pit). Maybe there isn't really a need for such a template, because the problem you are trying to solve with it can be approached differently. Maybe someone else already wrote something similar to your idea; it would be better to use what already exists instead of doing it all over again. For that reason, the best way to "learn" templates is probably to study the ones we already have on Wiktionary. Language-specific templates Many languages have their own set of templates, which can be found in one of the subcategories of Category:Templates by language. Language-specific templates are better able to cater to the needs of a specific language than a general template can, and allow for specific exceptions or restrictions that general templates don't. Because they are made for a specific language, knowledge of that language's grammar can be embedded into them. For example, the template {{es-conj}} automatically generates a table with a full set of inflected forms of a Spanish verb, while {{en-noun}} is capable of automatically showing the plural form of many English nouns. While it may be easier to use generic templates like {{head}} to start off with, you'll eventually come to a point where it's better to create a tailor-made set of templates for your language. At that point, however, you'll already have all the "old" entries to deal with, which still use the generic all-language templates, which you'll then have to fix. For that reason, it's encouraged to create at least a basic set of headword-line templates (see below) for each language, before you start to create entries in that language. Naming templates Try to use a name that is both short and descriptive. As a rule of thumb, the more often the template will be used, the more leeway there is in using a short name. Templates that are used only within other templates should have longer names, as they generally don't need to be used that often. If you can, try to avoid using characters outside the ASCII encoding (use only the Latin alphabet), so that everyone can easily type the template's name. Templates that are intended specifically for one language should have a name that begins with that language's language code, followed by a hyphen. For example, {{en-verb}} is intended to be used for English entries, {{nl-adj form of}} for Dutch entries, {{fr-conj-auto}} for French entries, {{sl-decl-adj}} for Slovene, and so on. What follows after the code is up to the creator of the template, but there are certain naming conventions that are followed, on which more below. If you are writing a template for a specific language, you include any of the characters that are used in that language as part of the name. However, even then, using just the Latin alphabet is preferable. By convention, usage-note templates have names beginning with U:, followed in most cases by a language code and then another colon, and then a short, descriptive name; for example, Template:U:en:less and fewer. (A small number of usage-note templates may be applicable across multiple languages and may omit the language code.) Reference templates have names beginning with R: (optionally followed by a language code and then another colon) and then a short, descriptive name; for example, Template:R:mia:Costa:2003 or Template:R:Etymonline. Changing existing templates Special care should be taken when making changes to an existing template, since the changes will (potentially) affect all pages that transclude the template. Depending on the editing interface you are using, you should be able to preview your changes before publishing them (in the standard editor the relevant features are called "Show preview" and "Show changes"). You may also be able to preview (before publishing) how another page that calls the template you are editing will look once your changes are applied ("Preview page with this template"). Most of our templates can be modified by any user, but sometimes templates are protected from editing by regular users. In such a case, proposed changes can be discussed on the template's associated discussion page or in Wiktionary:Grease pit to gain consensus before requesting that the changes be made by a template editor. Showing a link to the template page and documentation To display a link to a template page presented in the style of a call to that template, you can use: {{temp|template name}} For example: {{temp|quote}} produces: {{quote}} where you can follow the link to see how to use the "quote" template. This is useful in discussions and in template documentation, but should not be used in our dictionary entries. Headword-line templates मुख्य श्रेणी: Headword-line templates by language Headword-line templates are templates that are used to produce the headword line of a term. (historical note: this was formerly called the "inflection line", and headword-line templates used to be called "inflection templates") The headword line is the line that comes immediately below the header specifying the part of speech (such as Noun or Verb). At the very least, the headword line contains the headword in question, specially formatted in bold text. Additional information may also be presented on the headword line, such as the gender of a noun (for languages where that applies), or a selection of inflected forms. Most languages have their own set of headword-line templates; these are the most common form of language-specific template. In cases where the language lacks an appropriate headword-line template, {{head}} should be used. Naming Headword-line templates are named using the language code, followed by an abbreviated form of the part of speech that the template is used for. For example, {{nl-verb}} is for the headword line of Dutch verbs, {{en-noun}} is for English nouns, and so on. The following abbreviated part-of-speech names are currently in common use: Adjective: adj Adverb: adv Conjunction: con Determiner: det Interjection: interj Noun: noun Numeral: num Particle: part Postposition: postp Preposition: prep Pronoun: pron Proper noun: proper noun Verb: verb Languages may extend these names if they need templates for more specific purposes, such as {{nl-noun-dim}} for Dutch diminutive nouns. It's common to add -form at the end if the template is to be used for words that are not full dictionary entries (they are not lemmas) but are a form of another word. For example {{nl-adj-form}} for Dutch adjective forms. Formatting the headword The headword itself appears in boldface, unless it's in a writing system where bold text is harder to read, in which case it appears with a larger font-size (this is controlled through MediaWiki:Common.css). Within the template's code, the {{PAGENAME}} magic word is used to automatically display the name of the current page. Most headword-line templates also provide a parameter named |head=, which allows other editors override this default display, in case this is desired (for example, if additional accent marks should be displayed on the headword). Some templates may use other names for this parameter, but |head= is the most common and the most standard, so it is preferred for the sake of easy interoperability. There are a few different ways that headword lines have been created in the past using a template. Not all of them should be used anymore, but you may encounter such code in older templates and entries that have not been brought up to date. The currently preferred method is to invoke {{head}} from within the template. This allows the template to use the additional features that {{head}} provides, such as automatic script detection, transliteration and link processing. Examples: {{head|fr|noun|head={{{head|}}}}} {{head|ru|noun|head={{{head|}}}}} An older method was to write the raw HTML: the "strong" HTML element with the |class="headword" HTML attribute. This element is provided with a |lang= HTML attribute to specify the language code of the language that the word is part of. An additional HTML class, the script code, should be provided if the headword is not written in the Latin alphabet but in some other writing system like Cyrillic or Chinese. Examples: <strong class="headword" lang="fr">{{{head|{{PAGENAME}}}}}</strong> <strong class="headword Cyrl" lang="ru">{{{head|{{PAGENAME}}}}}</strong> A still older method was to simply surround the headword with wikicode to make it appear bold. This method is deprecated and discouraged because it does not supply the appropriate language or styling information, which is needed by browsers to select the correct fonts and provide further support for the language (such as adjusting the language of a screen reader). '''{{{head|{{PAGENAME}}}}}''' Genders and other grammar information For languages that have grammatical genders, the gender usually immediately follows the headword. Genders should be formatted using Module:gender and number or through {{g}}. Many templates allow you to indicate the gender by passing it as the first numbered parameter, although the |g= parameter is also commonly used (it is used by {{head}}). Writing the template to use the numbered parameter is preferred, however, because it's less likely to be overlooked by other editors – you have to consciously "skip" the first parameter to get to the second, which makes it more obvious when you forget it. Thus, a template that is used like {{ca-noun|m}} is preferred to one that is used like {{ca-noun|g=m}} (the ca-noun template itself already uses the first format, so using the second is an error in this case). It's usually good coding practice to add code to the template that checks whether the gender that has been provided to the template is valid. For example, French has no neuter gender, so if someone writes {{fr-noun|n}}, then that is an error. If it's not valid, the template should add the page to a cleanup category such as Category:French nouns lacking gender, so that it can be corrected. Inflected and related forms Following the headword and optional gender information, you can choose to display additional forms of the word, surrounded by parentheses. {{en-verb}} displays the various forms of an English verb, for example, while {{nl-adj}} displays the comparative and superlative form of a Dutch adjective. When displaying and/or linking to forms in the template, you can either use a generic linking template like {{l}} or, preferably, write out the link manually. When writing out the link, always link to the appropriate section. You should also provide the language code (with the |lang= HTML attribute) and a HTML class for the script code if it's not Latin. The forms should be displayed in bold while the grammatical information (such as "comparative" or "past tense") is displayed in italics. This should be done even if the letters don't normally look right in bold font – the language and script tags will ensure (through style sheets) that the text will not actually be bolded if it's not appropriate. Here are some varieties you can use (with example words already filled in; normally the template would determine these through other means such as parameters or the page name): (''plural'' <b lang="nl">[[woorden#Dutch|woorden]]</b>, ''diminutive'' <b lang="nl">[[woordje#Dutch|woordje]]</b>) (''genitive'' <span lang="sl">'''[[besede#Slovene|bésede]]'''</span>) (''simplified'' <b lang="cmn" class="Hani">[[马#Mandarin|马]]</b>, ''pinyin'' <b lang="cmn-pinyin">mǎ</b>, ''Wide-Giles'' <b lang="cmn-wadegile">ma<sup>3</sup></b>) A template may need additional parameters to correctly display the additional forms, while some forms can be determined automatically. Different templates currently use different approaches. {{nl-noun}} requires you to manually enter the forms, and will display a notice on the page and add the entry to a category if they are missing. {{en-verb}} on the other hand generates them automatically. There are pros and cons to both approaches. Determining the forms automatically makes things easier for the editor, because they do not have to concern themselves with the details. On the other hand, automatically-generated forms may not be correct, while they will more likely be correct if they have to be entered manually. Requiring editors to manually enter the forms also means that a user can add the template to an entry without having to worry whether the forms it has generated are correct (this is useful because an editor may not know the language but still want to add the template to an entry in that language). You will therefore have to make a trade-off. If the forms that the template can automatically generate are correct in the majority of cases, then it makes sense to do so. However, if automatically generated forms can only be correct in a small amount of cases, it makes more sense to require the editor to enter them. Be very mindful of which forms you choose to include in this way. While a lightly-inflected language like English only has a few forms, languages like Latin may have dozens, and they could never fit onto a single line (also keep in mind that some users might have smaller screens!). If a word in your language has too many distinct forms to fit on one line (4–5 is probably about the limit) then it's better to show either no forms on the headword-line, or show only a few key forms that help users figure out the remainder themselves. For Latin verbs in particular, the four verb forms that are displayed on the headword line are the least predictable forms, which most other forms can be regularly derived from (so-called "principal parts"). Categories It is generally expected that every headword-line template will add the entry to a category corresponding to its part of speech. {{en-verb}} adds the entry it is added to Category:English verbs, {{fr-noun}} adds it to Category:French nouns, {{nl-adj-form}} adds it to Category:Dutch adjective forms. The template {{head}} has a parameter to specify the language and category: {{head|ru|adjective}} adds the entry to Category:Russian adjectives. Inflection-table templates मुख्य श्रेणी: Inflection-table templates by language Languages that use several different forms of the same word often use inflection-table templates. These are templates that display a table or list containing all or most of the inflected forms of a particular word. Unless they are very small, these tables should be made collapsible, by enclosing them in the following code: <div class="NavFrame"> <div class="NavHead">(text to display when the table is collapsed)</div> <div class="NavContent"> (put the table itself here) </div> </div> By convention, tables that show the forms of nouns, pronouns and adjectives are named decl and are placed in a ====Declension==== section on the page, while tables that show the forms of verbs are named conj and are placed in a ====Conjugation==== section. Usually, the name also includes the specific inflection type or class that the word may follow. {{nl-decl-adj}} is used for Dutch adjectives, for example, while {{es-conj}} is used for Spanish verbs. However, sometimes there is no need for such a distinction and only a single template is needed: {{eo-conj}}. If a language needs at least two different templates for different inflectional classes of the same type of word, then it is considered good practice to create a third template, with the name ending in -table. This template should display the table itself, but should not create any of the forms that appear in the table. It should be "indifferent" to the specific kind of inflection, so to speak (programmers call this "separating interface and implementation"). An example of this is {{ca-conj-table}}, which is used as a general table, while {{ca-conj-ar}}, {{ca-conj-ir}} and others transclude the basic table template and fill it with the appropriate forms. If your language only needs one table of its kind (like {{eo-conj}} in Esperanto, where all verbs inflect exactly the same), then you probably won't need to separate the templates' duties in this way, but it may still help for clarity if nothing else. Form-of templates मुख्य श्रेणियाँ: Form-of templates, तथा Form-of templates by language On Wiktionary, a form-of entry is an entry for a word that is considered an inflected form of another word. Such entries don't contain a full definition. Usually the definition is a short description of the grammatical properties of this form, and a link to the main entry. Compare, for example, the entries for locate and its past-tense form located. The definitions of such entries are generated automatically with templates. There is a wide variety of form-of templates, and many of them not specific to one language but can be used for most languages. For that reason, it is often not necessary to create form-of templates for your language. It doesn't hurt to do so anyway, but it may be considered wasteful and redundant if your template does what a generic template already does perfectly. Some form-of templates also add the entry to a category. {{comparative of}}, when provided with the parameter |lang=da, adds the entry to Category:Danish comparative adjectives. This may or may not be desirable. Generally, the headword-line should add the category, so it is at the very least redundant if the form-of template also does this. Furthermore, a template may be used for more than one part of speech (case in point: {{comparative of}} can be used for adjectives, adverbs or determiners), and it may also conflict with the way a language's categories are structured. Therefore, it's probably good practice to not add categories with form-of templates, or to add only additional categories and not the main part-of speech category. Context label templates (please expand) {{label|____}} Tag a term in a definition and add a category link for it. Put this just after the "#" character and before the definition text. For example, to have (mathematics) appear, one may use {{label|en|mathematics}} and the term will also be added to Category:en:Mathematics. {{qualifier|____}} Shows the given qualifiers in a reader-customizable style, e.g., (qualifier). The default style is with parentheses and italics. This template is intended generally only used in the definition of other templates, but may also be used directly in articles at the beginning of a list item if no other template applies. Examples {{ux}} — show usage examples under a definition line {{uxi}} — inline form of the {{ux}} Category boilerplate templates (please expand) Citations Templates for entering quotations (also Category:Citation templates): {{quote-book}} {{quote-journal}} {{quote-meta}} ... Templates for referring to sources in quotations: See Category:Reference templates and [१]. Columns Long lists of terms (such as derived terms or translations) usually look better when formatted into columns. The templates below provide an easy method of doing this. Current Wiktionary style is to put such material in collapsible tables so that the user can display it only if they wish to. This makes an entry easier to read and navigate. Alternatively, content may be made permanently visible. It is preferable to use collapsible tables for long lists and to make only short lists permanently visible, or to use collapsible tables for all lists (given that short lists may eventually become much longer). To use any of these templates, place the "top" template immediately before the content and the "bottom" template immediately after. Place the "mid" (or "mid2") template as close to halfway through the content as possible. If using the templates for more than two columns, place a "mid3" template at one-third and another two-thirds of the way through the content, or the "mid4" at one-quarter, one-half and three-quarters of the way through. Use the templates from one group only at any one time. Do not combine templates from different groups, as this will give odd results or might not be parsed correctly by the browser. For "Translations" sections The following templates display translations in two columns in a collapsible table for the translations sections. They are for use only in the Translations section of an article; in other sections, use the templates below. The "trans-top" template takes an argument that is used as the header for the table. A gloss summarising the meaning being translated is put here. For example, in the entry for time, the gloss "inevitable passing of events" is given in the first table of translations, and this is generated thus: {{trans-top|inevitable passing of events}}. {{trans-top}} {{trans-mid}} {{trans-bottom}} Currently, templates for collapsible translation tables are available only in two-column format. For other lists Collapsible tables The following templates display lists in two columns in a collapsible table. They are for use in sections other than the Translations section of an article (not just the Related terms section, despite the name); in the Translations sections, use the templates above. The "rel-top" template takes an argument that is used as the header for the table. A gloss summarising the content of the table. For example, in the entry for time, the table of derived terms has the header "terms derived from time", and this is generated thus: {{rel-top|terms derived from ''time''}}. Note that this is the preferred format of a gloss for derived and related terms (which would have the header "terms related to time"). Note that the word or phrase which the terms are derived from or related to is italicised. {{rel-top}} {{rel-mid}} {{rel-bottom}} Very long lists can be formatted in four columns using the following: {{rel-top4}} {{rel-mid4}} {{rel-bottom}} where {{rel-mid4}} is to be used three times within the content to separate it into four columns of equal or approximately equal length. For lists that are always displayed Alternatively, a list of terms can be formatted so that it is always displayed (that is, not hidden in a collapsible table). This format is best reserved for short lists. The following templates display content in two, three or four columns. They are not for use in a Translations section of an article; in the Translations section, use {{trans-top}} etc. as described above. Two columns {{top2}} {{mid2}} {{bottom}} Three columns {{top3}} {{mid3}} {{mid3}} {{bottom}} Four columns {{top4}} {{mid4}} {{mid4}} {{mid4}} {{bottom}} Etymology Etymology templates: {{derived}} (shortcut {{der}}) {{borrowed}} (shortcut {{bor}}) {{learned borrowing}} (shortcut {{lbor}} {{orthographic borrowing}} (shortcut {{obor}} {{inherited}} (shortcut {{inh}}) {{PIE root}} {{affix}} (shortcut {{af}}) {{prefix}} (shortcut {{pre}}) {{confix}} (shortcut {{con}}) {{suffix}} (shortcut {{suf}}) {{compound}} (shortcut {{com}}) {{blend}} {{clipping}} {{short for}} {{back-form}} {{doublet}} {{onomatopoeic}} (shortcut {{onom}}) {{calque}} (shortcut {{cal}}) {{semantic loan}} (shortcut {{sl}}) {{named-after}} {{phono-semantic matching}} (shortcut {{psm}}) {{mention}} (shortcut {{m}}) {{cognate}} (shortcut {{cog}}) {{noncognate}} (shortcut {{noncog}}) {{langname-mention}} (shortcut {{m+}}) – like mention but also can generate a Wikipedia link for the language when used with w=1 {{rfe}} {{etystub}} {{unknown}} (shortcut {{unk}}) – only for words where no etymological information exists Languages: These templates "wrap" the language abbreviations used in Webster 1913 (see Wiktionary:Abbreviations in Webster#Languages). One function of these templates is to make transcribing etymologies from Webster 1913 simple. Another function is to expand the obscure abbreviation into the full name of the language. A third function of these templates is to automatically categorize words according to their etymologies (see Wiktionary:Categorization). These templates will automatically both add a word to an etymology category and create an interwiki link to the language article on Wikipedia, as well as expand to the name of the language, and are suitable for use in the "Etymology" section of an article. 11