Skip to content
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

Handling of diacritics in bibtex key generator #4709

Closed
doctor-ian opened this issue Mar 1, 2019 · 3 comments
Closed

Handling of diacritics in bibtex key generator #4709

doctor-ian opened this issue Mar 1, 2019 · 3 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs good first issue An issue intended for project-newcomers. Varies in difficulty. keygenerator

Comments

@doctor-ian
Copy link

JabRef version 4.3.1 on Windows 7.

There are certain diacritics (and other symbols) that produce undesired output when generating bibtex keys. I am using [auth3][shortyear] as generation pattern. Examples with first authors' last names and year:

  • Müller, 2019 -> Muel19 (4 characters instead of 3 when converting umlaut, i.e. ä, ö, ü)
  • Al-Ketan, 2019 -> Al-19 (dash in bibtex key is awkward, should probably be ignored in favor of the next letter and become AlK19)
  • D'Alessandro, 2019 -> DA19 (Apostrophe is correctly ignored, but the name is reduced to 2 characters when it should probably be DAl19)

Some other diacritics that I quickly tested (Ç, Â, é) are handled more gracefully, i.e. the corresponding letter without diacritic is used.

Steps to reproduce the behavior:

  1. Use [auth3][shortyear] as pattern for bibtex key generation.
  2. Enter one of the last names mentioned above in the last author field of a new article. Enter any year.
  3. Generate bibtex key (CTRL+G)
@Siedlerchr
Copy link
Member

Well, dash is a perfectly legal char in a bibtex/biblatex key: Forbidden are only these symbols: " # % ' ( ) , = { }
But I agree with you that the pattern of sometimes two, three and 4 chars is confusing.

@tobiasdiez tobiasdiez added bug Confirmed bugs or reports that are very likely to be bugs keygenerator good first issue An issue intended for project-newcomers. Varies in difficulty. labels Mar 1, 2019
@chel-seyy
Copy link
Contributor

Can I work on this issue?

@Siedlerchr
Copy link
Member

Thanks to @chelseyong this should now be fixed in the latest master.

We would like to ask you to use a development build from https://builds.jabref.org/master and report back if it works for you. Please remember to make a backup of your library before trying-out this version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs good first issue An issue intended for project-newcomers. Varies in difficulty. keygenerator
Projects
Archived in project
Development

No branches or pull requests

4 participants