[thelist] javascript-based webpage translation framework?

[Matt Warden]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mattias Thorslund wrote:
>>Under what circumstances would you be able to detect this after page
>>load and not upon receipt of the request on the server?
> 
> 
> Perhaps when letting the user switch languages, and avoiding a page reload?
> 
> IMO, the server should detect the preferred language from the browser
> settings and present the site in the highest-listed language that is
> available. But this assumes that people configure their browsers, which
> is not always true. So, presenting the alternatives on the site makes
> sense as well.
> 
> But this sounds like a lot of work and overhead simply to avoid a page
> reload...

That would only be valid for the page where the user initially changes
the language. The rest of the pages would be better off translated on
the server-side.

Replacing all the text nodes on the page would be a nightmare from an
initial coding standpoint and even moreso from a maintainability standpoint.

And, hate to rain on the Web 2.0 parade, but using JS to dynamically
request a full document of marked-up text seems... oddly similar to what
a browser would do on a document reload.



- --
Matt Warden
Oxford, OH, USA
http://mattwarden.com


This email proudly and graciously contributes to entropy.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEe3CKrI3LObhzHRMRAlMuAJ0XAUOp2daHb+ktPZoRP7Ty1yduWgCfRLsX
X8Xy1RrpBEi9cjTxH8WQZHk=
=PZ/N
-----END PGP SIGNATURE-----