How can I help?
OK, MPUI is great software (YMMV), but it is far from perfect. If you have some spare time and are willing to help MPUI to become even better, here is what you can do.
First of all, please mail me about your experiences or problems you had with MPUI. I'd also like to read suggestions for new features or improvements on the existing ones.
If you download the source code package of MPUI, feel free to have a look at the
mo_??.pas files and create a new file in your own native language. But be prepared for some amount of maintenance – the texts sometimes change, or new ones will be added!
You can also translate the MPUI website into your language. If you want to do that, please note that ...
- each page is generated using a »bare-bones« version of the page content. The content file is a complete HTML file by itself and can also be viewed directly. The URL is derived in the scheme
$page.$language.html, for example http://mpui.sf.net/?page=contribute&lang=en is actually http://mpui.sf.net/contribute.en.html plus some graphical and navigation stuff. Simply study the existing files to get an idea about how it is done.
- each language has a language description file, for example http://mpui.sf.net/locale/en. This file has to be translated, too.
- the files are always UTF-8 encoded, regardless of what is (or is not) specified in the HTML header.
- the Changelog page and the contents of the Roadmap page (except the headings) will not be translated.
- as with program translations, you should be aware that the translation has to be maintained.
Website and documentation improvements
If you have some corrections or additions for this website or general MPUI documentation, or you are even willing to completely maintain it, please let me know.
If you really dare to, you can also directly send patches to the MPUI source code, subject to the following recommendations:
- I mean patches. A patch is a diff between the latest MPUI version and the one modified by you. I will not accept complete source code packages.
- Neither will I accept code that greatly differs from the coding style of MPUI.
- Also, try to keep patches as small as possible. I want to have some amount of understanding of what MPUI's code does, so I need to be able to understand what the patch does without too much headaches. If you modify large parts of MPUI, you should rather fork the whole tree and create an own version.