-
Notifications
You must be signed in to change notification settings - Fork 12
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
Allow alternative placeholders for unknown characters #4
Comments
In my fork I've made |
I think both would be useful. |
let custom_replacement = "?";
"string".chars().map(|c|deunicode_char(c).unwrap_or(custom_replacement)).collect::<String>() |
I moved this over to kornelski#1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the docs
In my use case, I already have a placeholder character. I'd rather not do a search/replace in strings for
[?]
in case a user has that. It'd be nice if I was given the option to set what the placeholder would be.The text was updated successfully, but these errors were encountered: