Addison Phillips

Each string/substring should have a language and direction attribute (note that this is what W3C I18N is asking TC39 for with the maybe-terribly-named `Localizable` [proposal](https://github.com/w3c/i18n-discuss/blob/gh-pages/explainers/string-meta-explainer-402.md)). A `formatToParts` can produce a...

> Can't direction be derived from locale? Not entirely. Language information can be used as a fallback when no direction information is available, but we [don't think it is a...

@mihnita The older formatters return controls to elicit proper ordering of ambiguous sequences *within* a formatted string, such as a number (especially currency values) or date. The formatters do ***not***...

@mihnita Can you clarify: > There is still the question on how to deal convert the interior bidi chars to some kind of meta on "parts" If each "part" has...

I think that a given component should take care of its *interior* needs and then expose its own base paragraph direction. That way, if all the directions align you don't...

> It's not really covered by "invalid expression error" Why not? The description of that error is: > An Invalid Expression error occurs when a message includes an expression whose...

> I thought it was worth discussing. Totally worth the discussion.

This issue got mirrored to I18N's repo due to the `i18n-tracker` label and I dug around to find the reason for the tag in the IRC log above: > [...

I18N has added this issue to our agenda for our 2024-03-21 call. Keyboard cursor behavior is known to be complicated in a bidi context and we want to ensure that...

Agreed. I have some ideas for how to do this. I think this will be one topic for the virtual face-to-face or even post F2F (so late February/early March timeframe)....