r12a
Ah, sorry. My bad. I got my wires crossed wrt the line break comment. Still some example would help, do you have some you could show here? Thanks.
I only just now noticed this thread. Fwiw, the i18n WG has an open gap report on this topic at https://github.com/w3c/clreq/issues/247. That points to some tests that may be useful,...
In case it helps, i posted pictures of what i'd expect to see in vertical text for input.text, textarea, and select. Japanese https://r12a.github.io/scripts/jpan/ja.html#interaction Chinese https://r12a.github.io/scripts/hani/zh.html#interaction Mongolian https://r12a.github.io/scripts/mong/mn.html#interaction
In my opinion this would be extremely useful for French authors, but also for other languages. The NNBSP character was initially added to Unicode for Mongolian suffix handling, where it...
> Path of least resistance here seems to be to add more people as editors? You could do this either in the spec itself or as an “overwrite” in specref....
The new text is: > Clearly, this is not the case. Users of Arabic or Thai+character sets, for example, may not be familiar with the English alphabet or may not...
Under https://w3c.github.io/apa/captcha/#the-accessibility-challenge 1.2 The Accessibility Challenge it already says that > traditional CAPTCHAs have generally presumed that all web users can read and transcribe English-based words and characters, thus making...
> Ruby markup (`` and ``) is designed to let us associate individual words with annotations, which can be marked up in a different language (including Blissymbols) using the lang...
> I would emphasise that the use of ruby text is not absolutely of the essence of this proposal Understood. > what would be needed to enable the existing ruby...
> The unique key for a concept must remain the same for all time and not change if future developments result in the graphical representation of a concept changes. This...