Jump to content

Wikipedia talk:Wikipedia is not a dictionary/Archive 15

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 10←Archive 13Archive 14Archive 15Archive 16Archive 17

Sometimes it *acts* like a bad dictionary (and bad history)

Sometimes it seems Wikipedia and Wicktionary by nature having a fixation on most popular or recent material leads them to into acting as a revisionist dictionary and confused history. The specification of the most common usage can come off as defining the English language and that also gets the story chronology conflated. For example, I've been bouncing at Teleological argument. Wikis give the most common usage of the phrase, but then constrain the article to be the definition and only possible meaning, and tend to redo history to suit. To some extent that is offset by other wiki articles being in there and some where higher catgeories have been put into place. For example:

  • Bad dictionary: It is only by the specification "(for the existance of God)" apparent that Teleological argument has the English language meaning an argument using teleology, a style of argument formation. The article itself presents it as implicitly and only meaning an argument for the existence of God, and worse it also seems to give the view that all arguments for God are based on teleology. If you click the second link [Existence of God]] or the box about Philosophy of Religion you'll be able to see the wider meanings, but we've still lost any ability to write about Teleological arguments alone, and it would seem better to be explicit with distinction in the article start that it is a sub-set 'argument based on teleology, most famously the argument for existence of God' and not 'is the argument for the existence of God' use of is.
  • Bad dictionary pt 2: I understand that it's hard to hold until later in the article the conclusions, but the effect of the second sentence in Teleological argument "The argument is central to creation science which has promulgated the term "intelligent design theory" as a "scientific" version of the argument from design since 1988." is bad presentation and bad format. It's still in the entry paragraph so this seems showing a conclusion as part of defining the article topic. Alternatively it's coming across that the rest of the article will be selections of data that follow and support this point, which does not really seem any better.
  • Bad history: I understand that it's harder to find and cite texts before 2000, but that second sentance is also confused chronology mixing 2000's cite from a hostile article, a 1990s label, and a 1960s label. That all that are external to the phrase the article is supposedly about, or that they are subset examples of the concept instead of definitional "is" the concept all seems to get lost.

Markbassett (talk) 17:01, 9 September 2013 (UTC)

Wikipedia is a one-stop solution

When someone says, "I'm looking to find something", they "google" it. When someone is looking to "know something", they "check wikipedia". They don't check Wiktionary. They don't necessarily go to dictionary.com. They check wikipedia.

What that tells me is that Wikipedia needs to be the one-stop place for all knowledge, not the least of which are word definitions. After all, today, I can open one of my old encyclopedias and look for word definitions too (which the added benefit of information about etymology, use and history of the word). Then why do we expect any less from Wikipedia?

Finally, in defense of a more specific case, my page for Ptochocracy is up for deletion. I have only found the word in dictionaries and not much in use. It's a rare word with a complex use and history, much of which is not available to me directly, but via few passages present in old Google Books. I do believe the word has a place in Wikipedia, specifically if we aim to be the most thorough encyclopedia and cover literally every single form of government that has, can or might exist. (Ptochocracy is a form of government that is run by the poor of the society, almost the opposite of Plutocracy.) — Preceding unsigned comment added by Nitinkhanna (talk • contribs) 19:50, 30 July 2014 (UTC)

If there is no encyclopedic information available about the concept of ptochocracy then there shouldn't be a wp article about it. Nor does the word seem notable enough for WP:WORDISSUBJECT. Why not have a WP:Soft redirect from Wikipedia to Wiktionary? DexDor (talk) 19:58, 30 July 2014 (UTC)

Duplicate articles should be linked to Wikipedia:CFORK

I am going to change the link on "Duplicate articles" from WP:MERGE, which is a help page, to WP:CFORK, which is the corresponding guideline. And I will link the word "merge" with WP:MERGE. Of course I don't think this should be a problem, but revert, alert me, etc. if there is. Thx.--Kiyoweap (talk) 05:24, 24 April 2015 (UTC)

Note that WP:NAD policy now links to the WP:CFORK guideline, and WP:MERGE {{infopage}}, both lower status than policy. And the rule under WP:POLICY#Content cautions "Avoid overlinking ... Links to other advice pages may inadvertently or intentionally defer authority to them"? Is this seen as a problem, I mean, hyping CFORK guideline as if it is policy? --Kiyoweap (talk) 07:53, 16 May 2015 (UTC)

What we don't want to do is give the impression that the policy is deriving a rule from the "authority" of a non-policy, rather than self-stating the policy, and referring to the guideline or other page as where to find more information/details. For essays, it's generally safest to "see also" them, not to link to them in situ. Guidelines, however, have general community consensus as codifications of best practices, or they would not have {{Guideline}} on them for long. The problem with essays is they can be one editor's nonsense opinion, or they can (as in the case of WP:AADD) have more buy-in than many guidelines, but simply not be written in guideline style, and no one but the most experienced members of the community can tell the difference. I regularly remove essay links from policy and guideline pages, move them to a ==See also== section, or do {{Hatnote|See also WP:Handling trivia (essay)}}, carefully noting they're essays. I don't think {{Main}} should ever point to an essay from a policy or guideline page, though it's okay for it to point to a guideline (e.g. MOS:NUM) if the material in question is not covered by any policy (e.g. style matters).  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  04:15, 6 August 2015 (UTC)

Please fix this

The top row of the table near the top of this project says:

Wikipedia: A person, or a people, a concept, a place, an event, a thing etc. that their title can denote. The article octopus is about the animal: its physiology, its use as food, its scientific classification, and so forth.

Wiktionary: the actual words or idioms in their title and all the things it can denote. The entry octopus is about the word "octopus": its part of speech, its pluralizations, its usage, its etymology, its translations into other languages, and so forth.

In this case, Wikipedia's octopus article is actually about both of the above. Any thoughts?? Georgia guy (talk) 16:23, 24 March 2015 (UTC)

Yes. This page is wrong. - Dank (push to talk) 18:52, 24 March 2015 (UTC)
Easily fixable. As we know many articles have section "etymology" which is basically a dicdef.Staszek Lem (talk) 19:32, 25 March 2015 (UTC)
Yes, I don't see what the problem was. Not only do many Wikipedia articles specifically discuss the term that the article is based on, Wikipedia has many articles about words or phrases; Wikipedia:Wikipedia is not a dictionary#When a word or phrase itself may be an encyclopedic subject addresses that. The key is that a Wikipedia article should not simply resemble a dictionary. Flyer22 (talk) 04:40, 26 March 2015 (UTC)
I'd say that with human-invented concepts (e.g. anything to do with culture, politics, etc) the etymology is often strongly bound up with their development and how people have understood them through the ages (and with controversies about what they truely mean) and as such is an imortant aspect of the subject. With natural things (e.g. octopuses) how we came to refer to them in English is less important to the subject, but can still reflect how people have related to them and so can still be relevent. As such, while I don't think all articles need to give the etymology, I don't think we should be too keen to strip them out, and some should definitely have them. .Iapetus (talk) 16:28, 22 July 2015 (UTC)
I've long thought this segment was wrong and misleading. It is trying to get at something. The intro material at MOS:GLOSSARY touches on this: There's a difference between encyclopedic and dictionarian treatment of words-as-words.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  04:17, 6 August 2015 (UTC)

Literal translations from other languages

Hi there. I'm currently moderating (and participating in) a discussion about literal translations from words and names in other languages - specifically using the {{nihongo}} template, but I imagine there are other cases as well. I have a question about this policy/guideline that I think might clarify things and help us come to a consensus over there, so any help would be appreciated.

Basically, the question is whether literal translations are helpful in the scope of an article, when the actual name used in the country of origin is different from the literal translation. As a contrived example, I pointed out what I thought would be an inappropriate inclusion of a literal: If the Japanese text for "Mega Drive" was officially translated as "Mega Drive", but literally translates to "Enormous Engine", I can see how the literal could be interesting to some, but would not ultimately be helpful to understanding the article. User:Ryulong very helpfully illustrated how that would look in an article lead:

The Sega Genesis, originally released in Japan as the Mega Drive (kanji, romaji, literally "Enormous Engine") ...

User:Despatche contends that many of the literal translations we have are either incorrect or made-up, and I partially agree with him in that they're difficult for the average Wikipedia reader to verify mainly because it requires special domain knowledge (in this case, enough understanding of Japanese to either directly translate the text or to know how to use a dictionary or translation service to do it - and I don't count Google Translate in that set of tools). But moreover, even if we can be sure that the literals are always correct, are they necessarily meaningful? In my example above, nobody anywhere in any of our sources would refer to the game console as the "Enormous Engine" - it would be entirely unreferenced, and thus might fall afoul of WP:OR, WP:TRIVIA, and/or WP:NOT#DICT (which is what I'm here to ask about).

Basically, I'm wondering if there is (or should be) a provision in this guideline about handling translations of foreign words - the goal of an article like Sega Genesis is not to define the Japanese term, but to describe the subject. On the other hand, Ryulong pointed out that it does no particular harm (and in fact could be interesting information), which I can't really argue with other than asking if it's necessary information for understanding the subject.

Thanks - looking forward to your input. — KieferSkunk (talk) — 03:39, 2 October 2013 (UTC)

I know I'm not going to be much help, but I'd like to point out that this is precisely my problem. These translations are almost always misinformation by default, border on meaningless trivia, and are bloat to the lede. If we really want to have these translations, I would suggest an "Etymology" section explaining what each title may mean, like with so many other articles. But even then, it's really hard to source half of these translations, while it's really easy to source the actual title (though not necessarily the romaji that goes with it, but that's for another time).
I will say what I always will say: problems like these only exist because of an obsession with "localizing" everything, and we need to fight this obsession wherever it appears. We are an English-language encyclopedia about potentially everything, and nothing more or less; there is no reason why we should localize things that cannot be, such as names and titles. If we prioritize original titles and provide redirects for everything else, we will have a good balance of accuracy and accessibility. Only one point, but just because the United States has so many people for a single country does not mean we should use them as a metric of what name we should be using to refer to things that have very little to do with the country or any of those people.
Wikipedia influences everyone else far more than everyone else influences Wikipedia; that's fact. Titles and even words are made of three separate parts--the physical object versus the sounds assigned to it, and the meaning behind one or the other--that's also fact. I cannot wait for the day that people realize these two things, because it's going to make my job a lot easier, everyone a little more correct, and thus me a lot happier.
(I've got to start using "Enormous Engine" for something, it's too good :V) Despatche (talk) 04:32, 2 October 2013 (UTC)
A literal translation is not "misinformation". It is never being presented as anything other than a literal translation. Just because there are a handful of trademarked titles that differ from the literal translation does not mean it's "fake" or "wrong" or "being localized". It's just not official. It is providing misinformation by omitting the literal reading, which can be easily acquired by anyone by reading any translingual dictionary (or using Google or Babelfish or whatever) to confirm this information. The level of verification you are requiring for this information is bordering on obsessive. It's mindsets like this that kept the video games Wikiproject from even including the romanization of the Japanese text in the first place (it's not sourced so it shouldn't be included, it is not relevant to the article to include the way the characters are phonetically read, etc.).
And really, if this is all because one company decided to trademark several names in English (a language that their nation does not primarily speak) that do not match the very literal reading of the name used in their home nation then this is getting way out of hand. "ポケモン" is "Pokémon". "ポケットモンスター" is "Pocket Monster(s)". Just because a couple of video games switched those around for their domestic trademarks does not mean the literal reading should be completely ignored.—Ryulong (琉竜) 07:56, 2 October 2013 (UTC)
On the topic of things that can be "easily verified": Yes, someone could use a translation dictionary to look up the literal meaning of a phrase in Japanese, but that doesn't mean we're obligated to provide it. My point is not whether we're providing false information with the translation, but rather whether that translation provides any actual benefit to the reader. The point of the lede is not to push as much information as possible about the subject to the reader, but to introduce it to the reader so they can see at a glance what the essential details are. Even if "Enormous Engine" were a perfectly good literal, I would argue that since it's not essential (or even important) to the topic, it wouldn't belong in the lede. Moreover, if it has no meaning in the context of the article at all, I don't think there's any point in putting it there, correct as it may be. — KieferSkunk (talk) — 20:20, 2 October 2013 (UTC)
Here's another facet to "information overload": Last I checked, they were still arguing about this, but I was involved in a discussion a while back over at Pac-Man about the part that describes why Midway changed the game's name from the original Puck Man to Pac-Man when bringing it to the US: Because they realized the P could be easily changed to an F to form the word "Fuck". We went through several revisions, and at the time, the one we accepted was to simply state that the original title "could be easily vandalized", linking to the vandalism article in case people wanted to read up on that topic in general. We'd decided that the exact change (P to F) and the resulting word were unnecessary - the point of that section was that vandalism could be a problem, not exactly how it would happen or what offensive word would result. That also addressed concerns that we were censoring the topic ("OMG, you're using the word 'fuck'! You might offend somebody!") by bypassing the issue of censorship entirely. The root of the question, then, was "What is actually necessary here?", and it's a good question to ask in many other cases (I posit that this discussion is one of them). — KieferSkunk (talk) — 20:20, 2 October 2013 (UTC)
Also, I just wanted to address one other bit from your reply, Ryu: I've seen many, many cases of the {{nihongo}} template providing literal translations that I didn't think made any sense or added any usefulness to the article, both in and out of the VGProject, so it's not just about the usage in Pokemon. I see this as having a much broader scope, which is why I chose to bring it to a general policy/guideline page. — KieferSkunk (talk) — 20:25, 2 October 2013 (UTC)
You're still using the same arguments that people used for even including the Japanese language text on video game articles in the first place. This is the English Wikipedia, we do not need to include non-English names. This is an article on a video game, it is not necessary to include the transliterated reading of the Japanese text. And so on. It's two or more unobtrusive words added to the first line of the page. It's not harming anything and provides more real world context to the subject.—Ryulong (琉竜) 20:36, 2 October 2013 (UTC)
Fair enough, and I want to be clear that I'm not just being a deletionist. I just want to be sure that we know where the line should be drawn on "too much information" - by the opposite argument, we could say that once we tell the reader what the literal is, we might also interpret it or explain it somehow to show the full context by which it appears. Personally, I *do* think showing the actual Japanese text for a Japanese title is appropriate. POSSIBLY also showing the romanization so people know how to pronounce the Japanese text. I'm just not sure I agree on the "does no harm" for also doing the translation. But again, it's not purely my call - I would like to get some input from other users as well. — KieferSkunk (talk) — 01:42, 3 October 2013 (UTC)
WP:UE already states that if the original language text is provided and it's not in a Latin alphabet then you have to include the romanization so there's no budging on that fact.—Ryulong (琉竜) 03:10, 3 October 2013 (UTC)
As Masem already pointed out, that only applies if there is no English name. The examples you've pointed out (Final Fantasy, Pokemon Platinum, etc.) all have English names. Japanese-only titles are where that rule strictly applies. Here's the quote from that page that I think you're misinterpreting:


— KieferSkunk (talk) — 18:19, 3 October 2013 (UTC)
I'm talking of the romanization issue. Beijing includes pinyin for Mandarin Chinese. Athens includes romanizations of modern and ancient Greek. There's nothing that should make Japanese unique amongst these such that certain information is excluded just because a small area of editors doesn't think it's relevant to the discussion of their articles.—Ryulong (琉竜) 19:20, 3 October 2013 (UTC)
I think you're missing my point. There is a difference between a transliteration (showing what the foreign script says - as in, how it's pronounced, and if applicable, how it would be spelled using Roman characters), and a translation (telling the user what it means). Overall, I have less of an issue with a transliteration, and that policy does make it clear that if we're going to use foreign script, we should consistently show the romanized equivalent, so I'm not going to keep arguing on that. But my original request for feedback here was on translations - first off, do they fall into WP:DICT at all? And do we have guidance on when and when not to include them? I would ask that you give other people who aren't directly involved in the VG debate a chance to respond to those questions. — KieferSkunk (talk) — 19:31, 3 October 2013 (UTC)

I am still interested to see what others have to say on this issue, but Ryulong pointed me to WP:VG/JP, which shows the result of prior consensus discussions on this topic specifically in the videogames space. I'm satisfied that at least for that project, translations are agreed-upon to be useful. — KieferSkunk (talk) — 19:49, 4 October 2013 (UTC)

Hello? Anyone? Bueller? — KieferSkunk (talk) — 01:30, 15 October 2013 (UTC)

I had not read the talk page before I made my edit to this page, but I think I have partially addressed this issue with the addition of "Care should be taken when translating text into English that a term common in the host language does not create a neologism in English." This sentence existed in Wikipedia:Avoid neologisms prior to the merge on 26 April 2010. This is wording I added to the guideline Wikipedia:Avoid neologisms back in 2008. I originally placed that sentence into the guidance after a number of pages were shown to be words taken from a foreign language and used in English either directly by a Wikipedia editor or by a few academics in a country using a term in their own language in papers published in English, but not taken up by English authors. EG Macedonism which after a long debate (see Talk:Macedonian nationalism/Archive 2) was merged into Macedonian nationalism‎ -- PBS (talk) 11:26, 14 December 2013 (UTC)

  • Late commentary: It's original research to "reach" for an absurdist translation. Any thesaurus tells us that mega- and enormous (along with many other words) are essentially synonymous in such a context. If a Japanese–English dictionary tells us that the Japanese word here being rendered as 'engine' is also conventionally used for 'drive' in the computer optical media reader sense, then a (not "the") correct literal translation is in fact "Mega Drive", and it's not any kind of encyclopedic exercise to cast about a wacky alternative translation that someone thinks is "more" correct somehow; that's a point-of-view issue, too, and smacks of Engrish-ism. If the word really only ever means 'engine' then Mega Engine would be OK as a literalism, if consensus on the article's talk page thought this informative enough to include, which seems reasonable. But there's no reason to ever use 'enormous' in this case. FWIW, recommend asking for help at WT:LINGUISTICS any time something like this comes up. Anyone with linguistic training has a pretty good sense of what is and is not a reasonable contextual gloss (in sense 2.1 at wikt:gloss) of a non-English word or phrase given the available information.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  04:38, 6 August 2015 (UTC)

Proposal: permit warranted uses of dictionary definitions in relation to national culture and the provision of context to items on disambiguation pages

I have recently produced an article: English rose (personal description) which, at its root, has a purely dictionary style content. In this particular case, however, the article presents a dictionary content that may be argued to have provided inspiration to many of the items on the English rose disambiguation page and and that provides a significant reference in English culture.

The English Rose page, in an earlier form, had contained a content that strongly featured the primary definition/s of the phrase:
https://wiki.riteme.site/w/index.php?title=English_Rose&diff=prev&oldid=287273605
Over time this reference to the primary definition of the term was progressively edited away and this may have been partly due to Wikipedia's obsession with not being a dictionary.

In the case of disambiguation pages that contain items that are named due to a meaning conveyed by their name then I think that Wikipedia is lessened when it ignores the option of presenting dictionary content in the same space as a listing of disambiguation titles. Gregkaye (talk) 03:08, 6 August 2014 (UTC)

No need for any policy change here. Just write an encyclopedic not dictionarian article on the term. We have thousands and thousands of articles like this.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  04:39, 6 August 2015 (UTC)

Lists of "Local and indigenous names" for various animals

I noticed that there are several sections that contain lists of synonyms in various languages. Should these lists be migrated to Wiktionary? Jarble (talk) 18:32, 4 August 2015 (UTC)

They could be copied there, but on WP they serve a purpose. That said, many of them need pruning, to only include those that are evidenced in English-language sources as a vernacular name for the animal/plant. We don't need a list of every known name of something in every language with a word for it. Basically, there should be a 1:1 correspondence between non-English names redirecting to the article, and their appearance in the article (which means some redirs should be deleted at WP:MFD if they are not attested in English-language sources as names ever used in English). All you need for sourcing is something like a journal article reading, e.g., "The fnord (from the native Qwuertyuiop language) or rednosed frumious bandersnatch (Badersnaticus frumiosus fnorda) of northern Madagascar ...." What we don't want is a source like the following used to create a WP:LAUNDRYLIST in the article: "The frumious bandersnatch is known in Qwuertyuiop as fnord, in Abababababab as flord, in Gjsdosoifsdlfjsdfj as pnord ..." etc., etc. It needs to be used as a word-in-context in an English language sentence, not as a foreign word that English is linguistically reporting on. There's no policy "rule" about this, I'm just saying from a WP:COMMONSENSE perspective, the way to avoid WP:INDISCRIMINATE / WP:DICDEF / WP:NOR problems is to not be indiscriminate, to not treat an encyclopedia like a multilingual dictionary, and to not engage in novel analysis that posits that some foreign term is "used" in English because something in English referred to it in its original non-English context.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  04:50, 6 August 2015 (UTC)

Reason for deleting neologisms

WP:NEO comes up in deletion discussions every now and then, and this what it currently says:

Articles on neologisms are commonly deleted, as these articles are often created in an attempt to use Wikipedia to increase usage of the term.

Is that really the problem? In my experience, the problem with articles about neologisms is typically either a lack of third-party coverage of the denoted concept, or in fact the lack of a clear-cut definition with people using the neologism to denote multiple distinct concepts that should not be in a single article.

The current text suggests that the Wiki community assumes bad faith on the part of authors of such articles. QVVERTYVS (hm?) 17:25, 16 August 2015 (UTC)

I'd support adding these additional reasons, but also keeping the present one, since it's a common problem.  — SMcCandlish ☺ ☏ ¢ ≽ʌⱷ҅ᴥⱷʌ≼  01:39, 19 August 2015 (UTC)
Retrieved from "https://wiki.riteme.site/w/index.php?title=Wikipedia_talk:Wikipedia_is_not_a_dictionary/Archive_15&oldid=1079358900"