-
Notifications
You must be signed in to change notification settings - Fork 143
Why does expr_text() behave differently for variables containing non-ASCII characters? #691
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
Comments
Hello Hiroaki, could you install dev rlang and take this for a spin please? I'd like to make a quick patch release soon. I have run R CMD check for dplyr on Windows and found no issues so hopefully it doesn't break anything for non-unicode locales. |
Sure, I'll do it later today or tomorrow. |
Confirmed this issue is fixed on Windows. Thanks! library(rlang)
expr_text(sym("あa"))
#> [1] "あa"
expr_text(sym("aあ"))
#> [1] "aあ" Created on 2018-12-13 by the reprex package (v0.2.1) (By the way, I remembered I reported this issue from macOS; On Windows in my locale |
Thanks! Please also let me know if you see anything weird while working with dplyr/ggplot2. |
Sure 👍 |
(original issue: tidyverse/ggplot2#3017)
If the expression is a symbol and it has any non-ASCII characters,
expr_text()
adds backticks except when the character is at the head of the variable name. I'm failing to see the rule behind this... Is this intended? I feel backticks should not be added at all as long as the characters are representable in the current locale.Created on 2018-11-27 by the reprex package (v0.2.1)
Session info
The text was updated successfully, but these errors were encountered: