ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Petr Ferdus <pferdus@vertigo.fme.vutbr.cz>
Cc: ntg-context@ntg.nl
Subject: pdf font resource support
Date: Sun, 25 Nov 2001 12:26:39 +0100 (CET)	[thread overview]
Message-ID: <Pine.BSF.3.96.1011125122544.11290A-100000@vertigo.fme.vutbr.cz> (raw)
In-Reply-To: <3.0.6.32.20010531111252.01ac13a0@server-1>

Hi,
capabilities of newly released Context are quite remarkable. (definitely 
speedwise and xml procesing related). Thanks.
At moment I would have one question. Context seems to  loose ability to
include 
pdf font resource in generated files. The problem might be in macro
\doincludepdffontresource where it never goes inside (at least in my
tests), 
and pdf file always ends up without resource table. What could be done
with it?

Thanks.

Peter

simple test file:
% output=pdftex interface=en
\useencoding[pfr]
\setupbodyfont[csr] 
\setupcolors[state=start]

\starttext
  \bf \v r \v R
  test \`z \'z \v z \bf test \sl test \bs quite funny \`z \v r \page
  test \`Z \'Z \v Z \bf test \sl test \bs quite funny \`Z \v R \page
  \showcharacters \page
  \showaccents
\stoptext


  parent reply	other threads:[~2001-11-25 11:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3.0.6.32.20010525212835.0127d390@server-1>
     [not found] ` <Pine.BSF.3.96.1010529101027.14223A-100000@vertigo.fme.vutb r.cz>
2001-05-29  9:45   ` typeseting XML Hans Hagen
2001-05-29 14:05     ` Petr Ferdus
2001-05-30 15:01     ` Petr Ferdus
     [not found]     ` <Pine.BSF.3.96.1010529153914.15436A-101000@vertigo.fme.vutb r.cz>
2001-05-30 15:09       ` Hans Hagen
2001-05-30 20:12         ` Petr Ferdus
2001-06-14 23:07         ` Petr Ferdus
     [not found]         ` <Pine.BSF.3.96.1010615004606.12697C-100000@vertigo.fme.vutb r.cz>
2001-06-15  8:09           ` Hans Hagen
2001-06-27  7:46             ` typeseting XML - mixed buffers Petr Ferdus
     [not found]             ` <Pine.BSF.3.96.1010627092248.18364B-100000@vertigo.fme.vutb r.cz>
2001-06-27  8:28               ` Hans Hagen
2001-06-27  9:25                 ` Petr Ferdus
     [not found]                 ` <Pine.BSF.3.96.1010627110044.18364C-100000@vertigo.fme.vutb r.cz>
2001-06-27 10:26                   ` Hans Hagen
2001-06-27 10:43                 ` Petr Ferdus
     [not found]                 ` <Pine.BSF.3.96.1010627122029.18364D-100000@vertigo.fme.vutb r.cz>
2001-06-27 21:16                   ` Hans Hagen
2001-06-28  7:41                     ` Petr Ferdus
     [not found]                     ` <Pine.BSF.3.96.1010628091736.23569C-100000@vertigo.fme.vutb r.cz>
2001-06-28  9:31                       ` Hans Hagen
     [not found]     ` <Pine.BSF.3.96.1010530154343.20742A-101000@vertigo.fme.vutb r.cz>
2001-05-31  9:12       ` typeseting XML Hans Hagen
2001-06-01  8:03         ` Petr Ferdus
     [not found]         ` <Pine.BSF.3.96.1010601083337.29526A-100000@vertigo.fme.vutb r.cz>
2001-06-04  9:55           ` Hans Hagen
2001-06-06  4:47             ` Petr Ferdus
2001-06-06  8:01               ` very beta font switching/mapping Petr Ferdus
2001-11-25 11:26         ` Petr Ferdus [this message]
     [not found]         ` <Pine.BSF.3.96.1011125122544.11290A-100000@vertigo.fme.vutb r.cz>
2001-11-26 11:27           ` pdf font resource support 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=Pine.BSF.3.96.1011125122544.11290A-100000@vertigo.fme.vutbr.cz \
    --to=pferdus@vertigo.fme.vutbr.cz \
    --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).