Open hypetsch opened 3 years ago
Related to #718 however since this is a "smart select" popup, the searchbar's removeDiacritics is set to the default true
(changed in https://github.com/framework7io/framework7/commit/50f49754246fd6bd72cf87229bdaade68b840695) and AFAIK it's not possible to control it
I noticed it too, this information comes from the API (e.g. /rest/services
and I agree it should probably use the configured locale right away after it's changed - maybe @openhab/core-maintainers know why it doesn't/whether it can be improved. In any case if you restart OH the locale will be applied, if I'm not mistaken.
I agree it should probably use the configured locale right away after it's changed
IMHO it would be better if the configured locale is only used as fallback. Other REST operations determine the locale based on the Accept-Language
request header. That's also why you currently end up with mixed translations if you don't set the openHAB default locale to the same language as your browser. I.e. the backend should always use LocaleService.getLocale(acceptLanguageHttpHeader)
when such headers are available instead of LocaleProvider.getLocale()
.
Could we at least make use of some override function since I really wouldn't want to just use another browser extension to send Acccept-Langugage header to Openhab for being able to follow some tutorials which are most likely written in English.
The problem
The following issues where found in the "Regional Settings" section but may also apply to other elements.
1) Regional Settings > Land/Region: Searching for some characters does not yield an expected result (Browser language set to "German"). e.g. searching for "Öster" is missing "Österreich". A similar issue happens when searching for "Ä" which yields results without any "Ä". See also 3)
2) The scrollbar is hidden by the popup header:
3) The configured language is not consistently used. Although "English" is configured, some UI elements are still shown in German (even after page reload - probably by design?). When switching the browser to "English", the behavior of issue 1) is different; just a guess, but it looks a bit like the search is not using the translated entries?
Expected behavior
Your environment