1,793
edits
XML talk:TSFF: Difference between revisions
m
changing link from http->https
(link fix and two new comments on the subject) |
m (changing link from http->https) |
||
| Line 7: | Line 7: | ||
Instead of saving these images, the pixels could be read and turned into int32 values... | Instead of saving these images, the pixels could be read and turned into int32 values... | ||
:More interesting than import them as text would be import them with font files: | :More interesting than import them as text would be import them with font files: https://www.acutesystems.com/fonts.htm. However for this we would need that Neo would add this functionality to OniSplit. [[User:Script 10k|Script 10k]] ([[User talk:Script 10k|talk]]) 10:53, 30 November 2016 (CET) | ||
::Paradox is talking about a way to generate arrays of ints to represent the glyphs' pixels. If you export TSFFTahoma to XML, you'll see that OniSplit generates a raw list of ints which could be replaced with the ints generated by that VB code. It also takes that XML back in with the -create command and generates the TSFF.oni file again. It's not elegant, but it might work. | ::Paradox is talking about a way to generate arrays of ints to represent the glyphs' pixels. If you export TSFFTahoma to XML, you'll see that OniSplit generates a raw list of ints which could be replaced with the ints generated by that VB code. It also takes that XML back in with the -create command and generates the TSFF.oni file again. It's not elegant, but it might work. | ||