We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If one need piped processing for variables to do additional l10n, it's possible to use this notation:
#{variable:processor|param1|param2|...}
Examples:
#{count:localize_number}
#{date:format|short}
#{another.translation:phrase}
The same can be done for selector notation, to change selection rule:
((male|female))[:gender]
((male|female))[:ordinal]
That's not planned right now, because no real requests exist. Also syntax is subject to discuss.
Probably, that should not be done at all, because data can be prepared before passing to translate()
The text was updated successfully, but these errors were encountered:
Liquid's syntax is nice:
https://github.com/Shopify/liquid/wiki/Liquid-for-Designers#standard-filters
Sorry, something went wrong.
No branches or pull requests
If one need piped processing for variables to do additional l10n, it's possible to use this notation:
#{variable:processor|param1|param2|...}
Examples:
#{count:localize_number}
#{date:format|short}
#{another.translation:phrase}
- insert another translation by this keyThe same can be done for selector notation, to change selection rule:
((male|female))[:gender]
((male|female))[:ordinal]
That's not planned right now, because no real requests exist. Also syntax is subject to discuss.
Probably, that should not be done at all, because data can be prepared before passing to translate()
The text was updated successfully, but these errors were encountered: