<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scrapbook (Posts about writing)</title><link>https://scrapbook.netlify.app/</link><description></description><atom:link href="https://scrapbook.netlify.app/categories/writing.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 &lt;a href="mailto:non@existent.com"&gt;author&lt;/a&gt; </copyright><lastBuildDate>Fri, 16 Oct 2026 16:23:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Preparing Manuscripts</title><link>https://scrapbook.netlify.app/posts/preparing-manuscripts.html</link><dc:creator>author</dc:creator><description>&lt;nav id="TOC" role="doc-toc"&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#getting_started" id="toc-getting_started"&gt;Getting
Started&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#checklist" id="toc-checklist"&gt;Checklist&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#ms_word" id="toc-ms_word"&gt;MS Word&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#texlatex" id="toc-texlatex"&gt;TeX/LaTeX&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#special_symbols" id="toc-special_symbols"&gt;Special
symbols&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#figures" id="toc-figures"&gt;Figures&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#software" id="toc-software"&gt;Software&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#bibtex" id="toc-bibtex"&gt;BibTeX&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#correct_format" id="toc-correct_format"&gt;Correct
format&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#writing" id="toc-writing"&gt;Writing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/nav&gt;
&lt;h2 id="getting_started"&gt;Getting Started&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Any writing or presentation should reflect our own thought process
on why we initiate the project, how we design the research plan, how we
interpret the results, and how we troubleshoot where needed. So they
should probably start by describing what problems we are trying to
understand; What people already knew / what the state of the art is;
What calculations we did and how you did them; What you found; What the
findings tell you.&lt;/li&gt;
&lt;li&gt;Learn from others: &lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#Writing" title="wikilink"&gt;writing&lt;/a&gt;
and &lt;a href="https://scrapbook.netlify.app/posts/preparing-manuscripts.html#Presentations" title="wikilink"&gt;presentations&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;See &lt;a href="https://serialmentor.com/dataviz/"&gt;Fundamentals of Data
Visualization&lt;/a&gt; for a nice introduction to data visualization and
techniques for visualizing different types of information.&lt;/li&gt;
&lt;/ol&gt;
&lt;h3 id="checklist"&gt;Checklist&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Correct use of &lt;a href="https://www.merriam-webster.com/words-at-play/em-dash-en-dash-how-to-use"&gt;hyphens,
em dashes, and en dashes&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;When formatting equations and symbols, only italicize variables (but
not parentheses/square brackets, operators, or labels) italic; e.g., "E
/ k_B [K]" should have "E" and "k" italic, but not the division sign,
label "B", or the square brackets.&lt;/li&gt;
&lt;li&gt;For journals with a double-column layout, display items such as
figures and tables should target either full width (~6.5 -- 7 in) or
column width (~3.25 -- 3.5 in). This will signal to copy editors that we
prefer them to occupy a single column or across two columns.&lt;/li&gt;
&lt;li&gt;To manage the placement of display items, place them and their
captions into a text box with Shape Format -&amp;gt; Shape Outline and Wrap
Text set to "None" and "Square", respectively. Preferably, the text box
is then positioned to the top or the bottom of a page by using the Shape
Format -&amp;gt; Align option. Sometimes, Word will not break a continuous
paragraph to use up the whitespace in the previous page. To fix this,
move the text box below the paragraph, which will allow the paragraph to
flow to the previous page, and then re-align the text box to the top of
the page.&lt;/li&gt;
&lt;li&gt;Journal names are properly abbreviated. Authoritative sources for
journal name abbreviations include &lt;a href="http://www.issn.org/2-22661-LTWA-online.php"&gt;ISSN List of Title
Word Abbreviations&lt;/a&gt;, &lt;a href="https://images.webofknowledge.com/images/help/WOS/A_abrvjt.html"&gt;Web
of Science Journal Title Abbreviations&lt;/a&gt;, and &lt;a href="http://cassi.cas.org/search.jsp"&gt;Abbreviations for Elsevier
journals&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Double check the references. References imported to Zotero by DOIs
often have extra whitespace in front of subscripts (e.g., "CO
&lt;sub&gt;2&lt;/sub&gt;").&lt;/li&gt;
&lt;li&gt;Follow journal guidelines and if available, use journal-specific
Word/Zotero/LaTeX/BibTeX templates. For initial submission, when citing
an article with 10 or more authors, list the first 10 authors' names and
then use "et al." to represent additional authors (ACS Style
Guide).&lt;/li&gt;
&lt;li&gt;When you address a comment in Word, Overleaf, etc., please take care
not to remove it. If you delete and rewrite the block of text on which a
comment is made, then the comment itself will also be deleted, making it
very hard to follow up on them. One way we can avoid this is by first
writing new text inside the commented block and then delete the old
text. Another way for Word documents is to use strike-through text for
the word or sentence the comment is associated with and write/edit
around the strike-through text.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="ms_word"&gt;MS Word&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Do NOT make stylistic text changes on individual blobs of text,
including title and headings. For example, do not use these &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=1pThINj3kHFvTGuGTu5_ieI3dukPKkz0s"&gt;ribbon
options&lt;/a&gt; to make heading text bold and centered. This is a bad
practice because you have to 1) make the same style changes for all
headings; 2) remember to do the same for any new sections that are added
later; and 3) edit every heading all over again if you ever need to
submit to another journal with different requirements on
formatting.&lt;/li&gt;
&lt;li&gt;USE appropriate &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=1LQrYC89F9MAPFZ0Z1zNqe_1bbko4mjmc"&gt;Styles&lt;/a&gt;
to mark semantics of the text (e.g., title, Heading 2, Heading 3). If
say, Heading 3 does not have the desired format, click &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=1LQrYC89F9MAPFZ0Z1zNqe_1bbko4mjmc"&gt;Modify&lt;/a&gt;
to edit in the dialog that pops up. You can make more changes by
clicking the &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=1cDWbRFZibXk8NgrVxn_oCd9hWR7bTpgR"&gt;Format
button&lt;/a&gt;. A nice side effect of this is that you can turn on &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=155_Y5P3JQRJ8mK0cfMcWDWxQoVaqMw6O"&gt;Navigation
pane&lt;/a&gt; and see a clear outline of the document.&lt;/li&gt;
&lt;li&gt;NEVER hard code Figure X / Table Y in text. Use &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=17vtJR0BTJdsvHs_iALgJ87LgVKmcRpxl"&gt;Cross-reference&lt;/a&gt;.
To customize cross-reference labels (e.g., "Fig." or "FIGURE" instead of
"Figure"), &lt;a href="https://stackoverflow.com/a/34371621/661775"&gt;create
a new label&lt;/a&gt;. Do NOT make changes to the labels manually, which will
not work with Cross-reference properly.&lt;/li&gt;
&lt;li&gt;See &lt;a href="http://wordfaqs.ssbarnhill.com/CombineXrefs.htm"&gt;here&lt;/a&gt; for how
to combine multiple references. That is, do not write "Figure 1, Figure
2, Figure 3"; instead write "Figures 1 -- 3" or "Figures 1, 2, and 4"
(if not continuous).&lt;/li&gt;
&lt;li&gt;To add automatic equation numbering, use either &lt;a href="https://superuser.com/a/1121557/318218"&gt;#() syntax&lt;/a&gt; (available
since Word 2016) or &lt;a href="https://superuser.com/a/594560/318218"&gt;3-column no-border tables
with captions&lt;/a&gt;. To cross reference equations, first select the
equation number and &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=1Ii91qLxygxWEZMZqRqKiR_dtObeigVP3"&gt;insert
a bookmark&lt;/a&gt;. You can then use &lt;a href="https://drive.google.com/uc?export=view&amp;amp;id=15pDkX5RW0Vn-BWsrbcchpjfCL-bHI35U"&gt;Cross-reference&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;To cross reference section numbers (e.g., Section 2), in the
Cross-reference dialog, select Heading as Reference type and Heading
number as Insert reference to. For this to work though, the numbers in
section heading (e.g., "2. Methods") must be added using the numbered
list functionality, rather than by hand.&lt;/li&gt;
&lt;li&gt;The above points are very useful when adding new figures as the
document will auto-update the figure/table numbering. To update
cross-reference labels (in the text itself, not the captions),
right-click the label and select "update field" for manual updating. &lt;a href="https://support.microsoft.com/en-us/office/update-fields-7339a049-cb0d-4d5a-8679-97c20c643d4e"&gt;See
here&lt;/a&gt; for updating all fields at once.&lt;/li&gt;
&lt;li&gt;NEVER use text boxes for figure labels. Text boxes often move out of
alignment with the figures they are supposed to annotate. Instead,
annotate the figure in PowerPoint. When you are done, select everything
for the figure, right click, and either 1) Save as Picture or 2) Copy,
right click in Word, and Paste as Picture.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="texlatex"&gt;TeX/LaTeX&lt;/h2&gt;
&lt;h3 id="special_symbols"&gt;Special symbols&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;Text mode Angstrom: \AA Math mode: Angstrom: \mathring{A}, \r{A}, \r{\rm A} degree symbol: ^{\circ}&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;For quick referencing, &lt;a href="http://kirelabs.org"&gt;Kire Labs&lt;/a&gt;
made a tool called &lt;a href="https://detexify.kirelabs.org/classify.html"&gt;Dexterify&lt;/a&gt; which
uses symbol recognition to identify which LaTeX commands will give the
user-drawn character. For example, you can draw a tilde symbol in the
drawing box, and Dexterify will output various options for tildes.&lt;/p&gt;
&lt;h3 id="figures"&gt;Figures&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;When embedding figures in latex, the float default is usually h for
"here." For publications this should be t for "top." For figures that
are too large, the default behavior is to put the figure at the end.
Putting an exclamation point will gurantee this:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;\begin{figure}[t!]&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;a href="http://robjhyndman.com/researchtips/latex-floats"&gt;Controlling
figure and table placement in LaTeX&lt;/a&gt; explains how to place float
objects to places they belong.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;For the Xmgrace files, use figures in .eps format. Make sure that
the figure has the correct size in Xmgrace by providing the correct
number of pixels. Font size in labels and legends should be commensurate
with text size in the journal.&lt;/li&gt;
&lt;li&gt;ACS journal column widths are 3.25 in. So make sure to never go
below that in width. It is not necessary to make the figures 3.25" in
size unless otherwise requested by the journal.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="software"&gt;Software&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;When preparing manuscripts, keep all LaTeX as simple as possible. Do
NOT use any packages and only use the documentclass provided by the
journal. Always follow the author guidelines from the journal as closely
as possible.&lt;/li&gt;
&lt;li&gt;Neither ACS, AIP, Elsevier, nor Nature use "pdflatex". Thus, we must
use regular "latex".&lt;/li&gt;
&lt;li&gt;Data management plans now require extensive Supporting Information.
Essentially all simulation data that appears somewhere in a figure, also
need to be as numerical data in a table in the supporting info. This is
quite labor intensive.&lt;/li&gt;
&lt;li&gt;Relative paths should be used&lt;/li&gt;
&lt;li&gt;Some publisher programs will have difficulty with lines of longer
than 255 characters.&lt;/li&gt;
&lt;li&gt;Make sure to name the PDF something appropriate. For example, the
ACS supporting info file name is named based on the main paper. So, for
example, don't submit full_article.pdf&lt;/li&gt;
&lt;li&gt;ACS journals have a mistake with mathematical symbols. The
statement&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;The result is about 5.2&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;would be translated to&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;The result is ~5.2&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This is the wrong symbol for about; you should use the approximate
equals yourself; the program will think it's a mathematical equation
instead and it will correctly translate.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Latex differentiates between opening and closing quotes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="bibtex"&gt;BibTeX&lt;/h2&gt;
&lt;h3 id="correct_format"&gt;Correct format&lt;/h3&gt;
&lt;p&gt;An example BibTeX entry that has multiple issues:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;@article{X22,
author = {Gupta, Prashant Kumar and Meuwly, Markus},
journal = {The journal of physical chemistry. B},
number = {35},
pages = {10951--9},
volume = {116},
year = {2012}
}&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Title: This is sometimes missing from the output of reference
manager software, but is needed for all proposals and for some journals
(e.g., ACS journals now want the titles for citations). Also be careful
that the Web of Science may use the wrong
&lt;strong&gt;capitalization&lt;/strong&gt;: only the first word and names should be
capitalized (sentence case). The BibTeX style file should change titles
to the journal format automatically (e.g., title case for ACS journals).
However, there is a problem with names. For example, the name of our
method has to be typed as "{M}onte {C}arlo" otherwise the first letter
of these names will be lowercase.&lt;/li&gt;
&lt;li&gt;Author: Edit so that only the initials are included. No journal
wants the full middle name of the authors. Also &lt;strong&gt;NEVER&lt;/strong&gt;
use "et al." in your .bib file. For the few journals that want fewer
names, we will modify the BibTeX style file or directly edit the .bbl
file.&lt;/li&gt;
&lt;li&gt;Journal: Edit to use the correct abbreviation. LaTex does not
automatically find the correct abbreviations for the journal title. When
using Zotero, double check "Journal Abbr" is set correctly.&lt;/li&gt;
&lt;li&gt;Number: Remove or make sure the BibTeX template removes them. There
is no single journal that requires the issue number in the list of
references.&lt;/li&gt;
&lt;li&gt;Pages: Page numbers need to be given in full. That is, "10951-9"
should read "10951-10959".&lt;/li&gt;
&lt;li&gt;Some journals do not allow a separate .bib file, in which case the
references need to be embedded in the main .tex file.&lt;/li&gt;
&lt;li&gt;When a problem is found for a reference, make sure to fix the
citation source in Zotero or BibTeX. Develop the habit of checking the
title and journal abbr fields whenever you import a new reference,
either by DOI lookups or by extracting PDF metadata.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="writing"&gt;Writing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/uc?export=download&amp;amp;id=1apJX7h0jVTHVM3DF8VkybmR-j8-PdhMv"&gt;LSAC
Manuscript Guidelines (Enrique Iglesia, 2008)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/uc?export=download&amp;amp;id=1VfMsw-54xe8LB9WCOhUS8z1eJkPylyjp"&gt;On
writting manuscripts (Michele Boudart)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://drive.google.com/uc?export=download&amp;amp;id=1kolJ_6lxqRMVLtJa8PzAmHK5adqt3P0_"&gt;Whitesides'
Group_Writing a Paper (2004)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a href="https://drive.google.com/uc?export=download&amp;amp;id=1ZV8VfHO52oECW3PHzYw9X-_n50uH6RP9"&gt;Skillful
writing of an awful research paper (Royce Murray, 2011)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://drive.google.com/uc?export=download&amp;amp;id=1VT7ackzStVP3s8Hyramx17m96nmlAweE"&gt;Paper
writing gone Hollywood (2017)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://scrapbook.netlify.app/posts/Siepmann's_comments_on_clarity_and_precision_of_language" title="wikilink"&gt;Siepmann's comments on clarity and precision of
language&lt;/a&gt;&lt;/p&gt;</description><category>advice-tips</category><category>research</category><category>writing</category><guid>https://scrapbook.netlify.app/posts/preparing-manuscripts.html</guid><pubDate>Tue, 06 Dec 2016 00:04:10 GMT</pubDate></item></channel></rss>