Mutiplicity 3.6 Localization Feedback Thread
With our effort to include more languages for Multiplicity, we are creating this thread so that users can report any observed issues.
The primary focus for this release is the addition of localization support to Multiplicity - the added languages are in the Changelog below.
We employed a new process for generating translations and need to be confident that the translations meet the quality standards we have set for the product. Thus, what we are looking for is feedback from users who speak English fluently and any of the newly supported languages.
At this stage, it does not matter if you only have 1 PC (MP is designed to be used on 2), the evaluation of the language files detailed below is what we are initially interested in. Anyone who contributes meaningful feedback and assists with translations will be eligible to receive free license of Multiplicity KVM Pro - a $99.99 value.
With that, you can start by installing RC 1, starting a trial, or entering your current Multiplicity 3 credentials for activation.
Obtaining Multiplicity:
It is available via direct download only:
https://cdn.stardock.us/support/uploads/Multiplicity_3.6-j81-Setup.exe
Where are language files stored?
\Program Files (x86)\Stardock\Multiplicity\lang
The .lng files listed there are human-readable text files - easily edited in Notepad or any text editor you prefer.
How are language files formatted?
The format is:
'English text'='translated text'
English (en) file example:
"Cancel connection"="Cancel connection"
Spanish (es) file example:
"Cancel connection"="Cancelar conexión"
There is a list of reserved words that are intentionally not translated:
"Multiplicity", "Primary", "primary", "Secondary", "secondary", "Hotkeys", "hotkeys", "Seamless", "seamless", "hotkey", "HotKey", "Hotkey"
Also, where 'Computer' or "Computers' is seen in English, it is replaced with 'PC' and 'PCs' respectively in the translated text.
The following is an example of what we are looking for in a reply post:
Lang file: (es.lng for example)
Follow by blocks of:
Line number (Notepad++ has them for example):
Old traslanted text:
New translated text:
Reason for edit: ('Poor phasing' or 'confusuing \ conflicting direction')
Any 'New translated text' suggestions should be kept as short as possible as the MP UI was designed to fit the English text shown.
We do not need every line evaluated, however, we need enough to see if there are categorical patterns of issues we can address.
Grading the translation
Finally, we are looking for a letter grade you would give the translation as a whole:
A=No changes needed
B=Few issues but acceptable
C=Needs to be reworked before shipping
D=This is not a viable method for translating software
Thank you for your interest and any time you put into making Multiplicity a better product.




