Re: Regression testing of tetex
Junichi Uekawa <dancer@netfort.gr.jp> wrote:
> One thing that I am worried, from my perspective is that i18n isn't
> too tested, because it's often not obvious how to run tex files of
> languages other than your own.
The language documentation packages of texlive should provide some
examples. tetex also has some - do you want us to collect a list?
> That I guess so. Unlike CPAN, which seems to be mandatory to have a
> testsuite, tex doesn't seem to have such thing. Technically it might
> be doable, but I doubt if it can be ran in a reasonable time in terms
> of amount of work preparing it, and the amount of time required to run
> through.
That's a problem, indeed. But it would still be good to have one, even
if it isn't feasible to run it on every buildd or local build.
> What I had in mind was having some kind of an example tex file of what
> could be considered a typical usage, and re-run tex over it, producing
> dvi/ps/pdf. That way, we at least know they do compile, and if we can
> check the diffs, that might be a good way to catch any changes.
>
>
>
> /me checks, and rebuilding twice with dvipdfmx seems to obtain two
> different results... Apparently they have BaseName, FontName, CMapName
> directives different every time.
>
> @@ -751,7 +751,7 @@
> /CIDInit /ProcSet findresource begin
> 12 dict begin
> begincmap
> -/CMapName /RXGTTZ+CMR17-UTF16 def
> +/CMapName /WEUQPZ+CMR17-UTF16 def
> /CMapType 2 def
> /CIDSystemInfo <<
> /Registry (Adobe)
Sorry, I overlooked one snippet from my Makefile:
%.$(OUTEXT).new: %.$(OUTEXT)
egrep -a -v '/BaseFont|/FontName|/UniqueID|/ID|/CreationDate' $< > $@
And then I check the difference between $file.pdf.new and
$file.pdf.comp. This worked for me with the pdfTeX in teTeX 2.0.2, but
/CMapName obviously must be added, either for dvipdfmx or also for newer
pdfTeX versions.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
Reply to: