ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Eros Albertazzi <eros@lamel.bo.cnr.it>
Cc: ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re: newbi: config
Date: Fri, 07 Jun 2002 11:09:21 +0200	[thread overview]
Message-ID: <3D007841.CADDFB64@lamel.bo.cnr.it> (raw)
In-Reply-To: <5.1.0.14.1.20020605235247.0323b5e0@server-1>

Thanks for the time spent in answering, I appreciate and admire your
efforts.... 
hope I can pay you back with successfull presentation and A0 posters (my
goals) make with context (articles are nailed down to  latex and revtex
)... 
surely I wan't start bugging about german..

1-

> >figures        : figure As can not be found
> 
> what is the suffix of As? Looks like you use a graphicformat that is not
> known to pdftex or dvips
> 
My figures are (natively) .eps , I was under the impression that texexec
was taking care of the conversion, anyhow running texutil first and
separatly is not a big deal.... 
it was just a problem of knowing what to do.

2-
>esp not easy since you start with the tricky things: graphictext uses 
>tex/mp/gs etc ... -)

>\starttext
>\startMPcode
>  graphictext "MP" scaled 8 reversefill
>   withdrawcolor .7blue withfillcolor .7white
>   dashed evenly withpen pencircle scaled 1pt ;
>\stopMPcode
>\stoptext

Metafun manual starts this way.... 
I installed pstoedit and now if I texexec  the example above it creates
a .ps file (mpgraph.1) that has what should be, but it still dosn't get
into the (final) .pdf 

Bottom line (just a suggestion, but surely you thought already): I fell
that including  a whole set of tests and compiled files (even from
simple to complex one, fonts, figures...) in context .zip distribution
may help checking and testing, somehow even saving question time, and
also, even expert users or developers, can have a quality control to
always relay on....

3-
>>pdftex         : needs map file: original-vogel-symbol.map
>no problem, just a warning

>Warning: pdfetex (file /usr/share/texmf/dvips/config/pdftex.map):
>invalid entry
>  for `rtxptmro': SlantFont/ExtendFont can be used only with embedded T1
>fonts

>these are warnings: looks like some of you rmap files define slanted 
>versions of embedded fonts, you may want force embedding (good idea anyway 
>even for times etc)

Maybe I have a wrong attitude, but I am accustum to think that a warning
is just an indication of an error (soon or later....otherwise would be
just redundant information to cut)  and here, about fonts, my ignorance
is deep,.. so my worry and luck of confidence. 
Unfourtunatly I have no much time to sistematicaly understand... like a
black box that is better not to open, to not get overloaded....

How can I force embedding??  

Regards and thanks.
-- 
Eros Albertazzi
CNR-IMM, Sez. Bologna 
Via P.Gobetti 101
I-40129 Bologna, Italy  
Tel: (+39)-051-639 9179
Fax: (+39)-051-639 9216


  reply	other threads:[~2002-06-07  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 19:02 Eros Albertazzi
2002-06-05  7:59 ` Tobias Burnus
2002-06-05 11:01   ` Eros Albertazzi
2002-06-05 21:52     ` Hans Hagen
     [not found] ` <Pine.LNX.4.44.0206050954160.22693-100000@hils.physik.fu-be rlin.de>
2002-06-05 20:05   ` Hans Hagen
2002-06-06  7:55     ` Tobias Burnus
2002-06-06  8:24       ` Taco Hoekwater
2002-06-06  8:48         ` Hans Hagen
2002-06-06  8:54         ` Tobias Burnus
2002-06-05 21:54 ` Hans Hagen
2002-06-07  9:09   ` Eros Albertazzi [this message]
     [not found] <5.1.0.14.1.20020606111535.0346cd20@server-1>
2002-06-06 10:06 ` Tobias Burnus
2002-06-06 11:40   ` Taco Hoekwater

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=3D007841.CADDFB64@lamel.bo.cnr.it \
    --to=eros@lamel.bo.cnr.it \
    --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).