Skip to content
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

[feature] UTF8 encoding and join SMSs #5

Open
rchovan opened this issue Mar 16, 2020 · 1 comment
Open

[feature] UTF8 encoding and join SMSs #5

rchovan opened this issue Mar 16, 2020 · 1 comment

Comments

@rchovan
Copy link

rchovan commented Mar 16, 2020

Hi,
I'm using script for telegram notification, but messages are received without diacritics. Is there a way how to display them correctly ? And 1 long message is distributed as 2 notifications, can it be joined into single notification ?

image

Same behavior is visible in emails too:

image

@eworm-de
Copy link
Owner

I think both of these are not easy to solve.

As for as I know RouterOS is not aware of any encoding, just using ASCII characters. I just added a degree sign (which is not ASCII) in 63ed093. Had to use the UTF-8 hex values... To solve this I would have to maintain character tables for every encoding I want to support, then do the decode and encode within the scripts. I do not think this will happen.

The split SMS bother me as well. A SMS has a maximum length of 160 characters, longer text can be split to several SMS. As far as I know the text for individual split SMS is reduced, instead some control characters for assembly are added. Sadly I can not access these control characters from RouterOS.
Reliable assembly of messages from what I have is pretty impossible.

If you have ideas to solve this let me know. Also feel free to contact support for propper support of split SMS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants