Subject: Re: spelling images and fields (was Re: Commit: fix that spelling + images bug)
Date: Sat Mar 24 2001 - 10:09:24 CST
>>>>> "Tomas" == Tomas Frydrych <email@example.com> writes:
>> Basically, as was pointed out later in the thread, the problem is
>> that we need the current ABI_UCS_OBJECT to be treated both as a
>> whitespace and as a word. Former is needed for images, latter for
Tomas> I fail to see the need to spellcheck fields, we are not going
Tomas> to allow spelling errors into the output of our fields, or are
I didn't say that :) The problem is caused by the fact that Images
and Fields are identified as "objects" in the backend.
When spellchecking, that needs to be translated to a valid unicode of
some sort. Presently both types get translated to ABI_UCS_OBJECT which
makes the spelling code break, but the selection code work. If we
change ABI_UCS_OBJECT to a space, spelling code will work and
selection code will not.
So my suggestion was to translate these to two different unicodes.
See 'case pf_Frag::PFT_Object:' in pt_PieceTable::getBlockBuf. That
needs to check the sub-types of the PFT_Object and translate
This archive was generated by hypermail 2b25 : Sat Mar 24 2001 - 10:09:32 CST