肯定我們有一個帶有外側頁邊的測試案例吧。他心想。
搜尋中……嗯。沒有 抱歉，沒有該控制的測試案例！
而且……深入挖掘 git 儲存庫中的歷史記錄，發現（a）它被縫合進控制裝訂側的布林值（ifBookOpenLeft）中，而不是擁有自己的布林值。不過，BookOpenLeft 還做其他事情，例如在頁面上定位標籤，所以這是一個錯誤。（b）幾個月後，由於 BookOpenLeft 有自己的控制項，這被修正了。（c）沒有人意識到那是 唯一將 outergutter 輸入到版面引擎的地方。
因此，目前外側頁邊控制項只是在使用者界面上切換該框的開或關，就這樣……
我會嘗試修復這個問題。
Surely we have a test case with an outer gutter? He says to himself.
Searching… Hmm. Nope Sorry, no test case for that control!
And… digging into the history in the git repository, this (a) was stitched into the boolean that controls the binding side (ifBookOpenLeft) rather than being its own boolean. BookOpenLeft does other things, though, like position tabs on the page, so that was a mistake. (b) that was then corrected as BookOpenLeft has its own control, a few months later. (c) no one realised that was the only place that outergutter was getting fed into the layout engine.
So, at the moment the outer gutter control makes that box toggle on or off on the user interface, and that’s about it…
I’ll have a go at fixing that.
機器翻譯自 English
