View Single Post
Old 07-23-2020, 04:48 PM   #22
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,816
Karma: 6000000
Join Date: Nov 2009
Device: many
Actually, I liked pieces of it but felt it actually was a bit too invasive. I felt a simpler solution might be possible. The main problem is adding a language attribute to any tag in CV would force the recreation of the entire text position language map and make it hard for the syntax highlighter to do its job on a line by line basis.

None of this is a problem for spellchecking static code via the spellcheck dialog when proper lang attributes have already been added.

I like BetterRed's idea of only doing on the fly spell checking in the primary language and reserve multi-language spellchecking to the spellcheck dialog as it would be much less invasive and the language of the text of any tag can be determined by the parsed dom by checking parents up to the html tag for the most recent lang attribute.

Last edited by KevinH; 07-23-2020 at 04:50 PM.
KevinH is offline   Reply With Quote