[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: KMail: Colored quoted text feature added
From:       Don Sanders <don () sanders ! org>
Date:       2000-04-19 10:42:01
[Download RAW message or body]

On Wed, 19 Apr 2000, Stefan Taferner wrote:
> On Wed, 19 Apr 2000, Don Sanders wrote:
> > On Tue, 18 Apr 2000, Espen Sand wrote:
> > > On Fri, 21 Apr 2000, Don Sanders wrote:
>
> [...]
>
> > > > I think the options to set the font should be removed and just the
> > > > ones for changing the color left.
> > >
> > > mmm, loosing todays italic style?
> >
> > Oh, that's a good point.
> >
> > On the spur of the moment I say ditch support for italicized quoting, the
> > colorized stuff looks heaps better anyway.
>
> Snief... I like the italic font  :~|       .... never mind ;-)
>
> Btw, if somebody does not enable colorized fonts the old style should IMO
> still be available.

Well since you like the italic font capability that's reason enough to keep 
supporting it I think.

> > > I am sure some people won't like that. I
> > > think we perhaps should modify the fontselector (kdelibs) so that it is
> > > possible to disable the "Font" and "Size" column on command. I will
> > > look into that. It should not break bin. compatibility.
> >
> > But then there would still be 6 fonts that could be customized? Really
> > even the previous three seems too many to me, and I probably should have
> > just used 2, one for message headers and folders and one for the
> > readerwindow and composing text.
>
> IMO it would be sufficient to differ between normal and quoted text only.
> And here it would be IMO sufficient to be able to select font attributes
> only.
>
> Ok, only my opinion. :-)

Hmm, I think I see. I would still want to be able to select a different font 
face for messages headers/folder list and the readerwindow (say a fixed width 
font for the readerwindow and a nicer looking font elsewhere so that ASCII 
art looks right).

Unfortunately if italicised replies are to be supported and optional then I 
can't see anyway of making a nice UI too support that.

Don.

[prev in list] [next in list] [prev in thread] [next in thread]