#1063 closed defect (bug) (maybelater)
translate.wordpress.org search is case-sensitive for non-English keywords
Reported by: | SergeyBiryukov | Owned by: | |
---|---|---|---|
Milestone: | Priority: | low | |
Component: | Translate Site & Plugins | Keywords: | |
Cc: |
Description
- Searching for "Название" produces 7 results:
The term name cannot be empty. | Название элемента не может быть пустым. |
Site Title & Tagline | Название и описание сайта |
New Link Category Name | Название новой рубрики ссылок |
New Category Name | Название новой рубрики |
New Tag Name | Название новой метки |
Software Name | Название платформы |
Site Title | Название сайта |
- Searching for "название" (same string in lower case) only produces one result:
A name is required for this term | Требуется название этого элемента |
I could not reproduce this on a standalone GlotPress install, so it appears to be specific to translate.wordpress.org.
Change History (9)
#3
@
9 years ago
I figured as much :) Any way to convert to UTF-8?
Having different results for the same term depending on the case is very unintuitive.
This ticket was mentioned in Slack in #polyglots by sergey. View the logs.
9 years ago
#6
@
8 years ago
- Resolution set to maybelater
- Status changed from new to closed
There are currently no plans for changing the charset to UTF-8, closing as maybelater,
#7
@
8 years ago
The "Case sensitive" checkbox should at least be disabled for non-Latin locales then, because it's currently misleading: the search is always case-sensitive for them, regardless of the checkbox.
#8
@
8 years ago
I've also noticed that search on translate.wordpress.org is case-sensitive for Cyrillic, even if the checkbox is left unchecked.
For example, "Главной" is not displayed when searching for "главной", and vice versa.
There are currently no plans for changing the charset to UTF-8, closing as maybelater,
Any chance to reconsider that?
Related: #394