[NTG-context] Not resetting chapter number on new part
I would like the chapters across all my bodymatter to be
numbered sequentially, even when they cross the part
boundary. I.e, if I have
\part{A part}
\chapter{A chapter}
\part{Another part}
\chapter{Another chapter}
I would like the latter to be numbered 2, not 1. I can of
course do this by hacking \part, but I would like to know if
there is a way to prevent number reset (something like
resetchapter=no).
--
Giuseppe "Oblomov" Bilotta
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] font havoc
Hans Hagen wrote: what puzzles me is: pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / -- bdpi 72 --mag 1+7/72 --dpi 79 cmmi10 ^ ^^^ which are diferent fonts That is just a timing error. What you see is the stdout and stderr messages from two separate programs intermixed. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] font havoc
Hans van der Meer wrote:
Suddenly it seems, I am getting bad messages for quite normal math
fonts:
Warning: pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / --
bdpi 72 --mag 1+7/72 --dpi 79 cmmi10
mktexpk: Mismatched mode ljfzzz and resolution 72; ignoring mode.
mktexpk: Can't guess mode for 72 dpi devices.
mktexpk: Use a config file, or update me. ( Why is this?)
Font cmsy8 at 72 not found
Warning: pdfetex (file cmmi10): Font cmmi10 at 79 not found
{/usr/local/teTeX/share/texmf-dist/fonts/enc/dvips/psnfss/8r.enc}usr/local/te
TeX/share/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb>teTeX/shar
e/texmf-dist/fonts/type1/urw/helvetic/uhvb8a.pfb>share/texmf-
dist/fonts/type1/urw/courier/ucrr8a.pfb>
I am not aware having changed to resolution 72 for ljfzzz or doing
something different from previous installations of new context
versions. The mode for ljfzzz was set with texconfig.
I was running the 2005-10-27 context version, but reverting tot
2005-08-31 did not solve the problem.
What has happened to my fonts?
Has it something to do with the fact that tetex and context seem to
use directories .texmf-config and .texmf-var differently?
Why does something that ran without a hitch suddenly is broken?
Does someone know how to restore things to normal?
probably due to the changes in latin modern map/enc naming; older
versions don't mix well currently
what puzzles me is:
pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / -- bdpi 72
--mag 1+7/72 --dpi 79 cmmi10
^
^^^
which are diferent fonts
is automapfile enabled on your system?
Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] font havoc
Taco Hoekwater wrote: Hans van der Meer wrote: Suddenly it seems, I am getting bad messages for quite normal math fonts: Warning: pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / -- bdpi 72 --mag 1+7/72 --dpi 79 cmmi10 Most likely cause: pdftex cannot find the map file that contains the cmmi10 entry, and therefore assumes it is a bitmap font. In my system, there are cmmi10 lines in the following three map files: fonts/map/pdftex/context/context-base.map fonts/map/pdftex/context/original-ams-cmr.map fonts/map/pdftex/context/original-public-lm.map Either pdftex cannot find those (the third one is normally the used one), or it loads an incorrect one. In any case, you should check the 'map file' part of context and pdftex's messages. Or you can try posting the log of the run \starttext Hello World!\stoptext if you can't figure out the messages yourself. btw, in the tui file you can see what map files are expected (loaded) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] font havoc
Hans van der Meer wrote: Suddenly it seems, I am getting bad messages for quite normal math fonts: Warning: pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / -- bdpi 72 --mag 1+7/72 --dpi 79 cmmi10 Most likely cause: pdftex cannot find the map file that contains the cmmi10 entry, and therefore assumes it is a bitmap font. In my system, there are cmmi10 lines in the following three map files: fonts/map/pdftex/context/context-base.map fonts/map/pdftex/context/original-ams-cmr.map fonts/map/pdftex/context/original-public-lm.map Either pdftex cannot find those (the third one is normally the used one), or it loads an incorrect one. In any case, you should check the 'map file' part of context and pdftex's messages. Or you can try posting the log of the run \starttext Hello World!\stoptext if you can't figure out the messages yourself. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] font havoc
Suddenly it seems, I am getting bad messages for quite normal math
fonts:
Warning: pdfetex (file cmsy8): kpathsea: Running mktexpk --mfmode / --
bdpi 72 --mag 1+7/72 --dpi 79 cmmi10
mktexpk: Mismatched mode ljfzzz and resolution 72; ignoring mode.
mktexpk: Can't guess mode for 72 dpi devices.
mktexpk: Use a config file, or update me. ( Why is this?)
Font cmsy8 at 72 not found
Warning: pdfetex (file cmmi10): Font cmmi10 at 79 not found
{/usr/local/teTeX/share/texmf-dist/fonts/enc/dvips/psnfss/8r.enc}usr/local/te
TeX/share/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb>teTeX/shar
e/texmf-dist/fonts/type1/urw/helvetic/uhvb8a.pfb>share/texmf-
dist/fonts/type1/urw/courier/ucrr8a.pfb>
I am not aware having changed to resolution 72 for ljfzzz or doing
something different from previous installations of new context
versions. The mode for ljfzzz was set with texconfig.
I was running the 2005-10-27 context version, but reverting tot
2005-08-31 did not solve the problem.
What has happened to my fonts?
Has it something to do with the fact that tetex and context seem to
use directories .texmf-config and .texmf-var differently?
Why does something that ran without a hitch suddenly is broken?
Does someone know how to restore things to normal?
Hans van der Meer
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Hans Hagen wrote:
Thomas A. Schmitz wrote:
... it's still missing a few features (I don't think it can
post-process pdf-files yet) and has a few buglets...
it should at least i remember writing some code -)
Here is an old example:
\defineregister[Name][Names]
\setupregister[Name][pagestyle=\it]
\setupregister[Name][bf][pagestyle=\bf]
\starttext
Names:
\Name[bf::]{Hans}
\Name{Taco}
\startregister[Name][bf::]{Patrick}
\page[yes]
\Name{Hans}
\stopregister[Name][bf::]{Patrick}
\page[yes]
\Name{Patrick}
\placeregister[Name]
\stoptext
--
Regrettably, I have now no time to install and check the new version of
newtexexec.rb, so perhaps it is already done. Please, for quick check
focus on 'Patrick' entry, it should have "1--2, 3" page numbers.
Or more complex example:
\defineregister[Name][Names]
\setupregister[Name]
\setupregister[Name][bf][pagestyle=\bf]
\starttext
Names:
\Name{Patrick}
\Name[bf::]{Hans}
\Name{Taco}
\startregister[Name][bf::]{Patrick}
\page[yes]
\Name{Patrick}
\page[yes]
\Name{Hans}
\stopregister[Name][bf::]{Patrick}
\placeregister[Name]
\stoptext
--
Possible variants:
1) Patrick 1, 2, {\bf 1--3}
2) Patrick {\bf 1--3}, 1, 2
3) Patrick 1--2, {\bf 1--3}
4) Patrick {\bf 1--3}, 1--2
in case of variants 1 v. 2 and 3 v. 4 I am not sure how the categories
'empty_string' and "bf" are sorted. But it does not matter since user
can set any category name.
variants 3, 4 should be set if some register option (coupling?) is set on
vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Thomas A. Schmitz wrote: ... it's still missing a few features (I don't think it can post-process pdf-files yet) and has a few buglets... it should at least i remember writing some code -) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Thomas A. Schmitz wrote: Alas, I spoke too soon... I tested again with a more complex document (the book project I'm working on), and I'm having problems again: page ranges still gobble up the other entries. If I insert a \seeindex command, the index is sorted according to page numbers instead of entries. The file is probably too big to send, but I can of course send logs, .tui or whatever might be useful... or make a dummy multipage doc with lots of entries Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] fix for verbatim
� wrote: On Wed, 9 Nov 2005, Hans Hagen wrote: (btw, it becomes time to drop non-etex code -) Is there any reason to keep it? sentiment Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Creatin metafun.mem on OSX
On 10 Nov 2005, at 09:36, Gerben Wierda wrote: The "crontab" tool takes care of this. You get mail as yourself on your system. (Now I understand) Right (in 99.99% of the cases). Update, installed, configured. I'm happy. Yes, everything works fine as usual. Thanks to all. As usual, too. -a- Andrea Valle DAMS - Facoltà di Scienze della Formazione Università degli Studi di Torino [EMAIL PROTECTED] ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Gerben Wierda wrote: Correction: I goofed up; after correcting the file, I get exactly what I expected. AFAICS, index generation now works flawlessly with newtexexec! Great, wonderful, kudos to you! Um, I just noticed. "newtexexec"? Has the command name changed? Please say no. Because a command name change would mean that I have to redistribute the binaries (where the command lives) and not just the context trees in texmf. no, for the moment stick to texexec here, when i set TEXMFSTART_MODE=experimental I get newtexexec automatically; the idea is that the stub (sh sript) is as follows: === texexec = #!/bin/sh texmfstart texexec $@ in that case texmfstart will locate the right script and do what is needed; no more hassle for distributers; basically only texmfstart needs to be copied to the bin path (texmfstart.rb -> texmfstart) plus some stubs be made (i made that mechanism because of the occasional changes in the tree locations) once newtexexec becomes texexec (the perl script will be replaced) i'll come back to it, so for the moment don't worry Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Hans can give a more authoritative answer, of course, but as a provisional one: no, the command name hasn't changed, you don't need to worry. The way ConTeXt is organized is that the binary texexec (which resides in texmf/ARCH/bin/) is just a small shell-script, a stub, that calls the real script in turn. This has been texexec.pl (in texmf/scripts/context/perl/), but you can of course modify it so it runs another script. Hans has been toying with ruby lately, so we now have texmf/scripts/ruby/newtexexec.rb which, I suppose, will replace the "old" texexec in due time. But as you have seen, it's not yet quite ready for prime time, it's still missing a few features (I don't think it can post-process pdf-files yet) and has a few buglets... So relax and vatch das blinkenlight! All best Thomas On Nov 10, 2005, at 9:33 AM, Gerben Wierda wrote: Correction: I goofed up; after correcting the file, I get exactly what I expected. AFAICS, index generation now works flawlessly with newtexexec! Great, wonderful, kudos to you! Um, I just noticed. "newtexexec"? Has the command name changed? Please say no. Because a command name change would mean that I have to redistribute the binaries (where the command lives) and not just the context trees in texmf. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
Alas, I spoke too soon... I tested again with a more complex document (the book project I'm working on), and I'm having problems again: page ranges still gobble up the other entries. If I insert a \seeindex command, the index is sorted according to page numbers instead of entries. The file is probably too big to send, but I can of course send logs, .tui or whatever might be useful... Best Thomas On Nov 10, 2005, at 12:35 AM, Hans Hagen wrote: Thomas A. Schmitz wrote: Correction: I goofed up; after correcting the file, I get exactly what I expected. AFAICS, index generation now works flawlessly with newtexexec! Great, wonderful, kudos to you! I'm happy again! Thanks Hans well, thanks for testing newtexexec -) Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: Creatin metafun.mem on OSX
>> If you start i-Installer and go to the Preferences and you go to the
>> "Other" tab you can set an automatic check for updates on i-Packages
>> you have ("Check packages for updates...").
>
> Already done.
>
>> This creates a unix 'crontab' entry which is run at the time you have
>> selected (e.g. every day a 07:00). This entry runs a helper program
>> that checks the remote version of all your i-Packages and will report
>> updated i-Packages via Mail.
>
> (Fine. How does this notification happen? Does he knows my email? Or am
> I asking something stupid?)
The "crontab" tool takes care of this. You get mail as yourself on your
system.
> Another obvious thing, but just to be sure. "Using gwtex" means for me
> typesetting from inside TeXShop with standard engine default. Right?
Right (in 99.99% of the cases).
> Thanks a lot to all for the support
>
> So, know I'm waiting for updates
They are already there. Hoever, I just noticed that people talk about
"newtexexec" and that is a command and if that is indeed a new command it
will not be available after the updated ConTeXt updater install.
G
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Index
> Correction: I goofed up; after correcting the file, I get exactly > what I expected. AFAICS, index generation now works flawlessly with > newtexexec! Great, wonderful, kudos to you! Um, I just noticed. "newtexexec"? Has the command name changed? Please say no. Because a command name change would mean that I have to redistribute the binaries (where the command lives) and not just the context trees in texmf. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
