Talk:national average

From Wiktionary, the free dictionary
Latest comment: 6 years ago by Sgconlaw in topic RFD discussion: November 2016–July 2017
Jump to navigation Jump to search

SoP really. Equinox 16:54, 24 June 2017 (UTC)Reply

RFD discussion: November 2016–July 2017[edit]

The following information passed a request for deletion (permalink).

This discussion is no longer live and is left here as an archive. Please do not modify this conversation, but feel free to discuss its conclusions.


SoP. Also easy to find "national total", "county average", and so on. Equinox 03:41, 20 November 2016 (UTC)Reply

Sidebar: clarity on "translation targets"[edit]

Could we have some clarity on when terms should be retained as "translation targets"? I looked at WT:SOP, and the only relevant paragraph seems to be the following: "In rare cases, a phrase that is arguably unidiomatic may be included by the consensus of the community, based on the determination of editors that inclusion of the term is likely to be useful to readers." However, it does not appear that "translation targets" are likely to be rare. Do we need to have a discussion and vote on the issue (@Daniel Carrero)? — SMUconlaw (talk) 14:09, 20 November 2016 (UTC)Reply

The translation target rationale is not in CFI. It is not clear that it is supported by consensus. I have seen a fair number of editors support translation target on a host of terms, but I do not know whether the supporters make up 2/3 or the like. I and bd2412 have been working on more specific criteria, the latest draft of which is at User_talk:Dan_Polansky/2015#Let's draft a vote for CFI translation criteria 2. --Dan Polansky (talk) 14:25, 20 November 2016 (UTC)Reply
Great, keep us informed when it's ready for wider discussion. — SMUconlaw (talk) 18:06, 20 November 2016 (UTC)Reply
I am basically an inclusionist but I don't like the idea of "translation targets" exactly. The way I prefer to think about it is that when lots of other languages have unexpected translations for a particular concept, it's a clue that the English term, however denotionally transparent, is nevertheless idiomatic, and should be kept on those grounds. Ƿidsiþ 13:34, 23 November 2016 (UTC)Reply
I agree that the existence of compound translations that use unexpected component words or patterns can be (strong?) evidence supporting English idiomaticity, at least if multiple language families or independent languages are involved. The argument would also support including terms like chalk and cheese, Mutt and Jeff, etc. DCDuring TALK 17:06, 23 November 2016 (UTC)Reply
I disagree that other languages' lexica can determine the idiomaticity of an English expression. English "be silent" is utterly unidiomatically SOP regardless of the existence of schweigen, zwijgen, taire, taceō, молча́ть, callarse, calar, and the rest. —Aɴɢʀ (talk) 17:00, 24 November 2016 (UTC)Reply
Classes of words such as the one you refer to seem to me to offer little support for idiomaticity. In the case of those translated into English as be + an adjective, I'd favor exclusion. I'm sure that are other patterns that similarly are trivially rendered into English phrases quite predictably. We already have a great deal of trivial content and hardly need more. DCDuring TALK 18:22, 24 November 2016 (UTC)Reply
But using an adjective to convey this idea IS idiomatic; most languages use a specific verb. (I am just talking about idiomaticity in an abstract way here; I agree that "be silent" doesn't need a dictionary entry.) Ƿidsiþ 08:01, 29 November 2016 (UTC)Reply
My personal opinion is that "translation target" should be restricted to a few very common phrases that are commonly expressed as a single word in other languages, i. e. day after tomorrow/day before yesterday, last year or maternal grandmother. It shouldn't be used indiscriminately as an argument for keeping any number of SoP entries. -- Pedrianaplant (talk) 10:14, 14 May 2017 (UTC)Reply

No consensus to delete. Also not really the place to settle the question of a translation target policy. bd2412 T 15:57, 20 June 2017 (UTC)Reply