*.OE4 Font File Headers
The following headers exist in the font file type *.oe4 you can see from the following template where the headers are featured this is the base level system of generating at OE4 Font File the template looks like:~
--[ Global Allocations ]------------------[ %MD55678901234567890123456789012 ]--
%globalallocation
--[ Header ]------------------------------[ %MD55678901234567890123456789012 ]--
%asciiart
+------------------------------------------------------------------------------+
| * * |
| Font Name: %font |
| Font Version: %vr |
| Font Licenses: %lics |
| |
| Company Name: %name |
| Company URL: %url |
| Company eMail: %email |
| |
| Generated By: https://github.com/Chronolabs-Cooperative/OE4... |
| Generated Version: 1.0.1 |
| * * |
+--------------------------------[ Chronolabs Cooperative + Undo Corporation ]-+
--[ Character Sets ]----------------------[ %MD55678901234567890123456789012 ]--
--[ %charset Allocations ]----------------[ %MD55678901234567890123456789012 ]--
--[ FontInfo Allocations ]----------------[ %MD55678901234567890123456789012 ]--
--[ Licenses Allocations ]----------------[ %MD55678901234567890123456789012 ]--
--[ FontInfo Data ]-----------------------[ %MD55678901234567890123456789012 ]--
--[ Licenses Data ]-----------------------[ %MD55678901234567890123456789012 ]--`
--[ %charset Data ]-----------------------[ %MD55678901234567890123456789012 ]--`
------------------------------------------[ yyyy/mn/dd hh:mm:ii ]------[ End ]--
The *.OE4 font file allows several different method of attack to downloading, for example a complete font all characters across many different character sets will make a file 200Mb+ the allocation system is to allow for the browsers for example to attack and download via part downloading the section of the file they require at the time, this would be through use of the Global Allocations at the start, allocations are a json section that outline the location in the file of individual components, it is also used for validating against the MD5 of the data to validate and certify the signature of the signed font file.
This is a JSON Data section that locates + the actual data in here length all the locations in the file of the headers for director or threaded part retrieval.
This is the header and the MD5 is of the ASCII art, when a program is generating this it can be the icon for the application or logo you don't have to ask the user each time what they want the ASCII Art to be. Partly why ASCII art is include to provider of verasity delegation unlike former earlier font formats, this is so there is ownership placed in imagery on the font data.
This is field separated data of all the character sets in the font file, it is code0::charset name zero||code1::charset name one the HTML ie. code is listed separated by two semi-colons and then the full name for the character set it listed.
This is the allocations table for the full name for the character set is listed where %charset is presented in the header for allocation of the character set data, used for validating signatures and certifying the signed font.
This is the validation allocation json data for the font information data, this is on run-time and used in conjunction with the MD5 of the Data table to certify the signed font file.
This is the validation allocation json data for the font licensing information data, this is on run-time and used in conjunction with the MD5 of the Data table to certify the signed font file.
This is font information data, it is separated by field separators of value-name-0::zlib compressed json zero||value-name-1::zlib compressed json one this includes all the data in pertinence to the header information and global settings for the font.
This is font licensing data, it is separated by field separators of license-code-0::zlib compressed json zero||license-code-1::zlib compressed json one this includes all the data in pertinence to the distribution licensing information and licensing for the font.
This is font character set physical character data; the full name for the character set is listed where %charset is presented in the header for actual data for the glyph in that character set, it is separated by field separators of 20::zlib compressed json chr(20)||45::zlib compressed json chr(45) this includes all the data in pertinence to the characters in numerical reference against the character set chart for this charset.
