- ntg-pdftex - NTG Mailing Lists

[ pdftex-Feature Requests-385 ] \ptexnoligatures should leave kerning intact
by noreply＠sarovar.org 15 Feb '06

15 Feb '06

Feature Requests item #385, was opened at 2005-07-10 17:38 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=385&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: \ptexnoligatures should leave kerning intact Initial Comment: % The new \ptexnoligatures primitive will break the % horizontal positioning of \mathaccents if the base % character is slanted. % There is no problem with \accent, nor with \mathaccent % on upright characters: $\dot{A} \dot{\rm{A}} \dot{\Delta} \dot{\mit\Delta}$ {\tenit \accent'137 A} \ptexnoligatures\tenit % OK \ptexnoligatures\textfont0 % = cmr10, \rm % OK \ptexnoligatures\textfont1 % = cmmi10, \mit % breaks shift $\dot{A} \dot{\rm{A}} \dot{\Delta} \dot{\mit\Delta}$ {\tenit \accent'137 A} \bye, Robert ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-02-15 10:17 Message: Logged In: YES user_id=1608 We can disallow the primitive in non-vertical mode. Makes sense. ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-15 10:10 Message: Logged In: YES user_id=3344 Another limitation which should be documented: If \ptexnoligatures is applied within a paragraph, the ligs and kerns created and inserted before this command are removed depending if a hyphenation pass is necessary to justify the paragraph. \ptexnoligatures has the _global_ side effect to suppress all ligs and kerns of the font which are created _afterwards in time_. TeX breaks the lines of a paragraph at the end of the paragraph. If hyphenation has to be applied, ligs are remapped to single chars, (implicit) kerns are removed ... and reconstituted afterwards using the font information valid at this (later) time. If the font info is changed in between, which is true if \ptexnoligatures is applied, already inserted ligs and kerns are removed. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-07-12 22:23 Message: Logged In: YES user_id=421 Changing this into a feature request. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-07-10 18:50 Message: Logged In: YES user_id=1608 This is because it (\ptexnoligatures) also disables the kerning information for the font. You'll have to accept that as a "known limitation" for now. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=385&group_id=106

1 0

poppler usage, autoconf
by Frank Küster 15 Feb '06

15 Feb '06

Hi, I've worked on the patch originally proposed at http://sarovar.org/tracker/index.php?func=detail&aid=474&group_id=106&atid=… I have rewritten the changes to the source files, so that they continue to use the xpdf code copy in the source tree and only use libpoppler if the compiler (or rather preprocessor) is called with -DPOPPLER. This version is attached. The harder part is the autoconf magic required for the switching, and not even writing autoconf (at least not yet), but rather incorporating the changes: On my system, "./reautoconf" does not work, instead complains: autoconf: invalid option -m I have $ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. Or is there a different way to regenerate configure after changes to its source files? TIA, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX)

4 7

[ pdftex-Feature Requests-385 ] \ptexnoligatures should leave kerning intact
by noreply＠sarovar.org 15 Feb '06

15 Feb '06

Feature Requests item #385, was opened at 2005-07-10 17:38 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=385&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) Summary: \ptexnoligatures should leave kerning intact Initial Comment: % The new \ptexnoligatures primitive will break the % horizontal positioning of \mathaccents if the base % character is slanted. % There is no problem with \accent, nor with \mathaccent % on upright characters: $\dot{A} \dot{\rm{A}} \dot{\Delta} \dot{\mit\Delta}$ {\tenit \accent'137 A} \ptexnoligatures\tenit % OK \ptexnoligatures\textfont0 % = cmr10, \rm % OK \ptexnoligatures\textfont1 % = cmmi10, \mit % breaks shift $\dot{A} \dot{\rm{A}} \dot{\Delta} \dot{\mit\Delta}$ {\tenit \accent'137 A} \bye, Robert ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-15 10:10 Message: Logged In: YES user_id=3344 Another limitation which should be documented: If \ptexnoligatures is applied within a paragraph, the ligs and kerns created and inserted before this command are removed depending if a hyphenation pass is necessary to justify the paragraph. \ptexnoligatures has the _global_ side effect to suppress all ligs and kerns of the font which are created _afterwards in time_. TeX breaks the lines of a paragraph at the end of the paragraph. If hyphenation has to be applied, ligs are remapped to single chars, (implicit) kerns are removed ... and reconstituted afterwards using the font information valid at this (later) time. If the font info is changed in between, which is true if \ptexnoligatures is applied, already inserted ligs and kerns are removed. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-07-12 22:23 Message: Logged In: YES user_id=421 Changing this into a feature request. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-07-10 18:50 Message: Logged In: YES user_id=1608 This is because it (\ptexnoligatures) also disables the kerning information for the font. You'll have to accept that as a "known limitation" for now. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=385&group_id=106

1 0

Re: [NTG-pdftex] poppler usage, autoconf
by Thomas Esser 15 Feb '06

15 Feb '06

> However, only if I'm sure that we will be able to incorporate this into > the standalone pdftex tarball, and into texlive. Is there any > documentation how Peter did it, and what needs to be done for simple > updates? He has put his material (patches + instructions; both excellent) here: ftp://ftpth.mppmu.mpg.de/pub/peb/web2c/autoconf/ Peter has also contacted several authors IIRC, so he might have additional information beyond this. And, as I already wrote, my current stuff is available from rsync://tug.org/tetexdevsrc/ and the migration has already happened there (Peter, I'd be happy if you look at this). > And are there any binaries in texlive that aren't in the teTeX > tree and already converted? I am not aware of any. Peter? Thomas

1 0

[ pdftex-Patches-93 ] \quitvmode
by noreply＠sarovar.org 14 Feb '06

14 Feb '06

Patches item #93, was opened at 2004-07-15 12:12 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106 Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: \quitvmode Initial Comment: The change file adds a new primitive called \quitvmode. In vertical modes, it is identical to \indent, but in horizontal and math modes it is \noindent. See http://www.metatex.org/web/quitvmode.html ---------------------------------------------------------------------- >Comment By: Taco Hoekwater (taco) Date: 2006-02-14 13:20 Message: Logged In: YES user_id=1608 http://www.metatex.org/web/quitvmode.html Bernd, this is a repository for patches. Discussion normally takes place on the ntg-pdftex mailing list, not here. Cheers, Taco ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-14 13:02 Message: Logged In: YES user_id=3344 IMHO the name should include a \...indent to be consistent with the existing \indent/\noindent, if this primitive has similar functionality. And why not using a macro solution? (This means that I ask to please add a small rationale when introducing new primitives.) \def\quitvmode{% \ifvmode \indent \else \noindent \fi} If I make this a \protected\def (using e-\TeX) this will also cover the cases where TeX is looking ahead and expanding tokens (i.e., inside alignments looking for \omit, \span etc.). Is there any unseen advantage of the new primitive not covered by this macro resp. plain's \leavevmode macro? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-05-13 16:42 Message: Logged In: YES user_id=421 This has been included in 1.21a ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106

1 0

[ pdftex-Patches-93 ] \quitvmode
by noreply＠sarovar.org 14 Feb '06

14 Feb '06

Patches item #93, was opened at 2004-07-15 12:12 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106 Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: Martin Schröder (oneiros) Assigned to: The Thanh Han (hanthethanh) Summary: \quitvmode Initial Comment: The change file adds a new primitive called \quitvmode. In vertical modes, it is identical to \indent, but in horizontal and math modes it is \noindent. See http://www.metatex.org/web/quitvmode.html ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-14 13:02 Message: Logged In: YES user_id=3344 IMHO the name should include a \...indent to be consistent with the existing \indent/\noindent, if this primitive has similar functionality. And why not using a macro solution? (This means that I ask to please add a small rationale when introducing new primitives.) \def\quitvmode{% \ifvmode \indent \else \noindent \fi} If I make this a \protected\def (using e-\TeX) this will also cover the cases where TeX is looking ahead and expanding tokens (i.e., inside alignments looking for \omit, \span etc.). Is there any unseen advantage of the new primitive not covered by this macro resp. plain's \leavevmode macro? ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-05-13 16:42 Message: Logged In: YES user_id=421 This has been included in 1.21a ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=93&group_id=106

1 0

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

