Re: [NTG-context] Supress chapter number in sections
I'm bumping my last question here... As Duncan suggested, \setupsection[section-3][previousnumber=no] supresses the chapter section numbers in my section headings. Is there an easy way to do likewise for the figure and equation numbers such that the numbering does not include the chapter number? Cheers, Randall ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new version
Adam Lindsay wrote: the next (main) release will probably have a new texexec (ruby version, smoother, faster, more clever, no ini file etc) what does texmfstart newtexexec --make --all do? 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] new version
Adam Lindsay wrote:
(i cc to karl who knows more about the detry details of path expansion than i
do)
Hans Hagen said this at Wed, 25 May 2005 17:34:24 +0200:
the next (main) release will probably have a new texexec (ruby
version, smoother, faster, more clever, no ini file etc)
Hmm. I hand-updated to the latest, and now texexec wants to rebuild the
format on every run.
I'm not used to seeing this, anyone have any hints on where to poke around?
(the format is in texmf.local/web2c/ and in a pdfetex subdir. I've
texhashed, too.)
since engine support is either broken or not implemented in kpse/tetex, i need
to sort it out myself; this is done in:
sub checktexformatpath {
# engine support is either broken of not implemented in some
# distributions, so we need to take care of it ourselves
my $texformats ;
if (defined($ENV{'TEXFORMATS'})) {
$texformats = $ENV{'TEXFORMATS'} ;
} else{
$texformats = '' ;
}
if ($texformats eq '') {
if ($dosish) {
$texformats = `kpsewhich --expand-var=\$TEXFORMATS`.chomp ;
} else {
$texformats = `kpsewhich --expand-var=\\\$TEXFORMATS`.chomp ;
}
}
if ($texformats !~ /web2c[\/\\].*\$ENGINE/) {
$texformats =~ s/web2c/web2c\/{\$ENGINE,}/ ;
$ENV{'TEXFORMATS'} = $texformats ;
print " fixing texformat path : $ENV{'TEXFORMATS'}\n";
}
if (! defined($ENV{'ENGINE'})) {
if ($MpEngineSupport) {
$ENV{'ENGINE'} .= $MpExecutable ;
} ;
$ENV{'ENGINE'} = $TeXExecutable ;
print "fixing engine variable : $ENV{'ENGINE'}\n"; ## just added
}
}
how i hate this naming; when -long ago- i started using local trees, i adopted
the texmf-local naming that i noticed in those days, and look what we have here:
fixing texformat path : .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/
share/texmf.local,!!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/
teTeX/share/texmf.tetex,!!/usr/local/teTeX/share/texmf}/web2c/{$ENGINE,}/{,}//
0
well, this magic line will append web2c/{$ENGINE,} to each path, including the
share/texmf.local path so i'm puzzled; one complication is that kpse is not able
to report the path that will be used (probably for good reason); so the format
should end up in:
!!/usr/local/teTeX/share/texmf.local/web2c/pdfetex/cont-en.fmt
could it be that the /{,}// is playing tricks? can you try to add
$texformats =~ s/\{\,\}\/\/// ;
i.e. get rid of the trailing crap so that th eend looks like /web2c/{$ENGINE,}/
can you check at what value texexec sets $ENGINE ?
(setting TEXFORMATS at the shell level will also work; that is what i normally
have)
watch this mix of teTeX and tetex and Users and Library vs share; if i would not
know better, i'd think it was a blob of tricky perl code -)
last time i tried it on the mac it worked, so i must try again
the file should end up in web2c/pdftex
fmtutil: running `pdfetex -ini -jobname=cont-en -progname=context
forget about fmtutil, it cannot and will not handle engines
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] new version
Hans Hagen said this at Wed, 25 May 2005 17:34:24 +0200:
> the next (main) release will probably have a new texexec (ruby
>version, smoother, faster, more clever, no ini file etc)
Hmm. I hand-updated to the latest, and now texexec wants to rebuild the
format on every run.
I'm not used to seeing this, anyone have any hints on where to poke around?
(the format is in texmf.local/web2c/ and in a pdfetex subdir. I've
texhashed, too.)
adam
fixing texformat path : .:{/Users/atl/Library/texmf,!!/usr/local/teTeX/
share/texmf.local,!!/usr/local/teTeX/share/texmf.gwtex,!!/usr/local/
teTeX/share/texmf.tetex,!!/usr/local/teTeX/share/texmf}/web2c/{$ENGINE,}/{,}//
0
executable : pdfetex
format : cont-en
inputfile :
output : pdftex
interface : en
current mode : none
TeX run : 1
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
\write18 enabled.
(/usr/local/teTeX/share/texmf.local/web2c/natural.tcx)
kpathsea: Running mktexfmt cont-en.fmt
fmtutil: running `pdfetex -ini -jobname=cont-en -progname=context
-8bit *cont-en.ini' ...
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4) (INITEX)
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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: Accents in MathML
I said: > Interestingly, if I forget about unicode and use é instead of é, > then no matter what I put in the preamble I get the e with a guillemot > superimposed. So whatever is mapping é incorrectly seems also to be > mapping é incorrectly. Further testing suggests that my problem is this: Between \startXMLdata and \stopXMLdata, where MathML is being parsed directly by ConTeXt, I get the wrong results for accented characters within elements. For example, I get an e character with a guillemot superimposed on top when I want an e with an acute accent. It doesn't seem to matter whether the markup is unicode é, the entity é, or the command \eacute. Similar problems happen with other accents I have tried. In the case of ñ the accent is almost right but comes out too big (looks like the maths version of the accent?). The following is my local test file, using unicode and comparing running text to in MathML: -- \mainlanguage[es]\enableregime[utf]\useencoding[uc] \usemodule[mathml]\setupoutput[pdftex] \starttext Situación niños volúmenes sí interés: \startXMLdata Situación niños volúmenessí interés\stopXMLdata \stoptext -- The following is a non-unicode test file that will process on Live and exhibits the same errors in the MathML accent rendering. It uses entity references instead of unicode in the MathML, but because they map to the same thing the output is the same: -- \mainlanguage[es]\enableregime[utf]\useencoding[uc] \usemodule[mathml]\setupoutput[pdftex] \starttext \startXMLdata Situación niños volúmenessí interés\stopXMLdata \stoptext -- I have a feeling I have made this more complex than it needed to be, but can anyone shed light on how to fix it? Thanks, Duncan PS Apologies for the nonsense Spanish content - it's just random words with accents. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: Accents in MathML
>>I'm processing some Spanish from Unicode and some of it is in MathML,
>>for which I use ConTeXt's native processing. There seems to be a problem
>>with accents. When I run this on Live:
>>
>>--
>>\mainlanguage[es]\enableregime[utf]\useencoding[uc]
>>\useXMLfilter[utf]\usemodule[mathml]
>>\starttext
>>Maths with accents:
>>\startXMLdata
>>interés\stopXMLdata
>>\stoptext
>
>
> are you sure that your e with accent is codes in utf?
>
> Hans
Further testing locally (rather than via Live) produces different
problems, so maybe the unicode is perverted by submitting the data via
http to the Live server?
In any event, testing only locally I can now produce the following results:
As long as I have either '\enableregime[utf]' or '\useXMLfilter[utf]'
then the é produces an e with a guillemot superimposed on top (this is
wrong - I wanted an e with an acute accent).
If I don't have either of those commands in the preamble, then I get Ãl,
which looks like the literal unicode as two ASCII chars.
Interestingly, if I forget about unicode and use é instead of é,
then no matter what I put in the preamble I get the e with a guillemot
superimposed. So whatever is mapping é incorrectly seems also to be
mapping é incorrectly.
Unfortunately none of this is the behaviour I originally experienced in
my large project file, which was stalling the process with the following
error:
! Please use \mathaccent for accents in math mode.
\char
19
\dobuildtextaccent ...{\let \char \normalaccent #1
\let \char \normalchar #2}
Inter\dobuildtextaccent {\char 19 }{e}
s
\secondoftwoarguments #1#2->#2
\MMLpmath ...tyle}{#1}\setMMLpmathstyle {mstyle}#2
\endgroup
l.1 ...{}{Inter\dobuildtextaccent {\char 19 }{e}s}
\xmlr
{mi}{X}{}{cargo}\emp...
...
l.15628 ...cargo\stopXMLdata
So I think I have two quite different errors, but it would be really
good to know what can make é come out right in the minimal file, while I
try to construct another minimal file which will give me the actual
error above!
Many thanks.
Duncan
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
