- ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-719 ] few buglets in build.sh
by noreply＠sarovar.org 07 Jan '07

07 Jan '07

Bugs item #719, was opened at 2007-01-02 04:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106 Category: Build process Group: v1.40.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sanjoy Mahajan (sanjoy) Assigned to: Martin Schröder (oneiros) Summary: few buglets in build.sh Initial Comment: Just compiled 1.40.0 using build.sh. I had to make a few changes to get it to run on my system (Ubuntu 6.10, i386). The purpose of the chunks in the attached diff: 1. The JOBS variable wasn't used, so I changed its name be descriptive for parallel builds, and used it (and a related load variable) in the line that appends to the MAKE variable. Also, without the necessary double quotes around that line, the rest of the line after $MAKE is interpreted as a command rather than as stuff to append to MAKE (run build.sh with "--parallel" to see the problem). I used the short option names for make, to keep the line within 80 chars. 2. "-a build" is an (incomplete) AND statement, rather than a test for the "build" directory existing. The test should be "-e build" to check for existence. 3. Brace expansion is suboptimal in sh and not very portable to different reimplementations of sh. According to the bash man page: "Brace expansion introduces a slight incompatibility with historical versions of sh. sh does not treat opening or closing braces specially when they appear as part of a word, and preserves them in the output. Bash removes braces from words as a consequence of brace expansion. For example, a word entered to sh as file{1,2} appears identically in the output." I don't know the full story, but the fake sh on my system (actually 'dash') doesn't do brace expansion at all. And if the bash man page is right, even if it did the expansion, it wouldn't help since build.sh uses braces in the middle of a word. So I rewrote the two uses of brace expansion to avoid it. The resulting "build.sh --parallel" worked fine in my limited tests. It still complained that it couldn't find the texmf tree, but I figure that's okay since pdftex'll eventually (I hope) use kpathsea and texmf.cnf. -Sanjoy ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-01-07 22:41 Message: Logged In: YES user_id=421 Thanks. I'll include your changes in the next version. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106

1 0

Re: [NTG-pdftex] [tex-live] \pdffontattr in pdftex-1.40.0-rc4
by Thanh Han The 06 Jan '07

06 Jan '07

Hi, sorry for the late response. The patch by Hartmut should solve the problem. to Hartmut: > > > pdfTeX warning (\pdffontattr): font \^^@ has conflicting attributes > is this a nullfont? how does one get it? this font has been loaded from a virtual font, hence it doesn't get any control sequence. I made another patch, which is more or less the same as what Hartmut did, plus some changes to make the warning more meaningful. Don't be afraid by the length of the patch, it just turns the module @<Print the font identifier for |font(p)|@> to a function named print_font_identifier() so it can be called with different parameters. Thanh --- /home/thanh/s2/pdftex.web 2006-12-20 16:16:42.000000000 +0100 +++ pdftex.web 2007-01-04 18:26:42.000000000 +0100 @@ -4062,7 +4062,33 @@ @ Boxes, rules, inserts, whatsits, marks, and things in general that are sort of ``complicated'' are indicated only by printing `\.{[]}'. -@p procedure short_display(@!p:integer); {prints highlights of list |p|} +@p +procedure print_font_identifier(f: internal_font_number); +begin + if pdf_font_blink[f] = null_font then + print_esc(font_id_text(f)) + else + print_esc(font_id_text(pdf_font_blink[f])); + if pdf_tracing_fonts > 0 then begin + print(" ("); + print(font_name[f]); + if font_size[f] <> font_dsize[f] then begin + print("@@"); + print_scaled(font_size[f]); + print("pt"); + end; + print(")"); + end else + if pdf_font_expand_ratio[f] <> 0 then begin + print(" ("); + if pdf_font_expand_ratio[f] > 0 then + print("+"); + print_int(pdf_font_expand_ratio[f]); + print(")"); + end; +end; + +procedure short_display(@!p:integer); {prints highlights of list |p|} var n:integer; {for replacement counts} begin while p>mem_min do begin if is_char_node(p) then @@ -4071,7 +4097,7 @@ begin if (font(p)<font_base)or(font(p)>font_max) then print_char("*") @.*\relax@> - else @<Print the font identifier for |font(p)|@>; + else print_font_identifier(font(p)); print_char(" "); font_in_short_display:=font(p); end; print_ASCII(qo(character(p))); @@ -4110,7 +4136,7 @@ begin if p>mem_end then print_esc("CLOBBERED.") else begin if (font(p)<font_base)or(font(p)>font_max) then print_char("*") @.*\relax@> - else @<Print the font identifier for |font(p)|@>; + else print_font_identifier(font(p)); print_char(" "); print_ASCII(qo(character(p))); end; end; @@ -6771,31 +6797,6 @@ Meanwhile, this is a convenient place to catch up on something we were unable to do before the hash table was defined: -@<Print the font identifier for |font(p)|@>= -begin - if pdf_font_blink[font(p)] = null_font then - print_esc(font_id_text(font(p))) - else - print_esc(font_id_text(pdf_font_blink[font(p)])); - if pdf_tracing_fonts > 0 then begin - print(" ("); - print(font_name[font(p)]); - if font_size[font(p)] <> font_dsize[font(p)] then begin - print("@@"); - print_scaled(font_size[font(p)]); - print("pt"); - end; - print(")"); - end else - if pdf_font_expand_ratio[font(p)] <> 0 then begin - print(" ("); - if pdf_font_expand_ratio[font(p)] > 0 then - print("+"); - print_int(pdf_font_expand_ratio[font(p)]); - print(")"); - end; -end - @* \[19] Saving and restoring equivalents. The nested structure provided by `$\.{\char'173}\ldots\.{\char'175}$' groups in \TeX\ means that |eqtb| entries valid in outer groups should be saved @@ -14943,7 +14944,7 @@ begin if (font(p)<font_base)or(font(p)>font_max) then print_char("*") @.*\relax@> - else @<Print the font identifier for |font(p)|@>; + else print_font_identifier(font(p)); print_char(" "); font_in_short_display:=font(p); end; print_ASCII(qo(character(p))); @@ -19340,11 +19341,15 @@ if pdf_char_marked(k, j) then pdf_mark_char(i, j); if (length(pdf_font_attr[i]) = 0) and (length(pdf_font_attr[k]) <> 0) then - pdf_font_attr[i] := pdf_font_attr[k]; - if not ((pdf_font_attr[i] = pdf_font_attr[k]) or - str_eq_str(pdf_font_attr[i], pdf_font_attr[k])) then begin - pdf_warning("\pdffontattr", "font ", false, false); - print_esc(font_id_text(k)); + pdf_font_attr[i] := pdf_font_attr[k] + else if (length(pdf_font_attr[k]) = 0) and (length(pdf_font_attr[i]) <> 0) then + pdf_font_attr[k] := pdf_font_attr[i] + else if (length(pdf_font_attr[i]) <> 0) and (length(pdf_font_attr[k]) <> 0) and + not str_eq_str(pdf_font_attr[i], pdf_font_attr[k]) then begin + pdf_warning("\pdffontattr", "fonts ", false, false); + print_font_identifier(i); + print(" and "); + print_font_identifier(k); print(" has conflicting attributes"); print_ln; print_ln; end; end; On Thu, Dec 28, 2006 at 06:38:51AM +0100, Hartmut Henkel wrote: > On Thu, 28 Dec 2006, Hartmut Henkel wrote: > > > On Wed, 27 Dec 2006, Reinhard Kotucha wrote: > > > > > I'm trying to run the vntex testfiles with the current pdftex > > > release recently uploaded to the TeXLive repository by Martin. > > > > > > Can anybody tell me what the warnings mean? > > > > > > pdfTeX warning (\pdffontattr): font \^^@ has conflicting attributes > > is this a nullfont? how does one get it? > > > in the intended cases it means, that it was tried to add two different > > font attributes to the same font dictionary. But here is a case where > > this happens even without: > > > > \pdfcompresslevel=0 > > \nopagenumbers > > \font\aa cmr10 at 10pt > > \pdffontattr\aa {foo} > > \aa abc > > \font\bb cmr10 at 11pt > > %\pdffontattr\bb {bar} > > \bb abc > > \bye > > > > Both TeX fonts refer to the same font dictionary. So there is only one > > font, and this gets the attribute "foo". > > > > > I get a lot of these messages. The (pdf) output seems to be ok. > > > > The above source creates the right PDF. Maybe we need to get rid of > > the warning here. > > Here is the try of a patch, which also shows what happens with the above > file. Reinhard, does it remove the warnings in your case? > > --- pdftex.web.orig 2006-12-21 17:19:20.000000000 +0100 > +++ pdftex.web 2006-12-28 06:07:11.771455920 +0100 > @@ -19341,6 +19341,8 @@ > pdf_mark_char(i, j); > if (length(pdf_font_attr[i]) = 0) and (length(pdf_font_attr[k]) <> 0) then > pdf_font_attr[i] := pdf_font_attr[k]; > + if (length(pdf_font_attr[k]) = 0) and (length(pdf_font_attr[i]) <> 0) then > + pdf_font_attr[k] := pdf_font_attr[i]; > if not ((pdf_font_attr[i] = pdf_font_attr[k]) or > str_eq_str(pdf_font_attr[i], pdf_font_attr[k])) then begin > pdf_warning("\pdffontattr", "font ", false, false); > > An alternative (more complicated) might be that one keeps font > dictionaries separate when the user wants different attributes. No idea > what the typical use of these attributes is. > > Regards, Hartmut

2 1

Re: [NTG-pdftex] [Fwd: [NTG-context] crash with pdftex-1.40]
by Thanh Han The 05 Jan '07

05 Jan '07

I can reproduce the problem, but have no idea how to fix it. pdftex crashes when a pclose is called in aclose(), file openclose.c. But I don't know anything about pipes in pdftex -- it was done by other people. Thanh On Thu, Jan 04, 2007 at 11:08:50PM +0100, Martin Schroeder wrote: > 2007/1/4, Hans Hagen <pragma(a)wxs.nl>: > > While playing around with the new shell escaping in pdftex-1.40, I got > > the following crash: > > I can't reproduce this. > > Best > Martin > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

4 5

Re: [NTG-pdftex] [Fwd: [NTG-context] crash with pdftex-1.40]
by Akira Kakuto 05 Jan '07

05 Jan '07

Hi Taco, >>> But this should be enough to reproduce it: >>> >>> \starttext >>> \input "\string|echo -n bla" >>> \stoptext > > I can reproduce the problem, but have no idea how to fix it. > > pdftex crashes when a pclose is called in aclose(), file > > openclose.c. But I don't know anything about pipes in pdftex > > I'll check it out. On windows (pdftex 1.40.0, ConTeXt 2007.01.02 13:44 MK II), \starttext \input "\string|echo This is a test." \stoptext works fine. The result is one page pdf with the sentence "This is a test." Thanks, Akira

1 0

[Fwd: [NTG-context] crash with pdftex-1.40]
by Hans Hagen 04 Jan '07

04 Jan '07

2 1

[ pdftex-Bugs-712 ] problems with \letterspacefont
by noreply＠sarovar.org 04 Jan '07

04 Jan '07

Bugs item #712, was opened at 2006-12-12 02:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106 Category: hz Group: v1.40.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: problems with \letterspacefont Initial Comment: % Testing the new \letterspacefont, I found: % % (1) it's certainly not correct to have the spacing % relative to character widths (look at `minimal'!) % (2) everything's shifted to the right % (3) when trying to expand the letter-spaced font, I % get the warning `font should be expanded before % its first use' (even before its first use), and % then pdftex segfaults. \pdfadjustspacing2 \hsize13cm This is normal text This is normal text This is normal text This is normal text This is normal text This is normal text {\letterspacefont\lspfont=\font 1000 %\pdffontexpand\lspfont 20 20 5 autoexpand % segfault \lspfont This isn't normal text This isn't normal text This isn't normal text This is minimal text} This is normal text This is normal text This is normal text \bye ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2007-01-04 15:59 Message: Logged In: YES user_id=710 The warning is misleading but harmless. The reason of the warning is that pdftex checks whether a font has not been used before expansion (its type has not been examined and is new/unknown yet). \letterspacefont sets the type of \y as a virtual font, thus pdftex thinks the font might have been used before. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-01-04 00:40 Message: Logged In: YES user_id=2217 I'm a bit confused about the status of (3): letterspacing and expansion: When expanding a letterspaced font, pdftex issues the warning: ``font should be expanded before its first use'', but apart from that, I cannot see any problems -- the font is both letterspaced and expanded. Or is there a reason for the warning? \pdfadjustspacing2 \font\x=cmr10 \x \letterspacefont\y=\x 100 \y \pdffontexpand\y 20 20 5 autoexpand ... \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-21 16:09 Message: Logged In: YES user_id=421 A patch for this will be included in the next version (1.40). ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 17:47 Message: Logged In: YES user_id=710 oops, I disabled ligature for letter-spaced font, but this should not affect the base font. Will have to rethink. Most likely the syntax will change like follows: \letterspacefont\f=cmr10 at 11pt 100 \f text ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-12-12 15:50 Message: Logged In: YES user_id=2217 % and here's % (4) ligatures will be broken up, not only in the % letter-spaced font (which is probably acceptable), % but in all subsequent uses of the base font, too fi\par {\letterspacefont\lspfont=\font 100 \lspfont fi}\par fi \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 13:31 Message: Logged In: YES user_id=710 I fixed (1) and (2); (3) is disabled now, ie you cannot expand a letter-spaced font. Please wait for another release from Martin. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106

1 0

[ pdftex-Bugs-712 ] problems with \letterspacefont
by noreply＠sarovar.org 04 Jan '07

04 Jan '07

Bugs item #712, was opened at 2006-12-12 02:53 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106 Category: hz Group: v1.40.0 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Robert (schlcht) Assigned to: The Thanh Han (hanthethanh) Summary: problems with \letterspacefont Initial Comment: % Testing the new \letterspacefont, I found: % % (1) it's certainly not correct to have the spacing % relative to character widths (look at `minimal'!) % (2) everything's shifted to the right % (3) when trying to expand the letter-spaced font, I % get the warning `font should be expanded before % its first use' (even before its first use), and % then pdftex segfaults. \pdfadjustspacing2 \hsize13cm This is normal text This is normal text This is normal text This is normal text This is normal text This is normal text {\letterspacefont\lspfont=\font 1000 %\pdffontexpand\lspfont 20 20 5 autoexpand % segfault \lspfont This isn't normal text This isn't normal text This isn't normal text This is minimal text} This is normal text This is normal text This is normal text \bye ---------------------------------------------------------------------- >Comment By: Robert (schlcht) Date: 2007-01-04 00:40 Message: Logged In: YES user_id=2217 I'm a bit confused about the status of (3): letterspacing and expansion: When expanding a letterspaced font, pdftex issues the warning: ``font should be expanded before its first use'', but apart from that, I cannot see any problems -- the font is both letterspaced and expanded. Or is there a reason for the warning? \pdfadjustspacing2 \font\x=cmr10 \x \letterspacefont\y=\x 100 \y \pdffontexpand\y 20 20 5 autoexpand ... \bye ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-21 16:09 Message: Logged In: YES user_id=421 A patch for this will be included in the next version (1.40). ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 17:47 Message: Logged In: YES user_id=710 oops, I disabled ligature for letter-spaced font, but this should not affect the base font. Will have to rethink. Most likely the syntax will change like follows: \letterspacefont\f=cmr10 at 11pt 100 \f text ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2006-12-12 15:50 Message: Logged In: YES user_id=2217 % and here's % (4) ligatures will be broken up, not only in the % letter-spaced font (which is probably acceptable), % but in all subsequent uses of the base font, too fi\par {\letterspacefont\lspfont=\font 100 \lspfont fi}\par fi \bye ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-12 13:31 Message: Logged In: YES user_id=710 I fixed (1) and (2); (3) is disabled now, ie you cannot expand a letter-spaced font. Please wait for another release from Martin. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106

1 0

Re: [NTG-pdftex] [tex-live] \pdffontattr in pdftex-1.40.0-rc4
by Akira Kakuto 03 Jan '07

03 Jan '07

Hi Reinhard, > > Here is the try of a patch, which also shows what happens with the > > above file. Reinhard, does it remove the warnings in your case? > > Yes, after I applied your patch, the warnings don't appear any more. In this respect, the released version seems to be the same as rc4: I see the warning with cmap.sty. Thanks, Akira

6 8

bug
by Hans Hagen 03 Jan '07

03 Jan '07

Hi, ! pdfTeX error (\pdfglyphtounicode): not allowed in DVI mode (\pdfoutput <= 0). l.1 \pdfglyphtounicode this is wrong i.e. it should be possible to generate a format which can produce both dvi and pdf and in that case one should be able to preload the unicode mappings test by taco also indicate that those settings don't survive a dump/undump Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 2

[ pdftex-Bugs-719 ] few buglets in build.sh
by noreply＠sarovar.org 02 Jan '07

02 Jan '07

Bugs item #719, was opened at 2007-01-02 04:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106 >Category: Build process Group: v1.40.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Sanjoy Mahajan (sanjoy) >Assigned to: Martin Schröder (oneiros) Summary: few buglets in build.sh Initial Comment: Just compiled 1.40.0 using build.sh. I had to make a few changes to get it to run on my system (Ubuntu 6.10, i386). The purpose of the chunks in the attached diff: 1. The JOBS variable wasn't used, so I changed its name be descriptive for parallel builds, and used it (and a related load variable) in the line that appends to the MAKE variable. Also, without the necessary double quotes around that line, the rest of the line after $MAKE is interpreted as a command rather than as stuff to append to MAKE (run build.sh with "--parallel" to see the problem). I used the short option names for make, to keep the line within 80 chars. 2. "-a build" is an (incomplete) AND statement, rather than a test for the "build" directory existing. The test should be "-e build" to check for existence. 3. Brace expansion is suboptimal in sh and not very portable to different reimplementations of sh. According to the bash man page: "Brace expansion introduces a slight incompatibility with historical versions of sh. sh does not treat opening or closing braces specially when they appear as part of a word, and preserves them in the output. Bash removes braces from words as a consequence of brace expansion. For example, a word entered to sh as file{1,2} appears identically in the output." I don't know the full story, but the fake sh on my system (actually 'dash') doesn't do brace expansion at all. And if the bash man page is right, even if it did the expansion, it wouldn't help since build.sh uses braces in the middle of a word. So I rewrote the two uses of brace expansion to avoid it. The resulting "build.sh --parallel" worked fine in my limited tests. It still complained that it couldn't find the texmf tree, but I figure that's okay since pdftex'll eventually (I hope) use kpathsea and texmf.cnf. -Sanjoy ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106

1 0

[ pdftex-Patches-603 ] Patch ColorStackTransformMatrix
by noreply＠sarovar.org 02 Jan '07

02 Jan '07

Patches item #603, was opened at 2006-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=603&group_id=106 Category: Primitives Group: v1.40.0 Status: Closed Resolution: Accepted Priority: 8 Submitted By: Heiko Oberdiek (oberdiek) Assigned to: Martin Schröder (oneiros) Summary: Patch ColorStackTransformMatrix Initial Comment: Subject: Patch ColorStackTransformMatrix Date: 2006/09/07 Author: Heiko Oberdiek The patch is based on pdftex-1.40.0-beta-20060906 It tries to solve two FAQ problems: * missing color stack * wrong annotation rectangles (links, anchors) if the material was scaled or rotated. Files: ColorStackTransformMatrix.patch The patch, apply it in src/texk/web2c/pdftexdir: patch <ColorStackTransformMatrix.patch pdftex.def A modified version that uses the patch if the new primitives are found. A short test file: \documentclass{article} \usepackage{color} \usepackage{pdflscape} \usepackage{hyperref} \begin{document} \tableofcontents \section{Hello World} \label{sec:hello} \textcolor{blue}{Blue\newpage Blue} \begin{landscape} See \autoref{sec:hello}. \end{landscape} \end{document} Without the patch: * Text on first page before "Blue" is blue instead of black. * Text on second page is black instead of blue. * The link frame on page three is misplaced. With the patch and modified pdftex.def these things are fixed. New commands % color stack * \pdfcolorstackinit * \pdfcolorstack % matrix transformations * \pdfsetmatrix * \pdfsave * \pdfrestore Syntax: %% expandable commands: \pdfcolorstackinit [page] [direct] <general text> %% general commands: \pdfcolorstack <stack number> <stack action> <general text> \pdfsetmatrix \pdfsave \pdfrestore <stack action> ::= set | push | pop | current Description for color stack: This color stack implementation allows several independent stacks (upto 32686): * Stacks can be used for other properties than color, especially other graphics state parameters. * Several "text flows across pages" can be supported by color stacks. Example: footnotes. \pdfcolorstackinit [page] [direct] {<initial value>} A stack is initialized by \pdfcolorstackinit. It expands to the number of the new stack. The common case, the traditinal color stack is already initialized as first stack: \pdfcolorstackinit page direct {0 g 0 G} The keyword "page" means, that this stack is page based. At the start of the new page, the current stack value is automatically set: \textcolor{blue}{A\newpage B} The second page with "B" will start with blue setting. The keyword "direct" has the same meaning as "direct" for \pdfliteral. If the stack value is set, it is done by an equivalent of \pdfliteral direct {...}. The mandatory argument is the initial value on the stack. It should be the default at page start for the property, see PDF documentation. \pdfcolorstack <stack number> push {<new color>} pushes the current value on the stack and sets the <new color>. \pdfcolorstack <stack number> pop pops and sets the current stack value. \pdfcolorstack <stack number> current sets the current stack value without changing the stack. This is useful for stacks that are initialized without keyword "page". Thus the page start setting can be set manually. \pdfcolorstack <stack number> set {<new color>} The current value is set to <new color>. Example (changed pdftex.def): \chardef\GPT@colorstack=0 % \def\set@color{% \pdfcolorstack\GPT@colorstack push{\current@color}% \aftergroup\reset@color }% \def\reset@color{% \pdfcolorstack\GPT@colorstack pop\relax }% If someone wants to add color stack support for footnotes, the principle would be: \edef\stackfootnote{\pdfcolorstackinit direct{0 g 0 G}}% % Then at begin of the footnote area on the page: \pdfcolorstack\stackfoonote current\relax % During footnote processing the footnote stack is used: \let\GPT@colorstack\stackfoonote Description for matrix transformations: Currently matrix changes are done and hidden inside \pdfliteral nodes; pdfTeX doesn't parse its contents and does not know the new settings of the transform matrix. Thus the patch adds new primitives to save pdfTeX from parsing \pdfliteral contents and to notify pdfTeX about matrix changes to use them in calculating link and anchor positions. \pdfsetmatrix{<a> <b> <c> <d>} is the equivalent to \pdfliteral{<a> <b> <c> <d> 0 0 cm} \pdfsave is the equivalent to \pdfliteral{q} \pdfrestore is the equivalent to \pdfliteral{Q} Some remarks: * TeX already supports translations, thus the matrix is limited to four values for scaling and rotating. * There are some restrictions about \pdfsave and \pdfrestore: * They must be properly nested. * A pair must start and end in the same group at the same level. * A pair must start and end at the same position. Happily these restrictions are satisfied by the graphics package. Example (changed pdftex.def): \def\Grot@start{% \pdfsave \pdfsetmatrix{% \Grot@cos\space\Grot@sin\space \if-\Grot@sin\else-\Grot@sin\fi\space\Grot@cos }% \wd\z@\z@ }% \def\Grot@end{\pdfrestore} \def\Gscale@start{% \pdfsave \pdfsetmatrix{% \Gscale@x\space0 0 \Gscale@y }% }% Have fun Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- >Comment By: Heiko Oberdiek (oberdiek) Date: 2007-01-02 09:20 Message: Logged In: YES user_id=1276 Hello, version 0.04b and next versions of pdftex.def are provided at the usual places, not here. (http://pdftex-def.berlios.de/ and CTAN:graphics/pdftex/pdftex.def (installed with a little delay)) Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2007-01-01 00:40 Message: Logged In: YES user_id=1276 Sorry, in newcolorstack, some initializations are missing. utils.c.diff adds them. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-31 14:31 Message: Logged In: YES user_id=421 This has been included in version 1.40 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-10-17 15:08 Message: Logged In: YES user_id=421 I still get the warning in utils.c :-{ Can you update the pdfTeX manual on this? ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2006-09-12 16:38 Message: Logged In: YES user_id=1276 | Two questions come to mind: | - how does this patch interact with existing documents, The design principle is that the patch does not have an effect if the new primitives are not used (modulo bugs). | i.e. | what must be changed when using this patch? Obviously the | use of \pdfliteral must be checked. Anything else? LaTeX's color/graphics: pdftex.def that support the new primitives. | - does this collide with pdftex's use of the cm? The only | use of the transformation matrix by pdftex I could find | concerns magnifications, so that's most likely not a | problem. I had played a little with magnification, but not too intensively. | Btw: gcc with -Wall -std=c99 gives this warning: | ../../../../src/texk/web2c/pdftexdir/utils.c: In function | ‘newcolorstack’: | ../../../../src/texk/web2c/pdftexdir/utils.c:1366: | warning: | operation on ‘colstacks’ may be undefined Assignments to colstacks are controlled by colstack_size, thus the warnung can be gnored. To avoid the warning replace static colstack_type *colstacks; by static colstack_type *colstacks = NULL; Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-09-12 16:06 Message: Logged In: YES user_id=421 Heiko, thank you very much for your patch. Two questions come to mind: - how does this patch interact with existing documents, i.e. what must be changed when using this patch? Obviously the use of \pdfliteral must be checked. Anything else? - does this collide with pdftex's use of the cm? The only use of the transformation matrix by pdftex I could find concerns magnifications, so that's most likely not a problem. Btw: gcc with -Wall -std=c99 gives this warning: ../../../../src/texk/web2c/pdftexdir/utils.c: In function ‘newcolorstack’: ../../../../src/texk/web2c/pdftexdir/utils.c:1366: warning: operation on ‘colstacks’ may be undefined ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=603&group_id=106

1 0

\pdffontattr in pdftex-1.40.0-rc4
by Reinhard Kotucha 02 Jan '07

02 Jan '07

Hi, I'm trying to run the vntex testfiles with the current pdftex release recently uploaded to the TeXLive repository by Martin. Can anybody tell me what the warnings mean? pdfTeX warning (\pdffontattr): font \^^@ has conflicting attributes I get a lot of these messages. The (pdf) output seems to be ok. 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. ----------------------------------------------------------------------------

3 4

[ pdftex-Bugs-719 ] few buglets in build.sh
by noreply＠sarovar.org 02 Jan '07

02 Jan '07

Bugs item #719, was opened at 2007-01-01 22:39 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106 Category: None Group: v1.40.0 Status: Open Resolution: None Priority: 5 Submitted By: Sanjoy Mahajan (sanjoy) Assigned to: Nobody (None) Summary: few buglets in build.sh Initial Comment: Just compiled 1.40.0 using build.sh. I had to make a few changes to get it to run on my system (Ubuntu 6.10, i386). The purpose of the chunks in the attached diff: 1. The JOBS variable wasn't used, so I changed its name be descriptive for parallel builds, and used it (and a related load variable) in the line that appends to the MAKE variable. Also, without the necessary double quotes around that line, the rest of the line after $MAKE is interpreted as a command rather than as stuff to append to MAKE (run build.sh with "--parallel" to see the problem). I used the short option names for make, to keep the line within 80 chars. 2. "-a build" is an (incomplete) AND statement, rather than a test for the "build" directory existing. The test should be "-e build" to check for existence. 3. Brace expansion is suboptimal in sh and not very portable to different reimplementations of sh. According to the bash man page: "Brace expansion introduces a slight incompatibility with historical versions of sh. sh does not treat opening or closing braces specially when they appear as part of a word, and preserves them in the output. Bash removes braces from words as a consequence of brace expansion. For example, a word entered to sh as file{1,2} appears identically in the output." I don't know the full story, but the fake sh on my system (actually 'dash') doesn't do brace expansion at all. And if the bash man page is right, even if it did the expansion, it wouldn't help since build.sh uses braces in the middle of a word. So I rewrote the two uses of brace expansion to avoid it. The resulting "build.sh --parallel" worked fine in my limited tests. It still complained that it couldn't find the texmf tree, but I figure that's okay since pdftex'll eventually (I hope) use kpathsea and texmf.cnf. -Sanjoy ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=719&group_id=106

