# Tag Info

2

A quick solution, with pictures changed: \documentclass{article} \usepackage[draft]{graphicx} \usepackage{url} \begin{document} \noindent \begin{tabular}{l l l} CUSTOMER: & \includegraphics[width=6cm,height=1.5cm,keepaspectratio]{at} & Date: \\%{% now "SHORT_DATE_FORMAT" %}\\ & {\url{ qb_full_name|upper }} ...

6

Your EPS file doesn't tell the truth about its bounding box. It says %!PS-Adobe %%Creator: The Mighty Setlink. %%BoundingBox: 58 35 612 525 %%EndComments while you computed a bounding box equivalent to %%BoundingBox: 113 67 506 741 and it's the missing 216bp from the top that are the culprit. If I edit the EPS file so that it reads %!PS-Adobe ...

5

As @egreg says in the comments, the original eps file is defective, and gets cropped when it is converted to pdf. The bounding box is wrong, but you probably won't see this in a viewer because the first line is also wrong, causing the file to be displayed as ordinary (non-encapsulated) postscript (so the bounding box will be ignored and you will see a lot of ...

1

zathura is a highly customizable and functional document viewer. It provides a minimalistic and space saving interface as well as an easy usage that mainly focuses on keyboard interaction. It offers a vim-like experience and most settings can be customized. Main features: automatic document reloading supports PDF, PostScript and DjVu mouse-free navigation ...

3

The other PDF viewers (okular, evince) seem to show the list OK, but it seems that only hyperxmp helps to fix this for Adobe Reader. \documentclass{article} \makeatletter \def\keywords#1{\def\k@yw@rds{#1}} \AtBeginDocument{\hypersetup{pdfkeywords={\k@yw@rds}}} \makeatother \usepackage{hyperxmp} \usepackage{hyperref} \keywords{LaTeX update, clist item} ...

4

You have to use the comma list variable: \documentclass{article} \usepackage{xparse} \ExplSyntaxOn \clist_new:N \g_jcsres_keywords_clist \NewDocumentCommand \keywords {m} { \clist_gset:Nn \g_jcsres_keywords_clist {#1} } \AtBeginDocument { \hypersetup { pdfinfo= { Keywords={\clist_use:Nnnn \g_jcsres_keywords_clist {,~} {,~} {,~} }, } ...

12

Unicode mapping based on font encoding Packages cmap or mmap add information about glyph to Unicode conversions into the PDF file based on the used TeX encoding. The hooks into the font loading mechanism of LaTeX and should be used as early as possible, e.g.: \RequirePackage{mmap}% (\usepackage does not work before \documentclass) \documentclass{article} ...

4

I suggest you to add the following lines to your preamble: \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} It worked perfectly with me. I am on mac OS (Texmaker also) and I couldn't try on windows. Edit: As suggested by @egreg , adding \usepackage{lmodern} might help.

0

I think this problem is caused by the PDF version of your file (version 1.2): MacAir-Papiro \$ file analysiscompsSprJan2011.pdf analysiscompsSprJan2011.pdf: PDF document, version 1.2 Please, use your LaTeX code with a PDF file version 1.4... To change the version of your PDF file, see here.

2

Here's a way that uses the fabulous arara tool to implement @egreg's solution main.tex % arara: makechapters: {items: [lions, zebras]} \documentclass{report} \begin{document} \include{lions} \include{zebras} \end{document} When you call arara main.tex you will get lions.pdf and zebras.pdf. You can list any number of chapter files in the items ...

6

It seems pdfTeX has trouble with the font encodings in analysiscompsSprJan2011.pdf that was generated by dvipdfm 0.13.2d. Workarounds: The example works with LuaTeX. It seems to work, if the PDF file is preprocessed by pdfcrop. Usually pdfTeX tries to detect the fonts in embedded PDF files and if the fonts are known, then pdfTeX uses the fonts directly ...

4

This seems to be a version issue. With Adobe Reader X (and presumably XI) commenting is enabled by default. However, the feature is disabled in Reader 9 unless enabled by Acrobat. I tried a few hacks, but was unable to determine exactly what Acrobat does to a pdf to enable commenting. There is a discussion of alternative software for annotating pdfs on ...

1

From Adobe reader FAQ Can I edit a PDF file using Reader? No. You cannot make permanent changes to PDF files using Reader. To edit PDF files, purchase Acrobat software.

3

! LaTeX Error: Cannot determine size of graphic in time_elapsed.pdf (no Boundin gBox). That looks very much like the error produced by latex when you try to include pure PostScript (.ps) image instead of encapsulated PostScript (.eps). Are you sure you are using pdflatex command for TeX-ing?

3

Try to compile the following with pdflatex. The simplest workflow should be like the following. \documentclass[preview]{standalone} \usepackage{graphicx} \begin{document} \includegraphics{example-image-a}% no need to explicitly specify the file extension. \end{document} You will get an output as follows. Useful links: How to deal with PDF figures ...

0

I could fix this problem by setting a different monospace font: \newfontfamily\listingsfont[Scale=.7]{DejaVu Sans Mono} \lstset{basicstyle=\listingsfont} (This is more or less what @Jan Hlavacek describes in his comment)

7

Option pdfnewwindow controls this behaviour, e.g.: \usepackage[pdfnewwindow]{hyperref} or \hypersetup{pdfnewwindow} The latter can also be used in a local group. The setting is disabled by setting to false: \hypersetup{pdfnewwindow=false}

2

I've had a similar problem to the one in this thread. However, all the solutions proposed here were not suitable for my situation, since I wanted to compare (mostly) text changes. Moreover, the changes were not "minimal", and the new document was several pages longer than the old one. For instance, I have not been able to make pdfpagediff work. As for the ...

7

Below you will find the minimal code for plain pdfTeX. VPlayer.swf from the media9 package is used as the video player component. Put it into the current directory along with the video file. The code may be repeated for further video inclusions; VPlayer.swf will be embedded only once per document. plain pdf\TeX{} video example: ...

3

Just a remark to question 2: The closest in terms of printing is probably PostScript (.ps). That's what laser printers understand directly and what is usually sent to the printer when you press "print" in your PDF reader. Nevertheless, pdfTeX with PDF is certainly the output format of choice these days (e.g., since it has the beautiful microtype). DVI is ...

4

The documentation and source code of media9 by Alexander Grahn is probably a good place to start. The documentation additionally contains a list of technical references at the end which you might also want to read.

2

concerning the outputs: in the meanwhile, this question is answered in prior entries. concerning point 2, it seems that there is a difference due to the package microtype (see practical difference link). concerning the real output: if you define the printing version as real output, then maybe a pdf will be closest to the real output. for instance, if you ...

5

DVI is TeX' own DeVice Independent format, it isn't understood outside the TeX world. PostScript was Adobe's first own "device independent" format (it is a vector format, really a program to define what to paint on the page). PDF (Portable Document Format) is a development by Adobe on PostScript to make it more compact and add other capabilities. PDF is the ...

2

Briefly, because your question is nontrivial, so an answer might be huge. DVI = DeVice Independent: output format of original Knuth's TeX PDF (Adobe): now output format of pdfTEX PS (PostScript): PostScript is a language, describing a page (I know that it is a simplification). For example, some graphic inclusions are not aviable in some of these outputs ...

7

I guess that this is what you want (don't load geometry): \setstocksize{25cm}{18cm} %Finale \settrimmedsize{24cm}{17cm}{*} \settrims{0.5cm}{0.5cm} \setlrmarginsandblock{3cm}{2cm}{*}%%%% \setulmarginsandblock{2.5cm}{3cm}{*} \checkandfixthelayout \fixpdflayout The summary printed by memoir says ****************************************************** Stock ...

0

This probably could be done with PDF and JavaScript (for switching the color of the brackets), but I know of no (La)TeX package and for that. And it would need JavaScript in the PDF viewer. And it will probably be quite fragile.

1

Merge with Ghostscript. Use pdfpages on the Ghostscript output like this: \documentclass{article} \usepackage{pdfpages} \usepackage{hyperref} \begin{document} \pagenumbering{Roman} \setcounter{page}{4} \includepdf[pages={1-17}]{gs-output.pdf} % contains table of contents \pagenumbering{arabic} \includepdf[pages={18-}]{gs-output.pdf} % Rest of the book ...

0

Try the \pdfcomment package. There's an option to add a tool tip to the PDF using \pdftooltip{item}{tooltip}, where the item can be a float (e.g. \pdftooltip{\includegraphics[]{}}{description of my figure}). The overall process that I've settled on to produce 508-compliant documents is to Produce a high-quality PDF from LaTeX which includes all of the ...

5

Package hyperref adds bookmarks (outlines). If only some pages are extracted, then there might be pages that have bookmark entries (e.g. by \section{bar}). However ghostscript does not reorganize the bookmark tree (non-trivial in general). It only makes a poor job of copying the tree, removing some invalid entries. Such page subset documents are not a ...

2

You might want to make sure (i.e. check the documentation) that pdfrender is supposed to actually affect non-text elements, too: does it promise to be capable of modifying line width for all kinds of paths? I'm not so sure. It may well be that the behavoir you're getting is within the limits of what's to be expected from that package -- or from the ›raw‹ ...

6

You can use the pgfpages package (not pdfpages) (it's part of TikZ/pgf and documented in section 58 of the TikZ manual) to do this: \documentclass{scrartcl} \usepackage{kantlipsum} \usepackage{pgfpages} \pgfpagesuselayout{4 on 1}[a4paper, landscape] \begin{document} \kant[1-13] \end{document}

9

You can make the text a bit more heavy by using Heiko's great pdfrender package. Just play with the LineWidth parameter. \documentclass[paper=a4]{scrartcl} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage{pdfrender,xcolor} \begin{document} \pdfrender{StrokeColor=black,TextRenderingMode=2,LineWidth=0.2pt} A wonderful serenity has taken ...

5

It appears that this issue is independent of the compiler, and it's not possible to "fine-tune" the .pdf output without changing the font package used. I answered pretty much the same question a while ago. It is possible to produce what I'd call ›faux ink gain‹, using the method I described in that answer, but it's going to produce unpredictable results ...

Top 50 recent answers are included