On Fri, Oct 05, 2007 at 01:03:16PM +0200, Dov Feldstern wrote: > Abdelrazak Younes wrote: > > Jean-Marc Lasgouttes wrote: > >> Abdelrazak Younes <[EMAIL PROTECTED]> writes: > >> > >>> You are clearly underestimating the required effort and > >>> the maintainance nightmare of a font based solution. UI is important > >>> yes but having developers understand the source code is also important > >>> in an open source project. > >> > >> I do not think that the current font range implementation cause lots > >> of problems. > > I really think the way fonts are used in LyX is *really* complicated and > > caused us lots of problem in the past. > > Can you give examples of this? (Serious question --- I haven't found this to > be the case, I've actually found it to work well.)
Change tracking. Initially it was crippled and very limited, then I partly un-crippled it, and then Michael put in _a lot_ of effort to iron all the bugs out and instill some sanity. I have done this (or a small part of this) and implemented new insets, and I can tell you what I found easier ;-) (Unfortunately insets are no good for CT) > Anyhow, I'm not advocating the use of the current font span mechanism > necessarily. I think ranges should be designed from scratch, considering the > new use-cases we envision for them. I have some ideas for this. Of course, > learning lessons from the current implementation is a must. Which is another > reason why I'm interested in hearing what you don't like about it. > > But I really don't think that this would be an insurmountable task, and I > think that advantages are many. It needs at least a clean-up. Andre has some ideas on that too. - Martin
