Jump to content

Template talk:IPA

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

The redirect T:IPA has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2023 December 27 § T:IPA until a consensus is reached. Queen of Hearts ❤️ (she/they 🎄 🏳️‍⚧️) 00:43, 27 December 2023 (UTC)[reply]

Slashes and brackets

[edit]

Could the template detect if the text is surrounded by / / or [ ] to not add them itself? Currently we can have ugly things like /[rɪd]/ and French pronunciation: [/fʁɑ̃sɛ/]. -- Error (talk) 17:10, 22 May 2024 (UTC)[reply]

As long as it's in the guide-linking mode (i.e. the first parameter is a language code), it should use brackets except for English, per MOS:PRON. Otherwise it could link a phonemic transcription to a phonetic key. Nardog (talk) 07:40, 23 May 2024 (UTC)[reply]

Would a div tag option be useful?

[edit]

Recently, an editor used this template to wrap a block of content that was already wrapped in <poem>...</poem> tags, which caused a Linter "span tag wrapping a div tag" error. I reverted because I didn't see a way for this template to emit div tags, and I didn't know if that would be useful.

I added a test case, since removed because I don't want to clutter up the Linter error reports, showing how the template was used in that case. If it would be useful and in conformity with the purpose of this template, a |div=yes option could presumably be added to the module code; that option would use div tags instead of span tags in this template's output. We inserted a similar option into {{Collapsed infobox section begin}} to fix Linter errors that cropped up in some situations. – Jonesey95 (talk) 22:09, 28 May 2024 (UTC)[reply]

You can just use {{IPA}} inside <poem>...</poem> instead of the other way around. Nardog (talk) 00:57, 29 May 2024 (UTC)[reply]

IPA for Brazilian Portuguese

[edit]

inputting {{IPA|pt-BR|...}} generates a text in incompatible fonts (seemingly with HTML sans-serif when I inspected it), when the same template with {{IPA|pt|...}} uses default fonts. Juwan (talk) 14:08, 1 August 2024 (UTC)[reply]

bumping and updating that this happens with every language with a country or region tag added. Juwan (talk) 23:51, 11 September 2024 (UTC)[reply]
As far as I can tell from reading IETF language tag, this is a bug on the browser's part. Nardog (talk) 00:52, 12 September 2024 (UTC)[reply]
Apparently it needs to be pt-Latn-BR-fonipa instead of pt-BR-Latn-fonipa. I'll deploy the fix once other pending bugs are ironed out. Nardog (talk) 05:34, 26 December 2024 (UTC)[reply]
@Nardog oh that's annoying. just to note that this is not actually a bug for just Brazilian Portuguese after all but for all [language code] + [country code] codes. good luck fixing that! Juwan (talk) 14:00, 26 December 2024 (UTC)[reply]
I've already fixed it in the sandbox, I'm just holding off on deploying it to reduce the number of times the job queue is flooded. Nardog (talk) 17:34, 26 December 2024 (UTC)[reply]
Deployed. Nardog (talk) 10:24, 27 December 2024 (UTC)[reply]
Category:Pages with Mari IPA is suddenly empty and it displays an error message: "Error: language code for "Mari" not found. Please see Template talk:IPA for assistance.". Should its history be merged into Category:Pages with Mari (Russia) IPA or is this a separate issue? plicit 11:12, 27 December 2024 (UTC)[reply]
It's one of the things fixed. Just deleting it is fine I think, as the whole page is generated by the template. I've tagged it with C4. Nardog (talk) 11:36, 27 December 2024 (UTC)[reply]