Support Localization #88
Comments
|
@jonpitch this is a great idea! I think this would be a really great feature to have. If you want to start working on it, that would be awesome, let me know if I can be of any help. |
|
Thanks @san650, I spent a little time gathering my thoughts and I have an alternate approach that I wouldn't mind your input on.
'ember-web-app': {
enabled: true,
locales: [{
code: 'en-us',
name: 'English name',
short_name: 'English short name'
}, {
code: 'it-it',
name: 'Italian Name',
short_name: 'Italian short name'
}]
}
const fs = require('fs');
const enUsManifestTranslations = JSON.parse(fs.readFileSync('path/to/en-us/translations.json'));
var app = new EmberApp(defaults, {
'ember-web-app': {
locales: [{
locale: 'en-us',
name: enUsManifestTranslations.name
}]
}
}
...The only thing I'm not sure on is the consumer might need the ability to swap out these files in the |
I have an application that requires localization. I'd like to be able to deliver a manifest that changes based on user locale. There's a minimal amount of content in the manifest itself that would require translation (
name,short_name,description, maybeicons), but what would be nice is if that content could live in my existing translation workflow and I could populate the manifest at build time.I think an approach could be something like:
const name = get(this, 'intl').t('ember-web-app.name');What I'm not sure of, if this is something this addon should have as a feature or if there's another addon here that extends this one? I'm open to suggestions or ideas. I also have some cycles coming up that I could work on one or the other.
The text was updated successfully, but these errors were encountered: