<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Cannot find special character if does not know character name but number" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111816#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Cannot find special character if does not know character name but number" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111816">bug 111816</a> from <a class="email" href="mailto:rb.henschel@t-online.de" title="Regina Henschel <rb.henschel@t-online.de>"> Regina Henschel</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=111816#c2">comment #2</a>) > Very unlikely that you know the hex/decimal value but not within what font > you find the character. I'd say WF because search is not the same as quick > access, i.e. hex/decimal values. You can get a code point very easily, not only by searching in the unicode charts but by tools like <a href="http://shapecatcher.com/">http://shapecatcher.com/</a>. Of cause you can enter the character name (see below), but that is cumbersome compared with entering the number. It is likely, that you do _not_ know the font. For example write U+232c and toggle it to unicode. I bet, you get a benzene ring by font fall back. Now tell me which font it is and whether you own other fonts which have this character. (In reply to Heiko Tietze from <a href="show_bug.cgi?id=111816#c2">comment #2</a>) > However, the same happens when search is active and I suggested to disable > the value fields in this case. If you have entered the character name correctly and so the search is active, then scrolling the font list works, although the field does not show the correct number. It is good, that this works, so please make no changes, which would disable this feature.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>