Thanks for the reply, Erin. The problem with the hyphenation API is that for the inflected forms, it returns not an empty result, but a *wrong* one. Here's the response for the word "confused":
If the response were an empty array, then it would be clear that I need to take other steps, like using the "related words" API to find the root form, etc. But since it returns an incorrect result, I now have to be suspicious of any response that returns just a single syllable.
My scenario is a custom dictionary UX based on the "color vowel
" teaching methodology. Each word in the dictionary is color-coded based on the vowel sound of the stressed syllable in the word. Also, I want to underline the stressed vowel in the word. The pronunciation API gives me the vowel sound of the stressed syllable, but the hyphenation API is critical for being able to underline the correct letters in the stressed syllable.
In cases where I can't get correct hyphenation for an inflected form, I'll have to instead show users the root form, which is okay (but not great). But the current behavior of the hyphenation API makes it hard, since any single-syllable response is possibly wrong.
It sounds like the fix might be a one-line change somewhere in the API - to just return an empty array rather than the entire word as a single syllable.