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