-
Notifications
You must be signed in to change notification settings - Fork 117
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
Enable unicode characters for TS channel and Arma server names #996
base: master
Are you sure you want to change the base?
Conversation
(cherry picked from commit f795518)
What about using |
u8, as far as i can see, can only be used for literals, so that doesn't help much for getting the string from a variable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff! only minor changes. The PR looks good but I would like to see how the mumble plugin supports it, before merging this branch into master.
@TheMagnetar Thanks, I don't have Mumble though so I can't test this with that, someone else with that all setup will need to lend a hand with that |
For sure, this is in our hands atm. Thanks for the PR @tbeswick96 |
Mumble compatibility branch here: https://github.com/IDI-Systems/acre2/tree/mumble-unicode Tried with |
Did anyone get a chance to test this with my example? @tbeswick96 |
I've not forgotten about this, just really busy. Intending to try and get this done in a few weeks |
When merged this pull request will:
wstring
instead ofstring
string
andwstring
TextMessage
__isascii
check from running only forsetTs3ChannelDetails
procedureGrę
and a local Arma MP instance with server nameGrę
. Channel switching works as expected. All other functionality seems unaffected (Could use a smoke test if anyone is interested in building and testing)Notes:
char*
. This gets interpreted as ASCII, and the majority of data passed around inside ACRE is ASCII.setTs3ChannelDetails
. This means data is sent into it in the "wrong" format, is converted and used accordingly, and where needed passed back out in the "wrong" format. The out I think is only for channel passwords. So it may be the case that a channel password containing unicode doesn't work as expected, however the bytes remain the same so TS should interpret it correctly. I've not tested this.