This template was considered for deletion on 15 October 2023. The result of the discussion was "no consensus". |
To help centralise discussions and keep related topics together, all language-specific IPA template talk pages redirect here. |
Template:IPA-all is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use ((edit template-protected)) to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. This template does not have a testcases subpage. You can create the testcases subpage here. |
Linguistics: Phonetics Template‑class | ||||||||||
|
@Nardog: "Swiss German" isn't the correct label, it should read "Swiss Standard German". The same seems to apply to the Austrian variety. Kbb2 (ex. Mr KEBAB) (talk) 14:11, 8 November 2019 (UTC)
de
, deu
, and ger
refer to the same language (see ISO 639#Relations between the parts), namely Standard German, or German for short. The latter short name also occurs in other language names, especially gsw
"Swiss German", nds
"Low German", pdc
"Pennsylvania German", gsg
"German Sign Language", sgg
"Swiss-German Sign Language" (though not in asq
"Austrian Sign Language"). As a consequence the labels "German(y) German" and "Austrian German" seem sufficient for national varieties of Standard German (de-DE
and de-AT
), but "Swiss German" is the label for gsw
, so de-CH
cannot be shortened to that and must be labelled "Swiss Standard German". Love —LiliCharlie (talk) 20:43, 8 November 2019 (UTC)
A discussion at Wikipedia talk:WikiProject Linguistics#IPA-x templates could use your input. --Gonnym (talk) 11:39, 22 January 2020 (UTC)
The current IPA templates, such as Template:IPA-es, appear to unconditionally generate empty paired <small></small>
tags for many outputs, which leads to redundant tags (and appears to be causing me downstream errors when I happen to use them via the article summary API; I am adding an ad hoc fix, but it'd be better to fix this upstream for all users).
For example on Yerba mate, the code from Spanish ((IPA-es|ˈʝeɾβa ˈmate|))
generates from Spanish <small></small><span title="Representation in the International Phonetic Alphabet (IPA)" class="IPA"><a href="/wiki/Help:IPA/Spanish" title="Help:IPA/Spanish">[ˈʝeɾβa ˈmate]</a></span>;
.
<small></small>
is undesirable output here, as it's meaningless and potentially problematic, and appears to be mandated by the template implementation doing the conditional inside rather than outside the tags (<small>((#switch...))</small>
- but what if the switch yields nothing?). --Gwern (contribs) 02:52 5 January 2021 (GMT)
Shouldn't these templates be emitting HTML like
<span lang="de-fonipa" title="Representation in the International Phonetic Alphabet (IPA)" class="IPA" multilinks-noscroll="true"> <a href="/wiki/Help:IPA/Standard_German" title="Help:IPA/Standard German" multilinks-noscroll="true">[ˈbʁeːgɛnt͡s]</a></span>
?
I mean, there should be lang="xx-fonipa"
on either the span or the a HTML tags.
--Error (talk) 15:13, 10 May 2021 (UTC)
lang="(({ISO|((#invoke:string|replace|((ROOTPAGENAME))|^(IPA%-)([a-z][a-z][a-z]?)|%2|plain=false))))}-fonipa"
should do the trick, e.g. for ((IPA-fr)) giving lang="fr-fonipa"
. Local overwriting for (the only such non-ISO-code case?) ((IPA-cadia)) would be needed though. --Marsupium (talk) 09:45, 9 June 2022 (UTC)
((ROOTPAGENAME))
will always give you the name of the page the template is transcluded in, not of the template that directly calls the template. Nardog (talk) 13:59, 9 June 2022 (UTC)
lang="(({lang|und))}-fonipa"
in ((IPA)) and specify the language in each IPA-xx. Nardog (talk) 21:34, 9 June 2022 (UTC)
lang="und-fonipa"
as you proposed is the best solution that doesn't over-complicate template code. Is there any admin or template editor around that could make the small required edits for ((IPA)) and ((IPA-all))? Best, --Marsupium (talk) 10:55, 17 June 2022 (UTC)
((#if:(({lang|))}|(({lang))}|und))
" looks like more complex code with the same result as the "(({lang|und))}
" you had proposed above. Or am I missing some wiki syntax details (again)? Best, --Marsupium (talk) 14:32, 17 June 2022 (UTC)
lang="-fonipa"
in case |lang=
is given but empty. Nardog (talk) 14:38, 17 June 2022 (UTC)class="IPA"
directly in the source, which should be fixed. Nardog (talk) 14:49, 17 June 2022 (UTC)There seems to be no way to override the small font size, so using the template in an infobox where the font is already reduced violates thr MOS. There should be a parameter to specify 100% font size. MB 02:19, 25 October 2021 (UTC)
This edit request to Template:IPA-es has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
May we please add a function where it could make:
((IPA-es|tu|mex))
→ Mexican Spanish: [tu]Similar to what is already done:
((IPA-es|tu|am))
→ American Spanish: [tu]Thank you for your assistance, please do ping me, waddie96 ★ (talk) 19:38, 9 May 2022 (UTC)
((edit template-protected))
template. Nardog (talk) 22:35, 10 May 2022 (UTC)Can you please add templates for the variationa of Spanish such as Mexican Spanish? Jumark27 (talk) 17:37, 24 August 2022 (UTC)
This templates use of no wrap spaces causes formatting issue on mobile. - LCU ActivelyDisinterested ∆transmissions∆ °co-ords° 21:00, 11 June 2022 (UTC)
@Nardog: Hey Nardog. Please, revert all the tagging of IPA to specific language, like in this case. I already reverted the ((IPA-arz)) one. The reason is as follows:
Thanks. --Mahmudmasri (talk) 22:11, 26 June 2022 (UTC)
Tracing your edits, I saw the following comment:
add lang attribute, as discussed on talk
I haven't seen any discussion on the tagging. Where is it? BTW, on Wiktionary, the IPA text is not tagged, rather the word "(key)" is linked to the corresponding language pronunciation page. --Mahmudmasri (talk) 22:31, 26 June 2022 (UTC)
arz-fonipa
: [foo]arz-Latn-fonipa
: [foo]Latn
. Let me know if the problem persists. Nardog (talk) 20:44, 27 June 2022 (UTC)
arz-Latn-fonipa
: [foo]) renders "normally" to me. There is just one concern:
((IPA|[foo]))
should render like [foo].IPA
should apply as long as it's not overridden by other styles with higher specificity. (English Wikipedia has long abandoned adding styles to .IPA
.) Nardog (talk) 22:47, 27 June 2022 (UTC)
span[lang|=arz-Latn]
and span[lang|=arz]
are triggered which annul the .IPA
specifications, which moves back to the first point: adding a language tag to the IPA text denies the IPA specifications from being normally used in case the language specific codes are already stylized. --Mahmudmasri (talk) 00:13, 28 June 2022 (UTC)span[lang|=arz-Latn]
is there to stop span[lang|=arz]
from being used in transliterated texts, but now the former is stopping all IPA styles. --Mahmudmasri (talk) 00:18, 28 June 2022 (UTC)
:not(.IPA)
, thought this is obviously not a really generalizable solution. @Error and Marsupium: Perhaps should we use simply und-fonipa
regardless of the transcribed language? I want to know what's best from the accessibility point of view. Nardog (talk) 22:36, 28 June 2022 (UTC)
:not(.IPA)
to span[lang|=arz-Latn]
and span[lang|=arz]
, for example?und
is fine. But we're not going to abandon it just because it ruined one person's CSS.span[lang|=arz-Latn]:not(.IPA)
. Nardog (talk) 02:07, 3 July 2022 (UTC)On mobile view, this is the only template that actually displays labels at a reduced size, probably because of a different html syntax. Can anyone change “85%” to “small” for consistency with all other templates? Or alternatively do the other way round. 〜イヴァンスクルージ九十八[IvanScrooge98](会話) 07:23, 3 September 2022 (UTC)
Hi, I am not sure if this is the right place to ask, but could someone (who is able to do so without breaking anything) add an IPA template for the language Gronings (ISO 639-3: gos)? The name should be Template:IPA-gos, I guess. I would like to add transcriptions in that language to some articles (e.g., places in the region where the language is spoken). It would be great if I could use a specific template for that, rather than the catch-all template. There is no dedicated key page (yet), but the article on the language has a phonology section, so I would suggest to use that as the page that the transcriptions link to. Thanks in advance! Isoglosse (talk) 16:22, 28 March 2023 (UTC)
Despite it being almost impossible to narrowly transcribe Irish words and phrases, the IPA-ga template uses [] square brackets, which are intended for narrow transcription. If you read Help:IPA/Irish, you'll see that the transcription standards used here are based on broad transcription (which uses // forward slashes). I intent to fix the template to more accurately represent this (by simply replacing the square brackets with forward slashes), but I am posting here to ask: Is there any underlying reason as to why this should not be done? Alpha2 5232 (talk) 08:40, 31 May 2023 (UTC)
If you wish to change those conventions, bring it up for discussion on the key's talk page. Creating transcriptions unsupported by the key or changing the key so that it no longer conforms to existing transcriptions will confuse readers.So propose your suggestions at Help talk:IPA/Irish before editing the key or any transcription. Nardog (talk) 08:51, 31 May 2023 (UTC)
I noticed that Persian رد (radd) has the Classical pronunciation of /ɾaðd/ and I don't think this can be correct. Exarchus (talk) 22:01, 9 June 2023 (UTC)
There is a disambiguation page for American Spanish as it could refer to Spanish language in the United States or Spanish language in the Americas. In which sense is used in ((IPA-es|tu|am))
? As a native Rioplatense Spanish adding sound files, should I use the am
value?
1ucian0 (talk) 19:53, 2 September 2023 (UTC)
am
no longer exists btw, the equivalent now is ((IPA|es-419|...))
, which produces "Latin American Spanish pronunciation: [...]". Nardog (talk) 22:13, 10 January 2024 (UTC)