-
Notifications
You must be signed in to change notification settings - Fork 35
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
Audit translation tokens #1619
Comments
For reference, here is how we can get all i18n tokens in use in our software: grep -iRoh '{{_ .*}}' * > missed.html.i18n.txt
grep -iRoh 'TAPi18n.__(.*)' * > js.i18n.txt Here is an alphabetical list of all translation tokens that are in use in our HTML and JavaScript:
|
@bajiat my apologies. Here are the i18n tokens I missed:
|
@frenchbread when creating i18n tokens in templates, please do not include a space before the underscore: <!-- not like this -->
{{ _ 'token' }}
<!-- like this instead -->
{{_ 'token' }} When auditing our i18n tokens, the spaces before the underscore threw us off for a bit. E.g. we were doing a project wide search for '{{_ ', so results for '{{ _ ' did not come up. |
@brylie These ones I have most probably already removed: |
Committed the changes to my local branch. |
Go through the en. i18n.json file. Make a project-wide search and check that each token is used. If a token is not used/found, remove the token.
The text was updated successfully, but these errors were encountered: