Re: Unicode in passwords

On Thu, 1 Oct 2015 07:01:12 +0200 Mark Davis ☕️ wrote: > I've heard some concerns, mostly around the UI for people typing in > passwords; that they get frustrated when they have to type their > password on different devices: > >1. A device may not have keyboard mappings

Re: UAX #29, Unicode Text Segmentation, update to improve Mongolian word segmentation

On Wed, 30 Sep 2015 14:04:45 -0700 announceme...@unicode.org wrote: > For further background on this issue and possible > ways to address it, see PRI #308 > , /Property Change for U+202F > NARROW NO-BREAK SPACE (NNBSP)/. Is this the announcement of PRI

Re: Unicode in passwords

> On 1 Oct 2015, at 07:19, Marc Durdin wrote: > > 2. The number of dots corresponds to the number of code points, which > is misleading with complex scripts or advanced input methods: you won’t > necessarily see one dot per keystroke; in some cases, typing a character

Re: Unicode in passwords

As to #1, my note needs some clarification. For characters that don't typically occur on *any* keyboards, people don't typically use those in their passwords, so switching between different devices doesn't matter. (One caveat would be where the password dialog permits selection from a palette.

Re: Unicode in passwords

On 1 Oct 2015, at 08:33, Richard Wordingham wrote: > > Even ASCII can have problems. A password containing '#' and '|' can't > be entered when a physical US keyboard (102 keys) is interpreted using > a mapping for a British keyboard (103 keys). (There seem to be > different conventions as to

NNBSP and Word Boundaries

The background document for PRI #308 (Property Change for NNBSP), http://www.unicode.org/review/pri308/pri308-background.html , says, "The only other widely noted use for U+202F NNBSP is for representation of the thin non-breaking space (espace fine insécable) regularly seen next to certain