Use English as fallback for missing strings when generating translation ...

[nichtsistwahr]

Generate client translation js with English fallback as suggested in https://meta.discourse.org/t/missing-translation-defaults-to-english/15771/9

[discoursebot]

You've signed the CLA, nichtsistwahr. Thank you! This pull request is ready for review.

[SamSaffron]

My worry here is that we are putting something into "dev" environment for production.

I would much prefer if

1. In development ... no fallback
2. in production ... fallback with an additional querystring ?localization_fallback=false for cases when localizers need to test without fallback.

[nichtsistwahr]

I can see that. Since I am not that experienced with rails development, I could use some pointers. I guess I would have to:

• generate two separate js locale files for each locale - one with and one without the merged EN locale
• register the additional assets
• add a route that registers the query string and decides which locale js to serve

Am I missing something?

[coding-horror]

Sam isn't this obviated by your changes documented here:

https://meta.discourse.org/t/enjoy-matching-translated-strings-and-their-translation-keys-right-in-the-
gui/19219

and

To enable you have the "verbose_localization" site setting.

Use:

I18n.verbose_localization_session()

?

[SamSaffron]

@coding-horror this is related but not the same issue, the attempt here is to make the UI usable in production in cases where only partial translation is available (fallback to English)

[SamSaffron]

@eviltrout we need to think about a solution here, we want to enable fallback localization in EN but only in prd.

[eviltrout]

Can't we just do it when baking the assets though? In production mode, mix in the english keys?

[SamSaffron]

yeah that was what I was thinking.

On Tue, Nov 25, 2014 at 2:18 AM, Robin Ward notifications@github.com
wrote:

Can't we just do it when baking the assets though? In production mode, mix
in the english keys?

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

[coding-horror]

Closing this for now as it is getting pretty old. Let's revisit later.