New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: russian commands doesn't work properly #799
Comments
@op-hui: Could you also post the source code for your "команда" command? |
class CmdTest(Command):
key = "команда"
aliases = ["команда2"]
locks = "cmd:all()"
help_category = "General"
def parse(self):
"Very trivial parser"
self.target = self.args.strip()
def func(self):
"This actually does things"
caller = self.caller
if not self.target or self.target == "here":
string = "%s команда." % caller.name
caller.location.msg_contents(string, exclude=caller)
caller.msg("Ты команда")
else:
target = caller.search(self.target)
if not target:
# caller.search handles error messages
return
string = "%s команда на тебя." % caller.name
target.msg(string)
string = "Ты команда на %s." % target.name
caller.msg(string)
string = "%s команда %s." % (caller.name, target.name)
caller.location.msg_contents(string, exclude=[caller,target]) |
@op-hui I can't test this right now, but what do you get if you do |
Got it, put debug before caller.search |
Bug presented in webclient and telnet sessions |
Between command named 'команда' and player name (named anonymous) i can put ANY THREE CHARACTERS:
|
Thanks for the further info. My first guess is that this may be a regex error in Evennia's command parser, possibly it is not setting the |
This is resolved in a7e42b2. Closing. |
Steps to reproduce the issue:
If put THREE spaces between utf-8 russian command name and plaername, they will fork fine
What I expect to see and what I actually see (tracebacks, error messages etc):
I see: команда player -> Could not find 'ayer'
I expected: команда player -> ok
No error messages in log
Extra information, such as Evennia revision/repo/branch, operating system and ideas for how to solve:
The text was updated successfully, but these errors were encountered: