<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><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#c5">Comment # 5</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 <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
<pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=111816#c2">comment #2</a>)
<span class="quote">> 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.
>
> However, the same happens when search is active and I suggested to disable
> the value fields in this case.</span >
@Heiko--I just have to say how ill-considered that statement is--especially as
you've already unilaterally had Akshay remove the "Characters:" edit view
destroying a functional IME we have had for inputting strings in alternate
language scripts.
And now you are saying that Unicode values are not important for search--and
for font selection. The Special Character dialog _is_ the sames as OS provided
quick access--it is _our_ visual interface for providing quick access.
Please give some thought to how we support polyglot users who are very
dependent on Unicode and need efficient tools for locating glyphs across font
families by Unicode name or Codepoint or Unicode subset.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>