A bit of exploration with Radio Userland and its translation capabilities uncovered quite a bit of information. Of course, nothing is really properly documented — you have to search and dig. Google is definitely your friend... First, you need to set up a database as described at http://frontier.userland.com/localizationGuestDatabases. All the translation work happens in this database. If it's located directly in the tools subfolder of Radio Userland, it will be activated with every startup. Second, you need to create your own new property. To do this, jump to user.prefs using Apple-J (Ctrl-J on Windows). There, create a new scalar of type String (Table menu, then New Scalar and select String). The name is language. This string is set to the value german and then activates the German translation from the guest database in the web interface. If you want documentation for the previous paragraph, you'll only find it indirectly. A search on http://radio.userland.com/ for localization at least revealed that the function radio.string.getLocalizedString takes the language version into account (or rather, the message — it was already older — stated that you need to patch this function so that it takes it into account). If you look at the function (simply jump to radio.string.getLocalizedString using Apple-J or Ctrl-J on Windows), you can see that it takes user.prefs.language into account. For hackers, Radio is a paradise because the entire script source code is there and you can just start hacking. You can rummage through everything and investigate. Stick your nose in everywhere and change just about anything. For end users, however, something as essential as activating a subsequently installed translation database should really be made a bit easier |;-)|.