![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | Archive 11 | Archive 12 | Archive 13 |
Template {{
Unicode}}
will be deleted due to being obsolete. As XP is no longer supported, its font declararion (targeting XP) will also be removed. That begs the question: is the current font declaration for IPA (also targeting XP) still necessary, or can they be removed as well? Note this would only impact XP users, and the template itself is not under discussion; only the font. -- [[
User:Edokter]] {{
talk}}
18:57, 11 April 2016 (UTC)
-- [[
User:Edokter]] {{
talk}}
18:02, 25 April 2016 (UTC)§ Conversion to IPA says
That's wrong. French ⟨j⟩ represents the voiced postalveolar fricative [ ʒ], but IPA ⟨j⟩ represents the voiced palatal approximant.
And for that matter, where's the conversion chart for the "natural spelling"? It sure isn't at Template:IPAc-fr/doc (where I'm also raising this question) or Help:IPA for French. How do you get /ʒ/ in {{ IPAc-fr}}?
Cross-referencing from WikiProject Linguistics.
Please {{Ping}} me to discuss. -- Thnidu ( talk) 18:13, 25 April 2016 (UTC)
I've created this module. It behaves the same way as this template when only one parameter is used, but if a language code is added to the first parameter, it creates a link to that language's help page – for instance, {{IPA/sandbox|fr|/ɛɡ.zɑ̃pl/}}
becomes
/ɛɡ.zɑ̃pl/. The list of help pages in the module isn't complete, but once it is, I think this module could be used to give this template a bit more functionality. —
Eru·
tuon
02:11, 17 October 2016 (UTC)
Finished the list. All ISO 639-1 and ISO 639-3 language codes for the languages that have IPA keys are included. — Eru· tuon 04:24, 17 October 2016 (UTC)
Hi Wikipedians, Would it be possible to render a /g/ as a /ɡ/ (the correct one) in the template for convenience?? Anyone who listens is the best!!😃 Thanks. — Awesomemeeos ( talk) 06:37, 7 July 2016 (UTC)
{{IPA|[g]}}
→ [g]{{IPA/sandbox|[g]}}
→ [ɡ]Kazi Zafar Ahmed is displaying "Lua error in Module:IPAc-en at line 13: attempt to index local 's' (a nil value)". That appears to be a result of recent edits to this template, although possibly the error is old wikitext in the article. Would someone please work out what is going on. Johnuniq ( talk) 06:09, 25 July 2017 (UTC)
if args1 and string.lower ...
to check if the parameter in question exists before trying to use string functions on it. —
Eru·
tuon
16:14, 25 July 2017 (UTC)Statement of the problem
Not even sure that this is correct place to ask this.... My immediate concern is {{ IPA-fr}} and {{ IPA-mg}}, but this a situation endemic to all "IPA-xx" templates where "xx" is some language code. Since {{ IPA-fr}} etc. call this template ({{ IPA}}) this seems like a good centralized place to discuss this.
{{ IPA-fr}} sends a string ("tananaʁiv" for example) to ({{ IPA}}. Well not exactly. If I specify the the string, "tananaʁiv", it actually sends "tananaʁiv". Note the brackets. But I don't want the brackets.
We could edit {{ IPA-fr}} and {{ IPA-mg}} to solve my immediate problem (I can't do it as I lack the chops to do it correctly). But if we did that it would leave {{ IPA-fr}} and {{ IPA-mg}} being different from all the other "IPA-xx" templates, which is not good. We'd have to change all the "IPA-xx" templates.
I could, in {{
IPA-fr}} and {{
IPA-mg}}, add nobrackets=|
to the switch statement (that is, it's treated like a blank parameter), then in the call use "nobrackets" (if present) to send "string" rather than "[string]" to the {{
IPA}}. This seems kludgy.
I guess better would be to send a parameter to here and then strip the brackets here... I guess maybe even easier would be never send them, and then add the brackets here in the absence of a param telling it not to...? Above my pay grade.
Or I may be missing a simple solution that's right there. If so, then Bob's your uncle.
But if not, what is our best way forward here?
Specific instance showing why this is a problem
The article Antananarivo begins thus:
Antananarivo ( /ˌæntəˌnænəˈriːvoʊ/ or /ˌɑːntəˌnɑːnəˈriːvoʊ/; [1] Malagasy pronunciation: [antananaˈrivʷ]), then temporarily French Tananarive ( /təˌnænəˈriːv/ [2] or /ˌtænənəˈriːv/; [3] French pronunciation: [tananaʁiv]), also known by its French colonial shorthand form Tana, is the capital and largest city of Madagascar.
This is objectively horrible on several levels. So what we want to do is change the lede sentence to something that actual humans can read:
Antananarivo, called Tananarive in French and also known by its colonial shorthand form Tana, is the capital and largest city of Madagascar.
and then later in the article body be like
The English pronunciation of Antananarivo is /ˌæntəˌnænəˈriːvoʊ/ or /ˌɑːntəˌnɑːnəˈriːvoʊ/; [4]. The Malagasy pronunciation is [antananaˈrivʷ], and the pronunciation of the old French name Tananarive is /təˌnænəˈriːv/ [5] or /ˌtænənəˈriːv/ [6] in English and [tananaʁiv] in French.
but as you can see the brackets are carried into the text by {{ IPA-fr}} and {{ IPA-mg}}, and we want to strip them. I mean, they're not horrible there, but they don't belong either, and it's non-excellent to have them.
(I do not know why "tananaʁiv" and "antananaˈrivʷ" are presented to the reader instead of the more atomized individual sounds I usually see. I assume that it's because these are non-English pronunciations and that is proper and necessary and why we have {{ IPA-fr}} etc. rather than just using {{ IPA}}.)
So now what? Herostratus ( talk) 20:12, 6 October 2017 (UTC)
![]() | This
edit request to
Template:IPA has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The IPA-tagging function in Module:IPA is ready to be deployed widely. It creates the exact same content as the existing template, but also changes regular g to IPA ɡ. Please replace the content of the template with the following:
{{#invoke:IPA|tag}}
— Eru· tuon 22:01, 19 June 2017 (UTC)
{{
IPA}}
to the output of {{
IPA/sandbox}}
, which currently uses {{#invoke:IPA|tag}}
. The first example differs only because it changes the g
to ɡ
. —
Eru·
tuon
20:55, 21 June 2017 (UTC)
|answered=
back to n
. --
Izno (
talk)
21:39, 21 June 2017 (UTC)
{{
IPA/sandbox}}
with the actual Lua function in the module, to prevent it changing if someone decides to use the sandbox template for something else. —
Eru·
tuonSee the template test cases at
Template:IPA/testcases. Output of the sandbox template {{
IPA/sandbox}} is identical to the output of {{
IPA}}, except that the non-IPA symbol g
is changed to ɡ
. —
Eru·
tuon
21:28, 22 June 2017 (UTC)
I have reverted the change because an error was reported at {{
IPA-hu}}. It looks like the "g" in the link to
Help:IPA for Hungarian was transformed to "ɡ" (the IPA symbol) as a result of the change. We should fix it.
Nardog (
talk)
22:40, 22 June 2017 (UTC)
g
that is not inside HTML tags or templates or targets of piped links, instead of replacing it. Should I do that? —
Eru·
tuon
17:33, 23 June 2017 (UTC)
g
's inside {{...}} that are supposed to appear in the outcome and ones that are not. Sorry if I'm preaching to the choir.
Nardog (
talk)
17:45, 23 June 2017 (UTC)
{{IPA/sandbox|[[g]]}}
adds the category, but {{IPA/sandbox|g}}
doesn't. I don't think it's ready.
Nardog (
talk)
18:17, 23 June 2017 (UTC)
Does using the right kind of "g" really justify a whole new lua module? Oppose as unnecessary over-complication {{3x|p}}ery ( talk) 19:28, 21 June 2018 (UTC)
If the template ends up being at the end of a line of rendered text and the stress falls on the first syllable of the word, the line break may be inserted between the ⟨/⟩ and ⟨ˈ⟩. For example:
Instead of:
Can someone please fix this? Esszet ( talk) 20:32, 9 August 2018 (UTC)
{{nowrap|{{IPA|/ˈbˠaːiːxt̪ˠ/}}}}
. Note this would also prevent breaking at spaces. If you still want the notation to break at a space, write e.g. {{IPA|{{nowrap|/ˈxxx}} yyy/}}
or {{nowrap|{{IPA|/ˈxxx <wbr />yyy/}}}}
. Inserting {{
wj}}
after /
, or before ˈ
or ˌ
, as in {{IPA|/{{wj}}ˈxxx{{wj}}ˌyyy/}}
, is yet another option.You know that the IPA transcription for “Brasil” is [bɾaˈziw], right? I couldn’t change it because the template is protected. Ten Islands ( talk) 15:31, 7 September 2018 (UTC)
Do we have a page, like Wikipedia:Graphics Lab, for requesting IPA transcriptions? There's nothing mentioned on Help:IPA, and a query on WP:VPM came up with nothing concrete. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:20, 18 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)
![]() | This
edit request to
Template:IPA has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change the full protection to semi-protection. I want to edit the doc page. 14bauhr ( talk) 18:13, 22 April 2020 (UTC)
{{
edit template-protected}}
is usually not required for edits to the documentation, categories, or interlanguage links of templates using a
documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage.
Izno (
talk)
22:45, 22 April 2020 (UTC)In wikt:Template:IPA, the template parameters are:
|1=
language code|2=
, |3=
, |4=
... pronunciation(s)|qualN=
qualifier for pronunciation N|nN=
reference note for pronunciation N|nocount=1
disable syllable counting|sort=
manual sort keyBecause w:Template:IPA has only one parameter max, and Wiktionary's has two min, these are completely compatible.
Therefore, please merge them, to keep current behavior if 1 parameter and use Wiktionary's behavior if >1. This would help when copying content from Wiktionary. Sai ¿? ✍ 11:22, 15 March 2021 (UTC)
I was expecting the {{lang-xx}} templates to produce HTML like <span lang="en-fonipa"></span>
to tag the text as English language transcribed as IPA.
Can you modify the template to emit lang tags?
--
Error (
talk)
00:29, 1 May 2021 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Per
MOS:SMALLTEXT it says Reduced or enlarged font sizes should be used sparingly, and are usually done with automated page elements such as headings, table headers, and standardized templates
. Furthermore, it states that these styles should not be used in infoboxes and other templates that already reduce size. I note that a lot of {{
IPA}} templates are used in the in the opening sentences and across infoboxes when introducing a non-English subject. Please can the automated formatting be removed to comply with the relevant MOS? >>
Lil-unique1 (
talk) —
18:37, 15 July 2022 (UTC)
class="IPA"
in the span tag that governs that. So if you need a larger font, all you need to do is adjust the font size in your browser. You can also change to a different font if you like. Just read the
Usage section on the template page. Hope this helps!
P.I. Ellsworth ,
ed.
put'r there
20:09, 15 July 2022 (UTC)
Italian pronunciationin small. Prose underneath a section header should be in one size as this aids readability whether you have a disability or not. >> Lil-unique1 ( talk) — 23:23, 15 July 2022 (UTC)
class="IPA"
to something else. That would then have a
domino effect for
several other applications. So it appears that a
consensus would be needed, and that means finding a centralized place to
discuss it such as
WT:LANG or
WT:IPA or even
WT:ACCESS. Not sure which venue would provide the best turnout of editors; however, placing neutral notices of where the discussion is being held can be very helpful.
P.I. Ellsworth ,
ed.
put'r there
16:15, 16 July 2022 (UTC)
IPA
class has nothing to do with the label size. That code is in
IPA-xx templates, not {{
IPA}}.
Nardog (
talk)
17:58, 16 July 2022 (UTC)
Jonesey95, you have fixed several
MOS:SMALLTEXT issues before. I came here after seeing the infobox in
Isa (name) and having to squint to read it. There is discussion above about needing consensus to change anything. But
MOS:SMALLTEXT is clear on this. The real issue is that these templates are commonly used in prose where there is no problem (e.g.
Najd). So isn't the solution that we need a |size=100%
parameter as in {{
post-nominals}} so the default of small can be overwritten only when needed, as in infoboxes?
For reference, the doc at that template says Font size: The optional |size= parameter allows for the size of the text, as a percentage, to be changed from the template's default of 85%. As per MOS:FONTSIZE, this must be added when the template is used in infoboxes (it should be set to 100%), because infoboxes already use size-reduced text.
That is exactly the same as here. It even says must; I think the small text must be fixed here also.
MB
00:40, 30 September 2022 (UTC)
<small>...</small>
tags in {{
IPA-ar}} and its siblings, not by {{
IPA}}. This IPA template applies only to the rendered pronunciation characters; as far as I can tell, class=IPA
is applied only to those characters, and there is no size reduction here. There may be a clever way around this double-small problem; I'll take a look. I think the grand solution is to have all of this rendering done by a single template (or module, presumably) instead of by
nearly 200 essentially identical templates (edited to add:
and 130+ more). That would involve a bit of programming by one of two or three editors I can think or whom I will not name yet, lest I incur their annoyance. –
Jonesey95 (
talk)
05:21, 30 September 2022 (UTC)
![]() | This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 10 | Archive 11 | Archive 12 | Archive 13 |
Template {{
Unicode}}
will be deleted due to being obsolete. As XP is no longer supported, its font declararion (targeting XP) will also be removed. That begs the question: is the current font declaration for IPA (also targeting XP) still necessary, or can they be removed as well? Note this would only impact XP users, and the template itself is not under discussion; only the font. -- [[
User:Edokter]] {{
talk}}
18:57, 11 April 2016 (UTC)
-- [[
User:Edokter]] {{
talk}}
18:02, 25 April 2016 (UTC)§ Conversion to IPA says
That's wrong. French ⟨j⟩ represents the voiced postalveolar fricative [ ʒ], but IPA ⟨j⟩ represents the voiced palatal approximant.
And for that matter, where's the conversion chart for the "natural spelling"? It sure isn't at Template:IPAc-fr/doc (where I'm also raising this question) or Help:IPA for French. How do you get /ʒ/ in {{ IPAc-fr}}?
Cross-referencing from WikiProject Linguistics.
Please {{Ping}} me to discuss. -- Thnidu ( talk) 18:13, 25 April 2016 (UTC)
I've created this module. It behaves the same way as this template when only one parameter is used, but if a language code is added to the first parameter, it creates a link to that language's help page – for instance, {{IPA/sandbox|fr|/ɛɡ.zɑ̃pl/}}
becomes
/ɛɡ.zɑ̃pl/. The list of help pages in the module isn't complete, but once it is, I think this module could be used to give this template a bit more functionality. —
Eru·
tuon
02:11, 17 October 2016 (UTC)
Finished the list. All ISO 639-1 and ISO 639-3 language codes for the languages that have IPA keys are included. — Eru· tuon 04:24, 17 October 2016 (UTC)
Hi Wikipedians, Would it be possible to render a /g/ as a /ɡ/ (the correct one) in the template for convenience?? Anyone who listens is the best!!😃 Thanks. — Awesomemeeos ( talk) 06:37, 7 July 2016 (UTC)
{{IPA|[g]}}
→ [g]{{IPA/sandbox|[g]}}
→ [ɡ]Kazi Zafar Ahmed is displaying "Lua error in Module:IPAc-en at line 13: attempt to index local 's' (a nil value)". That appears to be a result of recent edits to this template, although possibly the error is old wikitext in the article. Would someone please work out what is going on. Johnuniq ( talk) 06:09, 25 July 2017 (UTC)
if args1 and string.lower ...
to check if the parameter in question exists before trying to use string functions on it. —
Eru·
tuon
16:14, 25 July 2017 (UTC)Statement of the problem
Not even sure that this is correct place to ask this.... My immediate concern is {{ IPA-fr}} and {{ IPA-mg}}, but this a situation endemic to all "IPA-xx" templates where "xx" is some language code. Since {{ IPA-fr}} etc. call this template ({{ IPA}}) this seems like a good centralized place to discuss this.
{{ IPA-fr}} sends a string ("tananaʁiv" for example) to ({{ IPA}}. Well not exactly. If I specify the the string, "tananaʁiv", it actually sends "tananaʁiv". Note the brackets. But I don't want the brackets.
We could edit {{ IPA-fr}} and {{ IPA-mg}} to solve my immediate problem (I can't do it as I lack the chops to do it correctly). But if we did that it would leave {{ IPA-fr}} and {{ IPA-mg}} being different from all the other "IPA-xx" templates, which is not good. We'd have to change all the "IPA-xx" templates.
I could, in {{
IPA-fr}} and {{
IPA-mg}}, add nobrackets=|
to the switch statement (that is, it's treated like a blank parameter), then in the call use "nobrackets" (if present) to send "string" rather than "[string]" to the {{
IPA}}. This seems kludgy.
I guess better would be to send a parameter to here and then strip the brackets here... I guess maybe even easier would be never send them, and then add the brackets here in the absence of a param telling it not to...? Above my pay grade.
Or I may be missing a simple solution that's right there. If so, then Bob's your uncle.
But if not, what is our best way forward here?
Specific instance showing why this is a problem
The article Antananarivo begins thus:
Antananarivo ( /ˌæntəˌnænəˈriːvoʊ/ or /ˌɑːntəˌnɑːnəˈriːvoʊ/; [1] Malagasy pronunciation: [antananaˈrivʷ]), then temporarily French Tananarive ( /təˌnænəˈriːv/ [2] or /ˌtænənəˈriːv/; [3] French pronunciation: [tananaʁiv]), also known by its French colonial shorthand form Tana, is the capital and largest city of Madagascar.
This is objectively horrible on several levels. So what we want to do is change the lede sentence to something that actual humans can read:
Antananarivo, called Tananarive in French and also known by its colonial shorthand form Tana, is the capital and largest city of Madagascar.
and then later in the article body be like
The English pronunciation of Antananarivo is /ˌæntəˌnænəˈriːvoʊ/ or /ˌɑːntəˌnɑːnəˈriːvoʊ/; [4]. The Malagasy pronunciation is [antananaˈrivʷ], and the pronunciation of the old French name Tananarive is /təˌnænəˈriːv/ [5] or /ˌtænənəˈriːv/ [6] in English and [tananaʁiv] in French.
but as you can see the brackets are carried into the text by {{ IPA-fr}} and {{ IPA-mg}}, and we want to strip them. I mean, they're not horrible there, but they don't belong either, and it's non-excellent to have them.
(I do not know why "tananaʁiv" and "antananaˈrivʷ" are presented to the reader instead of the more atomized individual sounds I usually see. I assume that it's because these are non-English pronunciations and that is proper and necessary and why we have {{ IPA-fr}} etc. rather than just using {{ IPA}}.)
So now what? Herostratus ( talk) 20:12, 6 October 2017 (UTC)
![]() | This
edit request to
Template:IPA has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
The IPA-tagging function in Module:IPA is ready to be deployed widely. It creates the exact same content as the existing template, but also changes regular g to IPA ɡ. Please replace the content of the template with the following:
{{#invoke:IPA|tag}}
— Eru· tuon 22:01, 19 June 2017 (UTC)
{{
IPA}}
to the output of {{
IPA/sandbox}}
, which currently uses {{#invoke:IPA|tag}}
. The first example differs only because it changes the g
to ɡ
. —
Eru·
tuon
20:55, 21 June 2017 (UTC)
|answered=
back to n
. --
Izno (
talk)
21:39, 21 June 2017 (UTC)
{{
IPA/sandbox}}
with the actual Lua function in the module, to prevent it changing if someone decides to use the sandbox template for something else. —
Eru·
tuonSee the template test cases at
Template:IPA/testcases. Output of the sandbox template {{
IPA/sandbox}} is identical to the output of {{
IPA}}, except that the non-IPA symbol g
is changed to ɡ
. —
Eru·
tuon
21:28, 22 June 2017 (UTC)
I have reverted the change because an error was reported at {{
IPA-hu}}. It looks like the "g" in the link to
Help:IPA for Hungarian was transformed to "ɡ" (the IPA symbol) as a result of the change. We should fix it.
Nardog (
talk)
22:40, 22 June 2017 (UTC)
g
that is not inside HTML tags or templates or targets of piped links, instead of replacing it. Should I do that? —
Eru·
tuon
17:33, 23 June 2017 (UTC)
g
's inside {{...}} that are supposed to appear in the outcome and ones that are not. Sorry if I'm preaching to the choir.
Nardog (
talk)
17:45, 23 June 2017 (UTC)
{{IPA/sandbox|[[g]]}}
adds the category, but {{IPA/sandbox|g}}
doesn't. I don't think it's ready.
Nardog (
talk)
18:17, 23 June 2017 (UTC)
Does using the right kind of "g" really justify a whole new lua module? Oppose as unnecessary over-complication {{3x|p}}ery ( talk) 19:28, 21 June 2018 (UTC)
If the template ends up being at the end of a line of rendered text and the stress falls on the first syllable of the word, the line break may be inserted between the ⟨/⟩ and ⟨ˈ⟩. For example:
Instead of:
Can someone please fix this? Esszet ( talk) 20:32, 9 August 2018 (UTC)
{{nowrap|{{IPA|/ˈbˠaːiːxt̪ˠ/}}}}
. Note this would also prevent breaking at spaces. If you still want the notation to break at a space, write e.g. {{IPA|{{nowrap|/ˈxxx}} yyy/}}
or {{nowrap|{{IPA|/ˈxxx <wbr />yyy/}}}}
. Inserting {{
wj}}
after /
, or before ˈ
or ˌ
, as in {{IPA|/{{wj}}ˈxxx{{wj}}ˌyyy/}}
, is yet another option.You know that the IPA transcription for “Brasil” is [bɾaˈziw], right? I couldn’t change it because the template is protected. Ten Islands ( talk) 15:31, 7 September 2018 (UTC)
Do we have a page, like Wikipedia:Graphics Lab, for requesting IPA transcriptions? There's nothing mentioned on Help:IPA, and a query on WP:VPM came up with nothing concrete. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:20, 18 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)
![]() | This
edit request to
Template:IPA has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please change the full protection to semi-protection. I want to edit the doc page. 14bauhr ( talk) 18:13, 22 April 2020 (UTC)
{{
edit template-protected}}
is usually not required for edits to the documentation, categories, or interlanguage links of templates using a
documentation subpage. Use the 'edit' link at the top of the green "Template documentation" box to edit the documentation subpage.
Izno (
talk)
22:45, 22 April 2020 (UTC)In wikt:Template:IPA, the template parameters are:
|1=
language code|2=
, |3=
, |4=
... pronunciation(s)|qualN=
qualifier for pronunciation N|nN=
reference note for pronunciation N|nocount=1
disable syllable counting|sort=
manual sort keyBecause w:Template:IPA has only one parameter max, and Wiktionary's has two min, these are completely compatible.
Therefore, please merge them, to keep current behavior if 1 parameter and use Wiktionary's behavior if >1. This would help when copying content from Wiktionary. Sai ¿? ✍ 11:22, 15 March 2021 (UTC)
I was expecting the {{lang-xx}} templates to produce HTML like <span lang="en-fonipa"></span>
to tag the text as English language transcribed as IPA.
Can you modify the template to emit lang tags?
--
Error (
talk)
00:29, 1 May 2021 (UTC)
![]() | This
edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Per
MOS:SMALLTEXT it says Reduced or enlarged font sizes should be used sparingly, and are usually done with automated page elements such as headings, table headers, and standardized templates
. Furthermore, it states that these styles should not be used in infoboxes and other templates that already reduce size. I note that a lot of {{
IPA}} templates are used in the in the opening sentences and across infoboxes when introducing a non-English subject. Please can the automated formatting be removed to comply with the relevant MOS? >>
Lil-unique1 (
talk) —
18:37, 15 July 2022 (UTC)
class="IPA"
in the span tag that governs that. So if you need a larger font, all you need to do is adjust the font size in your browser. You can also change to a different font if you like. Just read the
Usage section on the template page. Hope this helps!
P.I. Ellsworth ,
ed.
put'r there
20:09, 15 July 2022 (UTC)
Italian pronunciationin small. Prose underneath a section header should be in one size as this aids readability whether you have a disability or not. >> Lil-unique1 ( talk) — 23:23, 15 July 2022 (UTC)
class="IPA"
to something else. That would then have a
domino effect for
several other applications. So it appears that a
consensus would be needed, and that means finding a centralized place to
discuss it such as
WT:LANG or
WT:IPA or even
WT:ACCESS. Not sure which venue would provide the best turnout of editors; however, placing neutral notices of where the discussion is being held can be very helpful.
P.I. Ellsworth ,
ed.
put'r there
16:15, 16 July 2022 (UTC)
IPA
class has nothing to do with the label size. That code is in
IPA-xx templates, not {{
IPA}}.
Nardog (
talk)
17:58, 16 July 2022 (UTC)
Jonesey95, you have fixed several
MOS:SMALLTEXT issues before. I came here after seeing the infobox in
Isa (name) and having to squint to read it. There is discussion above about needing consensus to change anything. But
MOS:SMALLTEXT is clear on this. The real issue is that these templates are commonly used in prose where there is no problem (e.g.
Najd). So isn't the solution that we need a |size=100%
parameter as in {{
post-nominals}} so the default of small can be overwritten only when needed, as in infoboxes?
For reference, the doc at that template says Font size: The optional |size= parameter allows for the size of the text, as a percentage, to be changed from the template's default of 85%. As per MOS:FONTSIZE, this must be added when the template is used in infoboxes (it should be set to 100%), because infoboxes already use size-reduced text.
That is exactly the same as here. It even says must; I think the small text must be fixed here also.
MB
00:40, 30 September 2022 (UTC)
<small>...</small>
tags in {{
IPA-ar}} and its siblings, not by {{
IPA}}. This IPA template applies only to the rendered pronunciation characters; as far as I can tell, class=IPA
is applied only to those characters, and there is no size reduction here. There may be a clever way around this double-small problem; I'll take a look. I think the grand solution is to have all of this rendering done by a single template (or module, presumably) instead of by
nearly 200 essentially identical templates (edited to add:
and 130+ more). That would involve a bit of programming by one of two or three editors I can think or whom I will not name yet, lest I incur their annoyance. –
Jonesey95 (
talk)
05:21, 30 September 2022 (UTC)