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

Handling custom runes mapping #54

Open
goten4 opened this issue Mar 4, 2021 · 2 comments
Open

Handling custom runes mapping #54

goten4 opened this issue Mar 4, 2021 · 2 comments
Assignees

Comments

@goten4
Copy link
Collaborator

goten4 commented Mar 4, 2021

In GSM7 official table, the character ç does not exist.
It would be great if it was possible to customize charset tables.

In my case, I could map ç to 0x09, to obtain something like this : hameÇon, instead of getting an error.

What do you think ?
Of course I can make a PR if you like !

@goten4
Copy link
Collaborator Author

goten4 commented Mar 6, 2021

Another thing about charset tables, it would be great if we can have the possibility to set a default character in case of a mapping is not found (instead of returning an error).
If the default character is not set, an error is returned, and if it's set, the encoder can use it.

@bachhh
Copy link
Collaborator

bachhh commented Mar 23, 2021

Good suggestion, I'm working on a PR for this.

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

No branches or pull requests

3 participants