https://bugs.documentfoundation.org/show_bug.cgi?id=112267
--- Comment #14 from Eyal Rozenberg <[email protected]> --- > The question is whether or not it should also be possible to search by > localized names such as "Kreuz" in German or "Croix" in French. It should. English should not have preferential status w.r.t. labeling of characters. Either we have localized search-by-name, or we not have search-by-name at all. ... that is, except if this functionality is "outsourced". If we use some system facility / library to perform this search, then I would say that it is NAB, but we should then file relevant bugs with whoever provides us this functionality. (In reply to V Stuart Foote from comment #1) > _No_ just no! At Unicode ver 10.0 there are ~136,000 defined codepoints each > with a Unicode consortium approved "name". If you were to argue in favor of removing all of these names and the search-by-name functionality altogether, then ok. Otherwise, why should it be English? Our users, in the general case, do not know any English. And the more we have adoption in Asia and Africa the more true this will be. (In reply to Muhammet Kara from comment #9) > Speaking as a translator: I don't think it is possible (for us) to provide > translations for all those characters in the unicode table. Please distinguish "possible" with "reasonable to invest effort it". It actually is possible for translation teams to translate the names of all characters; it is just not something that's (probably) not worthwhile to invest in relative to most localization work. > > But in case we find a source of translated strings for those characters, > that would be fantastic. :) Such translations should indeed happen, and perhaps have already happened, irrespective of LibreOffice. Unicode is a widely-accepted international standard, and world states or even commercial enterprises whose work involves typesetting, standardization, catalogues of characterts etc. - may already have performed such translations, or are likely to do so in the future. The resolution of this bug could depend on such efforts, not just on ours. > So I see only one way to go: enable search for characters by their > hexadecimal number along with their English names. If you have the hex value, then it's more like specifying something than searching it, but regardless, being able to type the hex code in the search would also help. I would file a separate bug about that though. (In reply to Eike Rathke from comment #13) > That's unmaintained since 5 years. True, there was just one commit in there. But that one commit has a very large range of characters for several important languages: Amharic, Kinyarwanda, German, Finnish, French, Irish, Danish, Dutch, Polish, Serbian and Slovak. -- You are receiving this mail because: You are the assignee for the bug.
