gi-ev / lni-proceedings Goto Github PK
View Code? Open in Web Editor NEWSupport for generating LNI proceedings
Home Page: https://gi-ev.github.io/LNI-proceedings/
License: Creative Commons Zero v1.0 Universal
Support for generating LNI proceedings
Home Page: https://gi-ev.github.io/LNI-proceedings/
License: Creative Commons Zero v1.0 Universal
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)
E.g., if texindy is not found
Hi,
assuming:
When executing:
in the project root, there are plenty of warnings of the form:
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?
The README.md has information on different levels: Installation, usage, ...
We should switch to https://github.com/just-the-docs/just-the-docs and re-order the contents.
Example _config.yml
: https://github.com/macros4outlook/quotefixmacro/blob/main/docs/_config.yml
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.
The generated .bib file currently contains the paper IDs as keys.
It would be nice, if the BibTeX keys are more human-readable.
This is a good use case of JabRef/jabref#110.
Shrinking the final proceedings.pdf seems not to be supported under Windows.
mgs
must be called instead of gs
(using MikTeX)PDFSETTINGS
and AutoRotatePages
options require a double slash instead of a single slashdPrinted=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"
}
Using exitfool? Maybe also with lualatex/pdflatex itself (https://github.com/latex3/pdfresources?)
Example:
LNI requires to generate a Generate gi-dl-datacite-dublincore-metadata.xlsx.
Generating xls
is hard, but csv
is more easy.
Experiments show that is is hard to generate this data directly using latex's capabilities. Using the generated bib
file and JabRef, it seems to be more easy. However, JabRef/jabref#2762 needs to be fixed.
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.
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
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).
Currently, the .csv and .bib do not contain the abstract and keywords. An abstract and keywords is good to be communicated to search engines or meta data.
This is a pre-condition for #23.
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 usetrim
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.
A viewport with 1cm offset is used.
Reproduce it:
\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}
\documentclass{scrartcl}
\usepackage{hyperref}
\begin{document}
\section{Section}
\label{sec}
This is Section~\ref{sec}.
\end{document}
pdflatex pax-include
pdflatex pax-include
perl C:\MiKTeX\scripts\pax\pdfannotextractor.pl pax-include
pdflatex pax-demo
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.)
Trade-off between ready-for-texing and WTFs at comitting vs. clean repository.
Maybe, we can have an example repository and a clean repository?
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?
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:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.