Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ref:xbin [2018/02/04 01:01] – [See Also] digital man | ref:xbin [2018/02/06 21:19] – [History] Added alt/bright-palette versions of marilyn and sync disk demo images digital man | ||
---|---|---|---|
Line 7: | Line 7: | ||
- One or two font (character set) definitions | - One or two font (character set) definitions | ||
- | {{: | + | ===== Example ===== |
+ | ==== CT-XBIN.XB ==== | ||
+ | {{: | ||
+ | ==== The same file displayed without embedded font or palette data ==== | ||
+ | {{: | ||
===== Fonts ===== | ===== Fonts ===== | ||
Line 14: | Line 18: | ||
When one or more fonts are specified in the file, the file becomes tied to a specific //character height// (or what they call " | When one or more fonts are specified in the file, the file becomes tied to a specific //character height// (or what they call " | ||
- | For example, in the typical 80x25 video mode, an 8x16 character (font) is used. While in 80x43 video mode, an 8x8 character is used. So a character height of 16 pixels is most common | + | For example, in the typical 80x25 VGA video mode, an 8x16 character (font) is used. While in the 80x43 EGA/ |
There is no provision in the XBin file format for a single file to apply to multiple character heights (video modes). | There is no provision in the XBin file format for a single file to apply to multiple character heights (video modes). | ||
Line 41: | Line 45: | ||
SyncTERM supports up to **4 active fonts** simultaneously (selected by the 4 possible combinations of bits 3 and 7 of each displayed character' | SyncTERM supports up to **4 active fonts** simultaneously (selected by the 4 possible combinations of bits 3 and 7 of each displayed character' | ||
- | In any case, initial experiments using an ad hoc file format were encouraging. I was using SAUCE fields for most of the additional data needed (character height, number of fonts, etc.) and the basic BIN file format with additional data defining the font characters/ | + | In any case, initial experiments using an ad hoc file format were encouraging. I was using SAUCE fields for most of the additional data needed (character height, number of fonts, etc.) and the basic BIN file format with additional data defining the font characters/ |
- | I don't like reinventing | + | I don't like reinventing |
However, XBin only supports a maximum of 2 fonts (the so-called "512 char" mode detailed earlier). Some of my experimental XBin images required more than 2 custom font definitions (especially in 8-pixel character height video modes), even 4 custom fonts could be required at times. | However, XBin only supports a maximum of 2 fonts (the so-called "512 char" mode detailed earlier). Some of my experimental XBin images required more than 2 custom font definitions (especially in 8-pixel character height video modes), even 4 custom fonts could be required at times. | ||
- | So rather than create another file format that many useful software tools may never fully support, I decided to move forward using the XBin format, but add the functionality that I needed for my XBin Image (" | + | So rather than create |
- | {{:xbin_sync_disks.png?400|}} | + | {{:ref: |
{{: | {{: | ||
- | {{:xbin_marilyn.png?400|}} | + | {{:ref: |
{{: | {{: | ||