Jump to content

Talk:Sierra Nevada

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Major update

[edit]

The edits by the IP editor on May 30, 2010 add some useful material, but also negatively impact the formatting of the article, and also I believe the writing. I will copy the current version of the article to /Temp and revert the edit. I will start to work on /Temp: all other editors are welcome to work on that version, too. When we reach a version we are happy with, we can replace the article contents. —hike395 (talk) 07:19, 30 May 2010 (UTC)[reply]

I'm finished with editing /Temp for today. Other editors: feel free to improve it further. —hike395 (talk) 09:38, 30 May 2010 (UTC)[reply]

I've copied the version from /Temp back into the main article. There have been a number of changes:

  • I wrote a new lede (a three-paragraph summary of the rest of the article)
  • Geography section somewhat compressed: some details were sent to the infobox by anon editor
  • Table of road passes sent to their own list article (to make this article more prose-filled)
  • Sections re-ordered
  • Ecology section compressed: list of species deleted (still in Ecology of the Sierra Nevada)
  • History section expanded
    • Anon editor added more material
    • I added section on 20th century protection from development
  • Pictures re-arranged, some dropped, some added
  • See also and external links compressed: links incorporated into main text by anon editor

As usual, everyone is free to improve on the article directly, or please add your comments here. Is there still missing material? I'm thinking we need a section on economic activity/tourism, and perhaps one on mountaineering.

Happy editing! —hike395 (talk) 10:47, 31 May 2010 (UTC)[reply]

Later: User:71.219.171.61 has some good feedback on the article (inline questions as HTML), I'll investigate the 1542 evidence, and other clarifications.
User:71.219.171.61 may not be familiar with the guidelines of writing a wikipedia article, however. Note that WP:LEAD states that the lede should be a stand-alone summary of the whole article. Therefore, it is OK to include the same information in the lede and in the infobox, or in the lede and in the whole article. Also note that WP:SEEALSO states: Links included in the "See also" section may be useful for readers seeking to read as much about a topic as possible, including subjects only peripherally related to the one in question. Having a link to Sierra Nevada-Great Valley Block in See Also does not require the Geology section to describe it.
I'll get to work on clarifying —hike395 (talk) 18:43, 31 May 2010 (UTC)[reply]
During editing:
  • {{Wide image}} is needed to properly format a large image for smaller displays. Note that WP:IMGSIZE directs us to not have images directly included larger than 500px. MOS:IMAGES directs us to use {{Wide image}}.
  • MOS:IMAGES also directs us to put images in the section that is most relevant: I moved the photo of General Sherman down to the conservation section, next to discussion of logging of Giant Sequoia.
  • There is no reliable, commonly-agreed upon "lowest" part of a mountain range. That parameter to the geobox is meant for other geographical features.
  • The Yosemite Online Library is a valuable source of public domain books/documents about the whole Sierra (despite its name). It's maintained by Dan Anderson.

Dear Anon Editor: are you reading this discussion page? If so, please indicate here. I have been addressing your concerns (e.g., I put a page number in for the 1912 date), but you reverted my edits and put back several of the notifications that my edit had addressed. Further, some of my edits are to make the article obey Wikipedia guidelines, but you revert those changes.

I left some notes as HTML comments on the article (a very poor practice, because it is impossible to add wikilinks and keep track of who is saying what). Let's confine our discussion here.

Other editors: I'm getting somewhat frustrated at the difficulty in cooperating with the Anon editor. Judging from the edit comments and the HTML comments left by the Anon editor, I think he/she may have an issue with my edits. I would welcome other editors to come in and help with some of these issues. Thanks!

--- —hike395 (talk) 01:49, 1 June 2010 (UTC)[reply]

OK, I don't think I can work with Anon Editor, keep my cool, and have a productive collaborative editing session. He/she is saying I'm making "false claims" in the edit summary. I cannot get him to discuss on the talk page: he keeps wanting to use HTML comments. I try and fix his concerns, but then he reverts the fixes and reposts the concerns. For example, he labeled "northern Sierra" as ambiguous in the Geologic History section. I did a bunch of research, cleaned up the section, removed the offending "ambiguous" phrase, and added references: that should have addressed the concern. He promptly restores the sentence with his concern again.
In previous edit disputes, I've seen some editors personalize a dispute with a single other editor. That's very likely to be happening here. It's not healthy for an article to simply ping-pong unproductively between two editors. There's no deadline: I'm willing to step back for a while and see if consensus will build without me.

—hike395 (talk) 09:58, 1 June 2010 (UTC)[reply]

I've undone the last anon edit and removed the hidden comments. Discussion should be here not in hidden comments. The anon needs to discuss here and focus on content - avoiding the comments about other editors. To that end I've semi-protected the article for a couple weeks. Vsmith (talk) 12:13, 1 June 2010 (UTC)[reply]

Restoring deleted information

[edit]

