date:20060514

nico wrote:
 
 
 Yes, strange. Looks like a grouping issue around this in page-flt:

Yes.

It works ok with

   \leavevmode {test}.

Also. The problem is the timing of \everypar, what TeX actually
executes is this:

\bgroup
\everypar {\egroup}
\par
{test}

Cheers, Taco





___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] bibdemo.tex example needs a few defs


Sanjoy Mahajan wrote:

So bibtex puts those LaTeX commands at the top of the .bbl file, and
ConTeXt doesn't know about \newcommand.  A temporary workaround is to
define those commands by hand (see below).  A better workaround is to
define \newcommand.  latex.ltx has a long and involved one, but maybe
there's a nicer ConTeXt way?


There used to be a module named bibltx that did precisely that,
but I removed it while waiting for Brook's \usemodule[latex].
I will re-instate the file, but that will take a while, so here
is the previous version ..

Cheers, taco


t-bibltx.tex
Description: TeX document
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Custom \unknownreference and \dummyreference; plus custom unknownreference in m-bib

Tobias Burnus wrote:
 Hi hans, hi Taco, hello all,
 
 I used the following in my thesis (2 years ago) to make sure I won't
 miss a unresolved reference:
 ---
 \def\unknownreference{~\clap{\blackrule[width=1.5ex,height=1.5ex,depth=0.3ex]%
   \kern-0.3ex$\blacktriangleright$}%
   \normalunknownreference}
 \def\dummyreference{$\blacksquare$}
 ---
 which produced for unresolvable references:  #myRef#  or  ##.
 
 This does not work anymore. I only get #myRef. How should one do it
 nowadays?

Do you mean you do not see the triangle?

 * * *
 
 In m-bib, actually not \unknownreference (or \dummyreference) but a
 simple '??' is used (not even bold.
 It would be great if this could be changed. (search for {??} and '
 ??\else'.)

Sure, will do that.

Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Linux: ConTeXt in local texmf-tree and Ruby scripts - HOWTO?

Peter Münster wrote:
 
 I've just seen, that there are a lot of symbolic links in the teTeX
 installation to /opt/teTeX/bin/texexec, so please forget my advice above.

Yes, you have to delele all those symlinks that teTeX provides.

If you go to the unix stubs directory in the ConTeXt distribution,
you can do :

   # for a in *; do rm -i /usr/local/teTeX/bin/i686-pc-linux-gnu/$a; done


Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] \startbackmatter requires \chapter to get bibliography?

Peter Münster wrote:
 
 \placepublications[criterium=all]
 

Yes.

 Hans and Taco, it seems that the bib module does not work with the ruby
 version of texexec. The cite command prints only .

You still have to run bibtex by hand in the new version. And perhaps
you need to regerate the bbl file  as well (I didn't think so, but if
it doesn't work ...).

The new scripts should not influence the bib module, but it could be
an other change in the latest context that is confusing your TeX.
It works fine for me, so giving advice is hard.

Cheers ,taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] New release and XeTeX - XeConTeXt

2006-05-14 Thread Otared KAVIAN

On 5/13/06, Christopher Creutzig [EMAIL PROTECTED] wrote:
Still, XeConTeXt does not work as expected in the current version:Hi Christopher,I tried the file you suggest with the latest version of ConTeXt and generated a new XeConTeXt (ConTeXt ver: 
2006.05.11 10:30 fmt: 2006.5.13, on MacOS X 10.4.6) and I didn't have any trouble with the following%% begin japanese.tex\starttext\font\Myface=Hiragino Mincho Pro W3 at 14 pt\Myface
こちらはテストです。日本語のテストです。%\bye\blankworks like a charm, and so does the ConTeXt way of defining a typeface:\definetypeface[myface][rm][Xserif][Hiragino Mincho Pro W3]\setupbodyfont[myface,14pt]
こちらはテストです。日本語のテストです。\stoptext%% end japanese.texthe japanese text is typeset identically with \Myface (defined with the good old Plain TeX way) and \myface (defined in ConTeXt way).Nevertheless still I encounter other problems with the new version of ConTeXt and I am reporting them in another thread.
Best regards: OK
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Problems with ConTeXt version 2006.05.11

2006-05-14 Thread Otared KAVIAN

Dear all,I installed the latest version of ConTeXt (that is version 2006.05.11) and although some problems have disappeared, some other are still there. Indeed I thank Hans H. and all the wizards working with him for having fixed some of the issues reported previously.
For your information, I am using Gerben Wierda's ConTeXt updater, and running MacOS X 10.4.6. I list below three problems I can observe with some of my test files:1) PostScript fonts declarations are not anymore working. For instance this
\starttext\usetypescript[palatino]\setupbodyfont[palatino,12pt]Here we are using the font \fontname\font.\blank\input knuth.tex\stoptextis typeset with lmr. The same is true with times.
2) Generating a format with XeTeX, that is creating XeConTeXt, is now possible but still MetaPost code is ignored in the resulting PDF file. For instance this\setupcolors[state=start]\starttext
\startMPcode fill fullcircle scaled 3cm withcolor red; fill fullcircle scaled 3cm shifted (2cm,1cm) withcolor transparent(1,0.5,green); \stopMPcode\stoptextworks fine in ConTeXt, but gives nothing with XeConTeXt.
3) Even though typesetting a file with ConTeXt from within TeXShop works fine, still there is the warningwarning : use 'texmfstart texexec' insteadwhich means that some day those (like me...) who have not well understood how to switch to texmfstart (and in particular how to make it work...) are going to have big problems with the next releases of ConTeXt...
Best regards: OK
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] New release and XeTeX - XeConTeXt

Christopher Creutzig wrote:
 (/usr/local/teTeX/share/texmf.local/tex/context/patterns/lang-de.pat
 ! Bad \patterns.
 \unknownchar -{
 \hbox {\vrule \!!width .5em\!!height 1ex\!!depth 
 \zeropoint }}
 l.114 .ge
  s6
 ?

  Same for me.  The problem is that in line 113, we have
 .ge5rö
 in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.

 Has anyone encountered this error? Is there a solution?
how old is your context

the latest version uses utf patterns for both pdftex and xetex so no 
special tricks are needed

Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] about texmfstart

Dalyoung wrote:
 Dear Aditya,

 I did what you told me,

 set RUBYLIB=/texmf.local/scripts/context/ruby
 export $RUBYLIB

   
i'll post a version that has all the modules/classes embedded (i.e. i 
made a ruby module that will package a script with libraries so that 
they become standalone)

Hans
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Problems with ConTeXt version 2006.05.11


Hi OK,

 1) PostScript fonts declarations are not anymore working. For instance this
 
 \starttext
 \usetypescript[palatino]

You need to specify the desired encoding on this line:

   \usetypescript[palatino][ec]

 2) Generating a format with XeTeX, that is creating XeConTeXt, is now 
 possible but still MetaPost code is ignored in the resulting PDF file. 

This is a problem in the XeTeX engine. It always uses the ^^-quoted
form on every byte value below decimal 32, which basically makes it
impossible to create a valid input file for metapost: There are no
line endings written to in the generated file, but instead there are
three-byte sequences, like ^^J or ^^M.

This is why the new linux executable has the -8bit switch. That may
be needed (or even working already) in the OsX version as well.

 3) Even though typesetting a file with ConTeXt from within TeXShop works 
 fine, still there is the warning
 
  warning : use 'texmfstart texexec' instead
 
 which means that some day those (like me...) who have not well 
 understood how to switch to texmfstart (and in particular how to make it 
 work...) are going to have big problems with the next releases of 
 ConTeXt...

The (perl) compatibility scripts will stay around for fairly long time
to come, so there is no reason to panic yet. ;-)

Cheers, taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Problems with ConTeXt version 2006.05.11

2006-05-14 Thread Otared KAVIAN

On 5/14/06, Taco Hoekwater [EMAIL PROTECTED] wrote: [...] You need to specify the desired encoding on this line:
  \usetypescript[palatino][ec]Hi Taco, Thanks for your attention.Indeed I had tried to add the encoding option, but then using either [ec] or \defaultencoding there appears a conflict with \enableregime[utf]. For instance,
\enableregime[utf]\starttext\usetypescript[palatino][ec] % or [\defaultencoding]\setupbodyfont[palatino,12pt]Here we are using the font \fontname\font.And these are some diacritics: é, ç, à, ô, î.
\blank\input knuth.tex\stoptextis typeset with Palatino, but then the diacritics are not typeset. On the other hand before the current version I used to use such settings even without specifying the encoding (that is 
\usetypescript[palatino]instead of \usetypescript[palatino][ec]). For the time being I avoid using non lmr fonts in my documents, but this indeed changes the pages I had before (however for the kind of things I do, this is not an issue...).
 2) Generating a format with XeTeX, that is creating XeConTeXt, is now
 possible but still MetaPost code is ignored in the resulting PDF file.This is a problem in the XeTeX engine. It always uses the ^^-quotedform on every byte value below decimal 32, which basically makes it
impossible to create a valid input file for metapost: There are noline endings written to in the generated file, but instead there arethree-byte sequences, like ^^J or ^^M.This is why the new linux executable has the -8bit switch. That may
be needed (or even working already) in the OsX version as well.Thanks for the insight. I understand that we have to wait for a change in XeTeX.
[...]The (perl) compatibility scripts will stay around for fairly long timeto come, so there is no reason to panic yet. ;-)Thanks for the assurance... I was only reporting a minor concern, shared by some other people on the list.
Cheers: OK
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Custom \unknownreference and \dummyreference; plus custom unknownreference in m-bib

Tobias Burnus wrote:
 
 \let\normalunknownreference\unknownreference

I deduced that :-)

 Well, I have the feeling that the whole \unknownreference does not work,
 but only the \dummyreference does.

It works for me :-/

Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Problems with ConTeXt version 2006.05.11


Hi OK (and Hans),

Otared KAVIAN wrote:
 \enableregime[utf]

 is typeset with Palatino, but then the diacritics are not typeset. On 

If you are using XeTeX, then you should not use \enableregime[utf].
If you are not useing XeTeX, then I do not understand what is going
wrong and need a minimal example + log output.

 the other hand before the current version I used to use such settings 
 even without specifying the encoding (that is
 \usetypescript[palatino]
 instead of \usetypescript[palatino][ec]). For the time being I avoid 

For Hans: could \usetypescript default to the of use \defaultencoding
(i.e. ec)?

Cheers, Taco
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] New release and XeTeX - XeConTeXt

2006-05-14 Thread Christopher Creutzig

Hans Hagen wrote:

  Same for me.  The problem is that in line 113, we have
 .ge5rö
 in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.

 how old is your context

  Indeed, that was stone age: 2006.05.08 12:59 - more than five days 
old.  :-)

 the latest version uses utf patterns for both pdftex and xetex so no 
 special tricks are needed

  Thanks for the pointer.  Strangely enough, I still can't typeset 
simple Japanese, but right now I don't have the time to investigate this 
further.


Best regards,
Christopher
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] \startbackmatter requires \chapter to get bibliography?

  \placepublications
 
 \placepublications[criterium=all]

Should I update the bibdemo.tex on the wiki to use criterium=all?  Or
is that example okay since \placepublications is not after
\startbackmatter?  (If so, I don't understand how \startbackmatter
changes it.)

-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] brace error after a \placefigure

From:Hans Hagen [EMAIL PROTECTED]
 \def\dodocomplexplacefloat[#1][#2][#3]#4%
 [magic code snipped]
 may work better

Tested and working here, thanks!

-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] \startbackmatter requires \chapter to get bibliography?

2006-05-14 Thread Peter Münster

On Sun, 14 May 2006, Taco Hoekwater wrote:

 Peter Münster wrote:
  
  Hans and Taco, it seems that the bib module does not work with the ruby
  version of texexec. The cite command prints only .
 
 It works fine for me, so giving advice is hard.

Hello Taco,
I've retried with the ruby-version and now it works for me too, I really
don't know what error I've made this morning...
So excuse me please for the noise!
Cheers, Peter

-- 
http://pmrb.free.fr/contact/
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] project files searched for using TEXINPUTS

In experimenting with projects, products, and components, I was tracing
file searches (using Linux, teTeX 3.0 and kpathsea).

From the cont-eni.pdf manual (p. 26 of the PDF file), explaining more
about components and project structure:

 Many TEX implementations look for a file in all directories and
 subdirectories when a requested file is not in the current
 directory. This is not only time--consuming but may lead to errors when
 the wrong file (a file with the same name) is loaded.

 For this reason ConTEXt works somewhat differently. A file that is not
 available on the working directory is searched for on the parent
 directories.

I agree with this reasoning.  But as implemented, if the current and
parent directories fail, ConTeXT will look in the TEXINPUTS search path.
Is that the intended behavior when looking for project files?  Probably
not ideal for the project file, though maybe it is useful for the
resulting environment file?

For finding figures, the behavior is clear: look in the local (.) and
then the global directories, and that's it.

For finding files specified by \input, the behavior is also clear (use
TEXINPUTS).

So I wondered whether the intention for finding project files was also
equally clear: look in . and in (grand)parent directories (I've
increased the number of levels to three).

Here's the test.tex file I used:

\startcomponent blah
\product null
\project abcd
\stopcomponent

$ texexec -passon=-kpathsea-debug 32 --once test  log
$ grep abcd log | grep kpse_find
kdebug:kpse_find_file: searching for ./abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../../../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ./abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for ../../../abcd of type tex (from TEXINPUTS 
environment variable)
kdebug:kpse_find_file: searching for abcd of type tex (from TEXINPUTS 
environment variable)

The last search, for 'abcd', runs through the entire TEXINPUTS path.
The other searches have directories specified, so they will look only in
those directories.

-Sanjoy

`A society of sheep must in time beget a government of wolves.'
   - Bertrand de Jouvenal
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] Problems with ConTeXt version 2006.05.11

Otared KAVIAN wrote:
 Hi Taco and Hans,


 On 14 mai 2006, at 15:40, Taco Hoekwater wrote:
 
  Hi OK (and Hans),
 
  [...]
  If you are using XeTeX, then you should not use \enableregime[utf].
  If you are not useing XeTeX, then I do not understand what is going
  wrong and need a minimal example + log output.
 

 Indeed the problem I am reporting concerns the use of \enableregime
 [utf] and \usetypescript in ConTeXt. I am attaching a minimal example
 together with the auxiliary files created during the typesetting with
 ConTeXt.
 If this can be of any help, I noticed that when using the palatino
 font, some ligatures disappear as well (like fi in first).
the next version will ignore utf regimes in xetex 

Hans 

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-

___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] New release and XeTeX - XeConTeXt

Christopher Creutzig wrote:
 Hans Hagen wrote:

   
  Same for me.  The problem is that in line 113, we have
 .ge5r�
 in Latin-1 encoding, but XeTeX tries reading the file in UTF-8.
   

   
 how old is your context
 

   Indeed, that was stone age: 2006.05.08 12:59 - more than five days 
 old.  :-)
   
for xetex indeed, but if we proceed in the way we do now, we will have 
reasoable stable xetex support soon 

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] mailing lists

Hans Hagen wrote:
 Hoi,

 We hebben het er niet meer over gehad .. de mailinglijst

 - afscherming (is nu ok denk ik)
 - archief (is er wel maar misschien niet wat we willen)
 - leden van de bestuurslijst

 Wat betreft het laatste, ik heb er geen bezwaar tegen als er op de 
 bestuurslijst ook mensen staan waarvan we als bestuur vinden dat ze 
 kunnen/mogen meedenken. (bv frans)
   
sorry, wrong list 

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] Optional Arguments for cite

From:Thomas A. Schmitz [EMAIL PROTECTED]
 but have a look at section 3.2 of the bibtex manual:
 \cite[extras={page~4}][key]

Just what I needed too, thanks.

But should it be 

  \cite[extras={, page~4}][key]

Otherwise I get, e.g. (Aamport, 1986bpage 4) as the reference.
(using t-bib.tex 2006.04.11).

-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] Bib-module: crossreferences