Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: write mod times to extra file in data folder? #58

Open
frankrolf opened this issue Feb 8, 2019 · 3 comments
Open

Suggestion: write mod times to extra file in data folder? #58

frankrolf opened this issue Feb 8, 2019 · 3 comments

Comments

@frankrolf
Copy link
Contributor

frankrolf commented Feb 8, 2019

I would like to benefit from the speed of storing modification times, and therefore need to store them in the UFO. The current version of ufonormalizer stores them in layerinfo.plist (for glif files) and lib.plist (for fontinfo files). This creates unnecessary data changes in version control.

Would it be possible for all those strings to live in their own, self-contained file in the /data folder? (Similar to com.adobe.type.processedHashMap)?

@typoman
Copy link

typoman commented Oct 9, 2019

This would be very nice, since every time a UFO is normalized but not changed, then still we get extra data in the diff that is distracting.

@frankrolf
Copy link
Contributor Author

I’ve moved to just not ever write the mod times – which makes #43 a reasonable suggestion.

@benkiel
Copy link
Contributor

benkiel commented Oct 10, 2019

PRs welcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants