[NTG-context] paragraph with a shape
How do I shape a paragraph like a mouth? Get your email and more, right on the new Yahoo.com ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] ConTeXt on Debian: The wiki entry
Hi everybody, this mail has a double purpose. At the end, there's a call for testers of a new (planned) Debian ConTeXt package that would be updated more frequently than now (at least in unstable and testing), where ConTeXt is tied to teTeX's or TeXlive's release cycles. But first, I'd like to talk about http://wiki.contextgarden.net/Debian_installation Are some of the people around who wrote this? I found some information in it misleading and in part just wrong (this has already been pointed out two weaks ago by plink), and have started to edit the page to change the parts that give us, the Debian TeX maintaines, most headache. But in the lower part, Steps to finish a first context upgrade, I felt lost. If these steps are really needed, then there's something seriously wrong in Debian's (and probably upstream's) packaging of ConTeXt. Therefore I didn't just change the text to reflect how I think it should work. Instead, we should try to figure out together whether it in fact does not work as it should, and then fix the Debian packages (hopefully still possible for etch). So the specific question I have are: - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? Finally, here comes Norbert Preining's Call for Testers: Dear all! We = Debian TeX maintainers searching for users of the Debian Operating Systems which are also using ConTeXt. Currently Debian etch (testing) and sid (unstable) contains packages for TeX live 2005. But this contains a bit old ConTeXt version, so users are asking us to update ConTeXt. We have prepared a updated ConTeXt package for Debian, based on the latest released version (2006.08.08), and would ask you to help use testing, as we are not experienced in ConTeXt type settings. I checked some simple documents from the ConTeXt Garden, and they worked, but more detailed testing would be nice. If you have interest, please contact us at [EMAIL PROTECTED] or, if you have a bit experience, you can straight away add deb http://www.tug.org/texlive/Debian/ context/ to your /etc/apt/sources.list file and install context. After this, please tell us our experiences/failures/suggestions. Thanks a lot and all the best Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] paragraph with a shape
Hi Victoria, At first, draw a mouth-like shape as a closed path with metapost then read http://www.pragma-ade.com/general/manuals/metafun-s.pdf (pages 399--424). The ML is a good source too (See "[NTG-context] Context and CD labels" for example)... Renaud Victoria Brown a crit: How do I shape a paragraph like a mouth? Get your email and more, right on the new Yahoo.com ___ 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] ConTeXt on Debian: The wiki entry
Hi Frank, A ConTeXt's package for debian will be great ! Frank Küster a écrit : Hi everybody, this mail has a double purpose. At the end, there's a call for testers of a new (planned) Debian ConTeXt package that would be updated more frequently than now (at least in unstable and testing), where ConTeXt is tied to teTeX's or TeXlive's release cycles. But first, I'd like to talk about http://wiki.contextgarden.net/Debian_installation Are some of the people around who wrote this? I found some information in it misleading and in part just wrong (this has already been pointed out two weaks ago by plink), and have started to edit the page to change the parts that give us, the Debian TeX maintaines, most headache. But in the lower part, Steps to finish a first context upgrade, I felt lost. If these steps are really needed, then there's something seriously wrong in Debian's (and probably upstream's) packaging of ConTeXt. Therefore I didn't just change the text to reflect how I think it should work. Instead, we should try to figure out together whether it in fact does not work as it should, and then fix the Debian packages (hopefully still possible for etch). My contributions was to copy Install a Metapost update and Install a pdfTeX update from tetex 3.0 Install to Debian Install... From my pov, ConTeXt is really great because of the reactivity of the devs. As a consequence, new astonishing features are often added... but there is a price: update often to the latest realease + install the latest metapost and the latest pdfTeX (moreover, here I need the latest beta of pdfTeX). IMHO, it will be nice if the deb provides debian's specifics + interactiv cont-tmf.zip download + install according debian specifics... but there will be dependencies problems... Maybe a full standalone context is the solution (with metapost, pdfTeX and all the binaries we need coexisting with the tetex's one) ? Dunno... Last point, it could be nice to have beta packages for ConTeXt an m-bib (separated)... So the specific question I have are: - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. It's the way ConTeXt does... ConTeXt's gurus have surely good reasons so I let them answer... - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? idem Finally, here comes Norbert Preining's Call for Testers: Dear all! We = Debian TeX maintainers searching for users of the Debian Operating Systems which are also using ConTeXt. Currently Debian etch (testing) and sid (unstable) contains packages for TeX live 2005. But this contains a bit old ConTeXt version, so users are asking us to update ConTeXt. We have prepared a updated ConTeXt package for Debian, based on the latest released version (2006.08.08), and would ask you to help use testing, as we are not experienced in ConTeXt type settings. I checked some simple documents from the ConTeXt Garden, and they worked, but more detailed testing would be nice. If you have interest, please contact us at [EMAIL PROTECTED] or, if you have a bit experience, you can straight away add deb http://www.tug.org/texlive/Debian/ context/ to your /etc/apt/sources.list file and install context. After this, please tell us our experiences/failures/suggestions. Thanks a lot and all the best OK, thanks, I'll do it as soon as I have a little more time (after my PhD defense... ;) ) Regards, Frank Renaud ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Hi Frank, Frank Küster wrote: Are some of the people around who wrote this? I found some information I do not use Debian and did not write that page, but I can answer your questions partially, at least. - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. Yes, it is. ConTeXt does not support only pdfetex, but all major engines, like XeTeX and Aleph. I have formats in: $TEXMF/web2c/aleph/ $TEXMF/web2c/luatex/ $TEXMF/web2c/pdfetex/ $TEXMF/web2c/xetex/ - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? It is almost certainly better to ignore/block fmtutil and use texexec instead. Properly setting up a ConTeXt update is not necesarily limited to format generation only. Greetings, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Hardcoded options in the Ruby scripts
Hello Hans,I'm still wondering why there are certain formats hardcoded in your scripts and how the "make all formats" feature does (not work).See scripts/ruby/base/tex.rb:Lines 131-137:Here are a few languages predefined which texexec "knows". If I want to add a format for another language, I have to add a new line here.Line 339: Here are the "default" TeX formats defined. No problem to consider something as default ;-), but the point is that "texexec --make --all" actually does "make all DEFAULT formats", NOT "make all AVAILABLE formats". :-(Anyway, the main problem I see is altering of a script which comes with the ConTeXt distribution - the changes made into this scripts must be done again and again after each update.My suggestion is:1. To put the format definition into a separate file (like user.rb or so) which won't be owerwritten in any case. [Note: cont-usr.tex is a good analogy to this]2. "Make all" should make ALL the defined ConTeXt formats, not the default ones.Thanks,Richard___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Hardcoded options in the Ruby scripts
Richard Gabriel wrote: Lines 131-137: Here are a few languages predefined which texexec knows. If I want to add a format for another language, I have to add a new line here. such as ...? (adding a user inferface is more that adding something to texexec) Line 339: Here are the default TeX formats defined. No problem to consider something as default ;-), but the point is that texexec --make --all actually does make all DEFAULT formats, NOT make all AVAILABLE formats. :-( which would be quite a lot -) what do you mean with all? Anyway, the main problem I see is altering of a script which comes with the ConTeXt distribution - the changes made into this scripts must be done again and again after each update. My suggestion is: 1. To put the format definition into a separate file (like user.rb or so) which won't be owerwritten in any case. [Note: cont-usr.tex is a good analogy to this] hm, must think about it ; i don't like too many dependencies 2. Make all should make ALL the defined ConTeXt formats, not the default ones. --all means: all patterns 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
[NTG-context] German hyphenation broken ?
Hi,
could someone please have a look at the minimal example below:
On my system it seems that the old germ hyphenation doesn't work
anymore.
Line 7 and line 9 are for sure hyphenated according to the new rules
Einbu-ßen and Sy-stem
Do others experience the same or is only my installation broken?
Steffen
(pdfeTeX, Version 3.141592-1.30.4-2.2, ConTeXt ver: 2006.10.13 20:06)
\usetypescript[postscript][\defaultencoding]
\setupencoding[default=texnansi]
\mainlanguage[deo]
\enableregime[mac]
\newdimen\Vertikal
\Vertikal=12pt
\setupbodyfont[postscript,10pt] \setupinterlinespace[line=12pt]
\definepapersize[Test][width=15.7cm,height=23.2cm]
\setuppapersize[Test][A4]
\setuplayout
[width=113mm,height=48\Vertikal,
backspace=20mm,topspace=15mm,
header=\Vertikal,headerdistance=0.5\Vertikal,
footer=3\Vertikal,footerdistance=0pt,
location=middle,marking=on,grid=no]
\starttext
\quad \index{Rentenversicherung– Zukunft der \~}Im Hinblick auf den
Umbau von Sozialversicherungssystemen hat das
Bundesverfassungsgericht allerdings einem künftigen Reformgesetzgeber
insoweit das Feld bereitet, als es angemerkt hat, daß das
westdeutsche (nunmehr gesamtdeutsche) gesetzliche
Rentenversicherungssystem von der Möglichkeit einer Umgestaltung
nicht so ausgenommen ist\footnote{Test}. Diese Tatsache ist nicht
neu; die bisher vorhandene Finanzkraft der Sozialversicherung hat die
Frage nur nicht aktuell werden lassen. Selbst wenn also ein
tiefgreifender Umbau verbunden mit Einbußen in der Rechtssubstanz von
Ansprüchen stattfinden würde, könnte man sich nur schwer auf eine
Präzendenzwirkung des Urteils zur rentenrechtlichen
Systementscheidung je berufen\footnote{Test}; die Akzeptanz einer
entsprechenden Reform mag dadurch vielleicht steigen, da die
politischen Akteure argumentieren können, so etwas ähnliches habe es
schon einmal gegeben.
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] German hyphenation broken ?
On Oct 23, 2006, at 3:25 PM, Steffen Wolfrum wrote: On my system it seems that the old germ hyphenation doesn't work anymore. Line 7 and line 9 are for sure hyphenated according to the new rules Einbu-ßen and Sy-stem Do others experience the same or is only my installation broken? I get this from \hyphenatedword: Ein-bu-ßen Sy-ste-ment-schei-dung The first is correct (Duden 1986 R 179: ß bezeichnet einen Laut und wird nicht getrennt). The second should be Sy-stem-ent-schei-dung, but this is probably one of the many weird exceptions of German that TeX can't handle. What did you expect? (When I switch to language [de], I get Sys-te-ment-schei-dung). Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Directories of pictures
Hans Hagen wrote: � wrote: With your previous example, I would have to place my pictures in current_dir/scr/images. I would like to put my pictures in tex_file_dir/scr/images, and have Context to find them no matter which directory I'm in when I execute texexec. Also, I would like to use relative paths, not absolute paths. ./src/images you can see what happens with \traceexternalfigurestrue \traceexternalfigurestrue just says it's checking '.', but it doesn't say if '.' is current shell directory or tex file directory. Maurício ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Taco Hoekwater [EMAIL PROTECTED] wrote: Hi Frank, Frank Küster wrote: Are some of the people around who wrote this? I found some information I do not use Debian and did not write that page, but I can answer your questions partially, at least. Thank you - yes, this helps. - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. Yes, it is. ConTeXt does not support only pdfetex, but all major engines, like XeTeX and Aleph. I have formats in: $TEXMF/web2c/aleph/ $TEXMF/web2c/luatex/ $TEXMF/web2c/pdfetex/ $TEXMF/web2c/xetex/ Ah, okay, that's clear. Has this already been this way one year ago when texlive2005 was released? Do you know whether the TeXlive developers are aware of that? - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? It is almost certainly better to ignore/block fmtutil and use texexec instead. Properly setting up a ConTeXt update is not necesarily limited to format generation only. Hm. What are the other things that need to be done? This is in fact an issue that affects not only Debian, but TeXlive and probably most TeX distributions. They currently assume that after an update of some files and/or executables, it's sufficient to run mktexlsr (possibly more than once), updmap(-sys) and fmtutil(-sys) --all. If this is not sufficient for ConTeXt, there are two possibilities: - fix fmtutil and updmap so that they do the right thing for ConTeXt - or implement a way to automate calling texexec. This would include using some configuration file, since not everybody who has aleph or xetex installed also wants a context format for this engine. To me, as a TeXlive and teTeX guy, it seems preferrable to choose option 1 and fix the existing distribution scripts. However, I don't know yet what else is needed when ConTeXt is updated, therefore I might be wrong, and switching to texexec might actually be better. But then this should be done consistently, and fmtutil should drop context handling completely (or just call texexec). Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Directories of pictures
Mari Voipio wrote:
On Fri, 20 Oct 2006, Jörg Hagmann wrote:
Use:
\setupexternalfigures[directory={path_to_your_figures,another_path}]
And you can even use relative paths and go 'down' in the directory tree:
\setupexternalfigures[directory={../pdf-images,../png-images}]
See also: http://wiki.contextgarden.net/Using_Graphics
Do you think it's possible to say something like:
\setupexternalfigures[directory={tex_file_directory/png-images}] ?
Note that ./png-images seems to look for
current_shell_directory/png-images.
Best,
Maurício
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Updating on Windows
Hello all! Quick question here because the Wiki is silent on this. When I want to (manually) update my ConTeXt windows (stand-alone) installation, do I only need the following two files: cont-tmf.zip cont-win.zip Or is there more? I know ScITE is supposed to have an Update ConTeXT option but I don't use this editor anymore. I found a nifty one called PSPad with a better interface (in my opinion -- and it also supports Unicode, so yay!) and it supports TeX very well. I had a lot of fun using its integrated Lorem ipsum generator when testing stuff. :-) Jeff ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Updating on Windows
Jeff Smith wrote: Hello all! Quick question here because the Wiki is silent on this. When I want to (manually) update my ConTeXt windows (stand-alone) installation, do I only need the following two files: cont-tmf.zip cont-win.zip Or is there more? ctxtools --update 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] ConTeXt on Debian: The wiki entry
Frank Küster wrote: - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. Yes, it is. ConTeXt does not support only pdfetex, but all major engines, like XeTeX and Aleph. I have formats in: $TEXMF/web2c/aleph/ $TEXMF/web2c/luatex/ $TEXMF/web2c/pdfetex/ $TEXMF/web2c/xetex/ Ah, okay, that's clear. Has this already been this way one year ago when texlive2005 was released? Do you know whether the TeXlive developers are aware of that? Yes, it was, Yes, 'they' were aware, and no, 'they' did not want to fix fmtutil. 'They' only dropped the separate format extensions and then decided that implementing a replacement was too much effort. - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? It is almost certainly better to ignore/block fmtutil and use texexec instead. Properly setting up a ConTeXt update is not necesarily limited to format generation only. Hm. What are the other things that need to be done? Nothing at the moment, AFAIK. But potentially lots of things. For instance: the next version of context will support non-kpathsea file searching, so it will have to initialize its database somewhere. It may want to/have to delete obsolete files and/or merge local configuration files with new released version. Or precompile patterns files or lua scripts, strip and optimize source files, and perhaps generate font metrics in one format or another. ConTeXt comes with its own font map files, so there is no real reason to fix updmap but if you want to the main problem is this: you have to extend it so that it does not treat dvips and pdftex map files as identical. To me, as a TeXlive and teTeX guy, it seems preferrable to choose option 1 and fix the existing distribution scripts. However, I don't know yet what else is needed when ConTeXt is updated, therefore I might be wrong, and switching to texexec might actually be better. But then this should be done consistently, and fmtutil should drop context handling completely (or just call texexec). I am very much in favor of using texexec for everything related to ConTeXt. Greetings, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Problems with MetaFun and registers
I have problems with the register macro in MetaFun.
When I try
==
\setupcolors[state=start]
\starttext
\definelayer[test]
\startuseMPgraphic{oeps}
path p ; p := fullcircle scaled 6cm ;
fill p withcolor .8white ;
draw p withpen pencircle scaled 1mm withcolor .625red ;
register (somepos-1,0cm,0cm,center currentpicture) ;
\stopuseMPgraphic
\setMPlayer [test] [somepos-1] [location=c]
{Does it work all right?}
\getMPlayer [test]{\useMPgraphic{oeps}}
\stoptext
==
(which is essentially copied from the manual) in ConTeXt live I get the
following error message
==
! Illegal unit of measure (pt inserted).
to be read again
-
\pospxywhd ...fnum \positionanchormode =\plusone -
\MPx \pageanchor \fi
\rela...
l.7 ...hd{somepos-1}{0}{5687206}{5687206}{0}{0}{0}
?
! Emergency stop.
to be read again
-
\pospxywhd ...fnum \positionanchormode =\plusone -
\MPx \pageanchor \fi
\rela...
l.7 ...hd{somepos-1}{0}{5687206}{5687206}{0}{0}{0}
No pages of output.
==
Am I doing something wrong or is the register functionality broken in
ConTeXt 2006.10.13?
/Fredrik
Teknisk projektledare
Ph.D. Complex Systems
AcobiaFLUX AB
[EMAIL PROTECTED]
Tel: +46 (0) 31 722 48 11
Fax: +46 (0) 31 722 48 01
Mob: +46 (0) 733 27 92 41
www.acobiaflux.se
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Updating on Windows
On 10/23/06, Hans Hagen [EMAIL PROTECTED] wrote: ctxtools --update Heh, too easy. Thanks. :-) Jeff Smith ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Taco Hoekwater [EMAIL PROTECTED] wrote: To me, as a TeXlive and teTeX guy, it seems preferrable to choose option 1 and fix the existing distribution scripts. However, I don't know yet what else is needed when ConTeXt is updated, therefore I might be wrong, and switching to texexec might actually be better. But then this should be done consistently, and fmtutil should drop context handling completely (or just call texexec). I am very much in favor of using texexec for everything related to ConTeXt. Can you point me to the place where it is documented which calls are needed to be called - when ConTeXt is updated - when any of the engines is updated? I don't use ConTeXt myself, and I always have problems finding the relevant places in the documentation, sorry... Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] resource libraries
Hallo! Is it possible somehow to extract all the images covered in an image database without lose of quality? Wolfgang Werners-Lucchini ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
http://wiki.contextgarden.net/Debian_installation Are some of the people around who wrote this? I wrote some of it (hangs head in shame) by typing in all the steps I had to use on my Debian stable/testing system to get a newer ConTeXt to work with tetex 3.0 as the basis. I agree, it is confusing and I hope it can be improved. In the previous discussion, the issue came up of whether ConTeXt should be installed per user or for the whole system. The Debian_installation instructions on the wiki are for a per-user install, because I couldn't figure out a robust way of having an easily updatable installation that goes in TEXMFLOCAL. A system-wide installation, if done cleanly, would be much easier (as plink pointed out). If you (or 'texexec --make' to generate the formats) ask kpathsea where to put the format files, it'll give you a directory in TEXMFHOME, so a per user install. But how do you ask kpathsea the correct question so that it'll tell you where they should go for a system-wide install? -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] resource libraries
Wolfgang Werners-Lucchini wrote: Hallo! Is it possible somehow to extract all the images covered in an image database without lose of quality? eh ... normally there should beno loss at all, pdftex just copies the resources 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] Directories of pictures
Maurício wrote:
Hans Hagen wrote:
� wrote:
With your previous example, I would have to place my pictures in
current_dir/scr/images. I would like to put my pictures in
tex_file_dir/scr/images, and have Context to find them no matter which
directory I'm in when I execute texexec. Also, I would like to use
relative paths, not absolute paths.
./src/images
you can see what happens with
\traceexternalfigurestrue
\traceexternalfigurestrue just says it's checking '.', but it doesn't
say if '.' is current shell directory or tex file directory.
tex cannot expand a path so we cannot determine that;
directory={.,default}
is also an option since default will make context lookj in tex related paths
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] ConTeXt on Debian: The wiki entry
Sanjoy Mahajan wrote: A system-wide installation, if done cleanly, would be much easier (as plink pointed out). If you (or 'texexec --make' to generate the formats) ask kpathsea where to put the format files, it'll give you a directory in TEXMFHOME, so a per user install. But how do you ask kpathsea the correct question so that it'll tell you where they should go for a system-wide install? you can't and i remember asking for such a feature but ... ; the only way to figure that out is to check all format paths and take the first one that fits; unfortunalty the tetex paths are rather messy so it's hard to predict in what permutation of home, usr, share, sys, opt * local * tex, TeX, teTeX, whatever * texmf, texmflocal, texmf-local, texmf-teTeX, texmf-dis, texmf.local, texmf-whocares * web2c, web2c/engine etc etc a format may end up; this is further complicated by the fact that kpse has to do some guessing about where it's configuration files are (web2c, etc, home, nowhere), what trees make sense, etc etc; and, yes, some of the paths are hard coded in the binaries, so relocating is tricky ... isn't it magic that tex still runs -) but luatex will make thinsg better (we hope) 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
[NTG-context] typesetting a url from variabless
Hi,
What is the best way of typesetting a url from a variable. For
example, if I have
\setvariables[test][website=http://www.xyz.com/~abc/first_index.html]
how can I print the url. I tried
\starttext
\goto{\getvariable{test}{website}}[URL(\getvariable{test}{website})]
\stoptext
but this does not seem to work. Any suggestions?
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Hans Hagen [EMAIL PROTECTED] wrote:
Sanjoy Mahajan wrote:
A system-wide installation, if done cleanly, would be much easier
(as plink pointed out). If you (or 'texexec --make' to generate the
formats) ask kpathsea where to put the format files, it'll give you
a directory in TEXMFHOME, so a per user install. But how do you ask
kpathsea the correct question so that it'll tell you where they
should go for a system-wide install?
you can't and i remember asking for such a feature but ... ;
Can you point me to this discussion? I think it doesn't need more as
what fmtutil-sys, updmap-sys and texconfig-sys do before calling
fmtutil, updmap or texconfig, respectively:
v=`kpsewhich -var-value TEXMFSYSVAR`
c=`kpsewhich -var-value TEXMFSYSCONFIG`
TEXMFVAR=$v
TEXMFCONFIG=$c
export TEXMFVAR TEXMFCONFIG
exec updmap ${1+$@}
However, it would be probably more elegant and context-like to not have
texexec and texexec-sys, but rather a commandline switch - in this case
the handling would have to be done in the perl (or ruby?) scripts, which
is somewhat trickier.
the only
way to figure that out is to check all format paths and take the first
one that fits; unfortunalty the tetex paths are rather messy so it's
hard to predict in what permutation of home, usr, share, sys, opt *
local * tex, TeX, teTeX, whatever * texmf, texmflocal, texmf-local,
texmf-teTeX, texmf-dis, texmf.local, texmf-whocares * web2c,
web2c/engine etc etc a format may end up;
I'm not sure what you mean. The default TEXMF path for teTeX (and I
think also for TeXlive) is
TEXMF =
{!!$TEXMFCONFIG,!!$TEXMFVAR,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFMAIN,!!$TEXMFLOCAL,!!$TEXMFDIST}
where the first three are per-user, the others are system trees. An
explanation about installing does not need to know whether, for example,
TEXMFLOCAL is called texmf.local or texmf-local or
/usr/local/share/texmf. The only problem might be that some users
change the order or the trees, but that's not a big problem if we
suggest to use the default path.
this is further complicated
by the fact that kpse has to do some guessing about where it's
configuration files are (web2c, etc, home, nowhere),
This is only a problem if people have more than one texmf.cnf - is this
actually the case? I don't think I ever heard of that.
what trees make
sense, etc etc; and, yes, some of the paths are hard coded in the
binaries, so relocating is tricky ... isn't it magic that tex still
runs -)
AFAIK only the search path for texmf.cnf is hard-coded, and that can't
be avoided. On the other hand, no one ever approached me and requested
a relocation: What would you want, and in which cases?
TIA, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
