On Mon, Jan 02, 2006 at 10:42:58AM +0100, Juergen Spitzmueller wrote: > Martin Vermeer wrote: > > > I think bug 2019 deserves your special attendance. > > > > Hmmm... perhaps the remark in insetcharstyle.C:draw: > > > > // I don't understand why the above .reduce and .realize aren't > > //needed, or even wanted, here. It just works. -- MV 10.04.2005 > > > > isn't quite true... could you have a look? I'm short on time right now. > > I have already tried to implement those, but that didn't change anything. I > have also tried other things to no avail, so I finally gave up. > I fear I just understand the whole fonts framework to less to fix this bug. > E.g. I just do not understand why, apparently, the color that is used to draw > the charstyle text on screen is also used in output, as is the case in the > bug in question. Aren't on-screen font colors and output font colors clearly > separated?
As further info, it appears that I have copied the getDrawFont/tmpfont etc. mechanism from insetert. There, however, the ::latex method ouputs directly by brute force, while in charinset, it goes over insettext, and thus lyxtext. Perhaps this is too powerful. That having been said, obviously *some* font attributes should appear both on-screen and in output. My understanding was that, for LaTeX use, charstyles were for things like Emph and Noun. They should not use any coloured representation on-screen, but rather "realistic" fonts. For XML, I just don't know. - Martin
pgphyQqFTB0B4.pgp
Description: PGP signature
