-
Notifications
You must be signed in to change notification settings - Fork 12
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
invalid PostScript font name #1
Comments
I can't reproduce your problem, but get font files attached. Please check this. I have compiled bdf2ttf by MSVC10's 32bit compiler on WIndows 10, |
Thanks! 👍 Your generated fonts worked successfully in Linux FontForge and Windows 7. 💯 I should have mentioned that I compiled and ran bdf2ttf under Linux, using For your reference, here is my GCC information and compilation output:
|
There seems be bad assumption of bdf2ttf. bdf2ttf consider |
It would be better that use size aware types |
I have fixed for gcc. @sunaku please try again with recent version. |
Thanks @koron! 🙇 I tried the fix but the problem still occurs. 😞 I will try to debug it further. 👷 |
I tried rebuilding bdf2ttf for 32-bit architecture (my system is 64-bit): $ make gcc CFLAGS=-m32 LDFLAGS=-m32
make -f compile/Make_gcc.mak
make[1]: Entering directory '/home/sunny/lab/bdf2ttf'
cc -m32 -c -o src/bdf.o src/bdf.c
g++ -m32 -c -o src/bdf2ttf.o src/bdf2ttf.cpp
cc -m32 -c -o src/main.o src/main.c
cc -m32 -c -o src/rcfile.o src/rcfile.c
g++ -m32 -c -o src/table.o src/table.cpp
cc -m32 -c -o src/ucsconv.o src/ucsconv.c
g++ -o bdf2ttf src/bdf.o src/bdf2ttf.o src/main.o src/rcfile.o src/table.o src/ucsconv.o -m32
make[1]: Leaving directory '/home/sunny/lab/bdf2ttf' I still get the "Postscript font name" error in FontForge 😞 but at least the embedded bitmap fonts appear correctly now 😌 (previously FontForge rendered them as empty, red boxes). 👷 Next idea... |
I won'f fix about this. |
😅 Fair enough, thanks for your help! 🙇 |
Hello,
I tried using bdf2ttf to transform the Tamzen font into TTF, but when I double-click on the resulting TTF file under Windows 7, an error dialog appears saying "Windows Font Viewer: The requested file ... is not a valid font file.". Similarly, I'm getting an error message when opening the resulting TTF file in FontForge under Linux: 😞
In the above screenshot, that "|0003|" Unicode glyph at the end of the font name is suspicious.
Steps to reproduce the bug
Thanks for your consideration. 😅
The text was updated successfully, but these errors were encountered: