` tags. It also leaves any `` and `` tags untranslated.
14 | - **Note**: This means you probably have to set up again some of the custom formatting you've added. Some custom rules for the translations can be configured in the hidden preferences with the `html2md` properties, but they now require you to restart Zotero. Please ping me if you need additional rules not included there.
15 | - Custom placeholders (not yet in the documentation).
16 | - Added a `noteTitle` placeholder to have different formatting from an item's title.
17 | - Added the ability to customise the text for Zotero links in hidden preferences
18 | - A few bug fixes
19 |
20 | ## [v0.1.3](https://github.com/argenos/zotero-mdnotes/releases/tag/0.1.3) - 2021-02-17
21 |
22 | - The `Create Standalone Note` menu is now optional and can be deactivated in the preferences.
23 | - Add separate menu for single-file exports
24 | - Make the Mdnotes menu slightly context-aware. If you select the single-file option under `File organization`, the menu should now be somewhat less confusing. This release also includes better documentation on how to use the single-file config option.
25 | - Add wiki link format for PDF attachments (#49)
26 | - Updated documentation
27 | - Add instructions to update mdnotes to the documentation (#45)
28 | - Standalone menu is now optional
29 | - Add details to configuration page for single- and multi-file exports
30 |
31 | ## [v0.1.2](https://github.com/argenos/zotero-mdnotes/releases/tag/0.1.2) - 2020-11-16
32 |
33 | - Fixed a bug where Zotero notes would not be exported (due to unsanitized file names)
34 |
35 | ## [v0.1.1](https://github.com/argenos/zotero-mdnotes/releases/tag/0.1.1) - 2020-11-16
36 |
37 | - Fix the export of missing URL fields
38 | - Fix the attachment as linked files when exporting Zotero notes to markdown.
39 | - Fix broken links
40 | - Fix formatting for placeholders
41 |
42 | ## [v0.1.0](https://github.com/argenos/zotero-mdnotes/releases/tag/0.1.0) - 2020-11-15
43 |
44 | - Add support for templates.
45 | - Removes unused preferences that are replaced by placeholders.
46 | - Add custom formatting for fields
47 | - Add hidden preference to customize the format of Zotero Notes
48 | - The content of the batch export with the single-file setting is now consistent with the split-files settings.
49 | - Remove automatic capitalization of links
50 | - Add support for standalone markdown notes
51 | - Zotero notes can now also include tags and related items
52 | - Renames the "Export Zotero item" menu to "Export to markdown"
53 | - The menu to export a Zotero note was merged into "Export to markdown"
54 | - Add option to use `file://` links for PDF attachments instead of using the URL scheme from Zotero (`zotero://`)
55 | - Hidden option to attach Obsidian URI links after notes are exported.
56 | - Other improvements and bug fixes to make things better under the hood.
57 |
58 | ## [v0.0.7](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.7) - 2020-09-06
59 |
60 | - Move Zotero links to metadata for single files (#9)
61 |
62 | ## [v0.0.6](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.6) - 2020-08-25
63 |
64 | - Fix create note preference
65 |
66 | ## [v0.0.5](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.5) - 2020-08-24
67 |
68 | - Add hidden preference for links to dates and type
69 | - Use tabs for preferences
70 |
71 | ## [v0.0.4](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.4) - 2020-08-20
72 |
73 | - Fix note names in Item export
74 | - Add links to PDFs in metadata
75 | - Changes label for adding notes as linked attachments
76 |
77 | ## [v0.0.3](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.3) - 2020-08-01
78 |
79 | - Change date format in Zotfile-extracted note titles to `yyyy-mm-dd` (compatibility with Windows)
80 |
81 | ## [v0.0.2](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.2) - 2020-07-29
82 |
83 | - Make user's home the default path
84 | - Add publication title only if available
85 | - Fix missing line before annotations header
86 | - Remove code block formatting from citekey
87 | - Fix missing publication titles
88 |
89 | ## [v0.0.1](https://github.com/argenos/zotero-mdnotes/releases/tag/0.0.1) - 202-07-28
90 |
91 | - Export Zotero metadata to markdown and creating a file for your own notes.
92 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to Mdnotes
2 |
3 | Hi! First of all, thanks for your interest in contributing to this plugin! Here are a couple of things to note about the status of this plugin and how to best help out.
4 |
5 | I am using [semantic versioning](https://semver.org/) for the releases of this project. Current versions still fall under this category:
6 |
7 | > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
8 |
9 | The main reason behind this is that this plugin started mostly as a script for my personal use. As more folks have started using this plugin, and more requests have been coming in, I've decided to do some refactoring to make it easier for other folks to contribute.
10 | Unfortunately, I can only work on this on my spare time, so it might take me a little while before this happens. You can track the progress for that [here](https://github.com/argenos/zotero-mdnotes/projects/1).
11 |
12 | ## Pull requests
13 |
14 | [Pull requests](https://github.com/argenos/zotero-mdnotes/pulls) are most definitely welcome if you can spare some time. Before you start working on something, please open an issue to discuss the changes you want to add. **I don't recommend starting any changes until v0.1.0 is released**, as the API is changing dramatically, but if there's something minor that can be easily modified we can discuss that in an issue.
15 |
16 | Please keep in mind that any additions you add should be as editor-agnostic as possible. If you want to add something specific for your editor of choice, it **MUST** be optional.
17 |
18 | ## Opening an issue
19 |
20 | Please use the templates I've provided, that will save both you and me a lot of time about details I need to consider your request.
21 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU GENERAL PUBLIC LICENSE
2 | Version 3, 29 June 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU General Public License is a free, copyleft license for
11 | software and other kinds of works.
12 |
13 | The licenses for most software and other practical works are designed
14 | to take away your freedom to share and change the works. By contrast,
15 | the GNU General Public License is intended to guarantee your freedom to
16 | share and change all versions of a program--to make sure it remains free
17 | software for all its users. We, the Free Software Foundation, use the
18 | GNU General Public License for most of our software; it applies also to
19 | any other work released this way by its authors. You can apply it to
20 | your programs, too.
21 |
22 | When we speak of free software, we are referring to freedom, not
23 | price. Our General Public Licenses are designed to make sure that you
24 | have the freedom to distribute copies of free software (and charge for
25 | them if you wish), that you receive source code or can get it if you
26 | want it, that you can change the software or use pieces of it in new
27 | free programs, and that you know you can do these things.
28 |
29 | To protect your rights, we need to prevent others from denying you
30 | these rights or asking you to surrender the rights. Therefore, you have
31 | certain responsibilities if you distribute copies of the software, or if
32 | you modify it: responsibilities to respect the freedom of others.
33 |
34 | For example, if you distribute copies of such a program, whether
35 | gratis or for a fee, you must pass on to the recipients the same
36 | freedoms that you received. You must make sure that they, too, receive
37 | or can get the source code. And you must show them these terms so they
38 | know their rights.
39 |
40 | Developers that use the GNU GPL protect your rights with two steps:
41 | (1) assert copyright on the software, and (2) offer you this License
42 | giving you legal permission to copy, distribute and/or modify it.
43 |
44 | For the developers' and authors' protection, the GPL clearly explains
45 | that there is no warranty for this free software. For both users' and
46 | authors' sake, the GPL requires that modified versions be marked as
47 | changed, so that their problems will not be attributed erroneously to
48 | authors of previous versions.
49 |
50 | Some devices are designed to deny users access to install or run
51 | modified versions of the software inside them, although the manufacturer
52 | can do so. This is fundamentally incompatible with the aim of
53 | protecting users' freedom to change the software. The systematic
54 | pattern of such abuse occurs in the area of products for individuals to
55 | use, which is precisely where it is most unacceptable. Therefore, we
56 | have designed this version of the GPL to prohibit the practice for those
57 | products. If such problems arise substantially in other domains, we
58 | stand ready to extend this provision to those domains in future versions
59 | of the GPL, as needed to protect the freedom of users.
60 |
61 | Finally, every program is threatened constantly by software patents.
62 | States should not allow patents to restrict development and use of
63 | software on general-purpose computers, but in those that do, we wish to
64 | avoid the special danger that patents applied to a free program could
65 | make it effectively proprietary. To prevent this, the GPL assures that
66 | patents cannot be used to render the program non-free.
67 |
68 | The precise terms and conditions for copying, distribution and
69 | modification follow.
70 |
71 | TERMS AND CONDITIONS
72 |
73 | 0. Definitions.
74 |
75 | "This License" refers to version 3 of the GNU General Public License.
76 |
77 | "Copyright" also means copyright-like laws that apply to other kinds of
78 | works, such as semiconductor masks.
79 |
80 | "The Program" refers to any copyrightable work licensed under this
81 | License. Each licensee is addressed as "you". "Licensees" and
82 | "recipients" may be individuals or organizations.
83 |
84 | To "modify" a work means to copy from or adapt all or part of the work
85 | in a fashion requiring copyright permission, other than the making of an
86 | exact copy. The resulting work is called a "modified version" of the
87 | earlier work or a work "based on" the earlier work.
88 |
89 | A "covered work" means either the unmodified Program or a work based
90 | on the Program.
91 |
92 | To "propagate" a work means to do anything with it that, without
93 | permission, would make you directly or secondarily liable for
94 | infringement under applicable copyright law, except executing it on a
95 | computer or modifying a private copy. Propagation includes copying,
96 | distribution (with or without modification), making available to the
97 | public, and in some countries other activities as well.
98 |
99 | To "convey" a work means any kind of propagation that enables other
100 | parties to make or receive copies. Mere interaction with a user through
101 | a computer network, with no transfer of a copy, is not conveying.
102 |
103 | An interactive user interface displays "Appropriate Legal Notices"
104 | to the extent that it includes a convenient and prominently visible
105 | feature that (1) displays an appropriate copyright notice, and (2)
106 | tells the user that there is no warranty for the work (except to the
107 | extent that warranties are provided), that licensees may convey the
108 | work under this License, and how to view a copy of this License. If
109 | the interface presents a list of user commands or options, such as a
110 | menu, a prominent item in the list meets this criterion.
111 |
112 | 1. Source Code.
113 |
114 | The "source code" for a work means the preferred form of the work
115 | for making modifications to it. "Object code" means any non-source
116 | form of a work.
117 |
118 | A "Standard Interface" means an interface that either is an official
119 | standard defined by a recognized standards body, or, in the case of
120 | interfaces specified for a particular programming language, one that
121 | is widely used among developers working in that language.
122 |
123 | The "System Libraries" of an executable work include anything, other
124 | than the work as a whole, that (a) is included in the normal form of
125 | packaging a Major Component, but which is not part of that Major
126 | Component, and (b) serves only to enable use of the work with that
127 | Major Component, or to implement a Standard Interface for which an
128 | implementation is available to the public in source code form. A
129 | "Major Component", in this context, means a major essential component
130 | (kernel, window system, and so on) of the specific operating system
131 | (if any) on which the executable work runs, or a compiler used to
132 | produce the work, or an object code interpreter used to run it.
133 |
134 | The "Corresponding Source" for a work in object code form means all
135 | the source code needed to generate, install, and (for an executable
136 | work) run the object code and to modify the work, including scripts to
137 | control those activities. However, it does not include the work's
138 | System Libraries, or general-purpose tools or generally available free
139 | programs which are used unmodified in performing those activities but
140 | which are not part of the work. For example, Corresponding Source
141 | includes interface definition files associated with source files for
142 | the work, and the source code for shared libraries and dynamically
143 | linked subprograms that the work is specifically designed to require,
144 | such as by intimate data communication or control flow between those
145 | subprograms and other parts of the work.
146 |
147 | The Corresponding Source need not include anything that users
148 | can regenerate automatically from other parts of the Corresponding
149 | Source.
150 |
151 | The Corresponding Source for a work in source code form is that
152 | same work.
153 |
154 | 2. Basic Permissions.
155 |
156 | All rights granted under this License are granted for the term of
157 | copyright on the Program, and are irrevocable provided the stated
158 | conditions are met. This License explicitly affirms your unlimited
159 | permission to run the unmodified Program. The output from running a
160 | covered work is covered by this License only if the output, given its
161 | content, constitutes a covered work. This License acknowledges your
162 | rights of fair use or other equivalent, as provided by copyright law.
163 |
164 | You may make, run and propagate covered works that you do not
165 | convey, without conditions so long as your license otherwise remains
166 | in force. You may convey covered works to others for the sole purpose
167 | of having them make modifications exclusively for you, or provide you
168 | with facilities for running those works, provided that you comply with
169 | the terms of this License in conveying all material for which you do
170 | not control copyright. Those thus making or running the covered works
171 | for you must do so exclusively on your behalf, under your direction
172 | and control, on terms that prohibit them from making any copies of
173 | your copyrighted material outside their relationship with you.
174 |
175 | Conveying under any other circumstances is permitted solely under
176 | the conditions stated below. Sublicensing is not allowed; section 10
177 | makes it unnecessary.
178 |
179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
180 |
181 | No covered work shall be deemed part of an effective technological
182 | measure under any applicable law fulfilling obligations under article
183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
184 | similar laws prohibiting or restricting circumvention of such
185 | measures.
186 |
187 | When you convey a covered work, you waive any legal power to forbid
188 | circumvention of technological measures to the extent such circumvention
189 | is effected by exercising rights under this License with respect to
190 | the covered work, and you disclaim any intention to limit operation or
191 | modification of the work as a means of enforcing, against the work's
192 | users, your or third parties' legal rights to forbid circumvention of
193 | technological measures.
194 |
195 | 4. Conveying Verbatim Copies.
196 |
197 | You may convey verbatim copies of the Program's source code as you
198 | receive it, in any medium, provided that you conspicuously and
199 | appropriately publish on each copy an appropriate copyright notice;
200 | keep intact all notices stating that this License and any
201 | non-permissive terms added in accord with section 7 apply to the code;
202 | keep intact all notices of the absence of any warranty; and give all
203 | recipients a copy of this License along with the Program.
204 |
205 | You may charge any price or no price for each copy that you convey,
206 | and you may offer support or warranty protection for a fee.
207 |
208 | 5. Conveying Modified Source Versions.
209 |
210 | You may convey a work based on the Program, or the modifications to
211 | produce it from the Program, in the form of source code under the
212 | terms of section 4, provided that you also meet all of these conditions:
213 |
214 | a) The work must carry prominent notices stating that you modified
215 | it, and giving a relevant date.
216 |
217 | b) The work must carry prominent notices stating that it is
218 | released under this License and any conditions added under section
219 | 7. This requirement modifies the requirement in section 4 to
220 | "keep intact all notices".
221 |
222 | c) You must license the entire work, as a whole, under this
223 | License to anyone who comes into possession of a copy. This
224 | License will therefore apply, along with any applicable section 7
225 | additional terms, to the whole of the work, and all its parts,
226 | regardless of how they are packaged. This License gives no
227 | permission to license the work in any other way, but it does not
228 | invalidate such permission if you have separately received it.
229 |
230 | d) If the work has interactive user interfaces, each must display
231 | Appropriate Legal Notices; however, if the Program has interactive
232 | interfaces that do not display Appropriate Legal Notices, your
233 | work need not make them do so.
234 |
235 | A compilation of a covered work with other separate and independent
236 | works, which are not by their nature extensions of the covered work,
237 | and which are not combined with it such as to form a larger program,
238 | in or on a volume of a storage or distribution medium, is called an
239 | "aggregate" if the compilation and its resulting copyright are not
240 | used to limit the access or legal rights of the compilation's users
241 | beyond what the individual works permit. Inclusion of a covered work
242 | in an aggregate does not cause this License to apply to the other
243 | parts of the aggregate.
244 |
245 | 6. Conveying Non-Source Forms.
246 |
247 | You may convey a covered work in object code form under the terms
248 | of sections 4 and 5, provided that you also convey the
249 | machine-readable Corresponding Source under the terms of this License,
250 | in one of these ways:
251 |
252 | a) Convey the object code in, or embodied in, a physical product
253 | (including a physical distribution medium), accompanied by the
254 | Corresponding Source fixed on a durable physical medium
255 | customarily used for software interchange.
256 |
257 | b) Convey the object code in, or embodied in, a physical product
258 | (including a physical distribution medium), accompanied by a
259 | written offer, valid for at least three years and valid for as
260 | long as you offer spare parts or customer support for that product
261 | model, to give anyone who possesses the object code either (1) a
262 | copy of the Corresponding Source for all the software in the
263 | product that is covered by this License, on a durable physical
264 | medium customarily used for software interchange, for a price no
265 | more than your reasonable cost of physically performing this
266 | conveying of source, or (2) access to copy the
267 | Corresponding Source from a network server at no charge.
268 |
269 | c) Convey individual copies of the object code with a copy of the
270 | written offer to provide the Corresponding Source. This
271 | alternative is allowed only occasionally and noncommercially, and
272 | only if you received the object code with such an offer, in accord
273 | with subsection 6b.
274 |
275 | d) Convey the object code by offering access from a designated
276 | place (gratis or for a charge), and offer equivalent access to the
277 | Corresponding Source in the same way through the same place at no
278 | further charge. You need not require recipients to copy the
279 | Corresponding Source along with the object code. If the place to
280 | copy the object code is a network server, the Corresponding Source
281 | may be on a different server (operated by you or a third party)
282 | that supports equivalent copying facilities, provided you maintain
283 | clear directions next to the object code saying where to find the
284 | Corresponding Source. Regardless of what server hosts the
285 | Corresponding Source, you remain obligated to ensure that it is
286 | available for as long as needed to satisfy these requirements.
287 |
288 | e) Convey the object code using peer-to-peer transmission, provided
289 | you inform other peers where the object code and Corresponding
290 | Source of the work are being offered to the general public at no
291 | charge under subsection 6d.
292 |
293 | A separable portion of the object code, whose source code is excluded
294 | from the Corresponding Source as a System Library, need not be
295 | included in conveying the object code work.
296 |
297 | A "User Product" is either (1) a "consumer product", which means any
298 | tangible personal property which is normally used for personal, family,
299 | or household purposes, or (2) anything designed or sold for incorporation
300 | into a dwelling. In determining whether a product is a consumer product,
301 | doubtful cases shall be resolved in favor of coverage. For a particular
302 | product received by a particular user, "normally used" refers to a
303 | typical or common use of that class of product, regardless of the status
304 | of the particular user or of the way in which the particular user
305 | actually uses, or expects or is expected to use, the product. A product
306 | is a consumer product regardless of whether the product has substantial
307 | commercial, industrial or non-consumer uses, unless such uses represent
308 | the only significant mode of use of the product.
309 |
310 | "Installation Information" for a User Product means any methods,
311 | procedures, authorization keys, or other information required to install
312 | and execute modified versions of a covered work in that User Product from
313 | a modified version of its Corresponding Source. The information must
314 | suffice to ensure that the continued functioning of the modified object
315 | code is in no case prevented or interfered with solely because
316 | modification has been made.
317 |
318 | If you convey an object code work under this section in, or with, or
319 | specifically for use in, a User Product, and the conveying occurs as
320 | part of a transaction in which the right of possession and use of the
321 | User Product is transferred to the recipient in perpetuity or for a
322 | fixed term (regardless of how the transaction is characterized), the
323 | Corresponding Source conveyed under this section must be accompanied
324 | by the Installation Information. But this requirement does not apply
325 | if neither you nor any third party retains the ability to install
326 | modified object code on the User Product (for example, the work has
327 | been installed in ROM).
328 |
329 | The requirement to provide Installation Information does not include a
330 | requirement to continue to provide support service, warranty, or updates
331 | for a work that has been modified or installed by the recipient, or for
332 | the User Product in which it has been modified or installed. Access to a
333 | network may be denied when the modification itself materially and
334 | adversely affects the operation of the network or violates the rules and
335 | protocols for communication across the network.
336 |
337 | Corresponding Source conveyed, and Installation Information provided,
338 | in accord with this section must be in a format that is publicly
339 | documented (and with an implementation available to the public in
340 | source code form), and must require no special password or key for
341 | unpacking, reading or copying.
342 |
343 | 7. Additional Terms.
344 |
345 | "Additional permissions" are terms that supplement the terms of this
346 | License by making exceptions from one or more of its conditions.
347 | Additional permissions that are applicable to the entire Program shall
348 | be treated as though they were included in this License, to the extent
349 | that they are valid under applicable law. If additional permissions
350 | apply only to part of the Program, that part may be used separately
351 | under those permissions, but the entire Program remains governed by
352 | this License without regard to the additional permissions.
353 |
354 | When you convey a copy of a covered work, you may at your option
355 | remove any additional permissions from that copy, or from any part of
356 | it. (Additional permissions may be written to require their own
357 | removal in certain cases when you modify the work.) You may place
358 | additional permissions on material, added by you to a covered work,
359 | for which you have or can give appropriate copyright permission.
360 |
361 | Notwithstanding any other provision of this License, for material you
362 | add to a covered work, you may (if authorized by the copyright holders of
363 | that material) supplement the terms of this License with terms:
364 |
365 | a) Disclaiming warranty or limiting liability differently from the
366 | terms of sections 15 and 16 of this License; or
367 |
368 | b) Requiring preservation of specified reasonable legal notices or
369 | author attributions in that material or in the Appropriate Legal
370 | Notices displayed by works containing it; or
371 |
372 | c) Prohibiting misrepresentation of the origin of that material, or
373 | requiring that modified versions of such material be marked in
374 | reasonable ways as different from the original version; or
375 |
376 | d) Limiting the use for publicity purposes of names of licensors or
377 | authors of the material; or
378 |
379 | e) Declining to grant rights under trademark law for use of some
380 | trade names, trademarks, or service marks; or
381 |
382 | f) Requiring indemnification of licensors and authors of that
383 | material by anyone who conveys the material (or modified versions of
384 | it) with contractual assumptions of liability to the recipient, for
385 | any liability that these contractual assumptions directly impose on
386 | those licensors and authors.
387 |
388 | All other non-permissive additional terms are considered "further
389 | restrictions" within the meaning of section 10. If the Program as you
390 | received it, or any part of it, contains a notice stating that it is
391 | governed by this License along with a term that is a further
392 | restriction, you may remove that term. If a license document contains
393 | a further restriction but permits relicensing or conveying under this
394 | License, you may add to a covered work material governed by the terms
395 | of that license document, provided that the further restriction does
396 | not survive such relicensing or conveying.
397 |
398 | If you add terms to a covered work in accord with this section, you
399 | must place, in the relevant source files, a statement of the
400 | additional terms that apply to those files, or a notice indicating
401 | where to find the applicable terms.
402 |
403 | Additional terms, permissive or non-permissive, may be stated in the
404 | form of a separately written license, or stated as exceptions;
405 | the above requirements apply either way.
406 |
407 | 8. Termination.
408 |
409 | You may not propagate or modify a covered work except as expressly
410 | provided under this License. Any attempt otherwise to propagate or
411 | modify it is void, and will automatically terminate your rights under
412 | this License (including any patent licenses granted under the third
413 | paragraph of section 11).
414 |
415 | However, if you cease all violation of this License, then your
416 | license from a particular copyright holder is reinstated (a)
417 | provisionally, unless and until the copyright holder explicitly and
418 | finally terminates your license, and (b) permanently, if the copyright
419 | holder fails to notify you of the violation by some reasonable means
420 | prior to 60 days after the cessation.
421 |
422 | Moreover, your license from a particular copyright holder is
423 | reinstated permanently if the copyright holder notifies you of the
424 | violation by some reasonable means, this is the first time you have
425 | received notice of violation of this License (for any work) from that
426 | copyright holder, and you cure the violation prior to 30 days after
427 | your receipt of the notice.
428 |
429 | Termination of your rights under this section does not terminate the
430 | licenses of parties who have received copies or rights from you under
431 | this License. If your rights have been terminated and not permanently
432 | reinstated, you do not qualify to receive new licenses for the same
433 | material under section 10.
434 |
435 | 9. Acceptance Not Required for Having Copies.
436 |
437 | You are not required to accept this License in order to receive or
438 | run a copy of the Program. Ancillary propagation of a covered work
439 | occurring solely as a consequence of using peer-to-peer transmission
440 | to receive a copy likewise does not require acceptance. However,
441 | nothing other than this License grants you permission to propagate or
442 | modify any covered work. These actions infringe copyright if you do
443 | not accept this License. Therefore, by modifying or propagating a
444 | covered work, you indicate your acceptance of this License to do so.
445 |
446 | 10. Automatic Licensing of Downstream Recipients.
447 |
448 | Each time you convey a covered work, the recipient automatically
449 | receives a license from the original licensors, to run, modify and
450 | propagate that work, subject to this License. You are not responsible
451 | for enforcing compliance by third parties with this License.
452 |
453 | An "entity transaction" is a transaction transferring control of an
454 | organization, or substantially all assets of one, or subdividing an
455 | organization, or merging organizations. If propagation of a covered
456 | work results from an entity transaction, each party to that
457 | transaction who receives a copy of the work also receives whatever
458 | licenses to the work the party's predecessor in interest had or could
459 | give under the previous paragraph, plus a right to possession of the
460 | Corresponding Source of the work from the predecessor in interest, if
461 | the predecessor has it or can get it with reasonable efforts.
462 |
463 | You may not impose any further restrictions on the exercise of the
464 | rights granted or affirmed under this License. For example, you may
465 | not impose a license fee, royalty, or other charge for exercise of
466 | rights granted under this License, and you may not initiate litigation
467 | (including a cross-claim or counterclaim in a lawsuit) alleging that
468 | any patent claim is infringed by making, using, selling, offering for
469 | sale, or importing the Program or any portion of it.
470 |
471 | 11. Patents.
472 |
473 | A "contributor" is a copyright holder who authorizes use under this
474 | License of the Program or a work on which the Program is based. The
475 | work thus licensed is called the contributor's "contributor version".
476 |
477 | A contributor's "essential patent claims" are all patent claims
478 | owned or controlled by the contributor, whether already acquired or
479 | hereafter acquired, that would be infringed by some manner, permitted
480 | by this License, of making, using, or selling its contributor version,
481 | but do not include claims that would be infringed only as a
482 | consequence of further modification of the contributor version. For
483 | purposes of this definition, "control" includes the right to grant
484 | patent sublicenses in a manner consistent with the requirements of
485 | this License.
486 |
487 | Each contributor grants you a non-exclusive, worldwide, royalty-free
488 | patent license under the contributor's essential patent claims, to
489 | make, use, sell, offer for sale, import and otherwise run, modify and
490 | propagate the contents of its contributor version.
491 |
492 | In the following three paragraphs, a "patent license" is any express
493 | agreement or commitment, however denominated, not to enforce a patent
494 | (such as an express permission to practice a patent or covenant not to
495 | sue for patent infringement). To "grant" such a patent license to a
496 | party means to make such an agreement or commitment not to enforce a
497 | patent against the party.
498 |
499 | If you convey a covered work, knowingly relying on a patent license,
500 | and the Corresponding Source of the work is not available for anyone
501 | to copy, free of charge and under the terms of this License, through a
502 | publicly available network server or other readily accessible means,
503 | then you must either (1) cause the Corresponding Source to be so
504 | available, or (2) arrange to deprive yourself of the benefit of the
505 | patent license for this particular work, or (3) arrange, in a manner
506 | consistent with the requirements of this License, to extend the patent
507 | license to downstream recipients. "Knowingly relying" means you have
508 | actual knowledge that, but for the patent license, your conveying the
509 | covered work in a country, or your recipient's use of the covered work
510 | in a country, would infringe one or more identifiable patents in that
511 | country that you have reason to believe are valid.
512 |
513 | If, pursuant to or in connection with a single transaction or
514 | arrangement, you convey, or propagate by procuring conveyance of, a
515 | covered work, and grant a patent license to some of the parties
516 | receiving the covered work authorizing them to use, propagate, modify
517 | or convey a specific copy of the covered work, then the patent license
518 | you grant is automatically extended to all recipients of the covered
519 | work and works based on it.
520 |
521 | A patent license is "discriminatory" if it does not include within
522 | the scope of its coverage, prohibits the exercise of, or is
523 | conditioned on the non-exercise of one or more of the rights that are
524 | specifically granted under this License. You may not convey a covered
525 | work if you are a party to an arrangement with a third party that is
526 | in the business of distributing software, under which you make payment
527 | to the third party based on the extent of your activity of conveying
528 | the work, and under which the third party grants, to any of the
529 | parties who would receive the covered work from you, a discriminatory
530 | patent license (a) in connection with copies of the covered work
531 | conveyed by you (or copies made from those copies), or (b) primarily
532 | for and in connection with specific products or compilations that
533 | contain the covered work, unless you entered into that arrangement,
534 | or that patent license was granted, prior to 28 March 2007.
535 |
536 | Nothing in this License shall be construed as excluding or limiting
537 | any implied license or other defenses to infringement that may
538 | otherwise be available to you under applicable patent law.
539 |
540 | 12. No Surrender of Others' Freedom.
541 |
542 | If conditions are imposed on you (whether by court order, agreement or
543 | otherwise) that contradict the conditions of this License, they do not
544 | excuse you from the conditions of this License. If you cannot convey a
545 | covered work so as to satisfy simultaneously your obligations under this
546 | License and any other pertinent obligations, then as a consequence you may
547 | not convey it at all. For example, if you agree to terms that obligate you
548 | to collect a royalty for further conveying from those to whom you convey
549 | the Program, the only way you could satisfy both those terms and this
550 | License would be to refrain entirely from conveying the Program.
551 |
552 | 13. Use with the GNU Affero General Public License.
553 |
554 | Notwithstanding any other provision of this License, you have
555 | permission to link or combine any covered work with a work licensed
556 | under version 3 of the GNU Affero General Public License into a single
557 | combined work, and to convey the resulting work. The terms of this
558 | License will continue to apply to the part which is the covered work,
559 | but the special requirements of the GNU Affero General Public License,
560 | section 13, concerning interaction through a network will apply to the
561 | combination as such.
562 |
563 | 14. Revised Versions of this License.
564 |
565 | The Free Software Foundation may publish revised and/or new versions of
566 | the GNU General Public License from time to time. Such new versions will
567 | be similar in spirit to the present version, but may differ in detail to
568 | address new problems or concerns.
569 |
570 | Each version is given a distinguishing version number. If the
571 | Program specifies that a certain numbered version of the GNU General
572 | Public License "or any later version" applies to it, you have the
573 | option of following the terms and conditions either of that numbered
574 | version or of any later version published by the Free Software
575 | Foundation. If the Program does not specify a version number of the
576 | GNU General Public License, you may choose any version ever published
577 | by the Free Software Foundation.
578 |
579 | If the Program specifies that a proxy can decide which future
580 | versions of the GNU General Public License can be used, that proxy's
581 | public statement of acceptance of a version permanently authorizes you
582 | to choose that version for the Program.
583 |
584 | Later license versions may give you additional or different
585 | permissions. However, no additional obligations are imposed on any
586 | author or copyright holder as a result of your choosing to follow a
587 | later version.
588 |
589 | 15. Disclaimer of Warranty.
590 |
591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
599 |
600 | 16. Limitation of Liability.
601 |
602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
610 | SUCH DAMAGES.
611 |
612 | 17. Interpretation of Sections 15 and 16.
613 |
614 | If the disclaimer of warranty and limitation of liability provided
615 | above cannot be given local legal effect according to their terms,
616 | reviewing courts shall apply local law that most closely approximates
617 | an absolute waiver of all civil liability in connection with the
618 | Program, unless a warranty or assumption of liability accompanies a
619 | copy of the Program in return for a fee.
620 |
621 | END OF TERMS AND CONDITIONS
622 |
623 | How to Apply These Terms to Your New Programs
624 |
625 | If you develop a new program, and you want it to be of the greatest
626 | possible use to the public, the best way to achieve this is to make it
627 | free software which everyone can redistribute and change under these terms.
628 |
629 | To do so, attach the following notices to the program. It is safest
630 | to attach them to the start of each source file to most effectively
631 | state the exclusion of warranty; and each file should have at least
632 | the "copyright" line and a pointer to where the full notice is found.
633 |
634 |
635 | Copyright (C)
636 |
637 | This program is free software: you can redistribute it and/or modify
638 | it under the terms of the GNU General Public License as published by
639 | the Free Software Foundation, either version 3 of the License, or
640 | (at your option) any later version.
641 |
642 | This program is distributed in the hope that it will be useful,
643 | but WITHOUT ANY WARRANTY; without even the implied warranty of
644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
645 | GNU General Public License for more details.
646 |
647 | You should have received a copy of the GNU General Public License
648 | along with this program. If not, see .
649 |
650 | Also add information on how to contact you by electronic and paper mail.
651 |
652 | If the program does terminal interaction, make it output a short
653 | notice like this when it starts in an interactive mode:
654 |
655 | Copyright (C)
656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
657 | This is free software, and you are welcome to redistribute it
658 | under certain conditions; type `show c' for details.
659 |
660 | The hypothetical commands `show w' and `show c' should show the appropriate
661 | parts of the General Public License. Of course, your program's commands
662 | might be different; for a GUI interface, you would use an "about box".
663 |
664 | You should also get your employer (if you work as a programmer) or school,
665 | if any, to sign a "copyright disclaimer" for the program, if necessary.
666 | For more information on this, and how to apply and follow the GNU GPL, see
667 | .
668 |
669 | The GNU General Public License does not permit incorporating your program
670 | into proprietary programs. If your program is a subroutine library, you
671 | may consider it more useful to permit linking proprietary applications with
672 | the library. If this is what you want to do, use the GNU Lesser General
673 | Public License instead of this License. But first, please read
674 | .
675 |
--------------------------------------------------------------------------------
/Makefile:
--------------------------------------------------------------------------------
1 | all: Makefile.in
2 |
3 | -include Makefile.in
4 |
5 | # RELEASE:=$(shell grep em:version install.rdf | head -n 1 | sed -e 's/ *//' -e 's/<\/em:version>//')
6 | RELEASE:=$(shell git tag --sort version:refname | tail -n 1)
7 | PREVRELEASE:=$(shell git tag --sort version:refname | tail -n 2 | head -n 1)
8 |
9 | mdnotes.xpi: FORCE
10 | rm -rf $@
11 | yarn build
12 | zip -r $@ content chrome.manifest defaults locale skin install.rdf update.rdf -x \*.DS_Store
13 |
14 | mdnotes-%-fx.xpi: mdnotes.xpi
15 | mv $< $@
16 |
17 | Makefile.in: install.rdf
18 | echo "all: mdnotes-${RELEASE}-fx.xpi" > Makefile.in
19 |
20 | release: mdnotes.xpi
21 | @mv $< mdnotes-$(RELEASE).xpi
22 | # Replace old version with new version in install.rdf and update.rdf
23 | sed -i 's/${PREVRELEASE}/${RELEASE}/g' install.rdf
24 | sed -i 's/${PREVRELEASE}/${RELEASE}/g' update.rdf
25 | # Show commits between the last two tags
26 | # @echo "\nChangelog\n------------"
27 | @git log --pretty=format:"%s" $(PREVRELEASE)..$(RELEASE) > changelog.md
28 |
29 | clean:
30 | rm -rf *.xpi
31 |
32 | FORCE:
33 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Mdnotes
2 |
3 | > [!IMPORTANT]
4 | > This plugin is not compatible with Zotero 7, and unfortunately I no longer have time to maintain or update it. There are many alternatives out there by now. If you are an Obsidian user, I recommend migrating to the [Zotero Integration plugin](https://github.com/mgmeyers/obsidian-zotero-integration).
5 | > Good luck out there!
6 |
7 | A Zotero plugin to export item metadata and notes as markdown files.
8 |
9 | ## Features
10 |
11 | Right now the menu is not context-aware, so read below to see what has to be selected for the menu to correctly create the files. Note that the output of the following options depends on your [configuration](docs/getting-started/configuration.md), the options below apply for the default settings:
12 |
13 | | What you want to do | What to select | Menu |
14 | | ------------------------------------------------------------ | -------------- | --|
15 | | [Export Zotero item metadata file](./docs/getting-started/README.md#export-a-zotero-item-or-notes-to-markdown) | Zotero Item | `Export to markdown` |
16 | | [Export Zotero notes to markdown](./docs/getting-started/README.md#export-a-zotero-item-or-notes-to-markdown) | Zotero Note | `Export to markdown` |
17 | | [Create a file for your own notes](./docs/getting-started/README.md#create-a-file-for-your-own-notes) | Zotero Item | `Create mdnotes file` |
18 | | [Batch export all of the above](http://argenos.github.io/zotero-mdnotes/#batch-export-all-metadata-and-notes) | Zotero Item | `Batch export to markdown` |
19 |
20 | With the exception of `Create mdnotes file` (for your own notes), you will be asked to choose a path. The file name(s) are automatically chosen based on the naming convention described in the section for each menu.
21 |
22 | To access the menu right-click on an item or note:
23 |
24 |
25 |
26 | ## Requirements
27 |
28 | Tested with Zotero v5.0.89 in Ubuntu 18.04.
29 |
30 | It is highly recommended that you have the following plugins installed:
31 |
32 | * [Zotfile](http://zotfile.com/)
33 | * [BetterBibtex](https://retorque.re/zotero-better-bibtex/)
34 |
35 | I have not tested without them, so I can't guarantee nothing will break.
36 |
37 | ## Installation
38 |
39 | You can install the plugin in Zotero as described [here](https://www.zotero.org/support/plugins):
40 |
41 | > To install a plugin in Zotero, download its `.xpi` file to your computer. Then, in Zotero, click “Tools → Add-Ons”, then drag the `.xpi` for the plugin onto the Add-Ons window that opens
42 |
43 | You can grab the latest version of `zotero-mdnotes` [here](https://github.com/argenos/zotero-mdnotes/releases/latest).
44 |
45 | ## Acknowledgements
46 |
47 | This plugin is based and was inspired by [zotero-roam-export](https://github.com/melat0nin/zotero-roam-export/).
48 |
--------------------------------------------------------------------------------
/chrome.manifest:
--------------------------------------------------------------------------------
1 | content mdnotes content/
2 | locale mdnotes en-US locale/en-US/
3 | locale mdnotes zh-CN locale/zh-CN/
4 | skin mdnotes default skin/
5 |
6 | overlay chrome://zotero/content/zoteroPane.xul chrome://mdnotes/content/overlay.xul
7 |
--------------------------------------------------------------------------------
/content/options.xul:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
24 |
25 | );
26 | }
27 |
28 | export default function Home() {
29 | const {siteConfig} = useDocusaurusContext();
30 | return (
31 |
34 |
35 |
36 |
37 |
38 |
39 | );
40 | }
41 |
--------------------------------------------------------------------------------
/docs/src/pages/index.module.css:
--------------------------------------------------------------------------------
1 | /* stylelint-disable docusaurus/copyright-header */
2 |
3 | /**
4 | * CSS files with the .module.css suffix will be treated as CSS modules
5 | * and scoped locally.
6 | */
7 |
8 | .heroBanner {
9 | padding: 4rem 0;
10 | text-align: center;
11 | position: relative;
12 | overflow: hidden;
13 | }
14 |
15 | @media screen and (max-width: 966px) {
16 | .heroBanner {
17 | padding: 2rem;
18 | }
19 | }
20 |
21 | .buttons {
22 | display: flex;
23 | align-items: center;
24 | justify-content: center;
25 | }
26 |
--------------------------------------------------------------------------------
/docs/static/.nojekyll:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/static/.nojekyll
--------------------------------------------------------------------------------
/docs/static/img/code-json.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/static/img/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/static/img/favicon.ico
--------------------------------------------------------------------------------
/docs/static/img/logo.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/static/img/markdown-brands.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/static/img/round-format-shapes.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Advanced Configuration",
3 | "position": 3
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/formatting.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Custom Formatting
3 | sidebar_position: 3
4 | ---
5 |
6 | Starting with **v0.1.0** it's possible to specify custom formatting and to use templates.
7 |
8 | ## Internal links
9 |
10 | The internal link preference influences how file names and therefore how links look.
11 |
12 | - `[[wiki links]]` can contain spaces and maintain their case
13 | - `[Markdown links](markdown-links.md)` are all lower case and spaces are replaced with dashes.
14 |
15 | ## Zotero Note formatting
16 |
17 | Zotero Notes are formated in HTML. The hidden preference `extensions.mdnotes.html_to_md` has a dictionary of how the HTML elements are translated into markdown.
18 |
19 | ## Placeholders
20 |
21 | With a few exceptions, you can format any placeholder by adding (or modifying) them in the settings. You can reach the hidden preferences menu from `Edit > Preferences > Advanced > Config Editor`. You can use the search to find existing configurations:
22 |
23 | 
24 |
25 | ### Default formatting
26 |
27 | #### Placeholder format
28 |
29 | By default, placeholder contents are replaced with:
30 |
31 | ```markdown
32 | {{bullet}} {{field_name}}: {{field_contents}}
33 | ```
34 |
35 | Where:
36 |
37 | - `{{bullet}}` - Defined in `extensions.mdnotes.bullet`
38 | - `{{field_name}}` - The name of the field transformed from camel case into sentence case.
39 | - `{{field_contents}}` - The contents of the field as described below.
40 |
41 | #### Field format
42 |
43 | Any placeholder that doesn't have their formatting defined in the hidden preferences has the following defaults:
44 |
45 | - `link_style`: As defined by the preference of [Internal links](#internal-links). Valid values include `wiki`, `markdown` and `no-links`.
46 | - `list_separator`: For fields that contain more than one value, the default is `, `.
47 | - `text_case`: How to capitalize the contents of the field: `title`, `sentence`, `lower` or `upper` case. The default will return the field content in its original case.
48 | - `remove_spaces`: If this is set to `true` spaces will be replaced with dashes.
49 |
50 | ### Adding new formatting rules
51 |
52 | If you want to add custom formatting for any field not currently there, you can add the format for a placeholder with right-click and `New > String`.
53 |
54 | ### Preference name
55 |
56 | The preference name should be `extensions.mdnotes.placeholder.`, where `yourFieldHere` should match a [supported Zotero field](https://www.zotero.org/support/kb/item_types_and_fields). Keep in mind that Zotero fields are usually accessed using camel case, and should be (usually) formatted as `fieldName`, e.g. `seriesTitle`.
57 |
58 | #### Preference value
59 |
60 | The value of the preference should be enclosed in braces, and defined as key/value pairs, e.g `{"key": "value"}`.
61 |
62 | In addition to the fields described in the [default field format](#field-format), the following options can be specified:
63 |
64 | - `content` - Formatting the placeholder's content ([default placeholder format](#placeholder-format))
65 | - `field_contents` - Formatting the field itself, which defaults to `{{content}}`
66 |
67 | ##### Examples
68 |
69 | Replacing the field label with custom text and changing the list separator to make a list:
70 |
71 | ```markdown
72 | {"content":"{{bullet}} PDF Attachments\n\t- {{field_contents}}", "field_contents": "{{content}}", "list_separator": "\n\t- "}
73 | ```
74 |
75 | Making the tags placeholder remove spaces and adding a hash sign before each tag:
76 |
77 | ```markdown
78 | {"content":"{{bullet}} Tags: {{field_contents}}", "field_contents": "#{{content}}", "link_style": "no-links", "list_separator": ", ", "remove_spaces": "true"}
79 | ```
80 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/placeholders.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Placeholders and wildcards
3 | sidebar_position: 2
4 | ---
5 |
6 | ## Placeholders
7 |
8 | ### Item placeholders
9 |
10 | You can add a `{{placeholder}}` for any [item field](https://www.zotero.org/support/kb/item_types_and_fields) in your templates. Fields are formatted in camel case, so make sure you find the right [field](https://api.zotero.org/itemFields?pprint=1) in Zotero's API.
11 |
12 | During export, any placeholder that is not a match for the selected item or that is blank will not be included in the markdown file.
13 |
14 | In addition to Zotero's supported fields, Mdnotes adds a few placeholders for an item:
15 |
16 | - `{{itemType}}` - The Zotero item type.
17 | - `{{citekey}}` - The citekey (requires the Better Bibtex plugin).
18 | - `{{collections}}` - A list of collections an item belongs to.
19 | - `{{related}}` - A list of [related items](https://www.zotero.org/support/related).
20 | - `{{tags}}` - The list of tags for the selected item.
21 | - `{{pdfAttachments}}` = A list of links to any PDF attachments.
22 | - `{{localLibrary}}` = The `zotero://` link to an item.
23 | - `{{cloudLibrary}}` = If you use [Zotero sync](https://www.zotero.org/support/sync), the link to that item in your cloud library.
24 | - `{{dateAdded}}` - The date the item was added to your library.
25 | - `{{notes}}` - A list of all the titles of all the child notes.
26 | - `{{mdnotesFileName}}` - The name of the default mdnotes file (following the naming convention).
27 | - `{{metadataFileName}}` - The name of the Zotero metadata file (following the naming convention).
28 |
29 | Note: The setting `extensions.mdnotes.templates.include_empty_placeholders` is _NOT_ being used right now and won't have an effect.
30 |
31 | ### Note placeholders
32 |
33 | Mdnotes supports the following placeholders for Zotero notes:
34 |
35 | - `{{mdnotesFileName}}` - The filename for the [mdnotes file](../getting-started/configuration.md#file-naming-convention) according to the file naming convention.
36 | - `{{metadataFileName}}` - The filename for a [Zotero Item export](../getting-started/configuration.md#file-naming-convention) according to the file naming convention.
37 | - `{{title}}` - The note's title (usually the first line).
38 | - `{{noteContent}}` - The contents of the note, translated to markdown as defined in the [preferences](./formatting.md#zotero-note-formatting)
39 | - `{{related}}` - A list of [related items](https://www.zotero.org/support/related).
40 | - `{{tags}}` - The list of tags for the selected note.
41 |
42 | ## Wildcards
43 |
44 | A `%(wildcard)` uses the same logic as the placeholder, but only includes the content of a Zotero item without any formatting. Keep in mind that any fields not included in a Zotero item will not be deleted from your file.
45 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/templates/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Templates",
3 | "position": 1
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/templates/defaults.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Default Templates
3 | sidebar_position: 1
4 | ---
5 |
6 | Templates define how the final Markdown document will look like. Starting on [v0.1.0](/changelog#v010---2020-11-15) you can specify a templates directory in the `Tools > Mdnote preferences`.
7 | Once a directory is specified, `Mdnotes` will look for the following files (they must be named **exactly** like this):
8 |
9 | ```txt
10 | .
11 | ├── Mdnotes Default Template.md
12 | ├── Standalone Note Template.md
13 | ├── Zotero Metadata Template.md
14 | └── Zotero Note Template.md
15 |
16 | ```
17 |
18 | The files must be located at the root of the folder you chose. For now, hidden folders (those starting with `.`) are not supported.
19 | If there is no path specified or the file doesn't exist, Mdnotes will use the default templates.
20 |
21 | The default templates can give you an idea of existing [placeholders and wildcards](../placeholders.md)
22 |
23 | ## Export to markdown
24 |
25 | Using the `Export to markdown` will export whatever you have selected, using the [zotero metadata template](#zotero-metadata-template) if you have selected an item or the [zotero note template](#zotero-note-template) of you have notes in your selected items.
26 |
27 | ### Zotero Metadata Template
28 |
29 | - **Which menu?**: `Export to markdown`
30 | - **What to select?**: A Zotero item.
31 |
32 | You can add (or remove) any [item placeholder](../placeholders.md#item-placeholders) to your template.
33 |
34 | ```markdown title="Zotero Metadata Template.md"
35 | {{title}}
36 |
37 | ## Metadata
38 |
39 | {{itemType}}
40 | {{author}}
41 | {{proceedingsTitle}}
42 | {{date}}
43 | {{dateAdded}}
44 | {{url}}
45 | {{DOI}}
46 | {{citekey}}
47 | {{collections}}
48 | {{related}}
49 | {{tags}}, #zotero, #literature-notes, #reference
50 | {{pdfAttachments}}
51 |
52 | {{abstractNote}}
53 |
54 | ## Zotero links
55 |
56 | {{localLibrary}}
57 | {{cloudLibrary}}
58 |
59 | {{notes}}
60 | ```
61 |
62 | ### Zotero Note Template
63 |
64 | - **Which menu?**: `Export to markdown`
65 | - **What to select?**: A Zotero note.
66 |
67 | You can add (or remove) any [note placeholders](../placeholders.md#note-placeholders) to your template.
68 |
69 | ```markdown title="Zotero Note Template.md"
70 | {{tags}}
71 | {{related}}
72 | {{mdnotesFileName}}
73 |
74 | {{title}}
75 |
76 | {{noteContent}}
77 | ```
78 |
79 | ## Creating files for your notes
80 |
81 | ### Mdnotes Default Template
82 |
83 | This template supports any [item placeholder](../placeholders.md#item-placeholders), which you can add (or remove) from your template.
84 | Read more about the specifics for [single-file](single-file.md) and [multi-file](multi-file.md) exports.
85 |
86 | ```markdown title="Mdnotes Default Template.md"
87 | {{title}}
88 |
89 | ![[%(metadataFileName)#Metadata]]
90 |
91 | Other files:
92 | {{mdnotesFileName}}
93 | {{metadataFileName}}
94 |
95 | ## Zotero links
96 |
97 | {{localLibrary}}
98 | {{cloudLibrary}}
99 |
100 | ## Notes
101 |
102 | -
103 | ```
104 |
105 | ### Standalone Note Template
106 |
107 | - **Which menu?**: `Create a standalone note`.
108 | - **What to select?**: A Zotero item.
109 |
110 | It is essentially a duplicate of the [mdnotes default template](#mdnotes-default-template).
111 | Its purpose is to provide a secondary template that can be used to add notes with _some_ metadata and automatically adding links to Zotero.
112 |
113 | :::info
114 | **Note**: Standalone notes must be activated in the `Mdnotes Preferences`.
115 | :::
116 |
117 | ```markdown title="Standalone Default Template.md"
118 | Related to: [[%(metadataFileName)]]
119 |
120 | ## Notes
121 |
122 | -
123 | ```
124 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/templates/multi-file.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Multi-File Templates
3 | sidebar_position: 2
4 | ---
5 |
6 | Multi-file exports match 1:1 the [default templates](defaults.md).
7 | You can read more about [item](../placeholders.md#item-placeholders) and [note](../placeholders.md#note-placeholders) placeholders in the next section.
8 |
9 | ### Mdnotes Default Template
10 |
11 | - **Which menu?**: `Create mdnotes file`
12 | - **What to select?**: A Zotero item.
13 |
14 | 
15 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/advanced/templates/single-file.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Single-File Templates
3 | sidebar_position: 3
4 | ---
5 |
6 | Single-file exports might require a few changes to the default configuration, depending on your needs, as described in the [single-file configuration](../../getting-started/file-organization/single-file.md).
7 | You can read more about [item](../placeholders.md#item-placeholders) and [note](../placeholders.md#note-placeholders) placeholders in the next section.
8 |
9 | ## Templates used in single-file exports
10 |
11 | - **Which menu?**: `Create full export note`
12 | - **What to select?**: A Zotero item.
13 |
14 | 
15 |
16 | ### Mdnotes Default Template
17 |
18 | For example, you might want to update the template to include an item's metadata:
19 |
20 | ```markdown
21 | {{title}}
22 |
23 | ## Zotero links
24 |
25 | {{localLibrary}}
26 | {{cloudLibrary}}
27 |
28 | ## Metadata
29 |
30 | {{itemType}}
31 | {{author}}
32 | {{proceedingsTitle}}
33 | {{date}}
34 | {{dateAdded}}
35 | {{url}}
36 | {{DOI}}
37 | {{citekey}}
38 | {{collections}}
39 | {{related}}
40 | {{tags}}, #zotero, #literature-notes, #reference
41 | {{pdfAttachments}}
42 |
43 | {{abstractNote}}
44 |
45 | {{notes}}
46 |
47 | ## My notes
48 |
49 | -
50 | ```
51 |
52 | ### Zotero Note Template
53 |
54 | If you include the `{{notes}}` placeholder in the `Mdnotes Default Template`, `mdnotes` will loop through the Zotero Notes of the selected items and add them one by one using this template.
55 |
56 | For single-file exports, you might want to edit your template to look like this:
57 |
58 | ```markdown
59 | {{tags}}
60 | {{related}}
61 |
62 | {{title}}
63 |
64 | {{noteContent}}
65 | ```
66 |
67 | :::info
68 | This template is also used by the `Export to markdown` menu when you select a Zotero note. If you ever want to export, the changes you make will affect both menus.
69 | :::
70 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Getting Started",
3 | "position": 2
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/configuration.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Configuration
3 | sidebar_position: 2
4 | ---
5 |
6 | To access `mdnotes` preferences, go to `Tools > Mdnotes preferences`
7 |
8 | ## Export preferences
9 |
10 | 
11 |
12 | ### Setting the starting path
13 |
14 | In `Tools > Mdnotes preferences` you can choose the path `mdnotes` will open with any of its menus. The path you select is just the starting point, before saving your files you can navigate to any other directory.
15 |
16 | ### File Organization
17 |
18 | You can choose to export your content as a [single file](file-organization/single-file.md) or [multiple files](file-organization/multi-file.md), and will be reflected on the right-click menu.
19 | Which configuration to choose depends on your preferences, and on your Zotfile configuration, the figure below illustrates a few of the possibilities based on the default templates:
20 |
21 | - [Multi-file](file-organization/multi-file.md) exports create separate files: one for your notes (blue), one with the item metadata (green) and one for each note (yellow).
22 | - [Single-file](file-organization/single-file.md) exports add all your content on a single file.
23 |
24 | 
25 |
26 | ### Template directory
27 |
28 | [Templates](../advanced/templates/defaults.md) define how the final Markdown document will look like. Starting on [v0.1.0](/changelog#v010---2020-11-15) you can specify a templates directory in the `Tools > Mdnotes preferences`.
29 |
30 | Depending on your choice of [file organization](#file-organization), you'll need to edit different templates.
31 |
32 | ### Add the created files as linked files to Zotero
33 |
34 | If you select the "Attach file links to Zotero", the markdown files will be added as [linked files](https://www.zotero.org/support/attaching_files#stored_files_and_linked_files), meaning you can access them by double-clicking on them from inside Zotero:
35 |
36 | 
37 |
38 | ## File naming convention
39 |
40 | In general, I recommend using the `citekey` as title. The exported files will use the prefix and suffix for the type of file being exported, following the pattern `.md`.
41 |
42 | 
43 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/file-organization/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "File Organization",
3 | "position": 3
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/file-organization/mdnotes-file-config.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/getting-started/file-organization/mdnotes-file-config.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/file-organization/multi-file.md:
--------------------------------------------------------------------------------
1 | # Multi-file Exports (Default)
2 |
3 | 
4 |
5 | Using the `Split files` option will create, as its name indicates, separate files for your metadata, Zotero notes, or your own notes. Whenever you use the `Export to markdown` menu:
6 |
7 | - One file containing the metadata will be created if you selected a Zotero item using the [`Zotero Metadata Template`](../../advanced/templates/defaults.md#zotero-metadata-template).
8 | - If you select a Zotero note, one file will be created using the [`Zotero Note Template`](../../advanced/templates/defaults.md#zotero-note-template)
9 |
10 | Using the `Create Mdnotes file` will create a note for **your** notes using the [`Mdnotes Default Template`](../../advanced/templates/defaults.md#mdnotes-default-template).
11 |
12 | By selecting a Zotero item and using the `Batch export to markdown` menu, `mdnotes` will create all the above files, i.e. one for the metadata and one for each Zotero note in that item.
13 | If your `Mdnotes` file doesn't exist, it will be created.
14 |
15 | :::info
16 | Your `Mdnotes` file will never be overwritten with the `Batch export` menu. If you wish to do so, you must use the `Create Mdnotes file` and confirm you want to overwrite it.
17 | :::
18 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/file-organization/single-file.md:
--------------------------------------------------------------------------------
1 | # Single-file Exports
2 |
3 | :::warning
4 | Single-file exports will replace your existing file **without** asking for confirmation. If you don't want this to happen, you must use [multi-file exports](multi-file.md).
5 | :::
6 |
7 | 
8 |
9 | The `Create full export note` menu exports an item's metadata and its Zotero notes as a single file.
10 | For that it uses the `Mdnotes Default Template`, which you should [edit](../../advanced/templates/single-file.md) by adding your desired metadata placeholders.
11 | Zotero notes included in this export will use the `Zotero Note Template`.
12 |
13 | The menus for `Export to markdown` and `Create standalone note` behave in the same way as in multi-file exports, and use their respective templates.
14 |
15 | :::info
16 | The file created with the `Create full export note` menu uses the `Mdnotes Default Template` and the prefix and suffix for `Mdnotes` file.
17 | :::
18 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/installation.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Installation
3 | sidebar_position: 1
4 | ---
5 |
6 | ## Requirements
7 |
8 | For zotero-mdnotes to work you'll need to install the following plugins.
9 |
10 | - [Zotfile](http://zotfile.com/)
11 | - [BetterBibtex](https://retorque.re/zotero-better-bibtex/)
12 |
13 | ## Installing `zotero-mdnotes`
14 |
15 | You can install the plugin in Zotero as described [here](https://www.zotero.org/support/plugins):
16 |
17 | > To install a plugin in Zotero, download its `.xpi` file to your computer. Then, in Zotero, click “Tools → Add-Ons”, then drag the `.xpi` for the plugin onto the Add-Ons window that opens
18 |
19 | You can grab the latest version of `mdnotes` [here](https://github.com/argenos/zotero-mdnotes/releases/latest).
20 |
21 | :::tip
22 | If you're using Firefox, make sure to right-click on the `xpi` file and use the `Save as` menu, otherwise Firefox will try to install the xpi as a plugin and will throw an error.
23 | :::
24 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/getting-started/update.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Updates
3 | sidebar_position: 4
4 | ---
5 |
6 | You can update `.xpi` package automatically through the Zotero app or manually update it.
7 |
8 | On the top menu bar click on `Tools` >> `AddOns`, and you'll arrive to the following page.
9 |
10 | 
11 |
12 | After clicking on `More`, you can configure automatic updates
13 |
14 | .
15 |
16 | ## Manually check for updates
17 |
18 | To manually check for updates, in the top-right corner click on the gear and select `Check for Updates`:
19 |
20 | 
21 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/attach-link-to-zotero.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/attach-link-to-zotero.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/config-editor.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/config-editor.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/dont-panic-md-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/dont-panic-md-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/dont-panic-zotero-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/dont-panic-zotero-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnote-update.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnote-update.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-addon-updates.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-addon-updates.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-batch.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-batch.gif
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-check-for-updates.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-check-for-updates.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-export-preferences-2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-export-preferences-2.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-export-preferences.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-export-preferences.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/mdnotes-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/mdnotes-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/multi-file-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/multi-file-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/notes-file.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/notes-file.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/single-file-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/single-file-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/yellow-md-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/yellow-md-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/yellow-zotero-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/yellow-zotero-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/images/zotero-item-export.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.1.3/images/zotero-item-export.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/limitations.md:
--------------------------------------------------------------------------------
1 | # Notes and Known Limitations
2 |
3 | - I assume the exported metadata and Zotero note files are _replaceable_.
4 |
5 | - **Why?** Items in your Zotero library may need to be updated or new annotations/highlights can be made to the PDF.
6 |
7 | - Batch export will overwrite the metadata and Zotero note files **without asking**.
8 |
9 | - The only file **not** overwritten during batch export is the Notes file which I assume **you** modify and don't want them overwritten! You can use the `Create Notes file` menu to do so.
10 |
11 | - The format used to export Zotero notes is somewhat hardcoded and relies on Zotfile's default format. [Let me know](https://github.com/argenos/zotero-mdnotes/issues/new) if this doesn't work for you.
12 |
13 | **v0.0.3** - Since forbidden characters for Windows file names can get quite complex, and I can't test in Windows nor invest much time in this, I've made a few assumptions about the title of your notes. If those assumptions are not met, the file with the extracted notes won't be created and batch export won't work. Check if your note:
14 |
15 | - uses anything other than the default Zotfile format, or if the note title contains more than one parenthesis this might fail
16 |
17 | - has any other special character in the first line (which is used as part of the file name), it will also fail. The only cases I'm checking are forward slashes `/` and colons `:`.
18 |
19 | Pull requests are welcome to handle this in a smarter way.
20 |
21 | - Zotero note exports reformat the date in the title:
22 |
23 | **v0.0.3:** Zotfile-extracted annotations include characters that are invalid for Windows file names. For that reason, the date is changed to follow an ISO format and stripping time, i.e. `yyyy-mm-dd`. This might not always work correctly depending on your time zone, and it might be better to fix it directly in Zotfile (see [this issue](https://github.com/jlegewie/zotfile/issues/480)).
24 |
25 | - If you move or rename your markdown files, the links in Zotero will be outdated. The only solution is to manually locate them.
26 |
27 | - I can only work on this on my spare time, so it might take me a while to fix your issue. That being said, I'll try to point you in the right direction if you [open an issue](https://github.com/argenos/zotero-mdnotes/issues/new). [Pull requests](https://github.com/argenos/zotero-mdnotes/pulls) are most definitely welcome if you can spare some time.
28 |
29 | - If you have questions, please use the Q&A category in [GitHub Discussions](https://github.com/argenos/zotero-mdnotes/discussions/new).
30 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.1.3/quick-start-guide.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 1
3 | ---
4 |
5 | # Quick-Start Guide
6 |
7 | This quick guide should get you started with `zotero-mdnotes`.
8 |
9 | ## Installation
10 |
11 | Download and [install](getting-started/installation.md) the latest version of the requirements and of `mdnotes`:
12 |
13 | - [Zotfile](http://zotfile.com/)
14 | - [BetterBibtex](https://retorque.re/zotero-better-bibtex/)
15 | - [Mdnotes](https://github.com/argenos/zotero-mdnotes/releases/latest).
16 |
17 | :::tip
18 | If you're using Firefox, make sure to right-click on the `xpi` file and use the `Save as` menu, otherwise Firefox will try to install the xpi as a plugin and will throw an error.
19 | :::
20 |
21 | ## Exporting content from Zotero as Markdown
22 |
23 | By default, `mdnotes` exports things on separate files, the rest of this guide assumes you have not customized your preferences just yet.
24 | You can change this later from the default `Split file` file organization to `Single file` in your [preferences](getting-started/configuration.md).
25 |
26 | ### Export a Zotero metadata or notes
27 |
28 | Right-click on the item or Zotero note (the yellow ones) you want to export, and select `Export to markdown`.
29 |
30 | :::tip
31 | If your item has multiple notes, you can select all of them and use the `Export to markdown` menu to create one file for each.
32 | :::
33 |
34 | ### Create a file for your own notes
35 |
36 | Select a Zotero item, right-click and select `Create mdnotes file` or `Create a standalone note`.
37 |
38 | ### Batch export all metadata and notes
39 |
40 | Selecting a Zotero item, and choosing the menu `Batch export to markdown` will create the markdown files for the metadata, export all Zotero notes and create a file for your own notes.
41 |
42 | ## Customizing your exports
43 |
44 | If exporting on multiple files is not your thing, or you want to change the way files are named, you can change some of those options in your [preferences](getting-started/configuration.md).
45 |
46 | ### Customize the content of your exports
47 |
48 | To change how the content of the exported files looks like, read more about [templates](advanced/templates/defaults.md) and [placeholders](advanced/placeholders.md).
49 |
50 | ### Customize the formatting of your content
51 |
52 | `Mdnotes` has some hidden preferences to add custom formatting, e.g. to only add links to collections, or export tags exactly as they look in Zotero. Check out the [formatting](advanced/formatting.md) page for more info.
53 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Advanced Configuration",
3 | "position": 3
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/formatting.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Custom Formatting
3 | sidebar_position: 3
4 | ---
5 |
6 | Starting with **v0.1.0** it's possible to specify custom formatting and to use templates.
7 |
8 | ## Internal links
9 |
10 | The internal link preference influences how file names and therefore how links look.
11 |
12 | - `[[wiki links]]` can contain spaces and maintain their case
13 | - `[Markdown links](markdown-links.md)` are all lower case and spaces are replaced with dashes.
14 |
15 | ## Zotero Note formatting
16 |
17 | Zotero Notes are formatted in HTML. The hidden preferences `extensions.mdnotes.html2.md` configures the [Joplin turndown](https://github.com/laurent22/joplin-turndown) styles and additional rules.
18 |
19 | To keep some of the elements used in Zotfile's PDF extraction, `` and `` tags are currently kept unmodified when translated to Markdown.
20 |
21 | :::note Migration from v0.1.3 to v0.2.0
22 |
23 | The old dictionary on the `extensions.mdnotes.html_to_md` is no longer supported. If you need additional rules not included in the new `html2md` preferences, please open an issue.
24 |
25 | :::
26 |
27 | ## Placeholders
28 |
29 | With a few exceptions, you can format any placeholder by adding (or modifying) them in the settings. You can reach the hidden preferences menu from `Edit > Preferences > Advanced > Config Editor`. You can use the search to find existing configurations:
30 |
31 | 
32 |
33 | ### Default formatting
34 |
35 | #### Placeholder format
36 |
37 | By default, placeholder contents are replaced with:
38 |
39 | ```markdown
40 | {{bullet}} {{field_name}}: {{field_contents}}
41 | ```
42 |
43 | Where:
44 |
45 | - `{{bullet}}` - Defined in `extensions.mdnotes.bullet`
46 | - `{{field_name}}` - The name of the field transformed from camel case into sentence case.
47 | - `{{field_contents}}` - The contents of the field as described below.
48 |
49 | #### Field format
50 |
51 | Any placeholder that doesn't have their formatting defined in the hidden preferences has the following defaults:
52 |
53 | - `link_style`: As defined by the preference of [Internal links](#internal-links). Valid values include `wiki`, `markdown` and `no-links`.
54 | - `list_separator`: For fields that contain more than one value, the default is `, `.
55 | - `text_case`: How to capitalize the contents of the field: `title`, `sentence`, `lower` or `upper` case. The default will return the field content in its original case.
56 | - `remove_spaces`: If this is set to `true` spaces will be replaced with dashes.
57 |
58 | ### Adding new formatting rules
59 |
60 | If you want to add custom formatting for any field not currently there, you can add the format for a placeholder with right-click and `New > String`.
61 |
62 | #### Preference name
63 |
64 | The preference name should be `extensions.mdnotes.placeholder.`, where `yourFieldHere` should match a [supported Zotero field](https://www.zotero.org/support/kb/item_types_and_fields). Keep in mind that Zotero fields are usually accessed using camel case, and should be (usually) formatted as `fieldName`, e.g. `seriesTitle`.
65 |
66 | #### Preference value
67 |
68 | The value of the preference should be enclosed in braces, and defined as key/value pairs, e.g `{"key": "value"}`.
69 |
70 | In addition to the fields described in the [default field format](#field-format), the following options can be specified:
71 |
72 | - `content` - Formatting the placeholder's content ([default placeholder format](#placeholder-format))
73 | - `field_contents` - Formatting the field itself, which defaults to `{{content}}`
74 |
75 | ### Examples
76 |
77 | Replacing the field label with custom text and changing the list separator to make a list:
78 |
79 | ```markdown
80 | {"content":"{{bullet}} PDF Attachments\n\t- {{field_contents}}", "field_contents": "{{content}}", "list_separator": "\n\t- "}
81 | ```
82 |
83 | Making the tags placeholder remove spaces and adding a hash sign before each tag:
84 |
85 | ```markdown
86 | {"content":"{{bullet}} Tags: {{field_contents}}", "field_contents": "#{{content}}", "link_style": "no-links", "list_separator": ", ", "remove_spaces": "true"}
87 | ```
88 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/hidden-prefs.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Hidden Preferences
3 | ---
4 |
5 | In addition to the ability to add [custom placeholders](placeholders.md#custom-placeholders) and [customize placeholder formatting](formatting.md#placeholders), there are a few hidden preferences for editor-specific syntax.
6 |
7 | ## Obsidian
8 |
9 | A few preferences to use exported files with [Obsidian](https://obsidian.md/) are described below.
10 |
11 | ### Block IDs
12 |
13 | Setting `extensions.mdnotes.obsidian.blocks` to true will append a block ID to all non-header text blocks of exported Zotero notes, i.e. to each highlight and annotation extracted by Zotfile.
14 |
15 | :::info
16 |
17 | The block ID is using a hash of the block contents, i.e. if you change your format the block won't match any more. I know this is brittle, and I'm not entirely happy with it, so I'm open to suggestions if you have a better idea to make the exported blocks reusable.
18 |
19 | :::
20 |
21 | ### Obsidian URI
22 |
23 | Setting `extensions.mdnotes.obsidian.attach_obsidian_uri` to true will add a link to the Obsidian notes as an attachment to their items, just like with [attach linked file](../getting-started/configuration.md#add-the-created-files-as-linked-files-to-zotero) preference.
24 |
25 | You must specify your vault name in `extensions.mdnotes.obsidian.vault`. The Obsidian link is then `obsidian://open?vault=&file=`.
26 |
27 | :::note
28 | This assumes you are using `Shortest path` for your link format so all file names are unique.
29 | :::
30 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/placeholders.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Placeholders and wildcards
3 | sidebar_position: 2
4 | ---
5 |
6 | There are both placeholders (e.g. `{{citekey}}`) and wildcards (e.g. `%(citekey)` for all fields.
7 |
8 | So when should you use them on your templates?
9 |
10 | - `{{placeholders}}` are a quick way to get `- : ` and allows you to apply some formatting.
11 | - `%(wildcards)%` are the raw contents of that field.
12 |
13 | Another important distinction is that `{{placeholders}}` are removed from your template if the item you're exporting doesn't have them, while `%(wildcards)` will be left there, and therefore should be used sparingly for things you know all items will have, e.g. title, authors, citekey, etc.
14 |
15 | ## Placeholders
16 |
17 | ### Item placeholders
18 |
19 | You can add a `{{placeholder}}` for any [item field](https://www.zotero.org/support/kb/item_types_and_fields) in your templates. Fields are formatted in camel case, so make sure you find the right [field](https://api.zotero.org/itemFields?pprint=1) in Zotero's API.
20 |
21 | During export, any placeholder that is not a match for the selected item or that is blank will not be included in the markdown file.
22 |
23 | In addition to Zotero's supported fields, Mdnotes adds a few placeholders for an item:
24 |
25 | - `{{itemType}}` - The Zotero item type.
26 | - `{{citekey}}` - The citekey (requires the Better Bibtex plugin).
27 | - `{{collections}}` - A list of collections an item belongs to.
28 | - `{{related}}` - A list of [related items](https://www.zotero.org/support/related).
29 | - `{{tags}}` - The list of tags for the selected item.
30 | - `{{pdfAttachments}}` = A list of links to any PDF attachments.
31 | - `{{localLibrary}}` = The `zotero://` link to an item.
32 | - `{{cloudLibrary}}` = If you use [Zotero sync](https://www.zotero.org/support/sync), the link to that item in your cloud library.
33 | - `{{dateAdded}}` - The date the item was added to your library.
34 | - `{{notes}}` - A list of all the titles of all the child notes.
35 | - `{{mdnotesFileName}}` - The name of the default mdnotes file (following the naming convention).
36 | - `{{metadataFileName}}` - The name of the Zotero metadata file (following the naming convention).
37 |
38 | #### Adding a new placeholder
39 |
40 | After setting up your templates, adding a new placeholder is as simple as adding the placeholder in the template you for your exports. For example, adding `{{publicationTitle}}` to your template will include the correct field for journals.
41 |
42 | ```markdown {2} title="Zotero Metadata Template.md"
43 | {{proceedingsTitle}}
44 | {{publicationTitle}}
45 | {{date}}
46 | ```
47 |
48 | The placeholder will use the [default](formatting.md#placeholder-format) formatting, unless you add a [new formatting rule](formatting.md#adding-new-formatting-rules).
49 |
50 | ### Note placeholders
51 |
52 | Mdnotes supports the following placeholders for Zotero notes:
53 |
54 | - `{{mdnotesFileName}}` - The filename for the [mdnotes file](../getting-started/configuration.md#file-naming-convention) according to the file naming convention.
55 | - `{{metadataFileName}}` - The filename for a [Zotero Item export](../getting-started/configuration.md#file-naming-convention) according to the file naming convention.
56 | - `{{noteTitle}}` - The note's title (usually the first line).
57 | - `{{noteContent}}` - The contents of the note, translated to markdown as defined in the [preferences](./formatting.md#zotero-note-formatting)
58 | - `{{related}}` - A list of [related items](https://www.zotero.org/support/related).
59 | - `{{tags}}` - The list of tags for the selected note.
60 |
61 | ### Custom placeholders
62 |
63 | Much like [adding new field placeholders](#adding-a-new-placeholder), it is possible to add custom placeholders. For this you'll need to add [new formatting rules](formatting.md#adding-new-formatting-rules). There are two main types of custom placeholders depending on their contents:
64 |
65 | - those that get their content from a Zotero field, in which case you need to define which field to get the contents from: `zotero_field: `.
66 | :::tip
67 | To define an additional placeholder that formats the authors as a list, named `{{authorList}}`, you should add a preference with the following:
68 |
69 | **Name**:
70 |
71 | ```txt
72 | extensions.mdnotes.placeholder.authorList
73 | ```
74 |
75 | **Value**:
76 |
77 | ```txt
78 | {"content":"List of Authors:\n\t- {{field_contents}}", "zotero_field":"author", "list_separator": "\n\t- ",}
79 | ```
80 |
81 | Note that your template can use both the default field placeholder `{{author}}` and your custom placeholder `{{authorList}}`.
82 |
83 | :::
84 |
85 | - those that have pre-defined contents, which need a `custom_content: ` definition
86 | :::tip
87 | To define a custom placeholder for `{{Earth}}`, you should add a preference with the following:
88 |
89 | **Name**:
90 |
91 | ```txt
92 | extensions.mdnotes.placeholder.Earth
93 | ```
94 |
95 | **Value**:
96 |
97 | ```txt
98 | {"custom_content":"Mostly harmless"}
99 | ```
100 |
101 | :::
102 |
103 | When specifying custom placeholders, the preference name shouldn't match a Zotero field.
104 |
105 | ## Wildcards
106 |
107 | A `%(wildcard)` uses the same logic as the placeholder, but only includes the content of a Zotero field without any formatting. Keep in mind that any fields not included in a Zotero item will not be deleted from your file.
108 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/templates/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Templates",
3 | "position": 1
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/templates/defaults.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Default Templates
3 | sidebar_position: 1
4 | ---
5 |
6 | Templates define how the final Markdown document will look like. Starting on [v0.1.0](/changelog#v010---2020-11-15) you can specify a templates directory in the `Tools > Mdnote preferences`.
7 | Once a directory is specified, `Mdnotes` will look for the following files (they must be named **exactly** like this):
8 |
9 | ```txt
10 | .
11 | ├── Mdnotes Default Template.md
12 | ├── Standalone Note Template.md
13 | ├── Zotero Metadata Template.md
14 | └── Zotero Note Template.md
15 |
16 | ```
17 |
18 | The files must be located at the root of the folder you chose. For now, hidden folders (those whose name starts with `.`) are not supported.
19 | If there is no path specified or the file doesn't exist, Mdnotes will use the default templates.
20 |
21 | The default templates can give you an idea of existing [placeholders and wildcards](../placeholders.md)
22 |
23 | ## Export to markdown
24 |
25 | `Export to markdown` will export whatever you have selected. It uses the [zotero metadata template](#zotero-metadata-template), if you have selected an item, and the [zotero note template](#zotero-note-template) if there are notes in your selected items.
26 |
27 | ### Zotero Metadata Template
28 |
29 | - **Which menu?**: `Export to markdown`
30 | - **What to select?**: A Zotero item.
31 |
32 | You can add (or remove) any [item placeholder](../placeholders.md#item-placeholders) to your template.
33 |
34 | ```markdown title="Zotero Metadata Template.md"
35 | {{title}}
36 |
37 | ## Metadata
38 |
39 | {{itemType}}
40 | {{author}}
41 | {{proceedingsTitle}}
42 | {{date}}
43 | {{dateAdded}}
44 | {{url}}
45 | {{DOI}}
46 | {{citekey}}
47 | {{collections}}
48 | {{related}}
49 | {{tags}}, #zotero, #literature-notes, #reference
50 | {{pdfAttachments}}
51 |
52 | {{abstractNote}}
53 |
54 | ## Zotero links
55 |
56 | {{localLibrary}}
57 | {{cloudLibrary}}
58 |
59 | {{notes}}
60 | ```
61 |
62 | ### Zotero Note Template
63 |
64 | - **Which menu?**: `Export to markdown`
65 | - **What to select?**: A Zotero note.
66 |
67 | You can add (or remove) any [note placeholders](../placeholders.md#note-placeholders) to your template.
68 |
69 | ```markdown title="Zotero Note Template.md"
70 | {{tags}}
71 | {{related}}
72 | {{mdnotesFileName}}
73 |
74 | {{title}}
75 |
76 | {{noteContent}}
77 | ```
78 |
79 | ## Creating files for your notes
80 |
81 | ### Mdnotes Default Template
82 |
83 | This template supports any [item placeholder](../placeholders.md#item-placeholders), which you can add (or remove) from your template.
84 | Read more about the specifics for [single-file](single-file.md) and [multi-file](multi-file.md) exports.
85 |
86 | ```markdown title="Mdnotes Default Template.md"
87 | {{title}}
88 |
89 | ![[%(metadataFileName)#Metadata]]
90 |
91 | Other files:
92 | {{mdnotesFileName}}
93 | {{metadataFileName}}
94 |
95 | ## Zotero links
96 |
97 | {{localLibrary}}
98 | {{cloudLibrary}}
99 |
100 | ## Notes
101 |
102 | -
103 | ```
104 |
105 | ### Standalone Note Template
106 |
107 | - **Which menu?**: `Create a standalone note`.
108 | - **What to select?**: A Zotero item.
109 |
110 | It is essentially a duplicate of the [mdnotes default template](#mdnotes-default-template).
111 | Its purpose is to provide a secondary template that can be used to add notes with _some_ metadata and automatically adding links to Zotero.
112 |
113 | :::info
114 | **Note**: Standalone notes must be activated in the `Mdnotes Preferences`.
115 | :::
116 |
117 | ```markdown title="Standalone Default Template.md"
118 | Related to: [[%(metadataFileName)]]
119 |
120 | ## Notes
121 |
122 | -
123 | ```
124 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/templates/multi-file.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Multi-File Templates
3 | sidebar_position: 2
4 | ---
5 |
6 | Multi-file exports match 1:1 the [default templates](defaults.md).
7 | You can read more about [item](../placeholders.md#item-placeholders) and [note](../placeholders.md#note-placeholders) placeholders in the next section.
8 |
9 | ### Mdnotes Default Template
10 |
11 | - **Which menu?**: `Create mdnotes file`
12 | - **What to select?**: A Zotero item.
13 |
14 | 
15 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/advanced/templates/single-file.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Single-File Templates
3 | sidebar_position: 3
4 | ---
5 |
6 | Single-file exports might require a few changes to the default configuration, depending on your needs, as described in the [single-file configuration](../../getting-started/file-organization/single-file.md).
7 | You can read more about [item](../placeholders.md#item-placeholders) and [note](../placeholders.md#note-placeholders) placeholders in the next section.
8 |
9 | ## Templates used in single-file exports
10 |
11 | - **Which menu?**: `Create full export note`
12 | - **What to select?**: A Zotero item.
13 |
14 | 
15 |
16 | ### Mdnotes Default Template
17 |
18 | For example, you might want to update the template to include an item's metadata:
19 |
20 | ```markdown
21 | {{title}}
22 |
23 | ## Zotero links
24 |
25 | {{localLibrary}}
26 | {{cloudLibrary}}
27 |
28 | ## Metadata
29 |
30 | {{itemType}}
31 | {{author}}
32 | {{proceedingsTitle}}
33 | {{date}}
34 | {{dateAdded}}
35 | {{url}}
36 | {{DOI}}
37 | {{citekey}}
38 | {{collections}}
39 | {{related}}
40 | {{tags}}, #zotero, #literature-notes, #reference
41 | {{pdfAttachments}}
42 |
43 | {{abstractNote}}
44 |
45 | {{notes}}
46 |
47 | ## My notes
48 |
49 | -
50 | ```
51 |
52 | ### Zotero Note Template
53 |
54 | If you include the `{{notes}}` placeholder in the `Mdnotes Default Template`, `mdnotes` will loop through the Zotero Notes of the selected items and add them one by one using this template.
55 |
56 | For single-file exports, you might want to edit your template to look like this:
57 |
58 | ```markdown
59 | {{tags}}
60 | {{related}}
61 |
62 | {{noteTitle}}
63 |
64 | {{noteContent}}
65 | ```
66 |
67 | :::info
68 | This template is also used by the `Export to markdown` menu when you select a Zotero note. If you ever want to export, the changes you make will affect both menus.
69 | :::
70 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "Getting Started",
3 | "position": 2
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/configuration.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Configuration
3 | sidebar_position: 2
4 | ---
5 |
6 | To access `mdnotes` preferences, go to `Tools > Mdnotes preferences`
7 |
8 | ## Export preferences
9 |
10 | 
11 |
12 | ### Setting the starting path
13 |
14 | In `Tools > Mdnotes preferences` you can choose the path `mdnotes` will open with any of its menus. The path you select is just the starting point, before saving your files you can navigate to any other directory.
15 |
16 | ### File Organization
17 |
18 | You can choose to export your content as a [single file](file-organization/single-file.md) or [multiple files](file-organization/multi-file.md), and will be reflected on the right-click menu.
19 | Which configuration to choose depends on your preferences, and on your Zotfile configuration, the figure below illustrates a few of the possibilities based on the default templates:
20 |
21 | - [Multi-file](file-organization/multi-file.md) exports create separate files: one for your notes (blue), one with the item metadata (green) and one for each note (yellow).
22 | - [Single-file](file-organization/single-file.md) exports add all your content on a single file.
23 |
24 | 
25 |
26 | ### Template directory
27 |
28 | [Templates](../advanced/templates/defaults.md) define how the final Markdown document will look like. Starting on [v0.1.0](/changelog#v010---2020-11-15) you can specify a templates directory in the `Tools > Mdnotes preferences`.
29 |
30 | Depending on your choice of [file organization](#file-organization), you'll need to edit different templates.
31 |
32 | ### Add the created files as linked files to Zotero
33 |
34 | If you select the "Attach file links to Zotero", the markdown files will be added as [linked files](https://www.zotero.org/support/attaching_files#stored_files_and_linked_files), meaning you can access them by double-clicking on them from inside Zotero:
35 |
36 | 
37 |
38 | ## File naming convention
39 |
40 | In general, I recommend using the `citekey` as title. The exported files will use the prefix and suffix for the type of file being exported, following the pattern `.md`.
41 |
42 | 
43 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/file-organization/_category_.json:
--------------------------------------------------------------------------------
1 | {
2 | "label": "File Organization",
3 | "position": 3
4 | }
5 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/file-organization/mdnotes-file-config.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/getting-started/file-organization/mdnotes-file-config.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/file-organization/multi-file.md:
--------------------------------------------------------------------------------
1 | # Multi-file Exports (Default)
2 |
3 | 
4 |
5 | Using the `Split files` option will create, as its name indicates, separate files for your metadata, Zotero notes, or your own notes. Whenever you use the `Export to markdown` menu:
6 |
7 | - One file containing the metadata will be created if you selected a Zotero item using the [`Zotero Metadata Template`](../../advanced/templates/defaults.md#zotero-metadata-template).
8 | - If you select a Zotero note, one file will be created using the [`Zotero Note Template`](../../advanced/templates/defaults.md#zotero-note-template)
9 |
10 | Using the `Create Mdnotes file` will create a note for **your** notes using the [`Mdnotes Default Template`](../../advanced/templates/defaults.md#mdnotes-default-template).
11 |
12 | By selecting a Zotero item and using the `Batch export to markdown` menu, `mdnotes` will create all the above files, i.e. one for the metadata and one for each Zotero note in that item.
13 | If your `Mdnotes` file doesn't exist, it will be created.
14 |
15 | :::info
16 | Your `Mdnotes` file will never be overwritten with the `Batch export` menu. If you wish to do so, you must use the `Create Mdnotes file` and confirm you want to overwrite it.
17 | :::
18 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/file-organization/single-file.md:
--------------------------------------------------------------------------------
1 | # Single-file Exports
2 |
3 | :::caution
4 | Single-file exports will replace your existing file **without** asking for confirmation. If you don't want this to happen, you must use [multi-file exports](multi-file.md).
5 | :::
6 |
7 | 
8 |
9 | The `Create full export note` menu exports an item's metadata and its Zotero notes as a single file.
10 | For that it uses the `Mdnotes Default Template`, which you should [edit](../../advanced/templates/single-file.md) by adding your desired metadata placeholders.
11 | Zotero notes included in this export will use the `Zotero Note Template`.
12 |
13 | The menus for `Export to markdown` and `Create standalone note` behave in the same way as in multi-file exports, and use their respective templates.
14 |
15 | :::info
16 | The file created with the `Create full export note` menu uses the `Mdnotes Default Template` and the prefix and suffix for `Mdnotes` file.
17 | :::
18 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/installation.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Installation
3 | sidebar_position: 1
4 | ---
5 |
6 | ## Requirements
7 |
8 | For zotero-mdnotes to work you'll need to install the following plugins.
9 |
10 | - [Zotfile](http://zotfile.com/)
11 | - [BetterBibtex](https://retorque.re/zotero-better-bibtex/)
12 |
13 | ## Installing `zotero-mdnotes`
14 |
15 | You can install the plugin in Zotero as described [here](https://www.zotero.org/support/plugins):
16 |
17 | > To install a plugin in Zotero, download its `.xpi` file to your computer. Then, in Zotero, click “Tools → Add-Ons”, then drag the `.xpi` for the plugin onto the Add-Ons window that opens
18 |
19 | You can grab the latest version of `mdnotes` [here](https://github.com/argenos/zotero-mdnotes/releases/latest).
20 |
21 | :::tip
22 | If you're using Firefox, make sure to right-click on the `xpi` file and use the `Save as` menu, otherwise Firefox will try to install the xpi as a plugin and will throw an error.
23 | :::
24 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/getting-started/update.md:
--------------------------------------------------------------------------------
1 | ---
2 | title: Updates
3 | sidebar_position: 4
4 | ---
5 |
6 | You can update `.xpi` package automatically through the Zotero app or manually update it.
7 |
8 | On the top menu bar click on `Tools` >> `AddOns`, and you'll arrive to the following page.
9 |
10 | 
11 |
12 | After clicking on `More`, you can configure automatic updates
13 |
14 | .
15 |
16 | ## Manually check for updates
17 |
18 | To manually check for updates, in the top-right corner click on the gear and select `Check for Updates`:
19 |
20 | 
21 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/attach-link-to-zotero.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/attach-link-to-zotero.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/config-editor.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/config-editor.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/dont-panic-md-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/dont-panic-md-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/dont-panic-zotero-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/dont-panic-zotero-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnote-update.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnote-update.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-addon-updates.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-addon-updates.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-batch.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-batch.gif
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-check-for-updates.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-check-for-updates.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-export-preferences-2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-export-preferences-2.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-export-preferences.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-export-preferences.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/mdnotes-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/mdnotes-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/multi-file-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/multi-file-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/notes-file.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/notes-file.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/single-file-menu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/single-file-menu.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/yellow-md-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/yellow-md-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/yellow-zotero-note.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/yellow-zotero-note.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/images/zotero-item-export.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/docs/versioned_docs/version-0.2.0/images/zotero-item-export.png
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/limitations.md:
--------------------------------------------------------------------------------
1 | # Notes and Known Limitations
2 |
3 | - I assume the exported metadata and Zotero note files are _replaceable_.
4 |
5 | - **Why?** Items in your Zotero library may need to be updated or new annotations/highlights can be made to the PDF.
6 |
7 | - Batch export will overwrite the metadata and Zotero note files **without asking**.
8 |
9 | - The only file **not** overwritten during batch export is the Notes file which I assume **you** modify and don't want them overwritten! You can use the `Create Notes file` menu to do so.
10 |
11 | - The format used to export Zotero notes is somewhat hardcoded and relies on Zotfile's default format. [Let me know](https://github.com/argenos/zotero-mdnotes/issues/new) if this doesn't work for you.
12 |
13 | **v0.0.3** - Since forbidden characters for Windows file names can get quite complex, and I can't test in Windows nor invest much time in this, I've made a few assumptions about the title of your notes. If those assumptions are not met, the file with the extracted notes won't be created and batch export won't work. Check if your note:
14 |
15 | - uses anything other than the default Zotfile format, or if the note title contains more than one parenthesis this might fail
16 |
17 | - has any other special character in the first line (which is used as part of the file name), it will also fail. The only cases I'm checking are forward slashes `/` and colons `:`.
18 |
19 | Pull requests are welcome to handle this in a smarter way.
20 |
21 | - Zotero note exports reformat the date in the title:
22 |
23 | **v0.0.3:** Zotfile-extracted annotations include characters that are invalid for Windows file names. For that reason, the date is changed to follow an ISO format and stripping time, i.e. `yyyy-mm-dd`. This might not always work correctly depending on your time zone, and it might be better to fix it directly in Zotfile (see [this issue](https://github.com/jlegewie/zotfile/issues/480)).
24 |
25 | - If you move or rename your markdown files, the links in Zotero will be outdated. The only solution is to manually locate them.
26 |
27 | - I can only work on this on my spare time, so it might take me a while to fix your issue. That being said, I'll try to point you in the right direction if you [open an issue](https://github.com/argenos/zotero-mdnotes/issues/new). [Pull requests](https://github.com/argenos/zotero-mdnotes/pulls) are most definitely welcome if you can spare some time.
28 |
29 | - If you have questions, please use the Q&A category in [GitHub Discussions](https://github.com/argenos/zotero-mdnotes/discussions/new).
30 |
--------------------------------------------------------------------------------
/docs/versioned_docs/version-0.2.0/quick-start-guide.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebar_position: 1
3 | ---
4 |
5 | # Quick-Start Guide
6 |
7 | This quick guide should get you started with `zotero-mdnotes`.
8 |
9 | ## Installation
10 |
11 | Download and [install](getting-started/installation.md) the latest version of the requirements and of `mdnotes`:
12 |
13 | - [Zotfile](http://zotfile.com/)
14 | - [BetterBibtex](https://retorque.re/zotero-better-bibtex/)
15 | - [Mdnotes](https://github.com/argenos/zotero-mdnotes/releases/latest).
16 |
17 | :::tip
18 | If you're using Firefox, make sure to right-click on the `xpi` file and use the `Save as` menu, otherwise Firefox will try to install the xpi as a plugin and will throw an error.
19 | :::
20 |
21 | ## Exporting content from Zotero as Markdown
22 |
23 | By default, `mdnotes` exports things on separate files, the rest of this guide assumes you have not customized your preferences just yet.
24 | You can change this later from the default `Split file` file organization to `Single file` in your [preferences](getting-started/configuration.md).
25 |
26 | ### Export a Zotero metadata or notes
27 |
28 | Right-click on the item or Zotero note (the yellow ones) you want to export, and select `Export to markdown`.
29 |
30 | :::tip
31 | If your item has multiple notes, you can select all of them and use the `Export to markdown` menu to create one file for each.
32 | :::
33 |
34 | ### Create a file for your own notes
35 |
36 | Select a Zotero item, right-click and select `Create mdnotes file` or `Create a standalone note`.
37 |
38 | ### Batch export all metadata and notes
39 |
40 | Selecting a Zotero item, and choosing the menu `Batch export to markdown` will create the markdown files for the metadata, export all Zotero notes and create a file for your own notes.
41 |
42 | ## Customizing your exports
43 |
44 | If exporting on multiple files is not your thing, or you want to change the way files are named, you can change some of those options in your [preferences](getting-started/configuration.md).
45 |
46 | ### Customize the content of your exports
47 |
48 | To change how the content of the exported files looks like, read more about [templates](advanced/templates/defaults.md) and [placeholders](advanced/placeholders.md).
49 |
50 | ### Customize the formatting of your content
51 |
52 | `Mdnotes` has some hidden preferences to add custom formatting, e.g. to only add links to collections, or export tags exactly as they look in Zotero. Check out the [formatting](advanced/formatting.md) page for more info.
53 |
--------------------------------------------------------------------------------
/docs/versioned_sidebars/version-0.1.3-sidebars.json:
--------------------------------------------------------------------------------
1 | {
2 | "version-0.1.3/tutorialSidebar": [
3 | {
4 | "type": "autogenerated",
5 | "dirName": "."
6 | }
7 | ]
8 | }
9 |
--------------------------------------------------------------------------------
/docs/versioned_sidebars/version-0.2.0-sidebars.json:
--------------------------------------------------------------------------------
1 | {
2 | "tutorialSidebar": [
3 | {
4 | "type": "autogenerated",
5 | "dirName": "."
6 | }
7 | ]
8 | }
9 |
--------------------------------------------------------------------------------
/docs/versions.json:
--------------------------------------------------------------------------------
1 | [
2 | "0.2.0",
3 | "0.1.3"
4 | ]
5 |
--------------------------------------------------------------------------------
/install.rdf:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 | Mdnotes for Zotero
5 | Export Zotero items and notes to markdown
6 | mdnotes@mdnotes.github.io
7 | 0.2.3
8 | https://github.com/argenos/zotero-mdnotes
9 | A. Ortega
10 | https://raw.githubusercontent.com/argenos/zotero-mdnotes/master/update.rdf
11 | 2
12 |
13 |
14 | zotero@chnm.gmu.edu
15 | 5.0.79
16 | 6.*
17 |
18 |
19 | juris-m@juris-m.github.io
20 | 5.0.79
21 | 6.*
22 |
23 |
24 |
25 |
--------------------------------------------------------------------------------
/locale/en-US/mdnotes.dtd:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
--------------------------------------------------------------------------------
/locale/zh-CN/mdnotes.dtd:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
--------------------------------------------------------------------------------
/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "scripts": {
3 | "build": "webpack"
4 | },
5 | "dependencies": {
6 | "buffer": "^6.0.3",
7 | "joplin-turndown": "^4.0.30",
8 | "path-browserify": "^1.0.1",
9 | "sha.js": "^2.4.11"
10 | },
11 | "devDependencies": {
12 | "webpack": "^5.4.0",
13 | "webpack-cli": "^4.2.0"
14 | }
15 | }
16 |
--------------------------------------------------------------------------------
/skin/default/overlay.css:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/argenos/zotero-mdnotes/3f5d1cb2b18fae43e30f34c626136b0af9bb22e8/skin/default/overlay.css
--------------------------------------------------------------------------------
/src/markdown-utils.js:
--------------------------------------------------------------------------------
1 | const css = require('css');
2 | var shajs = require('sha.js')
3 | const Turndown = require('joplin-turndown').default
4 |
5 | function hasStyle(node, property, value) {
6 | // From https://github.com/laurent22/joplin-turndown/blob/master/src/commonmark-rules.js#L150
7 | if (!node.nodeName =='SPAN') return false;
8 |
9 | const style = node.getAttribute('style');
10 | if (!style) return false;
11 |
12 | const o = css.parse('pre {' + style + '}');
13 | if (!o.stylesheet.rules.length) return;
14 |
15 | const textDecoration = o.stylesheet.rules[0].declarations.find(d => d.property.toLowerCase() === property);
16 | if (!textDecoration || !textDecoration.value) return false;
17 |
18 | const underlined = textDecoration.value.split(',').map(e => e.trim().toLowerCase()).indexOf(value) >= 0;
19 | return underlined;
20 |
21 | }
22 |
23 |
24 | function getConverter(){
25 | // Create a single Turndown provider which we'll use for all exporting. This
26 | // instance will be generated during Zotero load and will be kept in memory for
27 | // as long as the app is running.
28 | const converter = new Turndown({
29 | headingStyle: 'atx',
30 | hr: '---',
31 | bulletListMarker: Zotero.Prefs.get('extensions.mdnotes.html2md.default.bullet', true),
32 | strongDelimiter: Zotero.Prefs.get('extensions.mdnotes.html2md.default.strong', true),
33 | emDelimiter: Zotero.Prefs.get('extensions.mdnotes.html2md.default.em', true)
34 | })
35 |
36 | converter.addRule('p', {
37 | filter: 'p',
38 | replacement: function (content) {
39 | return '\n\n' + content + '\n\n'
40 | },
41 | escapeContent: function() {
42 | return false;
43 | },
44 | })
45 |
46 | converter.addRule('emphasis', {
47 | filter: ['em', 'i'],
48 |
49 | replacement: function (content, node, options) {
50 | if (!content.trim()) return ''
51 | return options.emDelimiter + content + options.emDelimiter
52 | },
53 | escapeContent: function() {
54 | return false;
55 | },
56 | })
57 |
58 | converter.addRule('strong', {
59 | filter: ['strong', 'b'],
60 |
61 | replacement: function (content, node, options) {
62 | if (!content.trim()) return ''
63 | return options.strongDelimiter + content + options.strongDelimiter
64 | },
65 | escapeContent: function() {
66 | return false;
67 | },
68 | })
69 |
70 | converter.keep(['span', 'font'])
71 |
72 | converter.addRule('strikethrough', {
73 | // filter: ['del', 's', 'strike'],
74 | filter: function (node) {
75 | return hasStyle(node, 'text-decoration', 'line-through') || node.nodeName === 'S' || node.nodeName === 'DEL' || node.nodeName === 'STRIKE';
76 | },
77 | replacement: function (content) {
78 | let delimiter = Zotero.Prefs.get("extensions.mdnotes.html2md.default.strikethrough", true);
79 | return delimiter + content + delimiter;
80 | }
81 | })
82 |
83 | converter.addRule('underline', {
84 | // filter: 'u',
85 | filter: function (node) {
86 | return hasStyle(node, 'text-decoration', 'underline') || node.nodeName === 'U';
87 | },
88 | replacement: function(content) {
89 | let open = Zotero.Prefs.get(`extensions.mdnotes.html2md.rules.underline.open`, true);
90 | let close = Zotero.Prefs.get(`extensions.mdnotes.html2md.rules.underline.close`, true);
91 | return open + content + close;
92 | }
93 | })
94 |
95 | return converter;
96 | }
97 |
98 | // Attach all utility functions to the Zotero.MarkdownUtils object. Any file
99 | // that has access to the Zotero object can then use it.
100 | Zotero.MarkdownUtils = new function () {
101 | /**
102 | * Converts a HTML string to Markdown
103 | *
104 | * @param {string} html The HTML to convert
105 | *
106 | * @return {string} The Markdown result
107 | */
108 | this.html2md = function (html) {
109 | const converter = getConverter();
110 | return converter.turndown(html)
111 | }
112 |
113 | /**
114 | * Extracts a possible title from the given Markdown. Attempts to use a h1,
115 | * but falls back to simply the first non-empty line.
116 | *
117 | * @param {string} md The Markdown
118 | *
119 | * @return {string} The extracted title
120 | */
121 | this.extractTitle = function (md) {
122 | const lines = md.split('\n')
123 |
124 | // First, attempt to extract the first heading level 1
125 | for (let line of lines) {
126 | if (/^#\s/.test(line)) {
127 | return line.substr(2) // Remove the "# " from the beginning
128 | }
129 | }
130 |
131 | // No heading level 1, so let's use the first paragraph
132 | for (let i = 0; i < lines.length; i++) {
133 | let candidate = lines[i].trim()
134 |
135 | if (candidate === '') {
136 | continue // Empty line
137 | }
138 |
139 | // We got a non-empty line. We need to strip some Markdown from it. I
140 | // guess right now removing bolds and italics suffices here, because the
141 | // main cause right now is to retrieve the
142 | // **Extracted Annotations (date)** - paragraph from it.
143 | // However, feel free to amend this to actually get to a plain text
144 | // version of that first paragraph.
145 | candidate = candidate.replace(/\*\*(.*)\*\*/g, '$1')
146 | candidate = candidate.replace(/\*(.*)\*/g, '$1')
147 | candidate = candidate.replace(/__(.*)__/g, '$1')
148 | candidate = candidate.replace(/_(.*)_/g, '$1')
149 |
150 | return candidate
151 | }
152 |
153 | // Return an empty string as fallback. TODO: Add handling in mdnotes.js!
154 | return ''
155 | }
156 |
157 | /**
158 | * Append Obsidian-style block IDs at the end of each block
159 | * @param {string} md Markdown string
160 | */
161 | this.addBlockIds = function (md, citekey) {
162 | const lines = md.split('\n')
163 | let new_md = "";
164 |
165 | // Loop through the file
166 | for (let line of lines) {
167 | let blockId = this.generateBlockId(line, citekey);
168 |
169 | if (line.startsWith('#') || /^\s*$/gm.test(line)){
170 | new_md += `${line}\n`;
171 | } else {
172 | new_md += `${line} ^${blockId}\n`;
173 | }
174 |
175 | }
176 |
177 | return new_md;
178 | }
179 |
180 | this.generateBlockId = function (str, citekey) {
181 | let ck = citekey ? citekey + "-" : "";
182 | let hash = shajs('sha256').update(str).digest('hex').substr(0, 7);
183 | return `${ck}${hash}`
184 | }
185 |
186 | }
187 |
--------------------------------------------------------------------------------
/update.rdf:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | 0.1.3
9 |
10 |
11 | zotero@chnm.gmu.edu
12 | 5.0.79
13 | 6.0.*
14 | https://github.com/argenos/zotero-mdnotes/releases/download/0.1.3/mdnotes-0.1.3.xpi
15 |
16 |
17 |
18 |
19 | juris-m@juris-m.github.io
20 | 5.0.79
21 | 6.0.*
22 | https://github.com/argenos/zotero-mdnotes/releases/download/0.1.3/mdnotes-0.1.3.xpi
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
--------------------------------------------------------------------------------
/webpack.config.js:
--------------------------------------------------------------------------------
1 | const path = require('path')
2 |
3 | // Defines the entry points for all additional helper classes. Each entry
4 | // needs to be compiled and then placed into the content-subdirectory.
5 | // For adding new files, do not forget to load the file in overlay.xul.
6 |
7 | // TODO: Possibly integrated mdnotes.js into the full build toolchain so that
8 | // we can have a cleaner plugin file with exactly one entry point and one
9 | // produced JS artefact which can be shipped with the plugin file.
10 | module.exports = {
11 | entry: './src/markdown-utils.js',
12 | output: {
13 | filename: 'markdown-utils.js',
14 | path: path.resolve(__dirname, 'content')
15 | },
16 | resolve: {
17 | // As npm-modules generally expect some node-stuff, we have to polyfill some
18 | // of these so that the expected functionality is being supported in the
19 | // resulting file.
20 | fallback: {
21 | // The CSS stringify component depends on fs, but we don't actually
22 | // need it for our own purposes, so we won't need to polyfill.
23 | "fs": false,
24 | // Path is being required by urix and CSS stringify, but we can polyfill it.
25 | "path": require.resolve("path-browserify")
26 | }
27 | }
28 | }
29 |
--------------------------------------------------------------------------------