Multilingual App

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Multilingual App

sebastianconcept
Hey guys,

what's your preferred approach to make an Amber app multilingual?

Some ideas we're brainstorming here:
  1. Using the translatable strings in a dictionary that's in a Translation object coming on a package of its own and deciding which to load dynamically (with require.js or whatever)
  2. Loading the Translation object dynamically with ajax
  3. Lazily loading the Translation object from the local storage that it's lazily installed there via AJAX
any thoughts? other appealing options?

sebastian

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Multilingual App

Clément Béra
Hello,

There is also the google API that permit to translate automatically using google traduction. It does not work very well on words but it works okay on a full web page (it works with lexical fields). 

I guess you could integrate that in Amber quite easily as the javascript library integration is easy. Of course, you would have to provide by yourself the main languages (like English / Spanish) to be sure the translation is accurate but you can provide the other languages of your multilingual app with google trad precising that it might not be accurate to customers.

For example look at this page : http://www.depale.fr . The web page is in French but you can choose on the left menu to translate it to any language google trad supports. The result is quite good in my point of view.


2013/4/8 Sebastian Sastre <[hidden email]>
Hey guys,

what's your preferred approach to make an Amber app multilingual?

Some ideas we're brainstorming here:
  1. Using the translatable strings in a dictionary that's in a Translation object coming on a package of its own and deciding which to load dynamically (with require.js or whatever)
  2. Loading the Translation object dynamically with ajax
  3. Lazily loading the Translation object from the local storage that it's lazily installed there via AJAX
any thoughts? other appealing options?

sebastian

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Clément Béra
Mate Virtual Machine Engineer
Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Multilingual App

paul-3
In reply to this post by sebastianconcept
Could this be an orientation?

https://developer.chrome.com/extensions/i18n.html


Am Montag, 8. April 2013 21:11:58 UTC+2 schrieb Sebastian Sastre:
Hey guys,

what's your preferred approach to make an Amber app multilingual?

Some ideas we're brainstorming here:
  1. Using the translatable strings in a dictionary that's in a Translation object coming on a package of its own and deciding which to load dynamically (with require.js or whatever)
  2. Loading the Translation object dynamically with ajax
  3. Lazily loading the Translation object from the local storage that it's lazily installed there via AJAX
any thoughts? other appealing options?

sebastian

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.