PDF , or Portable Document Format, by Adobe , is a page description language derived from Postscript. In 2008, PDF became ISO standard 32000-1:2008, based on PDF version 1.7.
VI: There are two problems when using PDFs. One is that PDF is page based, like PostScript, so pagination is the application's headache. Add headers, footers, tables that span pages, and this soon gets to be like a mini typesetting program. Doing a canvas on one page (modulo the next para) or a text widget onto one page seems doable.
The other is that I haven't figured out how to wrap text consistently. e.g. if a text item uses the -width option in the canvas, then I don't know how to decide where to break the text. I have read about this, and I've heard that this is possible in 8.4.5 or 8.5, but I still don't know how.
From the packages below it is clear that the only really missing thing is the conversion of the text widget to PDF. This has not yet been done and working with fonts, type, and glyphs is perhaps also one of the most difficult parts of a PDF file. Further, it seems that the Tk text widget lacks some introspection features that are needed when converting a text widget to PDF.
What: Tclhpdf Where: http://reddog.s35.xrea.com/wiki/tclhpdf.html Description: Tcl interface to HARU Free PDF Library Updated: 2007-09 (Added by Roy Terry see comp.lang.tcl posting: 2007-09-22) Contact: [email protected]
What: TEItools
Where: http://xtalk.price.ru/SGML/TEItools/
Description: Collection of Tcl and other tool scripts used for
transforming SGML documents to various other formats. Currently
supports HTML, LaTeX2e, RTF, PS, and PDF. Uses CoST.
Updated: 04/1998
Contact: mailto:[email protected] What: WELD
Where: http://www.javafoundry.com/javapdf
Description: Web Enabled Logic Documents (WELD) make use of Jacl/Tcl to
provide the ability to hold WWW applications together. WELD is
a part of JavaPDF (the open source servlet utilities project).
Updated: 2001-08
Contact: mailto:[email protected] (Lee T Hall)
Epspdf is a utility for converting between PDF, eps and PostScript formats. It can be run via command line or with a Tk GUI. Packaged as a Starpack.
Sen Sass's employer generates PDF by way of Java classes converting Docbook to FO to PDF (!).
Perl and Python do PDF. For example, see Regular Expressions: Low-cost PDF% , Cameron Laird and Kathryn Soraiz, Unix Review , 2003-04. Tcl, of course, has ways to exploit anything available through those languages, including Tclperl and Tclpython.
Another well-worn pathway involves transforming HTML to PDF.
GS 2003-11-29: txt2pdf is a simple C source code to convert text files to PDF.
Googie: Image Magick contains import tool, which can be executed by exec, so we can import wish window and save it as PDF. We can also use TclMagick instead of exec.
tonytraductor: In TickleText I just did:
proc pdfout {} {
if {$::filename != " "} {
set data [.txt.txt get 1.0 {end -1c}]
set fileid [open $::filename w]
puts -nonewline $fileid $data
close $fileid
eval exec enscript $::filename -q -B -p $::filename.ps &
eval exec ps2pdf $::filename.ps $::filename.pdf &
eval exec rm $::filename.ps &
} else {
set filename [tk_getSaveFile -filetypes $::file_types]
set data [.txt.txt get 1.0 {end -1c}]
wm title . "Now Tickling: $::filename"
set fileid [open $::filename w]
puts -nonewline $fileid $data
close $fileid
eval exec enscript $::filename -q -B -p $::filename.pdf &
eval exec ps2pdf $::filename.ps $::filename.pdf &
eval exec rm $::filename.ps &
}
}but, honestly, I don't know if enscript works on Windows. Or for exporting .tex files to pdf I just used pdflatex in a similar manner.
proc texpdf {} {
if {$::filename ne { }} {
set data [.txt.txt get 1.0 {end -1c}]
set fileid [open $::filename w]
puts -nonewline $fileid $data
close $fileid
eval exec pdflatex $::filename
} else {
set filename [tk_getSaveFile -filetypes $::file_types]
set data [.txt.txt get 1.0 {end -1c}]
wm title . "Now Tickling: $::filename"
set fileid [open $::filename w]
puts -nonewline $fileid $data
close $fileid
eval exec pdflatex $::filename
}
}Of course, I'm a total newbie, so, perhaps I'm missing something here, or maybe there is a more efficient way to this. I don't know. It does work, though. The TeX to PDF procedure complains about the period in the filename, but, a friend gave me a perl script to shave off the extension, so, I think I can fix that...but with a perl script. Either way, despite the complaint, it generates a pdf file every time. I have posted samples to the Tickle Text site.
The page Parsing PDF has some code for reading PDF files.
pstoedit is a C++ program that translates PostScript and PDF graphics into other vector formats. Tk canvas is an output option.
The content of a PDF file has four sections: header, body, cross references, and trailer. In essence, a PDF file consists of so-called objects which describe how the document should look like and how they are inter-related. Besides the objects, a PDF file contains some information on how and where to find these objects. The small examples below show a very simple PDF file. Apart from that, PDF files can contain binary data, can be encrypted, may be "linearized" (for quick access over the web), and even contain different versions of the same document in an incremental way.
The header consists of one line like this:
%PDF-1.4
The number denotes the version of the file format. If the version specified is 1.4 or higher, the version specification can be overridden by a Version entry in the document's catalog dictionary.
The "1.4" in this example represents version 1.4 of the Adobe Portable Document Format, which is the version used by Acrobat 5. The highest valid value is "1.7" (Acrobat 8), because version 1.7 of the PDF specification was made into an ISO standard (ISO 32000:2008). After version 1.7, additional feature sets used by Acrobat are indicated by adding an ExtensionLevel key to the catalog dictionary.
The body is a collection of so-called PDF objects. These carry the content which is displayed in a PDF viewer application. An object can look like this:
3 0 obj << /Type /Page /Parent 2 0 R /Resources 4 0 R /MediaBox [0 0 595 842] /Contents [6 0 R] >> endobj
It is started by a line “<object number> <generation number> obj” and ended by “endobj”. In between there can be nearly anything depending on the type of the object. The example above shows a typical object containing a PDF dictionary (which is like a Tcl array or dictionary) with keys and corresponding values. The values can be arrays, numbers, strings, and such and even dictionaries again. PDF dictionaries can be said to contain metadata about the document and the content of the file. The real data are located in so-called streams:
8 0 obj << /Length 32 >> stream 10 10 m 10 100 l 100 100 l S endstream endobj
The above object contains a stream that paints two lines on a page.
This sections contains the byte offsets for all objects in a PDF file. Like this:
xref 0 10 0000000005 65535 f 0000000010 00000 n 0000000060 00000 n 0000000124 00000 n 0000000231 00000 n 0000000000 00001 f 0000000299 00000 n 0000000424 00000 n 0000000542 00000 n 0000000625 00000 n
In this example there are 10 objects in the PDF file. This section of the PDF file makes it possible for viewer applications to quickly locate the objects needed to paint a pages content to the screen without searching through a possibly huge file. You can think of it as a poor-man's database lookup table.
The trailer is normally the first thing read by the viewer application:
trailer << /Size 10 /Root 1 0 R /Info 9 0 R >> startxref 811 %%EOF
On the second but last line it contains the byte offset to the start of the cross-reference section. Th PDF dictionary before this offset number contains some information about the PDF. The line with the “/Root” entry is a link to the root object, which is the starting point for the viewer. The root object lists the Pages object which then again refers to the each Page object, and the Page object contains the list of things to paint.
Version 1.5 of the PDF specification introduces things called "Object Streams" and "Cross-Reference Streams". Objects streams are used to reduce the size of the PDF file. This is achieved by making most of the objects in the file into the content of a Stream Object, which stream can then be compressed. . Objects stored in an object stream are called "Compressed Objects". The PDF specification explicitly names them so even when not actually compressed. Cross-Reference streams allow to provide cross-reference information for compressed objects. A cross-reference stream identifies a stream object and then lists the offsets within the object's data stream for each of the referenced objects. A PDF file that uses object and cross-reference streams need not have a cross-reference table, in which case it would obviously not be compatible with previous versions of Acrobat. A PDF file that uses both cross-reference stream and cross-reference table is called "Hybrid". Such a document could be structured to contain different content depending on whether it is viewed by an older or newer PDF viewer.
The Mathematical Orchid: Does anybody know of a pure Tcl tool to read PDF files? (For diagnostic purposes. I have a PDF file here that Acrobat can't open; even the newest version. But the author claims "it works fine on my PC".)
As far as I know, Tcl is able to handle binary files, so it should in principle be possible to do something like this. The only real difficulty is that parts of the file can be encrypted and/or compressed. (Anybody ever wrote a pure Tcl DEFLATE decompressor?)
Orchid, CL works often with PDF (and the people who work with PDF), and I suspect there's a problem "upstream". Briefly, no, Tcl doesn't read PDF in the sense I believe you mean. You're welcome to e-mail or join the Chat, for more detailed advice.
Lars H: A practical advice (if you can't fix the problem upstream) is to try a different PDF viewer (e.g. ghostscript can handle not only postscript but also PDF, to mention the most cross-platform one). In my early experiments with generating PDF the files used to be viewable in everything I tried except Acrobat, and the error messages gave no information. (Later PDF specifications more properly described the issue that Acrobat got hung up on, though, so I managed to fix it.)
DKF: Check that the PDF file has been downloaded correctly. If it was downloaded as text, there can be corruption of the contents (which, unlike PostScript, are binary).
The Mathematical Orchid: Already tried Ghostscript. Gives me some error about "JavaScript is required". The problem is a PDF file with some diagrams which refuse to display. (Half the diagram shows up, then some cryptic error message.) Downloaded several times, still won't display. Author insists they display with his copy of Acrobat. I'm guessing they have some extra software or something that they've forgotten they have. Well anyway, I've read the PDF spec (and the PS one, actually), so maybe I'll have a go at writing something myself. (As I say, I can read the file in Notepad, but the FLATE compressed parts are a tad difficult to follow. Most of a PDF file is actually plain ASCII until you compress it...)
IDG: Recent versions of acrobat have javascript built in, but it can be turned off in the preferences menu. Do you have an old version, or have you got javascript turned off?
schlenk: Decoding the pdf stream isn't very hard, but your right that the compression is one thing that needs a bit more work, the rest is straight forward, unless you have edited pdfs with newer dicts. I have an example that reads PDF metadata with Tcl somewhere (need to search it...), was two hours work or so.
DKF: BTW, 8.6 has a built-in zlib deflate command.
"pdf417_encode (sourceforge ) converts ASCII strings into pdf417 barcode". NOTE: PDF417 barcodes have nothing whatsoever to do with Adobe's Portable Document Format.
AMG: Any advice on how to script filling in existing PDF forms? ABU: You can use tclmupdf ; try this
package require mupdf-notk set pdf [mupdf::open "myform.pdf"] $pdf field "FIELDNAME1" "FIELDVALUE1" $pdf field "FIELDNAME2" "FIELDVALUE2" ... $pdf close ;# pdf changes saved
Read more about the "field" and "fields" methods in the wiki page.