XML talk:TSFF: Difference between revisions
Jump to navigation
Jump to search
Script 10k (talk | contribs) |
No edit summary |
||
Line 6: | Line 6: | ||
You could probably generate images of every glyph. | You could probably generate images of every glyph. | ||
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: http://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. | |||
::As for OniSplit handling a font file automatically, I don't think we can count on Neo adding frivolous functionality like that to OniSplit. I don't know if he is even planning on making any more releases. This is the sort of thing that normally a community would add to their primary modding tool, but in our case we don't even have a direct release of a recent version of the source code. That's why we would be better off trying to get Neo to open-source OniSplit than asking him for new features. I tried to contact him about this, but I don't think he checks his Yahoo email anymore. --[[User:Iritscen|Iritscen]] ([[User talk:Iritscen|talk]]) 17:15, 30 November 2016 (CET) |
Revision as of 16:15, 30 November 2016
Adding new fonts
Taking notes...
http://www.devasp.net/net/articles/display/139.html
You could probably generate images of every glyph. 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: http://www.acutesystems.com/fonts.htm. However for this we would need that Neo would add this functionality to OniSplit. 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.
- As for OniSplit handling a font file automatically, I don't think we can count on Neo adding frivolous functionality like that to OniSplit. I don't know if he is even planning on making any more releases. This is the sort of thing that normally a community would add to their primary modding tool, but in our case we don't even have a direct release of a recent version of the source code. That's why we would be better off trying to get Neo to open-source OniSplit than asking him for new features. I tried to contact him about this, but I don't think he checks his Yahoo email anymore. --Iritscen (talk) 17:15, 30 November 2016 (CET)