All graphic elements of the WebYaST interface, such as images, icons, and cascading style sheets (CSS), are stored in the YaST2 Webclient public directory:

/srv/www/yast/public/

This public directory contains the vendor subdirectory, which is used as an alternative location for vendor-specific images, icons, and style sheets. You can replace any file in the public directory by adding a file with the same relative path into the vendor subdirectory. If a file exists in this alternative location, WebYaST uses that file in place of its default equivalent.

WebYaST uses gettext to provide translations for text strings in the user interface. The translations are split in textdomains. Each textdomain contains text strings for a different part of the user interface, for example a WebYaST module.

Different textdomains are loaded for different modules. For example, when the WebYaST Status module is loaded, the following textdomains are loaded:

Loading standard textdomain: yast_webclient
Loading standard textdomain: yast_webclient_status
  

For each textdomain, the list of all text strings and their translations is available in an standard gettext .po file that you can edit. These .po are available in the WebYaST source packages.

The editable .po files have to be converted into binary .mo files with the rake makemo command. For the main WebYaST domain, the generated .mo files are located in /srv/www/yast/locale/LANGUAGE/LC_MESSAGES/. For WebYaST modules, the generated .mo files are located in /srv/www/yast/vendor/plugins/MODULE/locale/LANGUAGE/LC_MESSAGES/.

This translation mechanism can also be used for customizing the text strings.

	Translations of Customized Strings
If you customize English strings, do not forget to also customize their translations, if you want to use WebYaST in languages other than English.