我已经提交了反馈，但我也在这里写下我自己的观察。
我认为发布文档应该解释为什么以及何时需要“启用”。当我尝试新功能时，我和 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 中
十一月 19, 2024
提问于
由
Kent Spielmann
(1.8k 分)
发布
