Open ali1234 opened 3 years ago
It will be difficult to handle X/28 and M/29 packets in the current codebase because there is no state for the Parser object. That is, it doesn't know what packets have been processed before or after the current one. For HTML it is less of a problem because it operates on whole pages only, but it still can't handle M/29 - but this can be implemented in Service fairly easily.
Currently that means for console output we are limited to allowing the user to select a "local code of practice" which is used for all packets. That seems fairly close to what level 1 does, and we don't really support higher levels anyway.
Codepage support currently only works for Latin/English and partial Cyrillic support. Latter has to be manually selected and doesn't work for console output - only HTML.
My understanding of how it works: