Open jooyunghan opened 1 year ago
- use
*text*
instead- fix MD parser to support
_text_
Are you suggesting updating the English text to use *
instead of _
? I think we're mostly using *
right now, but it turns out that we have guidelines for this and they ask us to use _
instead: https://developers.google.com/style/text-formatting.
My plan is to reformat everything to be consistent when #318 is fixed. I'm hoping to find a volunteer to fix that issue before I do it myself :smile:
Btw, in Korean, we don't use italic to emphasize in general. Instead, we use bold or 'quote'. I'd like to avoid italic in Korean translation.
Okay, I love that you take that into account in the translation! You should not feel tied to the English source text (and it's formatting) here. So please translate *text*
into **text**
as you see fit in the Korean translation.
I thought only fixing in the Korean translation 😃
I thought only fixing in the Korean translation smiley
Okay, sounds great then!
Todo:
- s/블록/블럭 per @jiyongp 's suggestion in https://github.com/google/comprehensive-rust/pull/455/files#r1117272813
https://www.korean.go.kr/news/index.jsp?control=page&part=view&idx=10192&preview=null says 블록 is right.
Hi @jooyunghan, is this still something that we need to fix?
_text_
doesn't work when it's in the middle of a word: e.g. AbcdefIn Korean translation, there's so many cases due to postposition (-이/가, -을/를, -은/는..) in Korean language system.
Note
*text*
works: e.g. Abcdef.Ideas:
*text*
instead_text_
Btw, in Korean, we don't use italic to emphasize in general. Instead, we use bold or 'quote'. I'd like to avoid italic in Korean translation.