| 11 | | If you're making a new translation (from English), you can download the [http://openvpn-gui.git.sourceforge.net/git/gitweb.cgi?p=openvpn-gui/openvpn-gui;a=blob_plain;f=openvpn-gui-res-en.rc;hb=HEAD openvpn-gui-res-en.rc] using the [http://openvpn-gui.git.sourceforge.net/git/gitweb.cgi?p=openvpn-gui/openvpn-gui;a=tree GitWeb interface]. If you know your way around [http://git-scm.com/ Git] |
| | 11 | If you're making a new translation (from English), you can download the [http://openvpn-gui.git.sourceforge.net/git/gitweb.cgi?p=openvpn-gui/openvpn-gui;a=blob_plain;f=openvpn-gui-res-en.rc;hb=HEAD openvpn-gui-res-en.rc] using the [http://openvpn-gui.git.sourceforge.net/git/gitweb.cgi?p=openvpn-gui/openvpn-gui;a=tree GitWeb interface]. If you know your way around [http://git-scm.com/ Git] (or see our [wiki:GitCrashCourse git crash course]), checking out the latest development code from [http://sourceforge.net/scm/?type=git&group_id=248281 here] and sending in a real patch makes the life of OpenVPN-GUI developers easier. However, this is not by any means mandatory. In either case, you need to translate all English sentences in the English rc file. The portions that need to be translated are not clearly marked, but they in most cases be obvious enough. You should not translate any of the variables, or the GUI won't work properly. For best results you should test the translation in the GUI to make sure it works properly and that the translations make sense. |
