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
My concern is around UA's qualifying between fuzzy/approximate matches and exact matches. This could manifest in a number of ways in the UI but, to date, current implementations and this document do not separate the two groups. In cases where glyphs are especially hard to distinguish, someone could copy/paste or search terms using the incorrect spelling if they don't have an affordance that what they're using is only a fuzzy match.
A more difficult, but possibly useful, feature to add here would be the canonical match. When an English keyboard is used to match a German word resulting in a fuzzy match, perhaps the German (correct) spelling would be given an additional affordance.
The text was updated successfully, but these errors were encountered:
re: w3c/apa-review#8
My concern is around UA's qualifying between fuzzy/approximate matches and exact matches. This could manifest in a number of ways in the UI but, to date, current implementations and this document do not separate the two groups. In cases where glyphs are especially hard to distinguish, someone could copy/paste or search terms using the incorrect spelling if they don't have an affordance that what they're using is only a fuzzy match.
A more difficult, but possibly useful, feature to add here would be the canonical match. When an English keyboard is used to match a German word resulting in a fuzzy match, perhaps the German (correct) spelling would be given an additional affordance.
The text was updated successfully, but these errors were encountered: