> Here is a revised version of the proposal I sent on 12-21 in reaction
> to martin's proposed patch for GCC and UTF-8.

Thanks for this very elaborate proposal. It sounds good to me. I have
some concerns, which I'll split into separate messages.

> FIXME: the .uXXXX, .UXXXXXXXX and .xXX escape sequences described in
> (9) and (10) below are reported to not work for C++ mangled names; I
> don't fully understand the problem, though, so I haven't fixed this.

The problem really is the choice of escape character. The requirement
simply is: Different C++ objects need to have different assembler
names. Consider

class F{
  static int u00C0;
};

This is mangled as '_1F.u00C0'. Originally, I thought I could create
another C++ object with the same mangled name (containing À), but this
is not the case.

There still is a conflict with

extern "C" void _1F\u00C0();

Maybe it is OK to reserve this name for the implementation...

Regards,
Martin