「經文參考設定」似乎未遵循字元正規化設定

Question

我最近協助排查一個專案的問題，該專案的「經文參考設定」（Paramètres de références bibliques）標示出設定中定義的書名與文本中使用的書名之間存在多處衝突。該專案設定為使用 NFD 正規化。結果發現，至少部分衝突是由於設定中混用了不同的字元類型（例如，有時使用 â [\u00e2]，有時使用 â [\u0061\u0302]）。如果這個設定視窗（或者可能僅限於「書名」分頁？）中輸入的文字能根據字元正規化設定自動進行正規化，那就太好了。

另外，這是一個完全離題的附註，但不知為何，其中幾個書名的字串開頭還出現了零寬不換行空格 [\ufeff]。我完全不知道這是怎麼發生的。

機器翻譯自 English 顯示原文

Answer 1

請使用 Paratext 的「提供回饋」（Give Feedback）功能來報告錯誤或提出修改建議。開發人員通常會檢視這些問題，但不能保證在此網站上提出的建議會被加入支援佇列。

與此同時，如果您知道 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?