|
Post by hukka on Nov 17, 2011 16:12:13 GMT 2
|
|
|
Post by RayRayTea on Nov 17, 2011 16:48:08 GMT 2
Hmm still the same message ("...NE Header").
|
|
|
Post by hukka on Nov 17, 2011 18:28:23 GMT 2
How about now? Found a couple more bugs - I'm actually surprised font loading worked on any computer at all.
|
|
|
Post by RayRayTea on Nov 18, 2011 5:33:40 GMT 2
...and hey yes it works now! Great!!! Thank you 2!
|
|
|
Post by hukka on Nov 18, 2011 6:08:14 GMT 2
...and hey yes it works now! Great!!! Thank you 2! Cool beans! Background for the bug: I use strings internally to contain the binary font data in Fony (which is kind of naughty, but there you are). This worked fine till I upgraded to Delphi 2010, which changed its default strings from simple one-byte-per-char to Unicode strings. While modifying the code to use the simpler strings again I had accidentally left a few declarations in strategic places to use Unicode strings. This seems to still have worked fine for most locales, but on Chinese (at least) Delphi was performing Unicode conversion on the strings containing the font data, "corrupting" bytes. I have now made all the "data" strings RawByteStrings, so their content should no more be mangled by Delphi.
|
|
|
Post by Spike on Nov 24, 2011 22:54:23 GMT 2
A nitpick for you! In 1.4.3, the menu bar and pulldown menus don't match the font specified in Display Properties. In 1.4.0.2, they did. Doesn't affect usability in the least.
|
|
|
Post by hukka on Nov 25, 2011 0:25:56 GMT 2
A nitpick for you! In 1.4.3, the menu bar and pulldown menus don't match the font specified in Display Properties. In 1.4.0.2, they did. Doesn't affect usability in the least. Good catch, will fix in next update.
|
|
|
Post by TaeWong on May 31, 2013 11:07:25 GMT 2
When you open up Raize, you get an error: Couldn't find a valid NE header.
|
|
|
Post by hukka on May 31, 2013 17:40:49 GMT 2
When you open up Raize, you get an error: Couldn't find a valid NE header. Sounds like a corrupt or non-Windows/non-bitmap font. You can send it to me if you want me to have a look.
|
|
|
Post by ant222 on Mar 4, 2017 21:13:09 GMT 2
I still have this problem in Fony 1.4.7. Could you help me? EDIT: Please, test with Terminus.
|
|
|
Post by hukka on Mar 5, 2017 2:15:59 GMT 2
I still have this problem in Fony 1.4.7. Could you help me? EDIT: Please, test with Terminus. I can confirm Terminus.fon doesn't load, I'll look into it. Do you also have problems loading any other fonts?
|
|
|
Post by ant222 on Mar 5, 2017 18:09:46 GMT 2
Thank you very much. Fony loads other fonts correctly, if I open them from a location other than the WINDOWS\Fonts directory or via "Open installed font."
Does this forum support e-mail notifications?
|
|
|
Post by juanitogan on Mar 12, 2017 7:54:14 GMT 2
The Raize font mentioned above can be found here: www.raize.com/DevTools/Tools/RzFont.aspIt's a legit Windows FON font that doesn't open in fony for me either. It's a better programming font than ProFont and Proggy, in my opinion, so it's worth looking at. I can see it is built with a Borland tool, so that would be the likely difference with most. The header looks pretty weird compared to others. But these are really just DLLs, as you know, so anything that flies with DLLs flies with FONs. To modify Raize for PICO-8 programming, I pulled it apart and reassembled it with mkwinfont before working on it in fony (so borrow mkwinfont's code if you like, though I doubt you need to), which I've updated and placed here: github.com/juanitogan/mkwinfontAnyhow, thank you for making fony. It's a far nicer tool for working on bitmap fonts than I had hoped to find.
|
|
|
Post by hukka on Apr 1, 2017 21:08:58 GMT 2
Does this forum support e-mail notifications? I thought it did, but I didn't get any when new posts were made in this thread, thus the delayed replies. Sorry about that! To modify Raize for PICO-8 programming, I pulled it apart and reassembled it with mkwinfont before working on it in fony (so borrow mkwinfont's code if you like, though I doubt you need to), which I've updated and placed here: github.com/juanitogan/mkwinfontThanks for the offer, I may end up borrowing some of the header parsing code. Thanks! Your github page has some apt critique about Fony. I think a total rewrite is in order - Fony's codebase is pretty terrible and as such it's frustrating to work with. I've learned rather a lot since! I'll start working on a crossplatform remake after I get my current project a little further.
|
|