Hi guys,

for job-related reasons, I have to use Windows + cygwin, and the paper creation works like a charm, apart from the conversion from .tex to .pdf from Python. This is due to the difference in symbol for piping operations in Unix (|) and Windows (&). In my case, a tiny replacement of that symbol at line 109 of file publisher/build_paper.py would do the trick. But perhaps it would be great for the next year to add a programmatic platform check in the code :)

Cheers!

Davide

Equations in the PDF version of the Plyades'article (PR #49 ) are badly rendered.
I don't know on what side it should be corrected (rst side or PDF generation).

I have texlive-latex-recommended and texlive-latex-extra

$ port installed *texlive* | grep active
  texlive-basic @34245_0+doc (active)
  texlive-bibtex-extra @34207_0+doc (active)
  texlive-bin @2014_1+x11 (active)
  texlive-common @2014_0 (active)
  texlive-fonts-extra @34251_0+doc (active)
  texlive-fonts-recommended @34089_0+doc (active)
  texlive-latex @34192_0+doc (active)
  texlive-latex-extra @34239_0+doc (active)
  texlive-latex-recommended @34240_0+doc (active)
  texlive-pictures @34010_0+doc (active)

but still I get a LaTeX error that IEEEtran.cls is missing:
https://gist.github.com/cdeil/038c6d397b8bdc74a2b3

Would it be possible to bundle IEEEtran.cls in this repo?

Hi all,
Any update on when these proceedings will be on the Arxiv?

The instructions provided in the front-page README do not match those
written in the email that was sent to EuroSciPy contributors.

The README states:

Here are the steps to produce a paper:

• Fork the scipy_proceedings repository on GitHub.
• An example paper is provided in papers/00_vanderwalt. Create a new directory papers/firstname_surname, copy the example paper into it, and modify to your liking.
• Run ./make_paper.sh papers/firstname_surname to compile your paper to PDF (requires LaTeX, docutils, Python--see below). The output appears in output/firstname_surname/paper.pdf.

whereas the email says:

• Fork https://github.com/euroscipy/euroscipy_proceedings
• Clone the fork: git clone [email protected]:GITHUBLOGIN/euroscipy_proceedings
• Write your paper in papers/lastname.rst
• Commit and push it: git add papers/lastname.rst ; git commit -m "My paper" ; git push origin master

So in particular:

• which repo should be cloned: euroscipy_proceedings or scipy_proceedings? (I assume the former.)
• should the paper be papers/firstname_lastname/paper.rst or directly in papers/lastname.rst (the latter is not a good choice if a paper contains figures and external files)
• should the produced PDF be committed to the repo as well?

Thanks for any clarification!

In the PDF rendering:

• top of the articles refers to "EUROSCIPY 2013" and "6th" edition
• copyright text talks about 2014

Hey all.
I noticed that Arxiv layouts the paper slightly differently than my local sphix/buildsystem. Now I am somewhat disappointed, because I spent a significant time on engineering the paper such that it fits on 8 pages (which is already oversize, sorry for that!) But now Arxiv layouts it to 8.5 pages and then expands it to 10 with 1.5 blank pages.
Did someone else experience this kind of discrepancy? My local paper (Docutils 0.12, Sphinx 1.4):
https://dl.dropboxusercontent.com/u/50299996/Garbage%20Collection%20in%20JyNI.pdf
(Tex-file: https://dl.dropboxusercontent.com/u/50299996/paper.tex)
Compared to Arxiv-variant:
http://arxiv.org/pdf/1607.00825v1.pdf
The euroscipy_proceedings build-script does not leave room for layout configuration, does it?
Can I configure it such that it matches Arxiv-output?
Is it possible to fix this in Arxiv-repo?

Sorry for abusing the issue tracker but this question might be of general interest: Is it fixed already how to cite articles in this year's proceedings? I looked for last year's proceedings but couldn't find a proper reference.

Hi,

I have tried to use both list-table and csv-table without success. The rst2tex phase says nothing, the latex file looks ok, but the tex2pdf phase chokes with

Runaway argument?
{
! Paragraph ended before \text@command was complete.
<to be read again> 
                   \par 
l.199 symbol}
              & \textbf{%
!  ==> Fatal error occurred, no output PDF file produced!

Example table:

.. list-table:: Notation.
   :widths: 20 80
   :header-rows: 1

   * - symbol
     - meaning
   * - :math:`\Omega`
     - volume (sub)domain
   * - :math:`\Gamma`
     - surface (sub)domain

The only difference I spot between the latex source for table versus list- or csv-table is that the table output does not use the page continuation macros:

\hline
\endfirsthead
\hline
\textbf{%

symbol} & \textbf{%

meaning} \\
\hline
\endhead
\multicolumn{2}{c}{\hfill ... continued on next page} \\
\endfoot
\endlastfoot

Can this be fixed or should I use the pain(t)ed tables? Thanks :)

PS:

pygments.__version__: '1.4'
docutils.core.__version__: '0.8.1'

I've followed the README instructions but ran into an error when executing ./make_paper.sh papers/pierre_haessig

Here is the command log:

Building: pierre_haessig
PDFLaTeX error output:
================================================================================
This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012/Debian)
 restricted \write18 enabled.
entering extended mode
! I can't find file `paper.tex'.
<*> paper.tex

(Press Enter to retry, or Control-D to exit)
Please type another input file name: 
! Emergency stop.
<*> paper.tex

!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on texput.log.

================================================================================
/bin/sh: 1: cd: can't cd to /home/pierre/Travail

================================================================================

So paper.tex is not found even though it exists in the output/pierre_haessig directory

The last line of the lof probably the most informative since the full path to the to the output directory is in fact /home/pierre/Travail eolien/[...]/output/pierre_haessig So it contains white spaces (and also some accents !) which are not handled properly (cf. the can't cd error in the log).

1. Such reference is badly layout with large spaces:

.. [Blosc] Francesc Alted, http://blosc.org, https://github.com/FrancescAlted/python-blosc

2. Maybe it would be nice to add a way to specify units and use a latex package for this purpose.

I am using :math:123\,456\,mm

3. should we tweak orphan line and so on?

Otherwise it produces a very well formated document.