Comment 13 for bug 267356

At the end of the pipe - in the templates and views - we already require unicode. In the long run all encoded strings should be replaced by unicode.

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.