PureBasic Forums - English

600% is not enough to see it.

Trond wrote:600% is not enough to see it.

It is here... weird, perhaps a certain font?

I can see the jaggies clearly at 1200% but I wouldn't count that as a problem...

@Kale

maybe you could consider writing a book that is similar to

Waite Group's Visual Basic Source Code Library (The Waite Group)
by Brian Shea (Paperback - Dec 17, 1998)

or

Visual Basic 2005 Cookbook: Solutions for VB 2005 Programmers (Cookbooks (O'Reilly))
by Tim Patrick and John Craig (Paperback - Sep 21, 2006)

I'm sure there's a market for it.

Is there a reason for viewing the file at more than 600%?

I cannot read the page at that resolution.

Yup. I might just have that... urge... to look at a full stop in high detail

dna wrote:Is there a reason for viewing the file at more than 600%?

I cannot read the page at that resolution.

Then you can more easily see why it looks so bad at 100%.

But it does not look bad at 100%

The only artifacts I get appear at 600% resolution.

I was using Foxit though

I see it unsharp at 100%.. at 400% it seems like artifacts.

at 800% it's getting clearer and at 1600% I can see that it is because the Font is pixelized, not vectorized.
seems like a 72pt was used and resampled smaller.

I guess it was an old Font-File, no vectorised TrueType.

That's Very Odd we get two, or maybe three different views of the same document.

We use the LaTeX language to generate the pdfs.

The underlying TeX typesetting system and its fonts are aimed at very good quality when printing, not necessarily when viewing on the PC.
(We use the default font, "Computer Modern")

The CHM or HTML versions of the docs are better suited for online viewing imho.

It may be LaTex that's making the problem