Charts (rough cut)

[Marcel Schneider via CLDR-Users]

On 22/08/18 08:39, Mark Davis ☕️ via CLDR-Users wrote:
> 
> I think it is a good idea to add the non-breaking variants of included
> characters. That is something we can do automatically (there is a processor
> that can modify display of data in the survey tool, and modify data that is
> typed into the survey tool). Can you file a ticket for that?

Yes gladly, I’ve also quoted your text in http://unicode.org/cldr/trac/ticket/11376
> 
> We have to strike a balance here, because often the typographically more
> desired form is not present in fonts. We typically delay, for example,
> using new currency symbols until widespread fonts have caught up. We stay
> away from extensive use of the super or subscript Latin characters. Those
> are not uniformly supported in fonts, and tend to have a ransom-note
> appearance. So for English we don't use 13ᵗʰ, for example, even though that
> form would be in theory preferred to 13th. However, the Latin-1 characters
> are well supported:
> ª U+00AA FEMININE ORDINAL INDICATOR
> º U+00BA MASCULINE ORDINAL INDICATOR

Yes they are, thanks to well-established good policies. I’ve discussed superscripts 
in next ticket:
http://unicode.org/cldr/trac/ticket/11377
> 
> We don't include ' and " in the regular punctuation, because they are
> rarely the preferred form for display. (There is a mechanism
> called parseLenients that we could consider extended for cases where it
> could be useful to indicate that various input forms might be
> equivalent...).

The point of the ASCII single and double quotes among others made me think and 
file ticket #11343 suggesting to remove them in English, too (should be another 
ticket, will post and Xref):
http://unicode.org/cldr/trac/ticket/11343
> 
> As for more documentation, we'd welcome that. Some thoughts (not complete):
> 
> - We need to think about the best forum for it. The LDML spec is
> heavy-weight and slow to modify, while the
> http://cldr.unicode.org/translation pages have a very fast turn-around.
> The connections between the Survey Tool info panel for a path (or set of
> paths) and a particular http://cldr.unicode.org/translation page do
> require rebuilding and deploying the tool, which is not as light-weight,
> but fairly straightforward.
> - Best is to pick out obvious fixes or enhancements to the documentation
> with suggested rewording or additions for clearly identified places.

Above linked ticket #11343 is one example I thought at.

> - Suggestions for policy changes or enhancements should be kept
> separate, so that they can be reviewed and discussed first before specific
> text is considered.

Last posted #11377 falls in this category. Hopefully CLDR-TC and UTC may 
consider reviewing those policies, when seeing what’s at stake.

Thanks for follow-up,

Marcel