中文术语翻译

[likui628]

这个 issue 帖用于讨论确定翻译用语。

en	zh
Challenge	挑战
Solution	解答
References	参考
variadic tuple types	可变元组类型
type inference	类型推导
conditional types	条件类型
generic	泛型
flat type	普通类型
intersection types	交叉类型

[likui628]

e.g.
How about translating 'solution' to '解答' ?

[chenxiaoyao6228]

From my point of view, both '解法' and '解答' are OK, we can just use '解答'

[ghaiklor]

Can we close this one, did you have an agreement?

[charleserious]

I agree with "解答" too, kind more written terms.
And we already have a merged PR that follow this convention.

[likui628]

Close it later, we can discuss more terminology translation

[charleserious]

@likui628 @chenxiaoyao6228 we may need a way for collaborate with each other of our translations, letting others know the solutions you're working on.
I think the draft PR is a nice way for that, after we picked the solutions we directly push a draft PR, so that others could avoid duplicate works.
BTW, I'm curious how may of us are work on the Chinese translation?
cc @ghaiklor

[likui628]

@charleserious Absolutely.
we three guys are working on the translation.

[ghaiklor]

You can have a checklist of translations, where you tick anything that is in progress or done. I can create another issue where you can do it. Maybe this one can be closed then.

[ghaiklor]

Here is the issue - #171. Can you check if you are able to tick the boxes in the list?

[charleserious]

I think @likui628 wanna a place to put the technical terms. Maybe we could have a wiki page for that kind of staff.

[ghaiklor]

@charleserious what about having a GLOSSARY.md file in the root with language categories. There you can define all the words. Maybe other languages will join as well, although, I'm not sure in it. It's not a huge project, so there is definitely should be a balance between maintaining the project and expected result.

[charleserious]

Thanks @ghaiklor that’s nice, I think the GLOSSARY.md is great.
How’s your thoughts? @likui628

[charleserious]

@ghaiklor I've pushed a PR to fulfill what we discussed here and named the file in README.md.
And forgive my pool ruby practice.

[likui628]

I have no idea.
I still think it would be more convenient to discuss it here.

[ghaiklor]

@likui628 whatever suits you. I have no objection to have the glossary in the root anyway. The only thing that I'm thinking is that this file will be used by you only, which makes me think it has no usefulness in there 🤔

[charleserious]

I think we need a formal place to arrange our thoughts and to put our conclusions so that we can have a convenient way to collaborate with each other with the minimum effort.
And don't worry that we will overturn periodic summaries from time to time, that's reasonable.
@ghaiklor @likui628

[ghaiklor]

@charleserious let's add the meaning of the terms in the PR #172 and I'll wait the vote of @likui628. Once we came to the consensus about the GLOSSARY.md as a file, I'll merge the PR.

[likui628]

I find two examples for us.

1. vuejs-translations/docs-zh-cn
2. zh-hans.reactjs.org

By now, the glossary is still in process. so I suggest using the issue temporarily.
@ghaiklor @charleserious

[ghaiklor]

Ok, so waiting the PR to be ready to merge, including:

• GLOSSARY.md in the root of the repo (we are not a huge organisation, why complicating things)
• Having English and Chinese terms mapped
• Having a meaning of each mapping

Does everyone agree?

[charleserious]

I'm a little busy recently, but I'll make the PR #172 done.

[likui628]

agree