You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, the premise of the service is that it's basically applying google translate to our page? That sounds convenient, but I've also seen google translate make horrors out of other pages when I translate them. I wonder if there's some option to tell google - "when you read X, display X', not your translation of X".
We'll also need to translate any text in images and send those images instead when the user requests the site en espanol. Also the map.
Instead, it seems like it is for translating things in their totality before they are pushed into the world, rather than translating them at runtime with a few tweaks. In which case, it might be a useful tool for translating the site - but we'd still just be storing a separate lookup of strings for each language the user might request.
We could potentially use a service like this:
https://support.google.com/translate/answer/2534601?hl=en
or we could write our own translation with the help of CfD members, and incorporate it ourselves.
The text was updated successfully, but these errors were encountered: