I uploaded new minimals etc. 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 -----------------------------------------------------------------
Also a new release with most of last-week's bugs fixed and last week's extensions added: http://contextgarden.net/Release_Notes#Context_2005.07.27 Cheers, Taco Hans Hagen wrote:
I uploaded new minimals etc.
On Wed, 2005-07-27 at 18:28 +0200, Hans Hagen wrote:
I uploaded new minimals etc.
Thanks!
Unfortunately, the linux64tex.zip appears to be missing the binaries. It
also looks like you also haven't updated your site to list its
existence.
[Which kinda balances out in the end, doesn't it? ;-) ]
--
Stuart Jansen
Stuart Jansen wrote:
On Wed, 2005-07-27 at 18:28 +0200, Hans Hagen wrote:
I uploaded new minimals etc.
Thanks!
Unfortunately, the linux64tex.zip appears to be missing the binaries. It also looks like you also haven't updated your site to list its existence.
i'll have a look (btw, you can use the old binaries since nothing changed in that part) 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 -----------------------------------------------------------------
I have this problem: %% test.tex %-save this with utf-8 encoding-------------- \language[it] \enableregime[utf] \newif\ifArticleError %% \def\startArticle[#1]{% \getparameters[ARTICLE][#1] \setbox101=\vbox{% \csname ARTICLEdescription\endcsname% } %% here some sorts of checking %% if there are some errors %% while expanding %% \csname ARTICLEdescription\endcsname ; %% check will change state of \ifArticleError %% \ifArticleError %% errors: %% typescript macros \ARTICLEdescription \type{description:}% \edef\T{\expandafter% \meaning\csname ARTICLEdescription\endcsname}% \aftersplitstring \T \at>\to\Temp% \expandafter\type\expandafter{\Temp}% \else %% else ok \type{OK}% \fi } %% \starttext {{\bf Hòàà}\framed{wrong framed macros}} \startArticle[description={{\bf Hoòaà}\framed{ok framed macro}}] \startArticle[description={{\bf Hoòaà}\Framed{WRONG framed macro}}] \stoptext %-------------------------------------------------------------------- where oò := {o\`o} aà := {a\`a} compile it with $>texexec --pdf --batch test.tex Problems 1. i dont't know how to make checking 2. \type does not combine well with \meaning: ò (ie {\`o} ) is not show. thanks in advance luigi
luigi.scarso wrote:
Problems
1. i dont't know how to make checking
AFAIK, there is only one way to do this: write a new tex file on- the-fly and run a separate texexec on that file (using \write18), then parse the resulting log file for the occurence of any errors. Not simple at all, I'm afraid.
2. \type does not combine well with \meaning: ò (ie {\`o} ) is not show.
This is a side-effect of TeX being an 8-bit program that doesn't understand utf-8 itself. utf-8 in ConTeXt works by virtue of the first character of a sequence having catcode 13 (\active), but \meaning never outputs any catcodes except 12 (character) and 10 (space). This can be fixed by calling \scantokens: \expanded\type{\expandafter\scantokens\expandafter{\Temp}}% Cheers, Taco
Taco Hoekwater wrote:
AFAIK, there is only one way to do this: write a new tex file on- the-fly and run a separate texexec on that file (using \write18), then parse the resulting log file for the occurence of any errors. Not simple at all, I'm afraid.
hmm, i've hundred of \startArticle..
2. \type does not combine well with \meaning: ò (ie {\`o} ) is not show.
\expanded\type{\expandafter\scantokens\expandafter{\Temp}}%
good , but type also first \expandafter after \type thanks luigi
luigi.scarso wrote:
Taco Hoekwater wrote:
AFAIK, there is only one way to do this: write a new tex file on- the-fly and run a separate texexec on that file (using \write18), then parse the resulting log file for the occurence of any errors. Not simple at all, I'm afraid.
hmm, i've hundred of \startArticle..
I'll consider the possibility of adding a new primitive to pdfetex (the language) for the discovery of run-time errors like this. That will not help you at this moment, though.
2. \type does not combine well with \meaning: ò (ie {\`o} ) is not show.
\expanded\type{\expandafter\scantokens\expandafter{\Temp}}%
good , but type also first \expandafter after \type
Sorry, the correct solution is: \expandafter\expandafter\expandafter\type \expandafter\expandafter\expandafter {\expandafter\scantokens\expandafter{\Temp}}% or, a bit shorter but needing \(un)protect: \@EA\@EA\@EA\type\@EA\@EA\@EA{\@EA\scantokens\@EA{\Temp}}% My original post only \expanded the single token \type, not the whole argument. Cheers, Taco
Taco Hoekwater wrote:
Sorry, the correct solution is:
\expandafter\expandafter\expandafter\type \expandafter\expandafter\expandafter {\expandafter\scantokens\expandafter{\Temp}}%
sounds good, thanks (I was missing some \expandafter ...) luigi
luigi.scarso wrote:
I have this problem:
i have no clue what you're tryng to do -) - provide a zipped file (so that i get the right chars) - don't use box 101 ungrouped (it's probably in use) - get the meaning with: \convertcommand\ARTICLEdescription\to\ascii\ascii 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 -----------------------------------------------------------------
participants (4)
-
Hans Hagen -
luigi.scarso -
Stuart Jansen -
Taco Hoekwater