Template talk:IPA symbol/Archive 1

Archive 1

Proposed changes to the list

Just type a request below at the end of section. An editor familiar with the template might come along and change the list accordingly (stroke the line here when completed please).

• change 518 into Upstep. {{IPAsym|518}} → error
• add ꜛ◌ for Upstep. {{IPAsym|ꜛ◌}} → Upstep
• add ꜛ for Upstep. {{IPAsym|ꜛ}} → Upstep Already exists
• change 517 into Downstep. → error
• add ꜜ◌ for Downstep. {{IPAsym|ꜜ◌}} → Downstep
• add ꜜ for Downstep. {{IPAsym|ꜜ}} → Downstep Already exists

-DePiep (talk) 13:43, 5 August 2011 (UTC) -DePiep (talk) 18:14, 6 August 2011 (UTC)

• change 180 into singular "lateral click". {{IPAsym|180}} → error
• change 179 into singular "palatal click". {{IPAsym|179}} → error
• change 178 into singular "alveolar click". {{IPAsym|178}} → error
• change 177 into singular "dental click". {{IPAsym|177}} → error
• change 176 into singular "bilabial click". {{IPAsym|176}} → error

-DePiep (talk) 22:43, 6 August 2011 (UTC)

I moved upstep & downstep because there was nothing to dab from. I don't know if that will permanently be the case, though.

IMO the click families should be plural for the same reason language families are. We don't have our article at 'Semitic language', even though we could. — kwami (talk) 11:32, 7 August 2011 (UTC)

The change re Upstep and Downstep was obvious indeed.

I changed "clicks" into singular, as per WP:MOS. We do singular, unless absolutely necessary (scissors, pants). Although it is a family, the concept of "click" exists (we can write: A click is ...). We also have Consonant (but I know, stuff exists...). I am fine with the MOS.

Now right when I was typing this, an editor performed the editrequest here in IPAsym (I planned to pause it). Still, if you want to discuss it further, depending on the outcome we can and will revert, of course. -DePiep (talk) 12:06, 7 August 2011 (UTC)

No, it's more than just lexicalized cases like 'pants'. Germanic languages, for example, even though we say 'Eng. is a Germanic language'. The problem in my mind is that people are always saying Zulu has three clicks (dental, alveolar, lateral), etc., clearly not recognizing that's like conflating /t d s z n l/ in English. Just as the pl. in 'languages' alerts the reader that we're not talking about 'a' language, or the pl. in Egyptian hieroglyphs, so if they read about 'the dental click' in some lang, the pl. here alerts the reader that there's more going on than they may be aware of. — kwami (talk) 12:26, 7 August 2011 (UTC)

Hm, this is something I must chew on. Can it be, that the "Germanic language" does not exist in itself? It is purely an idea or concept, so one cannot say "the Germanic language" but yes; "a Germanic language". (Comes to mind, maybe another example: on families, one says "the Johnsons are coming over", and one person then surely is "a Johnson", but there is not "the Johnson". Here too a common ancestor is understood). Any lesson from biology? Primates are in the (Order of) Primates (same stuff: family, concept, we rarely use "the primate" but yes "a primate"), clearly. Still, we do have the singular article name. Your line about the 'alert', is a bit weak as an argument for the pluralisation imo, but you could mean to alert about a concept.

Now this way there is a point for clicks to be plural as with "Germanic languages". But still. I understand the MOS so, that it tries to prevent plurals in titles unless impossible to do so. That is a nice guideline or policy, because it produces consistancy and such. So all species & orders in biology are singular in their title here. I am with the monkeys here: I know a monkey ;-). I don't think clicks are an exception enough. -DePiep (talk) 13:56, 7 August 2011 (UTC)

Eh, Kwami, you reverted already? Into plural? Something is wrong. -DePiep (talk) 23:29, 13 August 2011 (UTC)

Please check

Hi there, I've just finished this template, which I'm going to use in a few places.

I have taken the symbols from Template:CSS IPA consonant chart and Template:CSS IPA vowel chart. Please add any missing symbols to the table. Also, I think due to a font issue, some of the symbols on my computer render as a central dot. For example, retroflex trill. Please check and substitute the proper symbol if my version is wrong. Thanks. 123.218.168.102 (talk) 11:58, 12 June 2010 (UTC)

Message to Kwamikagami

I write here because User_talk:Kwamikagami is protected - he/she may want to review this decision by the way.

Thank you for your contribution. Please note that your adding the category broke the template, because the noinclude tag should be *on* the last line of the template body, not the next line. Now fixed, thanks. 123.218.143.22 (talk) 00:17, 13 June 2010 (UTC)

Sorry, I'm not that familiar with it. (Also sorry for the protection: vandalism. Should be off in a few hours.) — kwami (talk) 00:33, 13 June 2010 (UTC)

Cool, I have added some documentation, still working on it. I meant to advertise the template when it's a bit more stable, but feel free to poke about. Now the documentation should make it immediately clear if it's broken badly, but do check Wikipedia:IPA_for_Russian and Wikipedia:IPA_for_French to be sure. I'll add some testcases later. (No worries about the protection, sorry myself, I assumed it was an indefinite protection, which I've seen abused too many times.) 123.218.143.22 (talk) 01:42, 13 June 2010 (UTC)

Alternative symbols for t͡s, d͡z, t͡ʃ, d͡ʒ, etc

Hello there.

I am considering whehter this table should include alternative symbols for t͡s, d͡z, t͡ʃ, d͡ʒ, etc. I notice that these symbols are often written simply as ts, dz, tʃ, dʒ, etc. However, according to the respective sound articles (t͡s, d͡z, t͡ʃ, d͡ʒ), this is incorrect. (The case of t͡ʃ seems actually less clear-cut, but more likely that article is sloppier than the other ones.) If it is incorrect, then I see it more a motivation to fix those examples that use "ts" rather than "fixing" this table. This is exactly what I have done in project pages that now use IPAlink, like WP:IPA for Italian etc.

The articles above (as well as IPA) also point out that previously, ligatures were used instead (respectively ʦ, ʣ, ʧ, ʤ). I have therefore added those ligatures to the table.

If it is decided that we should actually also add "ts" etc as alternatives (but see my argument against, above), please use the fall-through syntax, like so

 ...
  | ts
  | ʦ
  | t͡s = voiceless alveolar affricate
 ...

Thanks. 123.218.143.22 (talk) 04:09, 13 June 2010 (UTC)

Someone did that once before, and someone else then went through and deleted all the tie bars. Problem is, Microsoft fonts don't display the tie bar correctly. Also, it's rather distracting in languages like Italian which don't need it. (Polish is another matter.) — kwami (talk) 06:06, 13 June 2010 (UTC)

Can we have more details on the "Microsoft fonts" issue please? As for its being distracting, that's relative, and I think correctness trumps that. This discussion should probably be moved to WP:PHONETICS. 114.146.118.158 (talk) 18:39, 13 June 2010 (UTC)

There have been multiple discussions of these issues. Maybe search for 'tie bar' + IPA on talk pages. — kwami (talk) 20:41, 13 June 2010 (UTC)

Re Kwami: Maybe MS does not show them correctly (which implies something for the preferred usage of these symbols in Wiki - OK so far). But that should not exclude these symbols from this template, is it? A specialised article on these signs should be able to use the template (with or without MS effects). Even better: this template produces the name for such a badly-rendered symbol. -DePiep (talk) 10:20, 9 July 2010

Surprise: currently the three ts-variants are in right now (edit 13 June 2010 by User:Xyzzyva):

...
| ʦ
| ts
| t͡s = voiceless alveolar affricate
...

So this discussion seems to conclude different from reality? (conclusion: not because of MS-issues; reality: yes). -DePiep (talk) 10:27, 9 July 2010 (UTC)

Capitalisation: to single style

Currently capitalisation is mixed:

• all lowercase: | m = bilabial nasal
• first capital: | ỹ = Nasal vowel

Usage in linking (as in [[{{IPAsym|m}}]]) still functions as expected: Voiced bilabial nasal.
Proposal: For consistency, I propose keeping the original style: all (to) lowercase. . -DePiep (talk) 10:35, 9 July 2010 (UTC)

Well, I just changed it. All lc. All OK-DePiep (talk) 22:30, 9 July 2010 (UTC)

Including non-IPA symbols

Given the broad aim of this template (i.e. providing the name of a symbol), I propose to include non-IPA symbols too. Main goal is to provide the right name, not to punish editors who do not know that a symbol is non-IPA. Example (wanted situation):

• {{IPAsym|ᴙ}} → epiglottal trill (not: )
• [[{{IPAsym|ᴙ}}]] → epiglottal trill

To be solved then: should we mark the outcome like: epiglottal trill (non-IPA)? Would clarify the IPA-status, but would break a possible link. Any suggestions? -DePiep (talk) 10:50, 9 July 2010 (UTC)

We can add a redirect from epiglottal trill (non-IPA) to epiglottal trill. 123.225.152.131 (talk) 21:26, 19 July 2010 (UTC)

Default string

Hi there,

I think it would be better if the default were a (potentially salted) non-existent page, so that {{IPAsym|xxxx}} translates to something like "xxxx does not correspond to any IPA article. Please modify Template:IPAsym if you think it should.".

This means that editors see immediately a red link and they can either change this template or just remove the IPAsym template usage for now - or correct the mistake in the argument.

Thoughts? 118.7.230.94 (talk) 12:24, 19 July 2010 (UTC)

Great idea. Actually, it is already implied. Template:IPAsym has a /doc that describes the option:

{{IPAsym|pʰɪk|Boy, what a strange input}} → Aspirated consonant

The default output should stay "IPA", because current uses depend on that. Unless you promise to changee all current usages, the default should not be altered. -DePiep (talk) 23:30, 19 July 2010 (UTC)

Oh, OK I was not aware of the addition of a second parameter. Out of interest, when would it be useful to specify a second parameter?

I think I'm going to go ahead with this change. It's not really going to break anything. The worst that could happen is some links going red and attract attention, which is exactly what this change is meant to achieve. 205.228.108.58 (talk) 03:20, 20 July 2010 (UTC)

If you go ahead changing the default text "IPA", it might be reverted. You'd break working links. The template is automatically used in {{IPAlink}} and {{IPAblink}}, which presume linkability (i.e. yes to IPA, not to your suggestion xxxx does not correspond to any IPA article. Please modify Template:IPAsym if you think it should.

2nd parameter is only added recently. However, it does not return the input character (1st variable, xxxx in yr example above). To achieve that, you could repeat the character in the 2nd variable, like

{{IPAsym|xxxx|xxxx has no IPA-article}} → xxxx has no IPA-article

The 2nd variable is used in {{infobox IPA base}} (and so via {{infobox IPA}}) in case the character (actually IPA-number) is not found:

{{infobox IPA{{Infobox IPA |ipa-number=999 |ipa=dddd }} produces the return text (red in top) "IPA-nr: <ipa-number>", not the default "IPA" (which would be less sensible here):

IPA Number	999

-DePiep (talk) 10:47, 21 July 2010 (UTC)

Maybe this idea could work: if not found in IPAsym, then link to say IPAsym-pagenotfound, which should be a redirect to IPA. This should work fine for all current use (nicely to IPA as expected), and gives you the opportunity to research omissions by checking "What links here" on the redirect-page. Be sure to doc that well on the redirect, and allow 30 days for all caches to reflect the new link when checking WLH. Dunno if redirects should be used this way. -DePiep (talk) 11:07, 21 July 2010 (UTC)

OK, done. I don't think you understand, the whole point of this change is to make some links red. I know this template and IPAlink quite well, since I created them. Please discuss here if you find instances where this is actually breaking something. Thanks. 122.25.218.126 (talk) 13:21, 21 July 2010 (UTC)

Yes I do understand. I do not want red links. Until now, I thought you'd understand too. I'll take a look at what you did. -DePiep (talk) 18:16, 21 July 2010 (UTC)

Reverted, as I announced. Apart from seriuos Talk here, why diff IP's? -DePiep (talk) 18:20, 21 July 2010 (UTC)

Please point out here an example of real usage that in your opinion is "breaking". Until then, please do not revert. I am just correcting a design mistake I made when creating IPAsym and IPAlink. The documentation of IPAlink (which incidentally you failed to revert, thus leaving the pair in an inconsistent state) bears witness that it would have been a better idea to do this from the start, "The latter is normally more an example of accidental misuse than intentional use, or it could be a sign that a symbol is missing from the {{IPAsym}} table."

"I do not want red links" seems a rather obtuse statement and not a good justification for this revert. Red links are part of a functional wiki. They are not something "broken" or to be avoided at all cost. They highlight the fact that either (1) the target has been misspelled, or (2) information is missing, in this case either an article is missing, or an entry in IPAsym is missing, or both. 60.45.93.7 (talk) 22:10, 21 July 2010 (UTC)

118.7.230.94, 205.228.108.58, 122.25.218.126, 60.45.93.7: hi who are you. -DePiep (talk) 22:25, 21 July 2010 (UTC)

I fail to see how my identity is relevant to this discussion.

Please provide a valid rationale for your reversion and your opposing this change in general.

I think I have amply explained why this change is desirable, how it is not going to break anything and how it is in line with the original intention. Please provide any argument to the contrary, other than "I don't like it". 60.45.93.7 (talk) 12:20, 22 July 2010 (UTC)

- Not your identity, but your IP's. Because they're changing, I have to check whether (and assume that) I am discussing with one and the same person.

- The example of a broken link I gave before at 10:47, 21 July 2010 (UTC) (my reply "If you ..."). You have not explained or checked what happens to the links that currently (I still suppose) link to IPA, as is expected by any editor who uses IPAsym. This is what is documented, and how it the template is currently used. Indeed red links are not forbidden etc., but changing a working link into a red one is working backwards.

- You're right it might have been done different from the start, but now tyhe template us used given the IPA-default.

-Please note that your plan is aimed at editors, while articles are meant for readers. Your error-message is a jump out-of-text. Readers should not be bothered with error-messages. btw, why not use my tip on the redirect? Or check & change manually all WLH-articles that currently end up in IPA? -DePiep (talk) 20:14, 22 July 2010 (UTC)

The intention of this change is to show any new bad links as red in the future, which is in line with the way MediaWiki works. Also, and more to the point, the intention is to turn any links that currently point (incorrectly) to IPA into red links.

The essence of your opposing this change is that it could turn some links red. Can you not see a problem with your argument? That's part of the intention...

You keep saying "You'd break working links", yet you have not offered one example where this would actually happen. By example I don't mean a thought-up scenario, but an actual instance of current use of this template that would be (in your opinion only) "broken" by this change.

In summary, you are reverting this change on a flawed argument and on a supposition that you can't be bothered to verify.

Your suggestion of a redirect is not satisfactory, because editors would have no visual feedback that their link is... well, red.

The argument "articles are meant for readers" doesn't really cut it, because the way Wikipedia works is that readers who click on red links become editors. Admittedly this would be slightly more indirect, but I don't foresee any major catastrophes. If you do, please share any such disastrous scenarios.

You also say "You're right it might have been done different from the start", so it follows that your only point of contention really consists in those supposed broken links.

I have manually checked and there are no such links. I will therefore reinstate the change, with your kind permission. 123.218.168.141 (talk) 21:48, 22 July 2010 (UTC)

If there is no current use of the IPA-default, a change can be made on that aspect. (Simply, since you propose the change, it is up to you to prove that no harm is done). But please see next point:

Then, you introduce an error-message as a link. That use is not the way to use links or templates. It is like jumping out of the wiki-articlespace. If you want to show an error-massage in future edits then instead of a link (a "salted page"), you can show red text in the preview as is done at <ref></ref>-errors, or incorrect expressions (see Help:Calculation). That is: straight text (probably in red), not a link. Could you respond on this? -DePiep (talk) 12:40, 23 July 2010 (UTC)

Eh, you checked 230 pages manually? Could you tell what you did exactly? -DePiep (talk) 12:47, 23 July 2010 (UTC) correction -DePiep (talk) 12:53, 23 July 2010 (UTC)

I like your idea of a proper error message, thanks for pointing me to an example. I don't know how that works, but the "exception" will need to propagate through all the invoking templates. It should be fine, I'll have a look. Cheers. 123.225.176.231 (talk) 14:19, 23 July 2010 (UTC)

One way is to use the text (where you'd write the default/notfound text):
'''<span style="fontsize:big; color:red;">Here goes your message</span>'''
producing: Here goes your message
So you are manually sure in the 230 pages there is none that uses the #default? -DePiep (talk) 16:17, 23 July 2010 (UTC) btw, be sure to check the effect on {{infobox IPA}}, because that one uses parameter {{{2}}} for #default. added -DePiep (talk) 16:20, 23 July 2010 (UTC)

Uhm... yeah, but if it's that simple that's not going to cut through the invoking template, is it? End users invoke stuff like IPALink, not IPASym directly. I'll have a look at Help:Calculation. If it's not possible I'll fall back to the red link solution.

My understanding is that the infobox by design never uses what now is "IPA", I was under the impression that you introduced the second argument exactly for that reason. I'll check it anyway, don't worry. Thanks. 122.26.79.88 (talk) 21:50, 23 July 2010 (UTC)

-(plot spoiler: My final line below is: go ahead)

-Help:Calculations is only an example here of yes red text error message in preview, and not link to a salted page. I'd hope the code example is clear (to produce big red text). Just replace the default "IPA" with "<span style="color:red;">My Red Message</span>". Try it, it might work (the <span> ... </span> does the effects): My Red Message.

-If you create the red text in IPAsym (so replacing default text 'IPA'), it will produce ;ile [[My Red Text message]] in IPAlink etc (now red twice!). That I would not consider a problem: the editor previews, and sees your message in red, with or without brackets. Good.

-re infobox IPA is using a 2nd parameter: yes, I checked them all individually (and added the IPA-number in IPAsym when red). I did not provide a help/error-text. But you go ahead, and I'll take a look into it later on, and come back here to discuss. Just hope you're in for another improvement to keep the infobox IPA going.

-Just a tip you can skip: I like using the /Sandbox, that every Template/document (green in my screen) provides, in the bottom lines. I copy the source template-code, and the /Sandbox-page is free to test & try. There's also a link to a /Testcases page, to test the template like from a Wikipage. Playground!

Having read your replies, I'd say go ahead. -DePiep (talk) 22:30, 23 July 2010 (UTC)

This is done. I have used class="error", which is the standard way of reporting errors. It supports use of #iferror, no need to hard-code formatting, etc. Testcases check out fine. Please report any problems. Thanks. 122.26.79.88 (talk) 05:40, 24 July 2010 (UTC)

Nice. class="error" is even better, & a discovery for me. Consider this
 Done
-DePiep (talk) 08:39, 24 July 2010 (UTC)

No viable showsymbol option for IPAblink

[merged from {{IPAblink}} talk page. — kwami (talk) 06:07, 1 November 2010 (UTC)]

IPAblink with showsymbol option doesn't display the specified symbol, why? Could this please be fixed? E.g., {{IPAblink|ˤ|showsymbol=sˤ}} produces [ˤ]. Whereas {{IPAlink|ˤ|showsymbol=sˤ}} produces ˤ in any case, i.e., if I don't want the brackets, I'll use IPAlink, not IPAblink. Dan ☺ 12:03, 24 October 2010 (UTC)

I'll take a look into that. -DePiep (talk) 12:04, 24 October 2010 (UTC)

Now it's like this: {{IPAblink|ˤ|showsymbol=sˤ}} --> [ˤ]

please let me know (e.g. here) if there's something strange left. -DePiep (talk) 12:22, 24 October 2010 (UTC)

Brilliant, thanx Dan ☺ 15:15, 25 October 2010 (UTC)

Merge from {{IPAlink}} talk

Why not just have two parameters, the first being the link and the second the display, without having to type it "showsymbol=" each time? — kwami (talk) 18:15, 28 October 2010 (UTC)

linking

I've found about 200 articles with manual links, and am converting them over with AWB. Rather that adding 'showsymbol=', which is a pain in the ass, I'm adding additional symbols to this table.

Could we maybe get a shorter / quicker to type call extension for that? [as merged request above] — kwami (talk) 09:03, 31 October 2010 (UTC)

Okay, linked all I could find, apart from ones which use non-IPA symbols or link to Australian English phonology. — kwami (talk) 06:06, 1 November 2010 (UTC)

using {{IPA|p}} as input errors

At WP:VPT village pump I have asked this Wikipedia:Village_pump_(technical)#font-related_class.3D.22IPA.22_disrupts_a_.23switch: about IPAsym returning error when entering like: {{IPAsym|{{IPA|p}}}}. -DePiep (talk) 14:37, 24 January 2011 (UTC)

Outcome: do never use the template {{IPA}} around the input symbol. It will fail. -DePiep (talk) 13:21, 23 June 2011 (UTC)

ejectives or glottalization

Glottalization states, "There are two other ways to represent glottalization in the IPA: (a) the same way as ejectives, with an apostrophe...". Biblical Hebrew uses ʼ to denote glottalization, but the {{IPAblink}} templates there link the symbols to articles on ejectives. It's a mess. Suggestions? Dan ☺ 00:40, 18 February 2011 (UTC)

That article appears to say they likely were ejectives, so the link is appropriate. Actually, it says they're "glottalized", which could mean either ejectives or implosives; presumably it doesn't mean the latter. Probably it intends that there's something going on in the throat and we don't know what. If you're arguing they're not ejectives, then the ejective symbol should not be used when transcribing Hebrew in the IPA if you want to link anything. Same with using ‹c› for an affricate in Indic: if you use a symbol for something other than what it's defined to mean, then your links aren't going to work right. The fix shouldn't be at this end, but in the imprecise use of precisely defined symbols. — kwami (talk) 19:13, 5 May 2011 (UTC)

Ah, the glottalization article was imprecise. It should have said "to represent glottalization of sonorants in the IPA". The apostrophe and under-tilde are not interchangeable for obstruents. Fixed. — kwami (talk) 19:23, 5 May 2011 (UTC)

dental approximant and syllable break

• ð̞
• .

178.101.44.228 (talk) 17:25, 16 April 2011 (UTC)

Reverted, at least for now. Those aren't good links. — kwami (talk) 20:51, 16 April 2011 (UTC)

Why aren't they good links? There isn't a syllable break article yet (so, it could link to either hiatus (linguistics) or syllabification, or just create a whole new article).

IPA suprasegmentals include a plain dot (used to break syllables), but you just include an interpunct (used for syllabification)

With regard to the approximant, there is here already a bilabial approximant (found in Spanish) which links to voiced bilabial fricative, so I don't know why you don't have a dental approximant (also found in Spanish).

Couldn't you include ð̞ and .? Thanks.

Linked to redirects, in case those are ever expanded. — kwami (talk) 19:10, 5 May 2011 (UTC)

Template hacked

It would appear that the template has been hacked. Admins may need to review. dazzafar (talk) 15:49, 5 May 2011 (UTC)

It was, in fact, vandalism at {{StripWhitespace}}, which appears to have been fixed now. Richwales (talk · contribs) 17:00, 5 May 2011 (UTC)

IT's still vandalized. 69.113.235.6 (talk) 00:43, 6 May 2011 (UTC)

I can't see any sign of the original vandalism. If you're still seeing it, try clearing your browser cache. Richwales (talk · contribs) 05:41, 6 May 2011 (UTC)

Name changes are stable?

 Changed soundfile names to new article names using {{media rename}}. -DePiep (talk) 00:49, 29 June 2011 (UTC)
Recently [1] a dozen or so article names have been changed. e.g:

• ʒ was Voiced postalveolar fricative → Voiced palato-alveolar sibilant
  

No problem with me. A consequence is, that the corresponding soundfile has a different name:

• {{IPA soundbox|ʒ}} →
  ʒ
• {{IPA soundbox|ʒ|soundfile=voiced postalveolar fricative.ogg}} →
  ʒ

So: we need to enter the (non-default any more) soundfile name separately, or change the name of the soundfile. This problem also happens in the IPA infobox (example: see Voiced palato-alveolar sibilant, the soundfile is not found and not available any more).

The changes are:

symbol	old name	new name
s	voiceless alveolar fricative	voiceless alveolar sibilant
z	voiced alveolar fricative	voiced alveolar sibilant
ʃ	voiceless postalveolar fricative	voiceless palato-alveolar sibilant
ʒ	voiced postalveolar fricative	voiced palato-alveolar sibilant
ʂ	voiceless retroflex fricative	voiceless retroflex sibilant
ʐ	voiced retroflex fricative	voiced retroflex sibilant
t͡ʃʼ	postalveolar ejective affricate	palato-alveolar ejective affricate
t͡ʃ	voiceless postalveolar affricate	voiceless palato-alveolar affricate
d͡ʒ	voiced postalveolar affricate	voiced palato-alveolar affricate
ɕ	voiceless alveolo-palatal fricative	voiceless alveolo-palatal sibilant
ʑ	voiced alveolo-palatal fricative	voiced alveolo-palatal sibilant
ʷ	labialisation	labialization

My question is: are these changes stable now (i.e. no disagreement between phoneticians, no re-moves to be expected)? If so, then we can change the soundfile-names into the new names. If not, we'll wait. -DePiep (talk) 20:49, 22 June 2011 (UTC)

We, it's not a disagreement so much as a preference. [b] can be called a stop, plosive, or occlusive; [s] a fricative, sibilant, or sibilant fricative. None of them are wrong; it's more a matter of precision and common name. As for -sation vs -zation, since the -z- is both British and American but the -s- only British, the forms in -z- are preferable.

Can the infobox be customized so that it doesn't matter if the names match or not? — kwami (talk) 04:27, 23 June 2011 (UTC)

About that last one: IPA infobox, IPA soundbox and more use IPAsym essentially to produce the one and only sound-(article-)name; then, extending it with ".ogg", it composes the soundfile name as a default. So to cover multiple acceptable names for that sound, we'd need a new, different template that maps all the names to a single soundfile name (structure like {{IPAsym}}, but left hand entries differ), like.

...

| voiced postalveolar fricative

| voiced palato-alveolar sibilant = voiced postalveolar fricative.ogg

...

This would add another maintenance-thing. Especially since this does not warn the editor for missing entries (unless he's looking for them), we will loose more and more linked soundfiles in infobox & soundbox. Which is why I prefer stable (unchanging) names. If it is just once we can put up {{Rename media}} requests to rename the filenames.

Another solution is to enter the non-default filename in the IPA infobox, like | soundfile = voiced palato-alveolar sibilant.ogg. Which is an unwarned maintenance thing too, while still keeping the different name.

All together, if the new names will stay unchanged, we can propose the namechange once for these files. -DePiep (talk) 13:03, 23 June 2011 (UTC)

I don't expect they will change again any time soon. — kwami (talk) 15:14, 23 June 2011 (UTC)

Cool. And so short. I'll do as said. Sounds will be again. -DePiep (talk) 23:26, 23 June 2011 (UTC)

Check on existence .ogg-file old name/new name:

symbol	old name	new name
s
z
ʃ
ʒ
ʂ
ʐ
t͡ʃʼ	noicon
t͡ʃ	noicon
d͡ʒ
ɕ
ʑ
ʷ	noicon]	noicon
̃	noicon	noicon

-DePiep (talk) 09:05, 25 June 2011 (UTC) - Done -DePiep (talk) 00:49, 29 June 2011 (UTC)

Sorry about taking so long to respond, I've been out of town. I agree that the names are now probably going to be stable, and that changing the sound files accordingly was the right thing to do. Benwing (talk) 02:26, 3 July 2011 (UTC)

Support appreciated. -DePiep (talk) 16:36, 3 July 2011 (UTC)

request re editprotect

{{editprotect}} I'd like to make some edits as I am familiar with; please open it up for an hour or so. -DePiep (talk) 23:24, 29 June 2011 (UTC)

 Declined - This isn't how editprotected works. If you have changes you would like to make, please provide the code you'd like replaced and the code you'd like to replace it with here and an admin will make the edit. If you want a page unprotected, you should list it at WP:RFPP, although a high-profile template like this is very unlikely to be unprotected for any reason. Also, for future reference, the edit protected template adds pages to a watch category; you don't need to ask an admin directly. Hersfold ^(t/a/c) 23:34, 29 June 2011 (UTC)

Yes I know. I build this template virtually myself, as you can see in the history (and of the sandbox, and of the /doc, lest you forget). The decision to fullprotect is opaque, and cascading through a usersubpage does not help understanding either. I'll ask for pp change. -DePiep (talk) 00:03, 30 June 2011 (UTC)

Adding lines

1. To add one complete line:
<!-- EJECTIVES -->

• Where: right above the line | 101 401
• Above this injection a whiteline will stay present.
• Note: of course, this is to keep some overview in the list

2. To add: seven complete lines, starting with a space:

| ʈʼ = retroflex ejective
| fʼ = labiodental ejective fricative
| θʼ = dental ejective fricative
| ɬʼ = alveolar lateral ejective fricative
| xʼ = velar ejective fricative
| χʼ = uvular ejective fricative
| cʎ̝̥ʼ = palatal lateral ejective affricate

• Where: right below the line | sʼ = alveolar ejective fricative (search near "132 401")
  
• Below these lines a whiteline will remain.
• Note: the lines will add seven more IPA-symbols linked to an article.

The edits have been unit tested in the Template:IPAsym/sandbox, this version. -DePiep (talk) 01:09, 30 June 2011 (UTC)

 Done — Martin (MSGJ · talk) 16:29, 30 June 2011 (UTC)

Yeah done ultimately, but it has cost me two hours time+ and a day through to only get the question right with admin officers. And still no answers. -DePiep (talk) 00:40, 1 July 2011 (UTC)

Todo done: add later on

 added July 2011 -DePiep (talk) 01:14, 17 July 2011 (UTC)
When protection is loosened: As used in Affricate consonant:

• add t̠ɕ for t͡ɕ = voiceless alveolo-palatal affricateRelative articulation#Advanced and retractedRelative articulation#Advanced and retracted
  
  
• add ʈʂ for ʈ͡ʂ = voiceless retroflex affricate Voiceless retroflex affricate
  
  
• add t̠ʃ for t͡ʃ = voiceless palato-alveolar affricateVoiceless postalveolar affricate
  
  
• add d̠ʒ for d͡ʒ = voiced palato-alveolar affricate Voiced postalveolar affricate
  
  
• add d̠ʑ for d͡ʑ = voiced alveolo-palatal affricate Relative articulation#Advanced and retracted
  
  

Currently, I have solved it differently in that article, the links are provided (by using the second, existing IPA symbol). -DePiep (talk) 09:34, 30 June 2011 (UTC)

• add kʟ̝̊ʼ and kʼ for velar lateral ejective affricate Velar lateral ejective affricate(check presence. It looks like the first one, with an L, is missing. Second ione has Private Use Area code U+F268 LATIN LETTER SMALL CAPITAL L WITH BELT; keep?) -DePiep (talk) 15:14, 1 July 2011 (UTC)
• add k͡ʟ̝̊ k (variant symbol with PUA U+F268) for Voiceless velar lateral affricate Voiceless velar lateral affricate
• addc͡ʎ̥˔ for cʼ voiceless palatal lateral affricate Voiceless (2nd one uses Private Use Area U+F267 LATIN SMALL LETTER TURNED Y WITH BELT) -DePiep (talk) 08:53, 4 July 2011 (UTC)

Edit protected

Request

Please copy all code from the sandbox into the Template: {{IPAsym/sandbox}} → {{IPAsym}} (this version).

Changes

Added six symbols (see previous post on this talkpage). Includeonly moved.

Tested

Sandbox code is checked in test. -DePiep (talk) 12:52, 14 July 2011 (UTC)

 Done Danger (talk) 19:50, 16 July 2011 (UTC)

Appreciated -DePiep (talk) 01:11, 17 July 2011 (UTC)

Todo

• Removed my own post, see Proposed changes to the list, top of page) -DePiep (talk) 18:14, 6 August 2011 (UTC)

Edit protected request

Request

Please copy all code from the sandbox (this version) into the Template: {{IPAsym/sandbox}} → {{IPAsym}}, .

Changes

Added symbols as per talkpage: upstep, downstep, clicks into singluar. Also extra IPA numbers. Added comment groupnames. See sandbox diff for all changes.

Tested

Sandbox code is checked in testpage.-DePiep (talk) 00:07, 7 August 2011 (UTC)

 Done

Name change

[2] Now it's File:Voiced palatal stop.ogg. We've lost links to File:Voiced palatal plosive.ogg. -DePiep (talk) 23:38, 20 May 2012 (UTC)

Okay, how do we display the proper name, link to the correct article, and also link to the correct sound file? — kwami (talk) 07:19, 21 May 2012 (UTC)

Option 1: change the filename File:Voiced palatal plosive.ogg into File:Voiced palatal stop.ogg. This is out of out English WP, but can be done and is solid (assuming that the new name is OK). Any admin can find the template to request this.

Option 2: Use bypass, as explained {{IPA audio filename}}.

Note: right now, no clicks have sound links: Template:IPA chart non-pulmonic consonants with audio.

-DePiep (talk) 23:37, 26 May 2012 (UTC)

IPAlink

The new functionality of IPAlink (the bracket parameter) is inconvenient. The brackets should be the 2nd parameter, not the third. However, since we don't actually use this, I've left it for now. What we could do is add a line to recognize the input: if the 2nd param is a bracket, then it would look to the 3rd for text replacement; if not, then it would use the 2nd as text replacement. That way it wouldn't matter which order they're in, and there would be no need for a double pipe to skip a param. — kwami (talk) 08:05, 8 July 2012 (UTC)

I've made this in the sandbox: parameter 2 and 3 each can take a bracket or a label text (aka showsymbol). If a bracket is entered, that is recognised & used. Any other text (in parameter 2 or 3) will be used as label. See {{IPAlink/testcases}}

Examples:

• {{IPAlink/sandbox|m}} → m
• {{IPAlink/sandbox|m|<}} → <
• {{IPAlink/sandbox|m|My text}} → My text
• {{IPAlink/sandbox|m|My text|<}} → My text
• {{IPAlink/sandbox|m|<|My text}} → <

(using {{IPAlink/sandbox}}). Is this OK? -DePiep (talk) 17:06, 19 July 2012 (UTC)

Yeah, that looks good. Actually, the coding looks simple enough that I wonder if we couldn't modify it to optionally pass the bracket through {{{1}}} as well, though perhaps that would create complications with distinguishing link from display. Not important enough to bother with unless it's really easy. — kwami (talk) 20:58, 24 July 2012 (UTC)

I will chew on that idea. Wil be an extension of functions, so no decision needed for now (will fit). Btw, input options "] >" are gone deprecated by now and there is option "<" to produce "⟨" correctly. Will put this version into live. -DePiep (talk) 21:17, 24 July 2012 (UTC) correcting -DePiep (talk) 21:48, 24 July 2012 (UTC)

Input "g" errors

When I use {{IPAlink|g}}, it screams with reddish error...!? -Konanen (talk) 03:38, 7 December 2012 (UTC)

Formally the symbol isU+0261 ɡ LATIN SMALL LETTER SCRIPT G, which is not the regular keyboard "g". But since it is unambiguous, I've added the regular g U+0067 g LATIN SMALL LETTER G for this as input. So now it works: Voiced velar plosive. -DePiep (talk) 10:15, 7 December 2012 (UTC)

Undid: in should be the right character, not the regular "g" e.g. in /.-DePiep (talk) 10:25, 7 December 2012 (UTC)

typo in {{IPAsym/check}}

There is a typo in the results of the {{IPAsym/check}} output. "Creacky voice" should be "Creaky voice" instead. VanIsaac_{WS Vex}^contribs 02:30, 23 December 2012 (UTC)

Changed in {{IPAsym}}. -DePiep (talk) 11:08, 23 December 2012 (UTC)

"Aspiration (phonetics)" redirects to "Aspirated consonant"

Hi, whoever has the "magical" access to how (where?) this IPA template converts IPA notation to Wikipedia article links to associated phonetics articles needs to update whatever displays the results at Template:IPAsym/check_all for all the IPA symbols/notation that link to Aspiration (phonetics) as that is now a redirect to Aspirated consonant. Thanks, Bumm13 (talk) 22:41, 30 December 2012 (UTC)

Thanks. Your compliments, from inside knowledge, are received happily. -DePiep (talk) 22:52, 30 December 2012 (UTC)

Sorry if I came off sounding sarcastic, as it wasn't intended. No changes have occurred to IPA notation types that "dynamically" link to Aspiration (phonetics). I came across this issue at the Yale Romanization#Initials page (the "xʰ" wikilinks). It'd be nice not to have to use redirects for those links, but I can't see how to make such changes myself. Bumm13 (talk) 23:03, 31 December 2012 (UTC)

OK, I could have read it that way. So you want [pʰ] to link to Aspirated consonant directly, no to the redirect Aspiration (phonetics). Done [3]. -DePiep (talk) 14:29, 1 January 2013 (UTC)

ʊ

So where do you get your info? The official chart I linked to says it's rounded. — Lfdder (talk) 09:46, 29 April 2013 (UTC)

The Handbook also calls it the "near-close near-back rounded vowel" (p. 180). — Lfdder (talk) 10:54, 29 April 2013 (UTC)

Interesting catch. File:IPA vowel chart 2005.png has it on the right side of a dot, so rounded. That would also imply that in Template:IPA_chart_vowels we have swapped into wrong the pair at near-close central? -DePiep (talk) 11:59, 29 April 2013 (UTC)

Well, kwami made that chart (probably). There's no dot on the official one. I think I put that on the other side just to hide the dot. — Lfdder (talk) 12:12, 29 April 2013 (UTC)

Protected edit request on 26 July 2013

Move the tpl and its talk page to 'IPA symbol', a much less cryptic name for this template. Or just unprotect it for a bit so we can get it done. — Lfdder (talk) 22:02, 26 July 2013 (UTC)

Not done: page move requests should be made at Wikipedia:Requested moves. --Redrose64 (talk) 22:28, 26 July 2013 (UTC)

(edit conflict)

• Agree. asap. Extensive discussion: [4]. Also requested at ANI: [5]. -DePiep (talk) 22:31, 26 July 2013 (UTC)

Request already was done as required: [6]. Sigh. -DePiep (talk) 22:37, 26 July 2013 (UTC)

Then why were those discussions not linked when the edit request was made? I'm not a mind reader. Declined, per this edit summary: if I wasn't pissed off then, I am now. --Redrose64 (talk) 22:45, 26 July 2013 (UTC)

By time moments (and before ce) you might be right. By content here, requesting editor Lfdder better had been rewarded for making sense. -DePiep (talk) 23:01, 26 July 2013 (UTC)

And it is WP:RM/TR. the requst stands. -DePiep (talk) 23:26, 26 July 2013 (UTC)

Front vs. central "a"

Apparently, the IPA link for "a" currently always goes to Open front unrounded vowel, in keeping with the definition of IPA "a" as that cardinal vowel. However, in practice, in the description of many (or most) individual-language phonologies, "a" tends to be used for vowels that are not distinctively "front" but central (or variable). We have a separate vowel article for this, Open central unrounded vowel, Would it be feasible to have a choice of link target here, so that "a" could be linked to the "central" rather than "front" article where appropriate? (Similarly for "e" and "o", which are often used in phonemic or broad phonetic notations to stand for "mid" rather than ""close-mid" variants.) Fut.Perf. ☼ 09:26, 9 January 2015 (UTC)

You do have a choice. If you want to link to the central [ä], you need to write "ä|" before "a}}". Same for the mid vowels - write "e̞|" and "o̞|" before "e}}" and "o}}", respectively. — Peter238 (v̥ɪˑzɪʔ mɑˑɪ̯ tˢʰoˑk̚ pʰɛˑɪ̯d̥ʒ̊) 13:54, 20 February 2015 (UTC)

This is finally a request to the IPA to acknowledge that there is an Open central unrounded vowel which indeed contrasts with either of the open cardinal vowels, and assign an own symbol to it. The latest attempt to have it done failed because too many authors and publishers apposed for sheer economic reasons, trying to avoid to have to revise and reprint their publications. I strongly support another symbol for various reasons but I am currently not a member of the IPA because I cannot afford to pay the steep membership dues :-( --Purodha Blissenbach (talk) 16:08, 21 February 2015 (UTC)

In which languages though? As far as I'm aware, only the Hamont dialect of Limburgish has a phonemic /a - ä - ɑ/ contrast. Which, indeed, should be enough. — Peter238 (v̥ɪˑzɪʔ mɑˑɪ̯ tˢʰoˑk̚ pʰɛˑɪ̯d̥ʒ̊) 20:23, 21 February 2015 (UTC)

Low German and Bavarian have at least /ä - ɑ/ contrasts and at least some Palatinean and Moselle Franconian varieties clearly have /a̙ - ä/ contrasts in addition to lenght contrasts on them. There are certainly many more. --Purodha Blissenbach (talk) 15:57, 23 February 2015 (UTC)

Overhaul

I've been thinking of ways to potentially improve this module, because it definitely is in need of improvement. Specifically:

• As I touched upon previously, it would be nice if we didn't have to mark tie bars, length marks etc. in the data. That would considerably reduce repetitive inputs and thus make the data easier to maintain. That is, we should be able to write e.g. "ts" and have the same effect as writing "ts", "t͡s", "t͜s".
• It is a pain in the butt that we have to add every single possible combination for syllabic, aspirated, palatalized, etc. We should be able to define just the diacritics and let the module figure out where it should link to.
• We need a way to overview the data, something akin to what we have at Module:IPAc-en/phonemes. That'll help detect errors like duplicates and red links.

The first one can be easily solved by automatically removing the tie bars, length marks, etc. from the string the module compares to the data. For the second, I think what we can do is set up a list of diacritics independent of the symbols for phones and make the module go through each character and see if it matches any diacritic—if no complete match was found.

So Module:IPA symbol/sandbox is what I came up with. The data has been turned into a numbered list instead of a named one because otherwise the order of the overview list would be all over the place due to Lua's limitations. I got rid of the IPA numbers and X-SAMPA, which no one used ({{Infobox IPA}} relies on these to some extent, but that can be easily replaced). The article name is now optional and the name property will replace it if not specified in the data. (So the module now relies on redirects to make sure symbols link to the right articles. This encourages WP:NOTBROKEN and helps eliminate cases where e.g. {{IPA link|l}} and Alveolar lateral approximant direct to different articles or sections. One tiny drawback of this is that some symbols in charts will no longer appear in bold on the very pages about them, but this has been the case for symbols that link to sections anyway.) It also implements {{IPA link}} etc., which helps reduce server resource.

Some samples can be found at Template:IPA symbol/testcases. If no one has a problem I plan to implement it in a few days. Nardog (talk) 17:46, 26 January 2019 (UTC)

@Nardog: All of this sounds good to me. Coincidentally, I'm also thinking about removing the tie-bar from (some of) our phonology articles. Transcriptions with it aren't really more correct and the tie-bar can rather annoyingly encroach on the space belonging to the primary stress mark, if this makes sense.

Although I think I'd leave the length marks as they are. Kbb2 (ex. Mr KEBAB) (talk) 18:00, 26 January 2019 (UTC)

What do you mean? Now e.g. {{IPA symbol|aː}}, {{IPA symbol|aˑ}}, or even {{IPA symbol|aːˑ}}, {{IPA symbol|aːː}}, etc. returns "Open front unrounded vowel" even though they are not defined in /data because the module removes the length marks from the string to be compared to each symbol in the data. Nardog (talk) 18:09, 26 January 2019 (UTC)

@Nardog: Oh, that's how it's gonna work. In that case, I have no objections. Kbb2 (ex. Mr KEBAB) (talk) 12:56, 27 January 2019 (UTC)

How to avoid superfluous HTML tags

Enclosing {{IPA link}} in {{IPA}} is inelegant because it results in unnecessary nested HTML tags with the same class. For instance, {{IPA|[{{IPA link|a}} ~ {{IPA link|æ}}]}} (an example from Catalan phonology) results in <span title="Representation in the International Phonetic Alphabet (IPA)" class="IPA">[<span class="IPA">[[Open front unrounded vowel|a]]</span> ~ <span class="IPA">[[Near-open front unrounded vowel|æ]]</span>]</span>, with nested span tags both with the IPA class. This should be <span title="Representation in the International Phonetic Alphabet (IPA)" class="IPA">[[[Open front unrounded vowel|a]] ~ [[Near-open front unrounded vowel|æ]]]</span>.

Two ways to achieve this occur to me: an IPA link template that does not add the IPA class, or a template in which some syntactic construction can be processed into a link to the page about a phone. For instance, if a pair of braces were used to enclose the things that should be linked, the syntax for the example above would be {{IPA linker|{a} ~ {æ} }}. (That's just an example; obviously braces aren't a good choice because they conflict with template syntax.) The special link syntax method would be briefer, but the non-HTML-adding template method would be less obfuscatory, I guess. — Eru·tuon 01:59, 8 February 2019 (UTC)

Your suggested solutions strike me as a bit of overkill because the problem is just redundancy and doesn't present actual harm or inconvenience, and is not even particularly common (the regex search /\{\{IPA\|[^\}]*\{\{IPA ?link/ just returned only 6 articles). How about an option like |class=no which cancels the IPA class? Nardog (talk) 02:30, 8 February 2019 (UTC)

Huh, I got 237 results for hastemplate:"IPA link" insource:/\{\{IPA\|[^\}]*\{\{IPA ?link/, and 59 for hastemplate:"IPAlink" insource:/\{\{IPA\|[^\}]*\{\{IPA ?link/.

The more complicated HTML could cause problems with JavaScript or CSS that operates on the IPA class, but I'm not aware of any actual issues right now. (I have CSS that applies fonts to IPA and it works just fine.) It's more of a coding style issue.

A parameter does sound like a simpler solution. — Eru·tuon 11:59, 8 February 2019 (UTC)

Ah, I was doing /\{\{IPA[^\}]*\{\{IPA ?link/ instead of /\{\{IPA\|[^\}]*\{\{IPA ?link/ (which still doesn't explain why it returns fewer results though). hastemplate:IPA hastemplate:Module:IPA_symbol insource:/\{\{IPA\|[^\}]*\{\{IPA.?link/ probably returns all of the desired results. I'll implement |span=no (because, now that I think about it, it would cancel the span element altogether instead of just the IPA class) if that's okay. Nardog (talk) 12:31, 8 February 2019 (UTC)

On second thought, a dedicated template for plain links is certainly much simpler. I suggest "IPAplink" as the name. Nardog (talk) 17:12, 8 February 2019 (UTC)

A separate template would certainly make the wikitext easier to read. I don't have any better ideas for the name. As long as there's nothing else with the initial "p" that would need the name, it works. — Eru·tuon 00:46, 9 February 2019 (UTC)

Y Created {{IPAplink}}. Nardog (talk) 07:32, 9 February 2019 (UTC)

Thanks! I've started adding it. It needed a <nowiki /> or something like that at the beginning, so that when it's placed after a left square bracket ({{IPA|[{{IPAplink|blah}}]}}), the parser doesn't see [[[ and fail to generate a wikilink. — Eru·tuon 09:38, 9 February 2019 (UTC)

• I'm not completely in the light here, but I saw an edit like this, and that strikes me as an overcomplicated solution. If the wikicode has something like "{{IPA|[{{IPA link|a̠}}}}", isn't it better for everyone to simply trim it down to {{IPA link|a̠}}? And if it is important to have the span element have a title saying this is in IPA, then shouldn't that be produced by default from {{IPAlink}}? – Uanfala (talk) 02:33, 27 February 2019 (UTC)

  @Uanfala: I prefer having the brackets or slashes enclosed in {{IPA}} so that they are tagged with class="IPA" along with the stuff inside the bracketing. That means {{IPA|[{{IPAplink|...}} ...]}}. That is how other IPA transcriptions that do not contain IPA links are formatted. The brackets are enclosed in {{IPA}}: {{IPA|[...]}}, not [{{IPA|...}}]. (I tend to notice when this isn't the case because of my personal CSS.) When there isn't any bracketing (as in the table in the diff from Shiwiar language), it makes sense to remove {{IPA}} and switch to {{IPA link}} (diff). — Eru·tuon 04:46, 27 February 2019 (UTC)

  OK, I see. But it still feels like {{IPA|[{{IPAplink|...}} ...]}} is way too much code for that benefit. A gain in html tidiness, yes, but to a cost in wikicode readability. Isn't there a way to make {{IPAlink}} accept brackets, so that something like {{IPAlink|[q]}} can have the same output as {{IPA|[{{IPAplink|q}}]}} I'm assuming that a lot (or most?) of the uses of IPAlink are for single characters and so it will be worth it to expand the functionality of the template. – Uanfala (talk) 05:00, 27 February 2019 (UTC)

  {{IPAblink|q}} is equivalent to {{IPA|[{{IPAplink|q}}]}}. {{IPAplink}} is only for when {{IPA|...}} contains multiple links but only one set of brackets. Nardog (talk) 14:26, 27 February 2019 (UTC)

  Oh, I wasn't aware of the existence of this template, and this only shows how little I edit in this area. So, please correct me if I'm overlooking something else again, but surely we don't need a different template for each type of bracket? Template:IPA symbol uses Lua, so it shouldn't be too difficult to let let it accept (and output) brackets, but simply trim them away when looking up the symbol? – Uanfala (talk) 22:21, 27 February 2019 (UTC)

  Why not? The whole point of a template is to reduce repetitive inputs. {{IPAslink|a}} is much simpler than {{IPA link|/a/}} and the module going out of its way to internally remove the brackets. Nardog (talk) 08:36, 2 March 2019 (UTC)

  Because sparing editors the effort to type one, at most two, characters in this way creates extra complexity: learning about these three additional templates is not a big deal for the (probably not many) editors who want to use them, but they'll have to also be reckoned with by the much wider group of users who edit the pages they're used on. And slashes and brackets are displayed characters, so it's a bit counter-intuitive to effectively hide them from the wikicode using a dedicated template. For the module to internally remove the brackets is going to take one extra line of code, which I presume is not going to be terribly expensive computationally. – Uanfala (talk) 15:42, 2 March 2019 (UTC)

Aspirated consonants

Link calls like {{IPA symbol|t͡ɕʰ}} seem to produce a hyperlink to Aspirated consonant rather than to e.g. Voiceless alveo-palatal affricate. Is this the intended behaviour? It seems like it might be more useful to link the ʰ to Aspirated consonant and link the t͡ɕ to Voiceless alveo-palatal affricate. 158.132.130.179 (talk) 09:23, 21 September 2019 (UTC)

Use {{IPA link|t͡ɕ|t͡ɕʰ}} if you want to link to Voiceless alveolo-palatal affricate instead of Aspirated consonant while retaining the appearance. Use {{IPA link|t͡ɕ}}{{IPA link|ʰ}} if you want to link to both. Nardog (talk) 15:15, 21 September 2019 (UTC)

Automatic replacement of g with ɡ

The module already interprets g as a voiced velar stop, but I think it would be nice if it could go a step further and substitute g for ɡ when displaying the symbol. E.g., if I type {{IPA link|g}}, it would be nice if it output "ɡ" instead of "g". Similarly, it could automatically replace : with ː. פֿינצטערניש (Fintsternish), she/her (talk) 18:59, 10 January 2020 (UTC)

Prestopped / prenasalized

This template bundle currently ends up linking noncoronal prenasalized stops, if transcribed with ⁿ (not ᵐ / ᵑ / etc.) rather to nasal release: compare ⁿg with ⁿd, ᵑg. --Trɔpʏliʊm • blah 23:41, 18 January 2022 (UTC)

Why shouldn't it? The places of ⟨ⁿ⟩ and ⟨ɡ⟩ don't match, and the value of ⟨ⁿ⟩ is explicitly defined on the IPA chart as nasal release whereas its use for prenasalization is only implicit (or TBD). Accounting for combinations where places don't agree would be overkill. If it must be ⟨ⁿ⟩ for some reason, you can write {{IPA link|ᵑɡ|ⁿɡ}}. Nardog (talk) 07:41, 19 January 2022 (UTC)

Extended-confirmed-protected edit request on 14 April 2022

Add audio to voiceless retroflex lateral affricate Thatrustam (talk) 18:14, 14 April 2022 (UTC)

I want my audio file to be added between lines 888 and 889. Voiceless_retroflex_lateral_affricate.ogg

 Not done: This is not a lateral affricate. Nardog (talk) 18:22, 14 April 2022 (UTC)

How would you classify this sound? Thatrustam (talk) 18:30, 14 April 2022 (UTC)

I don't know exactly, but the fricative component doesn't sound like a lateral and more like an alveolar fricative, and it certainly doesn't match the way it sounds when I try it (and hear it back). If someone else agrees that's how a voiceless retroflex lateral affricate sounds then they can process this request though. Nardog (talk) 18:35, 14 April 2022 (UTC)

In my opinion, the stop part resembles the sound K — retroflex consonants can sometimes sound like velars. It is problematic to first pronounce a clearly retroflex T, and then move tongue to the alveolar fricative.

I don't mind waiting for another moderator. If need to improve the quality of the audio, I can re-record. Thatrustam (talk) 18:50, 14 April 2022 (UTC)

Extended-confirmed-protected edit request on 5 August 2022

Add File:Voiceless linguolabial fricative.ogg to the entry for the Voiceless linguolabial fricative. Vintium0 (talk) 17:57, 5 August 2022 (UTC)

 Done Nardog (talk) 19:43, 5 August 2022 (UTC)

Additions

@Theknightwho: Please observe WP:BRD. This is a page transcluded by thousands of pages so frequent edits are disruptive. The current iteration is already a drastically reduced set because it got bloated and difficult to maintain (see history). ⟨n˗⟩ etc. especially make no sense as there is no interference with a descender. As the documentation says (in bold no less), you can always provide alternative in {{IPA link}}. Nardog (talk) 12:48, 18 November 2022 (UTC)

@Nardog Then we can reduce the number of combinations for certain symbols. That's still no reason to remove the majority of it. Theknightwho (talk) 12:54, 18 November 2022 (UTC)

No, you add what's needed. Mass additions are a solution in search of a problem. Nardog (talk) 12:56, 18 November 2022 (UTC)

Several of those symbols are already in use, and all you're doing is wasting my time by forcing me to add things piecemeal in the coming weeks, rather than getting it done now. In any event, this is not a large data module, and I have no idea why you think it is particularly difficult to maintain - we seem to manage perfectly fine with lots that are many times larger than this on Wiktionary. Theknightwho (talk) 13:04, 18 November 2022 (UTC)

Every time article structure changes, which does and will happen every now and then, the module needs to be worked out all over, which balloons the more symbols you add. If you need them so badly, demonstrate the need and seek consensus by all means. But I doubt you truly do because, again, you can always use two parameters in {{IPA link}}. Nardog (talk) 13:15, 18 November 2022 (UTC)

Why would the data module need to be reworked with article structure, when it contains fixed information that is pegged to the IPA standard for the most part? If your concern is ensuring that links go to the right place, then you should be adjusting the redirect pages - not fudging the module at the expense of functionality. Theknightwho (talk) 13:22, 18 November 2022 (UTC)

Addendum: with judicious use of the {{R avoided double redirect}} template on the relevant redirects, everything would all get automatically processed by a bot anyway. From having looked through the history, I see no evidence at all that major restructuring is genuinely necessary within the data module itself. No wonder you've been finding it such a chore. Theknightwho (talk) 13:36, 18 November 2022 (UTC)