Yes, thank you, that answers the question. Format rather than
repertoire. Please note, though, that the example given of a
localizable message string is also an example of a localized sentence.
On 2020-01-10 11:17 PM, Steven R. Loomis wrote:
James,
A localizable message string is one similar to those given in the example:
English: “The package will arrive at {time} on {date}.”
German: “Das Paket wird am {date} um {time} geliefert.”
The message string may contain any number of complete sentences, including zero
( “Arrival: {time}” ).
The Message Format Working Group is to define the *format* of the strings, not
their *repertoire*. That is, should the string be “Arrival: %s” or “Arrival:
${date}” or “Arrival: {0}”?
Does that answer your question?
--
Steven R. Loomis | @srl295 | git.io/srl295
El ene. 10, 2020, a las 2:48 p. m., James Kass via Unicode
<unicode@unicode.org> escribió:
On 2020-01-10 9:55 PM, announceme...@unicode.org wrote:
But until now we have not had a syntax for localizable message strings
standardized by Unicode.
What is the difference between “localizable message strings” and “localized
sentences”? Asking for a friend.
