From fda7e0c1b59efcfbc2f124f4ee020602579b9e2f Mon Sep 17 00:00:00 2001 From: Eric MacDonald Date: Wed, 8 Sep 2021 21:48:48 -0400 Subject: [PATCH] Better formats --- zefie_wtvp_minisrv/WTVLzpf.js | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/zefie_wtvp_minisrv/WTVLzpf.js b/zefie_wtvp_minisrv/WTVLzpf.js index c3c8c75e..eba43f36 100644 --- a/zefie_wtvp_minisrv/WTVLzpf.js +++ b/zefie_wtvp_minisrv/WTVLzpf.js @@ -34,16 +34,16 @@ class WTVLzpf { /** * This is used to encode (one-byte) literals with no previous tracked occurence. * - * Bytes with best compression: SPACE and LF and e"/<>Tainoprst - * Bytes with good compression: TAB and ,-.1=ABCDEFGHILNOPRSbcdfghlmuw - * Bytes that don't change the length of the bit stream: 024:MW_kvy - * (The rest will increase the length of bit stream) + * - Bytes with best compression: SPACE and LF and e"/<>Tainoprst + * - Bytes with good compression: TAB and ,-.1=ABCDEFGHILNOPRSbcdfghlmuw + * - Bytes that don't change the length of the bit stream: 024:MW_kvy + * - The rest will increase the length of bit stream * - * I don't know what process they used to build this dictionary. - * I assume they frequency-scanned a bunch of HTML files they had. + * I don't know what process they used to build this dictionary. I assume they + * frequency-scanned a bunch of HTML files they had. * - * Using ISO-8859-1 chracter encoding. - * Didn't seem like they used a different dictionary for Japan builds (ISO-2022-JP). + * Using ISO-8859-1 chracter encoding. Didn't seem like they used a different + * dictionary for Japan builds (ISO-2022-JP). **/ nomatchEncode = [ /* [FLATTENED HUFFMAN CODE, CODE BIT LENGTH] */