Results (1 - 10 of 182)
- ScriptingManual: = Warzone 2100 - Scripting language manual = == Introduction == In ...
- = Warzone 2100 - Scripting language manual = == Introduction == In order for Warzone scripts to function properly two files are required: a file with a .slo extension and a file with a .vlo extension. A .slo file is the main part of the script and holds exec ...
- — 08/25/10 11:06:28
- #2119: bug: Crash in droidStartBuild, src/droid.c:1139 (pending)
- ... 54:06]Using language: Langage du système [11:54:16]Current Level/map is Sk-Aurora-T1 C:\Program Files\Jeux\Warzone 2100\warzone2100.exe caused an Access Violation at location 0043fedf in module C:\Program Files\Jeux\Warzone 2100\warzone2100.exe R ...
- — 08/24/10 12:13:42
- #2117: patch (a actual patch, not a request for one): Warzone Korean Font (new)
- Warzone 2.3.4 does not include a Korean font, so the Korean translation is currently useless. This file includes a batch of Korean ttf font files that can be downloaded and used freely. Please inspect the COPYING file for more information. ...
- — 08/23/10 17:41:45
- WikiStart: = Welcome to the Warzone 2100 Trac and Wiki = [[TOC]] Useful ...
- ... ScriptingIntroduction scripting] (using a custom C-like language called WZScript, soon to be replaced with Lua). To activate a mod, see the [http://wz2100.net/faq FAQ]. == Translations == Warzone can be [wiki:Translation translated] into every language. We don't speak all of those, so w ...
- — 08/16/10 00:06:29
- #2074: bug: Warzone 2.3.3 test run using Korean translation .mo file failed (closed: fixed)
- ... of message), I tried running Warzone with the local system language set to Korean (and the game language set to "system locale"). I created the directories necessary. (namely, locale\ko\LC_MESSAGES) I also changed the name of my .mo file to warzone2100.mo, which went inside the LC_MESSAGES folde ...
- — 08/11/10 12:49:01
- Translation: = Translation = [[TOC]] This is a quick guide to translating Warzone ...
- ... his is a quick guide to translating Warzone 2100 into other languages. There's a TranslationWindowsHowto, but be sure to read this page as well, since the howto doesn't cover everything mentioned here. You will also want to read through [wiki:Translation/Mac] as well. Be sure to check [WarzoneForum: ...
- — 08/10/10 22:16:46
- Translation/Mac: = Mac Specific Translation = [[TOC]] The Mac has a few platform specific ...
- ... po file you have been working on). If your language doesn't exist yet, use a copy of this [source:trunk/macosx/Resources/wzlocal/English.lproj/InfoPlist.strings InfoPlist.strings] file. The easiest way to edit the files is editor that understands UTF-8 (such as [http://notepad-pl ...
- — 08/10/10 17:26:29
- #2072: patch (a actual patch, not a request for one): Danish translation (new)
- I Just startede to translate it to danish
- — 08/10/10 13:28:59
- [11408]: Don't save translated descriptions in the keymap. Uses the English string ...
- ... That way, when changing the language, the descriptions will appear in the new language. Old files will still work, just show the translated string until a reset. Also mark all descriptions as translatable. Closes #2049.
- — 08/08/10 20:47:29
- [11406]: Don't save translated descriptions in the keymap. Uses the English string ...
- ... That way, when changing the language, the descriptions will appear in the new language. Old files will still work, just show the translated string until a reset. Also mark all descriptions as translatable. Closes #2049.
- — 08/08/10 20:45:37
Note: See TracSearch
for help on searching.
