Translate glossary

[tesseralis]

No description provided.

[smikitky]

As a starter, I have a glossary and a tentative translation guideline, which is a little outdated but was actually referred to by existing translators. Maybe this can be migrated here.

https://gist.github.com/smikitky/15f1332ec1d820b96159ccb56e6862a3

I know this is considerably inconsistent with the guideline of Vue available here. @potato4d, do you have any thoughts?

[smikitky]

And here's the existing translation of referece-glossary.md (~80% done as of today)

https://crowdin.com/translate/react/2976/en-ja

[potato4d]

@smikitky

Thanks for your comment.
I think that you can generally use the terms. LGTM.

Regarding guidelines, I think it is difficult for people to see their eyes.
While detailed rules comply with gist, how about base in JTF Style?
by this, we can use machine check with TextLint.

I will take a closer look at your guidelines tonight!

[smikitky]

In fact, I wasn't aware of the JTF guideline until yesterday. Looks like JTF has two rules that clearly conflicts with Vue's rule (I prefer Vue's rule, though):

5. カタカナ語の語尾の長音は省略しない。
6. 半角文字と全角文字の間に半角スペースを入れない

[potato4d]

The reason for conflicts is that the Vue Community has customized the rules.

And that is described in this part of the document.

https://github.com/vuejs/jp.vuejs.org/blob/lang-ja/CONTRIBUTING.md#%E7%BF%BB%E8%A8%B3%E3%82%B9%E3%82%BF%E3%82%A4%E3%83%AB

Some customization rules for Vue.js official website

I also think that Vue's style is desirable, so I would like to incorporate it.

@smikitky
I will submit a Pull Request to add CONTRIBUTING.md tonight.

Will not you discuss with it using Review Comment?

[tesseralis]

We should start a "style guide" page in the wiki with what we decide, even if it's just "use the same rules as vue".

[smikitky]

Okay, I think we can use textlint and that .textlintrc.

@potato4d I feel Japanese-specific style rules (e.g. 長音符) should live on Wiki rather than CONTRIBUTIONG.md, as @tesseralis suggests?

[tesseralis]

My main concern is that the repo should reflect the main react one as much as possible (e.g. we might want to copy over that version of CONTRIBUTING.md) in the future. Also we're still in the early stages and deciding what rules we want to follow so it makes more sense to keep it in a wiki.

Once we settle on the rules better, we can add it to the repo itself.

[tesseralis]

Ooh textlint is cool. I can recommend that to the other translations as well and maybe the english version as well hehe...

[smikitky]

For the meantime, let me use this translation for "boxed" text:

• Tip → ヒント
• Note → 補足
• Warning → 警告

[koba04]

+1 for using textlint.
It would be nice if we could create own dictionary using textlint-rule-prh like this

[potato4d]

@tesseralis @smikitky

React thinks that it is better to make CONTRIBUTING.md of React.
Then, let's merge it with the one of @smikitky's gist, incorporating Vue's example as an example!

[tesseralis]

@potato4d @smikitky @koba04 I added a TRANSLATION.md file to each of the forks to serve as a general language guideline.