Skip to content

Commit 76ca624

Browse files
committed
Add note elaborating on what the directionality of the resolved value means
1 parent 38a2fea commit 76ca624

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
@@ -943,6 +943,16 @@ The _Default Bidi Strategy_ is defined as follows:
943943
1. Let `fmt` be the formatted string representation of the _resolved value_ of `part`.
944944
1. Let `dir` be the directionality of `fmt`,
945945
one of « `'LTR'`, `'RTL'`, `'unknown'` », with the same meanings as for `msgdir`.
946+
> [!NOTE]
947+
> _Resolved values_ need to track two different pieces of metadata about directionality:
948+
> the "isolate" flag (see the next step for how that is used), which determines
949+
> whether the formatted result needs to be isolated; and the directionality itself.
950+
> Each _function handler_ can have its own means for determining the directionality
951+
> of the _resolved value_ it returns.
952+
> Alternately, an implementation could elide this tracking and instead determine
953+
> the directionality from the locale.
954+
> The directionality SHOULD NOT be determined by introspecting
955+
> the character sequence in `fmt`.
946956
1. Let the boolean value `isolate` be
947957
True if the `u:dir` _option_ of the _resolved value_ of `part` has a value other than `'inherit'`,
948958
or False otherwise.

0 commit comments

Comments
 (0)