update translation of traditioanl chinese based on english version dated at 2026/6/15. - #618
update translation of traditioanl chinese based on english version dated at 2026/6/15.#618hjy1210 wants to merge 22 commits into
Conversation
…缺兩個 rule，變動架構十幾個， 英文版的 literal-default (mroot)有問題。geometry.yaml 缺一個rule。對數的底改成底數。
linear-algebra.yaml 變動 scalar-determinant
… covariance, zero-matrix, identity-matrix, dimension-by 修改msubsup-skip-super, log, multi-line, default-multiline/mtr, default-multiline/mtd, simple-small-matrix, default-matrix/determinant 保留 intervals 與 absolute-value。
chemistry.rs 增加 dropped_msubsup_bug_358()
…x_intent, infix_intent_no_args(), infix_intent_one_arg(), function_intent(), function_no_args_intent(), function_one_arg_intent(),
…rty() 不通過，但找不到原因.
SimpleSpeak_Rules.yaml/per-fraction(fraction)
definitions/NavigationParts add absolute-value, minus, vector, magnitude. Unicode/top paren/bottom paren. unicode/at sign,as
|
Apologies for the delay in getting to this. I've been away for four weeks. I see that a number of tests have been changed to use some English. I want to verify that this is intended. For example: |
|
@NSoiffer Yes, it is intended. Similar to trace, homomorphism, norm, kernel. |
|
At Jun 30, commit e4006a4, already pass all checks with Rust/Pre Release skipped. Last week, this pull request response file conflicts with main branch, I resolved the conflicts and make a commit 6b5eaa6, pass all checks with Rust/Pre Release skipped again. Yesterday, this pull request response file conflicts with main branch again, I resolved the conflicts and make a commit 121c3af, pass all checks with Rust/Pre Release skipped again. I wonder why? Why I need to resolve conflicts many times? My procedure steps is not correct? It seems some action(not by me) may make changes to zh/tw files. |
3 participants
update translation of traditioanl chinese based on english version dated at 2026/6/15.