From 0fab6a2b5fcebe87d4f186a050f2b104427b6f11 Mon Sep 17 00:00:00 2001 From: ben Date: Sun, 18 Sep 2005 13:34:37 +0000 Subject: [PATCH] When documenting s0 and s1, get then the right way around. git-svn-id: svn://svn.tartarus.org/sgt/charset@6329 cda61777-01e9-0310-a592-d414129be87e --- iso2022.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/iso2022.c b/iso2022.c index 1853be7..726770d 100644 --- a/iso2022.c +++ b/iso2022.c @@ -191,10 +191,10 @@ static void read_iso2022(charset_spec const *charset, long int input_chr, /* dump_state(state); */ /* * We have to make fairly efficient use of the 64 bits of state - * available to us. Long-term state goes in s0, and consists of + * available to us. Long-term state goes in s1, and consists of * the identities of the character sets designated as G0/G1/G2/G3 * and the locking-shift states for GL and GR. Short-term state - * goes in s1: The bottom half of s1 accumulates characters for an + * goes in s0: The bottom half of s0 accumulates characters for an * escape sequence or a multi-byte character, while the top three * bits indicate what they're being accumulated for. After DOCS, * the bottom 29 bits of state are available for the DOCS function -- 2.11.0