https://bugs.documentfoundation.org/show_bug.cgi?id=133918
--- Comment #13 from [email protected] <[email protected]> --- (In reply to Eike Rathke from comment #11) > Also note that this bug talked about two different things, one is typing > "in" that should match "Inglés" in Spanish UI and for some reason did not > and was changed to "id" instead; no adhoc idea why because BCP47 language > tag recognition only kicks in when no matching language list entry was > found. Once language tag recognition was hit though then the old ISO 639-1 > code "in" is correctly changed to "id" for Indonesian, there is no "id" code. I can see how what you describe would solve all issues - however, the behavior you described does not match what is actually happening. I'm not familiar with the inner workings of the text widget, but I would assume that the problem is that the BCP47 tag recognition is being triggered before checking for a matching language in the listbox, or that the text added by the listbox matching (eg. if I type "I" it completes to "Ilocano" with "locano" selected) is somehow not taken into account at some point of the process. I'm assuming there's no way that LanguageTag::isValidBcp47 could convert "Inglés (Australia)" (first matching entry for "in") to "id", right? (I would expect the function to extract everything up to the first hyphen, if any, then try and match with the BCP47 codes). In that case, the only reasonable explanation is that aStr does not contain the completed language. -- You are receiving this mail because: You are the assignee for the bug.
