Custom translation directory
See original GitHub issueI would like to keep translations in different directory than translations
. I thought about changing inputPath
and outputPath
to something different. Unfortunately it doesn’t work, because the default path is hardcoded in node_modules/ember-intl/app/instance-initializers/ember-intl.js
Issue Analytics
- State:
- Created 7 years ago
- Comments:24 (10 by maintainers)
Top Results From Across the Web
Translation Directory
Portal for translators and translation agencies. Translation jobs. Database of freelance translators. Database of translation agencies.
Read more >Custom translation deployments | Drupal.org
Makes it possible to have custom files in your translations directory, and therefore also to deploy translations. To deploy translations you ...
Read more >40+ Places to Find a Translator | Redokun Blog
From directories to freelancers to agencies... ... Translated has been delivering professional translations and custom localization solutions since 1999.
Read more >Language Services Directory - American Translators Association
Find the translator or interpreter that meets your needs. Customize your search by language, specialties, location, credentials, and more.
Read more >safe location for custom translation | WordPress.org
The only way to display the custom translation, as far as I could see was to locate the custom translation file in the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jasonmit It looks nice. Works almost exactly as I was expecting. The only thing which I dislike is repeating translation path in each translation file.
Structure:
File en-us.yaml:
I would prefer to have it simply like
title: 'Notifications'
which is huge advantage while refactoring files around.
@jasonmit Thanks! I’ll have my team review to see how that works both from a dev and prod perspective and then provide feedback either way.