Re: [NTG-context] luatools --find-file cont-en.lua
On Sat, 15 Mar 2008, Peter Münster wrote: Hello, What is "luatools --find-file" supposed to find? It finds files like context.tex but no lua files like l-table.lua or cont-en.lua. "texmfstart --locate" finds also the lua files. Same behaviour here. Aditya___ 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] luatools --find-file cont-en.lua
Hello, What is "luatools --find-file" supposed to find? It finds files like context.tex but no lua files like l-table.lua or cont-en.lua. "texmfstart --locate" finds also the lua files. Greetings, Peter -- http://pmrb.free.fr/contact/ ___ 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] Strange format error with xetex engi ne on debian?sid
Le Saturday 15 March 2008 19:26:06 Peter Münster, vous avez écrit : > On Sat, Mar 15 2008, Morgan Brassel wrote: > > get the following error: > > > > kpathsea: Running mktextfm lmromanslant10-regular > > mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; > > nonstopmode; input lmromanslant10-regular > > This is METAFONT, Version 2.71828 (Web2C 7.5.6) > > > > kpathsea: Running mktexmf lmromanslant10-regular > > ! I can't find file `lmromanslant10-regular'. > > <*> ...; nonstopmode; input lmromanslant10-regular > > Hello Morgan, > > I don't know much about fonts, but I think, the latest ConTeXt requires > also the latest lm-fonts, since some file-names changed some months ago. > > Cheers, Peter You're right, lots of names have changed since previous version. I've sent a mail to this debian bug (#469437): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469437 Both lmodern and texlive-xetex need to be updated. Cheers, Morgan ___ 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] Strange format error with xetex engine on debian?sid
On Sat, Mar 15 2008, Morgan Brassel wrote: > get the following error: > > kpathsea: Running mktextfm lmromanslant10-regular > mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; > input lmromanslant10-regular > This is METAFONT, Version 2.71828 (Web2C 7.5.6) > > kpathsea: Running mktexmf lmromanslant10-regular > ! I can't find file `lmromanslant10-regular'. > <*> ...; nonstopmode; input lmromanslant10-regular Hello Morgan, I don't know much about fonts, but I think, the latest ConTeXt requires also the latest lm-fonts, since some file-names changed some months ago. Cheers, Peter -- http://pmrb.free.fr/contact/ ___ 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] "Missing" ligatures, smallcaps, etc.
Found it, and problem resolved. Sorry for the noise. David On Mar 15, 2008, at 10:05 AM, David Wooten wrote: > Thanks for the response, Mojca. > > I installed a few adobe opentype fonts some years back, using the > TeXFont script. The file a_zqd2tu.enc (referenced in the map files) is > not found in my tex trees (nor in a Google search). There's a decent > chance it could be found in a backup from that time, I'll see what I > can do about that. It's likely that that is the issue? > > Following is the font definition [1] and the map file [2]. > > Best, David > > [1] > > \loadmapfile [texnansi-LIGA-KERN-LNUM-TNUM-SMCP-adobe- > minionpro.map] > \loadmapfile > [texnansi-LIGA-KERN-ONUM-PNUM-adobe-minionpro.map] > > \starttypescript [serif] [MinionPro] [texnansi] > \definefontsynonym[SerifCaption][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-Capt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifText][texnansi-LIGA-KERN-ONUM-PNUM-MinionPro- > Regular][encoding=texnansi,handling=minionpro-hz] > \definefontsynonym[SerifSubhead][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-Subh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifDisplay][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-Disp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifItalicCaption][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-ItCapt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifItalicText][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-It][encoding=texnansi,handling=minionpro-hz] > \definefontsynonym[SerifItalicSubhead][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-ItSubh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifItalicDisplay][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-ItDisp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldCaption][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-BoldCapt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldText][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-Bold][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldSubhead][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-BoldSubh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldDisplay][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-BoldDisp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldItalicCaption][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-BoldItCapt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldItalicText][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-BoldIt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldItalicSubhead][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-BoldItSubh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifBoldItalicDisplay][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-BoldItDisp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldCaption][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-SemiboldCapt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldText][texnansi-LIGA-KERN-ONUM-PNUM- > MinionPro-Semibold][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldSubhead][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-SemiboldSubh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldDisplay][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-SemiboldDisp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldItalicCaption][texnansi-LIGA-KERN- > ONUM-PNUM-MinionPro-SemiboldItCapt] > [encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldItalicText][texnansi-LIGA-KERN-ONUM- > PNUM-MinionPro-SemiboldIt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldItalicSubhead][texnansi-LIGA-KERN- > ONUM-PNUM-MinionPro-SemiboldItSubh] > [encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifSemiboldItalicDisplay][texnansi-LIGA-KERN- > ONUM-PNUM-MinionPro-SemiboldItDisp] > [encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsCaption][texnansi-LIGA-KERN-LNUM-TNUM- > SMCP-MinionPro-Capt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsText][texnansi-LIGA-KERN-LNUM-TNUM-SMCP- > MinionPro-Regular][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsSubhead][texnansi-LIGA-KERN-LNUM-TNUM- > SMCP-MinionPro-Subh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsDisplay][texnansi-LIGA-KERN-LNUM-TNUM- > SMCP-MinionPro-Disp][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsItalicCaption][texnansi-LIGA-KERN-LNUM- > TNUM-SMCP-MinionPro-ItCapt][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsItalicText][texnansi-LIGA-KERN-LNUM-TNUM- > SMCP-MinionPro-It][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsItalicSubhead][texnansi-LIGA-KERN-LNUM- > TNUM-SMCP-MinionPro-ItSubh][encoding=texnansi,handling=minionpro] > \definefontsynonym[SerifCapsItalicDisplay][texnansi-LIGA-KE
Re: [NTG-context] "Missing" ligatures, smallcaps, etc.
Thanks for the response, Mojca. I installed a few adobe opentype fonts some years back, using the TeXFont script. The file a_zqd2tu.enc (referenced in the map files) is not found in my tex trees (nor in a Google search). There's a decent chance it could be found in a backup from that time, I'll see what I can do about that. It's likely that that is the issue? Following is the font definition [1] and the map file [2]. Best, David [1] \loadmapfile [texnansi-LIGA-KERN-LNUM-TNUM-SMCP-adobe-minionpro.map] \loadmapfile [texnansi-LIGA-KERN-ONUM-PNUM-adobe-minionpro.map] \starttypescript [serif] [MinionPro] [texnansi] \definefontsynonym[SerifCaption][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-Capt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifText][texnansi-LIGA-KERN-ONUM-PNUM-MinionPro- Regular][encoding=texnansi,handling=minionpro-hz] \definefontsynonym[SerifSubhead][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-Subh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifDisplay][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-Disp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifItalicCaption][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-ItCapt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifItalicText][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-It][encoding=texnansi,handling=minionpro-hz] \definefontsynonym[SerifItalicSubhead][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-ItSubh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifItalicDisplay][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-ItDisp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldCaption][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-BoldCapt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldText][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-Bold][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldSubhead][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-BoldSubh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldDisplay][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-BoldDisp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldItalicCaption][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-BoldItCapt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldItalicText][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-BoldIt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldItalicSubhead][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-BoldItSubh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifBoldItalicDisplay][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-BoldItDisp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldCaption][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-SemiboldCapt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldText][texnansi-LIGA-KERN-ONUM-PNUM- MinionPro-Semibold][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldSubhead][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-SemiboldSubh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldDisplay][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-SemiboldDisp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldItalicCaption][texnansi-LIGA-KERN- ONUM-PNUM-MinionPro-SemiboldItCapt] [encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldItalicText][texnansi-LIGA-KERN-ONUM- PNUM-MinionPro-SemiboldIt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldItalicSubhead][texnansi-LIGA-KERN- ONUM-PNUM-MinionPro-SemiboldItSubh] [encoding=texnansi,handling=minionpro] \definefontsynonym[SerifSemiboldItalicDisplay][texnansi-LIGA-KERN- ONUM-PNUM-MinionPro-SemiboldItDisp] [encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsCaption][texnansi-LIGA-KERN-LNUM-TNUM- SMCP-MinionPro-Capt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsText][texnansi-LIGA-KERN-LNUM-TNUM-SMCP- MinionPro-Regular][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsSubhead][texnansi-LIGA-KERN-LNUM-TNUM- SMCP-MinionPro-Subh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsDisplay][texnansi-LIGA-KERN-LNUM-TNUM- SMCP-MinionPro-Disp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsItalicCaption][texnansi-LIGA-KERN-LNUM- TNUM-SMCP-MinionPro-ItCapt][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsItalicText][texnansi-LIGA-KERN-LNUM-TNUM- SMCP-MinionPro-It][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsItalicSubhead][texnansi-LIGA-KERN-LNUM- TNUM-SMCP-MinionPro-ItSubh][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsItalicDisplay][texnansi-LIGA-KERN-LNUM- TNUM-SMCP-MinionPro-ItDisp][encoding=texnansi,handling=minionpro] \definefontsynonym[SerifCapsBoldCaption][texnansi-LIGA-KERN-LNUM- TNUM-SMCP-MinionPro-BoldCapt][encoding=texnansi,handling
[NTG-context] Incompatibility bib num style / reference prefix option
Hi,
I think I discovered a bug in the 'num' alternative of the bib module. It
seems to be incompatible with the prefix=+ option of referencing. The
following example gives an unknow reference:
% tex file
\usemodule[bib]
\setupbibtex[database=biblio]
\setuppublications[alternative=num]
\setuphead[chapter][prefix=+] % OK if commented
\starttext
\chapter[chap:one]{One} % OK if commented
Text \cite[test] text.
\completepublications
\stoptext
% bib file biblio.bib
@BOOK{test,
title = {T},
publisher = {P},
year = {Y},
author = {A}
}
By the way, the 'num' alternative also gives an unknow reference when
\completepublications is not present, while the default alternative is OK. Is
there a particular reason for this? Thanks.
Greetings,
Morgan
___
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] Strange format error with xetex engi ne on debian sid
Le Saturday 15 March 2008 17:01:41 Peter Münster, vous avez écrit : > On Sat, Mar 15 2008, Morgan Brassel wrote: > > I'm experiencing problems with the xetex engine on debian sid. I'm using > > the official packages context and texlive-xetex. Maybe one of you has the > > same setup and has a hint... When I try to compile a simple "hello > > world!" document, I get the following message: > > > > This is XeTeXk, Version 3.141592-2.2-0.996-patch1 (Web2C 7.5.6) > > %&-line parsing enabled. > > ---! /var/lib/texmf/web2c/pdftex/cont-en.fmt was written by pdftex > > (Fatal format file error; I'm stymied) > > Hello, > > If there is no xetex-format, then I get a similar error. > > So, first generate the xetex format: > texexec --make --all --xetex > > Then, check where the format has been written (perhaps > /var/lib/texmf/web2c/xetex/cont-en.fmt). > > Update the lsr-database: > mktexlsr > > Check, if at least kpsewhich finds the format: > kpsewhich -engine xetex cont-en.fmt > > It should find the same file, that you've just generated before. > > Then, you should be able to compile "Hello world!". > > Cheers, Peter Thanks, Peter. Yes the xetex format is missing whereas the pdftex one is present. I guess something is missing in the postinstall script of the context deb package. Unfortunately, I don't really know how to check it. Anyway, I ran texexec to build the format. As root, it is written to /etc/texmf/web2c/xetex/cont-en.fmt which is not very coherent with the location of the pdftex format. kpsewhich finds the format, but I'm stiil unable to compile Hello world. I now get the following error: kpathsea: Running mktextfm lmromanslant10-regular mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input lmromanslant10-regular This is METAFONT, Version 2.71828 (Web2C 7.5.6) kpathsea: Running mktexmf lmromanslant10-regular ! I can't find file `lmromanslant10-regular'. <*> ...; nonstopmode; input lmromanslant10-regular Please type another input file name ! Emergency stop. <*> ...; nonstopmode; input lmromanslant10-regular Maybe I should write a debian bug report. This problem hasn't been declared yet. But I'm not sure how to do that! Morgan ___ 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] Strange format error with xetex engine on debian sid
On Sat, Mar 15 2008, Morgan Brassel wrote: > > I'm experiencing problems with the xetex engine on debian sid. I'm using the > official packages context and texlive-xetex. Maybe one of you has the same > setup and has a hint... When I try to compile a simple "hello world!" > document, I get the following message: > > This is XeTeXk, Version 3.141592-2.2-0.996-patch1 (Web2C 7.5.6) > %&-line parsing enabled. > ---! /var/lib/texmf/web2c/pdftex/cont-en.fmt was written by pdftex > (Fatal format file error; I'm stymied) Hello, If there is no xetex-format, then I get a similar error. So, first generate the xetex format: texexec --make --all --xetex Then, check where the format has been written (perhaps /var/lib/texmf/web2c/xetex/cont-en.fmt). Update the lsr-database: mktexlsr Check, if at least kpsewhich finds the format: kpsewhich -engine xetex cont-en.fmt It should find the same file, that you've just generated before. Then, you should be able to compile "Hello world!". Cheers, Peter -- http://pmrb.free.fr/contact/ ___ 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] Strange format error with xetex engine on debian sid
Hi everyone, I'm experiencing problems with the xetex engine on debian sid. I'm using the official packages context and texlive-xetex. Maybe one of you has the same setup and has a hint... When I try to compile a simple "hello world!" document, I get the following message: This is XeTeXk, Version 3.141592-2.2-0.996-patch1 (Web2C 7.5.6) %&-line parsing enabled. ---! /var/lib/texmf/web2c/pdftex/cont-en.fmt was written by pdftex (Fatal format file error; I'm stymied) I didn't change anything to the setup made by official packages. Is there a problem with one of them? Best regards, Morgan ___ 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] References and formulae numbers in upshape
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wolfgang Schuster skrev:
>> Good to have more pals from sweden!
>>
>> Thanks for the answer, actually it was not what I meant.
>> I already use \mainlanguage[sv], but how do you customize so it appears
>> like: Bild 1 , Bild 2, .. or whatever 1 whatever 2 . or maybe
>
> \setuplabeltext[sv][figure=Bild ]
>
>> if you want to referencing to subfigures like whatever 1a whatever 1b ?
>
> \placefigure[here][fig:dummy]
> {\startcombination[2*1]
> {\externalfigure[dummy]}{a}
> {\externalfigure[dummy]}{b}
>\stopcombination}
>
> See \in{figure}{a}[fig:dummy] and \in{figure}{b}[fig:dummy].
>
> Greetings
> Wolfgang
>
> ___
> 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
> ___
>
Just Great!
Many thanks, it is good to to have you around!
Janneman - Örebro - Sweden
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH2+go/zRis+sQPvARAgszAKDEanNAprgNVuj49C4432GlBEMgIACg4qp7
aKqRPDNCxystR4CtZpnXH10=
=Im34
-END PGP SIGNATURE-
___
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] References and formulae numbers in upshape
> Good to have more pals from sweden!
>
> Thanks for the answer, actually it was not what I meant.
> I already use \mainlanguage[sv], but how do you customize so it appears
> like: Bild 1 , Bild 2, .. or whatever 1 whatever 2 . or maybe
\setuplabeltext[sv][figure=Bild ]
> if you want to referencing to subfigures like whatever 1a whatever 1b ?
\placefigure[here][fig:dummy]
{\startcombination[2*1]
{\externalfigure[dummy]}{a}
{\externalfigure[dummy]}{b}
\stopcombination}
See \in{figure}{a}[fig:dummy] and \in{figure}{b}[fig:dummy].
Greetings
Wolfgang
___
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] mplib
On Sat, Mar 15, 2008 at 11:18 AM, Hans Hagen wrote: > > Mojca Miklavec wrote: > > On Fri, Mar 14, 2008 at 6:51 PM, Aditya Mahajan wrote: > >> On Fri, 14 Mar 2008, Hans Hagen wrote: > >> > >> > so, if you have specific wishes ... now is the time to let them know > >> > >> Some questions (and hidden wishes) > >> > >> Does this mean that text between metapost graphic and context can be > >> really transparent? Currently \sometxt does not work with all macros, > >> (like an old feature request by Mojca to have two optional arguments for > >> setting the font in the gnuplot module). Will mplib mean that the > metapost > >> code can place any tex box at the desired location? > > > > Now that you mention it: I still need to adapt the gnuplot module to > > mkiv, but I'm a bit afraid of asking for help. (The most important > > thing would be to get rid of that stupid catcode trickery inside > > \startGNUPLOTscript ... \stopGNUPLOTscript that always tends to fail > > when one needs it, and to have one-to-one conversion, so that %,#, $, > > will have no special meaning.) Then, it would probably be a nice > > benchmark to discover bugs in the library :) > > > > For example, demos from this page (I'm not saying that they're too > > useful since 100x100 is too low resolution anyway): > > http://gnuplot.sourceforge.net/demo_4.3/pm3d.html > > currently all fail because of the "out-of-memory" problem (10.000 > > times "fill unitsquare scaled ... shifted ... withcolor ..."), but > > this might be a ConTeXt problem as well (the text inside > > \startMPgraphic ... \stopMPgraphic probably needs to be stored > > somewhere in TeX, even if there's no need for that). > > let's discuss this a few months from now when i have more code in place > > btw, how difficult would it be to add a lua api to gnuplot, in which > case we could communicate via lua tables Peter Hedwig has already done some work on it: http://peter.affenbande.org/gnuplot/ What his patch does: one calls gnuplot normally, and then, when you say set term lua dashed fontsize 15 "dashed fontsize 15" is parsed by lua. Then, gnuplot does its work, and calls functions: set_linestyle(3) set_color(...) draw_line(...) What Peter did was a mapping from C to lua, so the actual code that does "draw_line" is actually implemented in lua and can easily be changed and/or adapted without recompiling gnuplot. He now "converts" those function calls into TikZ Code, but that could easily be adapted into anything. So: output has already been implemented (and would "only" need to be adapted), while input might need some tweaking. I'm sometimes using a rather simple C++ library which opens gnuplot and pipes "set terminal ...", "plot ..." commands to gnuplot, so one can pass a C table to gnuplot. I could take a look at how it's done there. How do you imagine passing lua tables to gnuplot? Mojca PS: no need to say that even though his terminal is much more popular (it's the only decent LaTeX terminal I know) than the one for ConTeXt, I have seen zero discussion on the gnuplot mailing list about any intentions to integrate that code into gnuplot core. ___ 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] mplib
Mojca Miklavec wrote: > On Fri, Mar 14, 2008 at 6:51 PM, Aditya Mahajan wrote: >> On Fri, 14 Mar 2008, Hans Hagen wrote: >> >> > so, if you have specific wishes ... now is the time to let them know >> >> Some questions (and hidden wishes) >> >> Does this mean that text between metapost graphic and context can be >> really transparent? Currently \sometxt does not work with all macros, >> (like an old feature request by Mojca to have two optional arguments for >> setting the font in the gnuplot module). Will mplib mean that the metapost >> code can place any tex box at the desired location? > > Now that you mention it: I still need to adapt the gnuplot module to > mkiv, but I'm a bit afraid of asking for help. (The most important > thing would be to get rid of that stupid catcode trickery inside > \startGNUPLOTscript ... \stopGNUPLOTscript that always tends to fail > when one needs it, and to have one-to-one conversion, so that %,#, $, > will have no special meaning.) Then, it would probably be a nice > benchmark to discover bugs in the library :) > > For example, demos from this page (I'm not saying that they're too > useful since 100x100 is too low resolution anyway): > http://gnuplot.sourceforge.net/demo_4.3/pm3d.html > currently all fail because of the "out-of-memory" problem (10.000 > times "fill unitsquare scaled ... shifted ... withcolor ..."), but > this might be a ConTeXt problem as well (the text inside > \startMPgraphic ... \stopMPgraphic probably needs to be stored > somewhere in TeX, even if there's no need for that). let's discuss this a few months from now when i have more code in place btw, how difficult would it be to add a lua api to gnuplot, in which case we could communicate via lua tables 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 - ___ 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] References and formulae numbers in upshape
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johan Sandblom skrev:
> I believe the easy way is
>
> \mainlanguage{sv]
>
> which also has lots of other useful side effects.
>
> Johan, also from Sweden
>
> 2008/3/15, Jan-Erik Hägglöf <[EMAIL PROTECTED]>:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Wolfgang Schuster skrev:
>>
>>> On Fri, 14 Mar 2008 22:30:30 +0100
>> > Morgan Brassel <[EMAIL PROTECTED]> wrote:
>> >
>> >> Le Friday 14 March 2008 09:00:49 Wolfgang Schuster, vous avez écrit :
>> >>> What do you want seems to be not possible but you could use the
>> >>> following solution although it is better to define a new command.
>> >>>
>> >>> \let\normalin\in
>> >>>
>> >>> \definereferenceformat
>> >>> [figref]
>> >>> [left=\normal,
>> >>>text=\normal Figure,
>> >>>command=\normalin]
>> >>>
>> >>> \let\in\figref
>> >>>
>> >>> \starttext
>> >>>
>> >>> \placefigure
>> >>> [here][fig:det]
>> >>> {Example}
>> >>> {\blackrule[width=3cm,height=3cm]}
>> >>>
>> >>> \it See \in[fig:det] for details.
>> >>>
>> >>> \stoptext
>> >
>> >> Thank you for your help, Wolfgang! I think I'll define a new \ref command
>> >> similar to the one in LaTeX, with upshape number. But maybe a new option
>> >> would be welcome? (just as for numberstyle=normal in \setupformulae).
>> What do
>> >> you think? Is it a bad idea? I'm just curious...
>> >
>> > A new command to set the style for the number is OK but you need also
>> > one for the text but this need to be done by Hans because it is not
>> > possible to change the style for the predefined command in, at ... with
>> > the current implementation.
>> >
>> > Wolfgang
>> >
>> ___
>> > 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
>> >
>> ___
>> >
>>
>> Hi!
>>
>> As a new Context user (former LateX) from Sweden according to the above
>> discussion about references style to figures. I have a following
>> question. How do I customize the appearance of the figure text, I mean
>> for example:
>> Under every figure there is : Figure 1, Figure 2, Figure 3 and so on.
>> How do I make it like this : Picture 1, Picture 2, Picture 3 or
>> Picture 1a .1band such.?
>> In the swedish translation there is "Figur 1..."
>> I understand that it has to do with defining my own kind of \definefloat
>> or similar.
>>
>> Best Regards
>>
>> Janneman
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.6 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iD8DBQFH24Yr/zRis+sQPvARAltuAKCRX8yebwmD1hUvOrO0lToDea+RowCgp1/E
>> QuGKQMpRfcnoMSU0lXkVE28=
>> =wSRD
>> -END PGP SIGNATURE-
>>
>> ___
>> 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
>>
>> ___
>>
>
>
Good to have more pals from sweden!
Thanks for the answer, actually it was not what I meant.
I already use \mainlanguage[sv], but how do you customize so it appears
like: Bild 1 , Bild 2, .. or whatever 1 whatever 2 . or maybe
if you want to referencing to subfigures like whatever 1a whatever 1b ?
Thanks in Advance
Best Regards
Janneman -- Örebro - sweden
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH25Kb/zRis+sQPvARApFAAKC+TUUkQObvJwQQPvkjNP86tCH3CgCgjRZI
mcVAhziSRr0JkjOU2otjqT4=
=Eo0R
-END PGP SIGNATURE-
___
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] References and formulae numbers in upshape
I believe the easy way is
\mainlanguage{sv]
which also has lots of other useful side effects.
Johan, also from Sweden
2008/3/15, Jan-Erik Hägglöf <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wolfgang Schuster skrev:
>
> > On Fri, 14 Mar 2008 22:30:30 +0100
> > Morgan Brassel <[EMAIL PROTECTED]> wrote:
> >
> >> Le Friday 14 March 2008 09:00:49 Wolfgang Schuster, vous avez écrit :
> >>> What do you want seems to be not possible but you could use the
> >>> following solution although it is better to define a new command.
> >>>
> >>> \let\normalin\in
> >>>
> >>> \definereferenceformat
> >>> [figref]
> >>> [left=\normal,
> >>>text=\normal Figure,
> >>>command=\normalin]
> >>>
> >>> \let\in\figref
> >>>
> >>> \starttext
> >>>
> >>> \placefigure
> >>> [here][fig:det]
> >>> {Example}
> >>> {\blackrule[width=3cm,height=3cm]}
> >>>
> >>> \it See \in[fig:det] for details.
> >>>
> >>> \stoptext
> >
> >> Thank you for your help, Wolfgang! I think I'll define a new \ref command
> >> similar to the one in LaTeX, with upshape number. But maybe a new option
> >> would be welcome? (just as for numberstyle=normal in \setupformulae).
> What do
> >> you think? Is it a bad idea? I'm just curious...
> >
> > A new command to set the style for the number is OK but you need also
> > one for the text but this need to be done by Hans because it is not
> > possible to change the style for the predefined command in, at ... with
> > the current implementation.
> >
> > Wolfgang
> >
> ___
> > 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
> >
> ___
> >
>
> Hi!
>
> As a new Context user (former LateX) from Sweden according to the above
> discussion about references style to figures. I have a following
> question. How do I customize the appearance of the figure text, I mean
> for example:
> Under every figure there is : Figure 1, Figure 2, Figure 3 and so on.
> How do I make it like this : Picture 1, Picture 2, Picture 3 or
> Picture 1a .1band such.?
> In the swedish translation there is "Figur 1..."
> I understand that it has to do with defining my own kind of \definefloat
> or similar.
>
> Best Regards
>
> Janneman
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFH24Yr/zRis+sQPvARAltuAKCRX8yebwmD1hUvOrO0lToDea+RowCgp1/E
> QuGKQMpRfcnoMSU0lXkVE28=
> =wSRD
> -END PGP SIGNATURE-
>
> ___
> 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
>
> ___
>
--
Johan Sandblom, MD PhD
m +46735521477 Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
___
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] References and formulae numbers in upshape
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wolfgang Schuster skrev:
> On Fri, 14 Mar 2008 22:30:30 +0100
> Morgan Brassel <[EMAIL PROTECTED]> wrote:
>
>> Le Friday 14 March 2008 09:00:49 Wolfgang Schuster, vous avez écrit :
>>> What do you want seems to be not possible but you could use the
>>> following solution although it is better to define a new command.
>>>
>>> \let\normalin\in
>>>
>>> \definereferenceformat
>>> [figref]
>>> [left=\normal,
>>>text=\normal Figure,
>>>command=\normalin]
>>>
>>> \let\in\figref
>>>
>>> \starttext
>>>
>>> \placefigure
>>> [here][fig:det]
>>> {Example}
>>> {\blackrule[width=3cm,height=3cm]}
>>>
>>> \it See \in[fig:det] for details.
>>>
>>> \stoptext
>
>> Thank you for your help, Wolfgang! I think I'll define a new \ref command
>> similar to the one in LaTeX, with upshape number. But maybe a new option
>> would be welcome? (just as for numberstyle=normal in \setupformulae). What
>> do
>> you think? Is it a bad idea? I'm just curious...
>
> A new command to set the style for the number is OK but you need also
> one for the text but this need to be done by Hans because it is not
> possible to change the style for the predefined command in, at ... with
> the current implementation.
>
> Wolfgang
> ___
> 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
> ___
>
Hi!
As a new Context user (former LateX) from Sweden according to the above
discussion about references style to figures. I have a following
question. How do I customize the appearance of the figure text, I mean
for example:
Under every figure there is : Figure 1, Figure 2, Figure 3 and so on.
How do I make it like this : Picture 1, Picture 2, Picture 3 or
Picture 1a .1band such.?
In the swedish translation there is "Figur 1..."
I understand that it has to do with defining my own kind of \definefloat
or similar.
Best Regards
Janneman
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH24Yr/zRis+sQPvARAltuAKCRX8yebwmD1hUvOrO0lToDea+RowCgp1/E
QuGKQMpRfcnoMSU0lXkVE28=
=wSRD
-END PGP SIGNATURE-
___
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] References and formulae numbers in upshape
On Fri, 14 Mar 2008 22:30:30 +0100
Morgan Brassel <[EMAIL PROTECTED]> wrote:
> Le Friday 14 March 2008 09:00:49 Wolfgang Schuster, vous avez écrit :
> > What do you want seems to be not possible but you could use the
> > following solution although it is better to define a new command.
> >
> > \let\normalin\in
> >
> > \definereferenceformat
> > [figref]
> > [left=\normal,
> >text=\normal Figure,
> >command=\normalin]
> >
> > \let\in\figref
> >
> > \starttext
> >
> > \placefigure
> > [here][fig:det]
> > {Example}
> > {\blackrule[width=3cm,height=3cm]}
> >
> > \it See \in[fig:det] for details.
> >
> > \stoptext
> Thank you for your help, Wolfgang! I think I'll define a new \ref command
> similar to the one in LaTeX, with upshape number. But maybe a new option
> would be welcome? (just as for numberstyle=normal in \setupformulae). What do
> you think? Is it a bad idea? I'm just curious...
A new command to set the style for the number is OK but you need also
one for the text but this need to be done by Hans because it is not
possible to change the style for the predefined command in, at ... with
the current implementation.
Wolfgang
___
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] mplib
Aditya Mahajan wrote: >Will mplib mean that the metapost > code can place any tex box at the desired location? Yes. The aim is to have that supported in the next luatex beta. Best wishes, Taco ___ 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 ___
