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

Proposal for creating a Japanese localized version #20

Open
sun-flat-yamada opened this issue Apr 24, 2021 · 4 comments
Open

Proposal for creating a Japanese localized version #20

sun-flat-yamada opened this issue Apr 24, 2021 · 4 comments

Comments

@sun-flat-yamada
Copy link
Contributor

Nice to meet you. And thank you for the great sample.

I am in awe of JetBrains' tools, they are really well done. I want my colleagues to get more familiar with this tool, so I am conducting my own Hands on.

I'm teaching it while translating it into Japanese, and I'd be happy to contribute step by step, and I'd like to send out a PR when I make a localized version in Japanese.

So I would like to discuss the directory structure of the Japanese localized version.

I think it would be better to have separate repositories, would the following structure be ok?

ex.

JetBrains
 `- resharper-rider-samples (current english version)
 `- resharper-rider-samples-ja (japanese localized version)

Best regards.

@maartenba
Copy link
Contributor

Hi @sun-flat-yamada ! First of all, thank you for stepping up with this proposal. It's really something we would like to see, so thank you in advance for this.

I'd like us to try subdirectories in the current repository (en and ja, for example), and then a README that explains in both languages where to find localized resources.

If you want, I can make a commit to make these base changes?

@sun-flat-yamada
Copy link
Contributor Author

Thank you for your quick reply @maartenba .

I think your suggestion is fine. However, if it could be improved more, I think it would be better to create a intermediate directory like a 'localized'.

My understanding of your proposal is as follow:

resharper-rider-samples
  `- :
  `- 11-Other
  `- .gitattributes
  `- :
  `- en
  `- :
  `- ja
  `- :
  `- :

And the proposal I described above is below:

resharper-rider-samples
  `- :
  `- 11-Other
  `- localized (This naming is just an idea...)
    `- en (Is this redundant? The official (master) ver is already available in en.)
    `- :
    `- ja
    `- :
    `- :
  `- .gitattributes
  `- :

What do you think?

If you can make a subdirectory for localization, I would like the 1st commit to include the current English version. I will try to publish PRs in the order of the translated ones.

@maartenba
Copy link
Contributor

That's a good idea actually. I made a commit that adds the localized folder, and added ja in there.
Not sure about the kanji I used in the localized/README.md, but I trust you will correct it if needed :-)

You can copy everything in the localized/ja folder. Does that work for you?

@sun-flat-yamada
Copy link
Contributor Author

Thanks for the quick response. @maartenba

The preparation you have done is good.
The Japanese Kanji you wrote is also perfect.

When I start working on it, I'll 1st commit the latest en version at that time and send out a PR.

Thanks.

khalidabuhakmeh added a commit that referenced this issue May 18, 2021
…gation-4-contextual-navigation

(#20) Translate into Japanese @ 01-Navigation/4-Contextual_navigation
khalidabuhakmeh added a commit that referenced this issue May 20, 2021
…gation-5-navigate-class-hierarcheis

(#20) translate into Japanese @ 01-Navigation/5-Navigate_class_hierarchies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants