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

docs(aio): Add link to Japanese localization #20630

Closed
wants to merge 1 commit into from

Conversation

lacolaco
Copy link
Contributor

@lacolaco lacolaco commented Nov 26, 2017

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the new behavior?

Added a link to https://angular.jp , Japanese localized aio.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

The below contents are translated

  • index.html
  • features
  • quickstart
  • tutorial
  • glossary
  • cheatsheet

@lacolaco
Copy link
Contributor Author

Any blockers?

@lacolaco
Copy link
Contributor Author

lacolaco commented Apr 8, 2018

Our https://angular.jp is not completed localization but well-maintained and up-to-date.
It has 1600+ visitors per week. It is already used by many Japanese people.

I hope angular-l10n project is still alive...
cc/ @ocombe

@sandangel
Copy link

sandangel commented Apr 8, 2018

@lacolaco I just want to say thanks to you and the team. I'm working in Japan now and I really don't know how to explain some angular term to my Japanese colleges. Not many Japanese could use English or willing to learn it, and I was really happy when find out your site and give it to my team. I owe you one and hope could meet you in person at ng-japan conf in June. ^^

@gkalpak
Copy link
Member

gkalpak commented Apr 12, 2018

For some reason this is consistently failing on Travis, because it gets an old node.js version 😕

@lacolaco
Copy link
Contributor Author

Should I rebase to master?

@lacolaco
Copy link
Contributor Author

@gkalpak system all green!

@gkalpak gkalpak added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Apr 13, 2018
@IgorMinar IgorMinar closed this in 3bd682f Apr 13, 2018
IgorMinar pushed a commit that referenced this pull request Apr 13, 2018
@lacolaco lacolaco deleted the patch-2 branch April 13, 2018 07:28
@lacolaco
Copy link
Contributor Author

I'm really happy, and proud of joining the Angular platform! Thank you!

wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 13, 2018
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 13, 2018
wKoza pushed a commit to wKoza/angular that referenced this pull request Apr 13, 2018
@jenniferfell jenniferfell added the state: community Someone from the Angular community is working on this issue or submitted this PR label Dec 13, 2018
@ngbot ngbot bot added this to the needsTriage milestone Dec 13, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes state: community Someone from the Angular community is working on this issue or submitted this PR target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants