Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add phonetic pronunciation for WHATWG #448

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

tylerjmorg
Copy link
Contributor

I figured that it may be useful to add IPA pronunciations for the different examples on the FAQ page.

Small change, but may be useful for internationalization of the name. :)

Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is pretty neat. Happy to trust you these are correct.

whatwg.org/faq Outdated Show resolved Hide resolved
@tylerjmorg
Copy link
Contributor Author

Thank you! That should be fixed for IETF langs.

@tylerjmorg
Copy link
Contributor Author

Also, would you rather en-UK be switched to en-GB?

@annevk
Copy link
Member

annevk commented Jul 16, 2024

Yeah, en-GB would be better.

There was this feedback on Matrix about this PR:

They have "what" as rhyming with "lot" in both the UK and US pronunciations – I think at least in the US it's a lot more common to rhyme it with "cut"

Copy link
Member

@gsnedders gsnedders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder how much value there actually is in having the en-US/GB distinction here? There's only any notable distinction in the "what", and arguably even then these are different realisation of the same phonemes.

Comment on lines +56 to +57
<dd>en-US: /wɑːt.wi.dʒi/
<dd>en-UK: /wɒt.wi.dʒi/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This goes for all three, but is there actually a difference in vowel length between en-US/en-GB here? Because I don't believe there is?

@janbrasna
Copy link
Contributor

Actually, is there a preferred way how to call oneselves by the group/members?

If so, it would be also worth updating https://en.wiktionary.org/wiki/WHATWG#Pronunciation to show the preferred choice, or all acceptable forms.

@tylerjmorg
Copy link
Contributor Author

I'll address these questions based on my perceptive.

  1. I've based these pronunciations on the Cambridge Dictionary. So I'm unsure whether we should include multiple en-GB pronunciations which differ based on region. See a3.

  2. I agree, the vowel length should be changed especially since "WHAT" is grouped with WG phonetically in all three examples.

  3. Kind of tying into the first address. Since WHATWG is steered by Apple, Google, Microsoft, and Mozilla. Which the HQs are based in the U.S., we could just consider the en-US IPA as the primary pronunciation and leave other regions like en-GB to decide their own dialect (e.g., Welsh, Cockney, Yorkshire, etc).

  4. WHATWG is pronounced in multiple ways (e.g., I pronounce it as WHAT-DOUBLE YOU-GEE myself). So having just one way to pronounce WHATWG may lead to conflicts and unnecessary habit changes. However, the steering group may feel differently and that can be a discussion at a later time. I just think that think this PR wouldn't be the appropriate channel to discuss that big of a change.

Let me know what y'all think! Love to hear from you all! Should we ditch the en-GB section altogether? Do you think having IPA pronunciations may be unnecessary?

@annevk
Copy link
Member

annevk commented Aug 12, 2024

Let's see:

  • I like having the various pronunciations listed.
  • Adding IPA seems useful.
  • en-US might well be sufficient. All our other documentation is in en-US(-x-Hixie) so might as well stick with that here.
  • And yeah, while what-wee-gee is clearly superior, there's intentionally no right answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants