text:
Appendix:English pronunciation

English
The following tables show the International Phonetic Alphabet (IPA) and the English pronunciation (enPR) or (AHD) symbols that are used to represent the various sounds of the. The sounds of Received Pronunciation (RP, UK), General American pronunciation (GenAm, US), Canadian English (CanE), Australian English (AuE), and New Zealand English (NZE) are shown.

For vowels in other dialects, see Wikipedia's. An image of an old version of these tables is available.

Vowels
For a fuller list of dialects, see.

dialects (RP, Australia, New Zealand) do not pronounce what was historically a syllable-final r; instead they have a schwa, centering diphthong (ending in ), or a long vowel (ending in ). Rhotic dialects (General American and Canadian) pronounce the syllable-final r. Also, they make no vowel length distinction, so none of their vowels end in the length symbol.

This vowel table below lists the standard phonemic vowel notations in each accent and contains both monophthongs and diphthongs. Variations of notation within the same accent are also listed.

Foreign vowels
Found primarily in some English dictionaries' transcription of the original (foreign) pronunciations of foreign words, especially French or German.

In order to allow Module:syllables to count syllables, the disyllabic sequence must be transcribed with a period to mark the syllable break –  – so that it will not be confused with the New Zealand diphthong.

Syllable-final is sometimes replaced with :  instead of. In order to keep Module:syllables from counting as a syllable, add the non-syllabic diacritic:.

Some speakers do not contrast unstressed /ɪ/ and /ə/, or the two sounds may be in free variation. Some sources use the symbol ⟨ɨ⟩ or ⟨ᵻ⟩ to indicate the vowel which results from the merger of, or which may be pronounced as either of, these sounds.

To be added or sorted into the table above: bath, cloth.

Fortis and lenis
The so-called voiceless and voiced obstruents are more properly. Each member of a fortis–lenis pair is distinguished from the other by various articulatory and auditory features, but not consistently by voicing or lack of it.

In most dialects of English, the fortis (voiceless) stops and affricate are always voiceless, and are aspirated  at the beginning of a word and at the beginning of a stressed syllable: for example, RP today, chain  and account. Vowels and sonorants immediately preceding syllable final fortis obstruents are usually pronounced shorter than before lenis obstruents, as in bet vs. bed and bent vs. bend. This phenomenon is known as pre-fortis clipping.

The lenis (voiced) stops and affricate are always unaspirated. Lenis obstruents are often devoiced at the beginning or end of words, but are fully voiced between voiced vowels and sonorants.

The fortis–lenis distinction is neutralized in a few cases.

Initial consonant clusters consisting of and a stop (as in, , ) are typically analyzed as having a fortis stop, which agrees with the spelling, but may be analyzed equally well as having a lenis stop (i.e., , , ). The stop is both voiceless and unaspirated, and there is no additional phonetic feature that establishes it as either fortis or lenis.

In addition, some dialects have a sound change known as intervocalic alveolar, in which are both pronounced as an alveolar flap  between vowels or liquids and when not at the beginning of a stressed syllable. Further, in American English, between vowels may be pronounced as a nasalized alveolar flap,. The fortis stop loses its distinctive voicelessness, and essentially becomes lenis. Flapping causes and  to both be pronounced as, and causes  to be pronounced as , similar to.

Linking semivowels
When two vowels occur next to each other (termed hiatus), speakers sometimes perceive the vowels to be separated by a sound similar to one of the semivowels /j w/. The identity of such "linking semivowels" is predictable based on the identity of the preceding vowel: a /j/-like sound may be perceived after vowels ending in a high front unrounded sound, such as /iː~i/, /ɔɪ~oɪ/, /aɪ~ʌɪ~ɑɪ/, /eɪ~æɪ/, whereas a /w/-like sound may be perceived after vowels ending in a high back (or central) rounded sound, such as /uː~u~ʉː/, /aʊ~æʊ/, /əʊ~oʊ~əʉ~ɐʉ/.

Even though some speakers hear semivowels in these contexts, there is evidence that such "linking" semivowels are not phonetically identical to the semivowel phonemes that can be found at the start of words (as in "yearn" /jɜː(r)n/ or "weevil" /wiːvəl/). For example, the phonetician John Wells discusses "I earn" versus "I yearn" and "two evils" versus "two weevils" as minimal pairs showing that there is usually no neutralization of the phonemic contrast between the sequences /ɑɪ.ɜː/ and /ɑɪ.jɜː/, or between /tuː.iː/ and /tuː.wiː/. Therefore, such "linking semivowels" should not be included in phonemic transcriptions.

It is also inadvisable to include them in phonetic transcriptions, since a number of phoneticians have argued that what is heard as a semivowel is actually nothing more than the final portion of the preceding vowel or diphthong. For example, assuming we transcribe yellow and ready as [ˈjɛləʊ] and [ˈɹɛdi], it is unnecessary and redundant to use transcriptions such as yellowing [ˈjɛləʊwɪŋ] or readying [ˈɹɛdijɪŋ] as opposed to [ˈjɛləʊɪŋ] and [ˈɹɛdiɪŋ], since there is likely no distinction on the phonetic level between the segments transcribed [ʊ], [i] and the supposedly following segments [w], [j]. A 2014 phonetic study of American English found that there were significant acoustic differences between the pronunciation of two vowels separated by a phonemic glide, and sequences of a high vowel or diphthong followed by a vowel: the perceptual illusion of a glide in the latter case could be explained in terms of a diphthongal realization of the first vowel phoneme, rather than insertion of a glide after it.

An alternative analysis of the English vowel system treats the glides /j w/ as an inherent part of diphthongs and "tense" vowels. In this kind of analysis (which is not used on Wiktionary), words like yellow, yellowing and ready, readying might be transcribed as /ˈjɛləw/, /ˈjɛləwɪŋ/ and /ˈɹɛdɪj/, /ˈɹɛdɪjɪŋ/. Note that this analysis also does not involve glide insertion when these vowels are placed before other vowels.

Other symbols
A stress mark is placed before the syllable that is stressed in IPA and after it in enPR / AHD.

Note: The EnPR and print AHD marks are formatted slightly differently. Online, AHD writes both, though they do not always represent the same phoneme.

title: Appendix:English pronunciation


text:
raven

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

Noun

 * 1)  Any of several, generally large and lustrous black species of birds in the genus Corvus, especially the common raven,.
 * 2) A jet-black colour.
 * 1) A jet-black colour.

Adjective

 * 1) Of the color of the raven; jet-black.

Etymology 2
From, , from , itself from , from , itself from.

Noun

 * 1) Rapine; rapacity.
 * 2) Prey; plunder; food obtained by violence.

Verb

 * 1)  To obtain or seize by violence.
 * 2)  To devour with great eagerness.
 * 3)  To prey on with rapacity.
 * The raven is both a scavenger, who ravens a dead animal almost like a vulture, and a bird of prey, who commonly ravens to catch a rodent.
 * 1)  To show rapacity; to be greedy (for something).
 * The raven is both a scavenger, who ravens a dead animal almost like a vulture, and a bird of prey, who commonly ravens to catch a rodent.
 * 1)  To show rapacity; to be greedy (for something).

Etymology 1
Borrowed from.

Verb

 * 1) to (hold a) rave, to party wildly

Etymology
From, possibly after.

Verb
(or as past participle: )

 * 1)  to rave

Etymology
From, from.

Etymology
From.

Adjective

 * 1) even, level

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

title: raven


text:
Talk:crow

Thanks, mav. Where can I find the pronunciaton keys?

v. i. is verb intranstive, v. t. is verb transitive. -- Zoe

Proto-Germanic
I'm assuming this is cognate to Latin  so there's a Proto-Indo-European root somewhere. Mglovesfun (talk) 22:56, 3 July 2010 (UTC)
 * No, that's not possible – you forgot to consider the Germanic consonant shift (Grimm's law). Only *hrabnaz "raven" can be connected with corvus (but only via a root etymology; presumably a root *ker- "to shout", though it does not seem to be attested as a verb: I haven't found a fitting root in LIV). The root you are looking for is "to cry hoarsely" (though this is another noise root à la Pokorny that seems to be found only in nominal derivations: again, nothing in LIV). --Florian Blaschke (talk) 22:16, 3 July 2013 (UTC)

Snot?
Any reason why the Northern English slang definition of crow as snot/booger/bogey isn't included here?

--StrodoDoggins (talk) 21:24, 7 February 2023 (UTC)

title: Talk:crow


text:
elephant

Etymology

From, , from , , , re-latinized in as , from , from  (gen. ). Believed to be derived from an  form such as  (compare 🇨🇬, 🇨🇬) or. More at. Replaced 🇨🇬 (from the aforementioned form, from 🇨🇬), which replaced 🇨🇬.

Noun

 * 1) A mammal of the order Proboscidea, having a trunk, and two large ivory tusks jutting from the upper jaw.
 * 2)  Any member of the subfamily Elephantinae not also of the genera  and Primelephas.
 * 3)  Anything huge and ponderous.
 * Let's play hide and seek. I'll count. One elephant, two elephant, three elephant...
 * 1)  Ivory.
 * 2)  A xiangqi piece that is moved two points diagonally, may not jump over intervening pieces and may not cross the river.
 * 1)  Ivory.
 * 2)  A xiangqi piece that is moved two points diagonally, may not jump over intervening pieces and may not cross the river.
 * 1)  A xiangqi piece that is moved two points diagonally, may not jump over intervening pieces and may not cross the river.

Synonyms

 * see Appendix:Words used as placeholders to count seconds
 * see Appendix:Words used as placeholders to count seconds

Noun

 * 1)  animal

title: elephant


text:
User:Ellmist~enwiktionary

See: http://www.wikipedia.org/wiki/User:Ellmist

title: User:Ellmist~enwiktionary


text:
Pope Julius

Etymology
. Presumably named after Pope Julius II, the Warrior Pope.

Noun

 * 1)  A sixteenth-century gambling card game about which little is known.

title: Pope Julius


text: GNU FDL

title: GNU FDL


text:
User:Youandme

A Wiktionarist from Poland.

My experience, as far as languages are concerned: Future interests
 * Polish quite long :-)
 * English - I hope sufficently long, a bit shorter than Polish
 * Russian - long but not so valuable as English
 * German - longer than French, I guess that one could call it better than basic
 * French - shorter than German and no practical yet
 * Chinese - basic and practical
 * Tibetan - basic and practical
 * Of course, that's improvement of my current linguistic knowledge.
 * I'm also curious about four artificial languages I've got to know (thanks to work on Wikipedia):
 * Lojban
 * Esperanto
 * Interlingua
 * Slovio
 * and about tonal languages of Asia
 * and about those found in Polynesia.

title: User:Youandme


text:
Wiktionary talk:Common misspellings

I think this page and relevant maintenance page will be useless - almost all possible permutations of letters will be acceptable some time in the future. Unless we separate languages and their maintenance scripts. But even though all the alien words (links to other languages) for a given language perhaps will spoil the list of results. Youandme 03:55 Dec 13, 2002 (UTC)
 * Yeah, I've looked at this and am inclined to agree. For now I've wikified the entries (using the replace function from MS Word), but the over 1,800 lines still need more personal attention.  I would also question just how "common" some of these errors are.  There are also many items on the list which are "typos", i.e. errors that are caused by mistyoing words that one knows perfectly well.  ("Mistyoing" is the preceeding sentence was an example of such an unintentional error; keeping it there was intentional to prove my point.)  These errors can happen anywhere in a word, and although some are indeed more common than others, they probably do not merit an entry.

 * To the extent that a remark is needed or useful it should probably appear on the page for the erroneous word, and again in the variants section for the correct word(s) where the fact that it is a misspelling would be noted. That being said, I'm inclined to treat this list as a sort of to-do list, where lines are removed whne it is determined that a particular error does not merit attention, or when it has been remarked at appropriate places. Eclecticology 22:31 Feb 20, 2003 (UTC)

title: Wiktionary talk:Common misspellings


text:
Help:FAQ

Starting out
Q: How do I add a new word?

 * A: You can find out at Help:Starting a new page.

Q: Where is the alphabetical listing?

 * A: Try using the search feature instead. Special:Allpages lists all of the pages in Wiktionary, including the utility pages in the Wiktionary: namespace. Category:English lemmas gives an alphabetic listing of English entries in Wiktionary, and pages in Category:Lemmas by language do the same for other languages.

Q: I’ve found a common word that is missing from Wiktionary, and thought of adding a seed entry. But it seems like you want fully grown entries or nothing! I’m not a lexicologist. I’m just someone who feels they can contribute some simple dictionary definitions. I don’t know anything about etymology, translations or whatever! In Wikipedia a lot of people are quite happy to come along and copy-edit, wikify etc. Does that apply here?

 * A: Yes! Wiktionary is far from complete, but the wiki philosophy is just as strong. If a word does not exist on Wiktionary, add it. If you know nothing about etymology that’s fine; your humblest contribution is still better than nothing. Someone else can add the etymology later. The minimum you need to include is the language of the word, its part of speech, and its meaning.

 * However, if you are contributing a translation, it is important to know to which meaning of the word the translation applies.

Q: I’ve already done some work without signing up, but now I would like to create a username to have all my work shown as my own. How can I create a new username?

 * A: Just click on the Create an account or log in link on the top right of every Wiktionary page or Special:Userlogin.

Q: What are the characters in the logo?

 * A: Clockwise: シ, श, 말, ش, ש , 维, Ж, λ, W.

Q: Which words can have entries in Wiktionary?

 * A: This Wiktionary is intended to include "all words in all languages", with the definitions given in English. For which terms can be included, see Criteria for inclusion.

Pronunciation
Q: Is there a table indicating which IPA symbols make certain sounds?

 * A. Near the top of a page, there should be a pronunciation section, like so:
 * Just follow the links.
 * Just follow the links.

Q: How do we type those symbols?

 * A: When you are in the edit page you will see below the save buttons a box with many accented letters and a pull-down menu that reads “Latin/Roman”. Select “IPA and enPR” from the pull-down menu. (There isn’t an option for SAMPA as all SAMPA characters can be typed on an ordinary keyboard.) Position the text cursor where you want the symbol to be inserted, then click on the desired character.

Q: The IPA symbols are showing up as blocks in Internet Explorer, is there a way to fix this?

 * A. The easiest way for Windows/Internet Explorer users is to make sure the font “Arial Unicode MS” is installed on your computer. Then, in Internet Explorer go to Tools/Internet Options.../General tab. Select the “Fonts...” button at the bottom. Make sure the “Language script” displays “Latin based”, then set the “Web Page Font” to “Arial Unicode MS”. Click OK twice to exit.

Q: I’ve tried the above, and it still doesn’t work. Any other ideas?

 * A: Works fine when setting Skin to Classic, Nostalgica or MySkin on your Preferences side, but not with Skins Cologne Blue, MonoBook. Would be nice if somebody could fix this. Alternatively, try a different browser, such as Firefox, which displays these characters correctly.

Q: Are there any articles with sound pronunciation for the word? Is it possible for myself to record and submit a word pronunciation?

 * A: Yes; any article on this list (of articles that reference Template:audio) has a pronunciation; you can make requests at Pronunciation file requests. It's possible for anyone to record and submit pronunciations of words, but don't upload them here: they belong on Commons: so all the Wiktionaries can use them. For details see Help:Audio pronunciations and c:Commons:Pronunciation files requests.

Article format
Q: How do we format articles? Is there a standard format we should use?

 * A: Guidelines for this can be seen at Entry layout. The concepts on that page have varying levels of acceptability, and continue to evolve as new techniques are developed to deal with a wide array of challenges relating to different languages.

Q: Some people link to other words as they type a definition. Since every English word would eventually be listed on the Wiktionary, maybe someone could add a code (which perhaps could be turned off) that made every word link to its corresponding entry.

 * A: When an article is loaded the software checks each linking word to see if the article for the word exists, and it is marked in blue if it exists, red if it does not. It only takes a fraction of a second to check each word, but if more words are checked this time is cumulative. If every word is checked, it could cause serious slowdowns. This already happens in link-rich articles. How often does one really need a link to “the”?
 * Also, it’s often clearer to link a compound word, or the root of a word, depending on the meaning.

Real words
Q: That’s not a real word, is it?

 * A: In general, Wiktionary does not concern itself with metaphysical abstractions like “realness”. Instead, we use a set of objective criteria for inclusion (WT:CFI), and a word may meet those requirements in a number of ways, such as through its use in multiple publications over an extended period of time.

Writing definitions
Q: How should we go about writing definitions?

 * A: In some respects writing a definition is an art. Begin by finding examples where the word is used, and distill a definition that would be accurate for all of the examples. It may very well be that a word can have more than one definition. You can then add the quotations as examples. See also Help:Writing definitions & How to Write a Dictionary Definition.

Q: How shouldn’t we go about writing definitions?

 * A: One should not simply copy without crediting the definitions from other dictionaries and glossaries.

Q: Can I use what I find in other dictionaries and glossaries? How? How much?

 * A: Yes and no! Wiktionary should represent the language as it is used in practice, and that is best done through evidence of usage. Not all dictionaries provide this kind of evidence and may only reflect usages current at the time that the dictionary was published. The 1913 edition of Webster’s Dictionary is a popular freely available source, but it must be supplemented to show how some words have changed since 1913.

 * There are copyright issues associated with more recent dictionaries. Also, specialized glossaries and other books may have the only accurate definition of a technical term, but they may be protected by copyright. Fair use (or fair dealing) is important here, and can apply as long as we don’t use too much from one source. Whenever we use a source in that way, it must be credited. The legal issues about this are very complex, and it is wise to find other ways of expressing yourself so that fair use will not need to be a factor.

Limiting and/or ordering definitions
Q: To avoid bias, should we sometimes limit or order the definitions so as to avoid giving the impression that rare or difficult uses of a word are more common than they are?

 * A: Yes, in theory, the oldest uses of a word should be listed first, but in the absence of historical data this is difficult to do. Furthermore, definitions are sometimes related, and should be close to each other in such circumstances. Determining which usage is most common or popular requires expressing a Point of View, and should be avoided. Links to Wikipedia or references to the Oxford English Dictionary are better ways to ensure that the definitions are complete.

Q: Is there a subset of the Wiktionary that would include only meanings that are known to be necessary for learning English as a second language, or for learning common English idioms?

 * A: There is provision for this idea. If you have the time, you could consider participating in the separate project at Simple:Main Page that aims to do just that! This kind of simplification is not a simple undertaking, and it has not attracted a lot of interest.

Copyright infringement
Q: I saw some copyrighted material in a certain article, submitted by user XYZ. What should I do?

 * A: In a publication like ours it is never easy to determine when a copyright infringement has taken place. Fair use (see below) is not an infringement. If you suspect that an article contains copyrighted material, use the following steps:
 * Don’t panic, and do your homework.
 * On the talk page for the article show why you think it is a copyright violation. In particular show exactly where you think the text in question was originally published.
 * As a matter of courtesy, if the material was placed by a registered user, politely let them know about this on their talk page.
 * Add to the article and make a note at WT:RFC. There is no need to immediately remove the suspected material.