In the editing back-and-forth on 30 May-1 June, some information was deleted. I also believe that the format and writing of the article suffered. I will fix what I perceive as the problems, and keep track of the fixes, below. If other editors disagree, then can comment here or continue to improve the article directly.

  • Sequoia picture causes bunching, moved down to conservation section, where it is more topical
  • Infobox width: removed (50-80), no units specified
  • Infobox lowest: lowest part of Lower Montane Forest does not correspond to lowest part of range (an ambiguous concept). No RS: deleted
  • Infobox period: changed to Mesozoic --- most of the granite dates to the Cretaceous, but not all
  • Restored parenthetical translation to first sentence (redundancy with infobox is OK)
  • Mention of ecology and geology from lede restored
  • Geography: restore paragraphs describing boundaries of range
  • Geography: convert bullet list of summit peaks back into prose paragraph, eliminate subsection
  • Move list article wlinks back into See Also section (rather than somewhat artificial see also in different section)
  • History: restore facts (Fremont saw Lake Tahoe, legislature authorized California Geological Survey)
  • Protected areas: clarify that 15.4% are protected from logging, rather than the total area of all of the parks/wildernesses (somewhat different)

I shall go back and add more relevant photos to the article: the editing seemed to remove a number of them. Also, the Anon editor raised some valid points in his/her last edit, which I will attempt to address, if these edits reach consensus. Thanks! —hike395 (talk) 11:55, 3 June 2010 (UTC)[reply]

Thanks for your efforts, hike395. For me, it is important that when someone who wants to make major revisions to an article that many editors have worked on, that editor (anonymous or not) explains their rationale for changes, participates in open discussion about the changes, and accepts consensus decisions. Cullen328 (talk) 15:25, 3 June 2010 (UTC)[reply]
  • Sorry for being late: It looks like Vsmith has given Hike some breathing room by semi-protecting the article. If the Anon comes back and acts in the same way, you can email me and I'll try to help. I tend to only edit Wikipedia during the weekends now, so comments on my talk page during the week may languish until the weekend. Sorry about that. --mav (reviews needed) 13:23, 5 June 2010 (UTC)[reply]

Plural in the name?

[edit]

The name is singular Sierra Nevada, so therefore "the Sierra Nevada". However are they known as the Sierra Nevadas with an "s"? Other mountain ranges are plural such as the Alps, the Himalayas or the Appalachians? Can this not be the case here?109.151.101.18 (talk) 09:56, 20 August 2013 (UTC)[reply]

Strictly, no: "Sierra Nevada" means "snowy mountain range" or "snowy saw teeth" in Spanish. "Nevada" means "snowy". So, Sierra Nevadas would mean "snowys mountain range". See [1] Colloquially, people do use "Sierra Nevadas", but that is minority usage.[2]
More strictly, never: since "Sierra" means range, the real question is how many ranges comprise the Sierra Nevada. The geologic answer is one. The Sierra is but a single, huge, block of granite that forms a single range of mountains from north to south. This article is inconsistent, using both the singular and plural forms throughout. It really should be cleaned up to use the term "Sierra" and "Sierra Nevada" exclusively.DRLWorthington (talk) 18:45, 20 August 2014 (UTC)[reply]
I only found one plural usage in the article, which I just fixed. If you see any others (other than in the infobox, which lists plural usage as alternative names), please feel free to fix them. —hike395 (talk) 02:24, 21 August 2014 (UTC)[reply]
Note, too, that "Himalaya" is the strictly correct term for the montain range. The singular (mountain) form is "Himal". There has been a fair amount of controversy over the article title of Himalayas, see Talk:Himalayas —hike395 (talk) 06:09, 21 August 2013 (UTC)[reply]

This is a very old conversation, but I do think it's notable that English speakers tend to say "the Sierra Nevadas". Perhaps there is something to be researched and cited to see if this counts as a case of American English. RobotGoggles (talk) 08:15, 27 May 2021 (UTC)[reply]

Requested move 20 April 2020

[edit]
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: Clear consensus to move buidhe 00:20, 27 April 2020 (UTC)[reply]


– Per WP:PRIMARYTOPIC.

Averaged over the past ~5 years (the earliest data in the pageviews tool), this article has more than twice as many page views as the articles for all other Sierra Nevada mountain ranges combined.[1]

Average monthly pageviews:

Number of backlinks in article namespace:

When I did a Google search for "Sierra Nevada", all the first page web results were either for the mountain range in California and Nevada or for the various US companies that derive their name from that mountain range. When I did a search from Madrid, Spain in Bing (which lets you change your search location), the same thing happened.

The article for macOS Sierra, which is listed on the Sierra Nevada dab page, does get a similar amount of pageview traffic to Sierra Nevada (U.S.). However, very few people are searching for that OS as "Sierra Nevada" instead of "Sierra", so it is hard to imagine many of those pageviews coming from this dab page in particular.

