From: "Simon Hepburn" <[EMAIL PROTECTED]>
> Derek Broughton wrote:
>
> > I asked a question, based on the message that started this thread. Nobody
> > has attempted to answer it, but rather have veered off on this whole issue
> > of whether bytecode interpretation is turned on in any particular
From: "Alan Chandler" <[EMAIL PROTECTED]>
>
> There are two separate things.
>
> 1) Anti Aliasing
> 2) Hinting
>
> The byte code interpreter thing does the Hinting. But without hinting Anti
> Aliasing looks horrible.
>
> So, like you say, the answer is yes and no.
Thank you. That's what I t
Derek Broughton wrote:
> I asked a question, based on the message that started this thread. Nobody
> has attempted to answer it, but rather have veered off on this whole issue
> of whether bytecode interpretation is turned on in any particular version.
Hrmm... I thought I had. I obviously did no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 28 October 2002 4:53 pm, Derek Broughton wrote:
>
> Duh! I knew that. So why not stop beating a dead horse and answer the
> question. DOES anti-aliasing _rely_ on bytecode interpretation. And yes,
> I've read your reference, and I still c
Derek Broughton wrote:
> From: "Nick Sanders" <[EMAIL PROTECTED]>
>
> > but in any case as mentioned in my previous email IT DOES NOT
> > AFFECT YOU because you are running 2.1.2-7 from sarge and the
> > bytecode interpreter was turned off in 2.1.2-8 in sid and was
> > then turned back on in 2.1.2-
From: "Nick Sanders" <[EMAIL PROTECTED]>
>
> but in any case as mentioned in my previous email IT DOES NOT AFFECT YOU
> because you are running 2.1.2-7 from sarge and the bytecode interpreter was
> turned off in 2.1.2-8 in sid and was then turned back on in 2.1.2-10 so when
btw, of course it affe
Nick wrote:
> >
> > > i.e 2.1.2-8 turned off bytecode interpreter and 2.1.2-10 turned it back
> > > on so you can stop worrying now
> >
> > Can't _anybody_ read?
> >
> > I'm not running freetype from sid. I have no intention of running it from
> > sid. When it gets to sarge, I'll give it a shot -
>
> > i.e 2.1.2-8 turned off bytecode interpreter and 2.1.2-10 turned it back
> > on so you can stop worrying now
>
> Can't _anybody_ read?
>
> I'm not running freetype from sid. I have no intention of running it from
> sid. When it gets to sarge, I'll give it a shot - IF I can do so without
> st
From: "Nick Sanders" <[EMAIL PROTECTED]>
>
> >
> > And the relevance of this is what? You're right that that's the latest
> > mention of the bytecode interpreter - at least to my installed version -
> > but it doesn's even hint at the answer to my question.
>
> freetype (2.1.2-10) unstable; urgen
>
> And the relevance of this is what? You're right that that's the latest
> mention of the bytecode interpreter - at least to my installed version -
> but it doesn's even hint at the answer to my question.
freetype (2.1.2-10) unstable; urgency=low
* Turning back on the bytecode interpreter.
From: "Michael Schuerig" <[EMAIL PROTECTED]>
> On Monday 28 October 2002 14:15, Derek Broughton wrote:
> > So I ask again, "Is Debian really delivering a FreeType package
> > incapable of supporting anti-aliasing?" - which is what the original
> > poster seemed to believe was the situation. I don
On Monday 28 October 2002 14:15, Derek Broughton wrote:
> So I ask again, "Is Debian really delivering a FreeType package
> incapable of supporting anti-aliasing?" - which is what the original
> poster seemed to believe was the situation. I don't plan to infringe
> any patents and, if the bytecode
From: "Simon Hepburn" <[EMAIL PROTECTED]>
> Derek Broughton wrote:
>
> > Are you seriously telling me that FreeType (which I _only_ have for support
> > of my TTF fonts), as delivered by Debian, doesn't support anti-aliasing,
> > and I have to recompile it?
>
> It's not a question of whether it su
On Sun, Oct 27, 2002 at 01:39:10PM +0100, Miguel wrote:
> > freetype (2.1.2-8) unstable; urgency=low
> >
> > * CVS updates as of 2002-10-07
> > * Applied David Chester's ft-slight patch. Thanks to Roger So
> > for the suggestion. (Closes: Bug#163900)
> > * Turned off the bytecode interprete
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 27 Oct 2002 4:53 am, Rob Weir wrote:
> Are you sure?
> /usr/share/doc/libfreetype6/changelog.Debian.gz:
> freetype (2.1.2-8) unstable; urgency=low
Current version is 2.1.2-10 and it has been turned back on.
Tom
- --
Email: [EMAIL PROTECTE
> freetype (2.1.2-8) unstable; urgency=low
>
> * CVS updates as of 2002-10-07
> * Applied David Chester's ft-slight patch. Thanks to Roger So
> for the suggestion. (Closes: Bug#163900)
> * Turned off the bytecode interpreter.
>
> -- Anthony Fok <[EMAIL PROTECTED]> Fri, 11 Oct 2002 02:00:1
On Fri, Oct 25, 2002 at 09:23:56PM +0100, Simon Hepburn wrote:
> Derek Broughton wrote:
>
> > Are you seriously telling me that FreeType (which I _only_ have for support
> > of my TTF fonts), as delivered by Debian, doesn't support anti-aliasing,
> > and I have to recompile it?
>
> It's not a que
Derek Broughton wrote:
> Are you seriously telling me that FreeType (which I _only_ have for support
> of my TTF fonts), as delivered by Debian, doesn't support anti-aliasing,
> and I have to recompile it?
It's not a question of whether it supports AA or not, its whether it uses the
bytecode int
From: "Bob Tilley" <[EMAIL PROTECTED]>
> The cause and the correction to my recent browser rendering woes is on
> display today at The Register.
>
> The http://www.theregister.co.uk/content/4/27788.html";>article
> discusses how to "purtify" font display throughout the KDE environment. The
> tech
The cause and the correction to my recent browser rendering woes is on
display today at The Register.
The http://www.theregister.co.uk/content/4/27788.html";>article
discusses how to "purtify" font display throughout the KDE environment. The
techniques are probably applicable to other window mana
20 matches
Mail list logo
