.png)
.png)
.png)
Lookup > Search for unlinked local files
Lookup > Search for unlinked local files
.png)
JabRef looking up full text documents
JabRef looking up full text documents
.png)
File found
File found
.png)
+ 
4. Choose a start directory using the "Browse" button.
5. Click on "Search" / "Scan directory".
6. In "Select files", the files not yet contained in the library are shown.
@@ -40,9 +40,9 @@ In case you have numerous PDF files and want to convert them into new entries, J
8. Click on `Import`.
The windows close and the entry table now contains the newly-imported entries.
-9. The entry editor with the last imported entry is shown .png>)
+9. The entry editor with the last imported entry is shown 
10. You can now save the file and are finished.
-11. Optional: Click on "General" to see the linked file .png>)
+11. Optional: Click on "General" to see the linked file 
12. Optional: Click on "BibTeX source" to see the BibTeX source 
13. Optional: You have to shrink it to see the entry in the entry table, enlarge the JabRef window and use the mouse at the upper border of the entry editor 
14. Optional: Press Esc to show the entry preview 
@@ -65,7 +65,7 @@ We are also [thinking about](https://github.com/koppor/jabref/issues/169) replac
JabRef also offers to change the filenames. You can adapt the pattern at Preferences -> Import 
-Select "Choose pattern" and choose "bibtexkey - title" .png>) This results in the setting `\bibtexkey\begin{title} - \format[RemoveBrackets]{\title}\end{title}`.
+Select "Choose pattern" and choose "bibtexkey - title"  This results in the setting `\bibtexkey\begin{title} - \format[RemoveBrackets]{\title}\end{title}`.
This makes the filenames start with the bibtey key followed by the full title. In the concrete case, `\bibtexkey` only may be the better option as the described bibtey key already contains the title.
diff --git a/en/collect/import/importinspectiondialog.md b/en/collect/import/importinspectiondialog.md
index c9956dcc4..2054cf972 100644
--- a/en/collect/import/importinspectiondialog.md
+++ b/en/collect/import/importinspectiondialog.md
@@ -10,7 +10,7 @@ Entries are first shown in the inspection window. Note that, if this takes too l
Once the entries displayed in the inspection window, none of them have been added to one of your databases yet.
-.png>)
+
By default, all the entries are selected for importation, as shown by the checked boxes in the _Keep_ column. You can select/unselect an entry by clicking on these checkboxes. On the left panel, buttons allow you to **Select all** the entries for importation, or to **Deselect all** the entries.
diff --git a/en/collect/newentryfromplaintext.md b/en/collect/newentryfromplaintext.md
index c7bd705ab..b642ef80e 100644
--- a/en/collect/newentryfromplaintext.md
+++ b/en/collect/newentryfromplaintext.md
@@ -15,11 +15,11 @@ O. Kopp, A. Armbruster, und O. Zimmermann, "Markdown Architectural Decision Reco
2. The "Plain Reference Parser" window opens
- .png)
+ 
3. Paste the reference text:
- .png)
+ 
4. Click "Add to current library"
5. The result is selected in the entry table:
- .png)
+ 
diff --git a/en/contributing/how-to-improve-the-help-page.md b/en/contributing/how-to-improve-the-help-page.md
index 271094463..c623a79e5 100644
--- a/en/contributing/how-to-improve-the-help-page.md
+++ b/en/contributing/how-to-improve-the-help-page.md
@@ -16,7 +16,7 @@ At the top of each help page, you can find the GitHub icon with "Edit on GitHub"
This leads you to the GitHub page associated with the help page:
- (1) (1) (1) (1) (1) (2) (3) (3) (1) (1) (2) (1) (2).png>)
+
To actually edit the page, click on the pencil icon, as highlighted above.
@@ -24,25 +24,25 @@ To actually edit the page, click on the pencil icon, as highlighted above.
The window to edit the page at GitHub looks like this:
- (3) (3) (3) (1) (1) (2) (1) (2).png>)
+
Most text can be simply added/edited in this field as plain text. However, you can style your contribution by using [markdown](https://daringfireball.net/projects/markdown/). Markdown is a rather easy way to format text without the need for complex markup, such as with HTML. You can find an introduction to markdown [here](https://daringfireball.net/projects/markdown/) or [here](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
In order to review your changes, click on the "Preview changes" tab:
- (1) (1) (1) (3) (3) (3) (1) (1) (2) (1) (1).png>)
+
### 3. Saving the changes
To save the changes, create a so-called "Commit" by scrolling down and pressing the "Propose File Change" button:
- (2) (2) (2) (1) (1) (1).png>)
+
_Please note: The message you provide here will be visible in the history of the help page, so please consider your change and provide a meaningful description of your changes._
As the last step, submit the changes you have made back to the JabRef team:
- (3) (3) (3) (1) (1) (2) (1) (4).png>)
+
Just press the "Create Pull Request" button, and confirm the creation of the request on the next page.
diff --git a/en/contributing/how-to-translate-the-ui.md b/en/contributing/how-to-translate-the-ui.md
index 83672588b..332e8e78b 100644
--- a/en/contributing/how-to-translate-the-ui.md
+++ b/en/contributing/how-to-translate-the-ui.md
@@ -13,7 +13,7 @@ We use the service of [Crowdin](https://translate.jabref.org) to keep our transl
* Visit [https://translate.jabref.org/](https://translate.jabref.org) to get started
* Select your preferred language, login, and click on _JabRef\_en.properties_
- .png)
+ 
* Choose the string you want to translate in the left panel (strings to be translated are listed first)
and enter the translation in the central panel (suggestions are given at the bottom)
@@ -32,7 +32,7 @@ To test directly your translation, you must be able to compile the source tree a
Crowdin allows for downloading the current translation file:
-.png>)
+
Place the downloaded file in the path `src/main/resources/l10n`. Then, execute `gradlew run` in the root directory and JabRef should start.
diff --git a/en/finding-sorting-and-cleaning-entries/checkintegrity.md b/en/finding-sorting-and-cleaning-entries/checkintegrity.md
index dcbe4ae2b..ad8b2739d 100644
--- a/en/finding-sorting-and-cleaning-entries/checkintegrity.md
+++ b/en/finding-sorting-and-cleaning-entries/checkintegrity.md
@@ -4,4 +4,4 @@ JabRef can check the integrity of a library.
This feature is available through **Quality → Check integrity**.
-.png>)
+
diff --git a/en/finding-sorting-and-cleaning-entries/cleanupentries.md b/en/finding-sorting-and-cleaning-entries/cleanupentries.md
index 5625bd3e1..f48653af0 100644
--- a/en/finding-sorting-and-cleaning-entries/cleanupentries.md
+++ b/en/finding-sorting-and-cleaning-entries/cleanupentries.md
@@ -6,7 +6,7 @@ description: Tidy up your library
JabRef can cleanup the entries of a library. To do a cleanup of the entries, go to **Quality → Cleanup entries**. Then select the actions to be carried out.
-.png>)
+
under the table`Enable field formatters`. Then, under the table, you can select using 2 drop-down menus:
diff --git a/en/finding-sorting-and-cleaning-entries/filelinks.md b/en/finding-sorting-and-cleaning-entries/filelinks.md
index 94a78d9ce..9ea035801 100644
--- a/en/finding-sorting-and-cleaning-entries/filelinks.md
+++ b/en/finding-sorting-and-cleaning-entries/filelinks.md
@@ -29,7 +29,7 @@ If JabRef saves an attached file and my login name matches the name stored in th
In some settings, the bib file is stored in **the same directory** as the PDF files. Then, one ignores all the above directories and enable "Search and store files relative to library file location". In this case, JabRef starts searching for PDF files in the directory of the `bib` file. It is also possible to achieve this result by setting `.` as "General file directory" in the library properties.
-.png>).
+.
Relative file directories obviously only work in the library properties for a bib file, e.g. `a.bib` Library → Library properties → General file directory → `papers`. Assume to have two bib files: `a.bib` and `b.bib` located in different directories: `a.bib` located at `C:\a.bib` and `b.bib` located at `X:\b.bib`. When I click on the `+` icon in the general Tab of file `a.bib`, the popup is opened in the directory `C:\papers` (assuming `C:\papers` exists).
diff --git a/en/finding-sorting-and-cleaning-entries/getbibtexdatafromdoi.md b/en/finding-sorting-and-cleaning-entries/getbibtexdatafromdoi.md
index 577f947e6..e92eadd87 100644
--- a/en/finding-sorting-and-cleaning-entries/getbibtexdatafromdoi.md
+++ b/en/finding-sorting-and-cleaning-entries/getbibtexdatafromdoi.md
@@ -17,7 +17,7 @@ _The following features require your entry to have a DOI or ISBN and are disable
* Option A) In the entry table, right-click on the entry to complement, and select the menu **Get bibliographic data from DOI/ISBN/...**
* Option B) Open the [entry editor](../advanced/entryeditor/), and in the General tab, click on the button **Get bibliographic data from DOI**
-.png>)
+
Using any of the options opens the window _Merge entries_:
diff --git a/en/finding-sorting-and-cleaning-entries/groups.md b/en/finding-sorting-and-cleaning-entries/groups.md
index 3936784be..65d903f89 100644
--- a/en/finding-sorting-and-cleaning-entries/groups.md
+++ b/en/finding-sorting-and-cleaning-entries/groups.md
@@ -112,7 +112,7 @@ JabRef has five types of groups:
Groups based on explicit selection are populated only by manual assignment of entries.
-.png>)
+
After creating an explicit-selection group, you select the entries to be assigned to it and use either drag-and-drop or the context menu **Add selected entries to this group** of the group interface.
@@ -158,7 +158,7 @@ The content of the group is updated dynamically whenever the database changes.
The group contains the entries cited in a LaTeX document, based on its '.aux' file. The .aux file has to be specified.
-.png>)
+
The content of the group is updated dynamically whenever the `.aux` file changes.
diff --git a/en/finding-sorting-and-cleaning-entries/keywords.md b/en/finding-sorting-and-cleaning-entries/keywords.md
index e425b6e09..fe0eb1818 100644
--- a/en/finding-sorting-and-cleaning-entries/keywords.md
+++ b/en/finding-sorting-and-cleaning-entries/keywords.md
@@ -37,7 +37,7 @@ To fasten the addition of often-used keywords, JabRef can store the list of your
Go to **File → Manage content selectors**.
-.png>)
+
First, click on the field name "Keywords". Then, enter the list of your preferred keywords. Now, when you start to type one of your preferred keywords, JabRef will display a list of the matching ones (independently of the auto-completion). For more details, see the help section about [Managing content selectors](../advanced/contentselector.md).
diff --git a/en/finding-sorting-and-cleaning-entries/search.md b/en/finding-sorting-and-cleaning-entries/search.md
index d75e59aa1..3c8723a35 100644
--- a/en/finding-sorting-and-cleaning-entries/search.md
+++ b/en/finding-sorting-and-cleaning-entries/search.md
@@ -2,7 +2,7 @@
The search bar is located in the icon bar.
-.png>)
+
To make the cursor jump to the search field, you can:
diff --git a/en/getting-started.md b/en/getting-started.md
index 5afbca6ce..d87c3a3ca 100644
--- a/en/getting-started.md
+++ b/en/getting-started.md
@@ -20,7 +20,7 @@ Upon the first start of JabRef the main user interface is showing up the main el
* Icon bar (shortcuts for most frequently used features)
* Side bar (for groups and web search)
-.png>)
+
## Creation of a new library
@@ -36,7 +36,7 @@ The usage of a text-based file format has some advantages:
To create a new library, just select the "New library" menu item in the "File" menu:
-.png>)
+
The main screen is now showing an empty "entry table" we will now start to fill with some entries.
@@ -46,13 +46,13 @@ To add a new entry select the menu bar entry "Library" -> "New entry", click on
This opens a dialog where you can select the type of reference you want to store. By default all entry types defined by the BibTeX format are available:
-.png>)
+
For our running example we will select "Article".
After clicking on the "Article" button, the dialog closes and the so called "Entry Editor" is opened for the newly created entry:
-.png>)
+
The most important information about the references to be added can now be entered in the "Required Fields" tab. "Author", "Title", "Journal", and "Year" should be self-explanatory - however, a "citationkey", might not be familiar to you. Basically, the idea of the "citationkey" is coming from working with BibTeX, where it is necessary to have an unique identifier for each entry. This allows for referencing within a document you might be creating using the stored information in your library. Moreover, also within JabRef this "key" is used for example for cross-references to other related entries or to determine file names for full-text references.
@@ -64,7 +64,7 @@ The default key pattern is `[auth][year]`, which means that Author information i
After entering some information, you can see on the right side of the entry editor a preview of the bibliographic data:
-.png>)
+
There are further possibilities to add entries to your library which are described in the section "Collect" of this documentation:
@@ -76,7 +76,7 @@ There are further possibilities to add entries to your library which are describ
After creating the basic information the addition of all other bibliographical details is often cumbersome and error-prone. To ease this task, JabRef allows for an automatic completion of the bibliographic information by looking up the data in public databases. To use this feature just click on the "Update with bibliographic information from the web" button in the editor:
-.png>)
+
{% hint style="info" %}
The found information is most accurate if an identifier like a "DOI" or "ISBN" is maintained. If you already know such an unique identifier, this can also be already the starting point to create a new entry without manual entering any information by using the "create from ID" feature in the Create entry dialog. For more information see: [Collect](https://docs.jabref.org/collect) > ["Add entry using an ID"](https://docs.jabref.org/collect/add-entry-using-an-id)
@@ -84,7 +84,7 @@ The found information is most accurate if an identifier like a "DOI" or "ISBN" i
If additional information is found you will be asked in a dialog which information should be taken over:
-.png>)
+
## Adding a full text document
@@ -96,9 +96,9 @@ In order to use the automated feature, it is necessary to set-up a file director
To test the automatic download of full texts you can click on the "Get full-text" icon next to the file field, or choose "Lookup" -> "Search full text documents online" from the menu. As soon as a full-text is found, the file will be stored in the local file directory and linked to the entry:
-.png>)
+
-To open the downloaded full text you can click on the "file" icon before the file name - or use the same icon in the entry table: .png>)
+To open the downloaded full text you can click on the "file" icon before the file name - or use the same icon in the entry table: 
## Finding more references in the web
@@ -106,7 +106,7 @@ If you want to search for other references, it is also possible to directly trig
The search results will be shown in an window where you can select all the search hits to be added to your library.
-.png>)
+
## Next steps
diff --git a/en/setup/citationkeypatterns.md b/en/setup/citationkeypatterns.md
index 18e9a9211..dbfd65443 100644
--- a/en/setup/citationkeypatterns.md
+++ b/en/setup/citationkeypatterns.md
@@ -127,7 +127,7 @@ Keep in mind, Jabref uses a Java flavored regular expressions engine (there are
In addition to using regular expression replacement as [modifiers](citationkeypatterns.md#modifiers) of the field markers within [citation key patterns](citationkeypatterns.md#citation-key-patterns), regular expression matching and replacement can be done after the key patterns have been applied. In this case, the regular expression and replacement string are entered in the separate text fields above the [citation key patterns](citationkeypatterns.md#citation-key-patterns) section. If the replacement string is empty, then matches of the regular expression will be removed from the generated key.
-.png>)
+
The regex `(?<=.{12}+).+` with an empty replacement string will cut the length of all citation keys to 12.
@@ -135,7 +135,7 @@ The regex `(?<=.{12}+).+` with an empty replacement string will cut the length o
The citation key generator preferences contain an option for removing unwanted characters. Add or remove characters to the right of "Remove the following characters:" to control which characters are included in the citation keys.
-.png>)
+
Removing `-` from this list will allow it to be used while generating citation keys.
@@ -158,10 +158,10 @@ To change the citation key pattern to `[authors][camel]` for all libraries witho
.png)
2. Navigate to "Citation key generator"
- .png)
+ 
3. Change the default pattern to `[authors][camel]`
- .png)
+ 
4. Press "Enter" (forgetting to do this is a leading cause of puzzlement)
5. Click "Save"
@@ -171,10 +171,10 @@ To change the citation key patterns for a single library to `[auth][shortyear]`,
1. Make sure the library is open and selected in the JabRef main window
- .png)
+ 
2. From the "Library" menu, open the "Citation key pattern" setting
- .png)
+ 
3. Set the pattern for the desired entry types, and press the apply button.
- .png)
+ 
diff --git a/en/setup/customentrytypes.md b/en/setup/customentrytypes.md
index 967ac581b..da78d4433 100644
--- a/en/setup/customentrytypes.md
+++ b/en/setup/customentrytypes.md
@@ -6,7 +6,7 @@ When customizing an entry type, you both define how its entry editor should look
## Using the entry customization dialog
-.png>)
+
The entry customization interface is divided into two areas. On the left side all entry types (including any custom types) are listed. If you select a type from the left side, the right area shows all fields for the selected entry.
diff --git a/en/setup/externalfiletypes.md b/en/setup/externalfiletypes.md
index 3d566f719..9e3e84044 100644
--- a/en/setup/externalfiletypes.md
+++ b/en/setup/externalfiletypes.md
@@ -8,4 +8,4 @@ For each file link, a file type must be chosen, to determine what icon should be
A file type is specified by a graphical icon, a name, a file extension and an application to view the files. On Windows, the name of the application can be omitted in order to use Window's default viewer instead.
-.png)
Manage external file types
Manage external file types