-
Notifications
You must be signed in to change notification settings - Fork 76
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
what should demo look like? #26
Comments
It should kinda look like this: |
Then it failed utterly on my system. |
What platform / driver? |
linux 64-bit, gcc 7.1.0 glibc 2.26. |
Humm. That's the most corrupt I've seen the demo perform! No idea where to go from here. |
Maybe I'm missing the font that you use? |
I'm hoping to get this resolved before I build libreoffice |
No, there's no way you should get what you are getting.
Oh, does libreoffice use GLyphy after all? I thought that was abandoned. |
I don't really know, except to say that the BLFS (beyond linux from scratch) book says that glyphy is optional for LO. What can I do to help narrow down the cause? |
If you just want to move on with building your system, just skip GLyphy. It's not a strict requirement of anything. |
I understand that, but it sounds like a neat thing to have. The way my system is rendering fonts now seems a little off (they look clearer is some areas than others, probably due to where the pixels are relative to the glyphs. I'm not explaining it well.) |
Anyway, you were right, and the BLFS book was wrong. LO did NOT want to include glyphy. |
this could be a incorrect font file? eg #37 |
What should the demo look like?
I can see no discernible text in it. Just lines tightly packed together.
Is this how it /should/ look?
The text was updated successfully, but these errors were encountered: