View Single Post
Old 06-26-2024, 11:34 AM   #14
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,848
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by DiapDealer View Post
Will we be able to add something to the plugin framework to automatically force NFC on altered/added xhtml? Any plugin that has their own edit/search/diff checks might be on their own to ensure NFC on a search after edit, but it would be nice if plugin devs didn't have to worry about doing this themselves in general.
If we do this at the level of our TextResource object, we can always force NFC there on anything that sets text. That should handle the plugin changes since our plugin framework makes changes only at a file level only.

Since all of these force NFC changes are going to be invasive, I am going to create a branch.

Will we want to include these changes in a final Qt5 source release, or because they will be invasive and only impact biblical level RTL languages, and no data is lost, should we make these changes on our Qt6 only branch?

Just let me know.
KevinH is online now   Reply With Quote