[NTG-context] Solved! was Re: Confusion with font instructions

[David Rogers]

Radhelorn wrote:

>\loadmapfile [context-base] % !!!

On my machine, this was the missing piece. Thank you for your
persistence!

(makes a deep bow)  :-)

David
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Otared Kavian]

On 4 juil. 2005, at 23:33, Hans Hagen wrote:


Does:

\usetypescript [adobekb]   [ec]
\usetypescript [postscript][ec]

\loadmapfile[ec-base.map]

\usetypescript[times][\defaultencoding]
\setupbodyfont[times,12pt]

\starttext
\input knuth
\stoptext

work? If so, i'll add the map file loading to the adobekb typescripts



Hi Hans,

Thanks for your help and patience with my inexperience...

I tried your minimal file above on a new gwTeX + ConTeXt
(ver: 2005.06.27  fmt: 2005.7.4  int: english  mes: english)
installation and the result is the same, that is a PDF with bitmap  
fonts... I am using:

pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3)

The log-file of the first run says (among other things):
mktexpk: /var/tmp/texfonts/pk/modeless/adobe/times/ptmr8r.86pk:  
successfully generated.


When I add \loadallfontmapfiles to your minimal file, or (and) when I  
input the file type-akb.tex you sent in another message, the resulted  
PDF is the same (the only thing which changes is the log-file is that  
those ugly bitmap fonts are not anymore generated since they are  
cretaed in a first typesetting).


Although it is challenging to understand the problem, I can avoid  
using postscript fonts: so please don't spend much time on the issue...


Best regards: OK

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] How to "\processcommalist"?

[Hans Hagen]

Mojca Miklavec wrote:


Taco's solution already solved my problem, but I believe it would be
nice to add some \processenumeratedlist (well, some better name should
be given!) command to ConTeXt one day. That way it would be possible
to process some commands like
\filterpages[file.pdf][1,3,5]
also with
\filterpages[file.pdf][1-3,5,7-11]


ah, you stopped rading page-imp.tex too early, there's also:

\def\dowithrange#1#2% #2 takes number
  {\beforesplitstring#1\at:\to\fromrange
   \aftersplitstring #1\at:\to\torange
   \ifx\torange\empty\let\torange\fromrange\fi
   \dostepwiserecurse\fromrange\torange1{#2{\recurselevel}}}

but we can indeed make a nicer looking one

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

Otared Kavian wrote:


% times-bad.tex
\usetypescript [adobekb]   [\defaultencoding]
\usetypescript [postscript][\defaultencoding]
%\setupbodyfont [postscript] % with or without this line
\usetypescript[times][\defaultencoding]
\setupbodyfont[times,12pt]
\starttext
\input knuth
\stoptext


Does:

\usetypescript [adobekb]   [ec]
\usetypescript [postscript][ec]

\loadmapfile[ec-base.map]

\usetypescript[times][\defaultencoding]
\setupbodyfont[times,12pt]

\starttext
\input knuth
\stoptext

work? If so, i'll add the map file loading to the adobekb typescripts

Hans




-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] How to "\processcommalist"?

[Mojca Miklavec]

Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Taco Hoekwater wrote:
> >>Mojca Miklavec wrote:
> >>
> >>>I would like to define a command, which would be called in the following 
> >>>way:
> >>>\TheBossWantsTheWorkToBeDoneOn[monday,wednesday,thursday]{tidy up}
> >>>
> >>>so that it would be equivalent to:
> >>>\WeHaveToDo[monday]{tidy up}
> >>>\WeHaveToDo[wednesday]{tidy up}
> >>>\WeHaveToDo[thursday]{tidy up}
>
> Actually, there is an easier way to do this; just swap the arguments to 
> WeHaveToDo:
> 
> \def\TheBossWantsTheWorkToBeDoneOn[#1]#2%
>{\processcommalist[#1]{\WeHaveToDo{#2}}}
> 
> \def\WeHaveToDo#1#2{(#2: #1)}

Thanks for the proposal. I included it into Wiki, but in my case the
"\WeHaveToDo" was already defined and I needed it exactly in the form
that Taco suggested (to call \OnlyStep[#1]{#2} with
\OnSteps[1-3,5]{content} in t-rsteps module).

> btw, nice thread for a wiki entry

I added it to 
http://contextgarden.net/Inside_ConTeXt#Processing_lists_of_values.

> >>>Is there also a possibility to define a command like
> >>>\IHaveToDoTheTasks[1-4,7,9-11]{until tomorrow}
> >>
> >>There was not, but knowing Hans I trust that soon there will be :-).
> 
> hm, well, it does rain outside, but ...

Taco's solution already solved my problem, but I believe it would be
nice to add some \processenumeratedlist (well, some better name should
be given!) command to ConTeXt one day. That way it would be possible
to process some commands like
\filterpages[file.pdf][1,3,5]
also with
\filterpages[file.pdf][1-3,5,7-11]

Mojca
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

David Rogers wrote:


I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still
get the same effect. (I changed the font in my document from Times to
Palatino, in case I was only getting a Times that had been badly
generated on my first try with the map file still installed, but it now
creates a bad version of Palatino as well.)


how does your current tex file looks like?

Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

David Rogers wrote:


systems : print width forced to paper width
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)

...

you can try (top of document):

\preloadtypescripts

this saves some runtime


fonts   : using map file: original-youngryu-px


this is the one


[1.1{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/
original-empty
.map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/
original-base
.map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/ec-
public-lm.
map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/ec-base
.map}{/
usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-ams-
base.ma
p}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-
public-
lm.map}
Warning: pdfetex (file ec-urw-palatino.map): cannot open font map file


this one is missing on your system, it's an indocation that your setup expects 
texfont generated metrics


(you can generate the lot with " texmfstart texfont.pl type-tmf.dat --en=ec ")



{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-
youngryu-
px.map}]


thos one should do the job for your (math) palatino

 [2.2] [3.3]

Underfull \hbox (badness 2181) in paragraph at lines 56--56
 []\*palatino12ptrmsc*: Works Cit-ed 
[4.4]

systems : end file PretendPaper at line 60
 )
(see the transcript file for additional information)

 



hm, i have no idea how these pk fonts are generated; i've disabled those 
automatisms and don't want to mess up my system


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

David Rogers wrote:

Hans Hagen wrote:



Otared Kavian wrote:


used to work fine, but now it results in ConTeXt creating, the first
time, a whole bunch of things regarding fonts, and then the
resulting PDF contains some ugly jagging bitmap-looking characters
(interestingly this happens only to the text characters, not to the
math characters...).


behaviour also depends on your local cont-sys.tex; what happens if you
remove that file (or rename it)?



I don't have a cont-sys.tex anywhere, only cont-sys.ori and
cont-sys.rme (two of each). Is this relevant?


i that case things should work, so i'm puzzled; maybe some map files are not on 
your system?


what happens if you say (after loading the typescripts):

\loadallfontmapfiles

(i'll add some more map sync points)

Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Some gardening

[Mojca Miklavec]

Hans Hagen wrote:
> Mojca Miklavec wrote:
> 
> > Here's some more work for you Patrick, in case you get bored.
> > (I guess I'll soon be removed from the list as a spammer/abuser if I
> > continue writing mails such as this one :)
> > What do the others think about it?
> 
> some day others will start expecting you to help patrick gardening -)

I'm not a reliable person, I don't have as much time and I'm much
slower than "an average ConTeXt developer", but if I know how to do
something and if I have a possibility to do so (access to the
source,...), than I'm willing to contribute - step by step.

> > Take \setuplayout for example. Describing such huge collection of
> > parameters in plain text is not clear, synoptic any more. It would be
> > great if there would be a possibility to add descriptions for:
> > - the command as such (already there)
> > - every pair of braces (only one for \setuplayout), has to be visible
> > if it is optional or not
> > - every parameter inside a single brace
> > - every single option for that parameter (for example: width=middle
> > means that ...), default has to be marked
> 
> default maring is a bit tricky (since it can be \SomeCommand which will they
> blow up context visualizer; in principle, now that we've moved to xml for the
> descriptor, it's easier to add features.
> 
> can you give a more verbose example

Most options are already self explaining, but some are not. A nice
example are serried, broad, packed, ... in \setupitemize. Here it is
necessary to be able to specify what which option does.

An example:
- '\setupitemgroup' - we need place to describe a command and probably
give an example
- there are 4 groups of arguments for this command
- for each of these groups we would like to specify if the group
is optional or not, what this group does, defaults (if any) and
probably an example
- the third and fourth group have lots of possible arguments (broad,
serried, packed, columns, ... width=...,stopper=..., ...)
- we have to specify possible combinations of them (broad |
serried | n*broad | n*serried), (packed | unpacked) - broad and
serried may not occur at the same time, while broad and packed may
- we have to specify if the parameters are "swithches" (they are
present or they are not, like broad, packed) or if they have
parameters, like "headstyle=...".
- In case we have parameters like "headstyle=...", we have to specify
all the alternatives (normal | bold | slanted | boldslanted | ...),
probably note the default value as well. We also have to be able do
describe these alternatives. For example "caps - will typeset the head
of itemization in small caps". And possibility to add an example as
well.

Once again:

% perhaps some "pseudo commands" as this one could be added as well
\setupitemize[.1.][.2.][.3.] 
... equal to/see \setupitemgroup[itemize]

\setupitemgroup[.1.][.2.][.3.][.4.]

Classification (?): setups, different forms of paragraph typesetting
Description: The command is used to control the layout of itemization
environments.
Parameters:

[.1.] {\sl name} - the name of item group for which this setup holds
{\sl name}
example: itemize - equal to writing \setupitemize

(optional ?)
[.2.] {\sl number} | each - to which level of itemization the setup should apply
{\sl number} 
example: 2 - the second level of itemization
each - the setup will hold for all the levels

(optional ?)
[.3.] standard [default], (n*broad | n*serried), (packed | unpacked),
stopper, (joinedup | paragraph), (atmargin | inmargin | intext),
autointro, loose, section, columns, (one | two | three | four)
broad | n*broad - extra horizontal space after symbol
serried | n*serried - little horizontal space after symbol
example: someone would probably like to give an example of an
itemization environment with 2*serried option turned on (Wiki-like)
packed - no white space between items
unpacked - white space between items
stopper - use a character like '.' or ':' after the symbol
joinedup - no white space before and after itemization
paragraph - no white space before itemization
atmargin - symbol between margin and text
inmargin - symbol in margin
intext - symbol 
intro - no pagebreak
loose - ?
section - ?
columns - typeset in one, two, three or four columns (two is the default)
one - will make itemize in one column (where no 'columns' option
is set, this is the default)
two - will make itemize in two columns (default where 'colums'
option is set)
three - if columns option is set, it will make the itemize in three columns
four - if columns option is set, it will make the itemize in four columns
% I have a feeling that the user manual is not very consistent here

[.4.]
\dots

The schema should (I think it does already) support nested commands as
well (like most commands that accept the same parameters as
\setupframed). In this case no change in XML specification is needed,
but

Re: [NTG-context] Re: Confusion with font instructions

[Radhelorn]

David Rogers wrote:

OK, I tried this setup, and ConTeXt ran without stopping to complain,
but (as Otared described, I guess) the font actually produced is very
jaggy, both on screen and in print. My nostalgia for dot matrix





fonts   : resetting map file list
fonts   : using map file: original-base
fonts   : using map file: ec-public-lm
fonts   : using map file: ec-base
fonts   : using map file: original-ams-base
fonts   : using map file: original-public-lm
fonts   : using map file: ec-urw-palatino
fonts   : using map file: original-youngryu-px
[1.1{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/
original-empty
.map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/
original-base
.map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/ec-
public-lm.
map}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/ec-base
.map}{/
usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-ams-
base.ma
p}{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-
public-
lm.map}
Warning: pdfetex (file ec-urw-palatino.map): cannot open font map file
{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex/context/original-
youngryu-
px.map}] [2.2] [3.3]

> 

Well, here is your problem. pdftex cannot find map file for direct font 
inclusion and you get bitmaps.


I've found needed definitions in context-base.map and ec-base.map. 
ec-base is loaded by default, but dose nothing. Maybe someone explain 
this. As a quick solution try:


\loadmapfile [context-base] % !!!
\setupencoding [default=ec]
\usetypescript [adobekb] [\defaultencoding]
\usetypescript [palatino] [\defaultencoding]
\usetypescript [postscript] [\defaultencoding]
\usetypescript [lucida] [\defaultencoding]
\setupbodyfont [palatino]

\setupoutput[pdftex]

\startbuffer
Some {\bf text} to {\it test} {\sl font} {\bs switching}.
\stopbuffer

\starttext
\getbuffer

\switchtobodyfont [postscript] \getbuffer

\switchtobodyfont [lucida] \getbuffer
\stoptext

Works for me on tetex-3.0.

--
Radhelorn <[EMAIL PROTECTED]>
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Otared Kavian]