1 0

[ pdftex-Feature Requests-718 ] Request of pdfsync
by noreply＠sarovar.org 01 Jan '07

01 Jan '07

Feature Requests item #718, was opened at 2007-01-01 23:27 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=718&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Juan Luis Varona (jlvm) Assigned to: Nobody (None) Summary: Request of pdfsync Initial Comment: The syncronization between the .tex and the .pdf files is veeeeeery useful. It is not necessary to explain it. Now, there are some tools to do it, but they are far of being good enough. For instance, pdfsync makes some work, but it has a lot of problems. Of instance, the output is different with or without pdfsync. I have read in TUGboat that, perhaps in the near future, pdfsync can be integrated en pdftex itself and improved. I request to do it as soon as possible. Yours sincerely, Juan L. Varona jvarona(a)unirioja.es ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=718&group_id=106

1 0

[ pdftex-Patches-603 ] Patch ColorStackTransformMatrix
by noreply＠sarovar.org 31 Dec '06

31 Dec '06

Patches item #603, was opened at 2006-09-07 10:35 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=603&group_id=106 Category: Primitives Group: v1.40.0 >Status: Closed Resolution: Accepted Priority: 8 Submitted By: Heiko Oberdiek (oberdiek) Assigned to: Martin Schröder (oneiros) Summary: Patch ColorStackTransformMatrix Initial Comment: Subject: Patch ColorStackTransformMatrix Date: 2006/09/07 Author: Heiko Oberdiek The patch is based on pdftex-1.40.0-beta-20060906 It tries to solve two FAQ problems: * missing color stack * wrong annotation rectangles (links, anchors) if the material was scaled or rotated. Files: ColorStackTransformMatrix.patch The patch, apply it in src/texk/web2c/pdftexdir: patch <ColorStackTransformMatrix.patch pdftex.def A modified version that uses the patch if the new primitives are found. A short test file: \documentclass{article} \usepackage{color} \usepackage{pdflscape} \usepackage{hyperref} \begin{document} \tableofcontents \section{Hello World} \label{sec:hello} \textcolor{blue}{Blue\newpage Blue} \begin{landscape} See \autoref{sec:hello}. \end{landscape} \end{document} Without the patch: * Text on first page before "Blue" is blue instead of black. * Text on second page is black instead of blue. * The link frame on page three is misplaced. With the patch and modified pdftex.def these things are fixed. New commands % color stack * \pdfcolorstackinit * \pdfcolorstack % matrix transformations * \pdfsetmatrix * \pdfsave * \pdfrestore Syntax: %% expandable commands: \pdfcolorstackinit [page] [direct] <general text> %% general commands: \pdfcolorstack <stack number> <stack action> <general text> \pdfsetmatrix \pdfsave \pdfrestore <stack action> ::= set | push | pop | current Description for color stack: This color stack implementation allows several independent stacks (upto 32686): * Stacks can be used for other properties than color, especially other graphics state parameters. * Several "text flows across pages" can be supported by color stacks. Example: footnotes. \pdfcolorstackinit [page] [direct] {<initial value>} A stack is initialized by \pdfcolorstackinit. It expands to the number of the new stack. The common case, the traditinal color stack is already initialized as first stack: \pdfcolorstackinit page direct {0 g 0 G} The keyword "page" means, that this stack is page based. At the start of the new page, the current stack value is automatically set: \textcolor{blue}{A\newpage B} The second page with "B" will start with blue setting. The keyword "direct" has the same meaning as "direct" for \pdfliteral. If the stack value is set, it is done by an equivalent of \pdfliteral direct {...}. The mandatory argument is the initial value on the stack. It should be the default at page start for the property, see PDF documentation. \pdfcolorstack <stack number> push {<new color>} pushes the current value on the stack and sets the <new color>. \pdfcolorstack <stack number> pop pops and sets the current stack value. \pdfcolorstack <stack number> current sets the current stack value without changing the stack. This is useful for stacks that are initialized without keyword "page". Thus the page start setting can be set manually. \pdfcolorstack <stack number> set {<new color>} The current value is set to <new color>. Example (changed pdftex.def): \chardef\GPT@colorstack=0 % \def\set@color{% \pdfcolorstack\GPT@colorstack push{\current@color}% \aftergroup\reset@color }% \def\reset@color{% \pdfcolorstack\GPT@colorstack pop\relax }% If someone wants to add color stack support for footnotes, the principle would be: \edef\stackfootnote{\pdfcolorstackinit direct{0 g 0 G}}% % Then at begin of the footnote area on the page: \pdfcolorstack\stackfoonote current\relax % During footnote processing the footnote stack is used: \let\GPT@colorstack\stackfoonote Description for matrix transformations: Currently matrix changes are done and hidden inside \pdfliteral nodes; pdfTeX doesn't parse its contents and does not know the new settings of the transform matrix. Thus the patch adds new primitives to save pdfTeX from parsing \pdfliteral contents and to notify pdfTeX about matrix changes to use them in calculating link and anchor positions. \pdfsetmatrix{<a> <b> <c> <d>} is the equivalent to \pdfliteral{<a> <b> <c> <d> 0 0 cm} \pdfsave is the equivalent to \pdfliteral{q} \pdfrestore is the equivalent to \pdfliteral{Q} Some remarks: * TeX already supports translations, thus the matrix is limited to four values for scaling and rotating. * There are some restrictions about \pdfsave and \pdfrestore: * They must be properly nested. * A pair must start and end in the same group at the same level. * A pair must start and end at the same position. Happily these restrictions are satisfied by the graphics package. Example (changed pdftex.def): \def\Grot@start{% \pdfsave \pdfsetmatrix{% \Grot@cos\space\Grot@sin\space \if-\Grot@sin\else-\Grot@sin\fi\space\Grot@cos }% \wd\z@\z@ }% \def\Grot@end{\pdfrestore} \def\Gscale@start{% \pdfsave \pdfsetmatrix{% \Gscale@x\space0 0 \Gscale@y }% }% Have fun Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-31 14:31 Message: Logged In: YES user_id=421 This has been included in version 1.40 ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-10-17 15:08 Message: Logged In: YES user_id=421 I still get the warning in utils.c :-{ Can you update the pdfTeX manual on this? ---------------------------------------------------------------------- Comment By: Heiko Oberdiek (oberdiek) Date: 2006-09-12 16:38 Message: Logged In: YES user_id=1276 | Two questions come to mind: | - how does this patch interact with existing documents, The design principle is that the patch does not have an effect if the new primitives are not used (modulo bugs). | i.e. | what must be changed when using this patch? Obviously the | use of \pdfliteral must be checked. Anything else? LaTeX's color/graphics: pdftex.def that support the new primitives. | - does this collide with pdftex's use of the cm? The only | use of the transformation matrix by pdftex I could find | concerns magnifications, so that's most likely not a | problem. I had played a little with magnification, but not too intensively. | Btw: gcc with -Wall -std=c99 gives this warning: | ../../../../src/texk/web2c/pdftexdir/utils.c: In function | ‘newcolorstack’: | ../../../../src/texk/web2c/pdftexdir/utils.c:1366: | warning: | operation on ‘colstacks’ may be undefined Assignments to colstacks are controlled by colstack_size, thus the warnung can be gnored. To avoid the warning replace static colstack_type *colstacks; by static colstack_type *colstacks = NULL; Yours sincerely Heiko <oberdiek(a)uni-freiburg.de> ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-09-12 16:06 Message: Logged In: YES user_id=421 Heiko, thank you very much for your patch. Two questions come to mind: - how does this patch interact with existing documents, i.e. what must be changed when using this patch? Obviously the use of \pdfliteral must be checked. Anything else? - does this collide with pdftex's use of the cm? The only use of the transformation matrix by pdftex I could find concerns magnifications, so that's most likely not a problem. Btw: gcc with -Wall -std=c99 gives this warning: ../../../../src/texk/web2c/pdftexdir/utils.c: In function ‘newcolorstack’: ../../../../src/texk/web2c/pdftexdir/utils.c:1366: warning: operation on ‘colstacks’ may be undefined ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=603&group_id=106

1 0

Re: [NTG-pdftex] \pdffontattr in pdftex-1.40.0-rc4
by Akira Kakuto 30 Dec '06

30 Dec '06

Hi Reinhard, > it seems that you don't have cmap.sty in the seach path. I've installed cmap.sty and encountered the same warning. Thanks very much. Akira

4 4

Re: [NTG-pdftex] \pdffontattr in pdftex-1.40.0-rc4
by Akira Kakuto 29 Dec '06

29 Dec '06

Hi Reinhard, > The version in the TeXLive repository (now revision 3005) provides the > lines: > > Compiled with libpng 1.2.14; using libpng 1.2.14 > Compiled with zlib 1.2.3; using zlib 1.2.3 > Compiled with xpdf version 3.01 > > But I don't see these lines when I run "pdftex --version" using the > disk image. I think Martin's one shows the above lines, because he updated printversionandexit() in lib.a. -- Akira Kakuto

1 0

Re: [NTG-pdftex] \pdffontattr in pdftex-1.40.0-rc4
by Akira Kakuto 28 Dec '06

28 Dec '06

Hi Reinhard, > >> I'm trying to run the vntex testfiles with the current pdftex > >> release recently uploaded to the TeXLive repository by Martin. > >> > >> Can anybody tell me what the warnings mean? > >> > >> pdfTeX warning (\pdffontattr): font \^^@ has conflicting > >> attributes > > > Can you please tell me the name of the test file if it is in CTAN? > > Try ${TEXMF}/doc/generic/vntex/tests/urwvn-test.tex which you already > have installed. urwvn-test.tex requires other files from the tests > directory. You do not need the latest version, I did not change the > content of the file. Recent versions load a .cls file while former > versions loaded a .sty file. That's all. There should not be any > differences between the files from TL-2005 and the current files. > > > (I've tested a few vntex tests and I don't have the warning. > > Maybe I'm testing different files.) > > The files had not been changed, I got the messages after I switched > from pdftex-1.30 to pdftex 1.40. I don't encounter the warning also with the urwvn-test.tex. I send you the terminal output and the logfile. Thanks, Akira ------------------------------------------- Terminal output: This is pdfTeX, Version 3.141592-1.40.0-rc4 (Web2C 7.5.5) entering extended mode (./urwvn-test.tex LaTeX2e <2005/12/01> Babel <v3.8h> and hyphenation patterns for english, usenglishmax, ukenglish, ba sque, bulgarian, coptic, welsh, czech, slovak, german, ngerman, danish, spanish , catalan, estonian, finnish, french, irish, polygreek, monogreek, ancientgreek , croatian, hungarian, interlingua, ibycus, bahasa, icelandic, italian, latin, mongolian, dutch, norsk, polish, portuguese, pinyin, romanian, russian, samin, slovene, usorbian, serbian, swedish, turkish, ukrainian, dumylang, nohyphenatio n, loaded. (./vnsample.cls Document Class: vnsample 2005/08/27 (c:/usr/local/share/texmf/tex/latex/base/article.cls Document Class: article 2005/09/16 v1.4f Standard LaTeX document class (c:/usr/local/share/texmf/tex/latex/base/size10.clo)) (c:/usr/local/share/texmf/tex/generic/oberdiek/ifpdf.sty) (c:/usr/local/share/texmf/tex/latex/vntex/vietnam.sty (c:/usr/local/share/texmf/tex/latex/base/ifthen.sty) (c:/usr/local/share/texmf/tex/latex/base/fontenc.sty (c:/usr/local/share/texmf/tex/latex/vntex/t5enc.def) (c:/usr/local/share/texmf/tex/latex/vntex/t5cmr.fd)) (c:/usr/local/share/texmf/tex/latex/base/inputenc.sty (c:/usr/local/share/texmf/tex/latex/vntex/viscii.def)) (c:/usr/local/share/texmf/tex/latex/vntex/vncaps.tex)) (c:/usr/local/share/texmf/tex/latex/tools/multicol.sty) (c:/usr/local/share/texmf/tex/latex/misc/geometry.sty (c:/usr/local/share/texmf/tex/latex/graphics/keyval.sty) (c:/usr/local/share/texmf/tex/latex/misc/geometry.cfg)) (c:/usr/local/share/texmf/tex/latex/tools/array.sty) (c:/usr/local/share/texmf/tex/latex/fancyhdr/fancyhdr.sty)) (./urwvn-test.aux) (c:/usr/local/share/texmf/tex/latex/vntex/t5uag.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5ubk.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5ucr.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5uhv.fd) [1{c:/usr/local/share/texmf /fonts/map/pdftex/updmap/pdftex.map}] (c:/usr/local/share/texmf/tex/latex/vntex/t5unc.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5upl.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5fpl.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5utm.fd) [2] (c:/usr/local/share/texmf/tex/latex/vntex/t5pag.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5pbk.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5pcr.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5phv.fd) [3] (c:/usr/local/share/texmf/tex/latex/vntex/t5pnc.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5ppl.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5ptm.fd) (c:/usr/local/share/texmf/tex/latex/vntex/t5uzcm.fd) [4] (./urwvn-test.aux) ){c :/usr/local/share/texmf/fonts/enc/dvips/base/t5.enc}<c:/usr/local/share/texmf/f onts/type1/bluesky/cmtt10.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn /fplrc8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uagd8v.pfb><c:/u sr/local/share/texmf/fonts/type1/vntex/urwvn/uagdo8v.pfb><c:/usr/local/share/te xmf/fonts/type1/vntex/urwvn/uagk8v.pfb><c:/usr/local/share/texmf/fonts/type1/vn tex/urwvn/uagko8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ubkd8v. pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ubkd8v.pfb><c:/usr/local/ share/texmf/fonts/type1/vntex/urwvn/ubkdi8v.pfb><c:/usr/local/share/texmf/fonts /type1/vntex/urwvn/ubkl8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn /ubkl8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ubkli8v.pfb><c:/u sr/local/share/texmf/fonts/type1/vntex/urwvn/ucrb8v.pfb><c:/usr/local/share/tex mf/fonts/type1/vntex/urwvn/ucrbo8v.pfb><c:/usr/local/share/texmf/fonts/type1/vn tex/urwvn/ucrr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ucrro8v. pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uhvb8v.pfb><c:/usr/local/ share/texmf/fonts/type1/vntex/urwvn/uhvbo8v.pfb><c:/usr/local/share/texmf/fonts /type1/vntex/urwvn/uhvr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn /uhvro8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uncb8v.pfb><c:/u sr/local/share/texmf/fonts/type1/vntex/urwvn/uncb8v.pfb><c:/usr/local/share/tex mf/fonts/type1/vntex/urwvn/uncbi8v.pfb><c:/usr/local/share/texmf/fonts/type1/vn tex/urwvn/uncr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uncr8v.p fb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uncri8v.pfb><c:/usr/local/ share/texmf/fonts/type1/vntex/urwvn/uplb8v.pfb><c:/usr/local/share/texmf/fonts/ type1/vntex/urwvn/uplb8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ uplbi8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uplr8v.pfb><c:/us r/local/share/texmf/fonts/type1/vntex/urwvn/uplr8v.pfb><c:/usr/local/share/texm f/fonts/type1/vntex/urwvn/uplri8v.pfb><c:/usr/local/share/texmf/fonts/type1/vnt ex/urwvn/utmb8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/utmb8v.pf b><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/utmbi8v.pfb><c:/usr/local/s hare/texmf/fonts/type1/vntex/urwvn/utmr8v.pfb><c:/usr/local/share/texmf/fonts/t ype1/vntex/urwvn/utmr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/u tmri8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uzcmi8v.pfb> Output written on urwvn-test.pdf (4 pages, 713906 bytes). Transcript written on urwvn-test.log. --------------------------- Log file: This is pdfTeX, Version 3.141592-1.40.0-rc4 (Web2C 7.5.5) (format=pdflatex 2006.12.22) 28 DEC 2006 08:58 entering extended mode **urwvn-test (./urwvn-test.tex LaTeX2e <2005/12/01> Babel <v3.8h> and hyphenation patterns for english, usenglishmax, ukenglish, ba sque, bulgarian, coptic, welsh, czech, slovak, german, ngerman, danish, spanish , catalan, estonian, finnish, french, irish, polygreek, monogreek, ancientgreek , croatian, hungarian, interlingua, ibycus, bahasa, icelandic, italian, latin, mongolian, dutch, norsk, polish, portuguese, pinyin, romanian, russian, samin, slovene, usorbian, serbian, swedish, turkish, ukrainian, dumylang, nohyphenatio n, loaded. (./vnsample.cls Document Class: vnsample 2005/08/27 (c:/usr/local/share/texmf/tex/latex/base/article.cls Document Class: article 2005/09/16 v1.4f Standard LaTeX document class (c:/usr/local/share/texmf/tex/latex/base/size10.clo File: size10.clo 2005/09/16 v1.4f Standard LaTeX file (size option) ) \c@part=\count79 \c@section=\count80 \c@subsection=\count81 \c@subsubsection=\count82 \c@paragraph=\count83 \c@subparagraph=\count84 \c@figure=\count85 \c@table=\count86 \abovecaptionskip=\skip41 \belowcaptionskip=\skip42 \bibindent=\dimen102 ) (c:/usr/local/share/texmf/tex/generic/oberdiek/ifpdf.sty Package: ifpdf 2006/02/20 v1.4 Provides the ifpdf switch (HO) Package ifpdf Info: pdfTeX in pdf mode detected. ) (c:/usr/local/share/texmf/tex/latex/vntex/vietnam.sty Package: vietnam 2006/10/18 v1.2 support for Vietnamese (c:/usr/local/share/texmf/tex/latex/base/ifthen.sty Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC) ) (c:/usr/local/share/texmf/tex/latex/base/fontenc.sty Package: fontenc 2005/09/27 v1.99g Standard LaTeX package (c:/usr/local/share/texmf/tex/latex/vntex/t5enc.def File: t5enc.def 2006/11/21 v1.4 Vietnamese T5 encoding ) LaTeX Font Info: Try loading font information for T5+cmr on input line 100. (c:/usr/local/share/texmf/tex/latex/vntex/t5cmr.fd File: t5cmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions )) (c:/usr/local/share/texmf/tex/latex/base/inputenc.sty Package: inputenc 2006/03/04 v1.1b Input encoding file \inpenc@prehook=\toks14 \inpenc@posthook=\toks15 (c:/usr/local/share/texmf/tex/latex/vntex/viscii.def File: viscii.def 2005/04/21 v1.1 VISCII Vietnamese input encoding )) (c:/usr/local/share/texmf/tex/latex/vntex/vncaps.tex File: vncaps.tex 2006/06/07 v1.1 Captions in Vietnamese )) (c:/usr/local/share/texmf/tex/latex/tools/multicol.sty Package: multicol 2006/02/23 v1.6g multicolumn formatting (FMi) \c@tracingmulticols=\count87 \mult@box=\box26 \multicol@leftmargin=\dimen103 \c@unbalance=\count88 \c@collectmore=\count89 \doublecol@number=\count90 \multicoltolerance=\count91 \multicolpretolerance=\count92 \full@width=\dimen104 \page@free=\dimen105 \premulticols=\dimen106 \postmulticols=\dimen107 \multicolsep=\skip43 \multicolbaselineskip=\skip44 \partial@page=\box27 \last@line=\box28 \mult@rightbox=\box29 \mult@grightbox=\box30 \mult@gfirstbox=\box31 \mult@firstbox=\box32 \@tempa=\box33 \@tempa=\box34 \@tempa=\box35 \@tempa=\box36 \@tempa=\box37 \@tempa=\box38 \@tempa=\box39 \@tempa=\box40 \@tempa=\box41 \@tempa=\box42 \@tempa=\box43 \@tempa=\box44 \@tempa=\box45 \@tempa=\box46 \@tempa=\box47 \@tempa=\box48 \@tempa=\box49 \c@columnbadness=\count93 \c@finalcolumnbadness=\count94 \last@try=\dimen108 \multicolovershoot=\dimen109 \multicolundershoot=\dimen110 \mult@nat@firstbox=\box50 \colbreak@box=\box51 ) (c:/usr/local/share/texmf/tex/latex/misc/geometry.sty Package: geometry 2002/07/08 v3.2 Page Geometry (c:/usr/local/share/texmf/tex/latex/graphics/keyval.sty Package: keyval 1999/03/16 v1.13 key=value parser (DPC) \KV@toks@=\toks16 ) \Gm@cnth=\count95 \Gm@cntv=\count96 \c@Gm@tempcnt=\count97 \Gm@bindingoffset=\dimen111 \Gm@wd@mp=\dimen112 \Gm@odd@mp=\dimen113 \Gm@even@mp=\dimen114 \Gm@dimlist=\toks17 (c:/usr/local/share/texmf/tex/latex/misc/geometry.cfg)) (c:/usr/local/share/texmf/tex/latex/tools/array.sty Package: array 2005/08/23 v2.4b Tabular extension package (FMi) \col@sep=\dimen115 \extrarowheight=\dimen116 \NC@list=\toks18 \extratabsurround=\skip45 \backup@length=\skip46 ) (c:/usr/local/share/texmf/tex/latex/fancyhdr/fancyhdr.sty \fancy@headwidth=\skip47 \f@ncyO@elh=\skip48 \f@ncyO@erh=\skip49 \f@ncyO@olh=\skip50 \f@ncyO@orh=\skip51 \f@ncyO@elf=\skip52 \f@ncyO@erf=\skip53 \f@ncyO@olf=\skip54 \f@ncyO@orf=\skip55 ) \dimenA=\dimen117 \boxA=\box52 \boxB=\box53 ) (./urwvn-test.aux) \openout1 = `urwvn-test.aux'. LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. LaTeX Font Info: Checking defaults for T5/cmr/m/n on input line 9. LaTeX Font Info: ... okay on input line 9. -------------------- Geometry parameters paper: a4paper landscape: true twocolumn: -- twoside: -- asymmetric: -- h-parts: 28.45274pt, 788.14136pt, 28.45274pt v-parts: 28.45274pt, 540.60239pt, 28.45274pt hmarginratio: -- vmarginratio: -- lines: -- heightrounded: -- bindingoffset: 0.0pt truedimen: -- includehead: -- includefoot: -- includemp: -- driver: pdftex -------------------- Page layout dimensions and switches \paperwidth 845.04684pt \paperheight 597.50787pt \textwidth 788.14136pt \textheight 540.60239pt \oddsidemargin -63.73416pt \evensidemargin -63.73416pt \topmargin -43.81725pt \headheight 0.0pt \headsep 0.0pt \footskip 0.0pt \marginparwidth 57.0pt \marginparsep 11.0pt \columnsep 10.0pt \skip\footins 9.0pt plus 4.0pt minus 2.0pt \hoffset 0.0pt \voffset 0.0pt \mag 1000 (1in=72.27pt, 1cm=28.45pt) ----------------------- LaTeX Font Info: External font `cmex10' loaded for size (Font) <7> on input line 10. LaTeX Font Info: External font `cmex10' loaded for size (Font) <5> on input line 10. LaTeX Font Info: Try loading font information for T5+uag on input line 11. (c:/usr/local/share/texmf/tex/latex/vntex/t5uag.fd File: t5uag.fd 2005/08/24 Fontinst v1.929 font definitions for T5/uag. ) LaTeX Font Info: Try loading font information for T5+ubk on input line 18. (c:/usr/local/share/texmf/tex/latex/vntex/t5ubk.fd File: t5ubk.fd 2005/08/24 Fontinst v1.929 font definitions for T5/ubk. ) LaTeX Font Info: Try loading font information for T5+ucr on input line 27. (c:/usr/local/share/texmf/tex/latex/vntex/t5ucr.fd File: t5ucr.fd 2005/08/24 Fontinst v1.929 font definitions for T5/ucr. ) LaTeX Font Info: Try loading font information for T5+uhv on input line 34. (c:/usr/local/share/texmf/tex/latex/vntex/t5uhv.fd File: t5uhv.fd 2005/08/24 Fontinst v1.929 font definitions for T5/uhv. ) [1 {c:/usr/local/share/texmf/fonts/map/pdftex/updmap/pdftex.map}] LaTeX Font Info: Try loading font information for T5+unc on input line 43. (c:/usr/local/share/texmf/tex/latex/vntex/t5unc.fd File: t5unc.fd 2005/08/24 Fontinst v1.929 font definitions for T5/unc. ) LaTeX Font Info: Try loading font information for T5+upl on input line 52. (c:/usr/local/share/texmf/tex/latex/vntex/t5upl.fd File: t5upl.fd 2005/08/24 Fontinst v1.929 font definitions for T5/upl. ) LaTeX Font Info: Try loading font information for T5+fpl on input line 59. (c:/usr/local/share/texmf/tex/latex/vntex/t5fpl.fd File: t5fpl.fd 2005/09/13 font definitions for T5/fpl. ) LaTeX Font Info: Try loading font information for T5+utm on input line 64. (c:/usr/local/share/texmf/tex/latex/vntex/t5utm.fd File: t5utm.fd 2005/08/24 Fontinst v1.929 font definitions for T5/utm. ) [2 ] LaTeX Font Info: Try loading font information for T5+pag on input line 75. (c:/usr/local/share/texmf/tex/latex/vntex/t5pag.fd File: t5uag.fd 2005/08/24 Fontinst v1.929 font definitions for T5/pag. ) LaTeX Font Info: Try loading font information for T5+pbk on input line 82. (c:/usr/local/share/texmf/tex/latex/vntex/t5pbk.fd File: t5ubk.fd 2005/08/24 Fontinst v1.929 font definitions for T5/pbk. ) LaTeX Font Info: Try loading font information for T5+pcr on input line 91. (c:/usr/local/share/texmf/tex/latex/vntex/t5pcr.fd File: t5ucr.fd 2005/08/24 Fontinst v1.929 font definitions for T5/pcr. ) LaTeX Font Info: Try loading font information for T5+phv on input line 98. (c:/usr/local/share/texmf/tex/latex/vntex/t5phv.fd File: t5uhv.fd 2005/08/24 Fontinst v1.929 font definitions for T5/phv. ) [3 ] LaTeX Font Info: Try loading font information for T5+pnc on input line 107. (c:/usr/local/share/texmf/tex/latex/vntex/t5pnc.fd File: t5unc.fd 2005/08/24 Fontinst v1.929 font definitions for T5/pnc. ) LaTeX Font Info: Try loading font information for T5+ppl on input line 116. (c:/usr/local/share/texmf/tex/latex/vntex/t5ppl.fd File: t5upl.fd 2005/08/24 Fontinst v1.929 font definitions for T5/ppl. ) LaTeX Font Info: Try loading font information for T5+ptm on input line 128. (c:/usr/local/share/texmf/tex/latex/vntex/t5ptm.fd File: t5utm.fd 2005/08/24 Fontinst v1.929 font definitions for T5/ptm. ) LaTeX Font Info: Try loading font information for T5+uzcm on input line 136. (c:/usr/local/share/texmf/tex/latex/vntex/t5uzcm.fd File: t5uzcm.fd 2005/09/05 Fontinst v1.929 font definitions for T5/uzcm. ) [4 ] (./urwvn-test.aux) ) Here is how much of TeX's memory you used: 2046 strings out of 94125 25552 string characters out of 1168495 75062 words of memory out of 1500000 5249 multiletter control sequences out of 10000+50000 154501 words of font info for 82 fonts, out of 2000000 for 2000 679 hyphenation exceptions out of 8191 35i,7n,45p,189b,220s stack positions out of 3000i,500n,5000p,300000b,5000s {c:/usr/local/share/texmf/fonts/enc/dvips/base/t5.enc}<c: /usr/local/share/texmf/fonts/type1/bluesky/cmtt10.pfb><c:/usr/local/share/texmf /fonts/type1/vntex/urwvn/fplrc8v.pfb><c:/usr/local/share/texmf/fonts/type1/vnte x/urwvn/uagd8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uagdo8v.pf b><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uagk8v.pfb><c:/usr/local/sh are/texmf/fonts/type1/vntex/urwvn/uagko8v.pfb><c:/usr/local/share/texmf/fonts/t ype1/vntex/urwvn/ubkd8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/u bkd8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ubkdi8v.pfb><c:/usr /local/share/texmf/fonts/type1/vntex/urwvn/ubkl8v.pfb><c:/usr/local/share/texmf /fonts/type1/vntex/urwvn/ubkl8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex /urwvn/ubkli8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ucrb8v.pfb ><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/ucrbo8v.pfb><c:/usr/local/sh are/texmf/fonts/type1/vntex/urwvn/ucrr8v.pfb><c:/usr/local/share/texmf/fonts/ty pe1/vntex/urwvn/ucrro8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/u hvb8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uhvbo8v.pfb><c:/usr /local/share/texmf/fonts/type1/vntex/urwvn/uhvr8v.pfb><c:/usr/local/share/texmf /fonts/type1/vntex/urwvn/uhvro8v.pfb><c:/usr/local/share/texmf/fonts/type1/vnte x/urwvn/uncb8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uncb8v.pfb ><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uncbi8v.pfb><c:/usr/local/sh are/texmf/fonts/type1/vntex/urwvn/uncr8v.pfb><c:/usr/local/share/texmf/fonts/ty pe1/vntex/urwvn/uncr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/un cri8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uplb8v.pfb><c:/usr/ local/share/texmf/fonts/type1/vntex/urwvn/uplb8v.pfb><c:/usr/local/share/texmf/ fonts/type1/vntex/urwvn/uplbi8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex /urwvn/uplr8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uplr8v.pfb> <c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/uplri8v.pfb><c:/usr/local/sha re/texmf/fonts/type1/vntex/urwvn/utmb8v.pfb><c:/usr/local/share/texmf/fonts/typ e1/vntex/urwvn/utmb8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/utm bi8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/urwvn/utmr8v.pfb><c:/usr/l ocal/share/texmf/fonts/type1/vntex/urwvn/utmr8v.pfb><c:/usr/local/share/texmf/f onts/type1/vntex/urwvn/utmri8v.pfb><c:/usr/local/share/texmf/fonts/type1/vntex/ urwvn/uzcmi8v.pfb> Output written on urwvn-test.pdf (4 pages, 713906 bytes). PDF statistics: 172 PDF objects out of 1000 (max. 8388607) 0 named destinations out of 1000 (max. 131072) 1 words of extra memory for PDF output out of 10000 (max. 10000000)

2 1

[ pdftex-Feature Requests-421 ] \pdf shell escape addition
by noreply＠sarovar.org 28 Dec '06

28 Dec '06

Feature Requests item #421, was opened at 2005-08-26 20:32 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106 >Category: web2c Group: None >Status: Closed Resolution: Accepted Priority: 5 Submitted By: ivo welch (iaw4) Assigned to: Taco Hoekwater (taco) Summary: \pdf shell escape addition Initial Comment: I would humbly request that in addition add to \write18 ('--shell-escape'), you add a new command, say \input18 (or \pdftexshellinput18), which like \write18 executes a system() command on its argument, but which then pushes the stdout output from this shell command into the stdin stream that TeX is processing. (no, writing to a file and then inputting it does not do the job.) I cannot contribute to the code base of TeX, which seems like black magic to me. But I can offer $300 for this facility. If someone was planning to spend the time to do this anyway, this may push him/her over the margin. However, it is important to me that this enters the standard feature set of pdftex, so that it will persist through future versions, so this would be part of the bargain here. regards, /ivo welch ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-06-12 20:11 Message: Logged In: YES user_id=1608 > i.e. even \immediate\closeout doesn't make the file > immediately visible and fully readable? > isn't this a bug, if it is so? it is a bug in certain operating systems, not in TeX ;-) > btw, how will this work in case of non-immediate > \openin and \openout? (in case they will end up executed > during the \shipout?) The pipes will be opened (and closed, hopefully) during shipout, not before (just like normal '\openout' files). ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-12 18:49 Message: Logged In: NO > one of the reasons why intermediate files don't work > is that it interferes with flushing of files > [and the moment that files are seen] i.e. even \immediate\closeout doesn't make the file immediately visible and fully readable? isn't this a bug, if it is so? nevertheless, the Taco's implementation of this feature is nice; btw, how will this work in case of non-immediate \openin and \openout? (in case they will end up executed during the \shipout?) ---------------------------------------------------------------------- Comment By: Hans Hagen (hagen) Date: 2006-06-12 11:08 Message: Logged In: YES user_id=927 it may interest you that taco, fabrice an i have been playing with piping the last couple of weeks; we're still struggling with decent ways to get around operating system related problems; in order for such a feature (actually more generic that you suggest) to work, it must be cross platform; btw, one of the reasons why intermediate files don't work is that it interferes with flushing of files [and the moment that files are seen] Hans ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2006-06-11 15:36 Message: Logged In: YES user_id=1608 Hi Ivo, Sorry, I had completely forgotten about this. Attached is a (preliminary?) patch for openclose.c (in the texk/web2c/lib directory) that gives this functionality. It is a really simple thing: if the first character of a filename for \openin or \openout is a pipe symbol (|), the filename is assumed to be a request for a pipe to a command line that is given in the rest of the filename. Of course, you need "shell_escape = t" in your texmf.cnf for this to work. And whether or not this makes it to the distribution(s) is not up to me, of course. Have fun, Taco ------------------- Two small examples: \openin1= "|ls -l" \loop \unless \ifeof1 \read1 to \cs \message{\meaning\cs} \repeat \openout1= "|sort >alphabet.tex" \write1{b} \write1{a} \write1{c} \closeout1 \bye ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2006-06-11 04:58 Message: Logged In: NO could you please clarify why "no, writing to a file and then inputting it does not do the job"? ---------------------------------------------------------------------- Comment By: ivo welch (iaw4) Date: 2006-06-10 23:05 Message: Logged In: YES user_id=2771 any chance this will happen, taco? regards, /ivo ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2005-08-27 09:01 Message: Logged In: YES user_id=1608 I have an idea on how to do this, so I've assigned it to myself ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=421&group_id=106

1 0

Re: [NTG-pdftex] [tex-live] \pdffontattr in pdftex-1.40.0-rc4
by Akira Kakuto 28 Dec '06

28 Dec '06

> in the intended cases it means, that it was tried to add two different > font attributes to the same font dictionary. But here is a case where > this happens even without: > > \pdfcompresslevel=0 > \nopagenumbers > \font\aa cmr10 at 10pt > \pdffontattr\aa {foo} > \aa abc > \font\bb cmr10 at 11pt > %\pdffontattr\bb {bar} > \bb abc > \bye In the above case, I also encounter the warning. (Probably test files in vntex may be different.) Thanks Hartmut, Akira

1 0

Re: [NTG-pdftex] \pdffontattr in pdftex-1.40.0-rc4
by Reinhard Kotucha 27 Dec '06

27 Dec '06

Akira, I put my response back to the pdftex developers list because I think that it is very helpful if the developer who implemented the message "pdfTeX warning (\pdffontattr): font \^^@ has conflicting attributes" can tell us a bit more about it's meaning. >>>>> "Akira" == Akira Kakuto <kakuto(a)fsci.fuk.kindai.ac.jp> writes: > Hi Reinhard, >> I'm trying to run the vntex testfiles with the current pdftex >> release recently uploaded to the TeXLive repository by Martin. >> >> Can anybody tell me what the warnings mean? >> >> pdfTeX warning (\pdffontattr): font \^^@ has conflicting >> attributes > Can you please tell me the name of the test file if it is in CTAN? Try ${TEXMF}/doc/generic/vntex/tests/urwvn-test.tex which you already have installed. urwvn-test.tex requires other files from the tests directory. You do not need the latest version, I did not change the content of the file. Recent versions load a .cls file while former versions loaded a .sty file. That's all. There should not be any differences between the files from TL-2005 and the current files. > (I've tested a few vntex tests and I don't have the warning. > Maybe I'm testing different files.) The files had not been changed, I got the messages after I switched from pdftex-1.30 to pdftex 1.40. Thank you very much, Akira. Best 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. ----------------------------------------------------------------------------

1 0

Some 1.40 beta nitpicking
by Frank Küster 27 Dec '06

