docs: Reconciliation #95
Conversation
|
Deploy preview for zh-hant-reactjs-org ready! Built with commit 1074114 |
content/docs/reconciliation.md
Outdated
|
|
||
| We are regularly refining the heuristics in order to make common use cases faster. In the current implementation, you can express the fact that a subtree has been moved amongst its siblings, but you cannot tell that it has moved somewhere else. The algorithm will rerender that full subtree. | ||
| 我們會定期優化演算法，讓常見的使用場景能夠更有效率地執行。在當前的實現中，可以理解為一棵子樹能在其相同階層的兄弟之間移動，但不能移動到其他位置。如果移動到其他位置，則演算法會重新渲染整棵子樹。 |
There was a problem hiding this comment.
| 我們會定期優化演算法，讓常見的使用場景能夠更有效率地執行。在當前的實現中，可以理解為一棵子樹能在其相同階層的兄弟之間移動，但不能移動到其他位置。如果移動到其他位置，則演算法會重新渲染整棵子樹。 | |
| 我們會定期最佳化啟發式演算法，讓常見的使用場景能夠更有效率地執行。在目前的實作中，可以理解為一棵 subtree 能在其相同階層的兄弟之間移動，但不能移動到其他位置。如果移動到其他位置，則演算法會重新 render 整棵 subtree。 |
There was a problem hiding this comment.
Here I think using 優化 is more appropriate for refining.
There was a problem hiding this comment.
How about 我們會定期改善啟發式演算法？
There was a problem hiding this comment.
That will be great. Just wondering why 優化 doesn't suit the situation here.
I'm a newbie to document translation, so I'd like to know the thoughts behind to avoid making the same mistake next time 😅. Thanks!
There was a problem hiding this comment.
It's my habit just like 建立 better than 創建. I want to use more accurate terms in the document instead of use coming from Simplified Chinese terms.
There was a problem hiding this comment.
I see. Thanks for sharing that.
I have amended those changes to this commit.
Co-Authored-By: Peng Jie <[email protected]>
Translate Reconciliation.md. Thanks to @chentsulin for kindly reading the draft.
Feel free to let me know if there's any suggestion.