PageSourceSearch

https://retorque.re/mit.html

html retorque.re collected 2026-10-02 05:09:49 UTC 12,085 bytes, 234 lines download raw bytes

1<!DOCTYPE html>
2<html>
3
4  <head>
5  <meta charset="utf-8">
6  <meta http-equiv="X-UA-Compatible" content="IE=edge">
7  <meta name="viewport" content="width=device-width, initial-scale=1">
8
9  <title>Zotero at MIT</title>
10  <meta name="description" content="Just random thoughts
11">
12
13  <link rel="stylesheet" href="/css/main.css">
14  <link rel="canonical" href="https://retorquere.github.io/mit.html">
15  <link rel="alternate" type="application/rss+xml" title="Retorquere on GitHub" href="https://retorquere.github.io/feed.xml" />
16
17	
17<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>
17
18	
18<script>
19  	(adsbygoogle = window.adsbygoogle || []).push({
20    	google_ad_client: "ca-pub-1051968571419627",
21    	enable_page_level_ads: true
22  	});
23	</script>
23
24</head>
25
26
27  <body>
28
29    <header class="site-header">
30
31  <div class="wrapper">
32
33    <a class="site-title" href="/">Retorquere on GitHub</a>
34
35    <nav class="site-nav">
36      <a href="#" class="menu-icon">
37        <svg viewBox="0 0 18 15">
38          <path fill="#424242" d="M18,1.484c0,0.82-0.665,1.484-1.484,1.484H1.484C0.665,2.969,0,2.304,0,1.484l0,0C0,0.665,0.665,0,1.484,0 h15.031C17.335,0,18,0.665,18,1.484L18,1.484z"/>
39          <path fill="#424242" d="M18,7.516C18,8.335,17.335,9,16.516,9H1.484C0.665,9,0,8.335,0,7.516l0,0c0-0.82,0.665-1.484,1.484-1.484 h15.031C17.335,6.031,18,6.696,18,7.516L18,7.516z"/>
40          <path fill="#424242" d="M18,13.516C18,14.335,17.335,15,16.516,15H1.484C0.665,15,0,14.335,0,13.516l0,0 c0-0.82,0.665-1.484,1.484-1.484h15.031C17.335,12.031,18,12.696,18,13.516L18,13.516z"/>
41        </svg>
42      </a>
43
44      <div class="trigger">
45        
46          
47        
48          
49          <a class="page-link" href="/">Hello There</a>
50          
51        
52          
53        
54          
55          <a class="page-link" href="/mit.html">Zotero at MIT</a>
56          
57        
58          
59          <a class="page-link" href="/react.html">React.js</a>
60          
61        
62          
63        
64        <a class="page-link" href="/zotero-better-bibtex/">Zotero Better BibTeX</a>
65      </div>
66    </nav>
67
68  </div>
69
70</header>
71
72
73    <div class="page-content">
74      <div class="wrapper">
75        <h1 id="what-mit-gets-wrong-about-using-zotero-with-latex-and-bibtex">What MIT gets wrong about Using Zotero with LaTeX and BibTeX</h1>
76
77<p>You’re probably here because you visited the mit.edu page on <a href="http://libguides.mit.edu/c.php?g=176000&amp;p=1159208">Zotero at MIT: Zotero with LaTeX and
78BibTeX</a>, and you want to learn about the <a href="https://github.com/retorquere/zotero-better-bibtex/wiki">Better
79BibTeX</a> utility that page linked to. If you want to find out what
80Better BibTeX can do for you, you can visit the
81<a href="https://github.com/retorquere/zotero-better-bibtex/wiki">documentation</a>, but if you just want to download Better BibTeX
82for Zotero, you can find the latest release <a href="https://github.com/retorquere/zotero-better-bibtex/releases/latest">here</a>.</p>
83
84<p>The MIT page contains some omissions however that could unnecessarily scare you away from using Zotero for your Bib(La)TeX
85needs. The MIT librarians seem to be actively hostile to this being pointed out, which is why I’ve put up this page. On
86this page, I assume you’re open to using Better BibTeX to address these problems – if not, you probably would not be
87here, right? Onwards then. The headers below match the relevant section of the <a href="http://libguides.mit.edu/c.php?g=176000&amp;p=1159208">MIT
88page</a> to explain what I think could be reformulated.</p>
89
90<h2 id="how-do-i-export-from-zotero-to-bibtex">How do I export from Zotero to BibTeX?</h2>
91
92<p>The points below will assume you will use the ‘Better BibTeX’ format rather than the ‘BibTeX’ format as the MIT page
93instructs.</p>
94
95<h2 id="how-can-i-fix-references-that-had-problems-formatting-special-characters">How can I fix references that had problems formatting special characters?</h2>
96
97<p>Not even the standard BibTeX exporter from Zotero makes these entirely basic mistakes anymore, so I have no idea why
98this is still up there. Still, there <em>are</em> some LaTeX constructs that Zotero does not export well (although not the ones
99that the MIT page points out – mostly very esoteric math symbols). Better BibTeX however does, and if you ever find an
100exception, I very much welcome <a href="https://github.com/retorquere/zotero-better-bibtex/issues">bug reports</a> so I can get
101that corrected. I haven’t had bug reports like these in ages though. Better BibTeX has quite comprehensive coverage when
102it comes to translating references to correct BibTeX.</p>
103
104<h2 id="how-can-i-make-an-organization-name-display-correctly">How can I make an organization name display correctly?</h2>
105
106<p>It doesn’t look like the MIT librarians have ever used Zotero. You can toggle author fields in Zotero between two-part
107and single-part names by clicking the icon to the right of the author name. Single-part author names are written out
108properly quoted automatically. This is not something you need or want to by hand. You don’t even need Better BibTeX for
109this, or BibTeX at all for all that matter – single-part names (which are approriate for institutions or authors which
110are only ever referred to by a single name, such as Aristotle) is just supported functionality of Zotero even if you use
111the Word/OpenOffice plugins. To add insult to injury, the unnecesary “fix” proposed by the MIT librarians, to be
112performed manually <em>every time</em> you export your references, is actually not a fix at all but a source of problems in its own
113right – see the next point.</p>
114
115<h2 id="how-can-i-override-bibtex-capitalization-conventions">How can I override BibTeX capitalization conventions?</h2>
116
117<p>Again, the MIT librarians are making unwarranted assumptions here about what Zotero writes out <em>and</em> are suggesting a
118“solution” that is actually as bad as the problem it sets out to solve. The proper way to prevent</p>
119
120<blockquote>
121  <p>title={IEE Proceedings}</p>
122</blockquote>
123
124<p>to be turned into</p>
125
126<blockquote>
127  <p>Iee proceedings</p>
128</blockquote>
129
130<p>when your document is compiled is <strong>not</strong> to encode it as the MIT librarians suggest using</p>
131
132<blockquote>
133  <p>title=”{IEE Proceedings}”</p>
134</blockquote>
135
136<p>but rather</p>
137
138<blockquote>
139  <p>title={{IEE} Proceedings}</p>
140</blockquote>
141
142<p>The “solution” suggested by the MIT librarians does indeed prevent BibTeX from meddling with your capitalization, except
143some citation styles <em>demand</em> that they are able to do this – some styles demand that that title would become</p>
144
145<blockquote>
146  <p>IEE proceedings</p>
147</blockquote>
148
149<p>and the MIT “solution” prevents this. You only want to protect those exact <em>parts</em> that you want to exclude from this
150process, and guess what: <em>Zotero already does this</em> for words containing uppercase letters, so once again, the MIT
151librarians are offering a broken solution to a non-problem.</p>
152
153<p>In the case of Better BibTeX, it will even do this for non-ASCII capital letters like <code class="language-plaintext highlighter-rouge">Ñ</code>, and it handles a number of
154edge cases that the standard Zotero BibTeX doesn’t handle (for example when there italics or superscript bits in your
155title – this is devilishly complex, and I don’t fault Zotero for opting for a simpler translator when most references
156don’t need these features). If there are some parts where you want to keep something lowercased regardless of the
157BibTeX style you chose, you can wrap that part in <code class="language-plaintext highlighter-rouge">&lt;span class="nocase"&gt;....&lt;/span&gt;</code> and whatever’s between them will be
158excluded from case-changing. This is formally supported in Zotero and will work for BibTeX but also if you’re using your
159references in Word/LibreOffice/etc.</p>
160
161<p>Again, you do not need or want to make this change (manually or otherwise) every time you export to BibTeX when Zotero is perfectly
162capable of doing this for you. The rules governing such bracing are complex, and Better BibTeX will handle the complexity
163on your behalf if you will just let it.</p>
164
165<p>Or maybe you get extra points at MIT for doing references in unnecessarily clunky ways using very old and outdated
166versions of Zotero/Better BibTeX. But in that case I’d suggest just upgrading Zotero/Better BibTeX and lying to the
167librarians that you followed their recommendations, and use the extra time so gained to making your killer thesis
168argument even better.</p>
169
170      </div>
171    </div>
172
173    <footer class="site-footer">
174
175  <div class="wrapper">
176
177    <h2 class="footer-heading">Retorquere on GitHub</h2>
178
179    <div class="footer-col-wrapper">
180      <div class="footer-col  footer-col-1">
181        <ul class="contact-list">
182          <li>Retorquere on GitHub</li>
183          <li><a href="/cdn-cgi/l/email-protection#a2"></a></li>
184        </ul>
185      </div>
186
187      <div class="footer-col  footer-col-2">
188        <ul class="social-media-list">
189          
190          <li>
191            <a href="https://github.com/retorquere">
192              <span class="icon  icon--github">
193                <svg viewBox="0 0 16 16">
194                  <path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761 c0,3.428,2.223,6.337,5.307,7.363c0.388,0.071,0.53-0.168,0.53-0.374c0-0.184-0.007-0.672-0.01-1.32 c-2.159,0.469-2.614-1.04-2.614-1.04c-0.353-0.896-0.862-1.135-0.862-1.135c-0.705-0.481,0.053-0.472,0.053-0.472 c0.779,0.055,1.189,0.8,1.189,0.8c0.692,1.186,1.816,0.843,2.258,0.645c0.071-0.502,0.271-0.843,0.493-1.037 C4.86,11.425,3.049,10.76,3.049,7.786c0-0.847,0.302-1.54,0.799-2.082C3.768,5.507,3.501,4.718,3.924,3.65 c0,0,0.652-0.209,2.134,0.796C6.677,4.273,7.34,4.187,8,4.184c0.659,0.003,1.323,0.089,1.943,0.261 c1.482-1.004,2.132-0.796,2.132-0.796c0.423,1.068,0.157,1.857,0.077,2.054c0.497,0.542,0.798,1.235,0.798,2.082 c0,2.981-1.814,3.637-3.543,3.829c0.279,0.24,0.527,0.713,0.527,1.437c0,1.037-0.01,1.874-0.01,2.129 c0,0.208,0.14,0.449,0.534,0.373c3.081-1.028,5.302-3.935,5.302-7.362C15.76,3.906,12.285,0.431,7.999,0.431z"/>
195                </svg>
196              </span>
197
198              <span class="username">retorquere</span>
199            </a>
200          </li>
201          
202
203          
204          <li>
205            <a href="https://twitter.com/retorquere">
206              <span class="icon  icon--twitter">
207                <svg viewBox="0 0 16 16">
208                  <path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809
209                  c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27 c0,0.256,0.029,0.506,0.085,0.745C5.163,5.404,2.753,4.102,1.14,2.124C0.859,2.607,0.698,3.168,0.698,3.767 c0,1.134,0.577,2.135,1.455,2.722C1.616,6.472,1.112,6.325,0.671,6.08c0,0.014,0,0.027,0,0.041c0,1.584,1.127,2.906,2.623,3.206 C3.02,9.402,2.731,9.442,2.433,9.442c-0.211,0-0.416-0.021-0.615-0.059c0.416,1.299,1.624,2.245,3.055,2.271 c-1.119,0.877-2.529,1.4-4.061,1.4c-0.264,0-0.524-0.015-0.78-0.046c1.447,0.928,3.166,1.469,5.013,1.469 c6.015,0,9.304-4.983,9.304-9.304c0-0.142-0.003-0.283-0.009-0.423C14.976,4.29,15.531,3.714,15.969,3.058z"/>
210                </svg>
211              </span>
212
213              <span class="username">retorquere</span>
214            </a>
215          </li>
216          
217        </ul>
218      </div>
219
220      <div class="footer-col  footer-col-3">
221        <p class="text">Just random thoughts
222</p>
223      </div>
224    </div>
225
226  </div>
227
228</footer>
vendor: 113 bytes, lines 228-231
228
229
230
231  <script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script>
231<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"cc7cfaa388b747c88eba7d4b32a91ac8","r":1,"spa":2}' crossorigin="anonymous"></script>
231
232</body>
233
234</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.