[^SmileY]

Hi, first of all, why not make menus with auto translations?
I not searched, but i think the developers have a good reason

Second, The Next, Exit, Back And More in new menus are not auto translatable?
If is translatable, not working in last amxx-dev release.

About menu_setprop, if the devs want to make new menus in amxx multi-language, they can add in this native something like this:

PHP Code:

native menu_setprop(MyMenu, MPROP_LANGUAGE, "en"); 


This is my idea, but lets wait someone reply this

Thanks 4 n1ce work with amxx dev!!!11!1!11

[fysiks]

You can easily make menus multilingual using format/formatex() as well as the following for the administrative options:

#define MPROP_BACKNAME	2		/* Name of the back button (param1 = string) */
#define MPROP_NEXTNAME	3		/* Name of the next button (param1 = string) */
#define MPROP_EXITNAME	4		/* Name of the exit button (param1 = string) */

[^SmileY]

Originally Posted by fysiks You can easily make menus multilingual using format/formatex() as well as the following for the administrative options: #define MPROP_BACKNAME 2 /* Name of the back button (param1 = string) */ #define MPROP_NEXTNAME 3 /* Name of the next button (param1 = string) */ #define MPROP_EXITNAME 4 /* Name of the exit button (param1 = string) */

Yes, but is not only this, i mean change all options I.E

At code:

PHP Code:

iMenu = menu_create("MY_MENU","MenuHandle",true /* ML */);

menu_additem(iMenu,"OPTION_1","0");
menu_additem(iMenu,"OPTION_2","1"); 


At Lang file:

[en]
MY_MENU = Menu Title
OPTION_1 = Option 1
OPTION_2 = Option 2

And i can change the language with a simple menu_setprop.
Maybe I'm not explaining properly, I hope you understand

[HamletEagle]

If I understood what you mean, IMO it should not be added. If you only can set the language by the native what is the point of having a ML file ? The menu will be always in the language specified by you, and someone else needs to edit the source code. If I get it wrong, please explain.

[^SmileY]

Originally Posted by HamletEagle If I understood what you mean, IMO it should not be added. If you only can set the language by the native what is the point of having a ML file ? The menu will be always in the language specified by you, and someone else needs to edit the source code. If I get it wrong, please explain.

Not, will not be static in source, because you can get amx_language convar to put in menu_setprop...

And the real purpose is use amxx language in menus by player (LANG_PLAYER) not LANG_SERVER.

[fysiks]

I don't think you understood what I said. The way that you can do this, right now, is this:

PHP Code:

new szString[64]

formatex(szString, charsmax(szString), "%L", id, "MY_MENU")
iMenu = menu_create(szString, "MenuHandler");

formatex(szString, charsmax(szString), "%L", id, "OPTION_1")
menu_additem(iMenu, szString, "0");
formatex(szString, charsmax(szString), "%L", id, "OPTION_2")
menu_additem(iMenu, szString, "1"); 


You can do this same thing with the menu properties that I mentioned above.

The only thing that you can't do with this is build one menu and display that one menu to everybody. This means you can't use global menus that don't use LANG_SERVER. This would be the only added benefit of what you are suggesting. I'm guessing it would be a significant change in the code which probably wouldn't be worth the effort.

[Nextra]

I have been thinking about doing this, as I believe it was the original intent of the (currently unused) ml parameter for menu_create(). No promises of course, but this may become a thing in the future.

[^SmileY]

Originally Posted by Nextra I have been thinking about doing this, as I believe it was the original intent of the (currently unused) ml parameter for menu_create(). No promises of course, but this may become a thing in the future.

Yes, because uses format(ex) in every additem i think can be replaced with this. Using a simple ML parameter.

I said about menu_setprop because can be added to change the language menu with a simple prop.