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
2.8.1 [makeotf] ValueError: path is on drive c:, start on drive F: #602
Comments
mergeFonts is also broken. Call
|
I see two different issues in your reports. Your first comment shows a bug in makeotf, in that it should deal more gracefully with not being able to make a relative path between the temp file and the target path. I think makeotf should not attempt to do this when the files are on different drives. The second issue shows that mergeFonts does not recognize 'm_NOTDEF.map' as a mapping file. mergeFonts works on my system, so I suspect that the expected text is not present in the mapping file, that would cause it to be recognized as such. Did you follow the rules described in the output from 'mergefonts -h'? |
@LIXiangChen I'm working on a fix to the |
All the tools' names were changed to all-lowercase in #511 (v2.8.0) |
@miguelsousa Yes, that's exactly |
Return the original path when it can't be made relative because the paths are in different drives/mounts Fixes #602
Return the original path when it can't be made relative because the paths are in different drives/mounts Fixes #602
My Python was installed on C, and font project files are in a path on F. Execute
makeotf -f "font.ps" -fi "fontinfo" -ff "../table" -ch "../../_CMap/CJK-UTF32-H" -cs 25 -cl 33 -omitMacNames -r -nS
is all good in 2.7.2, but in 2.8.1 will return:The text was updated successfully, but these errors were encountered: