From ee8dc9c3c808560b3c1317d55f61d752040fd50f Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Tue, 10 Oct 2023 19:06:04 -0500 Subject: [PATCH] CLDR-17141 kbd: keep transform=no but document it - don't name the special marker --- docs/ldml/tr35-keyboards.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/ldml/tr35-keyboards.md b/docs/ldml/tr35-keyboards.md index 0d38eb2e55d..3f5fcab775d 100644 --- a/docs/ldml/tr35-keyboards.md +++ b/docs/ldml/tr35-keyboards.md @@ -739,8 +739,9 @@ _Attribute:_ `output` _Attribute:_ `transform="no"` > The `transform` attribute is used to define a key that does not participate in a transform. -> Using this attribute causes the marker `\m{no_transform}` to be added after the key’s output. -> In other words, the following produce identical results: +> Using this attribute causes a marker to be added after the key’s output. +> In other words, the following produce the same results, except that the `\m{no_transform}` marker can be used by other parts of the keyboard in the second case. + > ```xml > > @@ -1702,7 +1703,7 @@ One strategy would be to use a marker, which won’t be visible in the output, b Pressing `caret` `e` will result in `^e` (with an invisible _no_transform_ marker). The `^e` won’t have the transform applied, at least while the marker’s context remains valid. -As a convenience, the above is exactly identical to: `` +As a convenience, the above will behave identically to: `` (except that the marker used isn't otherwise usable) Another strategy might be to use a marker to indicate where transforms are desired, instead of where they aren't desired.