Skip to content

Commit 58afcfa

Browse files
committed
Add note elaborating on what the directionality of the resolved value means
1 parent 08be4f6 commit 58afcfa

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

spec/formatting.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -938,6 +938,16 @@ The _Default Bidi Strategy_ is defined as follows:
938938
1. Let `fmt` be the formatted string representation of the _resolved value_ of `exp`.
939939
1. Let `dir` be the directionality of the _resolved value_ of `exp`,
940940
one of « `'LTR'`, `'RTL'`, `'unknown'` », with the same meanings as for `msgdir`.
941+
> [!NOTE]
942+
> _Resolved values_ need to track two different pieces of metadata about directionality:
943+
> the "isolate" flag (see the next step for how that is used), which determines
944+
> whether the formatted result needs to be isolated; and the directionality itself.
945+
> Each _function handler_ can have its own means for determining the directionality
946+
> of the _resolved value_ it returns.
947+
> Alternately, an implementation could elide this tracking and instead determine
948+
> the directionality from the locale.
949+
> The directionality SHOULD NOT be determined by introspecting
950+
> the character sequence in `fmt`.
941951
1. Let the boolean value `isolate` be
942952
True if the `u:dir` _option_ of the _resolved value_ of `exp` has a value other than `'inherit'`,
943953
or False otherwise.

0 commit comments

Comments
 (0)