To create a new translation, first prepare your system to compile emc and get a checkout of the current source code, as described here: Installing EMC2.
After compiling emc2, you will find several files with the ".pot" extension in the src/po directories. For each of these you copy the file to a new ".po" file for your language--the two letter code for Spanish is "es". For example, copy "rs274_err.pot" to "es_rs274_err.pot". At the top of the file, enter some information that identifies the translation, the translator, and so on.
Next, for each message in es_rs274_err.pot, write the translation. (For messages that you skip, the original text will be shown instead)
When you want to test your translation, execute "make" again, then run the version emc you built.
There is more information about the process of producing translations in the file src/po/README, and in the documentation for gnu gettext which you can see by running 'info gettext' in the terminal after installing the gettext package.
If you are a developer, simply check in the .po and .msg files after you have updated and tested them. If you are not a developer, then e-mail a developer the updated version of these files.
|.po file pattern
|Used to translate
|all files in tcl/ including the mini and tkemc GUIs
|the interpreter's error messages
|the axis GUI and other Python programs
AXIS has translations for German, Hungarian, Italian, Portuguese, Romanian, and a couple more. There are translations for German, Romanian, and a partial Japanese translation for mini and TkEmc. You can use TkEmc or mini in your language by exporting the LANG variable with the ISO two-letter code for your language. On Ubuntu machines running AXIS, it may be necessary to set both LANGUAGE and LANG (e.g., LANGUAGE=de LANG=de_DE.UTF-8) or unset LANGUAGE and set only LANG.
export LANG=de ; scripts/emc
env LANG=ja scripts/emc