file: Readme-editors.txt = Rob Rutten ASP-CS editor recipes last: Jul 23 2007 Victoria init: Mar 18 2007 site: http://www.astro.uu.nl/~rutten/rrtex/manuals/publishers/aspcs note: RR use en, type ESC 64 CNTRL-X f Introduction ------------ These are loose remarks and recipes for ASP-CS editors made after my co-editing the ASP-CS proceedings of the Coimbra Solar Physics Meeting in 2006. The parallel directory ../authors contains corresponding recipes for ASP-CS authors. I do not maintain these files unless I will become ASP-CS editor again. Instruction to authors ---------------------- See file "Readme-authors.txt" in the parallel directory for ASP-CS authors. You might use it, or parts of it, for your own authors. I emphasized in "Readme-authors.txt" that authors should carefully choose between no publication, brief summary (1-2 pages), or extensive writeup (6-22 pages). This worked well: the pages left free by the no-submission and summary-only contributions balanced the longer papers and reviews. The latter give the book its value and make the editorial efforts worthwhile. The end of "Readme-authors.txt" contains a brief list of LaTeX do's and don't's. Many of our authors sinned against these, for example using "...." instead of ``.....'' but also many of the others. French authors are generally the most sloppy ones. I could repair many of these with my script "changetexstring" in all manuscript files at once. However, in hindsight I should have been much stricter and should have immediately returned any manuscript that did not adhere to these simple recipes (but half of the manuscripts went to my co-editors who were sinners themselves; the initial manuscript check should better be done by a single, stern person). On file organization -------------------- ASP recommends to have a subdirectory per author but this requires that the full-book calling file knows where each figure is. My template now has \def\figpaths to provide the figure path, redefinable in the full-book calling file. However, I found it more practical to work exclusively with the manuscript latex files (including \begin{doucment} etc) in indiviual author subdirs in a subdir authordirs, and to do all editing in these. For the full-book production I used scripts "aspundefone" and "aspundefall" to copy these author files into a single "bigbook" directory while automatically commenting out \begin{document} etcetera. Thus, I never edited any author stuff in the latter but only in the individual author directories - correcting, latexxing, and inspecting each standalone. This is a much faster way of working than running the whole book over and over again, and also permits easy author splits between editors. In addition, working with standalone files means that at the book completion I could also open up, via weblink, the author dirs to the authors to transfer back their final-version files for their Astro-ph preprint submission (for which one needs the individual processed latex source, the figures, and the style file). On bibtex --------- I suggest requiring the use of BibeX even while the ASP hasn't produced a proper asp.bst style file yet. Otherwise your authors will supply handmade \bibitems with a great many mistakes giving you endless trouble. A very nasty habit of Natbib is that it switches from author-year to numeric in-text citation at any \bibitem inconsistency. This means that while manuscripts can latex properly standalone in producing author-year citations from incorrect \bibitems when processed by the author, the whole book flips to numeric citation when just one manuscript with bad \bibitems is inserted. Very nasty: the author won't notice any problem and cannot be held responsible for not noticing her \bibitem flaws. The quick fix is to take out the last line of the full-book.aux file as done in my script auxlatex (courtesy John Leibacher, NSO). But it is much better to make all authors use bibtex so that all \bibitems have the same format and reference style. Another nasty issue is that you may have to make all bibtex labels unique per author, as for all other labels defined by authors. Otherwise, different authors may use the same \cite labels for different \bibitems. Terry Mahoney's ASP author instruction sets a bad example by using silly labels such as {ma02} (in addition to showing very bad, non-standard, incomplete, inhomogeneous, verbose \bibitems as examples). By making authors use ADS bibdata in their .bbl generation, a given ADS biblabel can serve for multiple authors but only if no single ADS-generated \bibitem is modified by any author, whereas the ADS references to conferences, unfortunately, are generally bad and must be improved manually. (ADS informed me that they aim to do better, but depend on what they get from the various publishers). At the end of my editing I constructed a file "coimbra.bib" with bibtex entries for all papers in our proceedings and spread it to all participants in order to boost their citing of these proceedings papers (including their own) in their other publications. I made it by adding typeout statements to the full-book calling file, but it is better done from the .toc file. It would be good to automate this per script. My scripts ---------- Subdirectory scripts has direct copies of the scripts I used, not modified into more generic file names. auxlatex = latex the full book with natbib fix (from John Leibacher's script, also available here) makepdf = produce full-book.pdf from the full-book.dvi This one didn't work in my little laptop (memory too small) so I ran it instead in our institute Linux server aspundef = comment out \begin{document} etc, also all \def's aspundefone = use on a specified author subdir (dir authordirs) aspundefall = use on all author subdirs (dir authordirs) changetexstring = bag of ubiquitous latex corrections I did these one by one editing this file, then for each executed changetexstringdeep = execute on all tex files under authordirs I used these for example to homogenize spectral species names greptexdeep = list string occurrences in latex files for example (within dir authordirs) greptexdeep \\title > ../greplist-title.txt to compare actual titles to those in the full-book latex file My latex input files -------------------- My rjr-asp.sty and rjr-asp-bib.bst files sit under my parallel recipes for ASP-CS authors at http://www.astro.uu.nl/~rutten/rrtex/manuals/publishers/aspcs Subdir latex contains copies of the layex input files I used: "coimbraprocs.tex" = full-book assembly file (sat in my directory bigbook). One thing it doesn't do properly is using \hyperref for the full book (which I tried but discarded). Most other .tex files sat in a subdir frontmatter/ and concern frontmatter stuff. ASP has an awkward habit of mixing that between meeting-specific entries in the latex style file and separate \input files. I adapted their templates considerably to make them work better. File "coimbrabib.tex" served to test my production of "coimbra.bib". I added that to show its format.