About I18n #39
Milestone
Comments
|
Yes, this is not very well supported currently, and would be a good candidate for inclusion 2.0. In the meantime, you can use Mustache's function rendering with literal template values. Perhaps something like this: <!-- template.html -->
<html>
<body>
<h1>{{#t}}Hello{{/t}}</h1>
</body>
</html>Then, define a context plugin like this: // myapp/i18n.js
define({
'name': 'i18n',
'init': function(config) {
this.language = navigator.language.split('-')[0];
this.translations = config.translations[this.language];
},
'context': function(context, routeInfo) {
var self = this;
return {
't': function() {
return function(text, render) {
return self.translations[text] || text;
};
}
}
}
});
// myapp/config.js
define(['data/config', ...],
function(config, ...) {
...
// TODO: use full language codes
config.i18n = {
'translations': {
'en': {
'Hello': 'Hello',
},
'zh': {
'Hello': '你好'
}
}
};
return config;
});
// myapp/main.js
define(['wq/app', './i18n', './config', ...],
function(app, i18n, config, ...) {
app.use(i18n);
app.init(config) ...
});This assumes a hardcoded list of a few translations, but you should be able to integrate an existing i18n library using a similar technique. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to use i18n in a wq project? The i18n approach is not working properly in wq project, especially with mustache template engine.
The text was updated successfully, but these errors were encountered: