- ntg-pdftex - NTG Mailing Lists

Re: [pdftex] Math Pdftex extensions ?
by Hans Hagen 15 Jan '06

15 Jan '06

Paul Pichaureau wrote: > Dear all, > > As I'm a fanatic a beautiful typography, I'm following your work on >pdftex with great attention, especially enjoying the pdftex extensions >already implemented (microtype and all the hz stuff). > > Anyway, I'm wondering if you plan to extend pdftex in order to >improve the mathematical typography of TeX. I'm developping a big set >of mathematical fonts (called mathdesign) and I'm quite aware of the >problems of TeX in this domain. > >I've precise points in mind: mathematical accents, radical with left >and right delimiters, and, of course, the insufficiencies of the tfm >format. But you already know that better than me. > >So, this is my question: is it planned to improve some of these points >in the future ? > > if you can point out the specific things that you want to be supported, the pdftex dev team can look into it after all, pdftex is also a playground for new tex functionality (within reasonable bounds) Hans

2 1

[ pdftex-Patches-469 ] \currentexpansionmode + \ifalignscanning - \ifinedef
by noreply＠sarovar.org 13 Jan '06

13 Jan '06

Patches item #469, was opened at 2006-01-12 02:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Morten Høgholm (morten) Assigned to: Nobody (None) Summary: \currentexpansionmode + \ifalignscanning - \ifinedef Initial Comment: Here's a patch made against pdftex-1.40.0-alpha-20060111. It removes the \ifinedef primitive for a different primitive, namely \currentexpansionmode. This read-only register is 0 when doing regular typesetting, 1 when inside \edef or \xdef and 2 in other cases of full expansion with scan_toks. It could possibly be extended to distinguish between \marks and \write etc. Comments more than welcome on this one! I have also added an \ifalignscanning test. It is true whenever TeX is looking for \noalign etc. so is most useful for a \stopalignscanning function defined as \def\stopalignscanning{\ifalignscanning\relax\fi} ---------------------------------------------------------------------- >Comment By: Morten Høgholm (morten) Date: 2006-01-13 05:50 Message: Logged In: YES user_id=3333 Yes, just ideas here, which is why I asked for comments. We can discuss this on the list (once my subscription is accepted). ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-01-12 11:22 Message: Logged In: YES user_id=1608 Like Hans, I also prefer separate if primitives, mainly because I do not want to have to remember the meanings of the possible integer values (for that reason, I'm not too happy about \currentgrouptype either). Taco ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-01-12 10:14 Message: Logged In: NO i wonder why we need \ifalignscanning or \stopalignscanner at all when eTeX already has this feature - any \protected macro stops the scanning. ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-01-12 09:08 Message: Logged In: YES user_id=927 somehow i think that if's are a better idea than a register because in your case the register only registers one case at the same time (when i saw this patch the first time, i wondered why not a complete set was implemented) - ifincsname - ifinedef - ifinwrite - ifinspecial - ifinpdfliteral - ifinannotbody - ifinmessage (special case of write) - ifinalign - ifinmark probably some more (ok, normally all those conditions can comfortably be catched in a macro package but if we add them, we should be complete in addition to this there can be a register which keeps track of the innermost one (we can have ifcsname inside an edef inside an align concerning the \stopalignscanner i think it's better to have something primitive like \crcr, say \endalign because using if's can have its own problem (we should not worry to much about a name clash, since one can always let it to another one); so, we should wait with adding this patches till (1) we agree and (2) it is complete remark: also, it's dangerous to add patched before a decent decission/interface is dediced upon; once it's in, we cannot change it any more Hans ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106

1 0

[ pdftex-Patches-469 ] \currentexpansionmode + \ifalignscanning - \ifinedef
by noreply＠sarovar.org 12 Jan '06

12 Jan '06

Patches item #469, was opened at 2006-01-12 02:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Morten Høgholm (morten) Assigned to: Nobody (None) Summary: \currentexpansionmode + \ifalignscanning - \ifinedef Initial Comment: Here's a patch made against pdftex-1.40.0-alpha-20060111. It removes the \ifinedef primitive for a different primitive, namely \currentexpansionmode. This read-only register is 0 when doing regular typesetting, 1 when inside \edef or \xdef and 2 in other cases of full expansion with scan_toks. It could possibly be extended to distinguish between \marks and \write etc. Comments more than welcome on this one! I have also added an \ifalignscanning test. It is true whenever TeX is looking for \noalign etc. so is most useful for a \stopalignscanning function defined as \def\stopalignscanning{\ifalignscanning\relax\fi} ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-01-12 11:22 Message: Logged In: YES user_id=1608 Like Hans, I also prefer separate if primitives, mainly because I do not want to have to remember the meanings of the possible integer values (for that reason, I'm not too happy about \currentgrouptype either). Taco ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-01-12 10:14 Message: Logged In: NO i wonder why we need \ifalignscanning or \stopalignscanner at all when eTeX already has this feature - any \protected macro stops the scanning. ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-01-12 09:08 Message: Logged In: YES user_id=927 somehow i think that if's are a better idea than a register because in your case the register only registers one case at the same time (when i saw this patch the first time, i wondered why not a complete set was implemented) - ifincsname - ifinedef - ifinwrite - ifinspecial - ifinpdfliteral - ifinannotbody - ifinmessage (special case of write) - ifinalign - ifinmark probably some more (ok, normally all those conditions can comfortably be catched in a macro package but if we add them, we should be complete in addition to this there can be a register which keeps track of the innermost one (we can have ifcsname inside an edef inside an align concerning the \stopalignscanner i think it's better to have something primitive like \crcr, say \endalign because using if's can have its own problem (we should not worry to much about a name clash, since one can always let it to another one); so, we should wait with adding this patches till (1) we agree and (2) it is complete remark: also, it's dangerous to add patched before a decent decission/interface is dediced upon; once it's in, we cannot change it any more Hans ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106

1 0

[ pdftex-Patches-469 ] \currentexpansionmode + \ifalignscanning - \ifinedef
by noreply＠sarovar.org 12 Jan '06

12 Jan '06

Patches item #469, was opened at 2006-01-12 07:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Morten Høgholm (morten) Assigned to: Nobody (None) Summary: \currentexpansionmode + \ifalignscanning - \ifinedef Initial Comment: Here's a patch made against pdftex-1.40.0-alpha-20060111. It removes the \ifinedef primitive for a different primitive, namely \currentexpansionmode. This read-only register is 0 when doing regular typesetting, 1 when inside \edef or \xdef and 2 in other cases of full expansion with scan_toks. It could possibly be extended to distinguish between \marks and \write etc. Comments more than welcome on this one! I have also added an \ifalignscanning test. It is true whenever TeX is looking for \noalign etc. so is most useful for a \stopalignscanning function defined as \def\stopalignscanning{\ifalignscanning\relax\fi} ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-01-12 14:44 Message: Logged In: NO i wonder why we need \ifalignscanning or \stopalignscanner at all when eTeX already has this feature - any \protected macro stops the scanning. ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-01-12 13:38 Message: Logged In: YES user_id=927 somehow i think that if's are a better idea than a register because in your case the register only registers one case at the same time (when i saw this patch the first time, i wondered why not a complete set was implemented) - ifincsname - ifinedef - ifinwrite - ifinspecial - ifinpdfliteral - ifinannotbody - ifinmessage (special case of write) - ifinalign - ifinmark probably some more (ok, normally all those conditions can comfortably be catched in a macro package but if we add them, we should be complete in addition to this there can be a register which keeps track of the innermost one (we can have ifcsname inside an edef inside an align concerning the \stopalignscanner i think it's better to have something primitive like \crcr, say \endalign because using if's can have its own problem (we should not worry to much about a name clash, since one can always let it to another one); so, we should wait with adding this patches till (1) we agree and (2) it is complete remark: also, it's dangerous to add patched before a decent decission/interface is dediced upon; once it's in, we cannot change it any more Hans ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106

1 0

[ pdftex-Patches-469 ] \currentexpansionmode + \ifalignscanning - \ifinedef
by noreply＠sarovar.org 12 Jan '06

12 Jan '06

Patches item #469, was opened at 2006-01-12 01:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Morten Høgholm (morten) Assigned to: Nobody (None) Summary: \currentexpansionmode + \ifalignscanning - \ifinedef Initial Comment: Here's a patch made against pdftex-1.40.0-alpha-20060111. It removes the \ifinedef primitive for a different primitive, namely \currentexpansionmode. This read-only register is 0 when doing regular typesetting, 1 when inside \edef or \xdef and 2 in other cases of full expansion with scan_toks. It could possibly be extended to distinguish between \marks and \write etc. Comments more than welcome on this one! I have also added an \ifalignscanning test. It is true whenever TeX is looking for \noalign etc. so is most useful for a \stopalignscanning function defined as \def\stopalignscanning{\ifalignscanning\relax\fi} ---------------------------------------------------------------------- >Comment By: Hans Hagen (hagen) Date: 2006-01-12 08:08 Message: Logged In: YES user_id=927 somehow i think that if's are a better idea than a register because in your case the register only registers one case at the same time (when i saw this patch the first time, i wondered why not a complete set was implemented) - ifincsname - ifinedef - ifinwrite - ifinspecial - ifinpdfliteral - ifinannotbody - ifinmessage (special case of write) - ifinalign - ifinmark probably some more (ok, normally all those conditions can comfortably be catched in a macro package but if we add them, we should be complete in addition to this there can be a register which keeps track of the innermost one (we can have ifcsname inside an edef inside an align concerning the \stopalignscanner i think it's better to have something primitive like \crcr, say \endalign because using if's can have its own problem (we should not worry to much about a name clash, since one can always let it to another one); so, we should wait with adding this patches till (1) we agree and (2) it is complete remark: also, it's dangerous to add patched before a decent decission/interface is dediced upon; once it's in, we cannot change it any more Hans ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106

1 0

[ pdftex-Patches-469 ] \currentexpansionmode + \ifalignscanning - \ifinedef
by noreply＠sarovar.org 12 Jan '06

12 Jan '06

Patches item #469, was opened at 2006-01-12 02:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Morten Høgholm (morten) Assigned to: Nobody (None) Summary: \currentexpansionmode + \ifalignscanning - \ifinedef Initial Comment: Here's a patch made against pdftex-1.40.0-alpha-20060111. It removes the \ifinedef primitive for a different primitive, namely \currentexpansionmode. This read-only register is 0 when doing regular typesetting, 1 when inside \edef or \xdef and 2 in other cases of full expansion with scan_toks. It could possibly be extended to distinguish between \marks and \write etc. Comments more than welcome on this one! I have also added an \ifalignscanning test. It is true whenever TeX is looking for \noalign etc. so is most useful for a \stopalignscanning function defined as \def\stopalignscanning{\ifalignscanning\relax\fi} ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=469&group_id=106

1 0

pdftex-1.40.0-alpha-20060111
by Martin Schröder 11 Jan '06

11 Jan '06

http://sarovar.org/download.php/895/pdftex-1.40.0-alpha-20060106-20060111.d… http://sarovar.org/download.php/896/pdftex-1.40.0-alpha-20060111.tar.bz2 - new patches: - 466 \primitive and \ifprimitive - 467 \ifinedef - improved patches: - 393 Ensure newline before endstream - pdfTeX now sets /ModDate and /Trapped by default (the values can be overridden with /pdfinfo) - more fixes to remove warnings from -Wall Have fun Martin -- http://www.tm.oneiros.de

1 0

pdftex-1.40.0-alpha-20060106
by Martin Schröder 10 Jan '06

10 Jan '06

http://sarovar.org/download.php/890/pdftex-1.40.0-alpha-20051226-20060106.d… http://sarovar.org/download.php/891/pdftex-1.40.0-alpha-20060106.tar.bz2 - many small fixes to remove warnings from -Wall - removed some unused variables - really fix bug 444 - add some GCC extensions and use *nprintf instead of *printf where possible - fixed a unicode bug in ttf2afm Have fun Martin -- http://www.tm.oneiros.de

2 2

[ pdftex-Patches-467 ] new primitive \ifinedef
by noreply＠sarovar.org 10 Jan '06

10 Jan '06

Patches item #467, was opened at 2006-01-10 04:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=467&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: new primitive \ifinedef Initial Comment: This patch (by Morten Høgholm) contains improvement for the \ifincsname primitive and implements a new similar primitive \ifinedef. Made against pdftex-1.40.0-alpha-20060106 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=467&group_id=106

1 0

/ModDate and /Trapped (was: [pdftex] PDFX3 Standard)
by Martin Schröder 09 Jan '06

09 Jan '06

On 2003-10-27 12:32:06 +0100, Martin Schröder wrote: > On 2003-10-27 12:38:19 +0100, Siep Kroonenberg wrote: > > /ModDate (D:\pdfdate) > > Will set this in the next version > > > /Trapped (False) > > Another primitive... :-{ Hi, we forgot about /ModDate and /Trapped. Any objections against setting /ModDate to the same value as /CreationDate per default? And should we also default /Trapped to /False? Best Martin -- http://www.tm.oneiros.de

3 6

[ pdftex-Bugs-393 ] Ensure newline before endstream
by noreply＠sarovar.org 07 Jan '06

07 Jan '06

Bugs item #393, was opened at 2005-07-25 16:09 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=393&group_id=106 Category: None Group: v1.30.0 Status: Open Resolution: None Priority: 2 Submitted By: Martin Schröder (oneiros) Assigned to: Martin Schröder (oneiros) Summary: Ensure newline before endstream Initial Comment: As reported by Hans, there is not always a newline before endstream, although the PDF reference recommends it. Any change needs careful testing. ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-01-06 23:45 Message: Logged In: YES user_id=929 Implementation of pdf_end_stream() changed: Last byte within any stream written to the PDF file is now remembered in pdf_last_byte, so that one can check if a separate pdf_new_line_char "\n" is needed before "endstream". No need to look back in maybe already flushed pdfbuf. Patch to 1.40.0-alpha-20060106. Plus a few tiny patches. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=393&group_id=106

2 1

[ pdftex-Patches-466 ] \primitive and \ifprimitive
by noreply＠sarovar.org 07 Jan '06

07 Jan '06

Patches item #466, was opened at 2006-01-07 17:22 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=466&group_id=106 Category: Primitives Group: v1.40.0 Status: Open Resolution: None Priority: 4 Submitted By: Taco Hoekwater (taco) Assigned to: Martin Schröder (oneiros) Summary: \primitive and \ifprimitive Initial Comment: This patch implements two new primitives: \primitive \par This will run the 'primitive' command \par, even if it has been re- or undefined in the meantime. \primitive is not expandable, because it may be asked to execute unexpandable primitives as well as expandable ones. If you supply a nonexistant primitive, it will be ignored (no error is raised). The second primitive is a new type of \if: \ifprimitive \par ... \else .. \fi returns true if the current meaning of \par is the 'primitive' command \par. The patch is against alpha-20051226, i hope that is not too old (?). I expect to do at least one minor update during the beta cycle, after the pdftex code is flattened. It was quite a struggle to make this change file work ok, and as a result, there are a few ugly web hacks. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=466&group_id=106

2 1

[ pdftex-Bugs-465 ] font expansion & \lastlinefit
by noreply＠sarovar.org 07 Jan '06

07 Jan '06

Bugs item #465, was opened at 2006-01-03 20:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106 Category: hz >Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion & \lastlinefit Initial Comment: With \lastlinefit > 0, the last line will always be expanded to the maximum (except if it doesn't contain a glue). Furthermore, I wonder whether \lastlinefit should ideally also effect the expansion amount (ie., the last line of the first paragraph should be set in cmr10-25, since the preceding one is set in cmr10-50)? \tracingoutput1 \showboxbreadth\maxdimen \pdftracingfonts1 \pdfadjustspacing2 \pdffontexpand\font 50 50 10 autoexpand \lastlinefit500 \hsize=16cm \input tufte\par \bye, Robert ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106

1 0

Re: [NTG-pdftex] pdftex-1.40.0-alpha-20060106
by Akira Kakuto 07 Jan '06

07 Jan '06

Hi Martin, > http://sarovar.org/download.php/890/pdftex-1.40.0-alpha-20051226-20060106.d… > http://sarovar.org/download.php/891/pdftex-1.40.0-alpha-20060106.tar.bz2 > > - many small fixes to remove warnings from -Wall > ... Please change tex-make.c as follows, though the corrected lines are rarely used in real life. Thanks Akira --- tex-make.c.orig Wed Dec 28 01:15:25 2005 +++ tex-make.c Sat Jan 07 08:27:10 2006 @@ -30,8 +30,9 @@ #include <kpathsea/readable.h> #include <kpathsea/tex-make.h> #include <kpathsea/variable.h> -#include <sys/wait.h> - +#ifndef WIN32 +# include <sys/wait.h> +#endif /* We never throw away stdout, since that is supposed to be the filename found, if all is successful. This variable controls whether stderr @@ -67,13 +68,13 @@ if (f > 1) { if (r > 0) { - sprintf(q, "%u+%u/(%u*%u + %u)", + sprintf(q, "%u+%u/(%u*%u+%u)", dpi/bdpi, dpi%bdpi, f, (bdpi - r)/f, r); } else { sprintf(q, "%u+%u/(%u*%u)", dpi/bdpi, dpi%bdpi, f, bdpi/f); } } else { - sprintf(q, "%u+%u/(4000 + %u)", dpi/bdpi, dpi%bdpi, bdpi); + sprintf(q, "%u+%u/(4000+%u)", dpi/bdpi, dpi%bdpi, r); } } } else {

2 1

Re: [NTG-pdftex] various features
by Thanh Han The 07 Jan '06

07 Jan '06

On Fri, Jan 06, 2006 at 07:14:16PM +0100, Hans Hagen wrote: > Martin ??? wrote: > > >On 2006-01-06 05:53:35 -0800, The Thanh Han wrote: > > > > > >>the patch I uploaded still has some problems with > >>auto prepending/appending kerns, so it is better to leave > >>them out for the moment. I will try to split the patch into > >>smaller patches so Martin can decide which one(s) should go > >>into official releases. > >> > >> > > > >I'm tempted to leave it in, as getting it in was quite some work > >-- and getting it out will probably be even more. Does it break > >any old features? If not, it can stay. We can always declare > >these features as experimental. > > > > > i agree with this those new features don't break things unless they are used (like hz or margin kerning). But they are not documented yet, probably only Hans and Robert are aware of them. So if we can live with that, it can stay. Makes our life simpler. Thanh

1 0

[ pdftex-Patches-453 ] Object Streams for PDF-1.5
by noreply＠sarovar.org 07 Jan '06

07 Jan '06

Patches item #453, was opened at 2005-11-26 18:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=453&group_id=106 Category: Object Streams Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: Object Streams for PDF-1.5 Initial Comment: Rough early patch, work in progress, produces PDF-1.5 object streams and cross reference streams. With the patch, and enabled by \pdfminorversion=5, and with luck, pdfetex produces e. g. from its WEB source a PDF file with size 5.97 MByte instead of 11.2 MByte without object streams. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-01-07 01:06 Message: Logged In: YES user_id=929 objstream.ch updated: 1. object stream statistics added. 2. maximum allocation values are added in brackets. Example: PDF statistics: 630 PDF objects out of 1000 (max. 8388607) 577 compressed objects within 6 object streams 113 named destinations out of 1000 (max. 131072) 8353 words of extra memory for PDF output out of 10000 (max. 10000000) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-12-26 20:21 Message: Logged In: YES user_id=929 Patch update. Object stream writing is now controlled by primitive \pdfobjcompresslevel = 0...3 (/pdfobjectstreams primitive removed). 0 = no object streams at all, 1 = compress objects excluding the ones from embedded PDF files (for handling of problematic PDF files) and /Info dictionary (for legibility), 2 = also compress objects from embedded PDF files, but leave /Info uncompressed, 3 = compress everything. Testing welcome. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=453&group_id=106

1 0

Re: [NTG-pdftex] various features
by Thanh Han The 06 Jan '06

06 Jan '06

Hi, the patch I uploaded still has some problems with auto prepending/appending kerns, so it is better to leave them out for the moment. I will try to split the patch into smaller patches so Martin can decide which one(s) should go into official releases. Thanh On Tue, Dec 20, 2005 at 10:17:50AM +0900, Akira Kakuto wrote: > > On 2005-12-19 14:16:49 +0100, Hans Hagen wrote: > > > Are all Than's recent patches included? Like the \pdfprependkern and > > > alike stuff? > > > > No. But I included all I got. > > > > Thanh? > > http://pdftex.sarovar.org/src/pdftex-20050924.patch.gz > > Please include the above patch by Thanh > which defines \pdfprependkern etc. > I'm personally using the subfont mechanism > in the patch to typeset Japanese. > The patch is for 1.30.3. So some hand work will be needed. > > Thanks, > Akira

3 2

Re: [NTG-pdftex] pdftex-1.40.0-alpha-20051226
by Thanh Han The 06 Jan '06

06 Jan '06

On Tue, Dec 27, 2005 at 09:39:39AM +0100, Hartmut Henkel wrote: > do we really want GNUish indentation? like > > if (strcmp (fp->tfm_name, nontfm) != 0) > { > p = (fm_entry *) avl_find (tfm_tree, fp); > if (p != NULL) > { > if (mode == FM_DUPIGNORE) > > i would prefer K%26R (--k-and-r-style): > > if (strcmp(fp->tfm_name, nontfm) != 0) { > p = (fm_entry *) avl_find(tfm_tree, fp); > if (p != NULL) { > if (mode == FM_DUPIGNORE) { so do I. Regards, Thanh

1 0

cmd line arguments
by Reinhard Kotucha 06 Jan '06

06 Jan '06

Hi, I got the latest issue of TUGboat today and read Hans' article about LuaTeX with great interest. Obviously Hans had the enhancement of [pdf]TeX in mind. But I think that much more can be done with it. Given that LuaTeX allows shell-escapes, I think that it makes a lot of sense to replace some Perl scripts by LuaTeX. For instance, Heiko fixed two bugs in epstopdf I reported but I did not get any response from the author of the C-version which still resides on CTAN. http://ctan.org/tex-archive/support/epstopdf This version is still broken. TeXLive does not provide Perl for Windows users and I suppose that MikTeX doesn't as well. Instead, binaries are provided. If someone detects a bug, a fixed Perl script can be provided for UNIX users immediately but Windows users still depend on someone who provides new binaries. Though I like Perl very much I think that LuaTeX is quite great. It can be make things much more portable. Suppose that someone ports epstopdf to LuaTeX, then Windows users can update easily. There is one problem concerning how [pdf]TeX reads the command line. [pdf]TeX expects a filename and considers all arguments which come before the filename as options. It complains if an option is not known. However, options after the filename are accessible by TeX. Try the following file: getargs.tex __________________________________________________________________ \def\OptionPrefix{-} \newlinechar=`\^^J \def\echo#1{\message{^^J#1}} \def\car#1#2\\{#1}\def\cdr#1#2\\{#2} \def\DefineOption#1#2{\expandafter\def\csname:opt:#1\endcsname{#2}} \def\ProcessOption#1{\csname:opt:#1\endcsname} \def\ProcessFile#1{\echo{File: "#1"}} \def\TestOption#1{% \expandafter\ifx\csname:opt:#1\endcsname\relax \echo{Unknown Option "#1", ignored} \else \ProcessOption{#1} \fi } \def\GetArg#1 {\setbox0=\lastbox\endgraf \if\OptionPrefix\car#1\\ \edef\Arg{\cdr#1\\} \TestOption\Arg \else \ProcessFile{#1}\expandafter\end \fi } %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \DefineOption{abc}{\echo{Known Option "abc"}} \DefineOption{def}{\echo{Known Option "def"}} \everypar{\GetArg} __________________________________________________________________ When I say tex -abc getargs -def -uvw xyz I get: $ tex -abc getargs -def -uvw xyz tex: unrecognized option `-abc' This is TeX, Version 3.141592 (Web2C 7.5.4) (./getargs.tex) Known Option "def" Unknown Option "uvw", ignored File: "xyz" No pages of output. Transcript written on getargs.log. Though it is good that TeX makes all arguments available to TeX which come after the filename, there is a problem if getargs is a format file. In this case the command line looks like getargs -abc -def -uvw xyz and everything before "xyz" is lost. In other words, if you say epstopdf -hires myfile.eps TeX will complain epstopdf: unrecognized option `-hires.' How can this problem be fixed? The current behaviour of web2c is absolutely correct but I assume that LuaTeX users need a bit more. Is it possible to convince [pdf]TeX to ignore unknown options for particular format files by adding some lines to texmf.cnf similar to TEXINPUTS.latex = ... which disable commandline option checking and pass everything to TeX? Another point: It would be nice if LuaTeX allows shell-escapes. This might be regarded as beeing unsecure. What about having a list of trusted programs in texmf.cnf? Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------

2 4

[ pdftex-Bugs-444 ] buffer overflow with \pdfmatch
by noreply＠sarovar.org 03 Jan '06

03 Jan '06

Bugs item #444, was opened at 2005-10-29 17:24 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=444&group_id=106 Category: None Group: v1.30.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: Martin Schröder (oneiros) Summary: buffer overflow with \pdfmatch Initial Comment: % The new \pdfmatch primitive will run into a buffer overflow with strings % longer than 1023 characters: % % (I am using 1.30.3 with Thanh's patches from pdftex.sarovar.org/src, % compiled under cygwin.) \def\x{1,2,3,4,5,6,7,8,9,0,} \def\testlist{% ,\x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x\x\x\x\x \x00,}% 1024 \ifcase\pdfmatch{,1,}{\testlist}\relax \fi % Also, if the pattern is too long: %\ifcase\pdfmatch{\testlist}{1}\relax \fi \bye, Robert. PS: Is there a simple way to escape all regex special characters in a string? ---------------------------------------------------------------------- >Comment By: Robert (schlcht) Date: 2006-01-03 19:03 Message: Logged In: YES user_id=2217 Hm, not really... The test case above still fails with both 1.30.5 and 1.40.0-alpha. Regards, Robert. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-12-04 14:12 Message: Logged In: YES user_id=421 This has been fixed in 1.30.5 ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2005-10-29 19:08 Message: Logged In: YES user_id=929 see patch to utils.c. This makes makecstring() memory grow on demand. Also increase MAX_CSTRING_LEN in ptexmac.h to e. g. 10000000. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=444&group_id=106

2 1

[ pdftex-Bugs-465 ] font expansion & \lastlinefit
by noreply＠sarovar.org 03 Jan '06

03 Jan '06

Bugs item #465, was opened at 2006-01-03 19:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106 Category: hz Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: font expansion & \lastlinefit Initial Comment: With \lastlinefit > 0, the last line will always be expanded to the maximum (except if it doesn't contain a glue). Furthermore, I wonder whether \lastlinefit should ideally also effect the expansion amount (ie., the last line of the first paragraph should be set in cmr10-25, since the preceding one is set in cmr10-50)? \tracingoutput1 \showboxbreadth\maxdimen \pdftracingfonts1 \pdfadjustspacing2 \pdffontexpand\font 50 50 10 autoexpand \lastlinefit500 \hsize=16cm \input tufte\par \bye, Robert ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=465&group_id=106

1 0

pdftex-1.40.0-alpha-20051221
by Martin Schröder 27 Dec '05

27 Dec '05

http://sarovar.org/download.php/866/pdftex-1.40.0-alpha-20051208-20051221.d… http://sarovar.org/download.php/867/pdftex-1.40.0-alpha-20051221.tar.bz2 - has a large patch from Thanh - pdflastlink has been fixed - remove generated pdf in case of fatal error Have fun Martin -- http://www.tm.oneiros.de

3 3

pdftex-1.40.0-alpha-20051226
by Martin Schröder 27 Dec '05

27 Dec '05

http://sarovar.org/download.php/872/pdftex-1.40.0-alpha-20051221-20051226.d… http://sarovar.org/download.php/873/pdftex-1.40.0-alpha-20051226.tar.bz2 - improved patches: - 453 Object Streams for PDF-1.5 - take PK resolution from "pk_dpi" parameter in texmf.cnf, if it has not been set by the format file or by the user - 432 Rules in a PDF qQ group - some fixes for Thanhs patch - some improvements from -Wall - .indent.pro for indent -- http://www.tm.oneiros.de

2 1

[ pdftex-Patches-453 ] Object Streams for PDF-1.5
by noreply＠sarovar.org 26 Dec '05

26 Dec '05

Patches item #453, was opened at 2005-11-26 18:05 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=453&group_id=106 Category: Object Streams Group: v1.30.0 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: Object Streams for PDF-1.5 Initial Comment: Rough early patch, work in progress, produces PDF-1.5 object streams and cross reference streams. With the patch, and enabled by \pdfminorversion=5, and with luck, pdfetex produces e. g. from its WEB source a PDF file with size 5.97 MByte instead of 11.2 MByte without object streams. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2005-12-26 20:21 Message: Logged In: YES user_id=929 Patch update. Object stream writing is now controlled by primitive \pdfobjcompresslevel = 0...3 (/pdfobjectstreams primitive removed). 0 = no object streams at all, 1 = compress objects excluding the ones from embedded PDF files (for handling of problematic PDF files) and /Info dictionary (for legibility), 2 = also compress objects from embedded PDF files, but leave /Info uncompressed, 3 = compress everything. Testing welcome. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=453&group_id=106

1 0

[ pdftex-Patches-462 ] HZ font expansion by text matrix manipulation
by noreply＠sarovar.org 23 Dec '05

23 Dec '05

Patches item #462, was opened at 2005-12-23 23:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=462&group_id=106 Category: Positioning Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: Nobody (None) Summary: HZ font expansion by text matrix manipulation Initial Comment: Use textmatrix Tm instead of /FontMatrix for font expansion. Then a font file will be embedded only once for all expansion factors. Gives smaller PDF files. Works then also for non-embedded fonts. TrueType not tried yet. Rough patch only, incomplete, work in progress, no warranty, not for production. Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=462&group_id=106

1 0