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
I18n::InvalidLocaleData: can not load translations from <path> #<Psych::SyntaxError: (<path>): found unknown escape character while parsing a quoted scalar #467
Comments
Hey @hardik-plume !
|
Please provide exact steps to reproduce this issue.
…On 11 Feb 2019, 19:18 +1100, Krzysztof Knapik ***@***.***>, wrote:
Hey @hardik-plume !
1. What is the psych version you're using ?
2. Do you edit your files manually or you're using some 3-rd party tool (e.g. localeapp) ?
3. Can you provide the yaml file or can you check if you can load it manually (YAML.load_file(file)) ?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hey @hardik-plume !
`Hardiks-MacBook-Pro-3:~ hardik$ rvm list => - current=* - current && default* - defaultHardiks-MacBook-Pro-3:~ hardik$ gem list libyaml *** LOCAL GEMS *** Hardiks-MacBook-Pro-3:~ hardik$ gem list yaml *** LOCAL GEMS *** Hardiks-MacBook-Pro-3:~ hardik$ gem list psych *** LOCAL GEMS *** psych (default: 3.1.0) *** LOCAL GEMS *** i18n (1.5.3, 0.9.5)
|
@hardik-plume Please format stacktraces with triple-backticks. This is pretty unreadable at the moment. |
where did this end up? |
What I tried to do
Use I18n outside rails for my rspec test. One of the yaml strings is invalid_email_address:
"L\'adresse e-mail n\'est pas valide"
What I expected to happen
When i call I18n.t(:invalid_email_address) in my rspec, it should return string
"L'adresse e-mail n'est pas valide"
What actually happened
I actually get an error
Versions of i18n, rails, and anything else you think is necessary
i18n gem version 1.5.3, ruby 2.6.1, osx 10.14.3
same code worked on ruby 2.4.2
The text was updated successfully, but these errors were encountered: