I didn't find a way out to use 2 fonts in the glossary expansion: I would require to first write the transliterated word (i.e. With diacritical marks) and then, between brackets, the same in Devanagari script (sanskrit) as could be done with Nisus in older days... sniff. I regret to be able to only choose one font for the expansion. Will this limitation be lifted in next release ?
0
using 2 fonts in glossary expansions
Started by Ganesh, Jan 20 2006 05:24 AM
1 reply to this topic
#2
-
- Admin
-
- 2,986 posts
Administrator
- Gender:Male
- Location:Toronto, Canada
- Interests:This Place!
Posted 20 January 2006 - 11:07 PM
Ganesh, on Jan 20 2006, 05:24 AM, said:
I didn't find a way out to use 2 fonts in the glossary expansion: I would require to first write the transliterated word (i.e. With diacritical marks) and then, between brackets, the same in Devanagari script (sanskrit) as could be done with Nisus in older days... sniff. I regret to be able to only choose one font for the expansion. Will this limitation be lifted in next release ?
There is no way to do this with current versions of Spell Catcher X, sorry to say.
I am considering this for the future, most certainly NOT the next release, though.
There are products that have this ability, however none of the implementations I've seen are what I'd consider acceptable ones (my opinion, at least for use in Spell Catcher X). All involve using the clipboard - the "rich text" expansion is copied and pasted, which almost inevitably means there will be side-effects involving the clipboard in certain situations.
What I'm looking into are ways to actually insert rich text into a document, more in-line with how Spell Catcher works now. If this can be done (not certain yet), it's a far better solution than the above, where you need to save off the contents of the entire clipboard on every expansion, then restore it afterwards. This is potentially very expensive - what if the clipboard contains 5 megabytes of data (not at all unreasonable)? This doesn't "get along" well with the various multiple-clipboard enhancement utilities out there, either.
In other words, yes, this is something I'd like to add (a relatively major feature enhancement), but I'm only interested in doing it the "right way." There are a couple of hopeful techniques, but these will only work with more modern OS X applications that support more advanced text input APIs and (most likely) have a good accessibility implementation.
