February 2007 - ntg-pdftex - NTG Mailing Lists

[ pdftex-Bugs-729 ] problem with pdftex-1.40.1 and Gentium ligatures
by noreply＠sarovar.org 02 Feb '07

02 Feb '07

Bugs item #729, was opened at 2007-02-02 14:33 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: Accepted Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with pdftex-1.40.1 and Gentium ligatures Initial Comment: Hi, Johan Sandblom ran into a problem with Gentium that seems to be related to pdftex's handling of cff fonts. Have a look the attached example. When you view the generated pdf document in Acrobat, there is no problem, but when you print it (at least in ar7), the Gentium c haracters are not visible at all in the output. Included is the output of acroread 7.0.8's print-to-file on linux . The really weird part is that removing the chancery font fixes the problem with the Gentium. /me doesn't get it, I hope someone else understand what happens. Taco ---------------------------------------------------------------------- Comment By: Reinhard Kotucha (reinhard) Date: 2007-02-02 20:20 Message: Logged In: YES user_id=4195 It seems that Gentium is empty: >From example-ptf-7.0.8.ps: [...] %ADOBeginSubsetFont: QCTAAA+Gentium Initial %ADOt1write: (1.0.24) %%Copyright: Copyright 2007 Adobe System Incorporated. All rights reserved. [...] /Encoding 256 array 0 1 255 {1 index exch /.notdef put} for def [...] dup /CharStrings 1 dict dup begin /.notdef <1C60D8A8C9B88EAF6D> |- end put [...] Please try with pdftops, it seems that AR is a bit confused. Regards, Reinhard ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2007-02-02 15:30 Message: Logged In: YES user_id=421 Further observations: kpdf and xpdf show the Gentium characters, gs 8.54 doesn't. A print to file of kpdf doesn't have the "fi", only "ll 1". ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106

1 0

[ pdftex-Bugs-729 ] problem with pdftex-1.40.1 and Gentium ligatures
by noreply＠sarovar.org 02 Feb '07

02 Feb '07

Bugs item #729, was opened at 2007-02-02 14:33 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106 Category: Fonts Group: v1.40.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with pdftex-1.40.1 and Gentium ligatures Initial Comment: Hi, Johan Sandblom ran into a problem with Gentium that seems to be related to pdftex's handling of cff fonts. Have a look the attached example. When you view the generated pdf document in Acrobat, there is no problem, but when you print it (at least in ar7), the Gentium c haracters are not visible at all in the output. Included is the output of acroread 7.0.8's print-to-file on linux . The really weird part is that removing the chancery font fixes the problem with the Gentium. /me doesn't get it, I hope someone else understand what happens. Taco ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2007-02-02 15:30 Message: Logged In: YES user_id=421 Further observations: kpdf and xpdf show the Gentium characters, gs 8.54 doesn't. A print to file of kpdf doesn't have the "fi", only "ll 1". ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106

1 0

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

02 Feb '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-02-02 13:54 Message: Logged In: YES user_id=710 the warning message can be removed. I left it there since I don't know what happens if a virtual font is loaded, used and then expanded and used again with font expansion. It should be alright to do so, but I am not very sure. Anyway, I will change the warning to be issued for non-virtual fonts only. It turned to be a design mistake that the \pdffontexpand primitive takes a base font and turns it to an expanded font. It would be better it was more like \letterspacefont, ie it should create a new font and leave the original font intact. ---------------------------------------------------------------------- Comment By: Taco Hoekwater (taco) Date: 2007-02-02 07:30 Message: Logged In: YES user_id=1608 > I hope luatex will abolish with this nonsensical connexion of ligatures and kerns? Yes. ligatures and kerns are totally separate in luatex. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-02-01 19:02 Message: Logged In: YES user_id=2217 If the warning is misleading, should it not be removed? On a different matter: Since \letterspacefont issues set_no_ligatures, there won't be any kerning, either. There's no way around that, I guess? (I hope luatex will abolish with this nonsensical connexion of ligatures and kerns?) ---------------------------------------------------------------------- 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-729 ] problem with pdftex-1.40.1 and Gentium ligatures
by noreply＠sarovar.org 02 Feb '07

02 Feb '07

Bugs item #729, was opened at 2007-02-02 14:33 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106 Category: Fonts Group: v1.40.1 Status: Open Resolution: None Priority: 5 Submitted By: Taco Hoekwater (taco) Assigned to: Hartmut Henkel (hhenkel) Summary: problem with pdftex-1.40.1 and Gentium ligatures Initial Comment: Hi, Johan Sandblom ran into a problem with Gentium that seems to be related to pdftex's handling of cff fonts. Have a look the attached example. When you view the generated pdf document in Acrobat, there is no problem, but when you print it (at least in ar7), the Gentium c haracters are not visible at all in the output. Included is the output of acroread 7.0.8's print-to-file on linux . The really weird part is that removing the chancery font fixes the problem with the Gentium. /me doesn't get it, I hope someone else understand what happens. Taco ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=729&group_id=106

1 0

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

02 Feb '07

Bugs item #712, was opened at 2006-12-12 03: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: Taco Hoekwater (taco) Date: 2007-02-02 08:30 Message: Logged In: YES user_id=1608 > I hope luatex will abolish with this nonsensical connexion of ligatures and kerns? Yes. ligatures and kerns are totally separate in luatex. ---------------------------------------------------------------------- Comment By: Robert (schlcht) Date: 2007-02-01 20:02 Message: Logged In: YES user_id=2217 If the warning is misleading, should it not be removed? On a different matter: Since \letterspacefont issues set_no_ligatures, there won't be any kerning, either. There's no way around that, I guess? (I hope luatex will abolish with this nonsensical connexion of ligatures and kerns?) ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2007-01-04 16: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 01: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 17: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 18: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 16: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 14: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 01 Feb '07

01 Feb '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-02-01 19:02 Message: Logged In: YES user_id=2217 If the warning is misleading, should it not be removed? On a different matter: Since \letterspacefont issues set_no_ligatures, there won't be any kerning, either. There's no way around that, I guess? (I hope luatex will abolish with this nonsensical connexion of ligatures and kerns?) ---------------------------------------------------------------------- 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

Re: [NTG-pdftex] [pdftex] a wrapper for using pdftex as a library call
by Thanh Han The 01 Feb '07

01 Feb '07

many thanks for a very informative response; I know little about system programming. I don't dare to make something very generic and secure. My initial thought is that this wrapper can ease the task converting a tex file to something else using pdftex or a tex-related program (I wanted to use the name 'runtex' for the wrapper but googling it found too many results). A developer who is not a tex guru can deploy this task via a well-defined API, and tex-specific issues can be (partly) hidden from him. I assume a few things as: - the application using runptex should not have setuid/setgid flag, and should not be run by root or a privileged user. - it's the responsibility of the application to ensure that the working dir are safe; for example the working dir must not be world-writable like /tmp, but rather a directory belongs to the process owner like $HOME/tmp or something similar. - there are some restrictions about paths and filenames: filename (without path) can contain only letters, digits and [-_.], path can contain the same plus path separator and space. - the main target plaform is linux; support for other platform is not mandatory if it's too difficult to do. Do you find those assumptions reasonable, or they are too much? > I assume your 'run_pdftex' interface is synchronous. IMO It would be at > least required to have an asynchronous version as well. I.e., a version > where you initiate the start and then later independently query and if > necessary wait for the result. The reason is obvious: the program can > do work on its own while TeX is running. Parallelism is extremely > important going forward. point taken > And an implementation detail: _never_ expose data structures unless it > is really, *REALLY* needed. I'm talking here about the > pdftex_data_struct, of course. > [...] point taken > case (BTW: why not return an error code and not just success/failure > information from the functions, then you don't have to pass a pointer to > the tmp variable to pds_print_error). I want to keep the error code and message inside the data structure, so that application can decide what to do with them. I also find it handy to for error handling in subroutines. For example if I use a check_path() subroutine inside init_pdftex_data() to check whether a path is valid, I can set the error code and message inside the check_path() function, which is simpler than to examine the return code of check_path() in init_pdftex_data(). And a simple return code is not enough informative, one often needs to report more detailed information than a return code, something like: opening tex file `/home/thanh/tex/foo.tex' for reading failed: file not found. > Anyway, if you make this change the information about the struct is > completely encapsulated in your code. This is important for > maintainability since it gives you the opportunity to change the > implementation as much as you want as long as the function interfaces > remain the same. agree > About pds_print_error_and_exit: such an interface is usually not useful > except in tiny little programs. Assume you write a graphical shell for > TeX. You don't want to terminate the program after a failed run, the > user should be able to fix problems and rerun. What is needed, though, > is the ability to show an error string. So, what maybe is needed is to > have a function which returns an error string which can be printed in > the appropriate way (on terminal, in dialog box, whatever). yes this function is little useful -- it's intended for testing/debugging purpose. Applications should handle the error in their way, using the error code and message stored in pdftex_data_struct. > About the interface naming: C's flat namespace is crowded. To minimize > the risk of conflicts you should standardize on a common prefix for all > function and type names and stick with it. E.g., > > pdftex_data_struct -> pdftexlib_data_struct > init_pdftex_data -> pdftexlib_data_init > pds_print_error_and_exit -> pdftexlib_error > run_pdftex -> pdftexlib_run > > you get the idea. agree. I will add runptex_ prefix to all relevant names. Thanh

1 0