Consider including updated Unicode data instead of relying on built in unicodedata

[justvanrossum]

Consider including updated Unicode data instead of relying on built in unicodedata

[punchcutter]

How about using what fontTools does: https://github.com/mikekap/unicodedata2

[justvanrossum]

Thanks! I'll have a look at unicode2.

I know FG's BiDi support is "weak" to say the least, but this is rather embarrassing.

My approach to BiDi and use of the python-bidi package should be on its way out, though, once I figure out how to address #35 (see latest comments).

[justvanrossum]

I've updated the FG code to use unicodedata2, but that doesn't solve the bidi issue, as python-bidi uses the builtin module. I could fork python-bidi, but given the more radical changes needed to fix #35 I'm not sure if that's worth it. Alternatively I could monkeypatch bidi.algorithm.

[justvanrossum]

Ok, I did the monkeypatching. I can push a release for you to try this out, or can you run from the source?

[justvanrossum]

Pushed v1.1.1, containing these fixes.

[punchcutter]

That looks good for the Unicode support side. Until next week when Unicode 13.0 is out and unicodedata2 needs to get updated again.

[justvanrossum]

Sure, I don't see how that can be avoided, though.

[punchcutter]

Yes, nothing to avoid, just one of those things to keep in mind. Not that there will be a ton of people working on Unicode 13 fonts right now, but I'm working on a couple Unicode 12 fonts which is how I ran into this so fast.

[justvanrossum]

Thanks for the report, it's much appreciated. I'll close this now. Please open a new issue if you find more, or reopen if you find the current fix/workaround is insufficient.