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.

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 #6

Merged
merged 9 commits into from
Oct 29, 2016
Merged

i18n #6

merged 9 commits into from
Oct 29, 2016

Conversation

senlin
Copy link
Contributor

@senlin senlin commented Oct 24, 2016

Referring to our earlier talk on the topic of internationalisation, I finally found the time to do this.

@factmaven
Copy link
Collaborator

Thanks @senlin for the update! As I understand, this allows the plugin to be translatable? The next step is to then add the language folder and translated files, right?

@senlin
Copy link
Contributor Author

senlin commented Oct 24, 2016

You're welcome :) It indeed allows the plugin to be fully translatable. Adding translations are no longer necessary as translations are now served via Translating WordPress. But I have added the language folder and generated a pot file.

I have just added a few more files to this PR that deal with changing the text domain in the main plugin file, adding the function that loads the translation file and adding the .pot file

@sectsect
Copy link
Contributor

@senlin
Thanks for your great job👏🏻

@factmaven
I'm ready to add the Japanese translation files.
If you need other language to test, I will submit a "pull request".

@factmaven
Copy link
Collaborator

Sounds great @senlin, this is very new and exciting for me. I'll go through the code so I can understand what you've done and merge your changes for the next update.

Thank @sectsect, feel free to go ahead with adding a Japanese translation. I'm going to push the changes that @senlin made so that it's properly prepared for localization. This way Japanese can be the first language it is translated in!

@senlin
Copy link
Contributor Author

senlin commented Oct 25, 2016

Cool to hear it's exciting for you @factmaven :)
If you have any questions, please let me know.

@sectsect
Copy link
Contributor

Hi @factmaven

Can you make a other branch from @senlin 's pull request?

CC: @senlin

@factmaven
Copy link
Collaborator

@sectsect: I current have a dev branch for any new and upcoming changes. This would be the ideal place to pull the changes until everything is finalized and pushed to master.

@senlin: Please change the pull request to our dev branch. According to this post, I cannot change the merge request to the dev brand on my end. This way, no changes are made to the master until everything is finalized.

@senlin
Copy link
Contributor Author

senlin commented Oct 26, 2016

I'm afraid I don't have time for that at the moment.
Easiest is to accept my PR, then merge it into your dev branch and then make clear that all further PRs are to be committed to that dev branch.

@factmaven factmaven self-assigned this Oct 26, 2016
@factmaven
Copy link
Collaborator

No worries, I'll do that. Thanks.

@factmaven factmaven merged commit c5b8e6e into factmaven:master Oct 29, 2016
@factmaven
Copy link
Collaborator

Merged, thanks.

@factmaven factmaven locked and limited conversation to collaborators Oct 29, 2016
@factmaven factmaven removed their assignment Mar 2, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants