Hello all!

Writemonkey Version 2.7 is almost done and it needs some of your attention. I prepared new language file (resx) with some new strings that are needed mostly for the new spell checking features. Please translate those. Most of you are already familiar with the process; if not, there is a brief attached to this message. **Also, don't hesitate to ask me anything, I'll gladly help you.**

New file: http://writemonkey.com/translators/Resources_en_wm235.zip

Thanks,  
i.

# Writemonkey localization project  guidelines

## The process (overview)

There is approximately 580 strings of different lengths in Writemonkey. All those strings must be translated in your language. You will be provided with base Resources.resx xml file with string names and original English strings. You will use a resource editor for head-to-head translation into your language. In the process you will create a new resx file (Resources.fr-FR.resx for example) and send it back to me. I will then send you back the compiled version of localized resources and new beta version of Writemonkey, so that youll be able to test the translated version, make adjustments ... We will repeat that process (sending the files back and forth) until you are happy with the result. The language pack will then be available for download on Wm's web site.

In the future, each new version of wm will probably ship with some new strings. At that point I will ask the translators for additional translations. If translator is not available, the users would be able to use old language packs, but with all new strings in English. If translator is not available permanently, I retain the right to find another one to finish the work.

## The resource editor

There are many free .net resource editors around, I tested some and settled with **ResEx editor 1.5 beta**. It is simple, provides comfortable translating environment and it is, as far as I can tell, reliable. If you know stuff about .net resources, you can use any editor you want, if not, dont bother, just use this one. You will find free installation at:

<http://resex.codeplex.com/releases/view/46284>

**IMPORTANT!**  
**It is imperative that you use version 1.5 beta or higher!**

### Some other options

You can also use **ResX Resource Manager** found at:

<http://resxresourcemanager.codeplex.com/>

Another possibility is Zeta resource editor. It has more functions (not that youll need them) and it works very well too.

<http://www.zeta-resource-editor.com>

To prepare your working environment (in ResEx Editor) do the following:

- Open ResEx editor, then open Resources.resx files I sent you.
- Select Tools / Add Culture. Select your culture from the list.
- Select newly created culture from the drop down menu in tool bar (if not already selected).
- You are set to go.

In the process you will create file **Resources.xx-XX.resx**. This is the file I need to compile language pack to use with Writemonkey.

**IMPORTANT!**  
When you reopen ResEx editor to continue with your work, you need to open original (English) Resources.resx file, not the resx file you created. The program will automatically open your translation file for you.

## Important points about software localization
(please read!)

We are looking for quality translations (writers are picky about words they see), so please, do not do it in a hurry. There is no deadline pressure, take your time. You can consult me anytime and request the compiled version of your work in progress to see how it performs in real world.

Translate into neutral language using standard technology terminology (Windows OS) for your language. If there are on-line tech dictionaries for your language, use them. Check also other (quality) apps on your machine 

Be creative. Avoid literal translations. They wont make sense in most cases. But do not be creative too much in a poetic sense. ;)

Be consistent. Quit and Exit for example are both correct, but choose only one and use it consistently everywhere. Make sure that your translation is consistent within and between other software products. Spell check your strings.

Try to match the length of the original string. Be short and concise. Your translations will probably be a little longer than original English ones. The majority of controls will allow longer strings, but the margin is sparse.

Use imperative mood where possible. It makes the texts easier to follow and the strings are shorter that way.

Match the original case. If string starts with lower case, translation must too, if it ends with colon, the same ... As for the exclamation marks (!)  use your language rules for them.

Do not use title case (Save As, Print Preview etc.) if that is not common in your language.

Match forced line breaks exactly! The majority of strings are one liners, but some are not. Use SHIFT+ENTER in ResEx Editor to force line break. Be especially careful when translating help card contents. No margin for error there.

Have Writemonkey open while translating to check the exact positions and context of UI strings. It will make more sense in many cases. Request compiled dll for testing any time.

## Monkey quotes

Your translation can ship without them. In that case English quotes kick in. No problem, English quotes are fine, there is no real need to translate them.

You can, if you really care, provide translated quotes in text file, one in each line, and they will be compiled into the language pack too. Not all quotes are translatable, many are language specific. Translate only those that make sense.