Initial translation setup

[EvanDotPro]

This PR adds the following translations:

• en_US
• de_DE / German - Thanks to @coss
• fr_FR / French - Thanks to @b-durand
• fr_CA / French - Thanks to @yanickrochon
• ja_JP / Japanese - Thanks to @sasezaki
• tr_TR / Turkish - Thanks to @HHGAG
• cs_CZ / Czech - Thanks to @dlu-gs
• es_ES / Spanish - Thanks to @adolfoabegg
• ar_SY / Arabic - Thanks to @tawfekov

Thank you to everyone who has contributed translations so far! You're all awesome!

[EvanDotPro]

It would be nice if we didn't have to do this to run the factory, but I don't have any immediate ideas.

[akrabat]

Should be ZendSkeletonApplication

[EvanDotPro]

Fixed, thanks.

[RWOverdijk]

Right now the locale is being hardcoded to en_US. Perhaps we should add the ability to choose a language in the skeleton to illustrate how to change the locale?

[EvanDotPro]

Good idea -- though, I'm not exactly sure what the best practice is on this, or how well routes support something like prepending a locale to the route stack... @DASPRiD may have more feedback on how he intended to handle this.

[HHGAG]

Hi Evan,

that could be solved like that:

$localeList = array(
    'en_US',
    'en_UK',
    'fr_FR',
    'fr_CA',
    'de_DE',
    'tr_TR',
);
$browser = Locale::acceptFromHttp($_SERVER['HTTP_ACCEPT_LANGUAGE']);
$locale = Locale::lookup($localeList, $browser, 'en_US');

since Zend\Locale\Locale::getBrowser() has been removed, but this would cause a direct depandancy to php5-intl extension, which isn't activated/loaded on the half of isp's in Germany, i don't know what is givven in the us

[EvanDotPro]

We could check if class_exists first. Thoughts?

[HHGAG]

Sure, why not. I hope that our ISP's will be forced to load intl by ZF2 release. ^^

[EvanDotPro]

Hmmm, I think we might have to add something to the TranslatorServiceFactory to do this cleanly.