Skip to content

Commit d031040

Browse files
authored
Allow expressions without annotations to dynamically choose a function
Fixes #42 Also addresses some problems with normative terms in the same text.
1 parent 5325158 commit d031040

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

spec/formatting.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -505,14 +505,17 @@ _Formatting_ is a mostly implementation-defined process,
505505
as it depends on the implementation's shape for resolved values
506506
and the result type of the formatting.
507507
508-
Formatting errors MAY be emitted during _formatting_,
509-
as formatting is not necessarily defined on every resolved value.
510-
A formatter MAY provide a value to use in such a case instead of a _fallback value_.
508+
Formatting is not necessarily defined on every resolved value.
509+
An implementation SHOULD emit formatting errors during _formatting_,
510+
but MAY provide a value to use in such a case instead of a _falback value_.
511511
512-
_Formatting_ MAY produce formatted messages with the following data types,
513-
as well as any others:
512+
An implementation MAY use the value of an _expression_'s _operand_
513+
to choose a _formatting function_ and default _options_ if no
514+
_annotation_ is supplied by the _expression_.
514515
515-
- A single concatenated string.
516+
Implementations MAY represent the result of _formatting_ using the most
517+
appropriate data type or structure. Some examples of these include:
518+
- A single string concatenated from the resolved _pattern_ and its parts.
516519
- A string with associated attributes for portions of its text.
517520
- A flat sequence of objects corresponding to each resolved value.
518521
- A hierarchical structure of objects that group spans of resolved values,

0 commit comments

Comments
 (0)