Giter VIP home page Giter VIP logo

lni-proceedings's People

Contributors

dependabot[bot] avatar heseba avatar koppor avatar michael-becker avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

lni-proceedings's Issues

Add script for processing publisher's PDF

The links in the PDF by the publisher are broken. There needs to be a script taking the publishers PDF and replacing the content by the proceedings PDF (and keeping the cover pages).

(If I understood @ibogicevic correctly)

Duplicate destination, newpax package problem

Hi,
assuming:

  • using the docker image danteev/texlive
  • one builds the proceedings following [1]
  • papers/ contains several subfolders, e.g. A1-1 and A1-2

When executing:

  • lualatex -synctex=1 proceedings.tex

in the project root, there are plenty of warnings of the form:

  • warning (pdf backend): ignoring duplicate destination with the name '[email protected]@13@'

This leads to the effect, that the jumpmarks of the original included pdfs (except the first included paper) are not resolved properly and point somehwere in the region of the first paper.

I see only one paper.newpax being generated in the project root (no .newpax files appear in the papers/A1-... directories) and thus creating name clashes. I assume it is due to the newpax syntax on proceedings.template.tex:
\directlua{newpax.writenewpax("papers/#3/paper")}
\saveimageresource{papers/#3/paper.pdf}

I fixed it temporarily for my project by altering it to
\directlua{newpax.writenewpax("papers/#3/#3paper")}
\saveimageresource{papers/#3/#3paper.pdf}

, subsequently also adapting the \addpaper commands and renaming the files to, e.g. A1-1/A1-1paper.pdf

This creates one distinct .newpax file for every included paper (still in the root dir) but now all jumpmarks for references, sections, etc. point to the correct location.

Is there any more elegant way of working around this issue?

[1] https://gi-ev.github.io/LNI-proceedings/

Whole "Startseiten" should be LaTeXed

Currently, `LNI-Startseiten.docx" needs to be adapted. Not all persons have Microsoft Word. Thus, we should offer a pure-LaTeX alternative.

This is a refinement of #18.

Nicer BibTeX keys

The generated .bib file currently contains the paper IDs as keys.
It would be nice, if the BibTeX keys are more human-readable.

grafik

This is a good use case of JabRef/jabref#110.

Support for shrinkpdf under Windows

Shrinking the final proceedings.pdf seems not to be supported under Windows.

  1. Maybe there should be an explizit hin to run the script through the Git bash?
  2. mgs must be called instead of gs (using MikTeX)
  3. The PDFSETTINGS and AutoRotatePages options require a double slash instead of a single slash
  4. The resulting PDF is optimized for printing, so all hyperlinks are removed. Shouldn't it be called using the dPrinted=false option to preserve the links?

For me the following invocation succeeded:

shrink ()
{
mgs \
-q -dNOPAUSE -dBATCH -dSAFER \
-sDEVICE=pdfwrite \
-dCompatibilityLevel=1.4 \
-dPDFSETTINGS=//printer \
-dPrinted=false \
-dEmbedAllFonts=true \
-dSubsetFonts=true \
-dCompressFonts=true \
-dFastWebView=true \
-dAutoRotatePages=//None \
-dDetectDuplicateImages=true \
-sOutputFile="$2" \
"$1"
}

Convert LNIs cover to full LaTeX code

Currently, GI e.V. offers a PowerPoint file for the book cover at https://gi.de/fileadmin/GI/Hauptseite/Service/Publikationen/LNI/LNI-Cover-Vorlage.ppt.

grafik

When using LaTeX, one might want to do everything using LaTeX and the package bookcover might come in handy. Thus, it should be planned to offer the cover by using bookcover. Example code for a book cover: https://github.com/latextemplates/uni-stuttgart-dissertation-template/blob/template/cover-print/cover.tex

Replacement of textunderscore in bibliography file does not take effect

make-proceedings replaces \textunderscore inside the proceedings.bib file. This doesn't seem to take effect, at least not in make-proceedings.bat under Windows:

sed -i "s/\\\\textunderscore //g" proceedings.bib

First, the above command seems to remove \textunderscore instead of replacing it with the _ character.
Second, why are there four backslashes in total? In my case the replacement worked only with two backslashes (one additional backslah to escape the given backslash of \textunderscore).

Port `metaExtract.py` to Python 3

When modernizing this, I also updated to Python3. This was not that easy.

Seems that I broke metaExtract.py at my naive update at #13.

@heseba May I ask whether you have Python3 skills and could properly update metaExtract.py to Python3? (Or should I try to get python2 running ^^)

Hyperlinks on first page of each paper take an offset

Update Question asked at tex.stackexchange: https://tex.stackexchange.com/q/420090/9075\
Update 2: Question deleted (because of 0) votes. I learned that I should use trim which should also solve the issues

We are using pax to keep hyperlinks in the final proceedings. They are working correctly with the exception of the first page of each paper. This is an issue of the pax package.

It happens, because we use an x offset in the viewport.

Minimal example

A viewport with 1cm offset is used.

Minimal example

Reproduce it:

pax-demo.tex

\documentclass{scrartcl}
\usepackage{graphicx}
\usepackage{pax}
\makeatletter
\def\PAX@viewport#1 #2 #3 #4\\{%
  \PAX@defaultbp\PAX@vllx{#1}%
  \PAX@defaultbp\PAX@vlly{#2}%
  \PAX@defaultbp\PAX@vurx{#3}%
  \PAX@defaultbp\PAX@vury{#4}%
  \edef\PAX@page@llx{\the\dimexpr\PAX@page@llx+\PAX@vllx\relax}%
  \edef\PAX@page@lly{\the\dimexpr\PAX@page@lly+\PAX@vlly\relax}%
  \edef\PAX@page@urx{\the\dimexpr\PAX@page@llx+\PAX@vurx\relax}% FIXED
  \edef\PAX@page@ury{\the\dimexpr\PAX@page@lly+\PAX@vury\relax}%
}
\makeatother
\begin{document}
\includegraphics[page=1, viewport=0 1cm 21cm 23.628cm]{pax-include.pdf}
\end{document}

pax-include.tex

\documentclass{scrartcl}
\usepackage{hyperref}
\begin{document}
\section{Section}
\label{sec}
This is Section~\ref{sec}.
\end{document}

demo.bat

pdflatex pax-include
pdflatex pax-include
perl C:\MiKTeX\scripts\pax\pdfannotextractor.pl pax-include
pdflatex pax-demo

Extraction of authors and title from papers

When generating the proceedings.tex, the authors' names are extracted from the square brackets [...] inside each paper.tex:

Check for all paper.tex that all authors are the format \author[Firstname Lastname \and ...]{...}

This is somewhat unfortunate because authors often use these square brackets for abbreviations, e.g., [Lastname et al.]
However, if proceedings.tex uses these abbreviations, they will appear in the table of contents and proceedings.bib, where one would usually expect to see all authors.

Would it be possibly to extract the authors' names from the curly braces inside each paper.tex? The abbreviated forms could still be copied into proceedings.tex as the optional argument of \addpaper, so that they will be shown in the header of the respective paper.

(Obviously, the same applies to the paper titles.)

Order of working steps in documentation

There seems to be an error in the documentation, which leads to a wrong order of working steps:

Step 9 requires users to adjust the pages in proceedings.tex:

Adapt pages=x-y (and possibly \pdfbookmark) at \includepdf[pagecommand={\thispagestyle{empty}},pages=5-5]{LNI-Startseiten.pdf} and subsequent \includepdf statements to match the page numbers of your foreword and sponsoring.

Later in step 11, a new proceedings.tex is generated:

During fixup phase, run /c/Python27/python ../addAuthTi.py ../proceedings.template ../proceedings.tex */paper.tex

Thereby, the previous adaptations from step 9 are overridden and need to be repeated. Not a big deal, but shouldn't the pages be adapted after proceedings.tex has been generated?

Unique paper IDs from the beginning to the end

Each paper has a unique paper ID when an author submits a paper (e.g., paper ID of conftool).
This ID should be used for storing papers.
It would be good if that ID is used at DOI processing.

Currently, the DOIs are generated sequentially.
That has the drawback if on-site proceedings and post-conference proceedings are generated and authors do not show and papers have to be removed for the final proceedings.

Steps:

  • Explain in README.md that concrete DOIs are generated sequentially
  • Offer possibility for using the paper IDs from begin to end

Implementation hints

  • Currently, the tool requires to sort-in the papers in directories wollowing patterns nm-o, where n is A, B, ..., m is 1, 2, 3, o is 1, 2, 3. This is very confusing when paper updates come in. Then, the paper number of the submission system has to be mapped to the tool's ID.
  • grafik

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.