<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Support ISO 14496-28 Composite Font Representation"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=96693">96693</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Support ISO 14496-28 Composite Font Representation
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>fontconfig
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>library
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>fontconfig-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>sascha@brawer.ch
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>freedesktop@behdad.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Could fontconfig support the Composite Font Representation of ISO 14496-28?
<a href="https://blogs.adobe.com/CCJKType/2012/04/cfr.html">https://blogs.adobe.com/CCJKType/2012/04/cfr.html</a>

At Google, we’re considering to release CFR files for grouping the myriad of
Noto fonts into a few families such as "Noto Sans", "Noto Serif", and "Noto
Mono". The total number of glyphs exceeds 64K, so we cannot just ship Noto Sans
etc. as one gigantic OpenType file. Instead, we need a mechanism for declaring
a virtual font. CFR has the advantage of being standardized. However, as of
June 2016, Apple is the only platform that implements CFR. But perhaps
fontconfig could follow Apple in that regard? Anyhow, here’s a draft CFR file
for Noto Sans, which might help to illustrate the CFR syntax:
<a href="https://github.com/googlei18n/noto-fonts/issues/707#issuecomment-224503236">https://github.com/googlei18n/noto-fonts/issues/707#issuecomment-224503236</a>

For downloading the official specification document (+errata) from ISO, search
for "14496-28" on this page:
<a href="http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html">http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html</a>

— Sascha Brawer, <a href="mailto:sascha@brawer.ch">sascha@brawer.ch</a> / <a href="mailto:sascha@google.com">sascha@google.com</a></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>