Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for internationalisation - help wanted #16

Open
whitty opened this issue Dec 20, 2020 · 1 comment
Open

Support for internationalisation - help wanted #16

whitty opened this issue Dec 20, 2020 · 1 comment
Assignees
@whitty
Labels
enhancement help wanted

Comments

@whitty
Copy link
Owner

whitty commented Dec 20, 2020 •
edited
Loading

The extension is now set up for internationalisation - all I need is someone to help with actual translations 😃
@whitty whitty self-assigned this Dec 20, 2020
@whitty whitty added this to the v1.0 milestone Dec 20, 2020
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
initial import of translation files
4b45e5c 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
convert javascript text bits to getMessage
3048589 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
wire in most of the i18n messages
3a411bc 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
use alternative i18n approach for options
aafb50f 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
apply i18n to the main query summary - maybe badly
37bfe4d 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
i18n: move general apply to utils
2fa3ace 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
i18n: use the common implementation with html keys
a0418a1 
mostly

issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
convert javascript text bits to getMessage
023f737 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
wire in most of the i18n messages
d6bcb50 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
use alternative i18n approach for options
11795c1 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
apply i18n to the main query summary - maybe badly
ddc5132 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
i18n: move general apply to utils
96955f2 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
i18n: use the common implementation with html keys
374818a 
mostly

issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
avoid warning by splitting the unicode warning into parts
f1f3574 
issue #16
whitty added a commit that referenced this issue Dec 22, 2020
@whitty
avoid warning by splitting the summary text into parts
db7c9ab 
issue #16
@whitty
Copy link
Owner Author

whitty commented Dec 22, 2020

Current status is that strings should now be present in messages.json ready for translation

@whitty whitty pinned this issue Aug 23, 2021
@whitty whitty changed the title Support for internationalisation Support for internationalisation - help wanted Aug 23, 2021
@whitty whitty removed this from the v1.0 milestone Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whitty whitty

Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whitty