[Libreoffice-bugs] [Bug 111816] New: Cannot find special character if does not know character name but number

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=111816

            Bug ID: 111816
           Summary: Cannot find special character if does not know
                    character name but number
           Product: LibreOffice
           Version: 6.0.0.0.alpha0+ Master
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: UI
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: rb.henschel at t-online.de

I use the special character dialog in its state in Version: 6.0.0.0.alpha0+
Build ID: f1a896c71c495bdef5861eb664581507b6b9b5bb
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86 at 42, Branch:master, Time: 2017-08-13_07:38:19
Locale: de-DE (de_DE); Calc: group

Situation: I want a double-struck A, I know the code point U+1D538, but I do
not know the character name and do not know which font has the character.

My Idea: I enter the code point into the field and scroll the font list.

Problem: If the current font does not has the character and I scroll the font
list using the arrow key, then the number is destroyed and therefore a wrong
subset is shown; even when I reach a font, which has the character.

The problem does not exists, when you start with a font, which has this
character. Then the number sticks and you can find other fonts, which have this
character too by scrolling the font list.

Help for testing: The fonts "Cambria Math", "DejaVu Sans", "DejaVu Serif",
"FreeSerif", "Linux Libertine G" or "STIX" contain the character. Of cause you
can use another character of the Plane 1 too for testing, e.g. U+1F609, an
Emoji.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170815/e75aed53/attachment-0001.html>