Besides the documentation you are just reading (which is written in DocBook XML), MySQL Administrator uses a number of XML files for internal purposes.
mysqlx_options.xml: Stores options selected in the Options dialog.
mysqlx_status_variables.xml: Stores the status variables known to MySQL Administrator, so that they can be assigned descriptions in various languages (see below for the XML file containing those descriptions). Those descriptions will show up in the Status Variables tab of the Health section. You can select the language of the descriptions in the General Options section of the Options dialog. That file also determines in which categories or subcategories a variable will appear, and the order in which categories and subcategories appear. It does not, however, determine in which order variables appear within a category or subcategory, as those are sorted lexically by MySQL Administrator.
mysqlx_system_variables.xml: Stores the system variables known to MySQL Administrator, so that they can be assigned descriptions in various languages (see below for the XML file containing those descriptions). Those descriptions will show up in the System Variables tab of the Health section. You can select the language of the descriptions in the General Options section of the Options dialog. That file also determines in which categories or subcategories a variable will appear, and the order in which categories and subcategories appear. It does not, however, determine in which order variables appear within a category or subcategory, as those are sorted lexically by MySQL Administrator.
mysqlx_translations_administrator.xml: Stores descriptions specific to MySQL Administrator, like descriptions for status and server variables, or category names, or labels used in dialogs. Here is an excerpt from that file, which contains English and German texts:
<textgroup id="MySQLVariables"> <text id="status_var_group_General"> <trans xml:lang="en">General</trans> <trans xml:lang="de">Allgemein</trans> </text> <text id="status_var_Uptime"> <trans xml:lang="en">How many seconds the server has been up.</trans> </text> ... <textgroup id="Form_InstanceForm"> <text id="FileMI"> <trans xml:lang="en">&File</trans> <trans xml:lang="de">&Datei</trans> </text> <text id="NewConnectionMI"> <trans xml:lang="en">&New Connection ...</trans> <trans xml:lang="de">&Neue Verbindung ...</trans> </text> <text id="SaveConnectionMI"> <trans xml:lang="en">&Save Connection ...</trans> <trans xml:lang="de">Verbindung &speichern ...</trans> </text> <text id="CloseMI"> <trans xml:lang="en">Clos&e</trans> <trans xml:lang="de">Be&enden</trans> </text> </textgroup> ...
From that excerpt, you can learn a number of things:
A description (called text) does not necessarily have to be translated (see status_var_Uptime). If it isn't, English will be used instead. [SH] Mike: True?
Adding another translation is as simple as adding another <trans xml:lang="language"> tag.
Therefore, translating the software is a painless task; however, please have a look at the Notes for Translators below!
mysqlx_translations_general.xml: Stores terms and descriptions that appear not only in MySQL Administrator, but also in other graphical MySQL programs. Its format, however, is identical with the format of the mysqlx_translations_administrator.xml file. Here is an excerpt from that file:
<textgroup id="ResourceStrings"> <text id="OKBtn"> <trans xml:lang="en">OK</trans> </text> <text id="CancelBtn"> <trans xml:lang="en">Cancel</trans> <trans xml:lang="de">Abbruch</trans> </text> ...
mysqlx_user_connections.xml: This file is described in How MySQL Administrator Stores Connections.