Important notes (Read them before you start please !).

1) Before you start doing a translation, drop me an Email ! Somebody else may already be working on that exact same language you wanted to do !?

2) Determine for yourself if you want to stay involved or not (after your translation submission). If you want to do a translation but afterwards don't want to be bothered again, then we respect that but we have a problem ! When a new version is released we need to be able to update the text dlls with the new strings. If you don't like to stay involved then we'd rather not have you do a translation ! It's a pity having to remove language support once it is in !
Don't get scared, we're talking about 20 lines (or so) of text every few months.

3) The amount-of-characters-limit per string (line) is 255 characters (as per Windows system limitations).

4) Please respect the layout of the *.rc files.
E.g. text such as "STRINGTABLE" and characters such as "{" , "," , "}" etc. are there for a reason.
Make sure you nicely place texts between quotes. Also don't place quotes inside quotes to avoid problems.

5) In the Text strings itself (between the quotes " ") there are sometimes special (formatting) characters present. Please notice them and leave them in !!!
E.g. single characters proceeded by a backslash \ (e.g. \n) or percentage (e.g. %s).

6) All IsoBuster text is displayed using the MS font ' MS Sans Serif ' and the charset is set to DEFAULT_CHARSET.
This works great for most languages in combination with the localized Windows OS. However, for Japanese this turned out not to work OK. IsoBuster is able to cope with this but the language dll then needs to contain special information :

If your language requires another charset to work properly add :
RCDATA Charset
     {
    your_charset_value,
    }
to IsoBuster_*.rc. Use the IsoBuster_JPN.rc file as an example !!!
If you have no idea ... leave it as is and we'll take up the matter after your testing.

7) The *.rc files need to be in standard ANSI text format, not in Unicode. If you use TextPad for instance then that won't be an issue but if you use XP Notepad make sure that you save the *.rc files to (Encoding=) ANSI text. We can not build from Unicode texts so we will have to send them back for you to convert, we do this to make sure that the ANSI text is saved on a system with the correct code pages present etc.

8) String T_ISOB_001 inside the IsoBuster_*.rc file contains the language name that is displayed in the language selection (Options).
Provide a string that contains both the English name and the localized name (Only the localized name may contain special non-Latin characters).
E.g. T_ISOB_001 "Dutch / Nederlands"

This assures that the strings can also be recognized on systems that don't have the proper code pages for your language. Otherwise these systems will simply show some silly characters that leave no clue as to which language it really is. For instance, if the language contains non-Latin characters (e.g. Korean, Russian, ..).

9) String T_ISOB_002 inside the IsoBuster_*.rc file contains the language dll revision that is displayed in the language selection (Options).
Make sure that the revision is the (current) version of IsoBuster for which you are doing the translation. This allows to easily see which languages are up to date and which are not.
E.g. if you are working on a translation for IsoBuster 2.5, then T_ISOB_002 in IsoBuster_*.rc should contain : T_ISOB_002, "2.5". Please use the following rule to create the version number:
The program version is something like this: x.y.z.w
Always use the number x.y (for instance 2.4)
Only add the number .z if it is different from 0 (for instance 1.9.1)
Never add .w

10) Under no circumstance will we be able to financially compensate for any efforts done nor can we be held responsible for wrong or bad translations.