AMS and Dynamic Types (as well as Assessment in a way) allow us to have additional attributes for object types. Sadly it is assumed that these additional types will be only available in one language (not internationalized).
Not that this would be annoying at the moment, but I wanted to raise the issue anyway.
My idea for a solution (using AMS as an example):
Instead storing the pretty_name and the pretty_plural name directly as a new attribute, I'd store "[_ ams.[acs_lang::util::create_language_key $pretty_name]]" and insert the pretty_name cum language key in the AMS catalog.
I know that this stores internationalization in a package where it does not belong in the first place, but I think it still is a good solution. You'd just have to keep in mind that you should never submit you language catalog files to CVS :).
Other ideas ?