<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> <span class="fn">Heiko Tietze</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Insert Special Character arbitrarily restricts which characters in font can be inserted"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=112020">bug 112020</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
                
           </td>
           <td>philipz85@hotmail.com
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Insert Special Character arbitrarily restricts which characters in font can be inserted"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=112020#c5">Comment # 5</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED INVALID - Insert Special Character arbitrarily restricts which characters in font can be inserted"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=112020">bug 112020</a>
              from <span class="vcard"><a class="email" href="mailto:tietze.heiko@gmail.com" title="Heiko Tietze <tietze.heiko@gmail.com>"> <span class="fn">Heiko Tietze</span></a>
</span></b>
        <pre>Font substitution is another question. We made a suggestion how to improve this
situation at
<a href="https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/">https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/</a>

Talking about the special character dialog there is room for advanced features,
no question. While the average user searches by the unicode name <foo>, your
use case is to look for a particular unicode id <U+XYZ> not knowing in what
font it is defined. Once we have collected all these advanced functions we can
think about a second view, perhaps a tab or an expandable area, where those
could be added. But for now I believe our solution is superior to KCharSelect
for most users.</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>