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

7420: Update Japanese translation for rules #308

Closed
wants to merge 3 commits into from

Conversation

mohno007
Copy link
Contributor

@mohno007 mohno007 commented Sep 20, 2021

This PR updates/improves Japanese translation of rules and its descriptions.

Update

  • Update texts based on new commits to messages.properties made after the last update date of the messages_ja.properties.
    • Support a new placeholder format introduced in Rule 2.0.
    • Use Markdown style link.
    • Add translations for newly added texts.
  • Update texts for translation correctness and understandability.

You can see decoded version of messages_ja using this script:

native2ascii -reverse core/org.openjdk.jmc.flightrecorder.rules.jdk/src/main/resources/org/openjdk/jmc/flightrecorder/rules/jdk/messages/internal/messages_ja.properties

Progress

  • Commit message must refer to an issue
  • Change must be properly reviewed

Issue

  • JMC-7420: Update Japanese translation for rules

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/308/head:pull/308
$ git checkout pull/308

Update a local copy of the PR:
$ git checkout pull/308
$ git pull https://git.openjdk.java.net/jmc pull/308/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 308

View PR using the GUI difftool:
$ git pr show -t 308

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/308.diff

Signed-off-by: Motohiro Ohno <m-ohno@atware.co.jp>
@bridgekeeper bridgekeeper bot added the oca label Sep 20, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 20, 2021

Hi @mohno007, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user mohno007" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@mohno007 mohno007 force-pushed the rules_i18n_jp_update branch from fac9758 to 48d36d4 Compare September 21, 2021 02:26
@thegreystone
Copy link
Member

Thanks @mohno007! Let me know if you need any help with verifying the OCA status! Meanwhile, I've asked a friend in Japan to verify the texts.

@mohno007
Copy link
Contributor Author

Let me know if you need any help with verifying the OCA status!

I run into a problem with OCA.
I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address.
Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use.

I have already contacted Oracle Support by email and currently waiting for a response.

I've asked a friend in Japan to verify the texts.

Thank you.
I write Java code but I'm not very familiar with Java internals and its translation, so it would be very helpful if someone could check this translation.

@thegreystone
Copy link
Member

I run into a problem with OCA.
I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address.
Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use.

@edvbld - can you help? What's the best way to help @mohno007 proceed with his application?

@thegreystone
Copy link
Member

Hi @davidbuckjp! Any chance you could take a look at this?

@thegreystone
Copy link
Member

I run into a problem with OCA. I submitted the OCA application once but I wanted to change my email address, so I withdrew it and changed my email address. Then I tried to submit the OCA application again, but I got an error which says the GitHub username is already in use.

I have already contacted Oracle Support by email and currently waiting for a response.

Have you heard back from Oracle Support yet?

@robilad
Copy link

robilad commented Oct 1, 2021

Hi, please send me an e-Mail at dalibor.topic@oracle.com and I can try to assist you to find a resolution for the OCA issue.

@thegreystone
Copy link
Member

Hi @mohno007! Just checking to see how things are going. Did you see @robilad's message?

@mohno007
Copy link
Contributor Author

mohno007 commented Oct 5, 2021

@thegreystone

Hi @mohno007! Just checking to see how things are going. Did you see @robilad's message?

Thank you for the notice and sorry for the late reply, I just realized it and send a email.

@thegreystone thegreystone changed the title Update Japanese translation for rules 7420: Update Japanese translation for rules Oct 12, 2021
@thegreystone
Copy link
Member

Hi @robilad & @mohno007 - how is that application coming along? We're starting to ramp down 8.2.0 now.

@mohno007
Copy link
Contributor Author

/signed

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 14, 2022

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@mlbridge
Copy link

mlbridge bot commented Jan 20, 2022

Webrevs

@thegreystone thegreystone self-requested a review January 21, 2022 12:09
@thegreystone
Copy link
Member

/reviewers 2

@openjdk
Copy link

openjdk bot commented Jan 21, 2022

@thegreystone
The number of required reviews for this PR is now set to 2 (with at least 1 of role committers).

Copy link
Member

@thegreystone thegreystone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs an updated copyright year.

@mohno007
Copy link
Contributor Author

mohno007 commented Jan 22, 2022

As you may know, I can sign the OCA.
Thank you to the developers for your patience.
Thank you to Dalibor-san and OCA support for resolving the issue.

@mohno007 mohno007 requested a review from thegreystone January 22, 2022 01:39
@thegreystone thegreystone requested a review from aptmac January 24, 2022 20:12
@openjdk
Copy link

openjdk bot commented Feb 2, 2022

@mohno007 This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7420: Update Japanese translation for rules

Reviewed-by: hirt, aptmac

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 57 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@thegreystone, @aptmac) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready label Feb 2, 2022
@thegreystone
Copy link
Member

Hi @mohno007! This PR is ready for integration! Please type /integrate in a new comment.

@thegreystone
Copy link
Member

Also - @mohno007, are you in the JMC dev slack? If not, would you like to be? Please ping me, and I'd be happy to invite you.

@thegreystone
Copy link
Member

Hi @mohno007 - a friendly reminder that this PR is ready for integration! Please write /integrate in a new comment in this PR to integrate.

@mohno007
Copy link
Contributor Author

/integrate

Thank you for reviewing and reminding me.

@openjdk openjdk bot added the sponsor label Feb 15, 2022
@openjdk
Copy link

openjdk bot commented Feb 15, 2022

@mohno007
Your change (at version ac631bd) is now ready to be sponsored by a Committer.

@thegreystone
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Feb 15, 2022

Going to push as commit 0002999.
Since your change was applied there have been 57 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk
Copy link

openjdk bot commented Feb 15, 2022

@thegreystone @mohno007 Pushed as commit 0002999.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants