Bugzilla – Bug 5407
Review jive_input for utf8 support
Last modified: 2011-01-17 09:54:49 UTC
I know some parts are slightly broken.
*** Bug 5491 has been marked as a duplicate of this bug. ***
Richard notes this is a real issue.
Do tell! Is this something we must fix for 7.0?
This is a potential crasher, it should be address if we have time. Otherwise it needs to be done for 7.0.1.
Reset priority
If this is not addressed for 7.0.1 then the utf8 characters need to be removed from the ALLOWEDCHARS_* strings for text input.
This won't be fixed for 7.0.1, I want to look at Pango for text rendering inside of rolling my own solution. Leaving this targeted for 7.0.1 as the utf-8 characters need removing from allowed strings.
Removed non-ascii characters from text input for 7.0.1 r2212. The original strings are kept in 7.1. Bumping this bug on to 7.1.
i have done a quick evaluation and using the ciaro and pango libraries looks to be the correct solution for this. a more in-depth investigation is needed, in particular looking at performance on jive.
Step 1 is to make the code UTF-8 save Step 2 would be to make the layout changes
bug 12416 has been created to cover jive_label and jive_textarea.
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the single original product.
*** Bug 10650 has been marked as a duplicate of this bug. ***
Reassigning to Richard for more info on what the issues are here.
The character wheel and text entry code it not utf-8 safe. This is needed esp. to support Russian keyboards.
current problems are not being fixed
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
We need to review when this change is done.
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Moving lower-priority bugs to next target