The Bitstream VERA font, the first truely crossplatform solution
Robert Brenstein
rjb at rz.uni-potsdam.de
Mon Feb 9 08:24:39 EST 2004
>At 8:33 PM +0100 2/7/04, Dom wrote:
>>About visually impaired persons: it's a pain for me to read those tiny
>>chars in the Help ;->
>>This ought to be a choice!
>
>Sorry. It was difficult to design this in, because the way styles in
>fields are architected currently, any change to font, size, style,
>or color sets all of them. For example, if you have a field of
>11-point Verdana, and you boldface one word, the word's font and
>size are set to Verdana 11 - so if you change the field to New York
>18, for example, the boldfaced word will still be Verdana 11.
>
>The documentation has a lot of style changes, so what this means in
>practice is that to change the doc font or size, you need to go
>through all the style runs on each of the thousands of cards in the
>documentation, and change the font and size for each of them. This
>can be done in a script but it takes too long to be practical as a
>preference setting. (But if the architecture changes to allow this
>to be fast, I'm sure it will be done.)
>--
>jeanne a. e. devoto ~ jaed at jaedworks.com
>http://www.jaedworks.com
This will be possible only when text attributes will become truly
inherited. I mean individually inherited. As it is now, they are
object/chunk attributes are now stored in sets (bundles of font name,
size, and style). This should be an enhancement request but I don't
recall seeing it in bugzilla.
Robert Brenstein
More information about the use-livecode
mailing list