On 18/06/2008, at 7:42 PM, Clayton Cornell wrote:
Geolocation isn't the answer.Good to know someone agrees with me on the Geolocation thing. It's my biggest pet peeve on the web next to Internet Explorer and its inability to deal with CSS standards :-P
Nothing on the Web is quite as annoying as IE's blatant lack of standards support. Some things are close, but they're mostly ignorance: Microsoft knows perfectly well that everyone relies on the Web standards, but they deliberately choose to ignore them, again and again. I'm sure there is a special Hell for people who ignore Web standards. ;) (It's probably full of Javascript popup ads.)
an effective language bar like that avoids a lot of problems.I am seeing it being used in a few places. I have changed a few pages myself.I find that if there are several translations of a certain page, it is best to create a template for that specific topic. In the template you add the InterWiki link syntax for each language the Wiki page is translated into, and then all you need to do is insert the template link in each translated page. Then as new translations are added, you add the InterWiki link to the template and all pages with that template are automatically updated with a link to the new language. This is how it is set up on the Main Page [1] and on the Extensions [2] page.
Thanks for the references. I'll try to use that next time I translate a wiki page.
It would be interesting to know. I wonder what the Wikimedia folks do about this.I have posted a question on the MediaWiki users forum. Have to wait and see if there is any reply.
OK. :)
C. [1] http://wiki.services.openoffice.org/wiki/Main_Page [2] http://wiki.services.openoffice.org/wiki/Extensions
from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n
PGP.sig
Description: This is a digitally signed message part
