Comment 14 for bug 267356

Am 01.10.2010, 11:58 Uhr, schrieb yuppie <email address hidden>:

> But first we have to make sure that all the code that handles Actions
> works with unicode. E.g. the GenericSetup handlers are not tested with
> ustring properties. And we need a migration strategy for the persistent
> strings.

> The current code is not broken, it's just not obvious how to use it.
> Adding unicode support for tool settings is a complete new feature.

Would it make sense to write a proposal or a blueprint for this?

I've experience the problems of non-unicode support in GenericSetup with a
mono-lingual German site. Of course, it's natural to use "native" titles
for actions, etc.

Charlie
--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226