Re: [NTG-context] bug in beta: extra \else
Hans Hagen wrote:
> Aditya Mahajan wrote:
>> On Mon, 16 Oct 2006, Aditya Mahajan wrote:
>>
>>> On Sun, 15 Oct 2006, Vit Zyka wrote:
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. [snip]
2. Accented characters inside \typebuffer are type set as
\dochar {225}
>>> This seems to be a bug. In utf-8 encoding, if an accented character is
>>> the first character of a buffer, it gets typed correctly. All other
>>> accented charaters come out as \dochar {225}. \getbuffer works fine.
>> I forgot to attach the test file. I am attaching it, hoping that the
>> encoding will come out correctly.
>>
>>> Can TeX choose the input encoding while writing files? If not, there
>>> may be really no robust way to solve this problem.
>>>
>>> Aditya
>
> in core-buf we need to treat the upper half of the vector:
>
>\recatcodeuppercharacterstrue % <---
>\setcatcodetable\vrbcatcodes
>
> in startbuffer
It also works well. Thank you
Vit
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Hans Hagen wrote:
> Vit Zyka wrote:
>> Hans Hagen wrote:
>>> Wolfgang Schuster wrote:
On Fri, 13 Oct 2006 19:16:58 -0400 (EDT)
Aditya Mahajan <[EMAIL PROTECTED]> wrote:
> On Fri, 13 Oct 2006, Vit Zyka wrote:
>
>
>> Hans Hagen wrote:
>>
>>> Vit Zyka wrote:
>>>
Hans Hagen wrote:
> Vit Zyka wrote:
>
>> Hi all,
>>
>> there is some deep bug that was discovered translating
>> Beginners manual. Let take single chapter e.g.
>> ma-cb-cz-alignments.tex
>>
>> With today beta I got .log attached (error ! Extra \else)
>> This will appear in both modes screen and normal.
>>
>> Interesting is that no error appears in context 2006-05-28.
>>
> quite some code is being rewritten / adapted to context mkiv so
> there could be low level differences
>
> can you make a small example, since this else problem can come
> from other places than reported
>
There are demonstrative files. Please, run
texmfstart texexec --pdf ma-cb-cz-test.tex
and
texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex
>>> this file: ma-cb-env-cz.tex refers to itself and probably should
>>> be :
>>> \startenvironment ma-cb-env-cz
>>>
>>> \environment ma-cb.tex
>>>
>>> \mainlanguage[cz]
>>> \language[en]
>>> \enableregime[latin2]
>>>
>>> \stopenvironment
>>>
>> Sorry, my fault but it does not solve the problem. I obtain the
>> same error with fresh context and corrected version of this file:
>>
>> -
>> \startenvironment ma-cb-env-cz
>>
>> \mainlanguage[cz]
>> \language[en]
>> \enableregime[latin2]
>>
>> \stopenvironment
>> -
>>
> There is something wrong with ma-cb environment files. The file
> ma-cb-en does not compile. I get an error
>
> ! Undefined control sequence.
> \@@olbackground ->\StatusAchtergrond
>
> \doifvaluesomething ...inga {\csname #1\endcsname
>}\ifx \!!stringa
> \empty \e...
>
> \stoplocalframed ...ing {\@@framed \c!background }
>\dobackedbox
> \handleframed...
>
> \PlaatschapterStatus ... [\v!chapter \v!number ]}}
> \vskip 0pt plus
> \scratchc...
> \PlaatschapterStatus
> {}{}{}
> \firstoftwoarguments #1#2->#1
>
> ...
> l.19 \Introduction {Introduction}
>
>
> I tried making minimal example of the file that you posted, but
> always get the same error. I am pretty certain that ma-cb-en.tex
> used to compile in the past.
>
> Aditya
>
Hi Aditya,
I had the same problems in past in solved them by myself. The problems
are dutch commands in the style-files and a typo.
I attached my corrected style-files, because it is faster to replace
send you the files than I need to look where I made corrections.
The files did not correct the problem with the backgrounds in the
headers Vit has mentioned.
>>> \edef\StatusAchtergrond
>>> {StatusAchtergrond%
>>>\ifodd\realpageno R\else\ifdoublesided L\else R\fi\fi}%
>>>
>>> \ifdubbelzijdig -> \ifdoublesided
>>>
>>> this low level if has been changed, ad a result tex's 'fast if then
>>> else ' skip routine does not see the \ifdubbelzijdig is if and gets
>>> confused
>>> Hans
>> Great, thank you Hans!
>>
>> Let us process to teh next two problems also visible in the test file.
>>
>> 1. In the chapter ornament (a gray spiral with red dots) the red dots
>> are not dots but lines.
> that was a tough one (esp because my by-now reference mkiv converter
> also had this problem)
>
> in meta-pdf.mkii patch:
>
> \def\flushconcatMPsegment
> {\ifcase\getMPkeyword\relax
> \flushMPconcatmoveto
> \resetMPmoveto
> \doMPconcat{\gMPs1}\a{\gMPs2}\b%
> \PDFcode{\!MP\a\space\!MP\b\space l}%
>\or
> \flushMPconcatmoveto
> \resetMPmoveto
> \doMPconcat{\gMPs1}\a{\gMPs2}\b%
> \doMPconcat{\gMPs3}\c{\gMPs4}\d%
> \doMPconcat{\gMPs5}\e{\gMPs6}\f%
> \PDFcode{\!MP\a\space\!MP\b\space
> \!MP\c\space\!MP\d\space
> \!MP\e\space\!MP\f\space c}%
>\or
> \bgroup
> \noMPtranslate
> \flushMPconcatmoveto
> \PDFcode{\!MP\lastMPmoveX\space \!MP\lastMPmoveY\space l S}
> \egroup
> \resetMPmoveto
>\or
> % \flushMPconcatmoveto
> % \resetMPmoveto
>\fi}
Great Hans, it work
Re: [NTG-context] bug in beta: extra \else
Vit Zyka wrote:
> Hans Hagen wrote:
>> Wolfgang Schuster wrote:
>>> On Fri, 13 Oct 2006 19:16:58 -0400 (EDT)
>>> Aditya Mahajan <[EMAIL PROTECTED]> wrote:
>>>
>>>
On Fri, 13 Oct 2006, Vit Zyka wrote:
> Hans Hagen wrote:
>
>> Vit Zyka wrote:
>>
>>> Hans Hagen wrote:
>>>
Vit Zyka wrote:
> Hi all,
>
> there is some deep bug that was discovered translating
> Beginners manual. Let take single chapter e.g.
> ma-cb-cz-alignments.tex
>
> With today beta I got .log attached (error ! Extra \else)
> This will appear in both modes screen and normal.
>
> Interesting is that no error appears in context 2006-05-28.
>
quite some code is being rewritten / adapted to context mkiv so
there could be low level differences
can you make a small example, since this else problem can come
from other places than reported
>>> There are demonstrative files. Please, run
>>> texmfstart texexec --pdf ma-cb-cz-test.tex
>>> and
>>> texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex
>>>
>> this file: ma-cb-env-cz.tex refers to itself and probably should
>> be :
>> \startenvironment ma-cb-env-cz
>>
>> \environment ma-cb.tex
>>
>> \mainlanguage[cz]
>> \language[en]
>> \enableregime[latin2]
>>
>> \stopenvironment
>>
> Sorry, my fault but it does not solve the problem. I obtain the
> same error with fresh context and corrected version of this file:
>
> -
> \startenvironment ma-cb-env-cz
>
> \mainlanguage[cz]
> \language[en]
> \enableregime[latin2]
>
> \stopenvironment
> -
>
There is something wrong with ma-cb environment files. The file
ma-cb-en does not compile. I get an error
! Undefined control sequence.
\@@olbackground ->\StatusAchtergrond
\doifvaluesomething ...inga {\csname #1\endcsname
}\ifx \!!stringa
\empty \e...
\stoplocalframed ...ing {\@@framed \c!background }
\dobackedbox
\handleframed...
\PlaatschapterStatus ... [\v!chapter \v!number ]}}
\vskip 0pt plus
\scratchc...
\PlaatschapterStatus
{}{}{}
\firstoftwoarguments #1#2->#1
...
l.19 \Introduction {Introduction}
I tried making minimal example of the file that you posted, but
always get the same error. I am pretty certain that ma-cb-en.tex
used to compile in the past.
Aditya
>>> Hi Aditya,
>>>
>>> I had the same problems in past in solved them by myself. The problems
>>> are dutch commands in the style-files and a typo.
>>>
>>> I attached my corrected style-files, because it is faster to replace
>>> send you the files than I need to look where I made corrections.
>>>
>>> The files did not correct the problem with the backgrounds in the
>>> headers Vit has mentioned.
>> \edef\StatusAchtergrond
>> {StatusAchtergrond%
>>\ifodd\realpageno R\else\ifdoublesided L\else R\fi\fi}%
>>
>> \ifdubbelzijdig -> \ifdoublesided
> >
>> this low level if has been changed, ad a result tex's 'fast if then
>> else ' skip routine does not see the \ifdubbelzijdig is if and gets
>> confused
>> Hans
>
> Great, thank you Hans!
>
> Let us process to teh next two problems also visible in the test file.
>
> 1. In the chapter ornament (a gray spiral with red dots) the red dots
> are not dots but lines.
that was a tough one (esp because my by-now reference mkiv converter
also had this problem)
in meta-pdf.mkii patch:
\def\flushconcatMPsegment
{\ifcase\getMPkeyword\relax
\flushMPconcatmoveto
\resetMPmoveto
\doMPconcat{\gMPs1}\a{\gMPs2}\b%
\PDFcode{\!MP\a\space\!MP\b\space l}%
\or
\flushMPconcatmoveto
\resetMPmoveto
\doMPconcat{\gMPs1}\a{\gMPs2}\b%
\doMPconcat{\gMPs3}\c{\gMPs4}\d%
\doMPconcat{\gMPs5}\e{\gMPs6}\f%
\PDFcode{\!MP\a\space\!MP\b\space
\!MP\c\space\!MP\d\space
\!MP\e\space\!MP\f\space c}%
\or
\bgroup
\noMPtranslate
\flushMPconcatmoveto
\PDFcode{\!MP\lastMPmoveX\space \!MP\lastMPmoveY\space l S}
\egroup
\resetMPmoveto
\or
% \flushMPconcatmoveto
% \resetMPmoveto
\fi}
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53
Re: [NTG-context] bug in beta: extra \else
Aditya Mahajan wrote:
> On Sun, 15 Oct 2006, Vit Zyka wrote:
>
>> Great, thank you Hans!
>>
>> Let us process to teh next two problems also visible in the test file.
>>
>> 1. [snip]
>>
>
>
>> 2. Accented characters inside \typebuffer are type set as
>> \dochar {225}
>>
>
> This seems to be a bug. In utf-8 encoding, if an accented character is
> the first character of a buffer, it gets typed correctly. All other
> accented charaters come out as \dochar {225}. \getbuffer works fine.
>
> Can TeX choose the input encoding while writing files? If not, there
> may be really no robust way to solve this problem.
>
a solution if to completely move to utf-8 internally and then make chars > 127
unexpandable ; the problem is that whatever input encoding does not mix well
with multipass utf data then
in mkiv we will follow a different route since luatex is utf internally
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] bug in beta: extra \else
Aditya Mahajan wrote:
> On Mon, 16 Oct 2006, Aditya Mahajan wrote:
>
>> On Sun, 15 Oct 2006, Vit Zyka wrote:
>>> Great, thank you Hans!
>>>
>>> Let us process to teh next two problems also visible in the test file.
>>>
>>> 1. [snip]
>>
>>> 2. Accented characters inside \typebuffer are type set as
>>> \dochar {225}
>>
>> This seems to be a bug. In utf-8 encoding, if an accented character is
>> the first character of a buffer, it gets typed correctly. All other
>> accented charaters come out as \dochar {225}. \getbuffer works fine.
>
> I forgot to attach the test file. I am attaching it, hoping that the
> encoding will come out correctly.
>
>>
>> Can TeX choose the input encoding while writing files? If not, there
>> may be really no robust way to solve this problem.
>>
>> Aditya
in core-buf we need to treat the upper half of the vector:
\recatcodeuppercharacterstrue % <---
\setcatcodetable\vrbcatcodes
in startbuffer
(i cannot post a fixed file yet because buffers and verbatim is being
reshuffled due to mkii/mkiv preparations)
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] bug in beta: extra \else
On Sun, 15 Oct 2006, Vit Zyka wrote:
> Great, thank you Hans!
>
> Let us process to teh next two problems also visible in the test file.
>
> 1. [snip]
> 2. Accented characters inside \typebuffer are type set as
> \dochar {225}
This seems to be a bug. In utf-8 encoding, if an accented character is
the first character of a buffer, it gets typed correctly. All other
accented charaters come out as \dochar {225}. \getbuffer works fine.
Can TeX choose the input encoding while writing files? If not, there
may be really no robust way to solve this problem.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
On Mon, 16 Oct 2006, Aditya Mahajan wrote:
On Sun, 15 Oct 2006, Vit Zyka wrote:
Great, thank you Hans!
Let us process to teh next two problems also visible in the test file.
1. [snip]
2. Accented characters inside \typebuffer are type set as
\dochar {225}
This seems to be a bug. In utf-8 encoding, if an accented character is
the first character of a buffer, it gets typed correctly. All other
accented charaters come out as \dochar {225}. \getbuffer works fine.
I forgot to attach the test file. I am attaching it, hoping that the
encoding will come out correctly.
Can TeX choose the input encoding while writing files? If not, there
may be really no robust way to solve this problem.
Aditya\enableregime[utf]
\starttext
\startbuffer
ábout Whát
\stopbuffer
\typebuffer \getbuffer
\startbuffer
Whát
\stopbuffer
\typebuffer \getbuffer
\stoptext
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Wolfgang Schuster wrote:
> On Fri, 13 Oct 2006 19:16:58 -0400 (EDT)
> Aditya Mahajan <[EMAIL PROTECTED]> wrote:
>
>
>> On Fri, 13 Oct 2006, Vit Zyka wrote:
>>
>>
>>> Hans Hagen wrote:
>>>
Vit Zyka wrote:
> Hans Hagen wrote:
>
>> Vit Zyka wrote:
>>
>>> Hi all,
>>>
>>> there is some deep bug that was discovered translating Beginners
>>> manual.
>>> Let take single chapter e.g. ma-cb-cz-alignments.tex
>>>
>>> With today beta I got .log attached (error ! Extra \else)
>>> This will appear in both modes screen and normal.
>>>
>>> Interesting is that no error appears in context 2006-05-28.
>>>
>> quite some code is being rewritten / adapted to context mkiv so there
>> could be low level differences
>>
>> can you make a small example, since this else problem can come from
>> other
>> places than reported
>>
> There are demonstrative files. Please, run
> texmfstart texexec --pdf ma-cb-cz-test.tex
> and
> texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex
>
this file: ma-cb-env-cz.tex refers to itself and probably should be :
\startenvironment ma-cb-env-cz
\environment ma-cb.tex
\mainlanguage[cz]
\language[en]
\enableregime[latin2]
\stopenvironment
>>> Sorry, my fault but it does not solve the problem. I obtain the same error
>>> with fresh context and corrected version of this file:
>>>
>>> -
>>> \startenvironment ma-cb-env-cz
>>>
>>> \mainlanguage[cz]
>>> \language[en]
>>> \enableregime[latin2]
>>>
>>> \stopenvironment
>>> -
>>>
>> There is something wrong with ma-cb environment files. The file
>> ma-cb-en does not compile. I get an error
>>
>> ! Undefined control sequence.
>> \@@olbackground ->\StatusAchtergrond
>>
>> \doifvaluesomething ...inga {\csname #1\endcsname
>>}\ifx \!!stringa
>> \empty \e...
>>
>> \stoplocalframed ...ing {\@@framed \c!background }
>>\dobackedbox
>> \handleframed...
>>
>> \PlaatschapterStatus ... [\v!chapter \v!number ]}}
>> \vskip 0pt plus
>> \scratchc...
>> \PlaatschapterStatus
>> {}{}{}
>> \firstoftwoarguments #1#2->#1
>>
>> ...
>> l.19 \Introduction {Introduction}
>>
>>
>> I tried making minimal example of the file that you posted, but always
>> get the same error. I am pretty certain that ma-cb-en.tex used to
>> compile in the past.
>>
>> Aditya
>>
>
> Hi Aditya,
>
> I had the same problems in past in solved them by myself. The problems
> are dutch commands in the style-files and a typo.
>
> I attached my corrected style-files, because it is faster to replace
> send you the files than I need to look where I made corrections.
>
> The files did not correct the problem with the backgrounds in the
> headers Vit has mentioned.
>
\edef\StatusAchtergrond
{StatusAchtergrond%
\ifodd\realpageno R\else\ifdoublesided L\else R\fi\fi}%
\ifdubbelzijdig -> \ifdoublesided
this low level if has been changed, ad a result tex's 'fast if then else ' skip
routine does not see the \ifdubbelzijdig is if and gets confused
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] bug in beta: extra \else
On Fri, 13 Oct 2006, Vit Zyka wrote:
> Hans Hagen wrote:
>> Vit Zyka wrote:
>>> Hans Hagen wrote:
Vit Zyka wrote:
> Hi all,
>
> there is some deep bug that was discovered translating Beginners manual.
> Let take single chapter e.g. ma-cb-cz-alignments.tex
>
> With today beta I got .log attached (error ! Extra \else)
> This will appear in both modes screen and normal.
>
> Interesting is that no error appears in context 2006-05-28.
quite some code is being rewritten / adapted to context mkiv so there
could be low level differences
can you make a small example, since this else problem can come from other
places than reported
>>> There are demonstrative files. Please, run
>>> texmfstart texexec --pdf ma-cb-cz-test.tex
>>> and
>>> texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex
>>
>> this file: ma-cb-env-cz.tex refers to itself and probably should be :
>>
>> \startenvironment ma-cb-env-cz
>>
>> \environment ma-cb.tex
>>
>> \mainlanguage[cz]
>> \language[en]
>> \enableregime[latin2]
>>
>> \stopenvironment
>
> Sorry, my fault but it does not solve the problem. I obtain the same error
> with fresh context and corrected version of this file:
>
> -
> \startenvironment ma-cb-env-cz
>
> \mainlanguage[cz]
> \language[en]
> \enableregime[latin2]
>
> \stopenvironment
> -
There is something wrong with ma-cb environment files. The file
ma-cb-en does not compile. I get an error
! Undefined control sequence.
\@@olbackground ->\StatusAchtergrond
\doifvaluesomething ...inga {\csname #1\endcsname
}\ifx \!!stringa
\empty \e...
\stoplocalframed ...ing {\@@framed \c!background }
\dobackedbox
\handleframed...
\PlaatschapterStatus ... [\v!chapter \v!number ]}}
\vskip 0pt plus
\scratchc...
\PlaatschapterStatus
{}{}{}
\firstoftwoarguments #1#2->#1
...
l.19 \Introduction {Introduction}
I tried making minimal example of the file that you posted, but always
get the same error. I am pretty certain that ma-cb-en.tex used to
compile in the past.
Aditya
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] bug in beta: extra \else
Vit Zyka wrote: > Hans Hagen wrote: >> Vit Zyka wrote: >>> Hi all, >>> >>> there is some deep bug that was discovered translating Beginners >>> manual. Let take single chapter e.g. ma-cb-cz-alignments.tex >>> >>> With today beta I got .log attached (error ! Extra \else) >>> This will appear in both modes screen and normal. >>> >>> Interesting is that no error appears in context 2006-05-28. >> quite some code is being rewritten / adapted to context mkiv so there >> could be low level differences >> >> can you make a small example, since this else problem can come from >> other places than reported > > There are demonstrative files. Please, run > texmfstart texexec --pdf ma-cb-cz-test.tex > and > texmfstart texexec --pdf --mode=screen ma-cb-cz-test.tex this file: ma-cb-env-cz.tex refers to itself and probably should be : \startenvironment ma-cb-env-cz \environment ma-cb.tex \mainlanguage[cz] \language[en] \enableregime[latin2] \stopenvironment - 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] bug in beta: extra \else
Vit Zyka wrote:
> Hi all,
>
> there is some deep bug that was discovered translating Beginners
> manual. Let take single chapter e.g. ma-cb-cz-alignments.tex
>
> With today beta I got .log attached (error ! Extra \else)
> This will appear in both modes screen and normal.
>
> Interesting is that no error appears in context 2006-05-28.
quite some code is being rewritten / adapted to context mkiv so there
could be low level differences
can you make a small example, since this else problem can come from
other places than reported
>
> In context 2006-09-10 this error appears only in normal mode. Screen
> mode is OK.
>
> Vit
>
> P.S. Today's beta shows even more problems:
> - inside typebuffer: only '\dochar {225}' instead of \'a in latin2
hm, sample ... maybe some pre-expansion problem
> - some metapost graphics is wrong
example ...
> But I suggest to solve them step by step.
sure
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