27 Dec '06

Hi, - INSTALL says: "The code of pdfTeX is in src/texk/web2c/pdfetexdir" However, s/pdfetexdir/pdftexdir/ - pdftex.xml says that pdfTeX is an "extension of TeX which directly generates PDF documents instead of DVI". Since it's routinely used to generate DVI now, and even provides additional features in DVI mode, this could be changed to "extension of TeX which allows direct generatiion of PDF documents and provides micro-typographic (and other) features in DVI and PDF mode". I'm also unsure whether pdflatex really deserves special mentioning? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)

1 0

[ pdftex-Feature Requests-715 ] highlight ligatures
by noreply＠sarovar.org 22 Dec '06

22 Dec '06

Feature Requests item #715, was opened at 2006-12-22 10:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106 >Category: Fonts >Group: v1.50 Status: Open Resolution: None >Priority: 3 Submitted By: Uli Laube (ulilaube) >Assigned to: Hartmut Henkel (hhenkel) Summary: highlight ligatures Initial Comment: Hello! >From time to time people in de.comp.text.tex ask for a solution to remove ligatures from german words automatically. As this requires quite some knowledge of the morphology of the german language, packages like rmligs or ligatex use lists of words to remove unwanted ligatures. As this depends on the ligatures available in the font used, it is quite troublesome to the compile the lists. I'am proposing the following addtion to be incorporated into pdftex: highlighting of the ligatures. If enabled pdftex uses a bold version of the font when it inserts ligatures in normal text and vice versa. Like /em and /emph work for italic text. This would allow the user of pdftex to prepare a draft copy of the document were all ligatures are highlighted and can be easily spotted. The user can then insert "| manually to remove the unwanted ligatures. Kind Regards and Happy Holidays Uli Laube ---------------------------------------------------------------------- Comment By: Uli Laube (ulilaube) Date: 2006-12-22 14:12 Message: Logged In: YES user_id=4116 Highlighting the ligatures would only be necessary in a draft copy. Then one would insert the "| in the appropriate places and disable the highlighting. A change in paragraph breaking is acceptable in my opinion as I would not want to distribute the version with highlighted ligatures. Changing the font color is a nice idea. But it would require an extra virtual font for every font used in the document as they might have different ligatures. Seems to me, that I have to learn how to write .vlp files :) ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 14:08 Message: Logged In: YES user_id=929 ...an example .vpl file with colorchange command: (CHARACTER O 2 (CHARWD R 0.777781) (CHARHT R 0.683332) (MAP (SPECIAL pdf:direct: 0.486 0.104 0.291 rg) (SETCHAR O 2) (SPECIAL pdf:direct: 0 0 0 rg) ) ) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 13:55 Message: Logged In: YES user_id=929 For highlighting a boldface font is needed that has the same metrics as the non-highlighted one, to keep paragraph breaking unchanged. What you can do right now is to generate a virtual font that contains colored ligatures! It is in fact possible to add PDF color change command specials into the .vpl virtual property list files of the virtual font, These commands will then be inserted into the PDF page stream in front of the glyphs. But also some solution on engine level should be doable. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Uli Laube (ulilaube) Date: 2006-12-22 11:22 Message: Logged In: YES user_id=4116 If a document uses different fonts, they might have different ligatures available. The special font and the macro packages might not be aware of this. As far as I know, the insertion of ligatures happens late when the .dvi oder .pdf is created. My hope is that switching to the bold version of the font when a ligature is inserted might be a way to have this feature work for all fonts. ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-12-22 11:08 Message: Logged In: YES user_id=3360 Since ligatures are inserted according to information in the fonts, I think this should be implemented as a combination of a special font (which uses noticeably different glyphs for ligatures), and a macro package that switches fonts. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106

1 0

[ pdftex-Feature Requests-715 ] highlight ligatures
by noreply＠sarovar.org 22 Dec '06

22 Dec '06

Feature Requests item #715, was opened at 2006-12-22 10:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Uli Laube (ulilaube) Assigned to: Nobody (None) Summary: highlight ligatures Initial Comment: Hello! >From time to time people in de.comp.text.tex ask for a solution to remove ligatures from german words automatically. As this requires quite some knowledge of the morphology of the german language, packages like rmligs or ligatex use lists of words to remove unwanted ligatures. As this depends on the ligatures available in the font used, it is quite troublesome to the compile the lists. I'am proposing the following addtion to be incorporated into pdftex: highlighting of the ligatures. If enabled pdftex uses a bold version of the font when it inserts ligatures in normal text and vice versa. Like /em and /emph work for italic text. This would allow the user of pdftex to prepare a draft copy of the document were all ligatures are highlighted and can be easily spotted. The user can then insert "| manually to remove the unwanted ligatures. Kind Regards and Happy Holidays Uli Laube ---------------------------------------------------------------------- >Comment By: Uli Laube (ulilaube) Date: 2006-12-22 14:12 Message: Logged In: YES user_id=4116 Highlighting the ligatures would only be necessary in a draft copy. Then one would insert the "| in the appropriate places and disable the highlighting. A change in paragraph breaking is acceptable in my opinion as I would not want to distribute the version with highlighted ligatures. Changing the font color is a nice idea. But it would require an extra virtual font for every font used in the document as they might have different ligatures. Seems to me, that I have to learn how to write .vlp files :) ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 14:08 Message: Logged In: YES user_id=929 ...an example .vpl file with colorchange command: (CHARACTER O 2 (CHARWD R 0.777781) (CHARHT R 0.683332) (MAP (SPECIAL pdf:direct: 0.486 0.104 0.291 rg) (SETCHAR O 2) (SPECIAL pdf:direct: 0 0 0 rg) ) ) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 13:55 Message: Logged In: YES user_id=929 For highlighting a boldface font is needed that has the same metrics as the non-highlighted one, to keep paragraph breaking unchanged. What you can do right now is to generate a virtual font that contains colored ligatures! It is in fact possible to add PDF color change command specials into the .vpl virtual property list files of the virtual font, These commands will then be inserted into the PDF page stream in front of the glyphs. But also some solution on engine level should be doable. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Uli Laube (ulilaube) Date: 2006-12-22 11:22 Message: Logged In: YES user_id=4116 If a document uses different fonts, they might have different ligatures available. The special font and the macro packages might not be aware of this. As far as I know, the insertion of ligatures happens late when the .dvi oder .pdf is created. My hope is that switching to the bold version of the font when a ligature is inserted might be a way to have this feature work for all fonts. ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-12-22 11:08 Message: Logged In: YES user_id=3360 Since ligatures are inserted according to information in the fonts, I think this should be implemented as a combination of a special font (which uses noticeably different glyphs for ligatures), and a macro package that switches fonts. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106

1 0

[ pdftex-Feature Requests-715 ] highlight ligatures
by noreply＠sarovar.org 22 Dec '06

22 Dec '06

Feature Requests item #715, was opened at 2006-12-22 10:48 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Uli Laube (ulilaube) Assigned to: Nobody (None) Summary: highlight ligatures Initial Comment: Hello! >From time to time people in de.comp.text.tex ask for a solution to remove ligatures from german words automatically. As this requires quite some knowledge of the morphology of the german language, packages like rmligs or ligatex use lists of words to remove unwanted ligatures. As this depends on the ligatures available in the font used, it is quite troublesome to the compile the lists. I'am proposing the following addtion to be incorporated into pdftex: highlighting of the ligatures. If enabled pdftex uses a bold version of the font when it inserts ligatures in normal text and vice versa. Like /em and /emph work for italic text. This would allow the user of pdftex to prepare a draft copy of the document were all ligatures are highlighted and can be easily spotted. The user can then insert "| manually to remove the unwanted ligatures. Kind Regards and Happy Holidays Uli Laube ---------------------------------------------------------------------- >Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 14:08 Message: Logged In: YES user_id=929 ...an example .vpl file with colorchange command: (CHARACTER O 2 (CHARWD R 0.777781) (CHARHT R 0.683332) (MAP (SPECIAL pdf:direct: 0.486 0.104 0.291 rg) (SETCHAR O 2) (SPECIAL pdf:direct: 0 0 0 rg) ) ) Regards, Hartmut ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-12-22 13:55 Message: Logged In: YES user_id=929 For highlighting a boldface font is needed that has the same metrics as the non-highlighted one, to keep paragraph breaking unchanged. What you can do right now is to generate a virtual font that contains colored ligatures! It is in fact possible to add PDF color change command specials into the .vpl virtual property list files of the virtual font, These commands will then be inserted into the PDF page stream in front of the glyphs. But also some solution on engine level should be doable. Regards, Hartmut ---------------------------------------------------------------------- Comment By: Uli Laube (ulilaube) Date: 2006-12-22 11:22 Message: Logged In: YES user_id=4116 If a document uses different fonts, they might have different ligatures available. The special font and the macro packages might not be aware of this. As far as I know, the insertion of ligatures happens late when the .dvi oder .pdf is created. My hope is that switching to the bold version of the font when a ligature is inserted might be a way to have this feature work for all fonts. ---------------------------------------------------------------------- Comment By: Frank Küster (frank) Date: 2006-12-22 11:08 Message: Logged In: YES user_id=3360 Since ligatures are inserted according to information in the fonts, I think this should be implemented as a combination of a special font (which uses noticeably different glyphs for ligatures), and a macro package that switches fonts. ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=715&group_id=106

1 0