-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify string file to be used in entry preview #323
Comments
@koppor I would be happy to address this, if you would like. |
@ahlusar1989 Sure, every helping hand is welcome! Please take care about good architecture when implementing it. See https://github.com/JabRef/jabref/wiki/High-Level-Documentation. Looking forward to your first pull request to JabRef! |
I think the current support for journal abbreviations is already sufficient and somewhat covers this feature request (or use case). Under "Manage journal abbreviations" you can edit the journal abbreviations and add custom ones. |
I put it on freeze, because we do not have support for placeholders ("Strings" in BibTeX) in JabRef. |
Some people (like myself) have a separate file with strings containing names for e.g. journals and conferences to keep the naming consistent (one good thing is that more people can use these abbreviations without having to share .bib-files). This is also the case with IEEE, which has the file IEEEabrv. bib (which is supported by JabRef). Now, it would be nice if this file could be specified in the .bib file in some way and that the content from the file in the first place is used to show the "correct" name in the entry preview. Later one could also think of using this file and make a reverse conversion of the abbreviation, just as it works with IEEE at the moment (maybe this is already supported? I do not use the built in abbreviation support except for IEEE).
Normally, this is specified in the TeX-file as
so one would probably need to add something corresponding JabRef specific to the bib-file.
The text was updated successfully, but these errors were encountered: