我已經提交過回饋，但我也在這裡陳述我自己的觀察。
我認為發布文件應該解釋為什麼以及何時需要「選擇啟用」。當我實驗新功能時，我有很多與 Kent 相同的困惑。
我認為應該澄清，任何人都可以使用該按鈕來視覺上看到空白。對於某些專案（例如我正在合作的一個專案），這可能已經足夠了，因為我們已經有能力透過鍵盤輸入所需的任何空白。透過 PT 插入新空白的能力才是需要選擇啟用的功能。
感謝 John 的實用回答。我一直對為什麼這是一個破壞性（breaking）功能感到疑惑，但我記得 9.4 及更早版本會刪除某些空白，所以我明白這與新系統不相容。（顯然，我們團隊需要的空白並不是那些被刪除的，所以我之前忘記了這個行為。）
I've submitted feedback already, but I'll put my own observations here too.
I think the release documentation ought to explain why and when "opting in" is necessary. I had many of the same confusions as Kent when I experimented with the new feature.
I think it should be clarified that anyone can use the button to visually see the whitespaces. For some projects (such as one I'm working with) that may be all that's needed because we already have the ability to keyboard any whitespaces we need. It's the ability to insert new whitespaces via PT that's an opt-in feature.
Thanks to John for his helpful answer. I had been questioning why this was a breaking feature, but I do remember that 9.4 and before deleted certain whitespaces, so I see how that wouldn't be compatible with this new system. (Obviously, the whitespaces that our teams need aren't the ones that get deleted, so I had forgotten about that behavior.)
機器翻譯自 English
Paratext
11月 19, 2024
已提問
由
Kent Spielmann
(1.8k 點)
提出
