[dev-context] new release

[Taco Hoekwater]

Mojca Miklavec wrote:
> 
> In the unicode vectors there are characters like \unic at whatever,
> \UnicodeWhatever (for example in vector 37), ...
> 
> I wanted to update this file:
> http://pub.mojca.org/tex/enco/contextlist/contextnames.txt, but I
> don't know which names would be better (it would be fine to have some
> sort of unified names). Hans suggested \ucWhatever since it's slightly
> shorter.

I've used \unic@ names for most things, except where a TeX
control sequence was already available (like \leftarrow etc.)

The prefix is there to prevent name clashes, of course. I have
build the csnames (almost) straight from the unicode name. So

   ADDRESSED TO THE SUBJECT => \unic at addressedtothesubject

I made (i think) only one change, for brevity's sake:

   SCRIPT CAPITAL L         => \unic at scriptL
   SCRIPT SMALL L           => \unic at scriptl

I prefer lowercase names as much as possible (they are internal
commands, after all) and adding the '@' prevents clashes with
document-level shortcuts/commands.

I agree unified names are important, but I don't feel strong
about the actual names used. I just used something that seemed
natural to me at the time ;-) Eventually, I want to be able
to take the unicode standard, lookup a _any_ character, and use
a simple recipe inside my head to create a ConTeXt name, like:

   \unicode{scriptL}

I know that this will have to wait for a while (for one, it would
use too much string space and hash entries, current TeX's are not
up to the task).

Cheers, Taco