I remember there was a discussion in one of @andrepereiradasilva 's PRs I helped with testing.

See this comment by @infograf768 and the comment just before that one.

It seems these texts come from the XMLs and may be decided by the Translation Teams.

If you look at the installation language files they do not have this
problem as they are correctly named in the XML file there. So this is not
the same issue as mentioned in your link it is simply a bug in the XML
files which I don't have access to in order to fix.
On 21 Feb 2016 11:44 am, "Richard Fath" notifications@github.com wrote:

I remember there was a discussion in one of @andrepereiradasilva
https://github.com/andrepereiradasilva 's PRs I helped with testing.

See this comment
#9101 (comment)
by @infograf768 https://github.com/infograf768 and the comment just
before that one
#9101 (comment).

It seems these texts come from the XMLs and may be decided by the

Translation Teams.

This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at issues.joomla.org/joomla-cms/9187
https://issues.joomla.org/tracker/joomla-cms/9187.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

Ah, I see. Sorry for confusion.

What the language is called is up to the TT but it must be unique and they
must use the same name in the installation language and the main language
pack
On 21 Feb 2016 1:04 pm, "Richard Fath" notifications@github.com wrote:

Ah, I see. Sorry for confusion.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

It's all done by script. https://github.com/joomla-projects/language-update-xml-generator/blob/master/translation_cron.php#L208 is the line in the cron file where the name gets processed for writing into the XML files. The package list is coming from http://joomlacode.org/gf/project/jtranslation3_x/frs/. The way it looks, someone just needs to rename the packages on JoomlaCode and the next time the cron runs after that it would all be fine.

I assumed something like that I just don't have the access to do it
On 21 Feb 2016 4:21 pm, "Michael Babker" notifications@github.com wrote:

It's all done by script.
https://github.com/joomla-projects/language-update-xml-generator/blob/master/translation_cron.php#L208
is the line in the cron file where the name gets processed for writing into
the XML files. The package list is coming from
http://joomlacode.org/gf/project/jtranslation3_x/frs/. The way it looks,
someone just needs to rename the packages on JoomlaCode and the next time
the cron runs after that it would all be fine.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

Ironically the user account that the cron job runs under doesn't have manage privileges on that project's files. @infograf768 or @Bakual I'd assume would have that.

Using fr-ca as an example it's simply a case of renaming the package as the
script is ignoring the actual language name in the XML
On 21 Feb 2016 4:29 pm, "Michael Babker" notifications@github.com wrote:

Ironically the user account that the cron job runs under doesn't have
manage privileges on that project's files. @infograf768
https://github.com/infograf768 or @Bakual https://github.com/Bakual
I'd assume would have that.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

The cron generating the update XMLs doesn't use the data inside the actual package, rather the package name in JoomlaCode and the file name to extract out all the required info.

Yeah that's what I meant. Weird that it's not consistent with the
installation languages
On 21 Feb 2016 4:48 pm, "Michael Babker" notifications@github.com wrote:

The cron generating the update XMLs doesn't use the data inside the actual
package, rather the package name in JoomlaCode and the file name to extract
out all the required info.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

in fact, i just have to change the project name on jomlacode with the jomlacode naming restrictions. will make test to see if it is b/c with en-au. at least to differentiate the english packs.

Thanks. I think the same as with fr-ca is better than nothing
On 21 Feb 2016 5:38 pm, "infograf768" notifications@github.com wrote:

in fact, i just have to change the project name on jomlacode with the
jomlacode naming restrictions. will make test to see if it is b/c with
en-au. at least to differentiate the english packs.

—
Reply to this email directly or view it on GitHub
#9187 (comment).

No B/C issue, i.e. update went fine from older pack.
English AU already done.

Others done too, will be available in an hour or so.
Will be
English US
English CA
English AU

Also modified FrenchCA to French CA

IMHO you can close.

BTW, FYI
These names come from the Releases Names.
If I want to get French CA, I have to add an underscore before CA and then another underscore before the lang tag:

Thank you very much. Closing