经文引用设置似乎未遵循字符规范化设置

Question

我一直在协助排查一个项目的问题，该项目中的经文引用设置（Paramètres de références bibliques）标记了多个冲突：设置中定义的书名与文本中使用的书名不一致。该项目设置为使用 NFD 规范化。结果发现，至少部分冲突是由于设置中混用了不同的字符类型（例如，有时使用 â [\u00e2]，有时使用 â [\u0061\u0302]）。如果此设置窗口中输入的文本（或者可能仅限于“书名”选项卡？）能够根据字符规范化设置自动进行规范化，那就太好了。

另外，顺便提一下，不知为何，其中几个书名的字符串开头还出现了零宽不换行空格 [\ufeff]。我完全不知道这是怎么发生的。

机器翻译自 English 显示原文

Answer 1

请使用 Paratext 的“提供反馈”（Give Feedback）功能来报告 Paratext 的 bug 或提出修改建议。开发人员通常会审阅这些问题，但不能保证在此站点上提出的建议会被加入支持队列。

在此期间，如果您知道 Paratext 正在对文本进行规范化，并且两个冲突的条目看起来相同，那么您应该可以选择文本选项并批准它。

关于零宽不换行空格的问题——团队是否使用了任何可能会插入这些字符的自动更正（AutoCorrect）？或者它们是否是从其他地方复制过来的？

机器翻译自 English 显示原文

Comments

Thanks for the reminder to use the "Give Feedback" feature. But what if other users have the same problem or suggestion or feedback? They aren't able to see feedback that has already been given this way and are unaware of what has been tried, or if there are any workarounds, or even if the idea has been considered and will later be implemented or discarded.

Yes, you're right about probably being able to just overwrite the settings with the actual text in the case of the mismatched character encoding. But I couldn't be sure that that was the only source of the conflicts. What if there were other "hidden" \uFEFFs, but in the text instead of the settings? I ended up checking out the unicode representation of each settings string in a different program and making sure the correct characters were used.

I can't answer the question about the source of the zero-width, non-breaking space. I doubt they are using AutoCorrect, but I can find out. My initial assumption was that it was introduced somehow by copy/pasting text, but I still don't know where they would have copied the text from other than Paratext itself. Maybe a Word document a long time ago (>10-15 years), if initial drafting was done that way?