(Go: >> BACK << -|- >> HOME <<)

Jump to content

Talk:International Phonetic Alphabet chart: Difference between revisions

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Content deleted Content added
→‎A few questions: new section
Line 15: Line 15:
:It's an issue with the font. Try Noto Serif (or simply <code>font-family: serif;</code>) and see if it works. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 10:30, 5 July 2020 (UTC)
:It's an issue with the font. Try Noto Serif (or simply <code>font-family: serif;</code>) and see if it works. [[User:Nardog|Nardog]] ([[User talk:Nardog|talk]]) 10:30, 5 July 2020 (UTC)
:: At this point Noto Sans fonts can hardly be recommended, for the current release versions still contain several bugs that concern IPA: [https://github.com/googlefonts/noto-fonts/issues/1265 badly scaled glyphs for modifier letters], [https://github.com/googlefonts/noto-fonts/issues/1392 wrong glyphs for contour tones], and [https://github.com/googlefonts/noto-fonts/issues/1603 ineffective lookups for Greek letters in phonetic notation]. The latter bug is also a reminder for our template programmers that it is not enough to add <code>.IPA</code> class markup to our source text. In order to prevent smart fonts (not only Noto fonts) from selecting glyphs for Greek when specially designed glyphs for IPA are available a valid [[IETF language tag]] should be added, probably <code><nowiki><span lang="und-Latn-fonipa">...</span></nowiki></code> (undefined language; Latin script; IPA). Note that the Unicode standard considers IPA a subset (writing system) of the Latin script though a few Greek letters are used, and see [https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry] for the subtag definitions. <small>[[Wikipedia:WikiLove|Love]]</small>&nbsp;—[[:commons:User:LiliCharlie|LiliCharlie]]&nbsp;<small>([[User talk:LiliCharlie|talk]])</small> 11:15, 5 July 2020 (UTC)
:: At this point Noto Sans fonts can hardly be recommended, for the current release versions still contain several bugs that concern IPA: [https://github.com/googlefonts/noto-fonts/issues/1265 badly scaled glyphs for modifier letters], [https://github.com/googlefonts/noto-fonts/issues/1392 wrong glyphs for contour tones], and [https://github.com/googlefonts/noto-fonts/issues/1603 ineffective lookups for Greek letters in phonetic notation]. The latter bug is also a reminder for our template programmers that it is not enough to add <code>.IPA</code> class markup to our source text. In order to prevent smart fonts (not only Noto fonts) from selecting glyphs for Greek when specially designed glyphs for IPA are available a valid [[IETF language tag]] should be added, probably <code><nowiki><span lang="und-Latn-fonipa">...</span></nowiki></code> (undefined language; Latin script; IPA). Note that the Unicode standard considers IPA a subset (writing system) of the Latin script though a few Greek letters are used, and see [https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry] for the subtag definitions. <small>[[Wikipedia:WikiLove|Love]]</small>&nbsp;—[[:commons:User:LiliCharlie|LiliCharlie]]&nbsp;<small>([[User talk:LiliCharlie|talk]])</small> 11:15, 5 July 2020 (UTC)

== A few questions ==

Would it be more correct to add tie-bars to all the affricates? If so, does anyone know how to do that?

I noticed that most of the cells have both a voiced and unvoiced symbol, with the voiceless diacritic being used if a full letter is not available. However, a few symbols (I found ⱱ̟ ⱱ ɾ̼ ɱ n̼ ɴ, there may be others) are missing their voiceless counterparts, and at least one voiceless symbol (ʈɭ̊˔) is missing its voiced counterpart. Is this intentional?

A few cells which are not shaded (many in the linguo-labial section, and some in the uvular section) are empty. Is this intentional?
Would it make sense to have specific symbols for all the dental, alveolar, and post-alveolar sounds, using diacritics, to better match the specificity provided for fricatives and affricates? Or is there some theoretical, practical, or other reason to reserve such specificity to the fricatives and affricates?

Thanks for reading!
[[User:JonathanHopeThisIsUnique|JonathanHopeThisIsUnique]] ([[User talk:JonathanHopeThisIsUnique|talk]]) 09:07, 26 September 2020 (UTC)

Revision as of 09:07, 26 September 2020

Add Noto Sans to font stack?

Most of the dotted circles in the table with diacritics show up as crossed boxes on my Android phone. I'm not sure why since it doesn't affect all of them, but I believe that adding Noto Sans to the font stack for whatever style those templates apply should fix the issue. BPJ (talk) 09:41, 5 July 2020 (UTC)[reply]

There is no "font stack"; the phonetic symbols differ from other text only insofar as they are given the .IPA class. You may specify a font for the class in your custom CSS (see Template:IPA for more). Nardog (talk) 09:58, 5 July 2020 (UTC)[reply]

I just tried and it appears to not work. I reset the cache but no improvement. BPJ (talk) 10:01, 5 July 2020 (UTC)[reply]

I see now that the problem appears with combining marks but not with modifier letters so probably a rendering issue. BPJ (talk) 10:06, 5 July 2020 (UTC)[reply]

It's an issue with the font. Try Noto Serif (or simply font-family: serif;) and see if it works. Nardog (talk) 10:30, 5 July 2020 (UTC)[reply]
At this point Noto Sans fonts can hardly be recommended, for the current release versions still contain several bugs that concern IPA: badly scaled glyphs for modifier letters, wrong glyphs for contour tones, and ineffective lookups for Greek letters in phonetic notation. The latter bug is also a reminder for our template programmers that it is not enough to add .IPA class markup to our source text. In order to prevent smart fonts (not only Noto fonts) from selecting glyphs for Greek when specially designed glyphs for IPA are available a valid IETF language tag should be added, probably <span lang="und-Latn-fonipa">...</span> (undefined language; Latin script; IPA). Note that the Unicode standard considers IPA a subset (writing system) of the Latin script though a few Greek letters are used, and see https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry for the subtag definitions. Love —LiliCharlie (talk) 11:15, 5 July 2020 (UTC)[reply]

A few questions

Would it be more correct to add tie-bars to all the affricates? If so, does anyone know how to do that?

I noticed that most of the cells have both a voiced and unvoiced symbol, with the voiceless diacritic being used if a full letter is not available. However, a few symbols (I found ⱱ̟ ⱱ ɾ̼ ɱ n̼ ɴ, there may be others) are missing their voiceless counterparts, and at least one voiceless symbol (ʈɭ̊˔) is missing its voiced counterpart. Is this intentional?

A few cells which are not shaded (many in the linguo-labial section, and some in the uvular section) are empty. Is this intentional? Would it make sense to have specific symbols for all the dental, alveolar, and post-alveolar sounds, using diacritics, to better match the specificity provided for fricatives and affricates? Or is there some theoretical, practical, or other reason to reserve such specificity to the fricatives and affricates?

Thanks for reading! JonathanHopeThisIsUnique (talk) 09:07, 26 September 2020 (UTC)[reply]