ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: Problem with bit maps with ConTeXt under MikTeX (works fine using LaTeX)
Date: Wed, 7 Nov 2001 09:29:47 +0100	[thread overview]
Message-ID: <20011107092947.0c79bdd4.taco@elvenkind.com> (raw)
In-Reply-To: <xuCJWjSadH67EwQZ@granby.demon.co.uk>

Hi Bruce,

dvips supports (some versions of) bmp as image format, pdftex as driver doesn't (in pdf mode, that is). If you output a DVI file, it can pass on the emtex specials essentially like latex does, but there is no support for that in Context.

If you send me the bmp file, I can probably hack it in. But bmp is a silly format and it is only partially supported by dvips anyway. So, why do you want to use it?

"Bruce Horrocks" <bh@granby.demon.co.uk> wrote:
> Hi,
> 
> I have two very simple files that include a batman image: the LaTeX one 
> works fine, the ConTeXt one doesn't (it just displays a frame saying 
> "name dummy, file sample.bmp unknown").
> 
> I'm new to ConTeXt so I'm hoping that there is something very simple 
> that I'm missing here, or that someone can at least suggest some 
> debugging options to set that might help me work out what is or isn't 
> happening.

-- 
groeten,

Taco


  reply	other threads:[~2001-11-07  8:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 23:50 Bruce Horrocks
2001-11-07  8:29 ` Taco Hoekwater [this message]
2001-11-07 11:37   ` Bruce Horrocks
2001-11-07 15:47     ` Taco Hoekwater
2001-11-07 17:04       ` Hans Hagen
2001-11-07 23:17         ` Bruce Horrocks
2001-11-08  9:27           ` Hans Hagen
2001-11-08 14:59             ` Bruce Horrocks
2001-11-08 16:08               ` Taco Hoekwater
2001-11-08  8:18         ` Taco Hoekwater
2001-11-07 17:17   ` 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=20011107092947.0c79bdd4.taco@elvenkind.com \
    --to=taco@elvenkind.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).