Closed ryukato closed 6 years ago
I think a different directory for the language you're implementing would be good approach.
By the way, thanks for offering to translate the reference guide to another language (guessing Korean if you add kr
to the file name), but I do want to ask you if we can expect a level of dedication on this.
We're not that versed in Korean, so any new additions we'd do to the Reference Guide would require an adjustment from your hand to fill the blanks.
Do you have the time for that?
Additionally, an added disclaimer to point out that support of the other language comes from you as a contributor would help I'd assume.
Does the required commitment change your stance to providing a Korean version of the Reference Guide?
I've been thinking the dedication and responsibility for the managing docs in Korean. Ok I will and can do that. And If I have something coming up and I can't have time for providing Korean version of docs, then I will let you know.
I'm already doing some work on it so I will let you know when I am done the first version of translation.
Great to hear you're willing to provide this @ryukato, much appreciated! Looking forward to the Korean docs, even though I cant read them. :)
if I want to translate this docs, how can I name each files? can I give a name of file with language code at the end of the name like "architecture-overview-kr.md"?