Some of the transforms in the page library currently require localized strings to be passed in as arguments. They are to be added to the DOM during these transformations. Currently the apps have the translated strings and pass them in when they invoke the transformations client-side.
It would be good to already know the translated strings on the server side (and pass in the locale, and be aware of potential language variants).
 Change the transforms to take a Locale as a parameter instead of the translated strings.
 Need to set up I18N either in page library or PCS.
 Probably need some mapping of domain names to locales; deal with language variants some more.
Examples of strings:
* `description_edit_add_description`: "Add title description"
* `table_infobox`: "Quick facts"
* `table_other`: "More information"
* `table_close`: "Close"
`FooterTransformer` and `References` would have some more strings if we go this route.
We'll need some way to pass in the translated strings to the PCS abstraction layer, which then will use that to replace some template strings with the actual value.
One idea is to use the `setMulti()` call to also add an object containing the L10N'd strings.
We also need to come up with a good set of template strings that we look for and strategy of replacing those strings with actual values.