[precis] Applying the rules three times to get a stable output string?

Christian Schudt <christian.schudt@gmx.de> Sat, 09 December 2017 15:37 UTC

From: Christian Schudt <christian.schudt@gmx.de>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <C64B78C6-8109-4F36-BB76-EA8AB229FCE2@gmx.de>
Date: Sat, 09 Dec 2017 16:37:01 +0100
To: precis@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/6_DJZ9IsDrfBmhGz897LO3V78Os>
Subject: [precis] Applying the rules three times to get a stable output string?
Precedence: list

Hi,

RFC 8264 introduced these new sentences:

   under certain circumstances, such as when Unicode
   Normalization Form KC is used, performing Unicode normalization after
   case mapping can still yield uppercase characters for certain code
   points

   Therefore, an implementation SHOULD apply the rules
   repeatedly until the output string is stable


I could imagine these sentences refer to code points of the „Unstable“ category, but this category is unused.

Are there any concrete code points or input strings which show this unstable behaviour?
I am asking for some test vectors, i.e. an input string, which doesn’t have the expected output string after the first rule application, but after the second one.

Thanks,
— Christian

[precis] Applying the rules three times to get a … Christian Schudt
Re: [precis] Applying the rules three times to ge… William Fisher
Re: [precis] Applying the rules three times to ge… Christian Schudt
Re: [precis] Applying the rules three times to ge… William Fisher
Re: [precis] Applying the rules three times to ge… Christian Schudt