Multiple encodings for 'Terminal'-workalike font
Sept 9, 2015 15:03:26 GMT 2
Post by largactyl on Sept 9, 2015 15:03:26 GMT 2
Hi,
I'm trying to create a font that would work like Windows' 'Terminal' font, more or less (in terms of encoding). Trouble is I can't really make sense of how the multiple Windows *and* DOS codepages are handled for a single font.
I'm actually sourcing my glyphs from several old DOS codepages; for a Terminal-like font, it looks like I should stick to "OEM/DOS" encodings anyway. Windows has multiple .FON files which map to the single font name "Terminal" - many of them with different DOS codepages, all specified as "DOS/OEM". Any idea what's going on 'under the hood' there?
I'm trying to create a font that would work like Windows' 'Terminal' font, more or less (in terms of encoding). Trouble is I can't really make sense of how the multiple Windows *and* DOS codepages are handled for a single font.
I'm actually sourcing my glyphs from several old DOS codepages; for a Terminal-like font, it looks like I should stick to "OEM/DOS" encodings anyway. Windows has multiple .FON files which map to the single font name "Terminal" - many of them with different DOS codepages, all specified as "DOS/OEM". Any idea what's going on 'under the hood' there?