[pdftex] pdftex Digest, Vol 131, Issue 5

Cirilo Alvarez cirilo_alvarez at hotmail.com
Thu Jul 16 06:45:55 CEST 2015 


> From: pdftex-request at tug.org
> Subject: pdftex Digest, Vol 131, Issue 5
> To: pdftex at tug.org
> Date: Tue, 14 Jul 2015 00:23:53 +0200
> 
> Send pdftex mailing list submissions to
> 	pdftex at tug.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://tug.org/mailman/listinfo/pdftex
> or, via email, send a message with subject or body 'help' to
> 	pdftex-request at tug.org
> 
> You can reach the person managing the list at
> 	pdftex-owner at tug.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pdftex digest..."
> 
> 
> Today's Topics:
> 
>    1.  Please make the CreationDate, ModDate and ID field
>       deterministic (Nicolas Boulenguez)
>    2. Embedding a font to use it in a form (Gregory Heytings)
>    3. Re: Embedding a font to use it in a form (Karl Berry)
>    4. Re: Embedding a font to use it in a form (Gregory Heytings)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 13 Jul 2015 16:08:51 +0200
> From: Nicolas Boulenguez <nicolas at debian.org>
> To: <pdftex at tug.org>
> Subject: [pdftex]  Please make the CreationDate, ModDate and ID field
> 	deterministic
> Message-ID: <20150713140851.GA19905 at pegase>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hello all.
> 
> As the original submitter, I would have liked an opportunity to
> discuss the choices, or else a word of explanation about them, or at
> least an alert about the commit, as I did mention that I was not
> reading the list [1].
> 
> I understand that upstream authors of a widely used software need to
> discuss privately before announcing changes, but now that you are at
> the coding stage, please consider answering a few questions about the
> selected design.
> 
> The CreationDate and ModDate are optional.  Why set them, unless
> \pdfinfo asks for that?
> 
> If you set them by default, and we do not find a work-around like [2],
> everyone concerned with reproducible builds will need to insert
>   \pdfinfo{/CreationDate(D:19900101000000Z00'00')/ModDate(D:19900101000000Z00'00')}
> or
>   \pdfinfo{/CreationDate(D:$DATEZ00'00')/ModDate(D:$DATEZ00'00')}
> into every TeX source during each build, or patch pdftex for its own
> use.  What concrete need does \pdfinfoomitdate answer?
> 
> The ID field is optional. Why set it, unless \pdftrailerid or similar
> asks for that?
> 
> If you set it by default, the following suggestion may help doing so
> without a new \pdftrailerid macro.
> 
> As I understand section 10.3 of the PDF specification [3], a md5 sum
> of the time, directory and base name is only a very vague
> implementation suggestion. Any randomly generated string, or
> non-cryptographic hash sum of the PDF file would satisfy the purpose
> better, with the latter being reproducible.
> 
> For example, would you consider defining the ID as an 8 characters
> hexadecimal represention of a 32 bits XOR sum of all contents written
> to the output file so far? The performance impact and collision risk
> would both be very small.
> 
> Is there any benefit in keeping the current implementation by default?
> 
> In the current implementation, what is the benefit of taking gmtime()
> into acount for the md5 sum, instead of CreationDate?
> 
> [1] http://tug.org/mailman/htdig/pdftex/2015-May/008940.html
> [2] http://tug.org/pipermail/pdftex/2015-July/008954.html
> [3] http://www.adobe.com/devnet/pdf/pdf_reference_archive.html
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 13 Jul 2015 15:31:51 +0200
> From: Gregory Heytings <ghe at sdf.org>
> To: <pdftex at tug.org>
> Subject: [pdftex] Embedding a font to use it in a form
> Message-ID: <alpine.DEB.2.11.1507131521440.7198 at svobanppv.bet>
> Content-Type: text/plain; format=flowed; charset="US-ASCII"
> 
> 
> Hi,
> 
> I try to use pdfTeX to create (text field) forms, and I would like to use 
> an embedded font for the text fields, instead of the standard system 
> fonts.  This is feasible (Acrobat can do it), be it that the font needs to 
> be embedded in full (i.e. not a subset), and apparently in a special way 
> (they do not appear in the list of embedded fonts in Acrobat).
> 
> This question is more or less similar to: http://tex.stackexchange.com/questions/36630/hyperref-how-to-format-text-in-a-forms-text-field , but it got no answer.
> 
> Does anyone know how to do this?
> 
> Thanks,
> 
> Gregory
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 13 Jul 2015 21:57:04 +0000
> From: Karl Berry <karl at freefriends.org>
> To: <ghe at sdf.org>
> Cc: <pdftex at tug.org>
> Subject: Re: [pdftex] Embedding a font to use it in a form
> Message-ID: <201507132157.t6DLv4Jg012826 at freefriends.org>
> Content-Type: text/plain
> 
> It should work to fully embed a font (no subsetting) by using <<foo.pfb
> in the map file entry instead of <foo.pfb.  This is tersely discussed in
> the pdftex manual under "fontfile", page 11 in the pdftex-a.pdf that is
> in TeX Live 2015.
> 
> However, I have no knowledge of how to specify a font for use in text
> field forms.  Maybe someone else here (Heiko, Martin ... ?) can help.
> 
> Best,
> Karl
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 14 Jul 2015 00:23:45 +0200
> From: Gregory Heytings <ghe at sdf.org>
> To: Karl Berry <karl at freefriends.org>
> Cc: <pdftex at tug.org>
> Subject: Re: [pdftex] Embedding a font to use it in a form
> Message-ID: <alpine.DEB.2.11.1507140004210.26890 at svobanppv.bet>
> Content-Type: text/plain; format=flowed; charset="US-ASCII"
> 
> 
> Hi Karl,
> 
> Many thanks for your answer!
> 
> >
> > It should work to fully embed a font (no subsetting) by using <<foo.pfb 
> > in the map file entry instead of <foo.pfb.  This is tersely discussed in 
> > the pdftex manual under "fontfile", page 11 in the pdftex-a.pdf that is 
> > in TeX Live 2015.
> >
> 
> After some more research, it seems indeed that one aspect of the problem 
> is to fully embed the font.  Apparently it does not work with pfa/pfb 
> fonts, however (but I am not sure that it cannot be done); it does work, 
> for sure, with an otf font file.
> 
> >
> > However, I have no knowledge of how to specify a font for use in text 
> > field forms.  Maybe someone else here (Heiko, Martin ... ?) can help.
> >
> 
> So far my best answer to my own question goes as follows: one has to 
> insert the otf file as a pdf object, with something like "\pdfobj stream 
> attr { /Subtype /OpenType } file {Font.otf}", and then create two other 
> pdf objects manually, namely a /FontDescriptor and a /Font, the latter 
> containing /FirstChar 0 /LastChar 255, and 256 values in the /Width array. 
> Then that font can be used in a form, by adding a reference to it in the 
> resource dictionary of the form.
> 
> (Once I got the above scheme working, I tried to remplace the "\pdfobj 
> stream attr { /Subtype /OpenType } file {Font.otf}" with a "\pdfobj stream 
> attr { /Subtype /Type1 } file {Font.pfa}", but it did not work anymore.)
> 
> The problem is that doing this involves a lot of manual work.  A more 
> direct way to do this (with pdfTeX) would be much appreciated.
> 
> Gregory
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> pdftex mailing list
> pdftex at tug.org
> http://tug.org/mailman/listinfo/pdftex
> 
> 
> ------------------------------
> 
> End of pdftex Digest, Vol 131, Issue 5
> **************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/pdftex/attachments/20150716/c2bb8f97/attachment-0001.html>

More information about the pdftex mailing list