References

  1. ^ https://tools.wmflabs.org/pageviews/?project=en.wikipedia.org&platform=all-access&agent=user&redirects=0&start=2015-07&end=2020-03&pages=Sierra_Nevada_(U.S.)%7CSierra_Nevada_de_Santa_Marta%7CSierra_Nevada_de_M%C3%A9rida%7CTrans-Mexican_Volcanic_Belt%7CSierra_Nevada_de_Lagunas_Bravas%7CSierra_Nevada_(stratovolcano)
  2. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Sierra%20Nevada%20(U.S.)&from_namespaces=0
  3. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Sierra%20Nevada%20(Spain)&from_namespaces=0
  4. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Trans-Mexican%20Volcanic%20Belt&from_namespaces=0
  5. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Sierra%20Nevada%20(Spain)&from_namespaces=0
  6. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Trans-Mexican%20Volcanic%20Belt&from_namespaces=0
  7. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Sierra%20Nevada%20(stratovolcano)&from_namespaces=0
  8. ^ https://dispenser.info.tm/~dispenser/cgi-bin/backlinkscount.py?title=Sierra%20Nevada%20de%20Lagunas%20Bravas&from_namespaces=0
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Pronunciation

[edit]

Sol505000 changed the IPA pronuciation of "Nevada" from be from "Nuh-vada" to "Nih-vada" (from the "uh" sound in "abbot" to the "ih" sound in "kit"). The edit comment was:

  1. See note 42 in Help:IPA/English
  2. The two vowels are the same in American English

The problem with this edit is

  1. There is no note 42 in Help:IPA/English
  2. Native American English speakers pronounce abbot differently than kit

I would like to restore the original IPA. Comments? — hike395 (talk) 19:53, 5 May 2023 (UTC)[reply]

I also am unconvinced by the substitution of /ɪ/; that sounds wrong to me.
That said, "abbot" vs "kit" is not an adequate refutation, because when saying they're the same in American English, Sol505000 is referring to the so-called weak vowel merger. Those of us with the merger typically do not make much distinction among reduced vowels in unstressed syllables. That doesn't apply to "kit"; monosyllabic words are typically treated according to the same rules as stressed syllables.
Just the same, it would sound weird to me to hear a speaker (at least a speaker with a GA accent) pronounce it /nɪˈvædə/. --Trovatore (talk) 20:15, 5 May 2023 (UTC)[reply]
I also agree with restoring the original IPA. As a resident of the Sierra Nevada, it also seems to me that /ni .../ is not the accurate representation of the pronunciation.
It's probably also worth noting that said user also made the change on the page for the state of Nevada and provided a differing reason there. Said reason there seems to be based on the Spanish language pronunciation, which the American pronunciation has drifted significantly away from. Crescent77 (talk) 22:32, 5 May 2023 (UTC)[reply]
There are thousands of transcriptions with word-internal /ə/ (that is also morpheme-internal) that are also "wrong" when you apply literal reading of the IPA symbols and you speak American English. "Las Vegas" //lɑːs ˈveɪɡəs// is [lɑs ˈveɪɡɨs] in AmE. American [lɑs ˈveɪɡəs] would be //lɑːs ˈveɪɡʌs// in our system (with all of the vowels being full/unreduced), or at least ambiguous between that and the former. In RP //ə// is really [ə] and //ʌ// can only be [ʌ] or [ɐ], so that "Las Vegas" //læs ˈveɪɡəs// (with the TRAP vowel) is [læs ˈveɪɡəs] (you could get [las ˈveːɡɐs] in Geordie, which is about as far away as you can get from RP in England. That's still //-əs// in our system, obviously, due to the lack of the foot-strut split). Our transcriptions are neither phonetic nor phonemic but diaphonemic. The initial syllable of "Nevada" is pronounced /nɪ/ in conservative RP and therefore the correct diaphoneme is //ɪ//. For many if not most speakers, this will actually be /ə/ in the syllable-final position immediately before stress just as //hw// is /w/ in most dialects.
My edits regarding the Spanish pronunciation of "Nevada" have nothing to do with the weak vowel merger but the pronunciation of the first ⟨a⟩. Sol505000 (talk) 01:38, 6 May 2023 (UTC)[reply]
Are you under the impression that our transcriptions privilege conservative RP? I don't think that's true at all, or at least should not be true. --Trovatore (talk) 01:47, 6 May 2023 (UTC)[reply]
That's not my impression, it's literally what the guide says. It tells us not to transcribe the weak vowel merger at all. Brits can also complain about the US pronunciation of "Las Vegas" being transcribed as /lɑːs ˈveɪɡəs/ and not /lɑːs ˈveɪɡɪs/, which is how they hear it (unstressed /ɪ/ spelled ⟨a⟩ is exceptional, IIRC, and occurs only in words that had /aː/ in that position before the Great Vowel Shift, such as "orange"). This is why we need the double slashes: //lɑːs ˈveɪɡəs// for the US pron, //læs ˈveɪɡəs// for the UK pron. The only diaphonemic difference here is in how the A in "Las" is pronounced: in the US it gets the usual PALM vowel, whereas in the UK it gets the usual TRAP vowel, both reflecting how the foreign ⟨a⟩ is treated in the respective dialect. The American schwa/schwi is close in the morpheme-internal word-internal position and mid elsewhere, AFAIK. It's an allophonic difference, for the most part. Sol505000 ( talk) 01:48, 6 May 2023 (UTC)[reply]
It is always amazing to me how long and detailed and technical these debates about minor pronunciation variations can be. I am not an IPA guy. I am a guy who was born in Michigan but has lived in California for 51 years. I started visiting the Sierra Nevada in 1975 and have spent many months deep in its wilderness over the years. I am an old mountaineer who spent time around with great climbers who talk about these mountains with great reverence. I now live in the Sierra Nevada foothills, in Nevada County, California. The fact is that some people say "Nuhvada" and some people say "Nehvada", and nobody has any problem with either pronunciation, and nobody argues about it or misunderstands. The pronunciation is the same, whether discussing the mountain range or the state where gambling is the main industry. The entire issue is so utterly trivial that electrons should not be wasted on it. In the real world, nobody cares. But people do care about "Sierra Nevadas", as Ansel Adams fans are well aware. Cullen328 (talk) 06:31, 6 May 2023 (UTC)[reply]
As a former resident of Nevada County currently living in the Sierra(s) closer to the state of Nevada, folks do argue about a pronunciation difference, but it's whether the second syllable is æ or a:. With the mountains, both are accepted, with the state it's generally only the former residents find acceptable. WP does seem to have that covered. Crescent77 (talk) 19:27, 6 May 2023 (UTC)[reply]

