Any thoughts on adding i18n support for drupalgap?

Drupal native jquery has support for i18n via the Drupal.t() function but this doesn't work in drupalgap and not entirely sure how it would.

I think it would be something like a remote call to get "translated" string from the server and then display that value rather than a value hard coded in to the app.

also, i use the idea of i18n and translated loosely since as drupal devs know it is possible to modify t() wrapped strings outside of i18n (see string overrides module). in dgap this would give the ability to change things like button labels, etc without having to recompile, submit to itunes, etc the app.

Comments

tyler.frankenstein’s picture

Title: any thoughts on i18n support? » any thoughts on i18n support? multi lingual
Status: Active » Needs work

As a relative n00b with multi lingual Drupal sites, I have some general thoughts about how this could be supported into DrupalGap. This ideally needs a serious conversation in #drupal-drupalgap on IRC if anyone is interested.

liquidcms’s picture

i'm english; the app (our first) we are doing is for the city of montreal.. and is (oddly) only in french.

so, although i am coding strings in EN; this is only to ease dev and we will eventually go back and change them all to FR. so, we don't really need i18n. but the next app we may. :) i don't know dgap too well; but pretty familiar with i18n so just thought it would be a pretty useful feature to have translatable/overridable strings support.

i'll add myself to the irc channel.

g089h515r806’s picture

I use it in Chinese, I need translate the English label into Chinese.

tyler.frankenstein’s picture

From another user:

I believe the issue for getting nodes might be caused by the fact that I have the internationalization module installed on the Drupal site.

This module serves up english or french content based on the url, so the node id stays the same between languages, but the url it retrieves is /en/node/54, instead of just /node/54.