Special characters not supported as argument to __
See original GitHub issueHi,
It seems like some special characters are not supported as argument to __
. They are replaced with a character code instead. For example, /
is replaced with /
and "
is replaced with "
.
Steps to reproduce :
index.js
const i18n = require('i18n')
i18n.configure({
directory: path.join(__dirname, 'translations'),
})
console.log(i18n.__({ phrase: "test", locale: "en" }, { var: '/' }))
console.log(i18n.__({ phrase: "test", locale: "en" }, { var: '"' }))
translations/en.json
{
"test": "{{var}}"
}
Version in package.json : "i18n": "^0.13.2"
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Characters allowed in GET parameter - Stack Overflow
The characters allowed in a URI are either reserved or unreserved. Reserved characters are those characters that sometimes have special meaning, but they...
Read more >Special characters not allowed in parameters name - Support
Hello, Would it be possible to allow the use of special characters in the parameters names ? As special I mean “?
Read more >Errors using special characters in Access databases - Office
Lists the special characters to avoid using when you work with the database object names or the field names in all versions of...
Read more >Using special characters for arguments with the CONNECT ...
The CONNECT statement which uses special characters in a password or any other parameter must be quoted in its final form.
Read more >1.3.2.1.2 Using Special Characters in Parameter Values
If a parameter value contains a special character, then the special character must be preceded by a backslash or the entire parameter value...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
please try with
{{{var}}}
- read https://github.com/mashpie/i18n-node#how-about-markupIt’s related to how mustache escapes any input. Tripple
{{{}}}
disables that.yes!.. Oof sorry for not read document properly