[NTG-context] Is this a bug?
Hello, all-- I asked this question a few days ago, in the context of solving a problem I was having. That problem is solved, thanks to Wolfgang, but I haven't seen any response to my mention of what I think is a bug. The issue I was having was that, when I tried to process an old project with mkIV, there was no output because the project structure was obsolete: it contained a project and several products, but no components. But even though there was no output, there was also no error message, and in fact the log file falsely reported that a PDF file had been saved. That can't be right, can it? Seems like a bug. My ConTeXt version is: current version: 2015.05.18 12:26 -- Matt Gushee ___ 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 ___
Re: [NTG-context] No output for no apparent reason
Hi, Wolfgang-- On Mon, Aug 3, 2015 at 1:18 AM, Wolfgang Schuster schuster.wolfg...@gmail.com wrote: Is it possible that your main file of your document is a project? When this is the case change this file to a product and all subfiles into components. Yes, that was the problem. And I can see there are a few other things I need to change, but the project was nowhere near finished anyway, and at least I now have output. By the way, shouldn't there be an error or at least a warning when ConTeXt can't produce output? At the very least, the log file should not report that a PDF file was saved when it was not. This seems like a bug. Thanks for your quick reply! -- Matt Gushee ___ 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 ___
[NTG-context] No output for no apparent reason
Hello, ConTeXt people-- I am coming back to ConTeXt after a long absence (for about the 3rd or 4th time - maybe if I just stuck with it I wouldn't keep having these problems, eh?). I have a new installation of the standalone ConTeXt package on an Arch Linux system. I obtained the 'first-setup.sh' script according to instructions, then ran: ./first-setup.sh --modules=all --engine=luatex --context=current I also have TeXlive, including ConTeXt, installed as a regular Arch package; however, I don't intend to use it. In any case, I have sourced /opt/context/tex/setuptex, so I have: $ which context /opt/context/tex/texmf-linux-64/bin/context $ context --version mtx-context | ConTeXt Process Management 0.61 mtx-context | mtx-context | main context file: /opt/context/tex/texmf-context/tex/context/base/context.mkiv mtx-context | current version: 2015.05.18 12:26 I have tried the hello world example described on the wiki, and the output from that is exactly as expected, but I am having trouble with a couple of projects that I created in 2006. Each project is moderately complex, including an environment file and several product files. Each project produced output in the past. But now I run 'context file', and there are no obvious errors (except for fonts not found, but in that case the default font should be used instead, correct?), yet no PDF is produced. Furthermore, the log files say that PDF files were generated, e.g.: mkiv lua stats result saved in file: hobo.pdf, compresslevel 3, objectcompresslevel 3 And yes, I've checked the modification times on the log files, and they are up to date. Of course I am not giving very much detail, but I have no idea what might be relevant. Any ideas about how to troubleshoot this? Thanks, Matt Gushee ___ 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 ___
Re: [NTG-context] Em dash using Hoefler
I don't think it's the font. I have been trying to produce an em dash using the latest stable release from contextgarden.net, with a couple of different fonts--Alegreya, which is a free OpenType font, Latin Modern, and one other that I don't remember. In my case, regardless of the font, \emdash works but --- does not. -- Matt Gushee On Tue, Aug 20, 2013 at 5:51 AM, Marco Patzer li...@homerow.info wrote: On 2013–08–20 Martin Moncrieffe wrote: Finder reports that my version of Hoefler is 8.0d2e1. This means we already have three different Hoefler versions in this thread. […] shows the the em dash is present in the font. When I use a version with em dash, your example works here. Someone using a Mac is probably in a better position to help out. You can also try to use simplefonts, it works for me: \usemodule [simplefonts] \setmainfont [Hoefler-Text] \starttext A test of Hoefler at 10 pt. The emdash--- does not work... \stoptext Marco ___ 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 ___ ___ 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 ___
Re: [NTG-context] Minor date formatting issue
Hi, Wolfgang--
On Fri, Aug 9, 2013 at 6:58 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
I am experimenting with the \currentdate command. I am finding that
\currentdate [weekday,{,~},month,day+,{,~},year]
which should work according to the Wiki, produces:
Thursday, Augustday+, 2013
It’s recommended to use “day:ord” with \currentdate but you also use “day:+”.
\starttext
\currentdate[day,space,day:ord,space,day:+]
\stoptext
Ah, yes, thank you!
Perhaps someone should update the wiki? I suppose I could get an
account and fix it myself ... if people don't mind someone as inexpert
as me messing around in there ...
--
Matt
___
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
___
[NTG-context] Minor date formatting issue
Hello, all--
I am experimenting with the \currentdate command. I am finding that
\currentdate [weekday,{,~},month,day+,{,~},year]
which should work according to the Wiki, produces:
Thursday, Augustday+, 2013
This command:
\currentdate [weekday,{,~},month,day,{,~},year]
works as expected. I also tried
\date [][weekday,{,~},month,day+,{,~},year]
but that produced the same result as above.
I have a recent stable release of the standalone ConTeXt package from
the Garden. Is there a new way to format a date with an ordinal
indicator (-st, -nd, -rd, -th), or is that just not working at the
moment? Please advise.
--
Matt Gushee
___
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
___
[NTG-context] Passing macro parameters to lua
Hello, good people--
I've encountered what appears to be a bug in either the TeX-Lua
interface or the documentation thereof (I have the latest stable
ConTeXt standalone from contextgarden.net).
I'm trying to create a macro that will insert different text depending
on whether one of the arguments is empty or not. My initial test
implementation (following the wiki section entitled Passing arguments
and buffers: ConTeXt commands that hook into Lua) looked like this:
\startluacode
userdata = userdata or {}
function userdata.empty_or_not(str)
if str == or str == nil then
context({\\sc Empty})
else
context(str)
end
end
\stopluacode
\def\emptyOrNot#1{%
\ctxlua{userdata.empty_or_not(#1)}%
}
\starttext
\emptyOrNot{Amazing Text!}
\emptyOrNot{}
\stoptext
This did not work. I determined that even when I passed a non-empty
string, the Lua interpreter detected it as nil. It turns out the fix
was simple--I had to quote the string, as follows.
\def\emptyOrNot#1{%
\ctxlua{userdata.empty_or_not(#1)}%
}
It took me a while to figure that out, though, since the wiki example
does not show quotes.
--
Matt Gushee
___
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
___
[NTG-context] Path problems w/ MkIV on Arch Linux
Hello, Folks--
Once again I'm returning to ConTeXt after a long absence [maybe if I
just kept using it I wouldn't have these problems?]. I'm trying to get
started with MkIV; I don't feel a strong need to have the very latest
code, so unless there are serious bugs, I want to use the version
included with TexLive. At any rate, that's what I currently have and
am trying to use. But I am running into issues with files not being
found, e.g.:
$ context --make
mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
Yes, I ran mtxrun --generate first, though I am a bit confused as to
whether I need to run that *and* luatools --generate, or just one or
the other. Anyway, mtxrun --generate appears to work:
$ mtxrun --generate
resolvers | resolving | found configuration file
'/usr/share/texmf-dist/web2c/texmfcnf.lua'
system | lua | compiling
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/trees/5044cbe2799fe389b078f26ff6b9ee8e.lua'
into
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/trees/5044cbe2799fe389b078f26ff6b9ee8e.luc'
system | lua | dumping
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/trees/5044cbe2799fe389b078f26ff6b9ee8e.lua'
into
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/trees/5044cbe2799fe389b078f26ff6b9ee8e.luc'
stripped
resolvers | caching | 'files' compiled to
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/trees/5044cbe2799fe389b078f26ff6b9ee8e.luc'
This shows that mtxrun finds the correct configuration file--as far as
I know, /usr/share/texmf-dist/web2c/texmfcnf.lua is the only instance
of texmfcnf.lua on my system. And then it uses the value I have set in
texmfcnf.lua to cache its output:
TEXMFCACHE = /var/cache/texmf,
-- not used by context at all
TEXMFSYSVAR = $TEXMFCACHE,
TEXMFVAR= $TEXMFCACHE,
So that's good. Yet the 'context' and 'luatools' commands can't find
the lua scripts. Well, I hypothesized that $LUAINPUTS might be wrong,
so I tried this:
LUAINPUTS=/usr/share/texmf-dist/scripts/context/lua luatools --generate
And it seems to work. However:
LUAINPUTS=/usr/share/texmf-dist/scripts/context/lua context --make
resolvers | resolving | using given filetype 'tex'
resolvers | resolving | remembering file 'cont-en.mkiv'
resolvers | resolving | using given filetype 'tex'
resolvers | resolving | remembering file 'cont-en.tex'
resolvers | formats | no tex source file with name 'cont-en' (mkiv or tex)
resolvers | formats | using format path
'/var/cache/texmf/luatex-cache/context/0399a8df3aef8d154781d0a9c2b8e28d/formats/luatex'
resolvers | resolving | using given filetype 'tex'
resolvers | resolving | remembering file 'cont-nl.mkiv'
resolvers | resolving | using given filetype 'tex'
resolvers | resolving | remembering file 'cont-nl.tex'
resolvers | formats | no tex source file with name 'cont-nl' (mkiv or tex)
system | total runtime: 0.239
So now the lua scripts are found, but the context macro files are not.
At this point let me describe how my system is set up. As I said
above, I'm attempting to use the ConTeXt that comes with TexLive. I've
just upgraded TeXLive to the 2013 release, but that does not seem to
affect these issues. Anyway, the executables are in /usr/bin;
/usr/bin/mtxrun is the complete Lua script (i.e. not a symlink or any
sort of stub), which appears to be identical to
$TEXMF/scripts/context/stubs/unix/mtxrun. /usr/bin/luatools and
/usr/bin/context also appear to be copies of their counterparts in the
aforementioned stubs directory.
The TeXLive packages for Arch provide the following trees:
/usr/share/texmf
/usr/share/texmf-dist
/usr/share/texmf-config
Almost everything important is now in /usr/share/texmf-dist, and there
are no ConTeXt-related files in /usr/share/texmf. Accordingly,
texmf.cnf contains the following definitions:
TEXMFDIST = $TEXMFROOT/texmf-dist
TEXMFMAIN = $TEXMFDIST
TEXMFLOCAL = /usr/local/share/texmf;/usr/share/texmf
So I have updated texmfcnf.lua to contain the following:
TEXMFDIST = selfautoparent:texmf-dist,
TEXMFMAIN = $TEXMFDIST,
TEXMFLOCAL = /usr{/local}/share/texmf,
I'm not sure if that syntax is correct, but the definition of
TEXMFLOCAL does not appear to affect the issues I'm concerned with
here. Also, I should mention that my main reason for defining
TEXMFLOCAL as I did (as well as TEXMFCACHE = /var/cache/texmf), is
that I feel rather strongly (in keeping with what I understand to be
'Linux best practices') that files which are not managed by the Linux
package manager should not be under /usr. But if by chance that is
causing problems I don't absolutely have to do it that way.
Anyway, somehow important files are not being found. Any suggestions?
--
Matt Gushee
Re: [NTG-context] Path problems w/ MkIV on Arch Linux
Thanks, Hans ...
On Wed, Jul 31, 2013 at 3:32 PM, Hans Hagen pra...@wxs.nl wrote:
On 7/31/2013 10:51 PM, Matt Gushee wrote:
code, so unless there are serious bugs, I want to use the version
included with TexLive. At any rate, that's what I currently have and
am trying to use. But I am running into issues with files not being
found, e.g.:
as a start you could try the distribution from the garden; at least it's a
good way to figure out if there is something fishy with your system
Okay, I've installed that, and it works fine ... though I had a small
glitch along the way that gives me an idea about what the problem may
be with the TeXLive version. More about that below.
in the reported 'tree' files in the cache you can check if files like
context.mkiv are present
They weren't.
mtxrun --variables
mtxrun --expansions
Actually, I had already tried that, but I didn't fully understand the
output. Here's an example:
resolvers | lists | LUAINPUTS
resolvers | lists | env: unset
resolvers | lists | var: .;$TEXINPUTS;$TEXMF/scripts/context/lua//
resolvers | lists | exp:
.;.;{home:texmf,!!selfautoparent:texmf-project,!!selfautoparent:texmf-fonts,!!/usr{/local}/share/texmf,!!selfautoparent:texmf-context,!!selfautoparent:texmf-linux,!!selfautoparent:texmf-dist,!!selfautoparent:texmf-dist}/tex/{context,plain/base,generic}//;{home:texmf,!!selfautoparent:texmf-project,!!selfautoparent:texmf-fonts,!!/usr{/local}/share/texmf,!!selfautoparent:texmf-context,!!selfautoparent:texmf-linux,!!selfautoparent:texmf-dist,!!selfautoparent:texmf-dist}/scripts/context/lua//
resolvers | lists | res:
.;.;{/home/matt/texmf,!!./texmf-project,!!./texmf-fonts,!!/usr{/local}/share/texmf,!!./texmf-context,!!./texmf-linux,!!./texmf-dist,!!./texmf-dist}/tex/{context,plain/base,generic}//;{/home/matt/texmf,!!./texmf-project,!!./texmf-fonts,!!/usr{/local}/share/texmf,!!./texmf-context,!!./texmf-linux,!!./texmf-dist,!!./texmf-dist}/scripts/context/lua/
Are the 'selfautoparent' references supposed to be resolved to
specific paths? If so, it certainly appears something was wrong here.
so no file database is present or the database has not all files
It was the latter, I suspect due to incorrect path settings in the config file.
does arch-linux use stock texlive or do they adapt it
There are a few, seemingly minor tweaks. There are three patches, all
for luatex:
poppler-0.20.patch
fix-fontforge-encoding.patch
luatex-r4449-radical-rule-thickness.patch
However, these all seem to deal with small graphics/fonts issues and
have no apparent relationship to finding files. There is also a
customized texmf.cnf, but NOT a customized texmfcnf.lua. I think
that's significant.
I said above that I ran into a minor problem when I installed the
Contextgarden package. What happened was that I saw two ../bin
directories: /opt/context/bin and /opt/context/tex/texmf-linux/bin .
At first I thought /opt/context/bin was meant to be used, so I added
both directories to my PATH [/opt/context/bin was first]. But that
produced errors. Then I removed /opt/context/bin from PATH, and
everything was fine. So I think I see what's going on: since many of
the path settings in texmfcnf.lua use 'selfauto*' variables, and
correct resolution of those depends on where the executables are
located. So I suspect that the default config file that comes with
ConTeXt in TeXLive assumes that the executables are ... I'm not sure
where, but somewhere other than /usr/bin . I could probably fix that,
but it would take me a while to figure out the correct values.
Anyway, at this point I'm seriously thinking about just forgetting
TeXLive and using the standalone ConTeXt package. I doubt I'll be
using any other TeX packages in the near future, and I'd rather spend
time creating documents than tinkering with config files. Is there
anything in TeXLive that's particularly useful with ConTeXt, that is
not included in the ConTeXt package?
Anyway, many thanks for your prompt attention!
--
Matt Gushee
___
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
___
Re: [NTG-context] Usage of \setupfootnotedefinition?
Thanks to Albrecht and Steffen for their quick and informative replies. I guess \setupfootnotedefinition isn't what I am looking for. It seems to mainly be a way to customize the footnote *numbering*, right? What I wanted to try was to put footnotes in the margin. My text has a lot of footnotes, and a few of them are absurdly long (no, I didn't write the book); the conventional layout results at several points in truly abominable pages, so I thought I'd try something unconventional. Guess I'll have to do it some other way. -- Matt Gushee : Bantam - lightweight file manager : matt.gushee.net/software/bantam/ : : RASCL's A Simple Configuration Language : matt.gushee.net/rascl/ : ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Splitting footnotes
Hello, folks-- I am trying to typeset a book that has many footnotes; most of them are of moderate length, but a few are terribly long[*]. I am trying to use \setupfootnotes[split=*], but so far haven't got good results. You see, there is only one footnote that really needs to be split across pages (it takes up about two-thirds of a page); if I use [split=tolerant], many footnotes get split, which I would like to avoid, but if I say [split=strict], the longest one does not get split. I have also tried numeric values, but that doesn't seem to do anything. So my questions/comments are: 1. What does a numeric value represent, and what is the range of useful values? I first tried fairly small values like 1, 10, 25, thinking it was the number of lines, then thought it might be a tolerance value (as in \badness), and tried 1000 and 1. None of these numbers had any effect. 2. It seems there is a very large gap between 'strict' and 'tolerant'. Might it not be a good idea to have four steps, e.g. 'verystrict', 'strict', 'tolerant', and 'verytolerant'; or 'verystrict', 'strict', 'medium', and 'tolerant'? [*] Of course, the ideal solution would be to edit or delete the overly long ones. However, I'm working with a well-known 19th century text. Thus, it's in the public domain and I can legally do whatever I want with it, but I don't feel it would be appropriate to make substantive alterations to the content. -- Matt Gushee : Bantam - lightweight file manager : matt.gushee.net/software/bantam/ : : RASCL's A Simple Configuration Language : matt.gushee.net/rascl/ : ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Usage of \setupfootnotedefinition?
Hi, all-- Can anyone point me to a realistic example(s) of \setupfootnotedefinition? I think it may help to solve a problem I am working with, but don't understand precisely how to use it. -- Matt Gushee ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] \setupheader: leftstyle rightstyle
Hi, all-- I would like to use different styles for left and right headers in a book: I would like to set the left side (which shows the book title) in small caps, and the right side (chapter title) in italics. \setupheader[style=\sc] works fine. So does \setupheader[style=\it] But \setupheader[leftstyle=\sc,rightstyle=\it] Doesn't work. Both headers appear in the (medium-weight roman) body font. Any idea why this is the case? -- Matt Gushee ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] \setupheader: leftstyle rightstyle
Patrick Gundlach wrote:
'rightstyle' in the source. And \setupheader is AFAIU for the section
title.
AFAIU? Sorry, I'm not familiar with that acronym.
\setupheadertexts[{\sc This is my book!}][{\it \getmarking[section]}]
Ah, yes, that does the trick! Thank you.
Mojca Miklavec wrote:
\setupheadertexts
[\sc Book Title][]
[][{\it (\getmarking[chapter][current])}]
Okay, that seems to work, too. But why use the [current] argument? Are
there conditions where
\getmarking[chapter]
doesn't return the current chapter title?
However, there seems to be a little bug. This works perfectly well for
section (\getmarking[section]), but for chapter the chapter labels
seem to be erased after the first appearance.
Hmm, that doesn't happen for me. I'm using the 2007-01-23 release of
ConTeXt. Which version are you using?
--
Matt Gushee
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
[NTG-context] \setupheader: leftstyle rightstyle not working
[sorry if this appears twice--I accidentally sent it from the wrong e-mail account] Hi, all-- I would like to use different styles for left and right headers in a book: I would like to set the left side (which shows the book title) in small caps, and the right side (chapter title) in italics. \setupheader[style=\sc] works fine. So does \setupheader[style=\it] But \setupheader[leftstyle=\sc,rightstyle=\it] Doesn't work. Both headers appear in the (medium-weight roman) body font. Any idea why this is the case? -- Matt Gushee ___ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
[NTG-context] Customizing chapter titles
Hi, All--
I am attempting to typeset a book in ConTeXt, but I am having some
problems with chapter titles:
1) The font I am using for titles is completely different from the body
font. I am trying to experiment with a couple of different variants,
though. The following works fine:
\setuphead [chapter]
[
style={\switchtobodyfont[CopperplateGothicCondensed, 15pt]},
]
However, I may want to set the chapter titles in bold. So I've
tried:
style={\switchtobodyfont[CopperplateGothicCondensed-Bold, 15pt]},
but this doesn't work: the titles default to the body text font (a
Garamond clone). It's not that the bold font is unavailable, because
if I use the first version and add:
numberstyle=\bf
it has the expected/desired result: the chapter number appears in
Copperplate Gothic Condensed Bold. I have also looked through the
pertinent typescript and map files, and there are no misspellings;
the required font files (tfm, vf, and pfb) are all present.
Furthermore, I've checked the log file, and the right typescript and
map files are always loaded; also, there is nothing in missfont.log.
But somehow, when I specify the Bold font, it just doesn't get
loaded.
2) In order to get the titles just right, I may need to use customized
commands (used via the [text|number]command parameters of
\setuphead). But when I attempt to use such commands, TeX usually
fails with the error:
! Argument of [my command name] has an extra }.
This is not true as far as I can see--at least all the curly braces
match in the source file. Here is one example of a command that
causes the error:
\def\ChapterNumber#1 {
\switchtobodyfont [CopperplateGothicCondensed-Bold, 15pt]
#1
}
I've tried various commands; this one works:
\def\SmallSpace#1{\setupinterlinespace[line=1.6ex]#1}
but everything else I have tried fails. Is it something to do with
white space in the definition?
I am using the 2007-01-23 release of ConTeXt on 2 different machines.
Both run Linux, but on one I have teTeX 3.0, while on the other one I am
using the minimal TeX provided by Pragma ADE. I have run the same files
on both machines, and I don't think the TeX distribution makes any
difference.
Thanks in advance for any suggestions.
--
Matt Gushee
___
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] texmfstart?
Matt Gushee wrote: Probably you just need either to put the Ruby script directory ($TEXMF/scripts/context/ruby) on your PATH, or create links from the scripts you want to use to a directory in your current PATH. Maybe just link texmfstart--it seems to be a front end for all the Ruby scripts. P.S.: I just came across this manual: http://www.pragma-ade.com/general/manuals/mtexmfstart.pdf -- Matt Gushee The Reluctant Geek: http://matt.gushee.net/rg/ ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texmfstart?
Hans van der Meer wrote: Since installing the last ConTeXt update I am aware of the message from texexec: warning : use 'texmfstart texexec' instead Good, I call: texmfstart texexec --version instead of texexec --version Result: -bash: texmfstart: command not found I've been away from ConTeXt for a while, so I don't have full knowledge of the recent changes. But it seems that many of the original Perl scripts are being replaced by Ruby scripts (of which texmfstart is one), which are in a different directory. Is my system suddenly incomplete? I am using Mac OS X 10.4.6, the most recent development I would think. What happened and how can I get to the level of system support ConTeXt seems to expect of me? Probably you just need either to put the Ruby script directory ($TEXMF/scripts/context/ruby) on your PATH, or create links from the scripts you want to use to a directory in your current PATH. Maybe just link texmfstart--it seems to be a front end for all the Ruby scripts. Oh, and of course you have to have Ruby itself. I don't know where you would get an OS X package, but the Ruby language Web site is: http://www.ruby-lang.org/ -- Matt Gushee The Reluctant Geek: http://matt.gushee.net/rg/ ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Unconventional page number placement
Hello, all-- Sorry about the repost, but I asked about this several days ago and didn't get any response. If there is a documented way to do what I want, feel free to just give me a hint as to where it is documented; or if there is no way to do it without deep hackery, please just let me know that. Thanks! %% I am creating a layout for electronic books in which all the body text is in a single, fairly narrow column, with minimal space at the top and bottom of each page. I would like to place page numbers in the left margin, aligned with the bottom of the text, and the running heads (if any) also in the left margin, aligned with the top of the text. Is there a way to do this in ConTeXt? I can see that the standard page numbering and header commands don't support this kind of placement. I can come very close to the desired effect with the following: * Place the page numbers in the margin area of the footer, e.g.: \setuppagenumbering [...,location=inleft] * Place the header text in the margin area of the header, e.g.: \setupheadertext [margin] [section] [] * Use negative dimensions to cause the header and footer to overlap the text area, e.g.: \setuplayout [...,headerdistance=-0.35in,footerdistance=-0.5in] As I said, this comes very close to the desired effect, but it seems impossible to correctly align the header text and page numbers with the main text. Also, the header texts are mostly too long to fit on a single line in the margin, and I have not found a way to induce line wrapping. Your suggestions are greatly appreciated. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Page numbers in margin?
Hello, all-- I am creating a layout for electronic books in which all the body text is in a single, fairly narrow column, with minimal space at the top and bottom of each page. I would like to place page numbers in the left margin, aligned with the bottom of the text, and the running heads (if any) also in the left margin, aligned with the top of the text. Is there a way to do this in ConTeXt? I can see that the standard page numbering and header commands don't support this kind of placement. I can come very close to the desired effect with the following: * Place the page numbers in the margin area of the footer, e.g.: \setuppagenumbering [...,location=inleft] * Place the header text in the margin area of the header, e.g.: \setupheadertext [margin] [section] [] * Use negative dimensions to cause the header and footer to overlap the text area, e.g.: \setuplayout [...,headerdistance=-0.35in,footerdistance=-0.5in] As I said, this comes very close to the desired effect, but it seems impossible to align the header text and page numbers with the main text. Also, the header texts are mostly too long to fit on a single line in the margin, and I have not found a way to induce line wrapping. Your suggestions are greatly appreciated. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Fourier Expert Fonts
Randall Skelton wrote: Can someone explain how I go about adding the Adobe Utopia Expert fonts so that ConTeXt is aware of them? I have the postscript fonts from Adobe but cannot figure out what to do with them. Is there a document that I've missed somewhere? Poking around in type-enc.tex suggests that much of the hard work has already been done... This doesn't directly address your problem, but it might help a bit: http://havenrock.com/textips/bookfonts.html Apologies if this is trivial... it has been a while since I tinkered with fonts in TeX. IMHO nothing to do with fonts in TeX is trivial. Sometimes there are simple solutions, but I've never found solutions that are both simple and clearly documented. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Fourier Expert Fonts
Randall Skelton wrote: Thanks Matt... after reading a few more sites, I was led back to trying: Well, I probably can't help much (I haven't been working w/ fonts much recently, either), but here are a couple of thoughts. texfont --fontroot=$HOME/Library/texmf --vendor=adobe --collection=utopia --makepath --install This creates a tree in ~/Library/texmf/fonts/*/adobe/utopia where * is either afm, tfm, type1, or vf. I also get $HOME/Library/texmf/map/pdftex/context/texnansi-adobe-utopia.map which I've added to my pdftex.cfg and run texhash. That's only useful if you are planning to use TeXnANSI encoding. You might try adding --encoding=ec to your texfont invocation. Then I think you will get an ec-adobe-utopia.map file. Unfortunately, I still get CM fonts for the caps and there are no old-style figures? You mean small caps, I presume? My first guess would be that they're not properly referenced in the typescript. As for old-style figures, are you sure Utopia is supposed to have them? If so, do you know which font contains them? Comparing type-enc.tex and the suggestions on Bill McClain's site, the typescript definitions are somewhat different and I'm wondering if this isn't the source of my problems: \definefontsynonym [Fourier-Regular] [futr8t] [encoding=ec] vs. \definefontsynonym [Fourier-Regular] [texnansi-futr8t ] [encoding=texnansi] My experience leads me to think that in general you should reference fonts with some encoding prefix. That prefixed name has to correspond to a name defined in a map file in your TeX tree; e.g., if your texnansi-adobe-utopia.map file defines a name something like 'texnansi-raw-futr8t.map', then in your typescript, 'texnansi-futr8t' should work. Then again, I suspect 'futr8t' might be the wrong name to use. Do you have TFM files named 'futr8t.tfm', and so on? Or are they named 'utopia'? In the latter case, I think the map file should say, e.g., 'texnansi-raw-utopia', and you should say 'texnansi-utopia' in the typescript. If you want to use EC encoding, then I guess you would change every instance of 'texnansi' above to 'ec'. By the way, is there a particular reason you don't want to use TeXnANSI? -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Dimensions of a picture
Taco Hoekwater wrote: It seems probable that your JPEG file is broken, there is no size limit for JPEG images, but there are some checks to make sure that the file is 'valid ', and your image failed one of those checks. There are several command-line utilities for checking image files. The ImageMagick suite has a program called 'identify,' which will give you lots of information (probably more than you want!): identify -verbose image_file If you're running Linux, ImageMagick is available for just about any distribution, and may already be installed on your system. I think you can get a version for Windows, too; not sure about MacOS. If the file is broken, 'identify' will tell you so. Otherwise, post the output of the command to the list, and hopefully someone will be able to tell you if there's something unusual about your file that makes it incompatible with pdefetex. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
SOLVED -- Re: [NTG-context] pdfetex can't find map files
Matt Gushee wrote: Warning: pdfetex (file original-public-vnr.map): \ cannot open font map file The files exist and are world-readable, so the above must mean that pdfetex just can't find them. Thomas Esser has explained that pdfetex uses $TEXPSHEADERS (or maybe $PSHEADERS) as the search path for map files. So I added $TEXMF/fonts/map// to TEXPSHEADERS in my texmf.cnf, and now everything works fine. It seems a little strange that pdf(e)tex doesn't use TEXFONTMAPS. Maybe it will in the future? Perhaps Hans can comment on that. Thanks to all. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: pdfetex can't find map files
Patrick Gundlach wrote: make sure you got your cont-sys. updated. If by that you mean simply installing the latest version, I'm pretty sure I did--since I ripped out all the context/ directories under /usr/share/texmf (which is where I had always installed ConTeXt before) and installed the latest package under /usr/local/share/texmf. But I'll double-check it. Do you happen to know the date of the correct version? Also have a look at http://news.gmane.org/gmane.comp.tex.tetex.general (the tetex mailing list archive). I had font problems, too, although different ones. Do you mean your exchange with Thomas Esser near the top of the list? Anyway, thanks. -- Matt Gushee Englewood, CO, USA ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] pdfetex can't find map files
Aargh!
Font problems again: after not using ConTeXt for a while, I installed
the December 6 package today, generated formats, copied cont-sys.rme and
texexec.rme, and so on. Since I recently upgraded my teTeX installation,
I also edited pdftex.cfg, adding a bunch of
map +foo
lines--though I guess that's not strictly necessary, since I have
\autoloadmapfilestrue
in cont-sys.tex.
All my fonts and typescripts are in the same places they were before,
and it seems they are being found; however, pdfetex seems to be unable
to use regular TeX fonts (e.g. Computer Modern) because it can't find
the map files installed by ConTeXt. There are a number error messages
that look like this (representing all the ConTeXt map files, I think):
Warning: pdfetex (file original-public-vnr.map): \
cannot open font map file
The files exist and are world-readable, so the above must mean that
pdfetex just can't find them.
Now, I did one important thing differently from before: I installed
ConTeXt under $TEXMFLOCAL, which on my system is /usr/local/share/texmf.
So the map files in question are in
/usr/local/share/texmf/fonts/map/pdftex/context/
And I *think* my texmf.cnf is set up correctly:
TEXMFLOCAL = /usr/local/share/texmf
TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}
TEXFONTMAPS = .;$TEXMF/fontname;$TEXMF/fonts/map//
% also TEXFONTMAPS.pdftex and TEXFONTMAPS.pdfetex w/ same values
TEXINPUTS.pdftex = .;$TEXMF/{pdftex,tex}/{plain,generic,context,}//
TEXINPUTS.pdfetex = \
.;$TEXMF/{pdfetex,pdftex,etex,tex}/{plain,generic,context,}//
TEXINPUTS.context = \
.;$TEXMF/{pdftex,etex,tex}/{context,plain,generic,}//
... and so on.
So, anyone have an idea what I might have missed?
--
Matt Gushee
Englewood, CO, USA
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Font definitions.
On Tue, Nov 02, 2004 at 11:29:35AM +, Dirar BOUGATEF wrote: Am trying to define a synonym of my font at 24pt where am not sure at which size my font is installed -should be 12pt- (The ttf includes all the following sizes 12, 18, 24,36, 48, 60, .. but as i've done the install from the pfb + afm that comes with it, i don't really know what size i have now). Both TrueType and Type1 fonts are scalable to any size you want. Some applications (MS Word) will show you a limited selection of sizes, but those are just the application designers' ideas of what sizes are useful--they have nothing to do with the capabilities of the fonts themselves. And regardless of what your Windows menus show, TeX uses its own system for handling fonts. So don't worry about the size: if the font is available at all, it is available in 24pt. But how did you install the fonts, exactly? Did you use the texfont utility? If so, your work is probably almost done, but texfont will have generated some new map files that are probably not known to the system. If you are trying to output PDF, then you probably just need to add references to the new map files to the master pdfTeX config; with DVI, it's a bit more complex, but again is basically a matter of editing one or two map files. This is the error message: It would be helpful if you also showed the exact command that resulted in this error. Maybe the true TeX gurus can deduce from the output what you were trying to do, but the rest of us need a bit more information to have a chance of understanding the problem. -- Matt Gushee When a nation follows the Way, Haven Rock PressHorses bear manure through Englewood, Colorado, USAits fields; [EMAIL PROTECTED] When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Context against XSL
On Fri, Oct 01, 2004 at 12:53:22PM +0200, Nikolai Weibull wrote: * Hans Hagen [EMAIL PROTECTED] [Oct 01, 2004 12:40]: comparisons between the not-taco engines show big differences (also in price) and as soon as extensions start coming into the picture, the 'acclaimed advantage of fo' disappears. Some peeople pay five digit numbers for engines where formulas has to be included as graphic. Heh, serious? That's incredible. I'm really beginning to doubt the authoring in XML-bandwagon's legitimacy. nikolai You and most of the XML community (I once claimed to be part of that, but have lately tried to distance myself, partly for the reasons being discussed here). The original idea was that XML would be a new and better way to author *Web documents*. Somewhere along the line it morphed into a general-purpose, universal data exchange format, in which capacity it serves reasonably well (though it likely should have been designed differently, had people foreseen how it would actually be used). Meanwhile, a ragged band of diehards continued trying to develop and promote XML specifically as a web technology and/or a document technology, but I think very few people have much hope in that area any more. There was an article on O'Reilly Network's XML.com in July entitled XML on the Web has Failed; that may not settle the question, but such a statement would have been unthinkable 2 or 3 years ago. But to get back to the question of XSL: a couple of years ago I was looking for a way to generate print-ready documents from XML. I tried the then-latest version of FOP, which was and maybe still is the most popular open-source XSL-FO processor. I was amazed, after several years of its development by the Apache project, how many features were unimplemented, including some that I considered obvious and important for complex documents (I think, for example, there was no way to do footnotes). In hindsight, this probably shouldn't have been surprising. Print documents are complex, and few people are interested in them, relative to the Web. There probably aren't enough users or interested programmers to support more than a couple of high-quality products in this problem space. Anyway, when I found that FOP wouldn't meet my needs, I started searching for something else--and found ConTeXt. Architecturally, it may not have XSL's Neoclassical tidiness, but it has one huge advantage: it works. -- Matt Gushee When a nation follows the Way, Haven Rock PressHorses bear manure through Englewood, Colorado, USAits fields; [EMAIL PROTECTED] When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How to use PostScript font
On Wed, Aug 18, 2004 at 05:02:00PM +0200, Hans Hagen wrote: [EMAIL PROTECTED] wrote: I'd like to use the paladino font from urw as my body font (Its the one used in the MetaFUN manual). I tried setting: \setupbodyfont[pos,12pt] but it does not work. What is the name that I should use? [ppl,12pt] may work, but nowadays we say: \usentypescript[palatino][\defaultencoding] \setupbodyfont[palatino,12pt] It should be noted (with apologies if this is too obvious) that while ConTeXt attempts to provide a simple, high-level font handling interface--and does a very good job, all things considered--it can't do magic. Either of the above techniques depends on font names that are defined outside of ConTeXt--by the underlying TeX distribution, by you, the user, or by a local administrator. So if neither of Hans' solutions works, you will just have to dig into your TeX font directory (e.g. /usr/local/share/texmf/fonts if you are on Linux--don't know for Windows) and find out the exact file names. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How to use PostScript font
On Wed, Aug 18, 2004 at 03:16:43PM -0400, [EMAIL PROTECTED] wrote: Someone suggsted that I use the actual font names. So I tried: That would be me. But what I really meant was that you may need to know those names in order to solve the problem, not that you can expect to use them directly in ConTeXt. Now I would say you should use a typescript if you can. There's no real benefit to using low-level font commands except that you might avoid the need to create typescripts. Because it looks to me like you probably need to either change the names of the fonts to conform to the built-in typescripts, or write your own typescript. The former could cause trouble if you ever want to use the fonts in LaTeX, so you're probably better off writing your own typescript. It's a bit weird at first, but really quite easy when you get used to it; hmm--let me give you a sample: I'll attach below my Palatino typescript. I haven't used it much lately, so I can't recall if it works 100%, but it might help you get started. I also use TeTeX on Linux, so it might be usable as is. For more info, there's a Fonts in ConTeXt manual that tells you most of what you need to know, and then Bill McClain has some good examples on the Web ... I believe his site is http://home.salamander.com/~wmmclain/. Fonts in TeX take a while to master, but once you do, life is great! (I think ... I hope ... I'll let you know when I get there ;-) -- type-palatino.tex - \usetypescriptfile[type-buy] \starttypescript [serif] [palatino] [8r] \usetypescript[serif][fallback] \definefontsynonym [Palatino-Roman] [pplr8r] [encoding=8r] \definefontsynonym [Palatino-Bold] [pplb8r] [encoding=8r] \definefontsynonym [Palatino-Italic][pplri8r] [encoding=8r] \definefontsynonym [Palatino-Bold-Italic] [pplbi8r] [encoding=8r] \definefontsynonym [Palatino-Slanted] [pplro8r] [encoding=8r] \definefontsynonym [Palatino-Bold-Slanted] [pplbo8r] [encoding=8r] \definefontsynonym [Palatino-Caps] [pplrc8t] [encoding=8t] \stoptypescript \starttypescript [serif] [palatino] [name] \definefontsynonym [Serif][Palatino-Roman] \definefontsynonym [SerifBold][Palatino-Bold] \definefontsynonym [SerifItalic] [Palatino-Italic] \definefontsynonym [SerifBoldItalic] [Palatino-Bold-Italic] \definefontsynonym [SerifSlanted] [Palatino-Slanted] \definefontsynonym [SerifBoldSlanted] [Palatino-Bold-Slanted] \definefontsynonym [SerifCaps][Palatino-Caps] \stoptypescript \starttypescript[PalatinoFace] \definetypeface [Palatino] [rm] [serif] [palatino] [default] [encoding=8r] \stoptypescript -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Disappearing headers -- belated followup
On Tue, Aug 10, 2004 at 09:03:20PM +0200, Hans Hagen wrote: i need a small doc with dummy text to see the effect -) \setupheader[state=empty] those seems redundant to me (since you set up the chapter head anyway) Without that, headers were appearing on the first page of the chapter. I expected there would be a global setup to suppress headers in such places, but I couldn't find it. Did I miss something? your problem probably is that you expect the title marking to be persistant while in reality it is coupled to the chapter mark; \decouplemarking[title] will decouple them Aha! That seems to fix the problem. But could you explain (if the reason is understandable to someone not very familiar with ConTeXt internals)? If the chapter and title headings are coupled, that implies (doesn't it?) that they will appear or not appear in pairs everywhere. Yet in my document, the title stopped appearing on one page and failed to reappear for the rest of the book, whereas the chapter headings continued. I may not absolutely need to know this, but it will help me understand ConTeXt a little better. Thanks for the response. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt output commercial printing houses: Thanks!
Thanks for all the responses. I got some very useful information here. I do have a couple of quick follow-up questions. On Sat, Jul 24, 2004 at 03:21:39PM -0500, Bill McClain wrote: Different shops might have different requirements, but Bookmobile simply requires an exact image of the book, page size defined to be the paper size. Easy. You're referring to just the interior, right? I would think that covers have to have a bit of bleed, no? This has all been for digital printing and perfect-bound paperbacks. Pretty much what I'm doing for now. As a matter of fact, partly inspired by your example, I'm attempting something rather similar to your publishing biz--though not in direct competition, I hope and believe. On Sun, Jul 25, 2004 at 12:01:03PM +0200, Mats Broberg wrote: Being a newbie when it comes to ConTeXt, but having worked in the commercial printing busines for a decade, I would say that the majority of printers actually prefer PDF files rather than Quark, InDesign or Pagemaker files. At least that is the case in Europe, and it would suprise me if it is not the same situation in USA. Well, yes. Many printers here do prefer PDF. However, there's a small problem in some cases--I know this is true for Kinko's, and was wondering if it's true for regular printers, too: they think that PDF means Adobe PDF--i.e. they believe that Adobe software is *the* way to produce PDF, and are mostly unaware that there is such a thing as a PDF standard. Now, I don't fully understand the issue, but apparently Adobe software doesn't entirely follow the published specs, whereas TeX does. And some processing software seems to be designed specifically to work with the quirks of Acrobat output, and sometimes has trouble with PDFTeX output. - Also, I don't know whether it is possible to downsample images in PDF's that you generate from ConTeXt. If it is, avoid it. That raises an important question: if downsampling is done, is it obvious what ConTeXt commands cause it to happen? The printer expects CMYK images (not RGB!) where the resolution is approx. 2 times the screen count in the final print, @ the physical size on the paper. So if you have an image in your PDF that is 10 cms /4 in. wide, and you want it printed in a 150 lpi (lines per inch) screen, make sure the original resolution is 300 dpi @ 10 cms / 4 in. Now that's interesting. I imagined you would get the best results with images that were designed exactly at the printer resolution. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problems with left and right
On Fri, Jul 23, 2004 at 11:26:45PM -0700, Hans Hagen Outside wrote: I have noticed a couple of cases where ConTeXt macros seem to have confused left and right sides: First of all, thanks for your quick reply! forthermore, think of right as raggedright And left as ... raggedleft? Anyway, I gather you're saying that the behavior I've observed is correct. E.g.: [align=left] [align=right] abc foo, bar, baz de dum-da-dum-da-dum fghijkl tweedledee With all due respect, I don't see how that makes any sense. In common English usage, left-aligned means the text is set against the left edge, and right-aligned means the text is set against the right edge. I can't imagine Dutch or other European languages are very different in that respect (though I've been known to guess wrong about languages). Furthermore, this usage of 'align=side' is inconsistent with some other things in ConTeXt, such as \rightaligned, which behaves as I would expect it to. 2) In order to format format headers for a book so that the book title appears on the left-hand page and the section title on the right, I had to do this: \setupheadertexts [] [section] [title] [] ... which, as I read the documentation, is in the opposite order to what it should be. Is this a bug in ConTeXt, or have I misconfigured something? no, think of spreads You mean page spreads? Like this? +++ ||| | even-| odd- | | numbered | numbered | | page | page | ||| +++ That's exactly what I was already thinking of, and it doesn't make sense: COMMAND:\setupheadertexts [] [section] [title] [] RESULT: +++ | title| section | ||| ||| ||| ||| +++ If you say there's a logical explanation for this, then I believe you. I still maintain it's really counterintuitive and likely to cause confusion. And if so, aren't you making extra work for yourself (because you have to explain it)? Or is it just me? -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problems with left and right
On Sat, Jul 24, 2004 at 10:39:52AM +0200, Peter Münster wrote: On Sat, 24 Jul 2004, Matt Gushee wrote: COMMAND:\setupheadertexts [] [section] [title] [] RESULT: +++ | title| section | ||| If you say there's a logical explanation for this, then I believe you. Hello Matt, isn't it logical, if you consider \setupheadertexts [odd-left] [odd-right] [even-left] [even-right] ? Please explain why I should consider it that way. Most books in every language I know of[*] are laid out with the even page on the left and the odd page on the right. Furthermore, the ConTeXt manual says: Those who want more variations in headers and footers can use four instead of two arguments \setupfootertexts [even left] [even right] [odd left] [odd right] So the order of arguments contradicts both the documentation and what I think of as common sense. NOTES: * There are exceptions, of course. Other than English, languages I am familiar with are mainly Chinese and Japanese. Traditional books in those languages are laid out in the opposite direction to European books, but almost all contemporary books in China, and I think most in Japan, follow the Western practice. Besides, we're all gwailos here, aren't we? -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Problems with left and right, Part II
On Fri, Jul 23, 2004 at 01:19:57PM -0600, Matt Gushee wrote: I have noticed a couple of cases where ConTeXt macros seem to have confused left and right sides: Just found another: \setuphead [title] [align=right] places the title on the left side, and vice versa. I have also confirmed that this takes place on both machines where I have ConTeXt installed, so it's unlikely to be caused by anything I did. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Disappearing headers
Hello, all--
I am trying to format a book such that the book title appears in the
header of each left-hand page, and the chapter title appears in the
header of each right-hand page. I think (though I haven't decided for
sure) that I want each chapter to start on a right-hand page. It seems
that, when chapters are forced to begin on right-hand pages, the book
title fails to appear on the first blank page inserted to move the
chapter start, and on all subsequent pages.
Here are the commands I am using related to headers:
\setuphead [title]
[align=left,textstyle={\switchtobodyfont[BernhardModern]\bf}]
\setuphead [chapter]
[page=right,head=nomarking,after=\blank]
\setuppagenumbering [alternative=doublesided,location=margin]
\setupheader [style=\it]
\setupheadertexts [] [chapter] [title] []
% reverse order, as mentioned in my earlier post
With all these commands enabled, I get the effect I want: chapters begin
on righthand pages, the title and chapter title appear, respectively, in
the left and right page headers (adjacent to the page numbers, with the
page numbers toward the outside edge of the page). But, as I said, the
book title stops appearing as soon as a blank page is inserted to move
the chapter start to the right.
If I comment out *both* the \setuphead [chapter] command and the
\setuppagenumbering command, the title continues to be displayed
throughout the text. If I enable either of the two, the title disappears
again. By the way, it appears that this \setuppagenumbering command has
a side-effect of forcing chapters to begin on the right. Is that really
a good idea? It's certainly surprising to me.
So, am I doing something wrong, or is this a bug?
--
Matt Gushee When a nation follows the Way,
Englewood, Colorado, USAHorses bear manure through
[EMAIL PROTECTED] its fields;
http://www.havenrock.com/ When a nation ignores the Way,
Horses bear soldiers through
its streets.
--Lao Tzu (Peter Merel, trans.)
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Virtual font tip
On Thu, Jul 08, 2004 at 01:03:55PM +0200, Holger Schöner wrote: After purchasing the FontSite 500 CD, I wanted to make good use of some of the nice text fonts it contains--in particular I wanted to create TeX virtual fonts that would add ff, ffi, and ffl ligatures and replace the ugly ( ;-) ) lining numerals with old-style figures. I do not know, whether this is exactly what you looked for. But I found a page by Christopher League, who created those virtual fonts (I think) for use in LaTeX. I had good success in using the stuff he put on his webpage as well for ConTeXt, and have set up a page in the Wiki, at Oh, I love when people provide solutions for my problems after I've already solved them for myself! Of course, I never asked. Maybe I should have. Thanks anyway. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Virtual font tip
On Thu, Jul 08, 2004 at 03:25:03PM +0100, Adam Lindsay wrote: Don't be discouraged, Matt. Oh, I wasn't really discouraged, just mildly sarcastic (as much as I dare to be toward someone who was just trying to help ;-) I think your tool is really nifty--it's precisely one of those if I have time, I'll learn about VPLs projects that I wanted to have realised at some point. Your solution goes far beyond the FontSite500 support, as far as I can see. Yes and no. Probably the technique is generally applicable, but the specific script I used relies on: * The way FontSite organizes their font families (including the specific code points assigned to the ligatures, which may be common but are probably not universal); * The file names generated by texfont; and * The organization and formatting of the VPL files that I had to work with. I expect these will vary depending on a number of circumstances, but I don't know exactly how. I would welcome suggestions (or patches) that will help make the script more generally useful. Thanks for the encouragement. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Virtual font tip
On Wed, Jul 07, 2004 at 08:48:14AM -0500, Bill McClain wrote: On Tue, 6 Jul 2004 18:07:39 -0600 Matt Gushee [EMAIL PROTECTED] wrote: Please let me know if you find any errors or points that need to be clarified. Very nice page! I think there is a typo here: $ for fam in *; do texexec --ve=fontsite --co=$fam --so=$fam --ma --in \ --virtual --expert done Should be texfont instead of texexec? Oops! You're absolutely right. I'll go fix that. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] How to define Small Caps when installing a new font (repost)
On Wed, Jul 07, 2004 at 06:37:12PM +0200, Fabio Fogliuzzi wrote: A question about fonts. I have successfully installed (for the first time) a font using the texfont utility and creating both small caps and slanted variants of the font. I wrote the following typescript saved in a file named 'Typeface.tex': All seems to work as expected, except for the use of the SansItalicCaps, SansBoldCaps and SansBoldItalicCaps variants. I don't have a definitive answer, but looking at the built-in ConTeXt modules will give you an important clue: the names SerifCaps, SansCaps, and MonoCaps appear in a number of places, e.g. in font-map.tex: \definebodyfont [14.4pt,...] [tf=Serif sa 1.06, sc=SerifCaps sa 1.06] But the variants you are trying to use don't occur at all, which suggests that ConTeXt has no way to recognize the combination of small caps with bold or italic. It would be nice if it did. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Virtual font tip
Hello, all-- After purchasing the FontSite 500 CD, I wanted to make good use of some of the nice text fonts it contains--in particular I wanted to create TeX virtual fonts that would add ff, ffi, and ffl ligatures and replace the ugly ( ;-) ) lining numerals with old-style figures. After considerable effort I figured out how to edit the VPL files for the desired effect. I also wrote a Python script to automate the process, though it may well not work for anyone else. Anyway, since I have found very little documentation on virtual fonts, I thought others might benefit from my experience, so I wrote up the procedure and posted in the (new) TeX Tips section of my Web site. So, if anyone is interested in this subject, have a look at http://havenrock.com/textips/bookfonts.html Please let me know if you find any errors or points that need to be clarified. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Two texexec.ini files?
On Tue, Jun 29, 2004 at 11:13:23PM +0200, Henning Hraban Ramm wrote: I have noticed that the ConTeXt distribution contains both $TEXMF/context/config/texexec.rme and $TEXMF/scripts/context/perl/texexec.rme Are they both supposed to be used? What happens if they're not the same? This is a FAQ. Oops, sorry. Except ... is there a list of FAQs somewhere? I've never seen it. They're both unused. You must rename or copy one to texexec.ini (I prefer it in config). Yes, I knew they had to be copied. I take it, then, that texexec.ini can be in either of the above locations ... maybe anywhere accessible to kpathsea? Anyway, it's a bit confusing to have two texexec.rme files. I would suggest removing one of them from the distribution. Thanks for your reply! -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] generating html
On Wed, Jun 23, 2004 at 04:04:20PM +0200, [EMAIL PROTECTED] wrote: is there an easy way to transform a ConTeXt document into html...? I searched the archives of this mailing list about a year ago for info on that subject, and found nothing. So it would appear there is no such way ... though I didn't investigate very deeply. What I would do--if I were working with new documents--would be to create the documents in XML; then I could use ConTeXt for the print version, and XSLT to generate HTML. XSLT isn't exactly easy, but it is proven and widely used. If you need to work with documents that are already in ConTeXt ... you know, now that I think about it, it probably wouldn't be very hard to write a script to translate ConTeXt to XML. Once you've done that translation, you use XSLT to output HTML. Again, not easy, but certainly feasible. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: ConTeXt-Wiki
On Tue, Jun 22, 2004 at 05:55:24PM +0200, Patrick Gundlach wrote: Arguments for a collection could be: 1) Perhaps a comprehensive and classified collection of sample documents could spare others such time consuming trials. a) it is impossible to have a comprehensive collection of documents. There are too many faces ConTeXt has. b) It is hard to classify the documents. Two possibilities: Yes, it is hard to classify them (and many other things) if you insist on forcing them into a single, canonical hierarchy. But what if you classified documents on the basis of keywords, or key phrases? Then visitors could either search based on those phrases or browse a keyword index. Of course, that assumes your Wiki software has some means of managing metadata. And you could just make some arbitrary decisions about what materials should be included and how to classify them. Even a very imperfect collection would be more helpful than none. And if people don't like your collection, tell them to start their own. Isn't that what the Web is all about? -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Installation problem
Hello, all-- I have just installed the latest (stable release of) ConTeXt on a new machine [details below], but texexec is not working properly. I keep getting the following error: sh: cont-en: command not found I have Googled for information on this problem, but the solution I found doesn't make sense to me. In response to a previous inquiry on this list, someone wrote: but the absence of cont-en that is the problem. Or if cont-en exists, it is not in your path or not executable. But what exactly is this 'cont-en'? I have two machines with working ConTeXt systems, and neither of them has a command with exactly that name. So I imagine the reference is to a file named 'cont-en.extension'. But there is more than one such file, and none of them seems to be a type of file that would normally be made executable (nor are they executable on the machines where I have ConTeXt working). Any thoughts as to what's wrong? Oh, yes, my system is: Debian GNU/Linux 3.0 teTeX 1.0.2 * Note that teTeX comes with an old and not-properly-configured version of ConTeXt. I unzipped the new package over that ... could something left over from the old ConTeXt be causing the problem? Thanks for any info. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Installation problem
On Mon, Jun 21, 2004 at 10:46:40AM +0200, Thomas A. Schmitz wrote: cont-en.efmt is a format file that ConTeXt need to run. In order for this file to be built, run texexec --make en de nl Yes, I knew about that, and had already created the en and nl formats (since I don't work with German documents at all, I don't need de, do I?). Just as a side note, why would the shell think the format is supposed to be a command? That makes me wonder if there is some incorrect quoting in the Perl script. On Mon, Jun 21, 2004 at 10:45:37AM +0200, Patrick Gundlach wrote: But what exactly is this 'cont-en'? probably a hard link to pdftex or pdfetex. Could be, but it's never been necessary in the past. As I mentioned, I have two working ConTeXt installations with no such command. teTeX 1.0.2 * Note that teTeX comes with an old and not-properly-configured version of ConTeXt. I unzipped the new package over that ... oh, bad thing ;-) Yes, I suppose so. Well, I've deleted all the old ConTeXt directories, reinstalled the new version, copied the *.rme files to *.ini (or whatever they are supposed to be ... I think), regenerated the 'en', 'nl', and 'metafun' formats, and run texhash ... I'm still getting the same error. I also ran a diff comparing the texmf.cnf from the new installation with one from one of my working installation. The files are identical in everything related to ConTeXt. So, thank you both for your quick replies, but it looks like there's some other problem. BTW, this is a very new release of ConTeXt--June 16, according to the Pragma Web site. Has anyone used this version successfully? -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Installation problem
On Mon, Jun 21, 2004 at 11:29:17AM +0200, Patrick Gundlach wrote: Hello, Well, I've deleted all the old ConTeXt directories, reinstalled the new version, copied the *.rme files to *.ini (or whatever they are supposed to be ... I think), regenerated the 'en', 'nl', and 'metafun' formats, and run texhash ... I'm still getting the same error. did you update texexec and texutil? They are symlinks, so yes, unzipping the new archive updated them. BTW, this is a very new release of ConTeXt--June 16, according to the Pragma Web site. Has anyone used this version successfully? The current beta is 2004.6.20 (see http://members.ping.de:8062/context/show/HomePage ;-) Okay, tried that, no change. I also tried creating /usr/bin/cont-en as a symlink to pdfetex and pdftex (not at the same time, of course). The results were, well, different: First, with cont-en as a link to pdftex: | [EMAIL PROTECTED]:/var/tmp$ texexec ut.tex | | TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004 | | executable : pdfetex | format : cont-en | inputfile : ut | output : standard | interface : en | current mode : none |TeX run : 1 | | This is pdfTeX, Version 3.14159-1.00a-pretest-2004-ojmw (Web2C 7.3.7) | I can't find the format file `cont-en.fmt'! | |return code : 256 | run time : 1 seconds | | total run time : 4 seconds Can't find 'cont-en.fmt'? Well, that makes sense, doesn't it? Since, as I understand it, ConTeXt normally uses pdfetex, which would need cont-en.efmt. But it was worth a try. So then I tried pdfetex: | [EMAIL PROTECTED]:/var/tmp$ texexec ut.tex | | TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004 | | executable : pdfetex | format : cont-en | inputfile : ut | output : standard | interface : en | current mode : none |TeX run : 1 | | This is pdfeTeX, Version 3.14159-1.00a-pretest-2004-ojmw-2.1 (Web2C 7.3.7) | This is pdfeTeX, Version 3.14159-1.00a-pretest-2004-ojmw-2.1 (Web2C 7.3.7) | (/usr/share/texmf/web2c/natural.tcx) | ** | ! End of file on the terminal... why? | entering extended mode | (./ut.tex | Error: cont-en (file pdftex.cfg): cannot open config file | |return code : 65280 | run time : 3 seconds | | total run time : 6 seconds Hmm ... two questions here: what is the 'End of file on the terminal?' Is that referring to natural.tcx (which comes from the ConTeXt distribution)? And what about pdftex.cfg? Indeed, it doesn't exist. But it doesn't exist on the machines where I have ConTeXt working, either. So I don't know if either of the above results are meaningful. Oh, by the way, the input file was this: \usetypescriptfile [type-utopia] \usetypescript [UtopiaFace] \showbodyfont [Utopia] \end And yes, the typescript in question is available; both it and this test file have worked for me on another machine. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Installation problem
On Mon, Jun 21, 2004 at 04:57:00PM +0200, Patrick Gundlach wrote: I just came across the same error. I don't know why I didn't notice before, but texexec seems to be 'broken'. Well, I don't know if it is really broken, but it just does not to the same thing it used to. It gives me same error as you get. Using an old texexec works fine for me. I didn't look into this yet. Ah-ha! Nice to know I'm not crazy after all. On Mon, Jun 21, 2004 at 05:11:44PM +0200, Hans Hagen wrote: hm, maybe some bug due to changed as a result of the new tds and binaries; i'll upload my local latest -) Thanks to Hans and all! -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: font mystery
On Sun, Oct 05, 2003 at 12:46:50PM +0200, Thomas A.Schmitz wrote: Maybe one further element that would suggest Context is using a cached copy of the tfm-file instead of the newly created file: when I move the file Myfont.tfm out of the $home/texmf/fonts/tfm directory, pdftex gives me the expected error ! I can't find file `Myfont'. However, Context will still happily produce output--with an outdated copy of the tfm! Are you sure it is the TFM file that is out of date? Or might it be a PK font? If it is the latter, you can simply find the PK font cache (often something like /var/lib/texmf/fonts/... on Linux systems) and delete any suspicious files. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Writing Japanese using ConTeXt
On Sun, Jun 15, 2003 at 11:03:06PM +0200, Hans Hagen wrote: A few questions; - How are the rules for breaking? For a detailed explanation, you should refer to the big book. But actually the rules are not all that difficult--probably a good deal simpler than European languages, I'd say. The most important thing to know is that there is a certain set of characters that may not occur at the end of a line, and another set that may not occur at the beginning, and I believe (it's been a while since I seriously looked at any of this) that there are certain unbreakable pairs, but not a huge number of them. - how many glyphs are there (well, i could look it up in the big cjk book) That's rather a tricky question, and the answer depends partly on whether you want a complete solution or an 80/20 one. You probably know that there are two main character sets in Japanese: jis-x-0208 and jis-x-0212 (of course, the full names are suffixed with years, but I forget what the current versions are). The vast majority of all Japanese text (notice I said text, *not* documents) can be written with hiragana and katakana (50+ characters each), roman alphabet (256, I guess?), and the kanji in jis-x-0208, of which there are about 6000. However, it's hard to get away without using jis-x-0212. Literary terms and probably some specialized scientific vocabulary often require it, and most critically, geographic and personal names very often use jis-x-0212 characters. It's common to find names whose characters are represented in jis-x-0208, but for any given name you must use a different glyph that is in jis-x-0212. In Japanese culture it is unacceptable to substitute glyphs in names. An analogy in Western languages might be: suppose you had a typesetting system that was incapable of rendering the string sen at the end of the word. Thus, whenever yyou encountered the names Andersen or Olsen, you would print them as Anderson and Olson. I don't think anyone would consider that acceptable. So the upshot of this is that, though jis-x-0212 glyphs make up a very small proportion of the Japanese text that is printed (I'd guess 1-2 percent), a large proportion of documents (40-50 percent, maybe) require one or more glyphs from that set. So that's another 8000 glyphs, if you want to do it right. One other point that may or may not matter is that ... I'm not sure if this is the correct terminology, but the code points of the Japanese character sets are arrayed in a sparse matrix (?). Each plane is 194x194, rather than 256x256. I used to know why. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Writing Japanese using ConTeXt
is that besides Lunde's books there is really nothing available in English. I could probably make some sense out of the Japanese works that are available, but it would take up much more time than I have. With the ConTeXt example that I posted yesterday, I am already able to write Japanese in UTF-8, use a Unicoded Japanese font in ConTeXt, and get Japanese output. I hope the hard part is already behind me! :-) The only thing that still puzzles me is how I can add interglyph space so that TeX can break the lines. If someone can help, I would really appreciate it! Sorry, no idea. But it sounds like you've made an admirable effort so far. I was working along similar lines a couple of years ago, but was never able to produce anything useful. Guess you're a better TeXnician than I. -- Matt Gushee When a nation follows the Way, Englewood, Colorado, USAHorses bear manure through [EMAIL PROTECTED] its fields; http://www.havenrock.com/ When a nation ignores the Way, Horses bear soldiers through its streets. --Lao Tzu (Peter Merel, trans.) ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
