You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This weekly meeting will focus on display/markup elements, which have been discussed previously in #26 and #186. They are rather variably supported in our current spec proposals:
Questions that may be answered by this discussion:
Should display/markup elements be supported by the spec?
Should standalone elements be supported?
Should start/end pairs of elements be supported?
Should other connected sets of elements be supported? For example, a start/middle/end set of elements.
Should elements be separate from placeholders/formatting functions?
Should elements be used to mark up messages for formatting? For example, to indicate that a span should be styled bold.
Should elements be used to mark up messages for localisers? For example, to indicate that a span should not be translated.
Should some elements be supported by default?
If you have additional questions in mind, please post them in comments below. I'll send a poll about these to the mailing list in the next few days, to get a bit of a baseline on where we're starting from.
The text was updated successfully, but these errors were encountered:
Unicode MessageFormat WG - Weekly Meeting
Start time: 18:30 CET / 9:30 PT
Call : Link
Notes Link
This weekly meeting will focus on display/markup elements, which have been discussed previously in #26 and #186. They are rather variably supported in our current spec proposals:
Questions that may be answered by this discussion:
If you have additional questions in mind, please post them in comments below. I'll send a poll about these to the mailing list in the next few days, to get a bit of a baseline on where we're starting from.
The text was updated successfully, but these errors were encountered: