ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: problem with printing pdf files (MKIV on Mac)
Date: Fri, 25 Mar 2011 14:31:43 +0100	[thread overview]
Message-ID: <AANLkTinhYFSbtTC2NpjMTF3-MhJ3TWOkYiNKb+D+zPBw@mail.gmail.com> (raw)

Hello,

I'm not sure if anyone will be able to help, but it doesn't hurt to ask.

I'm using ConTeXt MKIV 2011.03.11 11:45 (I will try to upgrade first).
When I try to print the document from Mac (Skim.app) to two different
printers, I get pure junk on both of them (bold and italic fonts come
out semi-ok, but regular doesn't). If I print an older document or if
I compile the same document with MKII, the document prints out fine on
the same printer. The document also prints out fine when printing from
Linux.

I'm using one network PostScript printer and one network printer that
is most probably using PCL drivers and both generate junk. I'm using
"palatino" typescript.

Mac is well known for displaying Word-generated documents as
almost-pure-junk (one gets a different font and screwed up kerning
instead of the original font that one would see in Word or in
generated PDF when opened with Adobe Acrobat; but I'm not sure if it
is Apple or Microsoft that have buggy software in that case) and for
crashing on documents using smooth shading patterns.

Does anyone have any suggestion how I could figure out what is wrong
with the document? I would like to figure out if it is LuaTeX's or
Apple's fault that it behaves so weird. (Can I send a document to
PostScript printer on specific IP from a Mac without having to use
Apple's libraries for handling PDF?)

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


             reply	other threads:[~2011-03-25 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 13:31 Mojca Miklavec [this message]
2011-03-25 13:35 ` luigi scarso
2011-03-25 15:52 ` Hagmann Jörg
2011-04-01 17:50   ` Florian Wobbe
2011-04-01 19:31     ` Mojca Miklavec
2011-04-21 21:10       ` Mojca Miklavec
2011-05-01 11:55         ` Leo Razoumov
2011-03-25 16:40 ` Florian Wobbe
2011-03-25 17:18   ` Mojca Miklavec
2011-03-25 17:28     ` Mojca Miklavec
     [not found]       ` <AANLkTimm6PjxbzKft=pwdNu6CSz2yWVEOzZH7bEDMVcO@mail.gmail.com>
2011-03-25 18:17         ` Florian Wobbe
2011-03-25 17:43     ` Florian Wobbe
2011-03-25 17:46       ` Hans Hagen
2011-03-25 18:02 ` Mojca Miklavec
2011-03-25 18:28   ` Hans Hagen
2011-03-25 21:38     ` Mojca Miklavec
2011-03-26 18:07       ` Mojca Miklavec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinhYFSbtTC2NpjMTF3-MhJ3TWOkYiNKb+D+zPBw@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).