On Thursday 05 March 2015 12:00 AM, Rasmus wrote:
> Hi,
>
> Vaidheeswaran C <vaidheeswaran.chinnar...@gmail.com> writes:
>
>> 1. Visit http://www.amazon.in/How-Read-Book-Touchstone-book/dp/0671212095
>> 2. Add it to Zotero.
>> 3. Export My Library to BibTeX format.
>> 4. The attached file -- My Library 1.bib -- is what I get.
>>
>> When I import the above .bib file to JabRef GUI, the keys that are
>> reported are \cite{adler_how_1972},
>> \cite{center_for_history_and_new_media_zotero_????}.
>>
>> I am a novice comes to citation. I had a vague impression by that `_'
>> is not allowed in cite keys. If we go this way, then the above
>> workflow will be a nightmare.
>
> Underscore is fine. Here's the regexp that bibtex.el uses for keys:
>
> \\([][[:alnum:].:;?!`'/*@+|()<>&_^$-]+\\)
>
> See bibtex-entry-head.
I am complaining about how org-element.el behaves.
This [cite:@adler_how_1972] becomes this:
(citation
(:key
#("adler" 0 5
(keymap
(keymap
(follow-link . mouse-face)
(mouse-3 . org-find-file-at-mouse)
(mouse-2 . org-open-at-mouse))
face org-link mouse-face highlight htmlize-link
(:uri "cite:@adler_how_1972")
fontified t))
:parentheticalp nil :begin 192 :post-blank 0 :end 214 :suffix
(#4=(underline
(:begin 204 :end 209 :contents-begin 205 :contents-end 208
:post-blank 0 :parent #3#)
#("how" 0 3
(:parent #4#)))
#("1972" 0 4
(:parent #3#)))
:parent #5#))
> Jabref is pretty solid (though I'm not at fan of how handles encoding) and
> will not produce wrong keys.
>
> Cheers,
> Rasmus
>
