You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From my (limited) experience, the implementation is very picky and hard to debug, since every locale only supports a subset of the IPA phones, and the tag is completely ignored as soon as there's just one unsupported character in the ph attribute. The validation of ph would be a very useful feature, but also very complex. Maybe this should be a separate issue, or even be outsourced to a separate library?
Just a clarification: the "this archived page" link was only relevant to the feature being in beta / being out of beta. This context got lost during issue splitting. The current version of the API documentation is here.
Splitting this off from #12
From my (limited) experience, the implementation is very picky and hard to debug, since every locale only supports a subset of the IPA phones, and the tag is completely ignored as soon as there's just one unsupported character in the ph attribute. The validation of ph would be a very useful feature, but also very complex. Maybe this should be a separate issue, or even be outsourced to a separate library?
see this archived page) for more details
The text was updated successfully, but these errors were encountered: