JabRef
v4
v4
  • JabRef Bibliography Management
  • General information about JabRef
    • Entry Editor
    • Best Practices
    • Command line use and options
    • Automatic Backup (.sav and .bak) and Autosave
    • Remote operation
    • Installation
  • About BibTeX and its fields
    • URL and DOI links in JabRef
    • File links in JabRef
    • Links to other entries
    • The 'owner' field
    • Time stamped fileds
    • Journal abbreviations
    • Special Fields
    • Set/clear/rename fields
    • Field content selector
    • Strings
  • Finding, Sorting, and Cleaning Entries
    • Searching within the library
    • Searching externally using Online Services
      • ACM Portal
      • arXiv
      • CiteSeerX
      • DBLP
      • DOAJ
      • Google Scholar
      • GVK
      • IEEEXplore
      • INSPIRE-HEP
      • MathSciNet
      • MEDLINE
      • SAO/NASA Astrophysics Data System
      • Springer
      • Unpaywall
      • zbMATH
    • Searching externally using Publication Identifiers
      • DiVA
      • DOI -- Digital Object Identifier
      • IACR eprint IDs
      • ISBN number
      • Medline
      • RFC document
      • SAO/NASA Astrophysics Data System
      • Title of the paper
    • Add unlinked PDFs including BibTeX data into the database
    • Synchronize file links
    • Cleanup entries
    • Save actions
    • Check integrity
    • Get BibTeX data from DOI
    • Find duplicates
    • Merge entries
    • Groups
    • Replace string
  • Import and Export
    • Import
      • JabRef Browser Extension
      • Custom import filters
      • Import from Microsoft Word -- MS Office Bibliography XML format
      • Import inspection window
      • New subdatabase based on AUX file
      • New entry from plain text
    • Export
      • Custom export filters
      • EndNote Export Filter
      • Export to an External SQL Database
      • Export to Microsoft Word -- MS Office Bibliography XML format
    • Other integrations
      • LaTeX Citations Tab
      • OpenOffice/LibreOffice integration
      • Pushing to external editor application
      • XMP metadata support in JabRef
    • Knowledge
      • Comparison of the Medline (txt), Medline (XML), and RIS format
  • Collaborative Work
    • Sharing a Bib(La)TeX Database
    • Shared SQL Database
    • Migration of pre-3.6 SQL databases into a shared SQL database
  • Configuration of JabRef
    • Customize the BibTeX key generator
    • Customize entry types
    • Customize general fields
    • Customize key bindings
    • Database properties window
    • Entry preview setup
    • Manage external file types
    • Manage protected terms
    • The string editor
  • Frequently Asked Questions and Howtos
    • General FAQs
    • Contributing
    • Sharing
    • How Tos
      • How to expand first names of a BibTeX entry
      • How to Improve the Help Page
      • How to translate the JabRef User Interface
    • FAQs on Operating Systems
      • Linux
      • Mac OS X
      • Windows
Powered by GitBook
On this page
  • Rendering of constants in JabRef's entry editor
  • JabRef's typed Strings
  • Further reading

Was this helpful?

Edit on GitHub
Export as PDF
  1. About BibTeX and its fields

Strings

PreviousField content selectorNextFinding, Sorting, and Cleaning Entries

Last updated 3 years ago

Was this helpful?

BibTeX supports storing constant strings using @String {key = value}. JabRef supports managing them using BibTeX → Edit strings, which opens the . These values can be used in fields. For example, you can have:

@String { kopp = "Kopp, Oliver" }
@String { kubovy = "Kubovy, Jan" }
@String { et = " and " }

and then in some entry for example

@Misc{m1,
  author = kopp # et # kubovy,
}

or

@Misc{m2,
  author = kopp # " and " # kubovy,
}

In the JabRef field editor, the author has to be inserted as #kopp# #et# #kubovy# or #kopp# and #kubovy#.

Rendering of constants in JabRef's entry editor

Strings are rendered specially in the entry editor. This is especially important in the case of months. For instance, take the following BibTeX entry:

@Misc{m3,
  month = may,
}

In JabRef, the entry editor then displays #may#. In case the entry editor just displays may, this is written as follows:

@Misc{m4,
  month = {may},
}

In other words: The character # indicates something special in the entry editor.

JabRef's typed Strings

JabRef enhances the concept of Strings to add a type to those @Strings. The issue is how to preserve such type of a string in a BibTeX file. JabRef adds the type though prefixes:

  • @String { aKopp = "Kopp, Oliver" } is a @String with the type author.

  • @String { iMIT = "{Massachusetts Institute of Technology ({MIT})}" } is a @String with the type of institution.

  • @String { anct = "Anecdote" } is a @String of type other.

  • @String { lTOSCA = "Topology and Orchestration Specification for Cloud Applications" } is a @String of type other.

Then @Strings of type author should be used for author and editors fields only. @Strings of type institution should be used for institution and organization fields only. @Strings of type publisher should be used only for publisher fields. And finally @Strings of type other can be used anywhere.

It can also happen that you will have the same institution for more types:

  • @String { aMIT = "{Massachusetts Institute of Technology ({MIT})}" } if the institution will appear as author or editor

  • @String { iMIT = "{Massachusetts Institute of Technology ({MIT})}" } if the institution will appear as institution or organization

  • @String { pMIT = "{Massachusetts Institute of Technology ({MIT}) press}" } if the institution will appear as publisher.

Even if the last example may appear contradicting the intention was to remove duplicity and unify the names of persons and institutions.

Further reading

See for a MWE for string constants.

String Editor
https://tex.stackexchange.com/questions/303467/bibliography-contents-journal-names-not-abbreviated-even-with-ieeeabrv/303489#303489