Template talk:IPA/Archive 5

Wrong characters
At least in my browser with the fonts I have installed, some IPA characters show up wrong. is supposed to be a handwritten g, i.e. identical to g in sans-serif fonts, but for me (at least, and presumably others as well) it shows up identical to γ (gamma from the Greek alphabet, not the IPA alphabet). Also, the inverted small capital R, is supposed to have the vertical stroke on the left, the rounded part on the lower right, and the diagonal in the upper right. But instead it's displayed with the vertical stroke on the right, the rounded part on the lower left, and the diagonal in the upper left. I don't know which font is creating these problems, but maybe we should stop using it. --Angr/comhrá 19:46, 14 Apr 2005 (UTC)


 * These characters look correct on my browser here - I'm using plain vanilla IE6 on Windows 2003. rossb 21:51, 14 Apr 2005 (UTC)

I'm using plain vanilla Netscape 7.2 on Windows XP. When I use IE it works. --Angr/comhrá 22:34, 14 Apr 2005 (UTC)


 * look fine to me in Opera and MSIE on WinXP. Jordi·✆ 23:47, 14 Apr 2005 (UTC)

Am I the only Wikipedian who uses Netscape? I even added ".IPA { font-family: Doulos SIL; Gentium; }" to my monobook.css page to force fonts that I know display the characters correctly, but it still doesn't work; those fonts don't show up. It's very confusing, because every IPA-containing sans-serif Unicode font I have installed on my computer (Arial Unicode, Lucida Sans Unicode, Microsoft Sans Serif) has those two characters correct when I use them on MS Word. --Angr/comhrá 11:16, 15 Apr 2005 (UTC)

That should be, with a comma. Try, or making the selector more specific, like. —Michael Z. 2005-04-15 15:22 Z 

Thanks, Michael! I added both "span" before and "!important" after and now it works. --Angr/comhrá 19:27, 15 Apr 2005 (UTC)


 * Glad it worked. Also, because of WP's caching, I find I can't test changes to monobook.css or monobook.js.  They'll just show up within a day or two.  —Michael Z. 2005-04-15 19:32 Z 


 * Well here it is over eight months later and I finally found out which font was causing all the trouble: MS Reference Sans Serif. I simply deleted it and now I don't need to specify anything in my monobook.css page and all the characters look right. Also, I'm using Mozilla Firefox now, not Netscape anymore. --Angr (t·c) 13:35, 31 December 2005 (UTC)

It's months later, and I'm still seeing the problem on some computers that run Firefox 1.5. Can we get the "!important" fix for the main monobook.css file on the site, so that individual users (who may not be CSS or even relatively computer literate) don't have to hack their systems to make it work? Dave 21:32, 30 April 2006 (UTC)

͈͈͈͈͈ ͈ ͈
Hi there, I don't really know what I'm talking about, but I was wondering if you can shed some light on this. At Korean language, there is this use of the template, <>, which does not render correctly on my browser (Firefox 1.5). Is it something you could fix perhaps? Cheers. PizzaMargherita 22:25, 21 April 2006 (UTC)


 * The character in question is combining diacritical mark, code point 0348, its appearance and usage are described at Korean language. Since you use Firefox, IPA does not affect your display. (It affect only MSIE.) If it does not render correctly on your browser, that would indicate that you don't have a font that supports this code point. If it displayed correctly, it would modify the preceding character: two vertial lines would appear under the &lt; (which may not be what the editor intended). --teb728 16:44, 8 June 2006 (UTC)

Please remove Bitstream Vera Sans from font family!
Esteemed Powers That Be,

I am using Windows XP and Internet Explorer 6. Normal text of Wikipedia gets displayed in Arial as specified, text in the IPA template gets displayed in Arial MS Unicode, which works perfectly (except for the bug with the tie bar, of course). Today I wanted to open a WordPerfect document and installed OpenOffice 2.0 for this purpose. Surprise! The most basic characters in IPA template now get displayed in a weird font with shading (each letter looks like a jpeg, sort of), and all other characters are rectangles! It turns out that in this template Bitstream Vera Sans has priority over Arial Unicode MS. Bitstream Vera Sans indeed looks like what Internet Explorer displays now, and it is devoid of special characters more "exotic" than Čč. It is not a Unicode font!!! It is even worse than plain Arial (which has, for example, basic Greek and Cyrillic)! Please remove it! *wince* *wail*

(The alternative, of course, would be that I and everyone else with both Windows and OpenOffice delete that font from their computers. Surely deleting it from the IPA template would make more sense.)

Yours truly

David Marjanović | david.marjanovic_at_gmx.at | 00:06 CEST | 2006/5/15

Addendum: These strangenesses do not happen with unicode and latinx. These templates do not have Bitstream Vera Sans, as shown in Template_talk:Polytonic. Accordingly, it's indeed Bitstream Vera Sans that is the culprit.

David Marjanović | david.marjanovic_at_gmx.at | 02:01 CEST | 2006/5/17

Hello? Anybody here? Is this page on nobody's watchlist?

David Marjanović | david.marjanovic_at_gmx.at | 00:13 CEST | 2006/5/27


 * There is no font specification in this template.--MarSch 10:21, 29 May 2006 (UTC)
 * Actually, yes there is (indirectly). class="IPA" triggers a stylesheet rule, which should be changed. Shinobu 20:27, 29 May 2006 (UTC)

I removed Bitstream Vera from the .Unicode and .IPA classed. I wonder how it crept in there in the first place? —Ruud 00:50, 11 June 2006 (UTC)


 * Here's how. --cesarb 04:17, 18 June 2006 (UTC)


 * Thank you very much!!!
 * David Marjanović | david.marjanovic_at_gmx.at | 16:32 CEST | 2006/7/17

Category
What exactly do we anticipate the category being used for? This is a meta-category and should properly be on the talk page, if a category is needed at all. But I would think what links here would be just as good. Christopher Parham (talk) 23:29, 1 August 2006 (UTC)
 * Never mind, I think. Christopher Parham (talk) 03:59, 4 August 2006 (UTC)

Māori version of the template made
mi:Template:IPA on the Māori wiki (mi), for use on Takuu, an article I am developing, and on upcoming linguistics-related articles. I have made it a protected template. I can't add the interwiki here since I am not a sysop on en. Cheers Kahuroa 05:17, 9 August 2006 (UTC)

Bambara Wikipedia
Is this be needed for the Bambara Wikipedia? Guaka 00:41, 29 August 2006 (UTC)

Linking, again
Hi, I propose a new template to link to articles using an IPA anchor. A preliminary version is available at. It uses the "nounderlines" class to stop underlines from being displayed.

Usage:


 * Works with slashes
 * And brackets
 * And brackets

You can see Elder Futhark to see why this might be needed. --Kjoonlee 07:13, 20 October 2006 (UTC)
 * But what should we call this template? Template:IPA2 is already taken and IPA3 isn't very easy to remember. Template:IPA link, perhaps?
 * Another reason this sort of template might be needed: Northern cities vowel shift can link to the vowels directly. --Kjoonlee 09:16, 21 October 2006 (UTC)

Doh. Template isn't really needed, since class="IPA" is now sufficient to suppress underlines and syntax does the job. --Kjoonlee 09:38, 21 October 2006 (UTC)

Yet more linking: a proposal
I have an idea which I call "IPA Quickhelp templates" for making IPA symbols more comprehensible, like this: ʒ (try rolling over that with your mouse). That is,. Currently it doesn't work with popups, I'm hoping to fix that. This is an improvement over the "linking" mentioned above for two reasons: To discuss the concept, go here: template talk:Ʒ.--Homunq 04:38, 7 December 2006 (UTC)
 * 1) The tooltip text that it shows is a redirect with a non-jargon name, so the average person who doesn't know all the IPA symbols (I consider myself savvy and I know maybe half by sight) and who doesn't know what "fricative" means can figure it out by just holding the mouse over each symbol in turn.
 * 2) The process of adding an alias is handled by a template and so requires much less typing and thought and linkchecking.