-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
Hey Gianluca, 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. |
Hello,
Thanks, that would be very useful! Thanks, |
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"? |
@gianlucabaldassarre You can try out a version at https://builds.jabref.org/implement1506 in a few minutes. I went with |
With #4722 now also a more flexible solution using 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. |
Hello Matthias,
it is nice to see the issue was followed so keenly. : )
Bye,
Gianluca
…On Wed, 6 Mar 2019 at 19:51, Matthias Geiger ***@***.***> wrote:
With #4722 <#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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1506 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ANq4DwCrPu2fzAKZoGSoI2SFNrbTMGoNks5vUA47gaJpZM4I5g11>
.
--
.|.CS...|.......|...............|..|......US.|||.|||||.||.||||..|...|.......
Gianluca Baldassarre, Ph.D.,
Laboratory of Computational Embodied Neuroscience,
Istituto di Scienze e Tecnologie della Cognizione,
Consiglio Nazionale delle Ricerche (LOCEN-ISTC-CNR),
Via San Martino della Battaglia 44, I-00185 Roma, Italy
E-mail: gianluca.baldassarre@istc.cnr.it
Web: http://www.istc.cnr.it/people/gianluca-baldassarre
Tel: +39 06 44 595 231
Fax: +39 06 44 595 243
Motto: 'Learn from the past, live in(tensely) the present, dream for the
future'
Life mission statement: 'Serve humanity through core knowledge'
...CS.|||.||.|||.||..|.......|........|...US.|.|....||..|..|......|.........
|
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:
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
The text was updated successfully, but these errors were encountered: