TYPO3.Flow

I'd even like to see an option to flag specific messages for export.. We surely needn't every all available messages pushed out to the client.

Also there's the need to take care about different js-framework's localization approaches. In MooTools for example, it's

 1Locale.define('en-US', 'Date' /* Date is the entitiy to describe, could also be 'Vendor\MyPackage\Domain\Model\Thing' */, {
 2
 3    months: ['January', 'February', 'March', 'April', 'May', 'June', 'July', 'August', 'September', 'October', 'November', 'December'],
 4    days: ['Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday'],
 5    dateOrder: ['month', 'date', 'year', '/'],
 6    AM: "AM",
 7    PM: "PM",
 8    //members can be functions; these will be executed and passed any arguments with .get(member[,args])
 9    ordinal: function(dayOfMonth){
10        return (dayOfMonth > 3 && dayOfMonth < 21) ? 'th' : ['th', 'st', 'nd', 'rd', 'th'][Math.min(dayOfMonth % 10, 4)];
11    },
12    lessThanMinuteAgo: 'less than a minute ago'
13
14});

I'm open for discussion :)

Maybe this could be achieved with a ViewHelper:

1<script>
2var myLabels = {f:xliffToJson(source: 'SomeLabelsCatalog', locale: 'de_DE')};
3</script>

(with cooler naming)

I like the viewhelper idea. Options that such a viewhelper should have:
- select locale (obviously), default should be current session locale
- select package where translations get picked from (optimally it would also be possible to get translations from all packages)
- get a list of translations that start with a specific identifier prefix (e.g. "foo.bar.baz.*" or "date.month.long.*")
- result array should be possible to be associative (with identifier as key) or indexed (default behaviour?)

I agree that this would be very useful. Filtering the messages would be a nice option.

A reference could be the JS localization found in TYPO3 CMS (typo3/sysext/lang/res/js/be/typo3lang.js). It even handles plurals.

The main question is where to generate such a file. A view helper makes sense IMO.

I think that should go hand-in-hand with #42407 which I just added as a relation to this issue.

If this can be of any use, here's a quick and dirty solution I threw together for a project: https://gist.github.com/4065082