- * is used for an EXACTFU node that contains at least one "ss" sequence in
- * it. For non-UTF-8 patterns and strings, this is the only case where
- * there is a possible fold length change. That means that a regular
- * EXACTFU node without UTF-8 involvement doesn't have to concern itself
- * with length changes, and so can be processed faster. regexec.c takes
- * advantage of this. Generally, an EXACTFish node that is in UTF-8 is
- * pre-folded by regcomp.c (except EXACTFL, some of whose folds aren't
- * known until runtime). This saves effort in regex matching. However,
- * the pre-folding isn't done for non-UTF8 patterns because the fold of
- * the MICRO SIGN requires UTF-8, and we don't want to slow things down by
+ * is used in non-UTF-8 patterns for an EXACTFU node that contains at
+ * least one "ss" sequence in it. For UTF-8 patterns, the procedures in
+ * step 1) above are sufficient to handle these, but for non-UTF-8
+ * patterns and strings, this is the only case where there is a possible
+ * fold length change. That means that a regular EXACTFU node without
+ * UTF-8 involvement doesn't have to concern itself with length changes,
+ * and so can be processed faster. regexec.c takes advantage of this.
+ * Generally, an EXACTFish node that is in UTF-8 is pre-folded by
+ * regcomp.c (except EXACTFL, some of whose folds aren't known until
+ * runtime). This saves effort in regex matching. However, the
+ * pre-folding isn't done for non-UTF8 patterns because the fold of the
+ * MICRO SIGN requires UTF-8, and we don't want to slow things down by