From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: stand-alone ConTeXt
Date: Sun, 14 Jun 2009 19:26:02 +0200 [thread overview]
Message-ID: <fe8d59da0906141026s3d0ac8e6va110ef886a7aed9f@mail.gmail.com> (raw)
In-Reply-To: <6faad9f00906140841v78f47192h3d8a3f8c84f69d04@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]
On Sun, Jun 14, 2009 at 5:41 PM, Mojca Miklavec <
mojca.miklavec.lists@gmail.com> wrote:
> On Sun, Jun 14, 2009 at 17:22, luigi scarso wrote:
> >
> >>> For me, pstopdf is a number one candidate to luafication :)
> >>> (Had problems with it recently)
> >>
> >> yes, will be done (we use it here in workflows with massive amounts of
> >> conversions, auto downsampling, etc)
> >
> > If I understand well, pstopdf uses ghostscript .
> > "luafication" will use ghostscript again ?
>
>
> Unless Hans rewrites the whole GS interpreter ... yes.
>
>
> The problem is that current pstopdf doesn't work reliably for me (no
> way to do EPSCrop, sometimes wrong paper orientation, the graphic
> missing completely ...),
hmm strange -- do you have an example ?
By defautl gs choose rotation studying dominant text orientation on current
page; cfr Setting page orientation
in Ps2pdf.htm
There is an option in pstopdf -dAutoRotatePages=/None .
so I usually stick to ps2pdf (perl or shell,
> I think)
A wrapper shell around gs
There is also pstill
http://www.wizards.de/~frank/pstill.html
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 2076 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-06-14 17:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1288.1244895890.3589.ntg-context@ntg.nl>
2009-06-13 15:19 ` Vyatcheslav Yatskovsky
2009-06-14 10:28 ` Hans Hagen
2009-06-14 15:22 ` luigi scarso
2009-06-14 15:41 ` Mojca Miklavec
2009-06-14 17:12 ` Hans Hagen
2009-06-14 17:26 ` luigi scarso [this message]
2009-06-14 18:00 ` Mojca Miklavec
2009-06-14 18:50 ` luigi scarso
2009-06-14 17:10 ` Hans Hagen
2009-06-14 17:39 ` luigi scarso
2009-06-14 18:21 ` Hans Hagen
2009-06-11 10:10 Carlos Breton Besnier
2009-06-11 10:39 ` Hans Hagen
2009-06-11 15:05 ` Kevin D. Robbins
2009-06-11 18:12 ` Mohamed Bana
2009-06-11 19:06 ` Kevin D. Robbins
2009-06-11 19:36 ` Khaled Hosny
2009-06-11 20:42 ` Idris Samawi Hamid ادريس سماوي حامد
2009-06-11 22:10 ` Kevin D. Robbins
2009-06-12 7:44 ` Hans Hagen
2009-06-13 2:29 ` Yue Wang
2009-06-13 11:30 ` Henning Hraban Ramm
2009-06-13 11:41 ` Hans Hagen
2009-06-15 4:03 ` Yue Wang
2009-06-15 7:19 ` Hans Hagen
2009-06-15 12:26 ` Yue Wang
2009-06-15 14:33 ` Joel C. Salomon
2009-06-15 14:40 ` Yue Wang
2009-06-15 15:05 ` Hans Hagen
2009-06-15 15:17 ` Wolfgang Schuster
2009-06-20 13:17 ` Mojca Miklavec
2009-06-21 11:09 ` Hans Hagen
2009-06-21 18:49 ` Mojca Miklavec
2009-06-21 20:55 ` Hans Hagen
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=fe8d59da0906141026s3d0ac8e6va110ef886a7aed9f@mail.gmail.com \
--to=luigi.scarso@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).