Biuro Fornet MK wrote:
Dear Sirs.
I represent Polish company. We start currently a project - kind of computer helpdesk, where we advice (because of lot of reasons) moving to Linux to our customners.
While they are in most cases very sceptic about this, your Wine makes a great help for us. Unfortunately, the English language is still the biggest barrier for Polish customers.
Thats why we would like to contribute to Wine development and spreading a "good hope" :) in the way we can afford right now.
I would like to propose:
- full translation of your WWW page to Polish, and setting this
"localisation" at our www host.server.
You can browse the source for the main wine site is here: http://cvs.winehq.org/cvsweb/lostwages/
It should be possible to translate this site and bugzilla as well, both have been built with translation in mind the AppDB is much harder and I do not know about the wiki.
export CVSROOT=:pserver:cvs@cvs.winehq.org:/home/wine cvs login (password cvs) cvs checkout lostwages
Mail patches to:wine-patches@winehq.org with the prefix [LOSTWAGES] so the website maintainer can easily see them.
- full translation - or help if anyone started, although i cant find
any note on your site - of Wine software: GUI/API/DOCS/help docs into Polish.
2.1 I think you get more bang for you buck with this stuff. Translating the documentation (at least the users guide and FAQ) is a good idea.
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/wine co -P docs
When prompted for a password press the enter key. A subdirectory named docs will be created.
Mail patches to:wine-patches@winehq.org with the prefix [WINEDOCS] so the maintainer of the documentation can easily see them.
2.2 Also keeping the resources files (*.rc), for winecfg at the very least, up to date would be very much apreciated by Polish users. There is also the README in the root of wine.
export CVSROOT=:pserver:cvs@cvs.winehq.org:/home/wine cvs login (password cvs) cvs checkout wine.
[snip stuff about customer support]
I would start with translating the documentation and resource files before tackling the web site(s) but that is up to you.
--
Tony Lambregts