- ntg-context - Mailing Lists

Re: [NTG-context] Context Minimal for Windows installer
by Mojca Miklavec 18 Nov '07

18 Nov '07

On 11/18/07, Vyatcheslav Yatskovsky wrote: > Hello Mojca, > > Thank you for svn account. Where do you think I should place my installer? I'll drop you a note on a privite mail. > > A wishlist for Vyatcheslav (although I cannot test): > > - it would be nice if the installer would first ask the user for the > > location of minimals > > It's easy, I'll start with it. Thanks. > > - then, you need to download (or include in the zip) the rsync > > binaries and put them into PATH, that path might be a separate one > > (distinct from ConTeXt bin in any case) > > Now rsync is bundled with installer. (I think it changes rarely, so if it will, I'll better update the installer.) if user selects default folder (c:\contextminimal), he gets the following structure: > > Directory of C:\contextminimal > > 11.11.2007 04:36 <DIR> mswin > 31.01.2007 11:33 1 873 811 cygwin1.dll > 07.11.2006 09:26 283 136 rsync.exe > 30.05.2006 16:18 118 784 SetEnv.exe > 18.11.2007 01:12 691 481 unins000.exe > 18.11.2007 01:12 6 452 unins000.dat > > So, installer-related binaries are located in root installations folder, while Contexts sits in mswin subfolder. OK, rsync should come with it, and true: it doesn't change so often. > > - can you please take a look into > > http://minimals.contextgarden.net/setup/mswin/ and try to reproduce > > the behaviour of first-setup.bat. You might need some binaries already > > present, but it would be nice to get rid of the need for > > http://minimals.contextgarden.net/minimals/ (even though I will > > probably keep providing them) - so, it would be nice if you could call > > mtx-update instead of syncing the whole folder > > - if you use mtx-update.lua, you can ask the user to select the > > desired engines,, the desired modules (probably not implemented yet), > > and the user is also able to choose ConTeXt distribution (to roll back > > if the latest one causes problems), and choose wheather to clean old > > files or not; the functionality provided in mtx-update might improve > > and/or change, but it might be a good idea to keep you informed, it's > > only that the minimals are still in development phase, so they're not > > quite stable yet and paths might still change > > Hmm.. I never used mtx-update, and, moreover, my experiments with mixing installer scripts with lua scripts failed so far (I cound't make format files from it). Can you try it once more? http://minimals.contextgarden.net/setup/mswin/ is really minimalistic,so you can probably figure out what's going on (or ask in case you have problems) and try to reproduce it (you can first call rsync to fetch the needed binaries and scripts, and then call mtx-update properly). mtx-update should now be able to create formats when called with "--make" (depending on the engins you select to download). > If mtx-update is so powerful, let it be the base of your installer, but I'd rather keep my simple and "pop", satisfying needs of non-advanced users (like me). It might not be *so powerful* yet, but it would then be equivalent with the "plain way" of setting things up, and it would be easier for you later to add a checkbox into your installer if some functionality in mtx-update is extended. > BTW, InnoSetup allows to write very flexible scripts using build-in Pascal, so I can always duplicate most needed functionality on it, and I will be 100% confident that it will work on 100% of machines. :) I believe that. But mtx-update should work on all machines as well (if it doesn't, it should better be fixed). But it would really make sense not to depend on precompiled "full minimals" since you loose most control of what should be included and what not. If you > Rsyncing the whole folder will not be necessary when I implement selection of "components". Then the user can select what to download and what to not (fonts, etc.) I'd be very thankful if you point me out some obvious components that user might exclude from set up. > > > - it would be nice to have "enable minimals/disable minimals" switch, > > so that one can theoretically run MikTeX in parallel (when the > > distribution is enabled, it shadows MikTeX, when it's disabled, MikTeX > > will run normally) > > Yeah, but know very well that making Contest work in global way requires not only enabling its settings, but disabling MikTeX settings... OK, I didn't know that. What exactly do you need to do (which MikTeX components/settings do you need to disable) if you want to enable "minimal ConTeXt"? > So it would be troublesome, and I believe that person having both packages should better use conventional installer, like yours. But in that case any "comfortable windows user" would still be greatuf for an "installer", even if its sole reason is to ask the user for the destination of the distribution, and to download the necessary files. So, everything can remain the same, but you don't need to set eny environmental variables, you only create a batch file called "enablecontext.bat" or similar somewhere in PATH (or in some place that you place into PATH), with the contens: C:\Programs\context\setuptex.bat C:\Programs\context depending on where the user decided to install ConTeXt. So, when someone is in console and types in enablecontext, the environment will be set up properly. That was the approach I've been using when working on windows. (When I think about it, setuptex could (or should?) be adapted in such a way that one wouldn't need to provide any arguments to it, but that's a completely unrelated subject.) Some *really low priority* tasks for the future of the installer might also be: - check if ruby is installed and ask the user to install it if needed (well, Hans is planning to rewrite most of his ruby scripts to lua, so that miht not even be necessary :) - check if perl is installed and ask the user to install it if needed - [for me] once the rest is done, I would like to reproduce "mswincontext.zip" (add the missing bits and pieces to the repository), but that's also lower priority than the rest > > - you might need to provide alternative servers in the future/ask the > > user which server to choose for downloading (in case of too much > > traffic, another server could possibly mirror the contents from the > > garden) > > Sure. Just point me them. Well ... only as a remainder for the future :) According to Patrick we didn't reach the bandwidth limit yet :) > P.S. If you cannot run the installer, you may found useful see my screenshots attached. Great! Thanks a lot for it. It really looks proffessional. There's only a slightly misleading information (you need at least 2.9 MB space :) :) :) :) (Miktex -> MikTeX, Context -> ConTeXt) Thanks a lot for the great job :) Such an installed has been waited for for wuite some time :) Mojca

