Re: Character name translations

There are different use cases, and I think they are getting confused.

1. Present a name for each character, some sort of formal name.
I think this is probably the least useful for average users.

2. Allow searching for characters, eg in a character picker.
Sample use case: search for "dash" (or the equivalent in Georgian) and get
the dashes.

3. Provide disambiguating information about a character (to distinguish
from visually similar characters).
Sample use case: have a hover over a character and show "em dash" vs "en
dash" (or the equivalent in Georgian).

Mark <https://plus.google.com/114199149796022210033>
*
*
*— Il meglio è l’inimico del bene —*
**

On Thu, Dec 20, 2012 at 8:18 AM, Asmus Freytag <asmusf_at_ix.netcom.com> wrote:

> In my other message, I made clear that I think translations of just the
> names is a lot less useful than translation of the full information
> presented in the code charts, which includes block (and therefore script)
> names, annotations and listing of alternate names by which these characters
> are known to ordinary users.
>
Received on Thu Dec 20 2012 - 11:20:06 CST