Question About Tbamud localization

First of all, the command in the original English code is as follows:
Command <argument> or Command <argument> <argument>
However, in Korean, the command comes after:
<argument> Command or <argument> <argument> Command
This problem was solved by creating a reverse_order function in the command_interpreter function.
I'm trying to modify the trg file to make the teleport trigger work.
en~ appears to be the enter command.
The enter command has been localized into Korean as "입장".
The localization command for look is "봐".
The localization of the teleport command is "텔레포트".

The full code for the localized #65401 trigger is as follows:
I entered a trigger command in a room with an object that has this trigger applied, but it is not working.
English is entered as follows:
enter gate
Korean is entered as follows:
문 입장

Do I need to modify a specific function to input the commands in a different order?

I think if the command and arguments were passed,
The sentence should be printed to the screen, but it is not.
I think the arg and command are not being passed.

For debugging, I suggest simply making a trigger with the body 

%echo% cmd=%cmd% actor=%actor.name% arg=%arg%

This shows you what the script receives.

First, I modified the trg file as you taught me, like this:

#65401
Obj Command 65401 - East Gate Midgen~
1 c 7
입~
%echo% cmd=%cmd% actor=%actor.name% arg=%arg%
if %cmd.mudcommand% == 입장 && 문 /= %arg%
- The rest is omitted -

I entered a command, but no message was echoed.

I modified the command_otrigger file as follows:
int command_otrigger(char_data *actor, char *cmd, char *argument) {
obj_data *obj = NULL;
int i = 0;

send_to_char(actor, "cmd : %s\r\n", cmd);
trim_spaces(argument);
send_to_char(actor, "argument : %s\r\n", argument);

cmd and arguments are printed to the screen.
cmd : 입장
argument : 문

I changed trig arg to another word according to the trigger manual, but it doesn't print on the screen.
@n#<virtual number>
<trig name>~
<attach type> <trig type> <numeric arg>
<trig arg>~
<command list>
~

And, in interpreter.c, do_enter is localized into Korean as follows:
{"입장", "입장", POS_STANDING, do_enter, 0, 0, FALSE, ACTION_NONE, {0, 0}, NULL},

The object trigger issue was resolved by removing the trigger from the object and setting the object option to portal.

I finally found the cause.
I was testing the mud as a super administrator account all the time.
I commented out
else if (!IS_SET(bitvector, DG_ALLOW_STAFFS) && GET_LEVEL(ch) >= LVL_GRSTAFF) in the valid_dg_target function in the dg_misc.c file and the problem was solved.