Instead of a long and technical debate, I think we should follow standard WP procedure in case of a factual dispute, and consult reliable sources. I consulted four different online dictionaries:

  1. Merriam-Webster --- nə-ˈva-də
  2. Britannica --- /siˌerənəˈvædə/ /siˌerənəˈvɑːdə/
  3. Collins (American English) --- siˈɛrə nəˈvædə ; siˈɛrə nəˈvɑdə
  4. Dictionary.com --- siˈɛr ə nəˈvæd ə, -ˈvɑ də

In all cases, these RSes use a schwa ə. The possible source of the dispute is that Collins says that it's sɪˈɛərə nɪˈvɑːdə in British English. Since the mountain range is in the US, I believe we should use the American pronunciation, per MOS:TIES and MOS:RETAIN.

I really think we need to revert to the schwa ə. — hike395 (talk) 14:14, 6 May 2023 (UTC)[reply]

I agree, the WP guidelines Sol505000 references leave much open for interpretation, following the reliable sources is much more WP appropriate. Crescent77 (talk) 19:32, 6 May 2023 (UTC)[reply]
Longman Pronunciation Dictionary gives both /ə/ and /ɪ/ in the first syllable and recommends the latter for RP (so the pronunciation is not limited to Conservative RP - Wells would not recommend it in that case). Cambridge English Pronouncing Dictionary gives both but recommends the pronunciation with /ə/ for both dialects. The correct diaphoneme is clearly //ɪ//.
A local consensus here does not override MOS:DIAPHONEMIC. We've been through this before on Melbourne and other pages. Per Help:IPA/English, //ɪ// is always distinguished from //ə// in unstressed syllables per note 24 and 35. Americans should interpret //ɪ// in this position as their /ə/. Sol505000 (talk) 20:34, 6 May 2023 (UTC)[reply]
None of the sources you provide show clear support for your position. Crescent77 (talk) 21:29, 6 May 2023 (UTC)[reply]
They do. An unstressed /ɪ/ in the British pronunciation (or one British pronunciation) that corresponds to /ə/ in the American pronunciation is our //ɪ// diaphoneme. Sol505000 (talk) 21:41, 6 May 2023 (UTC)[reply]
Wow, that's a perplexing response. You seem to be indicating you have nothing to support your position. Why are you pushing for the change? Crescent77 (talk) 21:46, 6 May 2023 (UTC)[reply]
I am not indicating that though? Sol505000 (talk) 21:49, 6 May 2023 (UTC)[reply]
Okay, I'm on mobile so it's hot easy to edit to match your edits, so I'll just continue the thread. So who are you referencing when tou say "our"? Crescent77 (talk) 21:50, 6 May 2023 (UTC)[reply]
Help:IPA/English, obviously. Sol505000 (talk) 21:50, 6 May 2023 (UTC)[reply]
It's not obvious when it's not stated in the comment itself, and the previous comment references multiple different locations. Crescent77 (talk) 21:53, 6 May 2023 (UTC)[reply]
Help:IPA/English is the only IPA guide on Wikipedia that deals with diaphonemes rather than phones (actual sounds) themselves. I thought it was clear. Sol505000 (talk) 22:23, 6 May 2023 (UTC)[reply]
And it says the two are interchangeable. I don't understand why you're pushing one over the other, when both references and consensus suggest the opposite. Crescent77 (talk) 22:49, 6 May 2023 (UTC)[reply]
Where does it say that? Sol505000 (talk) 22:50, 6 May 2023 (UTC)[reply]
The key shows a schwa as acceptable, with no notes suggesting otherwise. Note 35 says the 2 are not distinguished in certain circumstances, but does not advise against the use of schwa. I don't see anything saying we're required to replace the schwa with the i, which if I understand correctly, is what you seem to be indicating. Crescent77 (talk) 23:06, 6 May 2023 (UTC)[reply]
It does. It clearly tells us to use ⟨ɪ⟩ whenever RP and GA diverge and the latter uses a schwa to the exclusion of /ɪ/. Sol505000 (talk) 23:08, 6 May 2023 (UTC)[reply]
Where? Please reference that. Crescent77 (talk) 23:11, 6 May 2023 (UTC)[reply]
You reference where it says that ⟨ə⟩ can be used in this context. Sol505000 (talk) 23:17, 6 May 2023 (UTC)[reply]
The key at the top of the IPA guide.. The references hike395 provided. Crescent77 (talk) 23:40, 6 May 2023 (UTC)[reply]
Just to ask, your responses are confusing, are you a native English speaker? Crescent77 (talk) 21:51, 6 May 2023 (UTC)[reply]
That is not relevant to this discussion. Sol505000 (talk) 22:12, 6 May 2023 (UTC)[reply]
No offense intended, you don't need to answer
I'm just trying to give you a chance to explain yourself and support your point of view so I better understand it. Your suggestion seems to be based purely on a personal subjective interpretation of a vague guideline, the issue being hat both consensus and references support the opposite.
You seem to operating in good faith, have thought about this alot, and have a strong conviction you are making a positive change. I'd like to believe you are making the correct interpretation and be able support your efforts, but with Wikipedia we need you to make arguments supported by references and guidelines. No offense, but you're kind of all over the place. Your opening statement references notes than don't exist, and your arguments haven't had clear support from references nor guidelines since. I'm just trying to give you a chance to better explain yourself, because at this point it seems a revert of your edit is the WP appropriate thing to do. Crescent77 (talk) 22:59, 6 May 2023 (UTC)[reply]
I can't see how my interpretation is subjective or how the guideline is vague. Maybe you just don't understand it? Sol505000 (talk) 23:05, 6 May 2023 (UTC)[reply]
I don't understand it, my issue is that I'm not so sure you to do either .
If you have a reference showing clear support for your specific change, please copypaste the specific wording showing so. Linkspam to general guidelines full of material unrelated to the discussion at hand are not helpful. Crescent77 (talk) 23:11, 6 May 2023 (UTC)[reply]
If you don't understand the Help:IPA/English guide then this discussion should be ended. Sol505000 (talk) 23:20, 6 May 2023 (UTC)[reply]
I understand the guide, what I don't understand is how you are using it as a justification for your change. I need you to reference the specific phrasing in that guide supporting your change, which you have failed to do upon previous requests.
If you wish to end the discussion here, feel free to do so, but please undertand, at this point, it seems pretty clear that a revison to schwa is in order. Crescent77 (talk) 23:39, 6 May 2023 (UTC)[reply]
You clearly don't understand the guide. If you did, you'd know that the weak vowel in rabbit, bizarre, Latin, usually spelled with ⟨i⟩ or ⟨e⟩, is the diaphoneme we're discussing here. Per guide, the only allowed transcription of that vowel is ⟨ɪ⟩. regardless of how it is realized in any specific dialect. Help:IPA/English deals with diaphonemes, not sounds per se.
I am just going to repeat that a local consensus here does not override MOS:DIAPHONEMIC. I will revert any changes to a schwa symbol. Sol505000 (talk) 23:50, 6 May 2023 (UTC)[reply]
A consensus most certainly does, that's how WP operates. Please reconsider your position, your comment suggests an intent to violate the Wikipedia:Edit warring policy which could result in block. Crescent77 (talk) 00:01, 7 May 2023 (UTC)[reply]
No, it does not. If you want to change MOS:DIAPHONEMIC you can go to Wikipedia talk:Manual of Style/Pronunciation and make your case there. If you want to change the guide, go to Help talk:IPA/English. This discussion here has no bearing on either of them. Sol505000 (talk) 00:04, 7 May 2023 (UTC)[reply]
Please review Wikipedia:Policies and guidelines as well as Wikipedia:Five pillars. Crescent77 (talk) 00:17, 7 May 2023 (UTC)[reply]
See Wikipedia:Manual of Style. "This Manual of Style (MoS or MOS) is the style manual for all English Wikipedia articles (though provisions related to accessibility apply across the entire project, not just to articles)." MOS:DIAPHONEMIC is not mentioned there but MOS:PRON is. MOS:DIAPHONEMIC is a mere subsection of that. Sol505000 (talk) 00:29, 7 May 2023 (UTC)[reply]
Please review the material I suggested. Note that WP:MOS is a guideline, whereas WP:Consensus is a policy. Crescent77 (talk) 00:37, 7 May 2023 (UTC)[reply]
A consensus based on a lack of understanding of Help:IPA/English and MOS:DIAPHONEMIC is not valid. You have shown your lack of understanding of the guide so I consider this conversation to be over. Sol505000 (talk) 00:41, 7 May 2023 (UTC)[reply]
Unfortunately it looks like you also need to review Wikipedia:No personal attacks. Crescent77 (talk) 01:18, 7 May 2023 (UTC)[reply]
OK, everybody, let's take a deep breath. People are getting entrenched into emotional positions that aren't going to be helpful in the long run.
Sol505000, you're coming across a bit imperious here. It would be productive to dial it back a little.
My fellow Americans, I can understand the frustration at having someone come tell us we have to write a symbol meaning the "ih" sound in our pronunciation key, when we can hear the "ih" sound but just don't say it that way. But consider on the other side: We consistently transcribe the diphthong in "out" as /aʊ/, whereas RP speakers would say /ɛʊ/. They can hear the difference between that and /aʊ/, but just don't say it (the latter) way. Similarly for r's after vowels.
This diaphonemic scheme is pretty complicated but does seem to be designed to preserve information as best possible. If you know the details and have a pronunciation key from the scheme, you can accurately predict the pronunciation in a wide variety of accents. It's a fair criticism that the learning burden required to do that is high. --Trovatore (talk) 01:04, 7 May 2023 (UTC)[reply]
Thanks for the constructive input.
I'm still trying to understand Sol's viewpoint, do you agree with them? What do you understand to be the appropriate symbology in this situation? Crescent77 (talk) 01:15, 7 May 2023 (UTC)[reply]
I think the idea goes something like this: Although those of us with the weak vowel merger can hear the difference between /nɪˈvædə/ and /nəˈvædə/, we shouldn't be misled by it, because we don't distinguish /ɪ/ from /ə/ phonemically in unstressed syllables. That is, there's no pair of words with different meanings, where we would understand one of them if it used /ɪ/ in an unstressed syllable, and the other if it used /ə/.
On the other hand, RP speakers do use it distinctively even in unstressed syllables ("Lenin" vs "Lennon"), and therefore might be misled, given that they would specifically say /nɪˈvædə/.
(As an aside, I'm not really so sure that Americans don't distinguish "Lenin" from "Lennon" the same way, at least in careful speech, which is a possible flaw here.)
As for preferred typology — I'm not sure. The /nɪˈvædə/ strikes me as odd enough in GA that it might make sense to call it out as a specifically UK pronunciation, but in fairness note the point about the "out" diphthong I raised above.
On a related note, at some point the use of the reduced-vowel version /ᵻ/ seems to have been deprecated in our pronunciation keys. I'm not sure that was a great decision. But it wouldn't help much here, because as far as I'm aware there is no common American pronunciation of "Nevada" that uses [ᵻ]. --Trovatore (talk) 05:31, 7 May 2023 (UTC)[reply]
Yes, the whole point is that the distinction between //ɪ// and //ə// in unstressed syllables applies only to those speakers that do not have the weak vowel merger. Therefore, we need to follow British sources on that because the distinction is as British as the distinction between //ɒ// and //ɑː//.
The fact that even RP speakers can use /ə/ in the first syllable of "Nevada" is no reason for a separate transcription. There's thousands of words in which this is the case (yet, other words, such as "rabbit", are heard only with an unstressed /ɪ/ in RP: /ˈræbɪt/, not */ˈræbət/). Modern RP features a partial merger that is particularly resisted in some environments (/ɪd/ in "batted" /ˈbæt#ɪd/ is typically distinguished from /əd/ in battered /ˈbætə#d/. ⟨#⟩ marks a morpheme boundary here. Non-rhotic Americans with the merger (as in older New York City English but not Boston or Southern American English) also distinguish the two (cf. "roses" /ˈroʊz#əz/, [ˈroʊzɨz] vs. "Rosa's" /ˈroʊzə#z/, [ˈroʊzəz]), but they rhyme "rabbit" /ˈræbət/, [ˈræbɨt] with "abbot" /ˈæbət/, [ˈæbɨt] which RP speakers do not. That's the weak vowel merger: the vowel is closer to /ɪ/ in some environments and to /ə/ in others, which is sadly not reflected in most dictionaries, which give /ɪ/ in some words and /ə/ in others not according to how the merged vowel really sounds in AmE (which would make the symbol ⟨ɪ⟩ far more common than it is now and the difference between /ə/ and /ʌ/ could be scrapped for AmE) but according to the RP distribution (more or less) which makes zero sense (nor do they consistently use ⟨ə⟩ for the merged vowel: batting is /ˈbætəŋ/ in AmE, not /ˈbætɪŋ/, because /ə/ triggers flapping and the nasal can be syllabic after g-dropping. If "Latin" has /ə/ then so does "batting"). If ⟨ə⟩ is good enough for /lɑːs ˈveɪɡəs/ then ⟨ɪ⟩ is good enough for /nɪˈvædə/. Sol505000 (talk) 10:07, 7 May 2023 (UTC)[reply]
Not all of that really rings true to me for AmE. Especially I don't agree with conflating /ə/ and /ʌ/. As I see it, the weak vowel merger creates a phoneme, most conveniently represented phonemically for AmE as /ə/, but this phoneme exists only for weak vowels; it has no stressed counterpart. The way you can tell that is the fact that it can be realized as many different phonetic vowels that in stressed positions are all phonemically distinct. The weak vowel is sometimes rendered as [ʌ], sometimes as [ɪ], sometimes as [ʊ], or somewhere indistinct among these, and while there may be certain statistical regularities, the realizations are more or less in free variation. I see no reason to pick out the ʌ particularly from among these. --Trovatore (talk) 18:02, 7 May 2023 (UTC)[reply]

