|
Great news. You are definitely getting closer!
That said, the XHTMLHighlighter issue is going to be a bug to fix. As someone edits a file and adds and removes lines, fixes spelling etc, means that offsets in to the file will change constantly meaning that there is no easy way to pass state information to the spellchecker that will allow it to spellcheck a word on the fly outside the default language when only passed a single line of text.
So we either let the highlighter spellcheck in all languages or in only the default language to decide to wavy underline it or not. And then let the formal spellcheck mechanism work to catch these instances properly.
Or we figure out some way to pass along more information that doesn't get outdated as soon as one character has been added or deleted making all offsets meaningless. Still not sure how to do that or if it is even possible. It is a shame we can not attach a hidden language attribute somehow to every word of text!
I think the wavy line spellcheck hint set as we type should either simply highlight based off of looking up the text outside of tags with the default dictionary or alternatively all opened dictionaries (okay if it is okay in any open dictioanry), until we figure out a way to determine a word's language from just a single line snippet/fragment.
KevinH
|