Comment 3 for bug 545746

I investigated the issue quite a bit deeper, see the resulting related blueprint.

Just before the release is not a very good time to change base translations. Changes in variable names are changes in the data model and it requires migration, so I'd like keep such changes rare. Changing them once would be perfect...

Introducing a more flexible model on the other hand will likely break the API compatibility for software like CanDo - again I'd like to do that after the Lucid release.

This is a very important topic and I'd like to work one step at the time towards generic solution:
1) split name data from UI, add rudimentary data structures, keeping the look and functionality identical
2) start adding important features (in parallel):
- Easter/Western support
- Chinese/Western name field schemas
...