[sanaell]

it s true for that ?

you don t want put a translation for the next amxX 0.2 ????

it s not very fair, because you can see 3 more download for each language
- 1 English
- 1 French
- 1 German

Why don t make the Amx X in internationnal version and plugin stay in original version (FRE/GER/ENG)

another idea ...
make it
LANG
\_english.inc
\_french.inc
\_german.inc

and #define LANGUAGE "english.inc"
or
#include <french>

with that we can make better modification and just post include if some error are in it without edit all and recompile all

[QwertyAccess]

its not that we dont want to put translation for amxX 0.2, we dont have the translators required to do this mostly.

[BAILOPAN]

It's not planned for 0.20. We'll come up with some sort of multi-language idea for 0.30.

[QwertyAccess]

i think 0.30 wont take as long as 0.20 is when we do the biggest changes having a new module API, and etc.

[sanaell]

Originally Posted by QwertyAccess its not that we dont want to put translation for amxX 0.2, we dont have the translators required to do this mostly.

could i ?

lmao
i can traduce if i have the good plugin

i ve just an idea betwen
multilang include or define


just in the name of plugin or version release
exemple
0.20.0 <- english release
0.20.1 <- french release
0.20.2 <- german release
you can explain that in a readme file
or
en_nameofplugin.amx
fr_nameofplugin.amx
ge_nameofplugin.amx

and give the 3 sma

i know it s more bigger that 1 files who contains all language, but it could be more clever to have only file from one language and less error

if one error is check in translation it s more easy to change and recompile the file

if you want you can contact me by msn ([email protected])

[NiLuJe]

Same Here ^^ , awaiting feedback about the translation team, could easily translate amx plugin also ;)