14 Feb '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: Accepted 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. ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-14 08:17 Message: Logged In: YES user_id=3344 IMHO it would be better to rephrase the above to (and change the implementation accordingly :-(): <quote mode="changed"> \primitive is expandable, because it may asked to execute expandable primitives as well as unexpandable ones. \primitive<cs> will expand to one token, the original TeX primitive. This token will then be processed further as usual. </quote> If \primitive is left unexpandable, a lot of programming techniques seems to be unavailable, e.g., all redefined expandable primitives in expandable-only context. Or any assignment to the get the original primitive, like \edef\orignumber{\expandafter\noexpand\primitive\number} \expandafter\let\expandafter\orignumber\primitive\number Sidenote: The new \primitive seems to implement a subset of a full-blown namespace mechanism. If (pdf)TeX would have namespaces, one simply has to access the appropriate token within the "primitive" namespace (e.g. \primitive::number to access the original \number primitive, assuming the notation \<namespace>::<csname>). How about choosing an appropriate namespace mechanism for (pdf)TeX and implementing it instead? ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-02-13 18:56 Message: Logged In: YES user_id=1608 We need to think about this. I see your point, but making \primitive expandable forces the introduction of un-redefinable tokens, and that has its own problematic side-effects (like slowing down each and every definition). I welcome third opinions on whether the benefits outweigh that downside. At one point I tried making the expandability depend on the referred primitive, but that gave me headaches at the implementation stage (a pity, because that would have been nice). Yet another solution is to have an expandable command as well as an unexpandable command (two primitives instead of just the single \primitive). On the side note: I will happily write an implementation ... but only if someone comes up with a specification that works under all conditions instead of only under specific programming styles :-) ---------------------------------------------------------------------- Comment By: Bernd Raichle (bernd) Date: 2006-02-13 17:40 Message: Logged In: YES user_id=3344 IMHO it would be better to rephrase the above to (and change the implementation accordingly :-(): <quote mode="changed"> \primitive is expandable, because it may asked to execute expandable primitives as well as unexpandable ones. \primitive<cs> will expand to one token, the original TeX primitive. This token will then be processed further as usual. </quote> If \primitive is left unexpandable, a lot of programming techniques seems to be unavailable, e.g., all redefined expandable primitives in expandable-only context. Or any assignment to the get the original primitive, like \edef\orignumber{\expandafter\noexpand\primitive\number} \expandafter\let\expandafter\orignumber\primitive\number Sidenote: The new \primitive seems to implement a subset of a full-blown namespace mechanism. If (pdf)TeX would have namespaces, one simply has to access the appropriate token within the "primitive" namespace (e.g. \primitive::number to access the original \number primitive, assuming the notation \<namespace>::<csname>). How about choosing an appropriate namespace mechanism for (pdf)TeX and implementing it instead? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=466&group_id=106

1 0

Re: [NTG-pdftex] 1.40 Manual (was 1.40 Schedule)
by Akira Kakuto 14 Feb '06

14 Feb '06

