I don't think this i18n strategy if flexible enough to allow translation into other languages. It assumes the structure of the language (e.g. translation for "AND_SHARED_WITH" is always one block and always in a certain place in the overall structure). We need to find an approach that leaves it up to the translation to define that structure.