JabRef
v5
v5
  • JabRef Bibliography Management
  • Installation
  • Getting started
  • Collect
    • Add entry manually
    • Add entry using an ID
    • Add entry using reference text
    • Searching externally using Online Services
    • Add entry using PDFs
    • Browser Extension
    • Import
      • Custom import filters
      • Import inspection window
  • Organize
    • Edit an entry
    • Groups
    • Keywords
    • Mark and grade
    • Comment on an entry
    • Searching within the library
    • Complete information using online databases
    • Manage associated files
    • Manage field names and their content
    • Best practices
    • Cleanup entries
    • Check integrity
    • Find duplicates
    • Merge entries
    • Save actions
  • Cite
    • BibTeX and biblatex
    • Pushing to external editor application
    • Export to Microsoft Word
    • OpenOffice/LibreOffice integration
  • Share
    • Sharing a Bib(la)TeX Library
    • Shared SQL Database
      • Migration of pre-3.6 SQL databases into a shared SQL database
    • Export
      • Custom export filters
    • Send as email
  • Configuration
    • Customize the citation key generator
    • Customize entry types
    • Customize general fields
    • Customize key bindings
    • Library properties
    • Entry preview setup
    • Manage external file types
    • Manage protected terms
    • The string editor
  • Advanced information
    • Main Window
    • Entry Editor
      • Links to other entries
      • The Bibtex / Biblatex source tab
      • The 'owner' field
      • Time stamp field
      • LaTeX Citations Tab
    • About BibTeX and its fields
    • Strings
    • Field content selector
    • URL and DOI links in JabRef
    • Command line use and options
    • Automatic Backup (.sav and .bak) and Autosave
    • XMP metadata support in JabRef
    • Remote operation
    • Custom themes
    • Journal abbreviations
    • New subdatabase based on AUX file
    • How to expand first names of an entry
    • Debugging your library file
    • Resources
    • License
    • Knowledge
      • MS Office Bibliography XML format
      • Comparison of the Medline (txt), Medline (xml), and RIS format
      • EndNote Export Filter
  • Frequently Asked Questions
    • Linux
    • Mac OS X
    • Windows
  • Discussion Forum
  • Contribute to JabRef
    • How to Improve the Help Page
    • How to translate the JabRef User Interface
Powered by GitBook
On this page
  • Rendering of constants in JabRef's entry editor
  • JabRef's typed Strings
  • More examples
  • Further reading

Was this helpful?

Edit on GitHub
Export as PDF
  1. Advanced information

Strings

PreviousAbout BibTeX and its fieldsNextField content selector

Was this helpful?

BibTeX supports storing constant strings using @String {key = value}. JabRef supports managing them using Library → Edit string constants, 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.

More examples

  • \@String{aKahle = "Kahle, Brewster "} -> author

  • \@String{aStallman = "Stallman, Richard"} -> author

  • \@String{iMIT = "{Massachusetts Institute of Technology ({MIT})}" } -> institution

  • \@String{pMIT = "{Massachusetts Institute of Technology ({MIT}) press}" } -> publisher

  • \@String{anct = "Anecdote" } -> other

  • \@String{eg = "for example" } -> other

  • \@String{et = " and " } -> other

  • \@String{lBigMac = "Big Mac" } -> other

Usage:

\@Misc {
  title       = "The GNU Project"
  author      = aStallman # et # aKahle
  institution = iMIT
  publisher   = pMIT
  note        = "Just " # eg
}

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