> 1. '-etex' cmdline switch is already mentioned in 'pdftex --help' but I > couldn't force it to work; the option is 'not recognized' during format > creation (pdftex-beta, 1.40.0, 13.02.2006 compiled under Cygwin). -etex is effective on my w32 binary. I investigated the difference: Best, Akira --- texmfmp.c.org Wed Jan 04 03:12:46 2006 +++ texmfmp.c Tue Feb 14 10:14:15 2006 @@ -42,8 +42,6 @@ #include <etexdir/etexextra.h> #elif defined (pdfTeX) #include <pdftexdir/pdftexextra.h> -#elif defined (pdfeTeX) -#include <pdfetexdir/pdfetexextra.h> #elif defined (Omega) #include <omegadir/omegaextra.h> #elif defined (eOmega) @@ -148,7 +146,7 @@ static int eightbitp; #endif /* Omega || eOmega || Aleph */ -#if defined(pdfTeX) || defined(pdfeTeX) +#if defined(pdfTeX) char *ptexbanner; #endif @@ -180,7 +178,7 @@ /* Must be initialized before options are parsed. */ interactionoption = 4; -#if defined(pdfTeX) || defined(pdfeTeX) +#if defined(pdfTeX) ptexbanner = BANNER; #endif @@ -264,7 +262,7 @@ fprintf(stderr, "-enc only works with -ini\n"); } #endif -#if defined(eTeX) || defined(pdfeTeX) || defined(Aleph) +#if defined(eTeX) || defined(pdfTeX) || defined(Aleph) if (etexp) { fprintf(stderr, "-etex only works with -ini\n"); } @@ -774,14 +772,14 @@ { "mltex", 0, &mltexp, 1 }, { "enc", 0, &enctexp, 1 }, #endif /* !Omega && !eOmega && !Aleph */ -#if defined (eTeX) || defined(pdfeTeX) || defined(Aleph) +#if defined (eTeX) || defined(pdfTeX) || defined(Aleph) { "etex", 0, &etexp, 1 }, -#endif /* eTeX || pdfeTeX || Aleph */ +#endif /* eTeX || pdfTeX || Aleph */ { "output-comment", 1, 0, 0 }, { "output-directory", 1, 0, 0 }, -#if defined(pdfTeX) || defined(pdfeTeX) +#if defined(pdfTeX) { "output-format", 1, 0, 0 }, -#endif /* pdfTeX or pdfeTeX */ +#endif /* pdfTeX */ { "shell-escape", 0, &shellenabledp, 1 }, { "no-shell-escape", 0, &shellenabledp, -1 }, { "debug-format", 0, &debugformatfile, 1 }, @@ -895,7 +893,7 @@ parse_src_specials_option(optarg); } #endif /* TeX */ -#if defined(pdfTeX) || defined(pdfeTeX) +#if defined(pdfTeX) } else if (ARGUMENT_IS ("output-format")) { pdfoutputoption = 1; if (strcmp(optarg, "dvi") == 0) { @@ -906,7 +904,7 @@ WARNING1 ("Ignoring unknown value `%s' for --output-format", optarg); pdfoutputoption = 0; } -#endif /* pdfTeX || pdfeTeX */ +#endif /* pdfTeX */ #if defined (TeX) || defined (MF) || defined (MP) } else if (ARGUMENT_IS ("translate-file")) { translate_filename = optarg; @@ -1610,7 +1608,7 @@ } /* FIXME -- some (most?) of this can/should be moved to the Pascal/WEB side. */ -#if !defined(pdfTeX) && !defined(pdfeTeX) +#if !defined(pdfTeX) static void checkpoolpointer (poolpointer poolptr, size_t len) {

1 0

[ pdftex-Bugs-481 ] "This can't happen (flushing)" with extra kerning+expansion+ligatures
by noreply＠sarovar.org 13 Feb '06

13 Feb '06

Bugs item #481, was opened at 2006-02-13 19:04 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=481&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: "This can't happen (flushing)" with extra kerning+expansion+ligatures Initial Comment: With the following test file, pdftex will abort with "This can't happen (flushing)": \pdfadjustspacing=1 \pdffontexpand\font 20 20 4 autoexpand \pdfappendkern=1 \knaccode\font`i=100 \hsize10em foo fii foo foo foo foo % but this works: %foo f{}ii foo foo foo foo \bye Hartmut's analysis was: ----------------------------------- FWIW, this happens in function do_subst_font(). But it starts with auto_expand_kern(), where the given kern indeed is appended to the i of "fi" and also to the 2nd "i". It seems as if at this time "fi" is not yet seen as a ligature. Then in do_subst_font() the "fi" is somehow already a ligature, and now the kern is part of the lig_ptr list (which is wrong). Then font(r) is recursively changed to 51, the expanded font number, and so the kern, which should not be in this list, gets the 51 as its type. But it must be 11 for a kern. Maybe a change should be that the kern does not end up in the lig_ptr list, but should come after the "fi" ligature. No idea, how. ----------------------------------- ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-02-13 21:25 Message: Logged In: YES user_id=929 My text above had a typo, sorry. Before you start searching... it's auto_append_kern(), not auto_expand_kern(). Regards, Hartmut ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=481&group_id=106

1 0

[ pdftex-Patches-462 ] HZ font expansion by text matrix manipulation
by noreply＠sarovar.org 13 Feb '06

13 Feb '06

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: Accepted Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: The Thanh Han (hanthethanh) 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 ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-02-13 19:41 Message: Logged In: YES user_id=421 The last word from Hartmut was that it's not ready yet and he'd be working on an improved version. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-02-13 19:05 Message: Logged In: YES user_id=2217 Will this make it into 1.40? I would love to see it included. I've tested it a bit and did not find any problems (I'm also using it for the pre-built microtype documentation on CTAN). Regards, Robert ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=462&group_id=106

1 0