I think I understand the argument, which appears to be saying there are two groups of pronunciations:

  • British pronunciation, which is /nɪˈvædə/
  • All others (including Americans), who have weak vowel merger, and should read /ɪ/ as /ə/

therefore, /nɪˈvædə/ "covers" the pronunciations and should be the only one (per MOS:DIAPHONEMIC).

The problem with this argument is that there are a substantial number of Americans (including myself) who do not have weak vowel merger, and hear and pronounce /ɪ/ distinctly from /ə/. Only showing /nɪˈvædə/ would thus direct a large number of non-vowel-merging Americans to mispronounce the word (i.e., not use their normal accent, but use an artificial British accent). This would be phonetic underdifferentiation.

Unfortunately, there does not appear to be a diaphoneme that is acceptable for use in WP in this case. As Trovatore pointed out, the symbol //ᵻ// used by the OED was deprecated in 2017, and //ə̇// has never been adopted by WP.

One way to resolve this conflict is to follow the second paragraph of MOS:DIAPHONEMIC, which says that alternative pronunciations can be used, and also points out that local pronunciations are of particular interest for place names. Thus, I would propose following Collins and use

/siˈɛrə nəˈvædə/, /siˈɛrə nəˈvɑdə/ (American English); /sɪˈɛərə nɪˈvɑːdə/ (British English)

