<div>Just a general question:<br></div><div><br></div><div>On the test pdf we only see author names.</div><div>Do you think that affiliation must be written ?</div><div><br></div><div>Regards,<br></div><div>Pierre</div><div> <br></div><div class="gmail_quote">2012/1/17 rafael grompone von gioi <span dir="ltr"><<a href="mailto:grompone@gmail.com">grompone@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi,<br> <br> I prepared a new version of the IPOL LaTeX class, incorporating<br> most of Nicolas' suggestions. The class files and examples are here:<br> <br> <a href="http://dev.ipol.im/~jirafa/ipol-latex-format/" target="_blank">http://dev.ipol.im/~jirafa/ipol-latex-format/</a><br> <br> The main changes are the addition of the IPOL logo and<br> reference at the beginning, and the links color. There are<br> also three variants to cope with the problem of the number<br> of characters per line:<br> <div class="im"><br> > In "The Elements of Typographic Style", Bringhurst writes: "Anything<br> > from 45 to 75 characters is widely-regarded as a satisfactory length<br> > of line for a single-column page set in a serifed text face in a text<br> > size. The 66-character line (counting both letters and spaces) is<br> > widely regarded as ideal." I think 66 characters per line may be too<br> > short and the current 100cpl too long, maybe 80 cpl is possible with<br> > more margins?<br> <br> </div>I am well aware of this rule, but the compromise in our case is not easy.<br> I think we should rule out the use of two columns, a classic solution,<br> because it is not comfortable on the web. Then, we can change<br> the margins and the paper size. The three variants proposed are:<br> <br> 1) The same margins as before in A4 paper. The full page is used and<br> this reduce the space wasted on the web page. The problem is that<br> there are about 100 cpl and it is not nice to read. The line length rule<br> is for continuous long reading, and IPOL articles are not to be<br> read as a novel. The reading quality of the LaTeX articles should be<br> far better than the current HTML version. So, the first option is to pay in<br> long lines this compromise.<br> <br> 2) The second option is to reduce the margins so as to get about 80 cpl.<br> The result is intermediate. The margins are better for a printed article,<br> but worse for a web page, and the lines (even if still long) are far better<br> than in option 1.<br> <br> 3) The last option is to use A5 paper. The length of the lines is optimal,<br> about 67 cpl. The page size may be even better than A4 for web reading.<br> The compromise is not so clear for printing. Printing two pages per paper<br> sheet produce a reasonable printed size without wasting paper. I think the<br> result is even better than the previous two options. However, it is an<br> uncommon paper size and it can confuse some people.<br> <br> What do you think?<br> <br> Please note that the commands defined by the LaTeX class changed<br> from the previous version. There is no longer a command to produce<br> the title; it is always generated after the IPOL logo and reference.<br> The user must only define the title and authors with a command.<br> <div class="im"><br> > * What should we write in the "ipolAbstract" ? Why do we need an<br> > "ipolCode" and "ipolSupp"? Can't this information be written in the<br> > article body, like it is currently in the wiki/HTML articles?<br> <br> </div>This was a suggestion by Jean-Michel Morel to give to the code<br> and supplementary material a especial status, suggesting they<br> are not optional but obligatory parts, particular to IPOL.<br> <div class="im"><br> > I am quite reluctant to publish PDFs provided by the authors, because<br> > it feels like publishing the compiled programs without having the<br> > source. We would be stuck to a format with very limited options for<br> > future evolution.<br> <br> </div>I think it is now clear that the initial submission should be on any<br> PDF format, as long as the editors and reviewers can read it.<br> <br> I agree too that the final PDF should be generated in<br> IPOL server, so we have the sources, we can generate<br> different quality/file size versions, and eventually we could<br> generate new versions on the future. But there are two<br> important points to discuss:<br> <br> 1) The procedure.<br> <br> I am quite sure that in many cases, going from the initial<br> PDF version to the one that can be compiled on IPOL servers<br> will not be straight forward. People sometimes uses particular<br> packages, and adapting the figures and tables to IPOL format<br> can take considerable time. I think this work must be done by<br> the authors. First using our LaTeX package and guidelines in their<br> own machines and then in our server. So we should provide an easy<br> way in which the authors can upload their zip/tgz to test as many<br> times as they need. Then, once they think the generated file is OK,<br> the editor should only check that the format is satisfied. But this<br> only implies checking the resulting PDF. Otherwise, it would be<br> too much work.<br> <br> 2) Future compilation of LaTeX files<br> <br> I agree that it would be nice to have well behaved LaTeX<br> sources to be able to be re-compiled to new formats<br> in the future. Unfortunately, I don't think this is possible.<br> We know already how much work it is needed to produce<br> C programs that satisfy a standard and that probably<br> we will be able to compile in the future. The problem is<br> worst for LaTeX: there is no real standard and we need<br> to use many packages developed by many different<br> people and different quality level. Moreover, we can ask<br> the authors to do the standardization effort on the code<br> because it is the essence of IPOL, but there is no point<br> in asking the same effort for the LaTeX files. The PDF<br> version of the articles are the standard version we will<br> surely have in the future.<br> <br> I don't think we can rely on the possibility of re-compiling<br> the articles in the future. As in any other journal, as format<br> evolve, old and new articles will co-exist having different formats.<br> <br> Comments and suggestions are very appreciated.<br> <br> Best regards,<br> rafael<br> _______________________________________________<br> discuss mailing list<br> <a href="mailto:discuss@list.ipol.im">discuss@list.ipol.im</a><br> <a href="http://tools.ipol.im/mailman/listinfo/discuss" target="_blank">http://tools.ipol.im/mailman/listinfo/discuss</a><br> </blockquote></div><br><br clear="all"><br>-- <br><div><font>Regards/Cordialement,</font></div><div><font>Pierre M</font></div><br>