Hi, A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded http://www.pragma-ade.com/preliminaries/hybrid-italics.pdf Files in that path will come and go. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 14 oct. 2011, at 23:26, Hans Hagen wrote:
Hi,
A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded
http://www.pragma-ade.com/preliminaries/hybrid-italics.pdf
Files in that path will come and go.
Hans
Hi Hans, Thanks for the new beta. I wanted just to report that \currentdate has still a bug in French: in French it gives day+ octobre 2011 Minimal example follows. Best regards: OK \starttext English: \currentdate French: \mainlanguage[fr] \currentdate \stoptext
Dear Hans, Am Freitag, den 14.10.2011, 23:26 +0200 schrieb Hans Hagen:
A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded
I read your document and not being able to contribute anything having to do with programming below you can find the thing which should be corrected in my opinion. Not being a native English speaker they could be wrong though. 1. s/motto’s/mottos/ 2. s/cambria/Cambria/ 3. `\par` not used everywhere 4. … *at* a boundary … 5. … by not passing the italic information *to* the font machinery … 6. For math italics I do not see a difference in the output when the value is `2` and `3`.
Files in that path will come and go.
Thanks, Paul
On 15-10-2011 16:45, Paul Menzel wrote:
Dear Hans,
Am Freitag, den 14.10.2011, 23:26 +0200 schrieb Hans Hagen:
A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded
I read your document and not being able to contribute anything having to do with programming below you can find the thing which should be corrected in my opinion. Not being a native English speaker they could be wrong though.
1. s/motto’s/mottos/ 2. s/cambria/Cambria/ 3. `\par` not used everywhere 4. … *at* a boundary … 5. … by not passing the italic information *to* the font machinery …
Thanks
6. For math italics I do not see a difference in the output when the value is `2` and `3`.
That's work in progress .. we need to adapt lfg files and so (but at least it offers a mechanism). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 14.10.2011 23:26, Hans Hagen wrote:
Hi,
A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded
http://www.pragma-ade.com/preliminaries/hybrid-italics.pdf
Files in that path will come and go.
Hans
Hi, in the current beta I noticed that processing of my documents takes ages. While looking in the project directory I noticed that context left behind HUGE log files (500MB to 4GB, depending on the number of runs). The logs contain many verbose infos, as seen in this example: --->3-------------------------------------------------- loading > Code syntax highlighting (ver: 2011.09.03) resolvers > modules > loaded: 'syntax-groups' (C:/context/tex/texmf-modules/tex/context/third/vim/t-syntax-groups.tex loading > Syntax highlighting groups (ver: 2011.09.03) \doifmode ->\unprotect \dodoifmode \unprotect ->\pushcatcodetable \setcatcodetable \prtcatcodes \pushcatcodetable ->\advance \catcoderestorelevel \plusone \tracepushcatcodetable \expandafter \chardef \csname scct:\number \catcoderestorelevel \endcsname \currentcatcodetable \tracepushcatcodetable -> \setcatcodetable #1->\catcodetable #1\the \everycatcodetable \tracesetcatcodetable #1<-\prtcatcodes \tracesetcatcodetable -> \dodoifmode ->\docheckformode \firstofoneargument \gobbleoneargument \docheckformode #1#2#3->\protect \checkedmodefalse \rawprocesscommacommand [#3]\dodocheckformode \ifcheckedmode \@EA #1\else \@EA #2\fi #1<-\firstofoneargument #2<-\gobbleoneargument #3<-\s!mkii \protect ->\popcatcodetable --->3-------------------------------------------------- Any ideas what's going wrong here? Thanks in advance! -- Best Regards, Andreas
On Wed, Oct 19, 2011 at 9:58 AM, Andreas Schneider
On 14.10.2011 23:26, Hans Hagen wrote:
Hi,
A new beta has been uploaded. Nothing new apart from some experimental code and a few bugfixes. I also uploaded
http://www.pragma-ade.com/preliminaries/hybrid-italics.pdf
Files in that path will come and go.
Hans
Hi,
in the current beta I noticed that processing of my documents takes ages. While looking in the project directory I noticed that context left behind HUGE log files (500MB to 4GB, depending on the number of runs). The logs contain many verbose infos, as seen in this example:
--->3-------------------------------------------------- loading > Code syntax highlighting (ver: 2011.09.03) resolvers > modules > loaded: 'syntax-groups' (C:/context/tex/texmf-modules/tex/context/third/vim/t-syntax-groups.tex loading > Syntax highlighting groups (ver: 2011.09.03)
\doifmode ->\unprotect \dodoifmode
\unprotect ->\pushcatcodetable \setcatcodetable \prtcatcodes
\pushcatcodetable ->\advance \catcoderestorelevel \plusone \tracepushcatcodetable \expandafter \chardef \csname scct:\number \catcoderestorelevel \endcsname \currentcatcodetable
\tracepushcatcodetable ->
\setcatcodetable #1->\catcodetable #1\the \everycatcodetable \tracesetcatcodetable #1<-\prtcatcodes
\tracesetcatcodetable ->
\dodoifmode ->\docheckformode \firstofoneargument \gobbleoneargument
\docheckformode #1#2#3->\protect \checkedmodefalse \rawprocesscommacommand [#3]\dodocheckformode \ifcheckedmode \@EA #1\else \@EA #2\fi #1<-\firstofoneargument #2<-\gobbleoneargument #3<-\s!mkii
\protect ->\popcatcodetable --->3--------------------------------------------------
Any ideas what's going wrong here?
Thanks in advance! it seems that there is a \tracingall somewhere I've had similar data when I put \tracingall as a first macro in context.mkiv -- luigi
On 19-10-2011 10:03, luigi scarso wrote:
Any ideas what's going wrong here?
Thanks in advance! it seems that there is a \tracingall somewhere
indeed, so best grep for that on your source files Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
syst-ini.mkiv line 626: \tracingstats\plusone The only one I find, but I skipped yhe mkii files. Hans van der Meer On 19 okt. 2011, at 11:46, Hans Hagen wrote:
On 19-10-2011 10:03, luigi scarso wrote:
Any ideas what's going wrong here?
Thanks in advance! it seems that there is a \tracingall somewhere
indeed, so best grep for that on your source files
Hans
On 19-10-2011 12:31, Meer, H. van der wrote:
syst-ini.mkiv line 626: \tracingstats\plusone The only one I find, but I skipped yhe mkii files.
yes but that the command itself Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 19.10.2011 12:35, Hans Hagen wrote:
On 19-10-2011 12:31, Meer, H. van der wrote:
syst-ini.mkiv line 626: \tracingstats\plusone The only one I find, but I skipped yhe mkii files.
yes but that the command itself
Hans
It seems the VIM module is the culprit here. In t-syntax-groups.tex on line 14 is: \tracingmacros=1 Commenting that line fixed the problem. @Aditya: can you re-release a fixed version please? :-) Thanks! -- Best Regards, Andreas
On Wed, 19 Oct 2011, Andreas Schneider wrote:
It seems the VIM module is the culprit here. In t-syntax-groups.tex on line 14 is: \tracingmacros=1 Commenting that line fixed the problem.
@Aditya: can you re-release a fixed version please? :-)
Sorry about that :( I uploaded a fixed version. Aditya
participants (7)
-
Aditya Mahajan -
Andreas Schneider -
Hans Hagen -
luigi scarso -
Meer, H. van der -
Otared Kavian -
Paul Menzel