Re: i18n
Mark Anderson <[email protected]>
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Message-ID | <[email protected]> |
i guess what i'm missing is why a client-side solution is preferable or otherwise attractive. server-side templating solutions generally support (or at least have to confront) dynamic content based on user preferences, client device, site customization, and a variety of other dimensions. language is just one such customization. what would be next? javascript-based switching of currency and temperature units? furthermore, http itself supplies a preference for language in the standard. i feel the same about pure client-side lang switching as i do about pure client-side css switching -- a cool hack perhaps, but not particularly necessary AFAIK. in any event, one approach would be to use the standard xml:lang attribute, and on the client exclude any elements (and their children) which possess an xml:lang attribute and its value differs from the desired one. -mda _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org