This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author PanderMusubi
Recipients PanderMusubi, ezio.melotti
Date 2012-12-14.21:20:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355520001.15.0.0129616207464.issue16684@psf.upfronthosting.co.za>
In-reply-to
Content
I myself have a lot of Python applications that process font files and interact with fonttools and FontForge, which are both written in Python too. As you also have your own dict for this purpose and probably other people too, it would be justified to add these three small dicts in the standard lib. Especially since this package in the standard lib follows the definitions from Unicode Consortium.

When this is shipped in one package developers will always have an in sync translation from abbreviated names to long names and vice versa. Over the last years I needed to adjust my dicts regularly for the added definitions by Unicode Consortium which are supported by stdlib.

At the moment, translation from Unicode codes U+1234 to human-readable Unicode names and vice versa is offered at the moment. Providing human-readable names for the property values is a service of the same level and will be catering to approximately the same user group.

If you agree that these dicts can be added I am willing to provide a script that will parse the aforementioned file.
History
Date User Action Args
2012-12-14 21:20:01PanderMusubisetrecipients: + PanderMusubi, ezio.melotti
2012-12-14 21:20:01PanderMusubisetmessageid: <1355520001.15.0.0129616207464.issue16684@psf.upfronthosting.co.za>
2012-12-14 21:20:01PanderMusubilinkissue16684 messages
2012-12-14 21:20:00PanderMusubicreate