tats-u
1
English:
Remove the node_modules folder and your package manager’s lock file using the following:
Japanese:
node_modulesフォルダとパッケージマネージャのロックファイルを以下のコマンドで削除します。
False-Positive QA Issues:
The source text ends with “:”; replace “。” with “:” at the end of your translation.
Japanese has no customs to use colons in normal text. Never suggest this unnatural change.
TaniaM
2
Hi @tats-u ,
Thank you for pointing this out! We have created a task for our developers to improve this behavior.
Hi @tats-u,
Just a quick update to let you know that the task has been completed, and the changes to the QA checks have been made.
Thanks a lot for pointing this out! Feel free to test it and let us know if it’s working as expected or if there’s anything else we can improve.
tats-u
4
Thank you for the info, but it does not seem to be work properly…
tats-u
5
Also, there is another false-positive QA issue:
The last ASCII semicolon must never be a fullwidth one because it is a part of import statements in JavaScript (strictly speaking, MDX).
Iliana
6
Hi @tats-u,
Thanks for providing your feedback. I’ve shared it with the development team, and they’ll be investigating the reasons these QA checks are appearing.
tats-u
7
The replacement suggestion can be more than one in Japanese (or possibly Chinese).
| English punctuation |
Japanese replacement candidates |
| ( |
( or ( |
| ) |
) or ) |
| . |
。 or . |
| , |
、 or , |
| : |
。 or : or : |
| ; |
。or 、 or ; or ; |
| " |
“ or ” or 「 or 」 or " |
You may have to show a message like:
The source text ends with “;”; replace “!” with “。”, “、”, “;”, or “;” at the end of your translation.
TaniaM
8
Hi @tats-u ,
Thanks! Passing to the team.
Sofiia
9
Hi @tats-u!
Just letting you know that we have created a separate task for our developers on this matter. We will let you know asap once it is done!