Re sorts:
During this phase, I conducted extensive searches on the Internet for VGA glyphs and CONFIG.SYS tools, and also made countless experiments on VPC. Now, I summarize the following regarding the VTF code sequence and the storage order of glyph data:
1. Code sequence: Theoretically and practically, I have achieved ① loading at one time the glyph data of continuous or out-of-order codes (partial or all ASCII codes) and the glyph data of out-of-order codes (all ASCII codes), ② loading at two times the glyph data of left and right halves of glyphs respectively with continuous codes (partial or all ASCII codes), and ③ loading at n*2 times the glyph data of sequential or out-of-order codes (partial or all ASCII codes). These can all be easily achieved on the DOS command line, but as a device driver, there are many problems - ① and ② are okay, but ③ is not. Originally, the method of ③ can be the most convenient way to achieve the unification of various sequential codes, especially for programs where the driver and execution are combined into one (my goal).
2. Storage order of glyph data: The storage order of glyph data in the normal Chinese character system font library is set as 1, 2, 3, 4,..., 31, 32. The VTF glyphs need to be split into left and right halves each occupying one ASCII character position/code position, and the glyph data is divided into 1, 3, 5,..., 29, 31 and 2, 4, 6,..., 30, 32. The overall storage order of glyphs has ① stored continuously in the order of the ASCII character set, ② stored in the order area of the left half glyph plus the order area of the right half glyph, and ③ the order of hz1 left half glyph right half glyph plus hz2 left half glyph right half glyph plus... plus hzn left half glyph right half glyph (Chinese character internal code/code out-of-order) storage. Among them, the order of ③ is beneficial for programming with the Chinese character code out-of-order method and secondary utilization of glyph data in the program.
3. If the file size is not much considered, the entire 256-character set glyphs can be loaded at one time, which can be compatible with various code sequences and achieve a unified storage order, and can also realize the program where the driver and execution are combined into one (my goal).
The thoughts on automatic replacement will be described in another post.
During this phase, I conducted extensive searches on the Internet for VGA glyphs and CONFIG.SYS tools, and also made countless experiments on VPC. Now, I summarize the following regarding the VTF code sequence and the storage order of glyph data:
1. Code sequence: Theoretically and practically, I have achieved ① loading at one time the glyph data of continuous or out-of-order codes (partial or all ASCII codes) and the glyph data of out-of-order codes (all ASCII codes), ② loading at two times the glyph data of left and right halves of glyphs respectively with continuous codes (partial or all ASCII codes), and ③ loading at n*2 times the glyph data of sequential or out-of-order codes (partial or all ASCII codes). These can all be easily achieved on the DOS command line, but as a device driver, there are many problems - ① and ② are okay, but ③ is not. Originally, the method of ③ can be the most convenient way to achieve the unification of various sequential codes, especially for programs where the driver and execution are combined into one (my goal).
2. Storage order of glyph data: The storage order of glyph data in the normal Chinese character system font library is set as 1, 2, 3, 4,..., 31, 32. The VTF glyphs need to be split into left and right halves each occupying one ASCII character position/code position, and the glyph data is divided into 1, 3, 5,..., 29, 31 and 2, 4, 6,..., 30, 32. The overall storage order of glyphs has ① stored continuously in the order of the ASCII character set, ② stored in the order area of the left half glyph plus the order area of the right half glyph, and ③ the order of hz1 left half glyph right half glyph plus hz2 left half glyph right half glyph plus... plus hzn left half glyph right half glyph (Chinese character internal code/code out-of-order) storage. Among them, the order of ③ is beneficial for programming with the Chinese character code out-of-order method and secondary utilization of glyph data in the program.
3. If the file size is not much considered, the entire 256-character set glyphs can be loaded at one time, which can be compatible with various code sequences and achieve a unified storage order, and can also realize the program where the driver and execution are combined into one (my goal).
The thoughts on automatic replacement will be described in another post.
my major is english----my love is dos----my teacher is the buddha----my friends--how about U

DigestI