Hi Adam, Hans...

...and all of you who are trying to help us solve (and maybe  
understand) the intricacies of font management!


Here is what I did: on Saturday I  tried to answer David Rogers'  
question and so typeset an example file I had, before sending him.

Unfortunately everything went wrong for some reasons and so I gave up.
After Adam's and Hans' suggestion right this afternoon, I uninstalled  
my gwTeX, as well as ConTeXt and reinstalled everything anew.

I did not, and I do not have pdftex.map in
*/fonts/map/*/context/
and nevertheless when I tried to typeset my minimal sample file:

% times-bad.tex
\usetypescript [adobekb]   [\defaultencoding]
\usetypescript [postscript][\defaultencoding]
%\setupbodyfont [postscript] % with or without this line
\usetypescript[times][\defaultencoding]
\setupbodyfont[times,12pt]
\starttext
\input knuth
\stoptext

on my "virgin" installation, something goes wrong and the log shows  
the following:


[...snip...]
Running mktexpk --mfmode / --bdpi 72 --mag 1+14/72 --dpi 86 ptmr8r
mktexpk: Running gsftopk ptmr8r 86
gsftopk(k) version 1.19.2
Process aborted
/813
[1] [2] [3] [4] [5] [6] [7] [8] [9] [11] [12] [14] [15] [16] [17]  
[30] [31]

[32] [33] [34] [35] [36] [37] [38] [39] [40] [41Terminated

("Terminated" because I aborted the process).

I am not at all familiar with mktexpk (I even ignored its exisetnce  
up to now...), but the option

--bpdi 72
makes me think it is building a "72 dots per inch" font which we all  
hate, even after magnification

--mag 1+14/72...

I should also say that this does not infer with math fonts which  
appear correctly as one may see from the PDF attachments I sent (and  
which went finally through the list's moderator).


Thanks again for your help: OK


On 4 juil. 2005, at 17:11, Adam Lindsay wrote:


Hi Otared,

What you mention sounds like a bug propagated by Hans last month.  
Take a

look at this thread:


(Assuming you're comfortable with the CLI, I'd suggest verifying  
the bad
file by navigating to /usr/local/teTeX/share or wherever your tex  
trees

live, and looking for the file:
ls */fonts/map/*/context/pdftex.map

If a file is returned, delete it (and mktexlsr again).

If nothing is returned, then never mind, it's something else on  
your system.


One brief comment on your font selection below:

Otared Kavian said this at Mon, 4 Jul 2005 16:28:31 +0200:



\usetypescript [adobekb][\defaultencoding]
\setupbodyfont[postscript]
\usetypescript[times][\defaultencoding] %or helvetica, or palatino
\setupbodyfont[times,12pt]



The [postscript] line in the above example is unnecessary. I'd suggest
cutting it out entirely. With a properly-configured system, the three
remaining lines should give you the results you expect.

adam
--



___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[David Rogers]

Hans Hagen wrote:

> Otared Kavian wrote:
>> used to work fine, but now it results in ConTeXt creating, the first
>> time, a whole bunch of things regarding fonts, and then the
>> resulting PDF contains some ugly jagging bitmap-looking characters
>> (interestingly this happens only to the text characters, not to the
>> math characters...).
>
>behaviour also depends on your local cont-sys.tex; what happens if you
>remove that file (or rename it)?

I don't have a cont-sys.tex anywhere, only cont-sys.ori and
cont-sys.rme (two of each). Is this relevant?

David
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[David Rogers]

Hans Hagen wrote:

>David Rogers wrote:
>
>> OK, I tried this setup, and ConTeXt ran without stopping to complain,
>> but (as Otared described, I guess) the font actually produced is very
>> jaggy, both on screen and in print. My nostalgia for dot matrix
printers
>> is not as great as one might suppose.  :-)
>
>So, do you get bitmaps fonts (i didn't kno wthat there were for the ps
fonts)? 

Yes, or so it appears - a bitmap Times and a bitmap Palatino, which are
vaguely recognizable. (the Palatino has oval bowls and long serifs, for
instance.)


>what does the pdftex log say?


I don't have the log of the first run, where it created the fonts, but
this is what I get now:





___


 TeXExec 5.4.2 - ConTeXt / PRAGMA ADE 1997-2005

fixing engine variable : pdfetex
executable : pdfetex
format : cont-en
 inputfile : PretendPaper
output : pdftex
 interface : en
  current mode : none
   TeX run : 1

This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 (/usr/local/teTeX/share/texmf.local/web2c/natural.tcx)
entering extended mode
(./PretendPaper.tex

ConTeXt  ver: 2005.06.27  fmt: 2005.7.2  int: english  mes: english

language: language en is active

system  : cont-new loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex
color   : palette rollover is available
)
system  : cont-old loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system  : cont-fil loaded
(/usr/local/teTeX/share/texmf.local/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
system  : cont-sys.rme loaded
(/usr/local/teTeX/share/texmf.local/tex/context/user/cont-sys.rme
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex))
bodyfont: 12pt rm is loaded
language: patterns en->ec:ec->1->2:2 uk->ec:ec->2->2:2
de->texnansi:tex
nansi->3->2:2 de->ec:ec->4->2:2 fr->texnansi:texnansi->5->2:2
fr->ec:ec->6->2:2
 es->ec:ec->7->2:2 pt->texnansi:texnansi->8->2:2 pt->ec:ec->9->2:2
it->texnansi
:texnansi->10->2:2 it->ec:ec->11->2:2 nl->texnansi:texnansi->12->2:2
nl->ec:ec-
>13->2:2 cz->il2:il2->14->2:2 cz->ec:ec->15->2:2 sk->il2:il2->16->2:2
sk->ec:ec
->17->2:2 pl->pl0:pl0->18->2:2 pl->ec:ec->19->2:2 loaded
specials: tex,postscript,rokicki loaded
system  : PretendPaper.top loaded
(./PretendPaper.top
specials: loading definition file tpd
(/usr/local/teTeX/share/texmf.local/tex/context/base/spec-tpd.tex
specials: loading definition file fdf
(/usr/local/teTeX/share/texmf.local/tex/context/base/spec-fdf.tex)
specials: fdf loaded
)
specials: fdf,tpd loaded
) (./env_mla.tex
systems : print width forced to paper width
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-akb.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-exa.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-syn.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-enc.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-dis.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-siz.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-map.tex)
(/usr/local/teTeX/share/texmf.local/tex/context/base/type-spe.te

Re: [NTG-context] Re: Confusion with font instructions

[Adam Lindsay]

David Rogers said this at Mon, 4 Jul 2005 09:02:56 -0700:

>I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still
>get the same effect. (I changed the font in my document from Times to
>Palatino, in case I was only getting a Times that had been badly
>generated on my first try with the map file still installed, but it now
>creates a bad version of Palatino as well.)

Sounds frustrating all around. I might be able to do more with a log
file (send off-list, please).
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
 Lancaster University, InfoLab21+44(0)1524/510.514
 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[David Rogers]

Adam Lindsay wrote:

>Hi Otared,
>
>What you mention sounds like a bug propagated by Hans last month. Take
a
>look at this thread:
>20050610.172825.65f0c37f.html#20050610.172825.65f0c37f>
>
>(Assuming you're comfortable with the CLI, I'd suggest verifying the
bad
>file by navigating to /usr/local/teTeX/share or wherever your tex trees
>live, and looking for the file:
>ls */fonts/map/*/context/pdftex.map
>
>If a file is returned, delete it (and mktexlsr again).


I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still
get the same effect. (I changed the font in my document from Times to
Palatino, in case I was only getting a Times that had been badly
generated on my first try with the map file still installed, but it now
creates a bad version of Palatino as well.)

David
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Some gardening

[Hans Hagen]

Mojca Miklavec wrote:


Here's some more work for you Patrick, in case you get bored.
(I guess I'll soon be removed from the list as a spammer/abuser if I
continue writing mails such as this one :)
What do the others think about it?


some day others will start expecting you to help patrick gardening -)


Take \setuplayout for example. Describing such huge collection of
parameters in plain text is not clear, synoptic any more. It would be
great if there would be a possibility to add descriptions for:
- the command as such (already there)
- every pair of braces (only one for \setuplayout), has to be visible
if it is optional or not
- every parameter inside a single brace
- every single option for that parameter (for example: width=middle
means that ...), default has to be marked


default maring is a bit tricky (since it can be \SomeCommand which will they 
blow up context visualizer; in principle, now that we've moved to xml for the 
descriptor, it's easier to add features.


can you give a more verbose example


The ability to add commands is already there I think (I have never
tried it out yet). What about adding commands for (official and
third-party) modules? It should be separated from the main page, but
still offering the same functionality.


in principle each module should have an associated spec file

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

David Rogers wrote:


OK, I tried this setup, and ConTeXt ran without stopping to complain,
but (as Otared described, I guess) the font actually produced is very
jaggy, both on screen and in print. My nostalgia for dot matrix printers
is not as great as one might suppose.  :-)


So, do you get bitmaps fonts (i didn't kno wthat there were for the ps fonts)? 
what does the pdftex log say?


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

Adam Lindsay wrote:


Sadly, that page relies on type-pre, which is deprecated!
(Yes, the situation changes again.)


hm, i can enable that one again, but will not give guarantees (some fonts have 
changed, for instance antikwa and we now have proper encoding support for latin 
modern so all those other things should go otherwise they will interfere;


which ones from type-pre are used?


So, the situation should now be:

% Times, Helvetica, Courier:
\usetypescript [adobekb]   [\defaultencoding] % default=ec
\usetypescript [postscript][\defaultencoding]
\setupbodyfont [postscript]

% or, for Times, Helvetica, and Latin Modern TT:
\usetypescript [adobekb][\defaultencoding]
\usetypescript [times]  [\defaultencoding]
\setupbodyfont [times]

% or, for Palatino & Latin Modern TT:
\usetypescript [adobekb]  [\defaultencoding] 
\usetypescript [palatino] [\defaultencoding]

\setupbodyfont [palatino]

The situation is "dynamic" because, to Hans's increasing frustration,
the font files that get distributed change with just about every release
of tetex (which gwTeX is mostly based on) or TeXLive.


indeed; the only way out is to have an additional zip with font files (something 
that we discussed last ntg meeting); for instance,


- say that you want verbatim
- and use ec encoding
- and use kb names
- and don't want --- ligatures and such

 impossible (with the current tex, less impossible with the next release of 
pdftex) .. so, you switch to texnansi


- for which there are kb names
- but metrics are never shipped
- so you need to generate them with texfont
- and then *not* load the kn typescripts

etc etc. it's just impossible to keep up with feature requests (fonts, 
languages, backends) and at the same time be compatible with the way latex users 
are accustomed to it cq. latex changes dealing with fonts cq. distributions keep 
changing


(so guess why i only use tex font generated metrics)


Anyway, I hope this helps in the short term!


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Hans Hagen]

Otared Kavian wrote:


It is right that handling fonts is extremely disappointing and instable...
For instance, what used to work does not work anymore properly with the 
new version of ConTeXt I installed two weeks ago...


much of this has nothing to do with context but with

- switching from cm to lm (context has done this switch, latex will do that 
later)
- changes in the tds structure (hard to cope with automatically)
- changes in map files etc (there will be some more but in the end that mess 
will be cleaned up so that we don;t have differences in backends any more)



For instance:

\usetypescript [adobekb][\defaultencoding]


this maps kb names and should work if they are present (only when your encoding 
is ec!)



\setupbodyfont[postscript]
\usetypescript[times][\defaultencoding] %or helvetica, or palatino
\setupbodyfont[times,12pt]


nothing has changed here

used to work fine, but now it results in ConTeXt creating, the first 
time, a whole bunch of things regarding fonts, and then the resulting 
PDF contains some ugly jagging bitmap-looking characters (interestingly 
this happens only to the text characters, not to the math characters...).


behaviour also depends on your local cont-sys.tex; what happens if you remove 
that file (or rename it)?


it seems that you have a map file problem


Adding \usetypescript[postscript] does not help neither.


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] How to "\processcommalist"?

[Hans Hagen]

Mojca Miklavec wrote:

Taco Hoekwater wrote:


Mojca Miklavec wrote:


I would like to define a command, which would be called in the following way:
   \TheBossWantsTheWorkToBeDoneOn[monday,wednesday,thursday]{tidy up}

so that it would be equivalent to:
   \WeHaveToDo[monday]{tidy up}
   \WeHaveToDo[wednesday]{tidy up}
   \WeHaveToDo[thursday]{tidy up}

I played a bit with different variants of \processcommalist, but I
can't figure out how to use it in this particular case.


The trick is to store the tidy up inside the processing command,
like so:

  \def\WeHaveToDo[#1]#2{\message{(#1: #2)}}

  \def\TheBossWantsTheWorkToBeDoneOn[#1]#2%
{\begingroup
 \def\processitem##1{\WeHaveToDo[##1]{#2}}%
 \processcommalist[#1]\processitem
 \endgroup }

  \TheBossWantsTheWorkToBeDoneOn[monday,wednesday,thursday]{tidy up}



Great, thanks Taco! It works. It seems easier than I thought, but I
could have spent hours looking for the proper solution alone.


Actually, there is an easier way to do this; just swap the arguments to 
WeHaveToDo:

\def\TheBossWantsTheWorkToBeDoneOn[#1]#2%
  {\processcommalist[#1]{\WeHaveToDo{#2}}}

\def\WeHaveToDo#1#2{(#2: #1)}

\starttext

\TheBossWantsTheWorkToBeDoneOn[monday,wednesday,thursday]{tidy up}

\stoptext

btw, nice thread for a wiki entry


I hope this will land in the t-rsteps module (\OnSteps[1,2,3,6]{...}).



Is there also a possibility to define a command like
   \IHaveToDoTheTasks[1-4,7,9-11]{until tomorrow}


There was not, but knowing Hans I trust that soon there will be :-).


hm, well, it does rain outside, but ...

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Adam Lindsay]

Hi Otared,

What you mention sounds like a bug propagated by Hans last month. Take a
look at this thread:


(Assuming you're comfortable with the CLI, I'd suggest verifying the bad
file by navigating to /usr/local/teTeX/share or wherever your tex trees
live, and looking for the file:
ls */fonts/map/*/context/pdftex.map

If a file is returned, delete it (and mktexlsr again).

If nothing is returned, then never mind, it's something else on your system.

One brief comment on your font selection below:

Otared Kavian said this at Mon, 4 Jul 2005 16:28:31 +0200:

>\usetypescript [adobekb][\defaultencoding]
>\setupbodyfont[postscript]
>\usetypescript[times][\defaultencoding] %or helvetica, or palatino
>\setupbodyfont[times,12pt]

The [postscript] line in the above example is unnecessary. I'd suggest
cutting it out entirely. With a properly-configured system, the three
remaining lines should give you the results you expect.

adam
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
 Lancaster University, InfoLab21+44(0)1524/510.514
 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[David Rogers]

Adam Lindsay wrote:

>Patrick Gundlach said this at Mon, 4 Jul 2005 09:54:06 +0200:
>
>>Hello David,
>>
>>> I am new to ConTeXt, as my question is about to reveal.
>>
>>This questions can also come from more experienced users :)
>>
>>> Which set of instructions should I follow, in order to allow use of
>>> Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution,
latest
>>> ConTeXt installed? 
>>
>>OK, do you have LaTeX working? Then you can use the standard
>>postscript fonts for ConTeXt as well. Have a look at the (yet
>>unfinished page)
>>
>>http://contextgarden.net/Psnfss
>
>Sadly, that page relies on type-pre, which is deprecated!
>(Yes, the situation changes again.)
>
>So, the situation should now be:
>
>% Times, Helvetica, Courier:
>\usetypescript [adobekb]   [\defaultencoding] % default=ec
>\usetypescript [postscript][\defaultencoding]
>\setupbodyfont [postscript]


OK, I tried this setup, and ConTeXt ran without stopping to complain,
but (as Otared described, I guess) the font actually produced is very
jaggy, both on screen and in print. My nostalgia for dot matrix printers
is not as great as one might suppose.  :-)

And I thought I was just asking for a shortcut answer to a dumb
question!

Thanks for the help
David
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Otared Kavian]

On 4 juil. 2005, at 9:54, Patrick Gundlach wrote:
Hello David,



I am new to ConTeXt, as my question is about to reveal.



This questions can also come from more experienced users :)



Which set of instructions should I follow, in order to allow use of
Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution, latest
ConTeXt installed?



OK, do you have LaTeX working? Then you can use the standard
postscript fonts for ConTeXt as well. Have a look at the (yet
unfinished page)

http://contextgarden.net/Psnfss

Patrick
--



Hi Patrick, David and Adam,

It is right that handling fonts is extremely disappointing and instable...
For instance, what used to work does not work anymore properly with 
the new version of ConTeXt I installed two weeks ago...

For instance:

\usetypescript [adobekb][\defaultencoding]
\setupbodyfont[postscript]
\usetypescript[times][\defaultencoding] %or helvetica, or palatino
\setupbodyfont[times,12pt]

used to work fine, but now it results in ConTeXt creating, the first 
time, a whole bunch of things regarding fonts, and then the resulting 
PDF contains some ugly jagging bitmap-looking characters 
(interestingly this happens only to the text characters, not to the 
math characters...).


Adding \usetypescript[postscript] does not help neither.

I wanted to answer David's question on Saturday but when I tried my 
examples, I was dispappointed and did not answer.


Best regards: OK
PS: When I added two samples of the PDF files to my previous post, it 
was blocked due to the fact that the message was over 40 Kb. So I am 
posting again without the attachments.


___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Re: Confusion with font instructions

[Adam Lindsay]

Patrick Gundlach said this at Mon, 4 Jul 2005 09:54:06 +0200:

>Hello David,
>
>> I am new to ConTeXt, as my question is about to reveal.
>
>This questions can also come from more experienced users :)
>
>> Which set of instructions should I follow, in order to allow use of
>> Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution, latest
>> ConTeXt installed? 
>
>OK, do you have LaTeX working? Then you can use the standard
>postscript fonts for ConTeXt as well. Have a look at the (yet
>unfinished page)
>
>http://contextgarden.net/Psnfss

Sadly, that page relies on type-pre, which is deprecated!
(Yes, the situation changes again.)

So, the situation should now be:

% Times, Helvetica, Courier:
\usetypescript [adobekb]   [\defaultencoding] % default=ec
\usetypescript [postscript][\defaultencoding]
\setupbodyfont [postscript]

% or, for Times, Helvetica, and Latin Modern TT:
\usetypescript [adobekb][\defaultencoding]
\usetypescript [times]  [\defaultencoding]
\setupbodyfont [times]

% or, for Palatino & Latin Modern TT:
\usetypescript [adobekb]  [\defaultencoding] 
\usetypescript [palatino] [\defaultencoding]
\setupbodyfont [palatino]

The situation is "dynamic" because, to Hans's increasing frustration,
the font files that get distributed change with just about every release
of tetex (which gwTeX is mostly based on) or TeXLive.

Anyway, I hope this helps in the short term!
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
 Lancaster University, InfoLab21+44(0)1524/510.514
 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Re: Confusion with font instructions

[Patrick Gundlach]

Hello David,

> I am new to ConTeXt, as my question is about to reveal.

This questions can also come from more experienced users :)

> Which set of instructions should I follow, in order to allow use of
> Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution, latest
> ConTeXt installed? 

OK, do you have LaTeX working? Then you can use the standard
postscript fonts for ConTeXt as well. Have a look at the (yet
unfinished page)

http://contextgarden.net/Psnfss

Patrick
-- 
ConTeXt wiki and more: http://contextgarden.net
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Re: Some gardening

[Patrick Gundlach]

Hi Mojca,

> Here's some more work for you Patrick, in case you get bored.

Sorry, but I wasn't able to find the last word in my dictionary. 




I have printed out your suggestions(*), the all make much sense to me, so
my plan is to implement them all. I'll report back when I have
something to show.

Some of these suggestions (for example to add wiki like markup to
texshow-web was already on my long-term todo list).

Thank you very much for your suggestions.

Patrick


(*) I never print out mails, but this was just too important

-- 
ConTeXt wiki and more: http://contextgarden.net
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context