As title, it seems that this locale package misses the zh_TW locale.

I think it can add this locale. And the related reference is available here.

Once this issue is accepted, I will work on this issue and create related PR.

Hello Jack.

After a thorough discussion with Andreas (who maintains the Deutsch locale), we think it would be much easier to have two i18n repos:

• one with English language only
• one with all other languages

a) On the i18n English repo, we need "you" (Statamic) to update the English files each and every time you update Statamic
b) we also need version tags (ie 2.9.2, 2.9.3..) on the commits
c) and we really need a way for translators to identify what were the changes made: you can easily do so with a version comparison that should appear on a Readme file in this repo.
Take a look at that: EllisLab/EE-Language-English@4.1.3...4.2.0 (you can also compare between commits)

Then, on the other repo, we could proceed as we do today with Pull Requests from the various translators and a single Readme file to follow on the latest version that has been translated.

Would you mind telling us what you think of that?

Could it be possible to:

1. either create a 2.x branch OR prune the Master branch in order to only keep 2.x files
2. refresh the English folder in the kept branch (2.x or Master) to update it with the latest folders and files found in the Statamic base install folder
3. always update the English folder each and every time you update Statamic to a new version, AND maintain a changelog of the differences (ie "Github compare 2.8.2...2.8.3")

Number 2 and Number 3 will make MUCH easier the process of translating/localizing the CP in any language. Statamic is offering natively a very nice way to localize content, so I guess there really is a user base in The Netherlands, Germany, Belgium that would appreciate to work with an up-to-date translated CP.

Thanks for all.

'taxonomy_terms_empty' => 'Where a Taxonomy is the grouping, a Term is the actual label applied to a piece of content. For example, "Red" would be a term in "Colors".',
'section_label' => "Section Label",
'section_handle' => "Section Handle",
'status_active' => 'Active',

These keys still are in English, is this intended behavior?

'shorthand_instructions' => 'The 2 character laguage code.<br> Example: `en`, `de`.',

In 2.8.8, the key was OK : language instead go laguage

This has been introduced in 2.8.9.

Please create a v2 branch

Hey Jack.

Currently it is not really user-friendly to install or update translations as a non technician. Therefore, I think it would be a logical step, as far as the quality of Statamic is concerned, to add the possibility to install and or update the tranlation files within the Control Panel. This would make the maintenance of already updated Statamic installations much more easier and it could be even done by the customers themselves if a update was available.

What do you think?

If we would lift up the single language folders into the repository's root, it could be used as a git submodule in /statamic/resources/lang

Would be more in line with the version control everything mentality, and simplify updating languages along with statamic itself.

What do you think?