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

Key generator: how to obtain LastnameLastname2016WordsOfTitleWithUpperFirstLetter ? #1506

Closed
gianlucabaldassarre opened this issue Jun 20, 2016 · 6 comments

Comments

@gianlucabaldassarre
Copy link

JabRef version 3.4 on Debian 8 Jessie

Hello, I would like to set the key generator of JabRef so that it produces a key of the type:
[authors][year][title]
but I would like that the words of the title are all forced to have an initial upper letter to facilitate the reading of the key (by ``forced'' I mean independently of the fact that the words of the title are lower or upper case in the title field of the JabRef entry).

That is, I would like to obtain a key of this type:
LastnameLastname2016WordsOfTitleWithUpperFirstLetter
rather than:
LastnameLastname2016wordsoftitlewithlowerfirstletter
which is now generated by [authors][year][title] if the words of the title in the database entry are lower case.

I have seen in the JabRef Help that you can force lower or upper case letters as follows:

:lower: Forces the text inserted by the field marker to be in lowercase. For example, [auth:lower] expands the last name of the first author in lowercase.
:upper: Forces the text inserted by the field marker to be in uppercase. For example, [auth:upper] expands the last name of the first author in uppercase.

but I have not found a setting to obtain what I mention above, e.g. something like :firstupper or similar to set [title:firstupper] that would force the words of the title to have the first letter to be upper case and the following letters to be lower case.

Is it possible to obtain this in JabRef 3.4?

If not, would it be possible to add such feature in future versions of JabRef?

Thanks,
Gianluca

@matthiasgeiger
Copy link
Member

Hey Gianluca,
this is currently not possible.

But I agree that the feature would be useful to improve readability of such bibtex keys. We'll see whether we can add this in a future release.

@gianlucabaldassarre
Copy link
Author

Hello,

We'll see whether we can add this in a future release.

Thanks, that would be very useful!
I guess other people would use that feature to make the words of title more easily readable within the keys. Also, this would allow to standardise the title part of keys as in some references they come with an upper initial letter, in some others with a lower initial letter, and in yet some other with both (upper for keywords, lower for conjunction words), so keys using title words are a bit messy now.

Thanks,
Gianluca

@oscargus oscargus self-assigned this Aug 30, 2016
@oscargus
Copy link
Contributor

I can give this a go. @gianlucabaldassarre could you live with "of" being written as "of" or do you really want "Of"? (I can see that in this case you do want "Of", but we spent some time solving "of". ;-)

I think the modifier "title" can be a good name for the "of"-case. What about the first? "firstupper"?

@oscargus
Copy link
Contributor

@gianlucabaldassarre You can try out a version at https://builds.jabref.org/implement1506 in a few minutes. I went with title and camel where you would like to use camel.

@matthiasgeiger
Copy link
Member

With #4722 now also a more flexible solution using :capitalize, :titlecase and :sentencecase modifiers is available and therefore this issue can be closed.

Thus: This should be fixed in the latest development version. You can check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version.

@gianlucabaldassarre
Copy link
Author

gianlucabaldassarre commented Mar 8, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants