# Problem with UVS exported in UFO file

**URL:** <https://forum.high-logic.com/t/problem-with-uvs-exported-in-ufo-file/8476>\
**Category:** FontCreator - Bug Reports\
**Created:** [October 12, 2024, 5:08pm UTC](https://forum.high-logic.com/t/problem-with-uvs-exported-in-ufo-file/8476 "2024-10-12T17:08:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![NFSL2001](https://forum.high-logic.com/user_avatar/forum.high-logic.com/nfsl2001/32/9380_2.png) [@NFSL2001](https://forum.high-logic.com/u/NFSL2001)\
**Post date:** [October 12, 2024, 5:08pm UTC](https://forum.high-logic.com/t/problem-with-uvs-exported-in-ufo-file/8476/1 "2024-10-12T17:08:04Z")

</div>

In UFO lib.plist, the UVS sequences are separated for each VS codepoint. Eg:

```plaintext
<key>public.unicodeVariationSequences</key>
<dict>
    <key>FE00</key>
    <dict>
        <key>3001</key>
        <string>uni3001</string>
    </dict>
    <key>FE01</key>
    <dict>
        <key>3001</key>
        <string>uni3001.cpct</string>
    </dict>
    <key>FE00</key>
    <dict>
        <key>3002</key>
        <string>uni3002</string>
    </dict>
    <key>FE01</key>
    <dict>
        <key>3002</key>
        <string>uni3002.cpct</string>
    </dict>
</dict>

```

This is inefficient and could not be resolved correctly by other major UFO editors/compilers. The UFO standard specified:

> This key is a dictionary for Unicode Variation Sequences. Keys are Variation Selector code points as a hexadecimal numbers and values are dictionaries. These dictionaries contain \> **code points as hexidecimal numbers as keys and glyph names as values** \> .

The dictonaries for each VS codepoint should in theory contain all the Unicodes (since it mention “code points” and “glyph names” as plural). The suggested format should be as:

```plaintext
<key>public.unicodeVariationSequences</key>
<dict>
    <key>FE00</key>
    <dict>
        <key>3001</key>
        <string>uni3001</string>
        <key>3002</key>
        <string>uni3002</string>
    </dict>
    <key>FE01</key>
    <dict>
        <key>3001</key>
        <string>uni3001.cpct</string>
        <key>3002</key>
        <string>uni3002.cpct</string>
    </dict>
</dict>

```

See implementation of this format [LxgwWenkaiTC/sources/LXGWWenKaiTC-Light.ufo/lib.plist at af1621dc5a9bd08c50746861a3ad3bfdad9d8a56 · lxgw/LxgwWenkaiTC · GitHub](https://github.com/lxgw/LxgwWenkaiTC/blob/af1621dc5a9bd08c50746861a3ad3bfdad9d8a56/sources/LXGWWenKaiTC-Light.ufo/lib.plist#L1826-L1850).

---

<div class="post-metadata">

**Author:** ![ErwinDenissen](https://forum.high-logic.com/user_avatar/forum.high-logic.com/erwindenissen/32/9430_2.png) [@ErwinDenissen](https://forum.high-logic.com/u/ErwinDenissen)\
**Post date:** [November 8, 2024, 11:29am UTC](https://forum.high-logic.com/t/problem-with-uvs-exported-in-ufo-file/8476/2 "2024-11-08T11:29:55Z")

</div>

Thank you for making us aware of this. The next upcoming release will export Unicode Variation Sequences per the suggested format.