Template talk:IPA-en

This template was considered for deletion on 15 October 2023. The result of the discussion was "no consensus".

This template is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.Wikipedia HelpWikipedia:Help ProjectTemplate:Wikipedia Help ProjectHelp articles

Linguistics: Phonetics

	Linguistics portal This template is within the scope of WikiProject Linguistics, a collaborative effort to improve the coverage of linguistics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinguisticsWikipedia:WikiProject LinguisticsTemplate:WikiProject LinguisticsLinguistics articles
	This template is supported by Phonetics Task Force.

Archives

Archive 1

Template talk:Pron-en/Archive 1

Problems with wrapping

Both {{IPA-en|ˈxxx}} and {{IPA-en|ˈxxx|}} have problems with wrapping. Open page Template_talk:IPA-en/wrapping and resize it to see the problems.

Using # to represent a line break, on Chrome 12, for {{IPA-en|ˈsætɒnəˈwɔːl|}}, I see

/#ˈsætɒnəˈwɔːl/ -- wrong
/ˈsætɒnə#ˈwɔːl/ -- maybe acceptable

Presumably the problem is that Chrome is mishandling the IPA stress sign (ˈ) (reported to Chrome issues); is there any reasonable workaround? Setting word-break within .IPA css is probably going to break other things....

I don't see that problem on Internet Explorer 9 and Firefox 4.0.1, but for {{IPA-en|ˈsætɒnəˈwɔːl}}, on all three browsers, I see:

English#pronunciation: -- OK

but never

English pronunciation:#/ˈsætɒnəˈwɔːl/ -- should break here

so the next break is

English pronunciation: /ˈsætɒnəˈwɔːl/# and

This second problem should be easy to fix: there is an   after "English pronunciation:" in the IPA-en template -- this should be a normal (breaking) space. If others agree, an administrator is going to need to change it. --Macrakis (talk) 21:51, 11 June 2011 (UTC)[reply]

I've changed the   to   so now it's a normal breaking space. I don't think we can do anything about the other problem. —Angr (talk) 22:10, 11 June 2011 (UTC)[reply]

Mouseover help

Hi, is there any reason why this template (IPA-en) does not automatically have the mouseover help feature of IPAc-en? The mouseover feature is incredibly useful for the majority of us who are not very familiar with IPA, yet most articles do not seem to employ it? Why is that? It seems a waste... 81.159.111.3 (talk) 01:43, 7 June 2012 (UTC)[reply]

Yes, the old template was not designed with it. You can help by converting them over. There are only about 6,000 of them ... :) — kwami (talk) 02:52, 7 June 2012 (UTC)[reply]

But wouldn't it be easier just to implement the mouseover thing in the "IPA-en" template? 86.183.3.0 (talk) 10:29, 7 June 2012 (UTC)[reply]

Edit request on 8 November 2012

This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Rd WP:IPA for English to Help:IPA for English. — kwami (talk) 08:31, 8 November 2012 (UTC)[reply]

Done — Mr. Stradivarius ^{(have a chat)} 10:14, 8 November 2012 (UTC)[reply]

Make like IPAc using Lua?

How about using something like Module:IPAc to make this template function like {{IPAc-en}}, except without requiring every character or set of characters to be a separate argument? --Yair rand (talk) 07:49, 22 July 2013 (UTC)[reply]

Automatic inclusion in Requests for audio pronunciation (English) category

From what I can tell, Requests for audio pronunciation (English) is pretty poorly populated - I started populating by hand, but I'm thinking that since audio pronunciations are usually added to the IPA-en template, we could automatically check for the presence of an audio file and, if so, include the article in the category. For edge cases where having an audio pronunciation is, for some reason, not desirable, we could add a `no-audio` parameter to prevent inclusion. Is there some objection to this? Is Category:Requests for audio pronunciation (English) the right place to go, or should we make another new (also hidden) category that is automatically populated, like, Category:Pages with IPA-en templates without audio pronunciation? 0x0077BE [^talk/_contrib] 18:31, 2 November 2014 (UTC)[reply]