[Libreoffice-bugs] [Bug 114549] The Special character didn't show in upper right window on Special Characters UI

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #13 from himajin100000 at gmail.com ---
(In reply to V Stuart Foote from comment #11)

> What is weird is that you can enter FEFC (or decimal 65276) and show "ARABIC
> LIGATURE LAM WITH ALEF FINAL FORM" from Arabic Presentation Forms-B, but
> moving into the Halfwidth and Fullwidth Forms and entering FF01 in the Hex
> field--the dialog returns missing glyph rather than FULLWIDTH EXCLAMATION
> MARK. A glyph which is shown in a cell on the font grid and that can be
> selected/inserted.
> 
> Other CJK glyphs in the font, and present on the grid of Arial Unicode MS,
> also show "Missing Glyph" when entered by Hex or Decimal value. Yet they can
> be selected/inserted from the grid with scroll and mouse click. 
> 

Actually, it does support and searchable when the settting in Comment 9 is set
appropriately. Instead of IPAexGothic, we can bring "Arial Unicode MS"; the
fonts that has hiragana subset.

>(from tdf#118681)
>- keyboard entry is not sequential, text cursor of input field jumps to start with each Hex pair. Makes it difficult to reliably enter the codepoint--and finding a glyph in the SMP (e.g. for Emoji) is a real chore

So far I have been unable to reproduce the unreliable input of codepoint, but
today I encountered a similar situation when I was testing on my PC.

I still haven't checked (and would not be able to check anytime soon because of
the compile error with VS 2017 15.8 Preview 3.0 and 4.0) whether this is the
cause, but U+3042 for example, the font for the middle dropdown needs to have
U+0030 and U+0304 for the reliable input and I have overlooked that when I
wrote the patch?

-- 
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/20180712/0167ad7e/attachment-0001.html>