Q: What is copyright?

 * A: Copyright is a person’s exclusive economic right to use and exploit their own creative and artistic productions. Its duration depends primarily on the laws of the country in which that person lives. It may be accompanied by moral rights such as the right to be properly credited for one’s works. A work whose copyright has expired is said to be in the public domain.

Q: What is fair use?

 * A: In simple terms, “fair use” (also known as “fair dealing” or “fair practice”) is the allowable quotation of the copyrighted works of others. The concept is not relevant to works that are already in the public domain. Any such quotation must be properly credited. Whether any particular quotation constitutes fair use can often be a very difficult matter to resolve. In most cases, quoting a single definition or a brief illustrative passage from any author’s work will fall within the definition of fair use.

Namespaces
Q: Occasionally in a discussion I see a reference to a “namespace”. What is that?

 * A: A namespace is a group of pages designed to fulfill a special purpose. Namespaces are denoted by a prefix followed by a colon, as Talk:color. The one exception to that is the “article” namespace, which contains the substantive articles for the Wiktionary; it has no prefix. See Help:Namespace for more information. Articles in a namespace are also sorted and searched separately from those in other namespaces. Articles in different namespaces may have identical names after the prefix.

Q: Where can I see a list of active namespaces?

 * A: See Namespace or Special:Allpages. Currently, they are “(articles)”, “Talk”, “User”, “User talk”, “Wiktionary”, “Wiktionary talk”, “Image”, “Image talk”, “MediaWiki”, “MediaWiki talk”, “Template”, “Template talk”, “Help”, “Help talk”, “Category”, “Category talk”, “Appendix”, “Appendix talk”, “Thesaurus”, “Thesaurus talk”, “Concordance”, “Concordance talk”, “Rhymes”, “Rhymes talk”, “Transwiki”, “Transwiki talk”, “Citations”, “Citations talk”, “Module”, “Module talk”.

Q: Is it possible to restrict a search to a given namespace?

 * A: Yes, Special:Allpages allows you to search individual namespaces.

Wiktionary in your language
Q: What should I do if I want to start a Wiktionary in my own language?

 * A: You should go to the requests for new languages page on Meta.
 * Note that for words in your language, you can create its entry in English Wiktionary. English Wiktionary aims to have entries for all words in all languages. The entry title should be in the language's script and the definitions and explanations should be in English.

Referencing Wiktionaries from Other Wikipedias
Q: Are dog and Konduto suitable references from other Wikipedias to Wiktionaries?

 * A: From a Wikipedia, dog or the shorter dog should link to the Wiktionary in the same language.

 * From Wiktionary, a link beginning with the word Wiktionary is treated as a link to the page in the Wiktionary namespace with the title dog . Upper or lower case of the first letter of the article title may give different results in this Wiktionary (see here for the status of this on other Wiktionaries). In the same way, here the link Dog will link to wikipedia.

What is a template?
Q: What is a Wiktionary template?

 * A: The word template in Wiktionary jargon means an entry in the Template: namespace which substitutes the content of the template whenever it is addressed in an article.

Q: How does it work?

 * A: Someone devises a template such as Template:wikipedia. Then, others use it by adding the text into their articles. When anyone displays that article, the text from Template:wikipedia is included in that page. In this example the template produces a box that includes a link to the article with the same name in Wikipedia.

Q: Where can I find a list of these templates?

 * A: See Templates.

Examples
Q: Should I add examples to each definition?

 * A: Examples are good, but quotations are much better. A well-chosen quotation can do everything that an example can, and additionally show evidence
 * of the age of a word,
 * that the meaning given reflects actual use, and
 * that the word isn’t just made up for Wiktionary.

Log in
Q: If I have an account with Wikipedia, do I still have to create a new account with Wiktionary?

 * A: No, because of the Single log-in, you can keep the same username throughout all Wikimedia projects. See meta:Help:Unified login

Wikifying
Q: What is wikifying/wikification?

 * A: Putting two square brackets before and after a term will auto-generate a hypertext markup language link to that word’s page, here on Wiktionary. Thus, entering link will give link.

Q: Why don’t we wikify every word? That would be so cool!

 * A: We don’t for several reasons:
 * Logical continuity. The wikilinks are meant to help clarify aspects of a meaning; it’s good to have the important words stand out.
 * Server performance. The computers must check every word that’s linked like that. It’s no big deal on a short article, but it really slows down the downloading of longer articles.
 * If you really, really want something like this, you should add Wiktionary to the list of search engines in your browser. This way you will be able to select a word, right-click it and look it up on Wiktionary. Also, this will work on any website—not just Wiktionary!

Q: Fine then. Hey, look—a red link! Should I dewikify it?

 * A: Maybe, but usually, no! Red links let you know where there is work yet to be done. They also help new users understand that they can help out here too.

Q: Any other guidelines on what to wikify?

 * A: The following are but a few.
 * On the inflection line, (the line following the part-of-speech header) you should wikify all component words of idioms and phrases.
 * You should wikify all translated words.
 * You should wikify the expansion of abbreviations. Usually the main article should go with the short form’s expansion entry, not the abbreviation itself.
 * All foreign language words in the etymology section should be wikified.
 * All foreign languages in the etymology section should be wikified.
 * All inflections of a word should be wikified (plurals, comparatives, superlatives, third person, participles and past tenses.)
 * None of the words in example sentences or quotations should be wikified. The headword of the entry should be bolded, within example sentences and quotations.

Downloading Wiktionary
Q: Is it possible to download Wiktionary?

 * A: Yes. https://dumps.wikimedia.org/enwiktionary/ should have the latest copy of the main namespace. The cleanest navigation page is https://dumps.wikimedia.org/. Just download a *-articles.xml.bz2 file and some software to read it (for *nix, for Windows).

Q: The XML dumps are very hard to use. Is the data available in a more structured and machine readable format?

 * A: Yes, you can use the JSON dumps created by the Wiktextract project, downloadable from here. These are much easier to process if you are an end user.

Q: Can I use data from Wiktionary in my program?

 * A: As long as you meet the conditions of the GNU Free Documentation License or Creative Commons Attribution/Share-Alike License, certainly.

How do I batch upload?
Q: Hi, I have a bunch of words in language that I can upload, already containing the word, grammatical tags and basic English translation. However, how would I do a batch upload, since I don’t have the kind of time to enter each one separately?

 * A: The robot code in question is from the Using the Python Wikipediabot’s.

 * Example: dict.txt

Mangaung

Proper noun

 * 1) Bloemfontein

kgòtsò

Noun

 * 1) peace

 * Remember to learn the Wiktionary format of entries before starting. It will correctly run “throttled” by default. Start with ten entries. When you get ten to load correctly, try running one hundred then stop and check the results; make sure you haven’t been blocked for flooding and none of your entries have been edited already. If any have been edited, you don’t have the format correct and need to fix the problem before testing again.

 * Request bot status in the Beer parlour if you get complaints. If entries are not marked minor by default, go to Special:Preferences, [Editing] and check off “Mark all edits minor by default”.

Q: What if someone keeps posting messages on my talk page, saying I’m uploading them wrong?

 * A: Stop what you are doing. Ask for help on Wiktionary’s information desk.

How do I link to Wikipedia?
In general, we should have terms defined locally here. But in a definition, if you need to refer to the corresponding Wikipedia entry there are three common methods:
 * When referencing Wikipedia outside of a definition, you can simply use the inter-project prefix, e.g.   = WP:FAQ, or the template . Other useful interproject links to know are   for linking to Wikisource documents used for quotations, and of course you may use   to link to Wiktionary from other sister projects. Note that interproject links do not work in redirects.
 * When Wikipedia has one or more articles about a word or phrase, you can add in a “Further reading” section at the end of the entry, just before the categories:

Why do you block new editors so readily?
As said at the top of Help:Interacting with other users, “Actions that appear destructive are either a result of someone not caring, not understanding, or not concentrating. Those who don’t care should be blocked lest they cause damage, those who don’t understand should be educated, and accidental damage should be undone.” Allowing someone who doesn’t care about Wiktionary to edit it is a waste of everyone’s time, as is giving warnings to people who will not take them on board.

How and why was I prevented from publishing my changes to a page?
Wiktionary uses abuse filters (Special:AbuseFilter) to automatically identify certain edits as being probably vandalism, and prevent them from being made. Any text you try to add is saved in a log (Special:AbuseLog) which administrators can access, so if you believe your edit was not vandalism, you can request at the Information desk that an administrator look into it.

Why can’t I see words like “ads”, “Facebook” or “Twitter” in some entries?
Some ad-blockers censor these words. For instance, with an ad-blocker turned on, you may not be able to see the word “twitter” in the first definition for the word —the first definition will end with the word “to”. Or, you may not be able to see the content of the entry “ads” or “advert”. In most cases whitelisting “wiktionary.org” or temporarily disabling any ad-blockers you use will fix this but following an issue in April 2019, Wiktionary was whitelisted on a system used by major ad blockers. If the issue persists, make a post in the Grease pit.

ca:Viccionari:PMF csb:Wikisłowôrz:FAQ da:Wiktionary:OSS de:Hilfe:Häufig gestellte Fragen es:Wikcionario:FAQ fa:ویکی‌واژه:پرسش‌های رایج fr:Wiktionnaire:FAQ he:ויקימילון:שאלות ותשובות it:Aiuto:FAQ ja:Wiktionary:FAQ ko:위키낱말사전:FAQ lb:Hëllef:Heefeg gestallte Froen ms:Wiktionary:FAQ nl:WikiWoordenboek:Veelgestelde vragen nn:Wiktionary:Spørsmål og svar pl:Wikisłownik:FAQ pt:Ajuda:FAQ ro:Wikţionar:Întrebări frecvente sr:Викиречник:НПП sv:Hjälp:FAQ uk:Вікісловник:FAQ vi:Wiktionary:Câu thường hỏi zh:Wiktionary:常见问题解答

title: Help:FAQ


text:
User:Kpjas

Kpjas on http://pl.wikipedia.org, http://www.wikipedia.org and http://de.wikipedia.org.

I must confess I am responsible for the notorious pies reference in dog. Be prepared for more additions like this to Wiktionary in future.

title: User:Kpjas


text:
Reconstruction:Proto-Germanic/frijaz

Etymology
From. The original meaning was probably something like “from one's own clan”, from which a meaning “being a free man, not a serf” developed.

Adjective

 * 1) free

title: Reconstruction:Proto-Germanic/frijaz


text:
aquila

Noun

 * 1) eagle

Etymology
From.

Noun

 * 1) eagle
 * 2)  eagle

Etymology
origin, but probably related to. Displaced Proto-Indo-European.

Noun

 * 1) eagle
 * 2) the standard (of an eagle) carried by a Roman legion
 * 3) the astronomical constellation Aquila

Derived terms

 * , the name

Descendants

 * Balkan Romance:
 * Italo-Romance:
 * Padanian:
 * Northern Gallo-Romance:
 * Southern Gallo-Romance:
 * Ibero-Romance:
 * Asturleonese:, , , , , , ,
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Padanian:
 * Northern Gallo-Romance:
 * Southern Gallo-Romance:
 * Ibero-Romance:
 * Asturleonese:, , , , , , ,
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Southern Gallo-Romance:
 * Ibero-Romance:
 * Asturleonese:, , , , , , ,
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Southern Gallo-Romance:
 * Ibero-Romance:
 * Asturleonese:, , , , , , ,
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Ibero-Romance:
 * Asturleonese:, , , , , , ,
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Insular Romance:
 * (eagle), (sea eagle)
 * Borrowings:
 * Borrowings:

title: aquila


text:
Wiktionary:Entry layout

 * “WT:MOS” redirects here. For the style guide, see Style guide.

This is a list of norms that govern how an entry should be formatted. This includes what sections are allowed and what contents are expected to be found in them. These rules reflect what editors think as best concerning the standard format of an entry.

Flexibility
While the information below may represent some kind of “standard” form, it is not a set of rigid rules. You may experiment with deviations, but other editors may find those deviations unacceptable, and revert those changes. They have just as much right to do that as you have to make them. Be ready to discuss those changes. If you want your way accepted, you have to make the case for that. Unless there is a good reason for deviating, the standard should be presumed correct. Refusing to discuss, or engaging in edit wars may also affect your credibility in other unrelated areas.

A very simple example
This is a simple entry for the word bed, and shows the most fundamental elements of an entry:
 * 1) a word’s language (as a level 2 heading),
 * 2) its part of speech or “type” (as a level 3 heading),
 * 3) the word itself (using the correct headword template),
 * 4) a definition (preceded by “#”, which causes automatic numbering),
 * 5) links in the definition for key words,
 * 6) “References” (as a level 3 heading), and
 * 7) a verifiable place where you found the word.

This example can be copied and used to start an entry or section of an entry.

Noun

 * 1) A piece of furniture to sleep on.

Variations for languages other than English
Entries for terms in other languages should follow the standard format as closely as possible regardless of the language of the word. However, a translation into English should normally be given instead of a definition, including a gloss to indicate which meaning of the English translation is intended. Also, the translations section should be omitted.

For languages written in other scripts (Japanese, Gothic, etc.), we have romanization systems in place. It is required that each romanization entry contain at least one definition line starting with “#” in the wikitext.

Some languages do have characteristics that require variation from the standard format. For links to these variations see Language considerations.

List of headings
There are additional headings which you should include if possible, but if you don’t have the necessary expertise, resources or time, you have no obligation to add them, with the possible exception of “References”. The list below is not an exclusive list; other headings may be essential in some circumstances. An order for these headings is recommended, but variations in that order are also allowable.

A typical entry that uses many of these additional headings could be formatted thus:

Pronunciation

 * Phonetic transcriptions
 * Audio files in any relevant dialects
 * Rhymes
 * Homophones
 * Hyphenation

Noun
Headword line etc.
 * 1) Meaning 1
 * 2) * Quotations
 * 3) Meaning 2
 * 4) * Quotations

Verb
Headword line etc.
 * 1) Meaning 1
 * 2) * Quotations

Noun
Headword line
 * 1) Meaning 1 in English
 * 2) * Quotation in Finnish
 * 3) ** Quotation translated into English
 * 4) Meaning 2 in English
 * 5) * Quotation in Finnish
 * 6) ** Quotation translated into English

Related terms
A key principle in ordering the headings and indentation levels is nesting. The order shown above accomplishes this most of the time. A heading placed at one level includes everything that follows until an equivalent level is encountered. If a word can be a noun and a verb, everything that derives from its being the first chosen part of speech should be put before the second one is started. Nesting is a key principle of Wiktionary's entry layout norms, but it is difficult to describe with only a few words. If you have problems with it, look at existing entries or ask a more experienced editor for help.

Headings before the definitions
In general, headings in this group do not depend on the meaning of the word. They give an environment that leads up to the word and its relation to other words, and allow us to distinguish it from others that may be similar in some respects. Order of headings:

 * Alternative forms
 * Description
 * Glyph origin
 * Etymology
 * Pronunciation (or Production for sign language entries)

Headings after the definitions
These headings generally derive from knowing the meaning of the word. Order of headings:

 * Usage notes
 * Reconstruction notes
 * Inflection, Declension or Conjugation
 * Mutation
 * Quotations (when not given under a particular sense)
 * Alternative forms
 * Alternative reconstructions
 * Synonyms
 * Antonyms
 * Hypernyms
 * Hyponyms
 * Meronyms
 * Holonyms
 * Troponyms
 * Coordinate terms
 * Derived terms
 * Related terms
 * Collocations
 * Descendants
 * Translations
 * Trivia
 * See also
 * References
 * Further reading
 * Anagrams

Entry name
The name of the entry is the term, phrase, symbol, morpheme or other lexical unit being defined.

For languages with two cases of script, the entry name usually begins with a lowercase letter. For example, use for the English noun and verb, not. Words which begin with a capital letter in running text are exceptions. Typical examples include proper nouns, German nouns , and many abbreviations. If someone tries to access the entry with incorrect capitalization, the software will try to redirect to the correct page automatically.

For prefixes, suffixes and other morphemes in most languages, place the character “-” where it links with other words:, , , etc.

Some page titles can’t be created because of restrictions in the software, usually because they contain certain symbols such as # or |, or are too long. The full list of those entries is at Appendix:Unsupported titles. They are named using the descriptive format “Unsupported titles/Number sign”, while using JavaScript to show the correct title like a normal entry.

For names of matched-pair entries such as and * *, see.

For names of sign language entries, see.

Before the first language section
When multiple capitalizations, punctuation, diacritics, ligatures, scripts and combinations with numbers and other symbols exist, such as (as in “frying pan”),  (the Greek god),  (meaning “all-”) and  (Japanese for “bread”), use the template  at the top of the page to cross-link between them:. When there are too many variations, place them in a separate appendix page, in this case Appendix:Variations of "pan".

Language

 * Each entry has one or more L2 (level-two) language sections. For example, the entry has different meanings in English and Spanish, both on the same page.
 * For languages that have multiple names, a single name is chosen that should be used throughout Wiktionary. Typically, this is an English name for the language. See Languages for more information.
 * Priority is given to Translingual: this heading includes terms that remain the same in all languages. This includes taxonomic names, symbols for the chemical elements, and abbreviations for international units of measurement; for example, , and . English comes next, because this is the English Wiktionary. After that come other languages in alphabetical order.
 * Language sections are no longer separated from each other by a horizontal line.

Part of speech
The part of speech (POS) is a descriptor like “Noun” or “Adjective”; they are different types of terms, phrases, symbols, morphemes and other lexical units on Wiktionary. Each entry has one or more POS sections. In each, there is a headword line, followed by the definitions themselves.

Allowed POS headers:

 * Parts of speech: Adjective, Adverb, Ambiposition, Article, Circumposition, Classifier, Conjunction, Contraction, Counter, Determiner, Ideophone, Interjection, Noun, Numeral, Participle, Particle, Postposition, Preposition, Pronoun, Proper noun, Verb
 * Morphemes: Circumfix, Combining form, Infix, Interfix, Prefix, Root, Suffix
 * Symbols and characters: Diacritical mark, Letter, Ligature, Number, Punctuation mark, Syllable, Symbol
 * Phrases: Phrase, Proverb, Prepositional phrase
 * Han characters and language-specific varieties: Han character, Hanzi, Kanji, Hanja
 * Romanization
 * Logogram
 * Determinative

Other headers can be proposed as new additions to the list. The use of nonstandard POS headers may cause an entry to be categorized in a cleanup category for further inspection.

Some POS headers are explicitly disallowed:

 * Abbreviation, Acronym, Initialism
 * “(POS) form”: Verb form, Noun form, etc.
 * “(POS) phrase”: Noun phrase, Verb phrase, etc. (with the exception of Prepositional phrase)
 * “(attribute) (POS)”: Transitive verb, Personal pronoun, etc. (with the exception of Proper noun)
 * “(POS) (number)”: Noun 1, Noun 2, etc.
 * Cardinal number, Ordinal number, Cardinal numeral, Ordinal numeral (note that ordinal numbers like are classified as adjectives but put in Category:English ordinal numbers by a template and fractions like  are nouns, and are added to Category:English fractional numbers by a template)
 * Clitic, Gerund, Idiom

Headword line
The headword line is the line directly below the part of speech header, in which the word is repeated, along with a romanization if applicable. You can use either the generic template or language-specific templates, such as  for English nouns. In some languages, additional information such as genders and inflected forms are found in the headword line.

 * For an overview of templates used, see.
 * For examples in English entries, see.

Definitions
The definitions are in the POS section, below the headword line. The definitions are organized as a numbered list. The numbers are generated by adding the number sign (#) at the start of each definition in the wikitext. The key terms of a definition should be linked to the respective entries.

 * The vote “2006-12/form-of style” is relevant to this section, without specifying text to be amended in this document, so please see it for details.

 * The vote “2010-08/Italicizing use-with-mention” is relevant to this section, without specifying text to be amended in this document, so please see it for details.

For definitions concerning matched-pair entries and their components, see.

Abbreviations
For abbreviations, acronyms and initialisms (such as and ), the definitions usually use templates linking to the expanded forms of the abbreviation. For example, one of the senses in the entry may be a template that displays “Initialism of personal computer.” Do not capitalise words in the expanded form unless that is how the expanded form is usually written. (In the previous example, don’t write “Personal Computer”.) Where the expanded form is an entry that exists (or should exist) in Wiktionary, link to it. Otherwise, if an appropriate Wikipedia article exists, link to it. When the expanded form does not merit either a Wiktionary entry or a Wikipedia article, link it to its component words. You may expand the definition with a gloss if appropriate.

Context labels
A context label identifies a definition which only applies in a restricted context. Such labels indicate, for example, that the following definition occurs in a limited geographic region or temporal period, or is used only by specialists in a particular field and not by the general population. Many context label templates also place an entry into a relevant category, but they must not be used merely for categorization (see category links, below). One or more labels may be placed before the definition:

Details in Context labels.

Example sentences

 * Main article: Example sentences

 Generally, every definition should be accompanied by one or more quotations illustrating that definition. Quotations are supplemented by example sentences, which are devised by Wiktionary editors in order to illustrate definitions. Example sentences should:
 * be grammatically complete sentences, beginning with a capital letter and ending with a period, question mark, or exclamation point.
 * be placed immediately after the applicable numbered definition, and before any quotations associated with that specific definition.
 * be italicized, with the defined term boldfaced.
 * be as brief as possible while still clarifying the sense of the term. (In rare cases, examples consisting of two brief sentences may work best.)
 * be indented using the “ ” command placed at the start of the line.
 * for languages in non-Latin scripts, a transcription is to be given in the line below, with an additional level of indentation: “ ”.
 * for languages other than English, a translation is to be given in the line below (i.e. below the sentence or below the transcription), with an additional level of indentation: “ ”, and with the translation of the defined term boldfaced.
 * not contain wikilinks (the words should be easy enough to understand without additional lookup).

The goal of the example sentences is the following, which is to be kept in mind when making one up:
 * To place the term in a context in which it is likely to appear, addressing level of formality, dialect, etc.
 * To provide notable collocations, particularly those that are not idiomatic.
 * To select scenarios in which the meaning of the example itself is clear.
 * To illustrate the meaning of the term to the extent that a definition is obtuse.
 * To exemplify varying grammatical frames that are well understood, especially those that may not be obvious, for instance relying on collocation with a preposition.

Alternative forms

 * See also Forms and spellings

Some variations of the same word kept in multiple pages include:

 * regional variations:, ; ,
 * historical variations:, ; ,
 * hyphenization/compounds:, ,
 * style variation: ,
 * uncertain capitalization: ,
 * different scripts:, (Serbo-Croatian for )

Description
The “Description” section is placed in entries for symbols, containing a visual description of the current symbol.

Section contents:
 * 1) The visual description should be as short as possible. Just using the name from the Unicode codepoint should usually be enough for the character description.
 * 2) * The entry ⌛ (Unicode name: ) may be described as “An hourglass.”
 * 3) When the Unicode codepoint name does not tell anything about the character shape, a short shape description may be added in one’s own words.
 * 4) * The entry 🔗 (Unicode name: ) may be described as “Two or three interlocked chain links.”
 * 5) Major rendering variations may be mentioned.
 * 6) * The entry 🏦 (Unicode name: ) may mention: “This is sometimes rendered as a bank emoji, or just the written word ‘bank’.”

Etymology

 * Main article: Etymology

The first header below the language heading is usually the level 3 “Etymology” header. The etymology is given right below the header without indentation. Etymology essentially shows where the word comes from. This may show the forms in other languages that underlie the word. For many modern words it may show who coined the word. If a word is derived from another in the same language by a regular rule, such as formation of an English adverb by adding “ly”, it is not necessary to repeat the complete details of the word’s origin on the page for the derived word.

Sometimes two words with different etymologies belong in the same entry because they are spelled the same (they are homographs). In such a case there will be more than one “Etymology” header, which we number. Hence for a word like lead the basic header skeleton looks like this:

Verb
Note that in the case of multiple etymologies, all subordinate headers need to have their levels increased by 1 in order to comply with the fundamental concept of showing dependence through nesting.

When multiple etymologies are present, we recommend that – whenever possible – they are ordered by descending commonness in the language, so that the most common etymology is at the top. This may differ from the order given in a native monolingual dictionary. We recognize that editors won't always have sufficient information or context to order etymologies that way, so we encourage the application of this guidance on a best-effort basis.

We also recommend that etymologies for lemmas precede etymologies for non-lemma forms. Languages on Wiktionary include non-lemma forms to varying degrees (if at all); however, it's a universal goal to increase the coverage of lemmas. In narrow cases, non-lemma etymologies can precede lemma etymologies, such as when a very common non-lemma form happens to have a rare or obsolete lemma homograph. Additionally, a lemma derived from a non-lemma form can follow that non-lemma form. Further deviations from this recommendation are allowable subject to editor consensus, reached on an entry's talk page, Beer parlour or another forum.

 * The vote “2007-10/style for mentioned terms” is relevant to this section, without specifying text to be amended in this document, so please see it for details.

Pronunciation

 * Main article: Pronunciation

The “Pronunciation” section includes the transcriptions, audio pronunciations, rhymes, hyphenations and homophones.

 * The region or accent (,, , et al.) is first if there is regional variation, followed by the name of the transcription system, then a colon, then the transcription. It is preferable to use an established transcription system, such as enPR or IPA (see Wiktionary:Pronunciation key for an outline of these two systems). Phonemic transcriptions are normally placed between diagonal strokes , and phonetic transcriptions between square brackets.
 * For audio pronunciations, upload the Ogg file to Commons and link to it using or a similar template.
 * Rhymes are listed in the “Rhymes” namespace. Do not list rhymes in the entry; instead, add a link to the respective rhymes page using . See the template for usage instructions.
 * Use the template to list hyphenation patterns.
 * Homophones are words in the same language that have the same sound. (Avoid using the ambiguous term, as it can mean either or .) Do not add: 1) words that are “nearly” homophones or rhymes (for example, for , do not add  or ); 2) words that are homophones if they are mispronounced in some way (e.g. for , do not add ); 3) words from other languages (which are unlikely to be true homophones anyway). Homophones are listed in alphabetical order using the  template. If a word is a homophone in a particular dialect, it may be added provided the dialect is indicated (for example,  is a homophone of  in accents with flapping, and  is a homophone of  in some non-rhotic accents).

A typical pronunciation section may look like the following (simplified) example based on the word :

Example with multiple accents (see entry ):

Examples with homophones depending on the dialect (see entries and, respectively):

Usage notes

 * These notes should not take the place of context labels when those are adequate for the job.
 * Describe how a term is used, rather than trying to dictate how it should be used from your point of view.
 * Curb the tendency to be long-winded in this section; brief explicit notes tend to be more effective.
 * When mentioning entries in running text, use the template, which italicizes entries written in Latin script.
 * Be prepared to document these notes with references.

Quotations

 * Main article: Quotations

Quotations are generally placed under the definition which they illustrate. If there is more than one being provided, or where this is not possible (e.g., a very early usage that does not clearly relate to a specific sense of the word), a separate section should be used. Quotations here are formatted normally but without definition numbers.

 * 1561, Flat Footed (translator), Platypus (author), Odes, chapter 3, line 12:
 * The hrunk it hrunketh every day.

Synonyms
This is a list of words that have similar meanings as the word being defined. They are often very inexact.

Where several definitions of the headword exist, synonyms can be given in a separate list for each meaning:

 * 1) Summarise the definition for which synonyms are being given with.
 * 2) List the synonyms for this definition, in alphabetical order and separated by commas, wikifying each synonym using.
 * 3) Use one line for each definition, beginning each line with a bullet.

The synonyms section for might look like this: *, ,  *  , ,

To avoid identical lengthy lists of synonyms in many entries a single reference can be made in each to a common Thesaurus page:

* See also Thesaurus:apex

An alternative to listing synonyms in a separate section is their placement immediately under the corresponding definition lines with :

#: #:
 * 1) The point, in an orbit about the Earth, that is furthest from the Earth.
 * 1) The highest point.

The choice between the two formats is subject to editorial discretion.

Further semantic relations

 * Main article: Semantic relations

The following headers are available to define sections containing semantically related words other than synonyms: Antonyms, Hypernyms, Hyponyms, Meronyms, Holonyms, Troponyms, Coordinate terms, See also.

Each of these sections is formatted exactly like the Synonyms section (see above).

All links in these sections use the template rather than plain wikilinks.

Derived terms
List terms in the same language that are morphological derivatives. For example, the noun driver is derived, by addition of the suffix -er, from the verb to drive. If it is not known from which part of speech a certain derivative was formed it is necessary to have a “Derived terms” header on the same level as the part of speech headings.

All links in this section use the template rather than plain wikilinks.

Related terms
List words in the same language that have strong etymological connections but aren’t derived terms. Each such term should be wikified. For example, datum and data should point to each other in this section since the latter is the plural of the former, and the plural form is not obtained by morphological derivation but was taken directly from Latin (where it is a morphological derivation). Another example is the pair of nouns pendant and pennant. These should cross-reference each other as they have very similar (arguably identical) etymologies in some subsenses.

Collocations

 * Main article: Collocations

Collocations are combinations of words that occur with much higher frequency than would be expected by chance.

Collocations may either be added under the corresponding sense using coi or co (after all nyms but before all examples), or under a dedicated  header, as described in Collocations.

Descendants
List terms in other languages that have borrowed or inherited the word. The etymology of these terms should then link back to the page.

Inherited terms should be listed first, ordered according to any layout specified on the relevant language considerations page (so far as one is specified), and otherwise alphabetically by language name or family at each indentation level. These are then followed by all other descendants (e.g. borrowed terms), alphabetically by language name at each indentation level. For languages with multi-word names, their place in the order is determined by the first letter of the first name component – for instance, Norwegian comes before Old English, which comes before Portuguese.

Translations

 * Main article: Translations

 * ONLY add translations that you are CERTAIN of. If you aren’t familiar with a language, or aren’t sure of a particular translation, it is far better not to add it than to risk adding an incorrect translation.
 * NEVER use automatic translation software to generate translations from English into a language you don’t speak. Automatic translations into English are likewise problematic. Translation software rarely gives accurate results.
 * DO NOT COPY from translating dictionaries (bilingual or multilingual) as this may constitute copyright violation. This applies to dictionaries both in print form and online. Dictionaries that are out of copyright may be used.

 * Translations should be given in English entries, and also in Translingual entries for taxonomic names. Entries for languages other than English and Translingual should not have Translations sections. Any translation between two foreign languages is best handled on the Wiktionaries in those languages.

 * English inflected forms will not have translations. For example, will not, as it is the plural and third-person singular of . In such entries as have additional meanings, these additional meanings should have translations. For example, the noun  should have translations, but the present participle of  will not.

 * The translation section is separated into a number of divisions that are keyed to the various meanings of the English word. Each division is separated into a distinct collapsible navigation box by use of the translation section templates (see below for example.) The boxes are each headed by a summary of the translated meaning.

 * Within each box, the languages for which translations exist are listed by their English names in alphabetical order. The language name is preceded by a bullet (generated by * ) followed by a colon and the translations into that language. The collapsible navigation box is obtained by adding the template just before the first language and  at the line after the last translation.

 * Use the template for each translation. This will create a link to that word in this Wiktionary and a small link to the Wiktionary for that language.    References for the translation should be on that other page rather than in the translation list. If you think  is too complex, simply enclose the translation in square brackets.

 * Translations not in the Latin script should display a transliteration according to that language’s transliteration policy, unless the policy states otherwise.

 * Do not link the language name.
 * Correct:
 * Portuguese: cachorro
 * Incorrect:
 * Portuguese: cachorro

 * Provide the grammatical gender of the translations of nouns, if appropriate, giving parameters such as m, f, n and c for “masculine”, “feminine”, “neuter” and “common” respectively to.

 * Do not add the pronunciation of the translation or detailed grammatical information: such information should be provided on the page for the translation itself.

 * Ensure that multiple translations are given in full. For example, for the German for “ankle”, which is Knöchel or Fußknöchel, write:
 * German: Knöchel, Fußknöchel
 * rather than just combining the two as “(Fuß-) Knöchel” or similar, which is liable to be misunderstood.

 * Do not give literal (word-for-word) translations of idioms, unless the literal translation is what is actually used in the target language. Most idioms do not translate word for word. For example, the idiom “none of your beeswax” cannot be translated into German literally as “nicht dein Bienenwachs”, as this does not have the same meaning in German; an idiomatic translation is “nicht dein Bier” (which means, literally, “not your beer” in English).

 * Do not give translations back into English of idiomatic translations. For example, when translating “bell bottoms” into French as “pattes d’éléphant”, do not follow this with the literal translation back into English of “elephant’s feet”. While this sort of information is undoubtedly interesting, it belongs in the entry for the translation itself.

Here is an example (a shortened version of the entry for orange) illustrating some of the conventions:

Noun

 * 1) The fruit of the orange tree.
 * 2) The reddish-yellow colour of an orange.

Translations

 * French: orange
 * German: Apfelsine, Orange
 * Japanese: オレンジ
 * Russian: апельси́н
 * Serbo-Croatian:
 * Cyrillic: наранџа, поморанџа
 * Roman: narandža, pomorandža

 * German: Orange
 * Hebrew: כתום
 * Latvian: oranžs

... ...
 * When a translation in the target language is not a lemma form, use alt parameter to display the translation but use lemma-forms as the page name, e.g. the Russian translation of links to the Russian verb  but displays спя́щий, which is an equivalent of.
 * Russian:

 * When there is no single word equivalent in the target language, use with embedded wikilinks for the individual words. For example the Russian translation of :

... ...
 * Russian: сре́дства к существова́нию

Result:

 * Russian: сре́дства к существова́нию

Trivia
Other observations may be added, under the heading “Trivia”. Because of the unlimited range of possibilities, no formatting details can be provided.

Anagrams

 * Main article: Anagrams

Anagrams may be entered in alphabetical order under a level 3 header. Only list anagrams that are words in the same language. For post, the anagrams section would look like this:

You may include the alphagram which is not wikied unless it is itself a word. For post, the anagrams section would look like this:

Metadata
This is material which is edited in a regular edit box, but does not appear in the entry when it is read. In some cases where it appears depends on your user preferences, especially the skin that you have chosen.

Category links

 * Main article: Categorization

A Wiktionary category is a group of related entries which are listed on a category page. Sub-categories may also appear on that page. Categories and lists under various names may seem very similar, but the way they are built is very different; in most cases, but especially in open-ended lists, they complement each other.

To include an entry in a category, simply add a category tag to the entry thus:

The link will appear at the bottom of the page in some skins and at the top in others, regardless of where it is placed in the edit box. Category links are placed one per line at the end of the appropriate language section. Putting these tags in a consistent place makes them easier to find in a longer entry’s edit field. A category link appears red if its category page has not yet been described, but categorized entries will appear there. You should edit a new category page, usually to add a brief description of the category and adding one or more tags to place it in a higher-level category.

By convention, it is preferable to use the plural for most category names that are nouns. This will avoid having a category divided in two when some use the plural and some use the singular.

 * Some votes are relevant to this section, without specifying text to be amended in this document, so please see them for details:
 * Representative entries
 * Lexical categories
 * Add en: to English topical categories, part 2
 * Categories of names 2
 * Derivations categories
 * Chinese categories
 * Rename Category:US Category:American English

Images
Lemma entries, whether English or non-English, can contain relevant images. Constraints: Further constraints may apply on a case-by-case basis, as decided by editors.
 * An image of a person relating to the coinage or etymology should be excluded unless another rationale for inclusion applies. Thus, newspeak should not contain an image of George Orwell, and Pythagorean theorem should not contain an image of Pythagoras.

title: Wiktionary:Entry layout


text:
Wiktionary talk:Entry layout

 * Archives

 * 2002
 * 2003
 * 2004
 * 2005 plus Wiktionary:Beer parlour (WP:BP) discussions of that year relating to entry layout
 * 2006
 * 2007
 * 2008
 * 2009
 * 2010
 * 2011
 * 2012–2018

Indentation of examples
Current guidance is to use " " to indent examples. This abuses description list markup for a use (indentation) that it is not intended for, and also results in invalid HTML (description list definitions must be preceded by at least one term). It is additionally an accessibility error: see w:MOS:INDENTGAP. We should use something like w:Template:Block indent instead. Hairy Dude (talk) 14:04, 23 February 2019 (UTC)
 * I agree, but do you have an example of a working alternative? —Rua (mew) 14:12, 23 February 2019 (UTC)
 * Presumably the HTML problem could be addressed by wiki software. We like the definitions in a given PoS section to be numbered consecutively. Wouldn't the block indent template disrupt that? DCDuring (talk) 17:52, 23 February 2019 (UTC)
 * This would seem to be a WT:GP problem. DCDuring (talk) 17:57, 23 February 2019 (UTC)

proposed addition
Can we insert the little detail that Entry layout in their own different section are level four as per WT:QUOTE? Sobreira ►〓 (parlez) 10:26, 28 March 2019 (UTC)

update Synonyms
After the crushing victory in this vote, changes to this page need to be made to the List of headings section. --I learned some phrases (talk) 21:44, 19 April 2019 (UTC)

This page's introduction
Could someone with edit rights to the page (which is protected), correct the following error in the page's introduction?: "what editors think as best" should read "what editors think is best" (as > is), I think. Or it could just say, "what editors consider best". --Rogerhc (talk) 20:00, 20 April 2019 (UTC)

Numeral
It should be clarified "Numeral" is not for all numbers; ordinal numbers like first are classified as adjectives but put in Category:English ordinal numbers by a template. Fractions like seven eighths are nouns, and are added to Category:English fractional numbers by a template. -- Beland (talk) 00:31, 2 May 2019 (UTC)
 * Where would this text go? There is only one brief mention of "numeral" as a header. —Justin ( koavf ) ❤T☮C☺M☯ 22:57, 30 December 2019 (UTC)
 * I was just going to add it to the end of the "Part of speech" section. -- Beland (talk) 23:51, 30 December 2019 (UTC)
 * That makes sense. Since this section is very light on text and explanatory notes, I want to be conservative about adding anything that may seem extraneous. Can you show me a discussion on modifying this text? —Justin ( koavf ) ❤T☮C☺M☯ 00:40, 31 December 2019 (UTC)
 * Well, when I was doing some work on numbers I was confused about this until the discussion at Tea room/2019/April. -- Beland (talk) 02:37, 31 December 2019 (UTC)
 * It's in there now; thanks, Koavf! -- Beland (talk) 02:18, 1 February 2020 (UTC)

Hypernyms - Hyponyms - Meronyms - Holonyms - Troponyms
While I have an idea what hypernyms and hyponyms denote, I am not sure many people ordinarily know what Meronyms, Holonyms and Troponyms are.

Shouldn't these terms at least be linked to their respective dictionary entries?

This would make it a lot more convenient to find out about the meaning of these headers.

And isn't there any explanation of the recommended usage in the help pages which could be mentioned and linked to from here?

I tried to link these terms to their dictionary entries and add an explanation but the page is locked.

This talk page seems not to receive much traffic lately. In case the page itself has also not been maintained for several month it should maybe be unlocked so other people can help improving it?

best regards, KaiKemmann (talk) 21:57, 19 June 2019 (UTC)

PS: I would find it useful to mention other terms which are similar in spelling in an entry. I. e. it could be noted that complementary is very similar to complimentary. Is there a standard procedure to do this and should this maybe be explained on this page?
 * The main documentation is WT:Semantic relations (linked from WT:EL). The templates could link to the glossary, like so: ": foo, bar, baz". The template help pages already provide examples, is that not sufficient? – Jberkel 22:11, 19 June 2019 (UTC)

 * Perfect, thank you. "WT:Semantic relations" is exactly what I was looking for.
 * I did not notice the referral because - when I came across the section "List of headings" - I thought I had already found what I was looking for. I did not expect to find details about the headings (including this link) further down in the section "Contents" and hence never got that far ..
 * So maybe adding "See below for details" in the "List of headings" (as well as an internal link) would be a good idea.
 * Also neither WT:Semantic relations nor WT:EL seem to refer to the respective glossary entries OR to the Wiktionary entries OR to the "template help pages" that you mention.
 * I feel that the help pages do not make full or even sufficient use of the powerful tool of linking terms to lemmas, articles, glossary entries or whatever is available and appropriate to help readers and users understand the context as well as the details ..
 * I am not sure I fully understand what you mean by saying: "The templates could link to the glossary, like so: ": foo, bar, baz". The template help pages already provide examples, is that not sufficient?"
 * thanks again for you help,
 * KaiKemmann (talk) 00:58, 24 June 2019 (UTC)
 * I was referring to the, etc. templates, which could generate a link to the glossary (just before the list of referents). About template help pages: on  there's an example at the top: , all meronyms of hand. – Jberkel 10:34, 24 June 2019 (UTC)
 * To address your question about complementary and complimentary: in that particular case, each lists the other as a homophone (in a "Pronunciation" section). More generally, though, I've seen this handled with an also tag at the top of the entry and (in other cases) with an item in a "See also" section. There are probably other ways I don't recall at the moment. Someone more familiar with the conventions here should comment on this. - dcljr (talk) 23:29, 25 June 2019 (UTC)
 * To address your question about complementary and complimentary: in that particular case, each lists the other as a homophone (in a "Pronunciation" section). More generally, though, I've seen this handled with an also tag at the top of the entry and (in other cases) with an item in a "See also" section. There are probably other ways I don't recall at the moment. Someone more familiar with the conventions here should comment on this. - dcljr (talk) 23:29, 25 June 2019 (UTC)

One year later and I am running into the very same problem again: Finding the definitions of the terms of "semantic relation".

The help page is still locked so I cannot change it myself.

I would therefore once more like to ask a person with editing privileges to link the terms in the "List of headings" to the respective entries in "WT:Semantic relations". This should be simple enough to do and would make life easier for anyone looking for the definitions. It is rather time consuming to dig around the help pages or read through the whole article in order to find the link to the semantic relations page.

I notice that the "New Entry Creator" helpfully contains a list of these terms of semantic relation. But again, many users will not be familiar with these terms and the "New Entry Creator" neither contains a link to "WT:Semantic relations" nor to the respective templates, which Jberkel mentioned (By the way: When should these templates be used instead of the respective headings and why are they not mentioned on this help page?).

I feel that editing Wiktionary is unecessarily complicated by not making full use of the possibilities of interwiki links to the existing help and documentation pages.

thanks, KaiKemmann (talk) 19:25, 24 July 2020 (UTC)

Abbreviations
Minor quibble: The "Abbreviations" section says, "For abbreviations, acronyms and initialisms (such as and )…". It would probably be better to say, "…(such as and )…", since SNAFU is an acronym and PC is an initialism (i.e., the examples are in the opposite order of the list of terms). Perhaps for completeness we should also give an example of an abbreviation that is neither an acronym nor an initialism (e.g., apt.)? - dcljr (talk) 23:12, 25 June 2019 (UTC)
 * PING… This is still an issue 3 months later, so here's some text you can just paste into the right place:
 * Please replace:
 * With:
 * In the "Abbreviations" section. - dcljr (talk) 23:20, 29 September 2019 (UTC)
 * So, this really doesn't bother anyone else (who can edit the page, enough to edit the page)? - dcljr (talk) 01:39, 31 December 2019 (UTC)

"lb"
Just wondering, does it stand for something? (I assume the "l" is for language.) Thanks in advance. --Philologia Sæculārēs (talk) 00:51, 8 October 2019 (UTC)
 * In case you didn't notice, the name of the template as shown in the "Context labels" section is a clickable link, which takes you to the template's documentation, which reveals that the full name of the template is label. So "lb" is an abbreviation of "label". (I didn't know, either. :) - dcljr (talk) 01:07, 8 October 2019 (UTC)
 * Thanks Dcljr! --Philologia Sæculārēs (talk) 06:58, 8 October 2019 (UTC)

Need to document ALL heading levels, including «See also» (and it needs further «Don't use» text)
I just made a mistake when changing ===See also=== in fall off the wagon to the more specific ===Related terms===. I should've changed it to a fourth-level heading: ====Related terms====. I made this mistake in part because WT:EL doesn't specify what level «See also» goes at; WT:EL doesn't say anything about it; it doesn't appear in WT:EL (for good reason, I guess, since it most entries shouldn't include it); and though its placement order is defined in WT:EL, that section gives no guidance on heading levels.

I think there should be a master list of all possible headings, giving both their order and levels (using the wiki markup «=»s is the most handy for this). It really isn't necessary to punt with «Nesting is a key principle to the organization of Wiktionary, but the concept suffers from being difficult to describe with verbal economy. If you have problems with this, examine existing entries, or ask questions of a more senior person.». A master heading list would be easy to construct, and very useful.

That, and/or each heading section (e.g. WT:EL) needs to specify its expected level, and ideally, WT:EL and WT:EL should also document the correct nesting, either via the «=» markup, or via indentation.

And one final note is that the documentation of WT:EL should be modified to say that not only should it not be used for external links, but it also should not be used to link to other entries when a more specific heading exists for that purpose, such as ====Antonyms==== or ====Related terms====. --Dan Harkless (talk) 22:01, 8 October 2019 (UTC)

Mutation header in unconventional location
I've noticed that currently on WT:EL, the mutation header is located between the inflection table and the derived terms, descendants, -nyms, etc. But usually on Celtic language entries it in practice usually goes where "See also" is. Should EL be amended to move "Mutation" between "See also" and "Further reading"? mellohi! (僕の乖離) 21:24, 19 January 2020 (UTC)
 * Given that it's normally a level 3 heading, it should appear after any headings that are specific to a single part of speech. "See also" and "Further reading" are both level 4 headings in the entries I create, and in particular I place "See also" below "Related terms". —Rua (mew) 21:26, 19 January 2020 (UTC)
 * I agree with Rua's first sentence above, but in my entries, "See also" and "Further reading" are usually level 3 headings, so I tend to put "Mutations" before them, as the first of the post-POS level 3 headings. —Mahāgaja · talk 07:13, 20 January 2020 (UTC)

Page formatting - It's hard to find the definition
I have rarely used Wiktionary. However, today I sought to look up barmy, and I found it difficult to find the definition amidst all the words on the page. I would expect helping users quickly locate definitions would be a primary goal of Wiktionary, so I'd suggest finding ways to format the text on the page in such a way as to make it easier to find the definition(s). Daask (talk) 13:46, 31 January 2020 (UTC)

Edit request: Correct level for part of speech headings
Many sections list part of speech headings as being level three headings, e.g.,, while Entry layout lists an example of a level four part of speech heading, i.e.,. Of note, as recently as 2017 a level three heading was generally promoted with the option for "a lower level for terms that have multiple etymologies or pronunciation". Can someone resolve this apparent discrepancy by re-adding the note or some other change? —The Editor's Apprentice (talk) 23:44, 27 April 2020 (UTC)

Edit request: hatnote link to WT:FORMS
I would like to suggest adding the following immediately below the 'Alternative forms' heading at WT:ALTER:
 * Main article: Forms and spellings

I found the information at Forms and spellings immensely helpful in answering several points of confusion I had about alternative forms. Unfortunately, it took me a long time to find the page, since it's not really discoverable except by a careful use of the search feature. Colin M (talk) 21:03, 15 June 2020 (UTC)

Section Example sentences
Update needed at Section 'Example sentences'. The Template:ux places automatically the transliteration and translation in different rows, so there is no need for writing  below the ux example. Thank you. ‑‑Sarri.greek ♫ | 08:58, 31 August 2020 (UTC)

Need example sentence "#:" in List of Headings
Hi all, in the List of Headings section I noticed the example sentence missing. I think it should be there (?).

Noun
Headword line
 * 1) Meaning 1
 * Example sentence
 * 1) * Quotations

Facts707 (talk) 08:57, 3 April 2021 (UTC)

Request Wikipedia link at section Part of speech
Would be handy to link to Wikipedia at the top of the Part of speech section. E.g. not everyone knows what a circumposition or ideophone is. I.e.

Cheers, Facts707 (talk) 04:18, 23 April 2021 (UTC)

copyedit suggestion
Nesting is a key principle to the organization of Wiktionary, but the concept suffers from being difficult to describe with verbal economy. If you have problems with this, examine existing entries, or ask questions of a more senior person.

=>

Nesting is a key principle of Wiktionary's entry layout norms, but it is difficult to describe with only a few words. If you have problems with it, look at existing entries or ask a more experienced editor for help. --Espoo (talk) 07:26, 13 November 2021 (UTC)
 * Agreed, ✅, it was unnecessarily wordy. PseudoSkull (talk) 07:48, 13 November 2021 (UTC)

Information density and page aesthetics
Does anyone else feel like some pages that present a lot of information are off-putting? For a (very small and not cherrypicked) example of such an entry, for which I can only blame myself, see fluffy bunny. I think the context labels, long definition lines, and (in this case) italics contribute. Sometimes I feel an impulse to add usage examples just to add more blank space and give the reader room to breathe, but I generally refrain from actually doing so (of course, usage examples have more substantial benefits too). 70.172.194.25 04:23, 18 February 2022 (UTC)

Heading level of "References" and "Further reading" doesn't make sense
The heading level of "References" and "Further reading" as described in the section "List of headings" doesn't make sense to me. Here is the section in question with added indentation:

==English== ===Alternative forms=== ===Etymology=== ===Pronunciation=== ===Noun=== ====Usage notes==== ...  ===References=== ===Further reading=== ===Verb=== ====Usage notes==== ...  ===References=== ===Further reading=== ===Anagrams=== ...

The headings "References" and "Further reading" both occur twice, once for the noun section and once for the verb section. The heading level of them is three, so they are on the same level as   and. But they are relating to the noun section and to verb section respectively, so I think they should be one level deeper, namely four.

If you want to have a "References" or "Further reading" section with only three  (because it relates to both the noun and the verb section), you should put it right before , and there should be only one such section. Tc14Hd (talk) 22:27, 23 February 2022 (UTC)

 * I came here to ask precisely the same thing. This is confounded by the fact that "References" and "Further reading" are listed in the Headings after the definitions section, which starts by saying These headings generally derive from knowing the meaning of the word, but then also includes "Anagrams", which clearly does not conform to that definition.

 * From reading the page, it seems clear to me that "References", "Further reading" are (generally) meant to appear only once per language, just like "Anagrams". This is evidenced by:
 * "References" being described explicitly as a level 3 heading in §A very simple example;
 * Both "References" and "Further reading" appearing as level 3 headings in the example page layout in §List of headings;
 * Both "References" and "Further reading" appearing right before "Anagrams" in §Headings after the definitions (though this one could be said to be circumstantial).

 * Assuming my reading above is correct, the changes needed in the page to remove the current ambiguity would then be relatively minor (simply removing the first two instances of the "References" and "Further reading" headings in the example page layout in §List of headings). However, it would be good to also resolve the ambiguity of listing "References", "Further reading" and "Anagrams" at the end of §Headings after the definitions, possibly by grouping them under a third list of headings — say, "Headings at the end of the language section", or something to that effect. Here's a diff showcasing what implementing these changes could look like; the rendered page would then look like this.

 * By the way, while researching this topic to make sure my understanding above didn't contradict existing conventions, I also made slight clarifications in References (diff) and Help:Footnotes (diff). --Waldyrious (talk) 10:18, 25 September 2022 (UTC)

 * I didn’t even realize the list of headings stated that. I’ve always placed the “References” and “Further reading” sections at the end of the entry just before “Anagrams”. — Sgconlaw (talk) 13:26, 25 September 2022 (UTC)

 * Yeah, the current situation indeed seems to be due to an overlook, rather than a disagreement over where to place these sections. In that light, would you be willing to make the change I propose above (or something along those lines), or do you feel this needs more discussion? --Waldyrious (talk) 13:48, 25 September 2022 (UTC)

 * as this is a policy page, if you want to be really safe you should start a vote at "Votes". But since this may be an oversight, I suggest you start a discussion in a more prominent place such as "Beer parlour", and if most people agree that it is not a policy alteration then you can go ahead and change it. — Sgconlaw (talk) 13:59, 25 September 2022 (UTC)

 * Makes sense. I will do that, thanks! --Waldyrious (talk) 15:08, 25 September 2022 (UTC)

Shortcuts to
List of headings=== ==

Showing WT:ORDER and WT:LOH as shortcuts would be useful. I find I'm often looking for the order of headings and others may benefit from the shortcuts too. Cheers, Facts707 (talk) 05:20, 21 May 2022 (UTC)

✅ This, that and the other (talk) 09:28, 16 January 2023 (UTC)

Further reading only for dictionaries and encyclopedias
See. --Dan Polansky (talk) 06:31, 17 September 2022 (UTC)

change the link from "romanization"
At "we have romanization systems", instead of romanization, romanization should be linked. Utonsal (talk) 21:36, 18 November 2022 (UTC)

Pronunciation position for Chinese characters
On the pages for Chinese characters, the pronunciation section is many many times longer than it is for most other languages, frequently taking up more than a third or even half the entry. It makes it difficult to find the definitions for the characters when scrolling the page, and it makes it impossible to see both the etymological entry for the character and its definitions on the same page. Is it possible to alter the standard position of the pronunciation section for Chinese character entries to move the definition closer to the top, and to have it nearer to the etymology section? Infocidal (talk) 10:23, 21 January 2023 (UTC)

AutoDooz whitespace changes
the bot AutoDooz recently added blanklines to a lot of the pages I've edited and created. I had not known there was a standard, since the main page here has the headings listed entirely without blanklines, but since I had never seen a page like that I assumed blanklines were optional. Should we edit the main page to show where whitespace should and should not be added? Thanks, — Soap — 17:10, 4 February 2023 (UTC)

 * WT:NORM has details for treatment of whitespace but states Editors other than bots can treat these norms as guidelines. I don't think editors should worry too much about details that can be fixed by bots. JeffDoozan (talk) 17:25, 4 February 2023 (UTC)

Alternative form notes
Hello, to whomever has the privilege to edit this page, may you please add a passage under the "Alternative forms" header to state that, as per Votes/pl-2016-09/Placement of "Alternative forms" 2 (weaker proposal), editors can choose either to place the "Alternative forms" header above the main content and before etymology, with a L3 header, or before any Synonyms sections, with whatever header the Synonyms section would have (so L4 if single etymology, L5 if multiple etymologies)? Kiril kovachev (talk) 12:39, 25 June 2023 (UTC)

 * @Mahagaja Kiril kovachev (talk) 12:40, 25 June 2023 (UTC)

I was misled by "Example sentences"
Just want to share my experience with this guide: I was initially confused when reading the "Example sentences" subsection because the words "Example sentences should: be grammatically complete sentences, beginning with a capital letter and ending with a period, question mark, or exclamation point" made an impression that any examples of word usage other than quotations and example sentences (such as collocations) are disallowed in the definition area.

That confusion was resolved only a few days later when I reached the section "Collocations" and read it closely: "Collocations may either be added under the corresponding sense using or (after all nyms but before all examples), or under a dedicated   header" I was on the brink of removing all collocations from the entries where I added them. So I suggest to add some words to "Example sentences" to make sure users understand that adding collocations under definitions is not discouraged. Gradilion (talk) 05:06, 3 July 2023 (UTC)

3 edit requests for the Translations section
Could someone please change "Translations should be given in English entries, and also in Translingual entries for taxonomic names." to "Translations should only be given in English entries, and in Translingual entries for taxonomic names."? I think the second phrasing makes it clearer that translations between non-English languages are not recommended, while preserving the existing meaning.

Additionally, I would appreciate if this sentence and the one from the next list item ("English inflected forms will not have translations.") were made bold, as they indicate content guidelines like the ones preceding them, rather than formatting instructions as is the case with the items after them. I understand that attention is being called to the first three because they can lead to more serious policy violations, but I think their use of ALL CAPS is sufficient to highlight them an extra level above mere bold.

Finally, please fix the typo introduced in edit 12655430 by making the following change: " In If such entries as have additional meanings, these additional meanings should have translations." (I would further suggest starting the sentence with "Hovewer," or "That said," to make the connection with the previous sentence more evident.)

Thanks in advance! Waldyrious (talk) 14:15, 1 August 2023 (UTC)

Cross-reference WT:FORMS
#Alternative forms should have  at the top, like #Example sentences. Nardog (talk) 13:23, 21 February 2024 (UTC)

title: Wiktionary talk:Entry layout