New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle non-ASCII chars when returning inference results. #241
Comments
Thank you for the report. This is an issue with the text rendering specific only to our web-based SDKs, and is currently in our queue to fix. Desktop and other SDKs do not have this issue and render the correct UTF8 accented characters. |
Thank you for your fast reactivity on all the threads I opened until now 💯 |
@safsoun The returned slot strings in both console and in the web SDKs should now render the correct UTF8 characters. In the case of the web SDKs, please update to the latest versions of the |
Hello, I come back to this issue. It appears it was not fixed.. Still having non-ASCII characters. |
Hello, I am a little bit confused. You are saying the Picovoice Console shows the word "éteindre" correctly, whereas the board gives "C)teindre"? If that's true, I guess the software you are using to get data from the serial port probably has some issues with non-Ascii chars. what software did you use to monitor the serial output? |
Hello, Please consider this issue as resolved. Thank you. |
Hello,
After testing French language, the detection is working fine but the returned string from slots is "tricky" when the word contains symbols such as 'é', 'è' etc..
For example, for the word "éteindre", the returned slot string is "éteindre" which is not user-friendly!
I don't know how do you manage this, I propose to replace any letter of a specific symbol by its basic Latin letter, for example:
'é', 'è' -> e
à -> a
etc ..
PS: I tried to put the text "eteindre" instead of "éteindre" in the rhino console but the dictionary rejected the first one :-(
The text was updated successfully, but these errors were encountered: