Hello there! TL;DR: https://github.com/melmothx/context-unofficial-test-suite A week ago I had a conversation with mpfusion and another user over IRC about the ConTeXt test suite. mpfusion had a tarball with some test and an elaborate machinery to see if the testfiles compile. He kindly provided the tarball, and I took the liberty to do it my way (I didn't hear back from him, I assume he's working on his solution), using the testfiles and rewriting the code. My solution is quite simple, is written in perl (300 lines all included) and probably is not portable to non-unix machines. It uses imagemagick and pdftoppm to raster the PDF, and it's resonably fast (with a trick to speed up the difference parsing). It produces an ascii table like this: ./run-test.pl --run Using /usr/local/bin/context mtx-context | ConTeXt Process Management 0.52 mtx-context | mtx-context | main context file: /usr/local/texlive/2012/texmf-dist/tex/context/base/context.mkiv mtx-context | current version: 2012.05.30 11:26 ................. | File name | Success | Differs Avg | Worst value | Pages | Time | | arrows-001 | OK | 0.000000 | 0.000000 | 1 | 2 | | catcodes-001 | OK | 0.000000 | 0.000000 | 1 | 2 | | columnsets-001 | OK | 0.000000 | 0.000000 | 10 | 4 | | date-002 | OK | 0.000000 | 0.000000 | 1 | 2 | | dates-001 | OK | 0.605634 | 0.605634 | 1 | 2 | | dates-002 | OK | 0.000000 | 0.000000 | 1 | 3 | | hsv-001 | OK | 0.000000 | 0.000000 | 8 | 5 | | inclusion | OK | 0.000000 | 0.000000 | 1 | 2 | | metapost-001 | OK | 0.000000 | 0.000000 | 1 | 2 | | metapost-002 | OK | 0.000000 | 0.000000 | 1 | 2 | | mixed-001 | OK | 0.000000 | 0.000000 | 2 | 2 | | narrower-bidi-001 | OK | 0.000000 | 0.000000 | 4 | 2 | | ppchtex-001 | OK | 0.000000 | 0.000000 | 1 | 2 | | ppchtex-005 | OK | 0.000000 | 0.000000 | 1 | 2 | | ppchtex-006 | OK | 0.000000 | 0.000000 | 1 | 2 | | spot-001 | OK | 0.000000 | 0.000000 | 1 | 3 | | tables-001 | OK | 0.000000 | 0.000000 | 1 | 1 | It leaves the visual diffs as png images under diffs/ I'd like to know if there is some interest in this thing, as (obviously) the test suit is not really populated to have any kind of value. There is also room for improvement (like custom arguments to the compilation). Happy euroTeXt to the lucky partecipants. Enjoy! Best wishes -- Marco
On Sun, 7 Oct 2012, Marco Pessotto wrote:
Hello there!
TL;DR: https://github.com/melmothx/context-unofficial-test-suite
A week ago I had a conversation with mpfusion and another user over IRC about the ConTeXt test suite. mpfusion had a tarball with some test and an elaborate machinery to see if the testfiles compile. He kindly provided the tarball, and I took the liberty to do it my way (I didn't hear back from him, I assume he's working on his solution), using the testfiles and rewriting the code.
[....]
I'd like to know if there is some interest in this thing, as (obviously) the test suit is not really populated to have any kind of value. There is also room for improvement (like custom arguments to the compilation).
This is an excellent idea. I am assuming that you are aware of the earlier effort: http://wiki.contextgarden.net/Test In particular the test repository: http://foundry.supelec.fr/gf/project/contexttest/scmsvn/ The test repository started around six years ago after discussions at the first ConTeXt meeting, but lost momentum after a few years. It does have a more extensive set of test cases, and a script to compare PDF files. It may be worthwhile to merge the two repos. Ideally such a test suite should be run periodically on a server and it can send an email to a list if one of the tests fails. Aditya
luigi scarso
On Wed, Oct 17, 2012 at 8:44 AM, Marco Pessotto
wrote: Aditya Mahajan
writes: > It may be worthwhile to merge the two repos.
I'm on my way. I'll keep you posted.
Can you use graphicsmagick ?
So far I've used imagemagick. I guess that it shouldn't be a problem to replace it with its fork, if it offers the same features. I've never used graphicsmagick. Can we expect better performances? -- Marco
On Wed, Oct 17, 2012 at 9:27 AM, Marco Pessotto
luigi scarso
writes: On Wed, Oct 17, 2012 at 8:44 AM, Marco Pessotto
wrote: Aditya Mahajan
writes: > It may be worthwhile to merge the two repos.
I'm on my way. I'll keep you posted.
Can you use graphicsmagick ?
So far I've used imagemagick. I guess that it shouldn't be a problem to replace it with its fork, if it offers the same features. I've never used graphicsmagick. Can we expect better performances?
It's not a huge difference, but it can integrated better with mkiv; see http://meeting.contextgarden.net/2011/talks/day1_05_luigi_graphicmagick/ (if you like these kind of things) -- luigi
luigi scarso
It's not a huge difference, but it can integrated better with mkiv; see http://meeting.contextgarden.net/2011/talks/day1_05_luigi_graphicmagick/ (if you like these kind of things)
I think I'll have to run some benchmark to see if it can save some resources and speed up the testing. I don't care too much for the mkiv integration. The other Marco's idea was exactly to make conTeXt run the tests. I prefer to let ConTeXt do the typesetting and do the dirty stuff with perl. So far I've included the testfiles from contexttest, parking the failing ones in a dedicated directory. There are 62 files now, and the test takes 13 minutes to run on my humble machine. These are the results for version 2012.10.16 23:38 against TeXlive2012: | File name | Success | Differs Avg | Worst value | Pages | Time | | arrows-001 | OK | 6.105634 | 6.105634 | 1 | 5 | | catcodes-001 | OK | 50.219512 | 50.219512 | 1 | 3 | | columnsets-001 | OK | 0.000000 | 0.000000 | 10 | 7 | | core-des-001 | OK | 0.324862 | 0.658451 | 23 | 9 | | core-des-002 | OK | 1.527666 | 2.651408 | 7 | 8 | | core-itm-001 | OK | 11.947183 | 13.753521 | 5 | 5 | | core-mat-001 | OK | 0.070423 | 0.070423 | 1 | 5 | | core-mat-002 | OK | 0.000000 | 0.000000 | 1 | 5 | | core-mat-003 | OK | 1.788732 | 1.788732 | 1 | 5 | | core-mat-004 | OK | 0.000000 | 0.000000 | 2 | 5 | | core-mat-005 | OK | 0.000000 | 0.000000 | 1 | 3 | | core-rul-001 | OK | 0.151408 | 0.151408 | 1 | 4 | | core-sec-001 | OK | 0.000000 | 0.000000 | 1 | 3 | | core-ver-001 | OK | 0.000000 | 0.000000 | 1 | 4 | | core-ver-002 | OK | 0.000000 | 0.000000 | 1 | 4 | | core-ver-003 | OK | 0.131162 | 0.524648 | 4 | 5 | | core-ver-004 | OK | 0.000000 | 0.000000 | 1 | 4 | | core-ver-005 | OK | 0.000000 | 0.000000 | 1 | 4 | | core-ver-007 | OK | 0.000000 | 0.000000 | 1 | 4 | | date-002 | OK | 0.000000 | 0.000000 | 1 | 3 | | dates-001 | OK | 3.880282 | 3.880282 | 1 | 4 | | dates-002 | OK | 0.359155 | 0.359155 | 1 | 4 | | enco-pfr-001 | OK | 0.095070 | 0.095070 | 1 | 4 | | floats-001 | OK | 31.651408 | 31.651408 | 1 | 4 | | floats-002 | OK | 31.651408 | 31.651408 | 1 | 5 | | hsv-001 | OK | 0.000000 | 0.000000 | 8 | 14 | | inclusion | OK | 0.000000 | 0.000000 | 1 | 4 | | math-pln-001 | OK | 0.049296 | 0.049296 | 1 | 4 | | meta-ini-001 | OK | 0.000000 | 0.000000 | 2 | 4 | | metapost-001 | OK | 0.000000 | 0.000000 | 1 | 4 | | metapost-002 | OK | 0.000000 | 0.000000 | 1 | 3 | | mixed-001 | OK | 21.327465 | 37.492958 | 2 | 4 | | narrower-bidi-001 | OK | 0.000000 | 0.000000 | 4 | 4 | | page-run-001 | OK | 0.000000 | 0.000000 | 1 | 4 | | page-txt-001 | OK | 0.445171 | 0.496479 | 7 | 5 | | ppchtex-001 | OK | 1.573944 | 1.573944 | 1 | 4 | | ppchtex-005 | OK | 1.169014 | 1.169014 | 1 | 4 | | ppchtex-006 | OK | 0.000000 | 0.000000 | 1 | 4 | | spacing-grid-001 | OK | 10.443662 | 10.531690 | 3 | 5 | | spacing-grid-005 | OK | 11.602993 | 14.975352 | 8 | 9 | | spacing-space-001 | OK | 0.000000 | 0.000000 | 1 | 3 | | spacing-space-002 | OK | 0.000000 | 0.000000 | 2 | 4 | | spacing-space-003 | OK | 0.000000 | 0.000000 | 1 | 4 | | spacing-space-004 | OK | 0.000000 | 0.000000 | 1 | 4 | | spec-mis-001 | FAILED | 0.000000 | 0.000000 | 0 | 0 | | spot-001 | OK | 0.000000 | 0.000000 | 1 | 4 | |struc-allkind-tex-001 | OK | 0.292254 | 0.292254 | 1 | 5 | |struc-allkind-xml-001 | OK | 1.471831 | 1.471831 | 1 | 6 | | struc-itemize-001 | OK | 0.176056 | 0.176056 | 1 | 4 | | struc-itemize-002 | OK | 0.000000 | 0.000000 | 1 | 3 | | struc-page-001 | OK | 6.237676 | 7.066901 | 4 | 14 | | struc-sections-002 | OK | 0.161972 | 0.161972 | 1 | 4 | |struc-sections-xml-002 | OK | 0.000000 | 0.000000 | 1 | 4 | | supp-mps-001 | OK | 0.000000 | 0.000000 | 1 | 4 | | supp-mps-002 | OK | 0.000000 | 0.000000 | 1 | 4 | | supp-mps-003 | OK | 0.000000 | 0.000000 | 1 | 3 | | supp-mps-004 | OK | 0.000000 | 0.000000 | 1 | 4 | | supp-mps-005 | OK | 0.000000 | 0.000000 | 1 | 3 | | tables-001 | OK | 0.577465 | 0.577465 | 1 | 4 | | widgets-fields-001 | OK | 0.000000 | 0.000000 | 1 | 5 | | x-res-00-001 | OK | 0.000000 | 0.000000 | 1 | 5 | | xml-chain-001 | OK | 0.000000 | 0.000000 | 1 | 4 | Looking at the diffs, many of the differences are really tiny, but differences exist nevertheless. It will take me some time to sort out which ones are just tiny space shifting, and which ones give really different output. To run the tests yourself it's extremely easy: git clone git://github.com/melmothx/context-unofficial-test-suite.git cd context-unofficial-test-suite ./run-test.pl --run 2>&1 | tee test.log Have a coffee and that's it. I always keep the repo on github synced with mine. Cheers P.S. When on-line, I'm logged into the #context channel on freenode as "melmothX". -- Marco
2012-10-17 Marco Pessotto:
luigi scarso
writes: It's not a huge difference, but it can integrated better with mkiv; see http://meeting.contextgarden.net/2011/talks/day1_05_luigi_graphicmagick/ (if you like these kind of things)
I think I'll have to run some benchmark to see if it can save some resources and speed up the testing. I don't care too much for the mkiv integration. The other Marco's idea was exactly to make conTeXt run the tests.
I removed that part, it was a stupid idea. At the moment it's a pure Lua solution. It's divided into two parts. The first part is the database update, Lua runs context on the tests and writes the results to a database (a Lua table stored in a file). For the second part context is run on the database to generate the report from the database. With this database you can display information like “What broke in the last beta”.
Looking at the diffs, many of the differences are really tiny, but differences exist nevertheless. It will take me some time to sort out which ones are just tiny space shifting, and which ones give really different output.
That's why I use a header for each test file. You can specify “sensitivity=low|medium|high”, this sets a predefined tolerance for the page difference. I don't see any other option. There is no single value which is sensitive enough, for instance to detect if a footnote is subscripted or not and at the same time tolerant enough not to always mark a fifty page document as “failed”. Marco
Marco Patzer
Looking at the diffs, many of the differences are really tiny, but differences exist nevertheless. It will take me some time to sort out which ones are just tiny space shifting, and which ones give really different output.
That's why I use a header for each test file. You can specify “sensitivity=low|medium|high”, this sets a predefined tolerance for the page difference. I don't see any other option. There is no single value which is sensitive enough, for instance to detect if a footnote is subscripted or not and at the same time tolerant enough not to always mark a fifty page document as “failed”.
I'm not sure that exists a “fuzzy” algorithm for the tolerance. From my testing, a minimal shift, say, to the right, on a full page will generate a lot of noise, because each glyph will be “doubled”. I'm generating, with the visual diffs, a script to launch two PDF viewers and eventually promote the generated to the new reference. I guess there is no shortcuts to the manual ispection of the diffs. -- Marco
On 17-10-2012 18:57, Marco Pessotto wrote:
Marco Patzer
writes: Looking at the diffs, many of the differences are really tiny, but differences exist nevertheless. It will take me some time to sort out which ones are just tiny space shifting, and which ones give really different output.
That's why I use a header for each test file. You can specify “sensitivity=low|medium|high”, this sets a predefined tolerance for the page difference. I don't see any other option. There is no single value which is sensitive enough, for instance to detect if a footnote is subscripted or not and at the same time tolerant enough not to always mark a fifty page document as “failed”.
I'm not sure that exists a “fuzzy” algorithm for the tolerance. From my testing, a minimal shift, say, to the right, on a full page will generate a lot of noise, because each glyph will be “doubled”. I'm generating, with the visual diffs, a script to launch two PDF viewers and eventually promote the generated to the new reference.
I guess there is no shortcuts to the manual ispection of the diffs.
vertical shifts are probably more an issue; for horizontal shifts you can use a threshold of .1em because that catches spaces and distances etc but ignores differences in fonts. 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 -----------------------------------------------------------------
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough. Full report here: https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e... (It's stored in the commit log). I also caught some problems which are fixed in the beta, but broken in TL12. Hans Hagen writes:
vertical shifts are probably more an issue; for horizontal shifts you can use a threshold of .1em because that catches spaces and distances etc but ignores differences in fonts.
I'm comparing pixel by pixel, I don't have any idea how to implement a sensible treshold system, without writing another TeX engine... Best wishes. -- Marco
2012-10-17 Marco Pessotto:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
I don't know if Hans appreciates a test suite, seems like plenty of work for him ;) Marco
On 17-10-2012 20:08, Marco Patzer wrote:
2012-10-17 Marco Pessotto:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
I don't know if Hans appreciates a test suite, seems like plenty of work for him ;)
I'm not alone doing this, am I? It all depends on how serious an issue is. For instance, columns use a new mechanism so it might be as simple as changing some defaults. 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 -----------------------------------------------------------------
Hans Hagen
On 17-10-2012 20:08, Marco Patzer wrote:
2012-10-17 Marco Pessotto:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
I don't know if Hans appreciates a test suite, seems like plenty of work for him ;)
I'm not alone doing this, am I?
It all depends on how serious an issue is. For instance, columns use a new mechanism so it might be as simple as changing some defaults.
Well, there aren't *so many* issues. If the columns are fine with you, they are fine with me too. Changing the references is not a problem. (Well, if they keep changing every week, well, that could be a problem for the well-being of the test suite). Some things, like the chemical stuff, require someone who actually does know what they are (I don't). The whole point of having a test suite is to catch the regressions before they pile up. I just reported everything I saw. Best wishes -- Marco
On 17-10-2012 21:30, Marco Pessotto wrote:
Hans Hagen
writes: On 17-10-2012 20:08, Marco Patzer wrote:
2012-10-17 Marco Pessotto:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
I don't know if Hans appreciates a test suite, seems like plenty of work for him ;)
I'm not alone doing this, am I?
It all depends on how serious an issue is. For instance, columns use a new mechanism so it might be as simple as changing some defaults.
Well, there aren't *so many* issues. If the columns are fine with you, they are fine with me too. Changing the references is not a problem. (Well, if they keep changing every week, well, that could be a problem for the well-being of the test suite).
Mixed columns probably need some time to become stable (and the width / distance should definitely be compatible).
Some things, like the chemical stuff, require someone who actually does know what they are (I don't).
Alan is currently reviewing the chemical subsystem.
The whole point of having a test suite is to catch the regressions before they pile up. I just reported everything I saw.
Sure. In principle we should be downard compatible (although mkiv might do things better than mkii) and at some point things should stabelize again. So, any indication if a substantial change is important. 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 Wed, 17 Oct 2012 22:52:33 +0200
Hans Hagen
On 17-10-2012 21:30, Marco Pessotto wrote:
Some things, like the chemical stuff, require someone who actually does know what they are (I don't).
Alan is currently reviewing the chemical subsystem.
Furiously, "breaking" many old curiosities, fixing broken and incomplete functionality, AND completely re-writing the documentation! (Not that I really know much about chemistry myself... :) Alan
Le mercredi 17 octobre 2012, Alan BRASLAU a écrit :
Furiously, "breaking" many old curiosities, fixing broken and incomplete functionality, AND completely re-writing the documentation! (Not that I really know much about chemistry myself... :) Since you talk about chemistry, is there now a way to type correctly isotopes (without any hacks). Actually \chemistry{^{238}_{92}U} do align '92' to the left. It should be aligned to the right.
Thank you.
(Maybe I should have open a new thread...)
--
Romain Diss
On Thu, 18 Oct 2012 00:20:01 +0200
Romain Diss
Le mercredi 17 octobre 2012, Alan BRASLAU a écrit :
Furiously, "breaking" many old curiosities, fixing broken and incomplete functionality, AND completely re-writing the documentation! (Not that I really know much about chemistry myself... :) Since you talk about chemistry, is there now a way to type correctly isotopes (without any hacks). Actually \chemistry{^{238}_{92}U} do align '92' to the left. It should be aligned to the right.
Thank you. (Maybe I should have open a new thread...)
Hum, I work all the time with $^3$He and $^4$He, but somehow I never thought of this as chemistry... I'll look into fixing \chemistry{^{32}_{15}P} (another one of my occupations), and Hans will then put it into the beta. Alan
On 18-10-2012 00:20, Romain Diss wrote:
Le mercredi 17 octobre 2012, Alan BRASLAU a écrit :
Furiously, "breaking" many old curiosities, fixing broken and incomplete functionality, AND completely re-writing the documentation! (Not that I really know much about chemistry myself... :) Since you talk about chemistry, is there now a way to type correctly isotopes (without any hacks). Actually \chemistry{^{238}_{92}U} do align '92' to the left. It should be aligned to the right.
It's on the agenda for luatex: prescripts. 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 -----------------------------------------------------------------
Romain wrote:
Since you talk about chemistry, is there now a way to type correctly isotopes (without any hacks). Actually \chemistry{^{238}_{92}U} do align '92' to the left. It should be aligned to the right.
What about \lohi with the [left] key? That typesets the super- and subscript ragged-left / as though they are to the left of the word (choose your favourite mnemonic). That might serve your needs until Alan gets \chemistry to parse and typeset isotopes correctly. http://wiki.contextgarden.net/Command/hilo Alpha particles are \lohi[left]{40}{2}He. Cheers, Sietse
On Thu, 18 Oct 2012 10:41:00 +0200
Sietse Brouwer
Alpha particles are \lohi[left]{40}{2}He.
Alpha particles are He\high{2+} (helium nucleus) not to be confused with He\low{2} (helium molecules) that DO exist but are unstable and only last 13 seconds or so. Someone needs to fix the wiki... (done!) \lohi[left]{}{4}He is a boson; \lohi[left]{}{3} is a fermion. By the way, \lohi[left]{2}{4}He is somewhat a tautology, like all such isotopic nomenclature, as He ALWAYS has an atomic number of 2, otherwise it is not He (and U ALWAYS has an atomic number of 92, otherwise it is no longer U). Alan -- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS URA 2464 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.braslau@cea.fr
Le jeudi 18 octobre 2012, Alan BRASLAU a écrit : > By the way, \lohi[left]{2}{4}He is somewhat a tautology, like all such > isotopic nomenclature, as He ALWAYS has an atomic number of 2, > otherwise it is not He (and U ALWAYS has an atomic number of 92, > otherwise it is no longer U). Sure but but the format is nevertheless usefull in some cases: - exercises like: "what is the chemical symbol of the \lohi[left]{2}{4}X atom?" - nuclear reactions where Z are usefull to balance the equations (see http://en.wikipedia.org/wiki/Nuclear_reaction for exemples). Of course if one know every Z and atomic symbol associated by heart, the nomenclature with Z is not needed. -- Romain Diss
Sietse wrote:
Alpha particles are \lohi[left]{40}{2}He.
Alain wrote:
Someone needs to fix the wiki... (done!)
[Alain fixed the wiki to "Alpha particles are \lohi[left]{4}{2}He\high{2+}."] But, but, but ... that doesn't demonstrate the fact that the elements right-align instead of left-align! I've changed it again: One stable isotope of tantalum is \lohi[left]{73}{180m}Ta. (This is my own fault: I deliberately added the extra 0 in \lohi[left]{40}{2}He, a long time ago, because I cared more about illustrativeness than truth. And because I was too lazy to look up a more suitable isotope. I am a bad person, and it is good that people like Alain exist to keep people like me in line. :-P) --Sietse
Le jeudi 18 octobre 2012, Sietse Brouwer a écrit :
What about \lohi with the [left] key? That might serve your needs until Alan gets \chemistry to parse and typeset isotopes correctly. Yes there are some "hacks" to typeset isotopes correctly, but I think it would be better to be able to typeset it in a simple way with \chemistry.
--
Romain Diss
On 17-10-2012 20:08, Marco Patzer wrote:
2012-10-17 Marco Pessotto:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
- i fixed the corner in framed - \chemical{EQUILIBRIUM}{boven}{onder} is fixed but top/bottom only work in formulas - for footnotes to migrate outside a description one needs to say \automigrateinserts (at least till we're sure that it always works ok) ----------------------------------------------------------------- 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 17-10-2012 19:58, Marco Pessotto wrote:
Ok, this is my first bug report. I noticed that the column width/margin is quite altered since TL12. There are some other problems, tough.
Full report here:
https://github.com/melmothx/context-unofficial-test-suite/commit/8575456ae9e...
(It's stored in the commit log).
I also caught some problems which are fixed in the beta, but broken in TL12.
Hans Hagen writes:
vertical shifts are probably more an issue; for horizontal shifts you can use a threshold of .1em because that catches spaces and distances etc but ignores differences in fonts.
I'm comparing pixel by pixel, I don't have any idea how to implement a sensible treshold system, without writing another TeX engine...
Last time I looked into this (quite a while ago) i did something like the attached; in there you find: local command = string.format('gm convert -verbose -density 72 "%s" %s',pdfname,ppmname) so I used a rather low density and (and then used md5 for comparing) 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 -----------------------------------------------------------------
A week ago I had a conversation with mpfusion and another user over IRC about the ConTeXt test suite. mpfusion had a tarball with some test and an elaborate machinery to see if the testfiles compile. He kindly provided the tarball,
That's me, by the way.
and I took the liberty to do it my way (I didn't
hear back from him, I assume he's working on his solution), using the testfiles and rewriting the code.
I cleaned up the code and rewrote some part of it. But it's in a stage where it does not compile. At the moment I'm quite busy and don't have time to work on that, that's why I didn't publish, yet. Marco
participants (8)
-
Aditya Mahajan
-
Alan BRASLAU
-
Hans Hagen
-
luigi scarso
-
Marco Patzer
-
Marco Pessotto
-
Romain Diss
-
Sietse Brouwer