1 0

some warnings about fonts
by Vyatcheslav Yatskovsky 18 Nov '07

18 Nov '07

Hello, While luatex was compiling fonts, I noticed some warnings. I suspect they are harmless, but I'd better report them. ... report >> fontnames: identifying system font files with suffix ttf report >> fontnames: 101 system files identified, 370 hash entries added, runtime 0.812 seconds report >> fontnames: identifying system font files with suffix ttc report >> fontnames: 0 system files identified, 0 hash entries added, runtime 0.063000000000002 seconds report >> fontnames: identifying system font files with suffix afm report >> fontnames: 0 system files identified, 0 hash entries added, runtime 0.061999999999998 seconds report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Bad call to gww_iconv_open, neither arg is UCS4 (Sjis->UTF-8) report >> load otf: warning: Glyph 2 is called ".notdef", a singularly inept choice of name (only glyph 0 may be called .notdef) FontForge will rename it. ... Best, Vyatcheslav

4 3

little coding assistance (please)
by Steffen Wolfrum 18 Nov '07

18 Nov '07

Hi, I need some help for shorten the TeX code in the following example: My footnotes are defined like this: \def\setnotebodyfont {\let\setnotebodyfont\relax \restoreglobalbodyfont \switchtobodyfont[rm,9pt]\setupinterlinespace[line=9.8pt] \parskip2pt} But sometimes at single pages I need to shrink footnote's setupinterlinespace and parskip a bit. To adjust the percentage of shrinking (setupinterlinespace[line= \dimexpr(9.8\MyFaktor)]\parskip\dimexpr(2\MyFaktor)}) I use the following: \newdimen\MyFaktor \MyFaktor=0.978pt [Normal body-text ...] \def\setnotebodyfont {\let\setnotebodyfont\relax \restoreglobalbodyfont \switchtobodyfont[rm,9pt]\setupinterlinespace[line=\dimexpr(9.8 \MyFaktor)]\parskip\dimexpr(2\MyFaktor)} [...] Text with footnotes [...] \def\setnotebodyfont {\let\setnotebodyfont\relax \restoreglobalbodyfont \switchtobodyfont[rm,9pt]\setupinterlinespace[line=9.8pt] \parskip2pt} [...] This works great, but looks ugly and not clear at all!! Could someone please provide me a definition like \ThightNotes[0.978] and \NormalNotes that I could hook handy and clear in the respective body-text? Thanks in advance, Steffen

2 3

Re: [NTG-context] Context Minimal for Windows installer
by Vyatcheslav Yatskovsky 18 Nov '07

18 Nov '07

Hello Idris, > Congratulations! Thanks. > What files exactly are downloaded? just mswincontext.zip? Downloaded are all files from http://minimals.contextgarden.net/minimals/mswin They are current beta, I think. > What are the installation options? There is only one option so far -- to do rsync or not to do it. This option must be On for the first time, since you have no files yet; it also be used to update Context by running the installer again. It may be Off if you just want to update environment vars. > It would be a good idea to add pdftex and xetex formats options as well. The installer doesn't make format files itself. (It might be good idea, but I stuck with difficulties here). After setup, the installer prompts the user to build format files manually. User is free to use any engine; I only tested it for Luatex, as the most progressive one. And a thing I must notice -- sorry, it cannot be installed along with Miktex or TeXLive, because environment vars will clash. It's inevitable; if you want to use them in parallel, use Context in old way. This installer is for clean machines only. But there is good news also. Uninstall is possible :) > Thanks for the wonderful contribution Thanks again. -- Best regards, Vyatcheslav Yatskovsky

1 0

Context Minimal for Windows installer (cont)
by Vyatcheslav Yatskovsky 18 Nov '07

18 Nov '07

BTW, I can share sources as well. Waiting only for what community says. And, can it be hosted as alternative installer at minimals.contextgarden.net? Vyatcheslav

1 0

context installer
by Vyatcheslav Yatskovsky 17 Nov '07

17 Nov '07

Hello, This is what happens when I run new context-setup-mswin installer: " G:\rsync\context-setup-mswin\context>first-setup.bat Should I create the cache path \Documents and Settings\Fine? [yes|no] [no] y Error in lua file loading: G:\rsync\context-setup-mswin\context\bin\mtxrun.lua:5 971: attempt to call field 'mkdirs' (a nil value) When you want to use context, you need to initialize the tree with: G:\rsync\context-setup-mswin\context\tex\setuptex.bat G:\rsync\context-setup-m swin\context\tex You can associate this command with a shortcut to the cmd prompt. " Best regards, Vyatcheslav

3 3

rsync command
by Vyatcheslav Yatskovsky 17 Nov '07

17 Nov '07

Hello, I found that the suggested rsync command for Windows leads nowhere. rsync -rvzctl rsync://contextgarden.net/minimals/minimals/win tex We have only mswin and windows folders inside minimals. Best regards, Vyatcheslav

1 0

-, -- and --- in Context
by Maurício 15 Nov '07

15 Nov '07

Hi, TeX fonts have the known convention for -, -- and ---. How would be the proper way to get those characters in Context? Should I use Unicode characters? I know that, at least in my instalation, -- and --- work as in TeX, but I would like to know if Context has a different standard way to do that. Thanks, Maurício

2 1

MetaPost 1.001 announcement
by Taco Hoekwater 14 Nov '07

14 Nov '07

The MetaPost team is happy to announce a new release of MetaPost: ---------------------------------------------------------------------- MetaPost 1.001 ---------------------------------------------------------------------- The sources and a win32 package can be downloaded immediately from https://foudnry.supelec.fr/projects/metapost/ The source package should compile normally on all systems that are capable of compiling a modern web2c-based TeX distribution. The win32 package is intended for texlive or a similar web2c-based installation, and has been tested only with TeXLive 2007. These executables will *not* work for miktex, sorry. Of course, we welcome any comments (either good or bad) that you may have. Simply replying to this message is fine, but see the bottom of the message for a more formal way to report bugs and feature requests. ---------------------------------------------------------------------- What is new in version 1.001: ---------------------------------------------------------------------- * The default cmyk 'black' color now uses only black, not all four ink colors (after a discussion on the mailing list). * Some issues were reported with the new turningnumber algorithm, all known problems are now fixed. * Gábor Braun discovered that mpost did not always download the font encodings into all the created output files. * Akira Kakuto and Hartmut Henkel found some small issues in mpto regarding trailing and leading whitespace. * A fix for the 'Helvetica' entries in trfonts.map was provided by Werner Lemberg, and Michail Vidiassov supplied two extra font entries for troff.map (Symbol and ZapfDingbats). Karl Berry provided the new file troff-updmap.map, to be used by the updmap tool in texlive. * Mpost now supports web2c's --output-directory option. * Any warnings about missing fonts and characters are now always written to the terminal as well as to the log. * Now that makempx is a C program, it needed a different install line in build.sh. Also, Olaf Mersmann contributed a patch to recognize 'gmake' in build.sh * Luigi Scarso found some typing errors in the web source that prevented clean weaving of the source. * Stephan Hennig fixed a number of problems in the manual (mpman.tex) and the introduction paper (mpintro.tex). He also wrote new sections on how to preview metapost graphics and on how to use metapost graphics inside other documents. On top of that, the manual is now hypertext-aware, and fixes for a whole series of small problems have been applied. ---------------------------------------------------------------------- Legal notice / license / bug reports ---------------------------------------------------------------------- MetaPost is a system for producing graphics developed by John Hobby at AT&T, based on Donald Knuth's Metafont. The MetaPost home page is http://tug.org/metapost. MetaPost and related programs are in the public domain. The MetaPost development project is currently hosted at Supelec, https://foundry.supelec.fr/projects/metapost; please report bugs and request enhancements through there if possible. Alternatively, you can reach us through the <metapost(a)tug.org> mailing list as well. Have fun! Taco Hoekwater, for the MetaPost team, November 14, 2007

4 4

\quotation
by Idris Samawi Hamid 14 Nov '07

14 Nov '07

Dear gang, This has bugged me for years but I never said anything since the workaround is so easy. OTOH I am working on something I'd like to share with others and an official solution would be better: \starttext \input knuth \startquotation \input knuth \stopquotation \input knuth \stoptext I. \start-\stopquotation surrounds the block quote in double-quotes marks. I don't know about other European languages but in English this is redundant; I've hardly ever seen block quotes use dbl-quote marks. We at least need a setup option to turn this off. II. There should be some default whitespace between the block quote and the surrounding text, just as \start-stopitemize has. Or at least this should be configurable in the setups. If these two are already there (not in the manual) then please let us know how to set this up. Otherwise could you add configuration options for this? FYI: Here is what I use =========== \definestartstop [quote] [before={\startnarrower[2*left,2*right]\blank[big]\noindenting}, after={\stopnarrower\blank[big]}] =========== Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

4 11