This patch ensures that feaLib always produces a name table with entries sorted in the order proscribed by the spec: platform id, encoding id, language id, name id. This breaks some tests, and so I have manually updated the test data to match the new outputs.
41 lines
1.2 KiB
XML
41 lines
1.2 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<ttFont>
|
|
|
|
<name>
|
|
<namerecord nameID="8" platformID="1" platEncID="0" langID="0x0" unicode="True">
|
|
Test8
|
|
</namerecord>
|
|
<namerecord nameID="10" platformID="1" platEncID="0" langID="0x0" unicode="True">
|
|
Test10
|
|
</namerecord>
|
|
<namerecord nameID="11" platformID="1" platEncID="0" langID="0x0" unicode="True">
|
|
Test11
|
|
</namerecord>
|
|
<namerecord nameID="1" platformID="3" platEncID="1" langID="0x409">
|
|
Test1
|
|
</namerecord>
|
|
<namerecord nameID="2" platformID="3" platEncID="1" langID="0x409">
|
|
Test2
|
|
</namerecord>
|
|
<namerecord nameID="3" platformID="3" platEncID="1" langID="0x409">
|
|
Test3
|
|
</namerecord>
|
|
<namerecord nameID="4" platformID="3" platEncID="1" langID="0x409">
|
|
Test4
|
|
</namerecord>
|
|
<namerecord nameID="5" platformID="3" platEncID="1" langID="0x409">
|
|
Test5
|
|
</namerecord>
|
|
<namerecord nameID="6" platformID="3" platEncID="1" langID="0x409">
|
|
Test6
|
|
</namerecord>
|
|
<namerecord nameID="7" platformID="3" platEncID="1" langID="0x409">
|
|
Test7
|
|
</namerecord>
|
|
<namerecord nameID="9" platformID="3" platEncID="1" langID="0x409">
|
|
Test9
|
|
</namerecord>
|
|
</name>
|
|
|
|
</ttFont>
|