i18n: enable local debug locale, en-XL

[exterkamp]

Summary
Revive locally generating en-XA! Since the tc/ en-XA doesn't work* and we want an immediate feedback loop for i18n PRs we should bring back local en-XA generation!

Looks pretty dope too:

You can see why not having placeholders is dangerous:

Definite hack to get the nested braces to work for plurals, but hey it works:

*tc/ en-XA will work again once #9114 is landed and fully in tc/ 😄

Related Issues/PRs
part of: #7238

Future work

• ar-XB locally too 😮
• Add this to the zeit deploys? @paulirish

[connorjclark]

can you explain this like i'm an idiot ... (just dig deep and pretend)

EDIT: oh, en-XA is some sort of test locale? that explains most of my confusion. is the point to show which parts of the UI are not actually being translated? If so, it kinda fails on numbers.

[exterkamp]

Yeah, basically. en-XA is a test locale that adds weird looking characters on every translatable character registered at that time. So when we have a PR like #9092 we could collect-strings, then look at a report in en-XA-local locale and it would be super obvious that something wasn't translated because it wouldn't have the messed up characters. Similarly we can see that the Learn More urls and all markup control characters are also messed up by this locale, indicating that they could be translated and messed up (e.g. #9000). So this is a simple and easy way to confirm that strings of new PRs are ready to translate.

It also has some cool stuff, notice, the metrics section the 1.0 ŝ indicating that the "s" for seconds is translated, but the Opportunities section has 0.63 s indicating that those seconds units haven't been translated! (that is part of #7238 to fix that very minor inconsistency)

It was mentioned here as well: #7010

[patrickhulce]

yay it's back! :D

[brendankenny]

nice!

[brendankenny]

LGTM!