Add en_AU

[bakkbone]

I translated for en_AU

[ozh]

I didn't notice any change in the translation file ? so what is the point ? :)

[bakkbone]

I didn't notice any change in the translation file ? so what is the point ? :)

For example, our server flags anything in EN_US :)

[ozh]

I still dont get the point of this, nor what "our server flags EN_US" means.

Adding define('YOURLS_LANG', 'en_AU'); to load an unmodified translation file is the same as doing nothing, or to do the define without adding any translation file... (except you're actually slowing things down a bit by loading an external file that contains the same strings as in core)

[bakkbone]

There are differences in spelling between US and AU English - as such our server is set to flag and repetitively notify admins for any installations not in AU English. Thus, we maintain enAU translations for as many programs our clients use as we are able. Apologies for attempting to contribute this to the broader community ¯_(ツ)/¯

[bakkbone]

And as such, there are changes:

[dgw]

as such our server is set to flag and repetitively notify admins for any installations not in AU English

This sounds like a waste of server resources. It's up to your clients whether they want to present content in AU English or some other dialect, is it not?

I'm not saying there shouldn't be an alternate English localization that uses UK/AU spellings. Just that it's not the hosting company's job to enforce dialect.

[ozh]

If there are changes (even minor), then this is different of course. You should have stated that in the first place :)

[bakkbone]

I'm not saying there shouldn't be an alternate English localization that uses UK/AU spellings. Just that it's not the hosting company's job to enforce dialect.

Each server has a language set - client chooses which language when selecting a server :) the notifications can be opted out of, mind you

[bakkbone]

You should have stated that in the first place :)

Apologies - had assumed that much went without saying