Testing the content and the file type
- Pseudotranslate: Copy Segments – Copies the source segment into the target segment without any modification.
- Pseudotranslate: Increase Segment Size – Pads the size of the target segment by appending extra characters in the target, as a configurable percentage of the source segment.
- Pseudotranslate: Replace Each Character – Replaces each character of each word in the source with a user-specified string.
- Pseudotranslate: Replace Each Word – Replaces each word in the source with a user-specified string in the target.
- Pseudotranslate: Reverse Each Word – Reverses the letters in each word in the source segment.
- Pseudotranslate: Wrap Each Segment – Wraps the source segment with a user-specified prefix and suffix in the target.
- Pseudotranslate: Wrap Each Word – Wraps the words in the source with a user-specified prefix and suffix in the target.
- Make sure that all of the translatable content has been properly exposed for translation. For example, if you were translating the strings of a product, you might do a pseudo translation and then look to see if all the strings in the application were translated.
- Make sure that your file type can handle large strings. When you translate from English into languages like German, the strings get much larger. You can test to make sure that your file type is correctly set up to work with longer strings.
- Make sure that your file type can handle the source and target character sets. You might need to handle character sets like right-to-left languages or multibyte (Asian) characters.
You can do all of this without paying anything for translation. Once you have done all of this, and fixed your application to handle all of these cases, you can then do the real translation and feel confident that your file type is ready.
X", when you looked at the translation, it would look like this:
XXXX XX X XXXX. XXX XXXXX XXXX. XXXX XXXX.
This is a test. XXX XXXXX XXXX. XXXX XXXX.
This is a test." was not translated and should have been. This points to a problem that you need to investigate.
Alternatively, if you replaced every character with the string "XX", it would double the length of every string and would allow you to see how the file type responds to longer strings. Similarly, if you replaced every character with an Asian character, you could see how the file type responds to multibyte characters.
[" and "]", the resulting translation might look like this:
[This is a test.] [This is only a test.] [This is a test of the emergency broadcast system.]
This is a test. [This is only a test.] [This is a test of the emergency broadcast system.]
You can see that "This is a test." is not surrounded by brackets. This means it wasn't exposed for translation.