From: Christian List <list1974@ho...> - 2003-12-05 02:47:44
Hi Hoa, Nguyen Huu
What you need to do, is to translate the strings in the file Merge.rc into
Your translated file should be named MergeVietnamese.rc and be placed under
You can download the full source for WinMerge 2.0 from:
and look at the other translations to get an idea how to do it.
When you are done, then please upload your files as a patch here:
Then one of the WinMerge developers will make sure it gets included in the
CVS source tree and made available for download to the public.
Please let us know if something is unclear, or if you need more help.
----- Original Message -----
From: Nguyen Huu Hoa
Sent: Wednesday, December 03, 2003 10:44 PM
Subject: [Winmerge-support] Add support for Vietnamese language
I'm interested in this project and want to add support for Vietnamese
language, but don't know where to start. Could some of you point it out?
Hoa, Nguyen Huu
From the experiences I had with the last new translations, the message probably needs some update.
I just noticed that :
- if the translator localizes only the 2.0, then the translation does not work for 18.104.22.168 or for cvs. For myself, and
until now, I updated the localized rc for cvs, but I am afraid I won't have time and envy do go on doing it.
- the swedish translator on the other hand translated both 2.0 and 2.1. That was great :). But he localized 2.1 cvs (not
22.214.171.124), and tried to update to cvs during one or two weeks, and this was quite messy to handle. Because during the
delay I required to apply his localization, he already had posted a new version.
- as we branch the 126.96.36.199, we may probably add new translations to the next updates of 188.8.131.52. So this makes now three
localizations : 2.0, 184.108.40.206 and cvs... (BTW can we post the 220.127.116.11 localization as a separate file to avoid updating
the whole beta ?)
The point I am pretty decided for, is that translators should localize at least two versions, 2.0 and 18.104.22.168 or cvs.
22.214.171.124 to cvs update is probably quick and may be done by us. For practical reason, I prefer the second version to be
for 126.96.36.199 rather than for cvs, but I have no firm idea about it.
Christian's message is very clear, and I prefer him to decide for the new formulation, so I just explained my wishes.