From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Minimals and XeTeX
Date: Mon, 11 Jan 2010 13:26:38 +0100 [thread overview]
Message-ID: <6faad9f01001110426k223d7e37h6ec4644dd884a32f@mail.gmail.com> (raw)
In-Reply-To: <fd3eb9bf1001110301w6af3e3a3wdc928f7f629294e7@mail.gmail.com>
2010/1/11 Vedran Miletić:
> Hi,
>
> I'm a new user of ConTeXt and minimals distribution and first I would
> like to say to thank everyone involved in it. Like most LaTeX users, I
> found something that was very hard to do in LaTeX to be fairly trivial
> in ConTeXt, and gave it a shot.
>
> Nevertheless, there is an issue with missing files that might be
> relevant and worth noting here. When compiling with --xtx, texexec (or
> xdvipdfmx) warns about missing dvipdfmx.cfg (that should, according to
> TeX Live structure, be in texmf/dvipdfmx/dvipdfmx.cfg), and once you
> manually add that, about missing cid-x.map
> (texmf/fonts/map/dvipdfmx/cid-x.map). After adding both files, there
> are no more complains.
>
> Can those files be added to minimals distribution?
I can add two empty files if that will make people happier. It's a
useless warning that makes no difference for ConTeXt.
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
___________________________________________________________________________________
prev parent reply other threads:[~2010-01-11 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 11:01 Vedran Miletić
2010-01-11 12:26 ` Mojca Miklavec [this message]
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=6faad9f01001110426k223d7e37h6ec4644dd884a32f@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).