I think we should think a step ahead. With templates it is not only possible to change the language but also the look and feel of the interface. We sould distinguish between skins and languages. Each skin can be available in different languages (i.e. "subskins": one directory for one skin and one subdirectory for each language). By reading out the directory-tree we can offer all skins and their languages. Also for the languages I think we shouldn't have a parameter which says: use this language. First the browser settings of the user should be taken, second an array with the preffered languages and third, if the array is omitted, the languages order you specify in your webserver (apache). So the koha-admin normally hasn't to take care of languages and only needs to set the array if he wants to override the apache settings or he is working with a webserver not capable of multi-language-environments. dorian