NFSL2001

[From the documentation](https://vuetifyjs.com/en/api/v-select/#props-items): > Can be an array of objects or array of strings. When using objects, will look for a title, value and disabled keys. This can be changed...

I'm not sure how to add support for this.... 😅 There seem to be a library that does that though: https://github.com/simoncozens/fontFeatures

Think I got it working now. Actually VFB module does have feature in it which surprise me for a sec there. I used the same parameter name as that.

Just wondering, should we pass the `do_gdef` and `doLookups` paramms in fontFeatures `unparse` to the extractor function?

@benkiel , CC @simoncozens

After a bit more messing around, I found out that -t *does* work without quotation marks. E.g. with the font given above in `WD-XL.zip`: ``` otf2otc -t head=0 -o WD-XL-test.ttc...

Escaping the space command with grave accent (`) works, but only for PowerShell. Caret (^) for Command Prompt does not escape the space. ``` > otf2otc -t CFF` =0 -o...

I have encounter this issue and require immediate help. The [Kangxi radicals](https://en.wikipedia.org/wiki/Kangxi_Radicals_(Unicode_block)) are all compatibility characters to their Unified Ideographs counterpart (e.g. U+2F00 `⼀` is equivalent to U+4E00 `一`). Same...

Thank you @punchcutter, the branch fix resolved the issue. I hope this get pushed to release soon.

I was on Windows 10 20H2. Trying to open a UTF-8 file when system is configured to GBK will make Python `open("filename")` containing non-ASCII characters results in the same 'gbk'...