You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The setVersionMajor function in ufowrite.c is supposed to copy the major version number from a version string to a destination string, skipping leading zeros. However, when the major version is zero (e.g. 0.500), nothing will be copied and the destination string (dst) ends up being empty.
I encountered the issue that causes an empty value (nothing) being written to the versionMajor property of fontinfo.plist when exporting to ufo format with tx, which isn't valid:
<key>versionMajor</key>
<integer></integer>
I believe it could be fixed by something like this: tamcy@a36fc9e
Indeed this is what is happening in setVersionMinor. I am not familar with this repo good enough to contribute a test case so I'm not submitting a pull request.
The text was updated successfully, but these errors were encountered:
The
setVersionMajor
function inufowrite.c
is supposed to copy the major version number from a version string to a destination string, skipping leading zeros. However, when the major version is zero (e.g. 0.500), nothing will be copied and the destination string (dst
) ends up being empty.I encountered the issue that causes an empty value (nothing) being written to the
versionMajor
property offontinfo.plist
when exporting toufo
format withtx
, which isn't valid:I believe it could be fixed by something like this: tamcy@a36fc9e
Indeed this is what is happening in
setVersionMinor
. I am not familar with this repo good enough to contribute a test case so I'm not submitting a pull request.The text was updated successfully, but these errors were encountered: