I'm not proposing a solution to I18N content, I am proposing a solution to I18N acs_objects.name.
We already have objects whose name is a message_key: in file-storage. How would a site-wide search or a linking package know how to deal different types of object names but with a instruction?
In my example the user-supplied object name never gets touched, only the rendering changes and is locale-dependant here.
The procedure in presentation knows how to deal with the content in name by "magic": name has #foobar#, presentation has lang::util::localize. If presentation is empty, nothing happens. If name is a list, the proc in presentation needs to know the semantics of the list elements.
We should move out I18N content to a different thread.
