Hi Akim, > On the other end, it would be nice if the FSF supported something like > '?locale=CODE' or '?lang=CODE', as some sites do, as it would relieve us > from having to maintain some correspondance by hand.
The only benefit that this syntax would have is that the PATTERN could be derived from the DEFAULT-URL. It would still be required to look up which translations of the web page exist and which don't. Why? Assume the Spanish translation exists and the Portuguese translation doesn't exist, and the user has set LANGUAGE=pt:es. Then it would be wrong to present DEFAULT-URL?lang=pt to the user, because it would show a 404 page or fall back to English. The user wants to see DEFAULT-URL?lang=es in this case, though. Bruno
