Localize Admin Strings

[SomosAMambo]

It would be great if all strings hardcoded into admin may be translated via lang* files.
Some of the strings are hardcoded in the index.js file (filters in listings, datepicker, etc).
I'm willing to pull my Brazilian Portuguese pack.

[weotch]

What do you mean by lan files? I'm not familiar with that term.

[SomosAMambo]

Sorry. Typo for "lang". Localization files natively supported by Laravel. resources\lang

[SomosAMambo]

Hello guys! This is very important for wider adoption. Our clients loved the CMS, but their teams can't read english.
There's also javascript strings, date fields, ...

I think this is too core related for a PR. But... we are committed to pull ours translations.

Is there plans to release this soon?

[weotch]

Next week I think we could tackle the changes that need making in the core. Specifically:

• Use lang files for strings rendered in PHP
• Passthrough lang configs to JS for use in strings rendered by JS

We'll implement the more obvious cases that pop up using these new systems and then you can PR any additional cases you find with your Portuguese pack, cool?

[SomosAMambo]

Damn yeah!

[brokenhd]

@SomosAMambo on dev-master we started localization for Portuguese (note that I used google translate so it's probably not 100% accurate). Also stubbed out the javascript string localization as well. Take a look at how we approached it and you can PR the rest.

[SomosAMambo]

Fantastic @brokenhd! Testing already. First thing I've noticed is that you did a great job translating to Brazilian Portuguese (aside from minor details) but the ISO language code for our language is pt-BR (Laravel treats it as pt_BR), "pt" is used for portuguese from Portugal. I'll tackle into the code now and PR.

You guys are great! Thank you!

[SomosAMambo]

Maybe... what do you guys think about publishing the localization files to resources\lang dir?

It'll allow devs to override strings on a project basis.