Would that satisfy everyone? — hike395 (talk) 23:44, 7 May 2023 (UTC)[reply]

The vast majority of Americans (and all Canadians, AFAIK) have the merger (see weak vowel merger). Only some Southern American English doesn't. The unstressed //ɪ// and //ə// are both closer to /ə/ in some positions and /ɪ/ in others in AmE. Using the symbol ⟨ɪ⟩ is not a judgement on the quality of the vowel, especially in AmE.
//ɪ// is the diaphoneme to be used in this case. It is listed twice, as a full vowel and as a reduced vowel subject to a merger with /ə/ in accents with the weak vowel merger.
That doesn't work: /nəˈv*də/ vs. /nɪˈv*də/ is not a diaphonemic difference but a phonemic one. The diaphoneme is //ɪ//: //nɪˈv*də//. The variation in the pronunciation of the second vowel is the only diaphonemic difference here: //nɪˈvædə//, //nɪˈvɑːdə//.
/siˈɛərə/ is an alternative pronunciation in BrE that coexists with /siˈɛrə/ and /ˈsɪərə/. It's not the same as the Mary-merry merger, in which case /siˈɛrə/ would not be possible in BrE. We can list /siˈɛərə/ and /ˈsɪərə/ as alternative BrE pronunciations. Sol505000 (talk) 02:24, 8 May 2023 (UTC)[reply]
Please check your claims, specifically "only some southern american english..." as your first link specifically mentions new england english. It's also a documented part of other vernaculars derived from such during westward expansion. Crescent77 (talk) 16:32, 19 August 2023 (UTC)[reply]
there are a substantial number of Americans (including myself) who do not have weak vowel merger That runs directly counter to what literature says. I wonder if you're not mistaking phones for phonemes. (The lack of the merger doesn't just mean you "hear and pronounce /ɪ/ distinctly from /ə/". It means they're in contrastive distribution in unstressed syllables.) Are Lenin and Lennon, bizarre and bazaar, etc. really distinct for you? Nardog (talk) 07:03, 8 May 2023 (UTC)[reply]
Speaking for myself unscientifically, I don't think I distinguish Lenin and Lennon, but I do think I distinguish bizarre and bazaar. --Trovatore (talk) 16:19, 8 May 2023 (UTC)[reply]
I agree, local vernacular does distinguish between bizarre and bazaar. Crescent77 (talk) 16:32, 19 August 2023 (UTC)[reply]
If this is backed up by sources then we need to update our definition of the weak vowel merger (currently, it only says that Rosa's is distinct from roses), Help:IPA/English and all transcriptions with a prevocalic /ɪ/ that is actually /ə/ in AmE. Nevada is not special in this regard, and I don't believe that this distinction (assuming that it exists) is limited to the local vernacular of Nevada. Sol505000 (talk) 11:29, 15 September 2023 (UTC)[reply]
Thanks for your continuing efforts on this topic.
I would just like to reiterate that the issue at hand may revolve around to what extent the weak vowel merger is present in the local vernacular in question. As noted above, it is heavily derived from American dialects which do not have the weak vowel merger. Crescent77 (talk) 04:59, 17 September 2023 (UTC)[reply]

We used to distinguish these possibilities, with ⟨ᵻ⟩ for the high reduced vowel. RP merges this with the KIT vowel, and GA with the COMMA vowel. Since we now have to choose between dialects, we should go with GA for US place names and RP for UK place names.

As for bizarre ~ bazaar distinction in GA, that's a matter of vowel reduction: with a reduced vowel, the two are homonyms, but without one the first has the KIT vowel, distinguishing it from Nevada, which does not. Without vowel reduction, Nevada has the DRESS vowel, as a local mentioned above.

Although /ə/ sometimes approaches [ɪ] in GA, esp. around /t/ and /d/, that's a phonetic detail, on par with aspiration, and we don't transcribe phonetic details.

Personally, I think we should just restore ⟨ᵻ⟩ to the template so that we can have pan-dialectal transcriptions again, rather than having to choose between RP and GA whenever it appears. — kwami (talk) 04:51, 5 December 2023 (UTC)[reply]

I agree that restoring ⟨ᵻ⟩ to the template would be the best option. But how likely is that to happen? Can we just use it at this article to resolve the dispute? — hike395 (talk) 22:49, 5 December 2023 (UTC)[reply]
No, changing the template would make it WP-wide. The argument to stop supporting ⟨ᵻ⟩ was that it was hard to know when to use it. If we have the KIT vowel in RP and the COMMA vowel in GA, then we'd use ⟨ᵻ⟩. The problem occurs when we don't have RS's for both RP and GA, but really it's usually pretty easy to figure out. — kwami (talk) 03:48, 6 December 2023 (UTC)[reply]
+1 Double sharp (talk) 04:05, 6 December 2023 (UTC)[reply]
To clarify, kwami, you're in favor of using ⟨ᵻ⟩ in this article? — hike395 (talk) 23:07, 6 December 2023 (UTC)[reply]
I'm in favor of restoring support of ⟨ᵻ⟩ to the template. I don't think it's appropriate to add a letter to a specific article if it isn't included in the key. If we don't have support of ⟨ᵻ⟩, then I think we should go with the GA pronunciation (i.e. schwa) over the RP, unless we list both, which IMO would be overkill. — kwami (talk) 00:40, 7 December 2023 (UTC)[reply]
What do you think of the argument (above) that MOS:DIAPHONEMIC implies that GA speakers will known to read /ɪ/ as /ə/? — hike395 (talk) 07:24, 7 December 2023 (UTC)[reply]
They'll just pronounce it wrong. That wouldn't matter much in cases where /ə/ is pronounced more or less as [ɪ], e.g. after /t/ or /d/, but it isn't in this case. It isn't diaphonemic, and won't work for Australians either. If we keep it as-is, we should mark it as the UK pronunciation. — kwami (talk) 09:32, 7 December 2023 (UTC)[reply]
The respelling is also wrong. Even if we transcribe it as /ɪ/ in IPA, the corresponding respelling is "nə-VAD-ə", not "niv-AD-ə", which makes no sense at all. — kwami (talk) 09:36, 7 December 2023 (UTC)[reply]
I agree with you: the current IPA is doing a disservice to our readers who will be misled into thinking the RP is the universal pronunciation for the mountain chain. I would support going back to /ə/ and fixing the respelling. — hike395 (talk) 10:07, 7 December 2023 (UTC)[reply]

Mass noun

[edit]

Context is this edit.

@Dogwith4shoes: can you explain your reasoning here, and ideally give a source? Right now your text makes it sound like "range" in English (in the sense of "mountain range") is a mass noun, but that is not true. "Range" is a count noun. You can say the Sierra Nevada is a range, but you can't say that it's "range", which you could if "range" were a mass noun. --Trovatore (talk) 00:04, 19 November 2024 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Sierra_Nevada&oldid=1258258035"