- ntg-pdftex - NTG Mailing Lists

[ 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