|
|||||||
| PR:BF2 General Discussion General discussion of the Project Reality: BF2 modification. |
|
|
Thread Tools | Display Modes |
2010-02-09, 10:33
|
#1 |
|
Retired PR Developer
Join Date: Jun 2007
Posts: 1,781
 Germany
Location: Frankfurt, Germany
|
Official PR Manual - A call for translators
The Project Reality manual is a great document for new players new to our games or old timers coming back. To make it easier for them we try to make it accessible in as many languages as possible and for this we need your help!
To make PR more accessible to those who are having a harder time with the English language we need translate the manual into more languages. If your spoken/written English is on a good level and you want to translate the manual into your native tongue, then go ahead and contact read further! We build up our manual through GitBook. A easy to distribute and edit platform. It uses the Markdown syntax, a very easy to learn system to do formatting. We store our manual on our GitHub. This makes it easier for community members to make their own translated versions and easier to update with each PR version. STARTING A NEW TRANSLATION: Beginner's knowledge of Git is helpful, but we'll try to give all necessary information here to get you started. At any stage feel free to ask questions in this thread or PM [R-DEV]Mineral. In order for you to work on your version of the manual, you will need to create your own copy, a Git Fork. Simply go to our GitHub page and click Fork button in the top right corner. This will now create a copy fork of our Manual on your GitHub profile for you to work on. You can also then invite other users to help you by inviting them to the fork repo. While you can edit the files through the GitHub website directly, we recommend to do it in your favorite file editor (just make sure it ends up in UTF-8 format!, notepad++ is also recommended) that has some markdown support. This means you will need to get the GIT first on your pc. For this you will need to download and install Git and install your repo. Familiarize yourself with how GIT works! Best method Once you have your fork installed on your computer, we suggest you copy the 'en' folder and change the name to the 2 letter language code that you are translating into. Then you open this new folder and in each subfolder you will find README.md files. These are the chapters and therefore the files that will need translating. You will also find the SUMMARY.md which is the page table. This one will also require translation of the titles. Note that there are many links (ex. {#subchapter-name}) in the files. These are used to link to chapters within the document. It's recommended not to change these names so all the links continue to work. Also don't translate and actual folder names. Also don't change any image names. Please in the meantime let us know you are working on a translation so we can take a look and potentially help out. Completion Once you think your translation is completed let us know and request a pull request from your fork, this will merge your edits into our repo and makes your translation come live on the official manual page! COMPLETED TRANSLATIONS:
HELP WITH IN PROGRESS TRANSLATIONS: If you want to help with a translation make sure to contact those already started on a translation to get access to their Git fork. Or contact us and we'll help out. You can see all current forks here. OLD TRANSLATIONS: Here is a list of translations of old manuals. They will all have a folder prepared on the Git to be started from. They need to updated to the new Markdown format as well be checked for changes between v1.3.1 and the current version. If you are willing to help you can do that by creating a Git Fork and editing within the language's folder. If you need any help contact [R-DEV]Mineral or post in this thread.
|
|
|
|
Last edited by Mineral; 2024-01-04 at 15:51..
|
| Tags |
| call, manual, official, translation, translators |
|
|
View Spearhead's IP Address
Threaded Mode