-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC: Fix typos in PDF document properties. #73
DOC: Fix typos in PDF document properties. #73
Conversation
BTW, does anyone happen to know why the PDF properties are not correctly set for book 2? Just have a look at one of the recent CDash builds, e.g. |
Thanks, @jhlegarreta . I am not familiar with the PDF properies issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I currently use Chrome to view PDFs (no dedicated PDF viewer installed), so I can't examine the properties. Which viewer are you using to examine the properties?
I use Adobe Acrobat Reader DC, but any other (?) allowing you to view the file should be fine. I ignore whether Chrome allows you explore the file properties. Once downloaded, in Acrobat Reader DC at least, you open the file, then click the |
Adobe's reader is authoritative, if this patch fixes the appearance in it it should be merged. |
3e7cfe4
to
0cc3713
Compare
I checked the generated PDFs in CDash and unfortunately the properties do not look better:
So
According to this post, this should solve it>
But may be it's due the encoding with which the file itself is being saved in the system (?).
BTW, it looks like you can inspect the properties of a PDF file from the command line via
Submitted a new patch set 0cc3713 using the |
0cc3713
to
76354a1
Compare
Same result as before; trying adding
in 76354a1. |
Below is the header from my thesis. My name contains accents and you can check whether they appear correctly in the generated document 😄 \documentclass[a4paper,11pt,final]{book}
\usepackage[american,ngerman]{babel}
%\usepackage[hyphens]{url}
%\makeatletter
%\g@addto@macro{\UrlBreaks}{\UrlOrds}
%\makeatother
\usepackage[T1]{fontenc}
\usepackage{textcomp}
\usepackage[sc]{mathpazo}
\linespread{1.05} % Palatino needs more leading (space between lines)
\usepackage{courier}
\usepackage{varioref}
%\vrefwarning
\usepackage{graphicx}
\usepackage[svgnames]{xcolor}
%\usepackage{fixltx2e} %fixltx2e is not required with releases after 2015
\usepackage{booktabs}
\usepackage{multirow}
\usepackage{dcolumn}
\newcolumntype{d}[1]{D{.}{.}{#1} }
\usepackage{fancyhdr}
\usepackage{listings}
\usepackage{amsmath}
\usepackage{rotating}
\usepackage{thesis}
\usepackage{cite}
\usepackage{subfig}
\usepackage[utf8]{inputenc}
\PassOptionsToPackage{hyphens}{url}\usepackage[unicode=true,pagebackref=true]{hyperref}
%\usepackage[pdfborder={0 0 0}]{hyperref}
\hypersetup{
pdftitle={An Efficient Inflation Method for Segmentation of Medical 3D Images},
pdfauthor={Dženan Zukić},
pdfpagelayout={TwoColumnRight},
}
% \usepackage{cleveref}
\usepackage[all]{hypcap}
\usepackage{hyphenat}
\usepackage{microtype}
\usepackage{textcomp}
\usepackage[labelfont=bf,indention=5mm,parskip=1mm]{caption}
\usepackage{parskip}
\setlength{\parindent}{5mm}
\renewcommand{\topfraction}{.85}
\renewcommand{\bottomfraction}{.7}
\renewcommand{\textfraction}{.15}
\renewcommand{\floatpagefraction}{.66}
\renewcommand{\dbltopfraction}{.66}
\renewcommand{\dblfloatpagefraction}{.66}
\setcounter{topnumber}{9}
\setcounter{bottomnumber}{9}
\setcounter{totalnumber}{20}
\setcounter{dbltopnumber}{9}
%\setcounter{secnumdepth}{3}
%\setcounter{tocdepth}{3}
\usepackage[section]{placeins}
\usepackage[all]{nowidow}
\pdfsuppresswarningpagegroup=1 %introduced with pdflatex 1.40.15
\begin{document} |
76354a1
to
8c5883f
Compare
Thanks for the input @dzenanz. Unfortunately, GitHub does not display the results for 76354a1; and I already committed 8c5883f. However, in a local test I made, the addition
did not do the trick. However, I think I found a workaround 😄. This post suggested using the And voilà, it worked in a small document I made with the ITK SWG properties. Cool !! I also tested that Let's see what CDash say to 8c5883f. Now, we may need more time or another topic for the book 2 properties mystery. |
Fix the missing escape character to write accents in the PDF document properties.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work, Jon!
@thewtex thanks for the review ! @dzenanz thanks for all the comments and also helping find the solution ! I've checked that the PDF properties are fixed for Book 1; the properties of Book 2 remain unchanged; I'll open an issue, have a look at it and hopefully propose a fix in another topic to push things forward. Merging. |
Fix the missing escape character to write accents in the PDF document
properties.