<h2>Translations instructions</h2>\r
<ul>\r
<li><a href="#translate">I want to translate into my own language</a></li>\r
+ <li><a href="#whatToTranslate">What can I translate?</a></li>\r
<li><a href="#developer">Instructions for those who know Subversion and Visual C++</a></li>\r
<li><a href="#everybody">Instructions for everybody else</a></li>\r
<li><a href="#shellextension">Translating ShellExtension</a></li>\r
\r
<p class="important">Please remember WinMerge is an Open Source project. Send translation updates to us as <code>.rc</code> file source patches. We WON't accept modified <code>.lang</code> binary files. We need the sources.</p>\r
\r
+<h3><a name="whatToTranslate">What can I translate?</a></h3>\r
+Listings below show what you can actually translate for WinMerge. And what is\r
+not useful to translate.\r
+\r
+You can translate:\r
+<ul>\r
+ <li>WinMerge program (visible strings, dialogs, messageboxes)</li>\r
+ <li>Explorer integration component (ShellExtension)</li>\r
+ <li>Installer<li>\r
+ <li>Read-me text shown in installer and in Start-menu</li>\r
+</ul>\r
+\r
+Currently you cannot translate:\r
+<ul>\r
+ <li>User manual</li>\r
+ <li>Web site</li>\r
+ <li>Various other documentation</li>\r
+</ul>\r
+\r
+Yes, we know, translating user manual would be a good thing. But currently we\r
+don't have a way to compile and show translated manual to users. If somebody\r
+can help us with this, we are of course interested.\r
+\r
<h3><a name="developer">Instructions for those who know Subversion and Visual C++</a></h3>\r
<p>Grab a copy of the source from <a href="http://sourceforge.net/svn/?group_id=13216">Subversion</a>.</p>\r
<p>You will need to translate all the strings in <code>Src\Merge.rc</code> to your language. Make a <code>Merge<em>YourLanguage</em>.rc</code> and upload it to SF.net as a patch <a href="http://sourceforge.net/tracker/?group_id=13216&atid=313216">here</a>.\r