Re: Encoding names? Are they accessible in TT fonts?

as Vid says, this is not stored within the font
as redear says, you can get the names from
http://www.unicode.org/Public/UNIDATA/NamesList.txt

I thank you all for the url. I have download the list.

I had need to develop a font for my own app, which I have over
the last many years, which contained the usual text/keyboard
chars, but then used the chars > 128 for special symbols
required by my app. (At least those chars which are eligible,
for which a number are not, such as soft-hyphen, etc.)

I decided to do this because people would also need the app
to record their own notes, and it would be laborious to have
to keep switching fonts to key in a symbol.

Initially I made the 'mistake' of using the symbol encoding,
but then switched to Windows ANSI and edited my own encoding
names, which it appears is simply a means to facilitate the
font's development, i.e., the names actually are not stored.

I have yet to fully evolve the font as Unicode for various
reasons.

1. It does not seems necessary yet. Yes, my app will not be
fully 'internationalized' but then my development environment
does not make full use of Unicode yet, either.

2. I have yet to find references which makes Unicode
'intelligible' in terms of the user, the application development
environment, and the font development environment.

Thanks all for contributing to this brief exploration.

--
George Newton
.