headers
Hongsheng Zhao | 7 Sep 08:17
Favicon

[BULK] A bug in jabref 2.4.

Dear Winedt+list,

I find a the bug in the recently released jabref 2.4, I know I should post this to the list of jabref, but I
cann't find the corresponding list of it. 

The jabref 2.4's bibtexkey generator pattern has the following bug:

the [auth][year] doesn't work correctly, it will do the following wrong thing like this:

----------------------
author = {{Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C}},

will be translated to:

SegallMDLindanPJDProbertMJPickardCJHasnipPJClarkSJandPayneMC
----------------------

Sincerely yours,
--

-- 
Hongsheng Zhao <zhaohscas <at> yahoo.com.cn> 
Xinjiang Technical Institute of Physics and Chemistry
Chinese Academy of Sciences 
GnuPG DSA: 0xD108493
2008-9-7
Permalink | Reply |
headers
Joseph Wright | 7 Sep 08:39

Re: [BULK] A bug in jabref 2.4.

Hongsheng Zhao wrote:
> Dear Winedt+list,
> 
> I find a the bug in the recently released jabref 2.4, I know I should post this to the list of jabref, but I
cann't find the corresponding list of it. 
> 
> The jabref 2.4's bibtexkey generator pattern has the following bug:
> 
> the [auth][year] doesn't work correctly, it will do the following wrong thing like this:
> 
> ----------------------
> author = {{Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C}},
>  
> will be translated to:
> 
> SegallMDLindanPJDProbertMJPickardCJHasnipPJClarkSJandPayneMC

Each author name should be separated by "and":

author = {Segall, M. D. and Lindan, P. J. D. and Probert, M. J. and
Pickard, C. J. and Hasnip, P. J. and Clark, S. J. and Payne, M. C.},

You'll also confuse the bibtex with the field as you gave.
-- 	
Joseph Wright
Permalink | Reply |
headers
Hongsheng Zhao | 7 Sep 11:22
Favicon

Re[2]: [BULK] A bug in jabref 2.4.

On Sunday, September 7, 2008 at 14:39, joseph.wright <at> morningstar2.co.uk wrote:
> Hongsheng Zhao wrote:
>> Dear Winedt+list,
>> 
>> I find a the bug in the recently released jabref 2.4, I know I should post this to the list of jabref, but I
cann't find the corresponding list of it. 
>> 
>> The jabref 2.4's bibtexkey generator pattern has the following bug:
>> 
>> the [auth][year] doesn't work correctly, it will do the following wrong thing like this:
>> 
>> ----------------------
>> author = {{Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C}},
>>  
>> will be translated to:
>> 
>> SegallMDLindanPJDProbertMJPickardCJHasnipPJClarkSJandPayneMC

> Each author name should be separated by "and":

> author = {Segall, M. D. and Lindan, P. J. D. and Probert, M. J. and
> Pickard, C. J. and Hasnip, P. J. and Clark, S. J. and Payne, M. C.},

If I use the and as the delimiter, then the ultimate compiled results would be:

-----------------
M. D. Segall, P. J. D. Lindan, M. J. Probert, C. J. Pickard, P. J. Hasnip, S. J.
Clark, and M. C. Payne.
-----------------
(Continue reading)

Permalink | Reply |
headers
Joseph Wright | 7 Sep 13:11

Re: [BULK] A bug in jabref 2.4.

Hongsheng Zhao wrote:
> 
> If I use the and as the delimiter, then the ultimate compiled results would be:
> 
> -----------------
> M. D. Segall, P. J. D. Lindan, M. J. Probert, C. J. Pickard, P. J. Hasnip, S. J.
> Clark, and M. C. Payne.
> -----------------
> 
> In fact, I just want the authors look like this in the ultimate
> compiled result files:
> 
> ---------------------
> Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C
> ---------------------

This is dependent on your BibTeX style.  The point of BibTeX is that the
formatting can be varied while using the same database.  Hence JabRef
expects to find author data in a known layout.
> 
> Furthermore, I also use a pare of redundant "{}" to include all of the
> authors in it in order to keep the override the BibTeX's
> capitalization conventions and keep some special latex command
> sequence, such as \ae correct in the the ultimate compiled result
> file,  but this will also confuse the jabref 2.4, I mean, in this
> case, the jabref 2.4 will treat all the authors in the inner "{}"
> added by me as the only one author, this is just the reason of my
> issue posted by my last mail.

You are only supposed to use {...} around specific items to be left
(Continue reading)

Permalink | Reply |
headers
Hongsheng Zhao | 7 Sep 13:41
Favicon

Re[2]: [BULK] A bug in jabref 2.4.

On Sunday, September 7, 2008 at 19:11, joseph.wright <at> morningstar2.co.uk wrote:
> Hongsheng Zhao wrote:
>> 
>> If I use the and as the delimiter, then the ultimate compiled results would be:
>> 
>> -----------------
>> M. D. Segall, P. J. D. Lindan, M. J. Probert, C. J. Pickard, P. J. Hasnip, S. J.
>> Clark, and M. C. Payne.
>> -----------------
>> 
>> In fact, I just want the authors look like this in the ultimate
>> compiled result files:
>> 
>> ---------------------
>> Segall M D, Lindan P J D, Probert M J, Pickard C J, Hasnip P J, Clark S J and Payne M C
>> ---------------------

> This is dependent on your BibTeX style.  The point of BibTeX is that the
> formatting can be varied while using the same database.  Hence JabRef
> expects to find author data in a known layout.
>> 
>> Furthermore, I also use a pare of redundant "{}" to include all of the
>> authors in it in order to keep the override the BibTeX's
>> capitalization conventions and keep some special latex command
>> sequence, such as \ae correct in the the ultimate compiled result
>> file,  but this will also confuse the jabref 2.4, I mean, in this
>> case, the jabref 2.4 will treat all the authors in the inner "{}"
>> added by me as the only one author, this is just the reason of my
>> issue posted by my last mail.
(Continue reading)

Permalink | Reply |
headers
Joseph Wright | 7 Sep 14:56

Re: [BULK] A bug in jabref 2.4.

Hongsheng Zhao wrote:
> 
>> You are only supposed to use {...} around specific items to be left
>> alone by BibTeX.  I think you will be very unlucky to find a BibTeX
>> style that alters capitalisation of names, and in any case you can get
>> JabRef to add braces around them "behind the scenes" when saving.
> 
> Do you mean the JabRef can do this for automatically?  If so, how can
> I make JabRef to add braces around them automatically?  In fact, I
> cann't find any options of JabRef to do the above things
> automatically.

Options -> Preferences -> File -> "Store the following fields with
braces around capital letters", which takes a semi-colon separated list.

>> Taking a complex example:
> 
>> author = {Bj{\o}rn Anders and A. N. T{\ae}rs and {A and B}},
> 
>> where "A and B" is a company name, and so the "and" is part of the name
>> itself.  JabRef will understand that type of entry just fine (some
>> trouble can arise if the first character of a name is accented, but this
> 
> Why in this case ( the first character of a name is accented) some
> trouble can arise?  What's the trouble?  How to solve it?

Just that JabRef might do things you don't quite expect:

Bekir {\c{C}}etinkaya
(Continue reading)

Permalink | Reply |
headers
Hongsheng Zhao | 7 Sep 17:16
Favicon

Re[2]: [BULK] A bug in jabref 2.4.

On Sunday, September 7, 2008 at 20:56, joseph.wright <at> morningstar2.co.uk wrote:
> Hongsheng Zhao wrote:
>> 
>>> You are only supposed to use {...} around specific items to be left
>>> alone by BibTeX.  I think you will be very unlucky to find a BibTeX
>>> style that alters capitalisation of names, and in any case you can get
>>> JabRef to add braces around them "behind the scenes" when saving.
>> 
>> Do you mean the JabRef can do this for automatically?  If so, how can
>> I make JabRef to add braces around them automatically?  In fact, I
>> cann't find any options of JabRef to do the above things
>> automatically.

Options ->> Preferences -> File -> "Store the following fields with
> braces around capital letters", which takes a semi-colon separated list.

>>> Taking a complex example:
>> 
>>> author = {Bj{\o}rn Anders and A. N. T{\ae}rs and {A and B}},
>> 
>>> where "A and B" is a company name, and so the "and" is part of the name
>>> itself.  JabRef will understand that type of entry just fine (some
>>> trouble can arise if the first character of a name is accented, but this
>> 
>> Why in this case ( the first character of a name is accented) some
>> trouble can arise?  What's the trouble?  How to solve it?

> Just that JabRef might do things you don't quite expect:

> Bekir {\c{C}}etinkaya
(Continue reading)

Permalink | Reply |

Gmane