Re: [Biborb-general] New features in CVS

[Guillaume Gardey]

Hi,

> o tarball doesn't seem be updated, wonder how do I check out a cvs 
> copy? tried the following command, not working
>
> cvs -z3 -d:pserver:address@hidden:/cvsroot/biborb co 
> biborb

I will update the tarball as soon as I perform some further test for 
importation.
Concerning the CVS, the command you used is not exact. 
(http://savannah.nongnu.org/cvs/?group=biborb). You should use these 
commands:

export CVS_RSH="ssh"
cvs -z3 -d:ext:address@hidden:/cvsroot/biborb co biborb

Since the beginning of the year, Savannah only accepts secured 
connections using ssh (protocol 2)


> o the display of basket (font is too small to be intelligible, see 
> atttached screenshot, I can hardcode to modify it, I wonder if there 
> are other better ways to do it?

Exact, + and - are small.  If you want to keep the + and -, you should 
modify the style.css file. The + and - link belong to the CSS class 
.basket_action. So if you want to change the size of the font, simply 
change the class (line 245->250) to:

#bibtex_table a.basket_action {
    display:inline;
    font-family:serif;
    color:navy;
    font-size:12pt;             // <---- ADD
}

More generally, you can change the look of biborb by customizing this 
file.

If you want to change + and - in add and remove or whatever you want, 
you should then edit the file bibtex_entry2tr.xsl. The + and - are 
coded line 68 and 71.

May be some meaningful icons will be more suitable...

> o what is current mechansims for dealing with duplicate entries? If 
> not, is there any plan to do so?

There is a mechanism when using biborb to add entry. It will detect 
that an id is already used and propose to modify it. I am still testing 
it because there is a small bug that sometimes does not allow to add 
the new entry when the id was modified.
Concerning the import features, there is no check at all of the bibtex 
file. It assumes the file or the edited text are well formed and don't 
contain duplicate ids or ids already in the database. I plan to find a 
simple way to solve these errors when importing (a reason why I do not 
include it in the tarball)


Guillaume

PGP.sig
Description: Ceci est une signature électronique PGP