Re: Yet another anti-aliased KDE screenshot

2001-11-05 Thread Magnus von Koeller
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 31 October 2001 02:14, Eray Ozkural (exa) wrote:
> Lucida Console looks good with konsole but is it really better than
> fixed (misc).

I have anti-aliased fonts running fine now but I still have some 
problems with fixed-width fonts. I'm running konsole without 
anti-aliasing at the moment, maybe I'll switch to Lucida Console. 

But the bigger problem is that I need a fixed-width font that has a 
bold typeface available (for the Signature status lines in KMail).

Does anybody have tips for me? Any other places to get Fonts from? (I 
have installed all the packages you listed in your mail.) Oh, btw, I 
don't have the 'Fixed' font, where do I get it from and is it really 
worth it?

- -- 
- -M

- ---  Magnus von Koeller  <[EMAIL PROTECTED]> --
 Georg-Westermann-Allee 76 / 38104 Braunschweig / Germany
   Phone: +49-(0)531/2094886 Mobile: +49-(0)179/4562940

 lp1 on fire (One of the more obfuscated kernel messages)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE75pZpUIvM6e6BgFARAi+AAKDVMdPq3V/E+eZIEKdx47iNdrRkMACeLvAw
P/+lscAZ2f40jTvs7hkYZcg=
=Laod
-END PGP SIGNATURE-




Re: Yet another anti-aliased KDE screenshot

2001-10-31 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday 31 October 2001 21:12, Tomas Pospisek wrote:
> Yup I am viewing them with konqueror and they *are* blurred and I also
> had them on on my dektop and it's awful - it hurts my eyes.
>
> I do understand what AA does. But IMHO it's not a good idea, unless you
> have big characters in respect to resolution, i.e. a pixel does not matter
> any more. Otherwise you'll just get *unsharp/fading* edges - and that's
> exactly my definition of blur.

It's a matter of taste it seems :)

Cheers,

- -- 
Eray Ozkural (exa) <[EMAIL PROTECTED]>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE74GNAfAeuFodNU5wRAk40AJ9cYD45dDWXUwIydl3xk0XU6827TQCfQrev
gKH9/7nF1yglB+rbK6tAtRc=
=83LO
-END PGP SIGNATURE-




Re: Yet another anti-aliased KDE screenshot

2001-10-31 Thread Tomas Pospisek

Zitiere "Eray Ozkural (exa)" <[EMAIL PROTECTED]>:

> If you're viewing that screenshot with konqueror you will see a fairly 
> accurate representation of what I'm using but if you use an image viewer
> that resamples that further for you, it will indeed look blurry.

Yup I am viewing them with konqueror and they *are* blurred and I also
had them on on my dektop and it's awful - it hurts my eyes. 

I do understand what AA does. But IMHO it's not a good idea, unless you
have big characters in respect to resolution, i.e. a pixel does not matter any
more. Otherwise you'll just get *unsharp/fading* edges - and that's exactly my
definition of blur.
*t




Re: Yet another anti-aliased KDE screenshot

2001-10-30 Thread Daniel Robert Franklin
[ PGP not available, raw data follows ]
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Tuesday 30 October 2001 05:48, Daniel Robert Franklin wrote:
> > So, in short, if you actually want to see the font, as opposed to a bunch
> > of artifacts, you need to use anti-aliasing. Don't mistake smoothness for
> > blurring.
> 
> That was some nice explanation. Anti-aliasing is something you ought to 
> integrate in any display system, or you will have jagged edges. Thus, some of 
> the hype associated with Mac OS X's Carbon.

Definitely. OSX takes it one step further though, although I don't think it
takes it far enough. My personal preference would be the total elimination
of the "pixel" as a concept for user-interface design, rather to have
everything in terms of vectors, geometric lines etc, then use a simple
rendering engine to sample that and turn it into pixels. Then you would be
able to do arbitrary scaling, translation and rotation with the aid of
hardware acceleration (much like the user-interface on the excellent QuArK
Quake map editor). You could use scalable dimensionally-normalised eps files
or some such thing for icons, buttons etc. I don't know if the WIMP paradigm
would still work in that environment, but it certainly would be interesting
to find out, or to develop something better :)

> 
> I'd always thought anti-aliasing was simply resampling, tho'.

Well, AA comes into that too - if you have an image with 600 dpi resolution
and you want to display it on a monitor with 100 dpi resolution you need to
downsample it. But this is not as simple as taking every 6th pixel (though
that is the way it is sometimes done). You need to low-pass filter it first,
or you will see artifacts. The effect is similar to sampling an analog
signal. Accurately changing the sample rate to something which is not 1/N (N
being an integer) (e.g. from 600 to 83 dpi) requires upsampling and then
downsampling - but you still need to filter.

> Which means there is actually some blending but not blurring, most
> algorithms are careful enough not to degrade image quality. On the other
> hand, the end result varies since there are different algorithms.

Yes. The precise digital filter used can be of many different designs, but
all are imperfect (a digital filter would need to be infinitely long for it
to be perfect). You will always get some aliasing but it should be much less
than with no filter (hopefully below the threshold of perception).

Forgive me for rabbiting on, as a DSP-obsessed electrical engineer, it's a
subject which is close to my heart :)

- Daniel

-- 
**
*  Daniel Franklin - Postgraduate student in Electrical Engineering
*  University of Wollongong, NSW, Australia  *  [EMAIL PROTECTED]
**




Re: Yet another anti-aliased KDE screenshot

2001-10-30 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 30 October 2001 01:36, Dan Born wrote:
> That's rather impressive.  I have a bunch of true type fonts, and
> anti-aliasing turned on in kde, but the only font available for a fixed
> width font under the control center is the "fixed" font, and "fixed" is the
> only thing available in konsole.  This is ugly looking...  how do I fix it?
>

Yes, I like the fonts as well :) I got mad trying out all different fonts, 
because at first there weren't many fonts available and I had to go back to 
bitmapped fonts.

You ought to start installing alternative fonts then. Summon apt.
$ apt-cache search true.*type

The following packages seem worthwhile:
fttools - FreeType font utilities.
x-ttcidfont-conf - Configure TrueType and CID fonts for X.
msttcorefonts - Installer for Microsoft TrueType core fonts
ttf-commercial - Install or share some commercial truetype fonts with windows.

And of course
anti-aliasing-howto - Anti Aliasing metapackage

The qt-fonts-HOWTO.html pretty much covers which fonts you can use.

Also, I'm not sure why you can't use any bitmapped fonts when you start using 
AA. Rather weird.

Lucida Console looks good with konsole but is it really better than fixed 
(misc). 

Thanks,

- -- 
Eray Ozkural (exa) <[EMAIL PROTECTED]>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE731BofAeuFodNU5wRAuO9AKCm+TC/1UTZ5kRRC/LLm/CZhe9b7gCfVt4p
hP4XQXURn6l78TeOE2rCYAY=
=N6mx
-END PGP SIGNATURE-




Re: Yet another anti-aliased KDE screenshot

2001-10-30 Thread Eray Ozkural \(exa\)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 30 October 2001 05:48, Daniel Robert Franklin wrote:
> So, in short, if you actually want to see the font, as opposed to a bunch
> of artifacts, you need to use anti-aliasing. Don't mistake smoothness for
> blurring.

That was some nice explanation. Anti-aliasing is something you ought to 
integrate in any display system, or you will have jagged edges. Thus, some of 
the hype associated with Mac OS X's Carbon.

I'd always thought anti-aliasing was simply resampling, tho'. Which means 
there is actually some blending but not blurring, most algorithms are careful 
enough not to degrade image quality. On the other hand, the end result varies 
since there are different algorithms.

I find the KDE AA satisfactory on XFree86, tho. The fonts look good on a 
hi-res display. I think that was one advantage Windoze had, only until 
recently :)

If you're viewing that screenshot with konqueror you will see a fairly 
accurate representation of what I'm using but if you use an image viewer that 
resamples that further for you, it will indeed look blurry.

My feeling is that especially web pages look a lot more like they were 
intended to.

So, could you tell me about your font settings?

Thanks,

- -- 
Eray Ozkural (exa) <[EMAIL PROTECTED]>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7305UfAeuFodNU5wRAqD7AJ9xywomgvSmb1qi3IGyuFY6748ImgCffRca
bR8zwWcVmFx4V5tjLgT6o40=
=E+Ea
-END PGP SIGNATURE-




Re: Yet another anti-aliased KDE screenshot

2001-10-29 Thread Daniel Robert Franklin
> On Mon, 29 Oct 2001, Dan Born wrote:
> 
> > That's rather impressive.  I have a bunch of true type fonts, and
> > anti-aliasing turned on in kde, but the only font available for a fixed 
> > width
> > font under the control center is the "fixed" font, and "fixed" is the only
> > thing available in konsole.  This is ugly looking...  how do I fix it?
> 
> I don't get it: why this antialiased hype? This blurry stuff makes my eyes
> hurt. How can anybody be using this? And it's *ugly*!

AA filters don't "blur" as such. They are a low-pass filter which removes
artifacts in a sampled signal. In this case, the artifacts result from
having geometric shapes (lines, fonts etc) which are "analog" and have
frequency components higher than your display (a sampling process which
represents a geometric line as a sequence of dots) can show. Sampling a
signal which has not been band-limited (filtered to remove frequencies
higher than half the sampling rate) results in things *appearing where they
are not* - that is, the jagged edges which appear even with Type 1 or
TrueType fonts with AA turned off. The jagged edges aren't real. AA filters
do vary in quality, but basically any functional low-pass filter is better
than none.

So, in short, if you actually want to see the font, as opposed to a bunch of
artifacts, you need to use anti-aliasing. Don't mistake smoothness for
blurring.

- Daniel

-- 
**
*  Daniel Franklin - Postgraduate student in Electrical Engineering
*  University of Wollongong, NSW, Australia  *  [EMAIL PROTECTED]
**




Re: Yet another anti-aliased KDE screenshot

2001-10-29 Thread Tomas Pospisek
On Mon, 29 Oct 2001, Dan Born wrote:

> That's rather impressive.  I have a bunch of true type fonts, and
> anti-aliasing turned on in kde, but the only font available for a fixed width
> font under the control center is the "fixed" font, and "fixed" is the only
> thing available in konsole.  This is ugly looking...  how do I fix it?

I don't get it: why this antialiased hype? This blurry stuff makes my eyes
hurt. How can anybody be using this? And it's *ugly*!
*t

> > http://orion.exa.homeip.net/~exa/kde-snapshot1.png

Exactly - yuck! :-(
*t


 Tomas Pospisek
 SourcePole   -  Linux & Open Source Solutions
 http://sourcepole.ch
 Elestastrasse 18, 7310 Bad Ragaz, Switzerland
 Tel: +41 (81) 330 77 11





Re: Yet another anti-aliased KDE screenshot

2001-10-29 Thread Dan Born
That's rather impressive.  I have a bunch of true type fonts, and 
anti-aliasing turned on in kde, but the only font available for a fixed width 
font under the control center is the "fixed" font, and "fixed" is the only 
thing available in konsole.  This is ugly looking...  how do I fix it?

Thanks,
Dan

On Monday 29 October 2001 10:19 am, Eray Ozkural (exa) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Check it out at
>
> http://orion.exa.homeip.net/~exa/kde-snapshot1.png
>
> Happy K'ing,
>
> - --
> Eray Ozkural (exa) <[EMAIL PROTECTED]>
> Comp. Sci. Dept., Bilkent University, Ankara
> www: http://www.cs.bilkent.edu.tr/~erayo
> GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D
> 539C -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE73XNkfAeuFodNU5wRAieCAJ9zM74eKjFibMKOOtso6DbO6sMbuACeNdUm
> UB60KzV7ZF20bGDw6PqlgGA=
> =ya07
> -END PGP SIGNATURE-




Yet another anti-aliased KDE screenshot

2001-10-29 Thread exa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Check it out at

http://orion.exa.homeip.net/~exa/kde-snapshot1.png

Happy K'ing,

- -- 
Eray Ozkural (exa) <[EMAIL PROTECTED]>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE73XNkfAeuFodNU5wRAieCAJ9zM74eKjFibMKOOtso6DbO6sMbuACeNdUm
UB60KzV7ZF20bGDw6PqlgGA=
=ya07
-END PGP SIGNATURE-