- ntg-pdftex - NTG Mailing Lists

Re: [NTG-pdftex] [pdftex] auto letter spacing
by Hans Hagen 12 Dec '06

12 Dec '06

Thanh Han The wrote: > On Mon, Dec 11, 2006 at 11:31:54PM +0100, Hans Hagen wrote: > >> Thanh Han The wrote: >> >>> Hi all, >>> >>> I am working on a primitive \letterspacefont that generates >>> a letter-spaced font from another font like this: >>> >>> ,-------- >>> | \font\f=cmr10 >>> | \letterspacefont\fx=\f 100 % letterspace \f by a factor 100/1000 >>> | \fx This is a text in letter-spaced cmr10 >>> `-------- >>> >>> the above example creates \fx as a virtual font, in which >>> each charater is taken from \f, and have a kern of >>> 50*quad(f)/1000 at each side. All this happens in pdftex >>> memory. >>> >>> However I am not sure the "more right" way to do this is that >>> each character c should have a kern of 5*width_of_c/1000 at >>> each side, ie the kern inserted around each character is >>> proportional to its width, instead of having a fixed global >>> value for all characters. This is more closed to the way font >>> expansion is done, but is different from what fontinst does >>> for letter-spacing. >>> >>> How do you see it? >>> >>> >> Is there a way to prevent the kern before or after a char? Say that we have >> a section title, in that case one does not want the margin to be spoiled >> (the first char needs to align then) >> > > I don't know of an easy way. But it's possible to have > another primitive that returns the kern at the left resp. > right side of a char from such a font. > > best would be to have something \noletterspacekern (will inhibit the next kern) \removeletterspacekern (removes the last kern, a kind of unkern) so that one can say: {\fx \noletterspacekern Some Text\removeletterspacekern} (\[left|right]letterspacekern<charnr> would be handy anyway) -- ----------------------------------------------------------------- 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 -----------------------------------------------------------------

1 0

[ pdftex-Bugs-712 ] problems with \letterspacefont
by noreply＠sarovar.org 12 Dec '06

12 Dec '06

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: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert (schlcht) Assigned to: Nobody (None) 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 ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=712&group_id=106

1 0

[ pdftex-Bugs-711 ] ToUnicode CMap feature does not work in recent beta
by noreply＠sarovar.org 11 Dec '06

11 Dec '06

Bugs item #711, was opened at 2006-12-09 16:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=711&group_id=106 >Category: Fonts >Group: v1.40.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Dohyun Kim (nomos) >Assigned to: The Thanh Han (hanthethanh) Summary: ToUnicode CMap feature does not work in recent beta Initial Comment: pdfTeX 1.40.0-beta-20061206 seems to have introduced a bug on ToUnicode CMap feature. While version 20061108 was ok about this, PDF file produced by beta-20061206 does not contain any ToUnicode CMap in any case. Even when I use the traditional \pdffontattr command, let alone the more recent \pdfgentounicode, I cannot find any unicode cmap notaion in the pdf. For your reference, I here link my test file (2Mb): http://people.ktug.or.kr/~nomos/mine/testtouni.tar.gz ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-11 18:20 Message: Logged In: YES user_id=421 A patch for this will be included in the next version (1.40). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=711&group_id=106

1 0

[ pdftex-Feature Requests-320 ] add support for a colour stack
by noreply＠sarovar.org 11 Dec '06

11 Dec '06

Feature Requests item #320, was opened at 2005-03-28 05:52 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=320&group_id=106 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Aleks Kleyn (aleks_kleyn) Assigned to: Nobody (None) Summary: add support for a colour stack Initial Comment: I want to change color of text using comand \textcolor {blue}. However when text flows from one page to another the color resets to standard on the next page. Initially I beleived that this problem of pdf. However I tried today latex.exe and then converted dvi to pdf. I got effect that I expected: text had on both pages the same color. However using of pdflatex is more better because it prepares bookmarks for pdf. ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-12-11 01:36 Message: Logged In: YES user_id=421 See patch 603. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-07-10 16:19 Message: Logged In: YES user_id=421 This is really a feature request. ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2005-06-16 14:45 Message: Logged In: YES user_id=421 The cause is a missing colour stack of pdfTeX; this is a known problem (and more properly a feature request). ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=496&aid=320&group_id=106

1 0

Re: [NTG-pdftex] [ pdftex-Bugs-711 ] ToUnicode CMap feature does not work in recent beta
by Thanh Han The 10 Dec '06

10 Dec '06

I forgot it when merging the patches by Hartmut. Will upload a patch soon. Thanks a lot for testing and reporting problems. Thanh On Sun, Dec 10, 2006 at 05:49:24PM +0900, Akira Kakuto wrote: > Hi, > > > pdfTeX 1.40.0-beta-20061206 seems to have introduced a > > bug on ToUnicode CMap feature. > > > > While version 20061108 was ok about this, PDF file > > produced by beta-20061206 does not contain any > > ToUnicode CMap in any case. > > I've also confirmed that Thanh (temporarily?) discarded > the "ToUnicode" feature. > > Thanks, > Akira > _______________________________________________ > ntg-pdftex mailing list > ntg-pdftex(a)ntg.nl > http://www.ntg.nl/mailman/listinfo/ntg-pdftex

1 0

Re: [NTG-pdftex] [ pdftex-Bugs-711 ] ToUnicode CMap feature does not work in recent beta
by Akira Kakuto 10 Dec '06

10 Dec '06

Hi, > pdfTeX 1.40.0-beta-20061206 seems to have introduced a > bug on ToUnicode CMap feature. > > While version 20061108 was ok about this, PDF file > produced by beta-20061206 does not contain any > ToUnicode CMap in any case. I've also confirmed that Thanh (temporarily?) discarded the "ToUnicode" feature. Thanks, Akira

1 0

[ pdftex-Bugs-711 ] ToUnicode CMap feature does not work in recent beta
by noreply＠sarovar.org 09 Dec '06

09 Dec '06

Bugs item #711, was opened at 2006-12-10 00:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=711&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dohyun Kim (nomos) Assigned to: Nobody (None) Summary: ToUnicode CMap feature does not work in recent beta Initial Comment: pdfTeX 1.40.0-beta-20061206 seems to have introduced a bug on ToUnicode CMap feature. While version 20061108 was ok about this, PDF file produced by beta-20061206 does not contain any ToUnicode CMap in any case. Even when I use the traditional \pdffontattr command, let alone the more recent \pdfgentounicode, I cannot find any unicode cmap notaion in the pdf. For your reference, I here link my test file (2Mb): http://people.ktug.or.kr/~nomos/mine/testtouni.tar.gz ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=711&group_id=106

1 0

[ pdftex-Patches-597 ] Patch for more structured font writing
by noreply＠sarovar.org 06 Dec '06

06 Dec '06

Patches item #597, was opened at 2006-08-20 16:37 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=597&group_id=106 Category: Fonts Group: v1.40.0 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Hartmut Henkel (hhenkel) Assigned to: The Thanh Han (hanthethanh) Summary: Patch for more structured font writing Initial Comment: Now there are individual structures for font dictionaries and font descriptors. Several font objects can share the same descriptor structure. All structures are registered in AVL trees and flushed at the end. The fm_entry structure is cleaned up, now contains mostly map related stuff. Font descriptors can be shared also by embedded PDF files. tfm_of_fm() is gone. New makesubsettag() based on md5sum() with collision detection. Written encoding vectors are minimized in size (try it out on pdftex-t.tex :-) Replacement of Type1 fonts from embedded files seems to work. TrueType writing not yet done, currently broken. Help appreciated! More see readme.pdf included in patch .tar file. Regards, Hartmut ---------------------------------------------------------------------- >Comment By: Martin Schröder (oneiros) Date: 2006-12-06 22:59 Message: Logged In: YES user_id=421 See patch 709 ---------------------------------------------------------------------- Comment By: Hartmut Henkel (hhenkel) Date: 2006-08-22 08:19 Message: Logged In: YES user_id=929 the patch doesn't fit to the TrueType model, needs more consideration... ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=597&group_id=106

2 1

pdftex-1.40.0-beta-20061206
by Martin Schröder 06 Dec '06

06 Dec '06

http://sarovar.org/download.php/1117/pdftex-1.40.0-beta-20061108-20061206.d… Another interim release incorporating Thanh's patches. I hope I haven't broken too much. --------------------------------------------------------------- pdfTeX 3.141592-1.40.0-beta-20061206 was released on 2006-12-06 --------------------------------------------------------------- - bugfix: crash with autokern (663) - memory for virtual fonts can now grow dynamically (patch 705) - rework the font mechanism (patches 597 and 709) - updated libpng to 1.2.14

1 0

[ pdftex-Patches-709 ] merging patch 597 by Hartmut
by noreply＠sarovar.org 06 Dec '06

06 Dec '06

Patches item #709, was opened at 2006-12-04 08:21 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=709&group_id=106 Category: Fonts Group: v1.40.0 Status: Open Resolution: None Priority: 6 Submitted By: The Thanh Han (hanthethanh) Assigned to: Hartmut Henkel (hhenkel) Summary: merging patch 597 by Hartmut Initial Comment: This is a patch against pdftex-1.40.0-beta-20061018 that merges patch 597 by Hartmut and does some clean up in the font mechanism. Testing welcome very much. ---------------------------------------------------------------------- >Comment By: The Thanh Han (hanthethanh) Date: 2006-12-06 17:05 Message: Logged In: YES user_id=710 patch updated to fix a bug with pdf inclusion. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-05 22:52 Message: Logged In: YES user_id=710 patch updated; tested with pdftex manual, microtype manual and base latex doc. A fix for bug #693 is included. ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-04 13:38 Message: Logged In: YES user_id=710 ah, sorry, my mistake. It's against pdftex-1.40.0-beta-20061108 (the latest beta), not pdftex-1.40.0-beta-20061018 ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-04 13:25 Message: Logged In: YES user_id=710 are you saying that you have troubles applying the patch against pdftex-1.40.0-beta-20061017? Can you please try to apply against pdftex-1.40.0-beta-20061018? I have checked everything again from the beginning as follows: - download and unpack http://sarovar.org/download.php/1100/pdftex-1.40.0-beta-20061017.tar.bz2 - download, ungzip and apply http://sarovar.org/download.php/1108/pdftex-1.40.0-beta-20061017-20061108.d… - download http://sarovar.org/tracker/download.php/106/495/709/237/pdftex-20061204-2.p… - cd /path/to/pdftex-1.40.0-beta-20061017/src - patch -p1 --dry-run /path/to/pdftex-20061204-2.patch The patch applied ok, apart from change-files.txt (I removed it from pdftexdir, as it's no longer relevant to pdftex). ---------------------------------------------------------------------- Comment By: Martin Schröder (oneiros) Date: 2006-12-04 12:33 Message: Logged In: YES user_id=421 I'm having troubles applying pdftex-20061204-2.patch against pdftex-1.40.0-beta-20061017, especially pdftex.web. Can you attach a diff against 1.40.0-beta-20061108 or your patched pdftex.web? ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2006-12-04 11:02 Message: Logged In: YES user_id=710 I updated the patch to revert auto kerns to be explicit. This will disable hyphenation if auto kern is used. On the other hand this is much more robust. The pending problems are: bug #693: still trying bug #484: will not be fixed, better treat it as a limitation bug #465: unlikely to be fixed ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=495&aid=709&group_id=106

1 0