refdb-devel — List for RefDB developers

[Refdb-devel] [ refdb-Bugs-3574407 ] manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

[SourceForge.net <no...@so...>]

Bugs item #3574407, was opened at 2012-10-04 00:12
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Perl modules
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

Initial Comment:
Apparently the POD in refdb-perlmod is buggy. The generated man page says:


POD ERRORS
       Hey! The above document had some coding errors, which are explained below:

       Around line 2044:
           =cut found outside a pod block.  Skipping to next block.


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2012-10-04 15:09

Message:
I've removed the offending =cut and don't see any POD errors afterwards. I
didn't notice any before though, so I'd appreciate if you could
double-check on your setup. The fix is in svn revision 759.

----------------------------------------------------------------------

Comment By: Mathieu Malaterre (malat)
Date: 2012-10-04 00:18

Message:
I guess there is an extra =cut ...:

$ cat RefDB::Makestyle
[...]
=cut

=head1 ELEMENT CLASSES

These classes model the XML elements found in the Refdb C<citestylex> DTD.

=cut


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

[Refdb-devel] [ refdb-Bugs-3574407 ] manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

[SourceForge.net <no...@so...>]

Bugs item #3574407, was opened at 2012-10-04 00:12
Message generated for change (Comment added) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Perl modules
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

Initial Comment:
Apparently the POD in refdb-perlmod is buggy. The generated man page says:


POD ERRORS
       Hey! The above document had some coding errors, which are explained below:

       Around line 2044:
           =cut found outside a pod block.  Skipping to next block.


----------------------------------------------------------------------

>Comment By: Mathieu Malaterre (malat)
Date: 2012-10-04 00:18

Message:
I guess there is an extra =cut ...:

$ cat RefDB::Makestyle
[...]
=cut

=head1 ELEMENT CLASSES

These classes model the XML elements found in the Refdb C<citestylex> DTD.

=cut


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

[Refdb-devel] [ refdb-Bugs-3574407 ] manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

[SourceForge.net <no...@so...>]

Bugs item #3574407, was opened at 2012-10-04 00:12
Message generated for change (Tracker Item Submitted) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Perl modules
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: manpage-has-errors-from-pod2man usr/share/man/man3/RefDB::Ma

Initial Comment:
Apparently the POD in refdb-perlmod is buggy. The generated man page says:


POD ERRORS
       Hey! The above document had some coding errors, which are explained below:

       Around line 2044:
           =cut found outside a pod block.  Skipping to next block.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3574407&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573740 ] refdb does not compile on debian

[SourceForge.net <no...@so...>]

Bugs item #3573740, was opened at 2012-10-02 01:48
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clients
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile on debian

Initial Comment:
By default on debian some stricter gcc options are used:


gcc -DPACKAGE_NAME=\"refdb\" -DPACKAGE_TARNAME=\"refdb\" -DPACKAGE_VERSION=\"1.0.0-pre2\" -DPACKAGE_STRING=\"refdb\ 1.0.0-pre2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"refdb\" -DVERSION=\"1.0.0-pre2\" -D_GNU_SOURCE=1 -DREADLINE42=1 -DHAVE_ICONV=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SOCKLEN_T=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_STRFTIME=1 -DHAVE_MKFIFO=1 -DHAVE_GETHOSTNAME=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRCSPN=1 -DHAVE_STRSTR=1 -DHAVE_STRTOLL=1 -DHAVE_ATOLL=1 -I.  -DSYSCONFDIR=\"/etc/refdb\" -DULLSPEC=\"%llu\" -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -c refdbib.c
refdbib.c: In function ‘make_cookedbib’:
refdbib.c:795: error: format not a string literal and no format arguments
refdbib.c:822: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_rawbib’:
refdbib.c:994: error: format not a string literal and no format arguments
refdbib.c:1029: error: format not a string literal and no format arguments
refdbib.c:1048: error: format not a string literal and no format arguments
refdbib.c:1082: error: format not a string literal and no format arguments
refdbib.c:1122: error: format not a string literal and no format arguments
refdbib.c:1130: error: format not a string literal and no format arguments
refdbib.c:1141: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1155: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_texbib’:
refdbib.c:1249: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1262: error: format not a string literal and no format arguments
refdbib.c:1273: error: format not a string literal and no format arguments
refdbib.c:1286: error: format not a string literal and no format arguments
refdbib.c:1317: error: format not a string literal and no format arguments
refdbib.c:1339: error: format not a string literal and no format arguments
refdbib.c:1396: error: format not a string literal and no format arguments
refdbib.c:1410: error: format not a string literal and no format arguments
refdbib.c:1427: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1433: error: format not a string literal and no format arguments
refdbib.c: In function ‘log_print’:
refdbib.c:1468: error: format not a string literal and no format arguments


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2012-10-03 15:37

Message:
I hadn't even noticed that there was a patch - thanks a million for that.
I've applied the patch successfully, see svn revison 757.

----------------------------------------------------------------------

Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 23:54

Message:
I am sure you noticed the patch is done against svn trunk. The patch
actually applies on 0.9.9 (with fuzzing) and svn trunk.

Anyway here are the default flags on debian:

$ dpkg-buildflags --get CFLAGS
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security

$ dpkg-buildflags --get CXXFLAGS
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security

and

$ dpkg-buildflags --get CPPFLAGS
-D_FORTIFY_SOURCE=2

One more things:

$ dpkg-buildflags --get LDFLAGS
-Wl,-z,relro



----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2012-10-02 15:14

Message:
Could you please specify which options you add to gcc? The error messages
apparently reflect the status of the last release. The line numbers differ
from the current svn version. In order to fix these problems I'd like to
reproduce this locally with the svn sources.

----------------------------------------------------------------------

Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 01:48

Message:
One cannot do:

      fprintf(stderr, get_status_msg(cs_status));

but instead

      fprintf(stderr, "%s", get_status_msg(cs_status));


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573740 ] refdb does not compile on debian

[SourceForge.net <no...@so...>]

Bugs item #3573740, was opened at 2012-10-02 01:48
Message generated for change (Comment added) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clients
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile on debian

Initial Comment:
By default on debian some stricter gcc options are used:


gcc -DPACKAGE_NAME=\"refdb\" -DPACKAGE_TARNAME=\"refdb\" -DPACKAGE_VERSION=\"1.0.0-pre2\" -DPACKAGE_STRING=\"refdb\ 1.0.0-pre2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"refdb\" -DVERSION=\"1.0.0-pre2\" -D_GNU_SOURCE=1 -DREADLINE42=1 -DHAVE_ICONV=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SOCKLEN_T=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_STRFTIME=1 -DHAVE_MKFIFO=1 -DHAVE_GETHOSTNAME=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRCSPN=1 -DHAVE_STRSTR=1 -DHAVE_STRTOLL=1 -DHAVE_ATOLL=1 -I.  -DSYSCONFDIR=\"/etc/refdb\" -DULLSPEC=\"%llu\" -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -c refdbib.c
refdbib.c: In function ‘make_cookedbib’:
refdbib.c:795: error: format not a string literal and no format arguments
refdbib.c:822: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_rawbib’:
refdbib.c:994: error: format not a string literal and no format arguments
refdbib.c:1029: error: format not a string literal and no format arguments
refdbib.c:1048: error: format not a string literal and no format arguments
refdbib.c:1082: error: format not a string literal and no format arguments
refdbib.c:1122: error: format not a string literal and no format arguments
refdbib.c:1130: error: format not a string literal and no format arguments
refdbib.c:1141: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1155: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_texbib’:
refdbib.c:1249: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1262: error: format not a string literal and no format arguments
refdbib.c:1273: error: format not a string literal and no format arguments
refdbib.c:1286: error: format not a string literal and no format arguments
refdbib.c:1317: error: format not a string literal and no format arguments
refdbib.c:1339: error: format not a string literal and no format arguments
refdbib.c:1396: error: format not a string literal and no format arguments
refdbib.c:1410: error: format not a string literal and no format arguments
refdbib.c:1427: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1433: error: format not a string literal and no format arguments
refdbib.c: In function ‘log_print’:
refdbib.c:1468: error: format not a string literal and no format arguments


----------------------------------------------------------------------

>Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 23:54

Message:
I am sure you noticed the patch is done against svn trunk. The patch
actually applies on 0.9.9 (with fuzzing) and svn trunk.

Anyway here are the default flags on debian:

$ dpkg-buildflags --get CFLAGS
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security

$ dpkg-buildflags --get CXXFLAGS
-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security

and

$ dpkg-buildflags --get CPPFLAGS
-D_FORTIFY_SOURCE=2

One more things:

$ dpkg-buildflags --get LDFLAGS
-Wl,-z,relro



----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2012-10-02 15:14

Message:
Could you please specify which options you add to gcc? The error messages
apparently reflect the status of the last release. The line numbers differ
from the current svn version. In order to fix these problems I'd like to
reproduce this locally with the svn sources.

----------------------------------------------------------------------

Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 01:48

Message:
One cannot do:

      fprintf(stderr, get_status_msg(cs_status));

but instead

      fprintf(stderr, "%s", get_status_msg(cs_status));


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573740 ] refdb does not compile on debian

[SourceForge.net <no...@so...>]

Bugs item #3573740, was opened at 2012-10-02 01:48
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: clients
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile on debian

Initial Comment:
By default on debian some stricter gcc options are used:


gcc -DPACKAGE_NAME=\"refdb\" -DPACKAGE_TARNAME=\"refdb\" -DPACKAGE_VERSION=\"1.0.0-pre2\" -DPACKAGE_STRING=\"refdb\ 1.0.0-pre2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"refdb\" -DVERSION=\"1.0.0-pre2\" -D_GNU_SOURCE=1 -DREADLINE42=1 -DHAVE_ICONV=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SOCKLEN_T=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_STRFTIME=1 -DHAVE_MKFIFO=1 -DHAVE_GETHOSTNAME=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRCSPN=1 -DHAVE_STRSTR=1 -DHAVE_STRTOLL=1 -DHAVE_ATOLL=1 -I.  -DSYSCONFDIR=\"/etc/refdb\" -DULLSPEC=\"%llu\" -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -c refdbib.c
refdbib.c: In function ‘make_cookedbib’:
refdbib.c:795: error: format not a string literal and no format arguments
refdbib.c:822: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_rawbib’:
refdbib.c:994: error: format not a string literal and no format arguments
refdbib.c:1029: error: format not a string literal and no format arguments
refdbib.c:1048: error: format not a string literal and no format arguments
refdbib.c:1082: error: format not a string literal and no format arguments
refdbib.c:1122: error: format not a string literal and no format arguments
refdbib.c:1130: error: format not a string literal and no format arguments
refdbib.c:1141: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1155: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_texbib’:
refdbib.c:1249: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1262: error: format not a string literal and no format arguments
refdbib.c:1273: error: format not a string literal and no format arguments
refdbib.c:1286: error: format not a string literal and no format arguments
refdbib.c:1317: error: format not a string literal and no format arguments
refdbib.c:1339: error: format not a string literal and no format arguments
refdbib.c:1396: error: format not a string literal and no format arguments
refdbib.c:1410: error: format not a string literal and no format arguments
refdbib.c:1427: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1433: error: format not a string literal and no format arguments
refdbib.c: In function ‘log_print’:
refdbib.c:1468: error: format not a string literal and no format arguments


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2012-10-02 15:14

Message:
Could you please specify which options you add to gcc? The error messages
apparently reflect the status of the last release. The line numbers differ
from the current svn version. In order to fix these problems I'd like to
reproduce this locally with the svn sources.

----------------------------------------------------------------------

Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 01:48

Message:
One cannot do:

      fprintf(stderr, get_status_msg(cs_status));

but instead

      fprintf(stderr, "%s", get_status_msg(cs_status));


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573758 ] No rule to make target `citationlistx/*.html', needed by `al

[SourceForge.net <no...@so...>]

Bugs item #3573758, was opened at 2012-10-02 02:58
Message generated for change (Tracker Item Submitted) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573758&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: No rule to make target `citationlistx/*.html', needed by `al

Initial Comment:
I cannot build refdb on my debian machine it fails with:


make[1]: Leaving directory `/home/mathieu/debian/debian-xml-sgml/packages/refdb/trunk/refdb-1.0/phpweb'
Making all in sru
make[1]: Entering directory `/home/mathieu/debian/debian-xml-sgml/packages/refdb/trunk/refdb-1.0/sru'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/mathieu/debian/debian-xml-sgml/packages/refdb/trunk/refdb-1.0/sru'
Making all in doc
make[1]: Entering directory `/home/mathieu/debian/debian-xml-sgml/packages/refdb/trunk/refdb-1.0/doc'
make[1]: *** No rule to make target `citationlistx/*.html', needed by `all-am'.  Stop.
make[1]: Leaving directory `/home/mathieu/debian/debian-xml-sgml/packages/refdb/trunk/refdb-1.0/doc'
make: *** [all-recursive] Error 1


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573758&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573740 ] refdb does not compile on debian

[SourceForge.net <no...@so...>]

Bugs item #3573740, was opened at 2012-10-02 01:48
Message generated for change (Comment added) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile on debian

Initial Comment:
By default on debian some stricter gcc options are used:


gcc -DPACKAGE_NAME=\"refdb\" -DPACKAGE_TARNAME=\"refdb\" -DPACKAGE_VERSION=\"1.0.0-pre2\" -DPACKAGE_STRING=\"refdb\ 1.0.0-pre2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"refdb\" -DVERSION=\"1.0.0-pre2\" -D_GNU_SOURCE=1 -DREADLINE42=1 -DHAVE_ICONV=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SOCKLEN_T=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_STRFTIME=1 -DHAVE_MKFIFO=1 -DHAVE_GETHOSTNAME=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRCSPN=1 -DHAVE_STRSTR=1 -DHAVE_STRTOLL=1 -DHAVE_ATOLL=1 -I.  -DSYSCONFDIR=\"/etc/refdb\" -DULLSPEC=\"%llu\" -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -c refdbib.c
refdbib.c: In function ‘make_cookedbib’:
refdbib.c:795: error: format not a string literal and no format arguments
refdbib.c:822: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_rawbib’:
refdbib.c:994: error: format not a string literal and no format arguments
refdbib.c:1029: error: format not a string literal and no format arguments
refdbib.c:1048: error: format not a string literal and no format arguments
refdbib.c:1082: error: format not a string literal and no format arguments
refdbib.c:1122: error: format not a string literal and no format arguments
refdbib.c:1130: error: format not a string literal and no format arguments
refdbib.c:1141: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1155: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_texbib’:
refdbib.c:1249: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1262: error: format not a string literal and no format arguments
refdbib.c:1273: error: format not a string literal and no format arguments
refdbib.c:1286: error: format not a string literal and no format arguments
refdbib.c:1317: error: format not a string literal and no format arguments
refdbib.c:1339: error: format not a string literal and no format arguments
refdbib.c:1396: error: format not a string literal and no format arguments
refdbib.c:1410: error: format not a string literal and no format arguments
refdbib.c:1427: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1433: error: format not a string literal and no format arguments
refdbib.c: In function ‘log_print’:
refdbib.c:1468: error: format not a string literal and no format arguments


----------------------------------------------------------------------

>Comment By: Mathieu Malaterre (malat)
Date: 2012-10-02 01:48

Message:
One cannot do:

      fprintf(stderr, get_status_msg(cs_status));

but instead

      fprintf(stderr, "%s", get_status_msg(cs_status));


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

[Refdb-devel] [ refdb-Bugs-3573740 ] refdb does not compile on debian

[SourceForge.net <no...@so...>]

Bugs item #3573740, was opened at 2012-10-02 01:48
Message generated for change (Tracker Item Submitted) made by malat
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mathieu Malaterre (malat)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile on debian

Initial Comment:
By default on debian some stricter gcc options are used:


gcc -DPACKAGE_NAME=\"refdb\" -DPACKAGE_TARNAME=\"refdb\" -DPACKAGE_VERSION=\"1.0.0-pre2\" -DPACKAGE_STRING=\"refdb\ 1.0.0-pre2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"refdb\" -DVERSION=\"1.0.0-pre2\" -D_GNU_SOURCE=1 -DREADLINE42=1 -DHAVE_ICONV=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SOCKLEN_T=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_FILE_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_UNISTD_H=1 -DTIME_WITH_SYS_TIME=1 -DRETSIGTYPE=void -DHAVE_STRFTIME=1 -DHAVE_MKFIFO=1 -DHAVE_GETHOSTNAME=1 -DHAVE_SELECT=1 -DHAVE_SOCKET=1 -DHAVE_STRCSPN=1 -DHAVE_STRSTR=1 -DHAVE_STRTOLL=1 -DHAVE_ATOLL=1 -I.  -DSYSCONFDIR=\"/etc/refdb\" -DULLSPEC=\"%llu\" -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -O2 -c refdbib.c
refdbib.c: In function ‘make_cookedbib’:
refdbib.c:795: error: format not a string literal and no format arguments
refdbib.c:822: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_rawbib’:
refdbib.c:994: error: format not a string literal and no format arguments
refdbib.c:1029: error: format not a string literal and no format arguments
refdbib.c:1048: error: format not a string literal and no format arguments
refdbib.c:1082: error: format not a string literal and no format arguments
refdbib.c:1122: error: format not a string literal and no format arguments
refdbib.c:1130: error: format not a string literal and no format arguments
refdbib.c:1141: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1155: error: format not a string literal and no format arguments
refdbib.c: In function ‘make_texbib’:
refdbib.c:1249: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1262: error: format not a string literal and no format arguments
refdbib.c:1273: error: format not a string literal and no format arguments
refdbib.c:1286: error: format not a string literal and no format arguments
refdbib.c:1317: error: format not a string literal and no format arguments
refdbib.c:1339: error: format not a string literal and no format arguments
refdbib.c:1396: error: format not a string literal and no format arguments
refdbib.c:1410: error: format not a string literal and no format arguments
refdbib.c:1427: warning: format ‘%d’ expects type ‘int’, but argument 3 has type ‘size_t’
refdbib.c:1433: error: format not a string literal and no format arguments
refdbib.c: In function ‘log_print’:
refdbib.c:1468: error: format not a string literal and no format arguments


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3573740&group_id=26091

[Refdb-devel] [ refdb-Bugs-3411615 ] refdb does not compile after libdbi-0.8.4 install

[SourceForge.net <no...@so...>]

Bugs item #3411615, was opened at 2011-09-19 22:40
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile after libdbi-0.8.4 install

Initial Comment:
After Installation of libdbi-0.8.4, and compilation and installation of libdbi-drivers 0.8.3-1, compilation of refdb (revision 718, but also revision 751)  fails.
see attached file for details.

----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2011-09-20 20:43

Message:
fixed in svn revision 753

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2011-09-20 09:02

Message:
My bad. This is a consequence of trying to fix the library versioning
information of libdbi as of 0.8.4. LIB_CURRENT had to be bumped to 1 in
order to upgrade application packages linked against libdbi properly.
However, RefDB expected libdbi versions with LIB_CURRENT=1 to have the new
instance-based interface. This will now be available as of LIB_CURRENT=2.
The quick fix is to edit all occurrences of the LIB_CURRENT check in the
RefDB sources, i.e. replace

LIBDBI_LIB_CURRENT < 1

with

LIBDBI_LIB_CURRENT < 2

There are 5 occurrences in src/dbfncs.c and one in refdbd.h.in. This
should fix the problem. I'll check in fixed RefDB sources asap.

----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2011-09-19 22:42

Message:
Sorry, forgot to mention: with libdbl-0.8.3 everything works. OS: slackware
13.7-x86_64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

[Refdb-devel] [ refdb-Bugs-3411615 ] refdb does not compile after libdbi-0.8.4 install

[SourceForge.net <no...@so...>]

Bugs item #3411615, was opened at 2011-09-19 22:40
Message generated for change (Settings changed) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
>Assigned to: Markus Hoenicka (mhoenicka)
Summary: refdb does not compile after libdbi-0.8.4 install

Initial Comment:
After Installation of libdbi-0.8.4, and compilation and installation of libdbi-drivers 0.8.3-1, compilation of refdb (revision 718, but also revision 751)  fails.
see attached file for details.

----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2011-09-20 09:02

Message:
My bad. This is a consequence of trying to fix the library versioning
information of libdbi as of 0.8.4. LIB_CURRENT had to be bumped to 1 in
order to upgrade application packages linked against libdbi properly.
However, RefDB expected libdbi versions with LIB_CURRENT=1 to have the new
instance-based interface. This will now be available as of LIB_CURRENT=2.
The quick fix is to edit all occurrences of the LIB_CURRENT check in the
RefDB sources, i.e. replace

LIBDBI_LIB_CURRENT < 1

with

LIBDBI_LIB_CURRENT < 2

There are 5 occurrences in src/dbfncs.c and one in refdbd.h.in. This
should fix the problem. I'll check in fixed RefDB sources asap.

----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2011-09-19 22:42

Message:
Sorry, forgot to mention: with libdbl-0.8.3 everything works. OS: slackware
13.7-x86_64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

[Refdb-devel] [ refdb-Bugs-3411615 ] refdb does not compile after libdbi-0.8.4 install

[SourceForge.net <no...@so...>]

Bugs item #3411615, was opened at 2011-09-19 20:40
Message generated for change (Comment added) made by akusmin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Nobody/Anonymous (nobody)
Summary: refdb does not compile after libdbi-0.8.4 install

Initial Comment:
After Installation of libdbi-0.8.4, and compilation and installation of libdbi-drivers 0.8.3-1, compilation of refdb (revision 718, but also revision 751)  fails.
see attached file for details.

----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2011-09-19 20:42

Message:
Sorry, forgot to mention: with libdbl-0.8.3 everything works. OS: slackware
13.7-x86_64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

[Refdb-devel] [ refdb-Bugs-3411615 ] refdb does not compile after libdbi-0.8.4 install

[SourceForge.net <no...@so...>]

Bugs item #3411615, was opened at 2011-09-19 20:40
Message generated for change (Tracker Item Submitted) made by akusmin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Nobody/Anonymous (nobody)
Summary: refdb does not compile after libdbi-0.8.4 install

Initial Comment:
After Installation of libdbi-0.8.4, and compilation and installation of libdbi-drivers 0.8.3-1, compilation of refdb (revision 718, but also revision 751)  fails.
see attached file for details.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3411615&group_id=26091

[Refdb-devel] [ refdb-Bugs-3222178 ] keyword scan too unspecific

[SourceForge.net <no...@so...>]

Bugs item #3222178, was opened at 2011-03-18 10:15
Message generated for change (Tracker Item Submitted) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3222178&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Markus Hoenicka (mhoenicka)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: keyword scan too unspecific

Initial Comment:
The keyword scan needs to be reworked as it is too unspecific. If there is a keyword "rat", the keyword will be assigned to articles that e.g. contain the word "regenerative" in their title. The code should be reworked to match only entire words

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=3222178&group_id=26091

[Refdb-devel] [ refdb-Bugs-1951835 ] risx url multiplying

[SourceForge.net <no...@so...>]

Bugs item #1951835, was opened at 2008-04-25 18:32
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=1951835&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Damien Jade Duff (damienjadeduff)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: risx url multiplying

Initial Comment:
Hiya!

Sorry but got another one here for the pile!

Now I'm using sqlite here and the issue seems similar to a previous one in which it wasn't refdb but libdbi. 

If I UPDATE a reference using refdbc that already has a LINK TYPE="url" but I have changed the url (i.e. the update is one in which the url changes), the url tag multiplies - I get another tag, one with the old url, one with the new. I presume I can get any number of them but I haven't checked. The way I judge the intended behaviour of updateref, an update should swap the reference with everything in the RIS tag and drop the old information. Whaddya reckon? Details below.

Cheerios!
Damien

SETUP:

refdb-1.0.0-pre1 (also happening on the svn as of this morning)
libdbi-cvs-20080421
libdbi-drivers-cvs-20080421
sqlite-3.5.8
Linux acws-0175 2.6.9-67.0.7.ELsmp #1 SMP Sat Mar 15 06:54:55 EDT 2008 i686 i686 i386 GNU/Linux

EXAMPLE:

mycomp% cat thisisatest2.risx
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN" "http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://www.cs.unc.edu/~welch/kalman/media/pdf/Julier1997_SPIE_KF.pdf</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes></notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% refdbc -d djdphd -u djd -w abc -C addref -A risx < thisisatest2.risx
999:1 added:0 skipped:0 failed
mycomp% refdbc -d djdphd -u djd -w abc -C getref -t risx :CK:=THISISATEST > testout1.risx
999:1 retrieved:0 failed
mycomp% cat testout1.risx
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN" "http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" id="209" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://www.cs.unc.edu/~welch/kalman/media/pdf/Julier1997_SPIE_KF.pdf</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% cat thisisatest.risx
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN" "http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" id="196" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://tinyurl.com/4dqojq</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes>bibtex doesn't seem to like all the escape characters refdb puts in the original URL so we switch to tinurl for now...</notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% refdbc -d djdphd -u djd -w abc -C updateref -A risx < thisisatest.risx
999:1 updated:0 added:0 skipped:0 failed
mycomp% refdbc -d djdphd -u djd -w abc -C getref -t risx :CK:=THISISATEST > testout2.risx
999:1 retrieved:0 failed
mycomp% cat testout2.risx
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN" "http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" id="209" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://tinyurl.com/4dqojq</link>
        <link type="url">http://www.cs.unc.edu/~welch/kalman/media/pdf/Julier1997_SPIE_KF.pdf</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes>bibtex doesn't seem to like all the escape characters refdb puts in the original URL so we switch to tinurl for now...</notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2011-03-09 06:31

Message:
CbOMe1  <a href="http://jcbmzlajqoyl.com/">jcbmzlajqoyl</a>,
[url=http://istruweloufy.com/]istruweloufy[/url],
[link=http://jgcaxqmvkzdg.com/]jgcaxqmvkzdg[/link],
http://yizhxnypuhmv.com/

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2008-04-29 22:11

Message:
Logged In: YES 
user_id=85809
Originator: NO

Hi again,

I've checked in a fix which resolves the URL duplication (and hopefully
doesn't break anything else), as well as an updated installation chapter
which avoids naming the dump file versions explicitly. I'm going to close
this bug, but feel free to reopen it if updating references should still
fail on your box.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2008-04-29 19:55

Message:
Logged In: YES 
user_id=85809
Originator: NO

Hi,

lets go through your tests one by one:

Part 1: URL duplication
I'm afraid I made an error when checking the URL duplication stuff.
Apparently I updated an existing entry with the original dataset - this
reproducibly does not duplicate the URL. However, if I follow your
instructions step by step, I do see the duplicate. I'll provide a fix
asap.

Part 2: refdb main database file creation
If the manual still mentions refdb.2.dump.sqlite, the information is
outdated. I'll try and rewrite the sections so I don't have to update them
with each new version of the dump files. Indeed, refdb.3.dump.sqlite is the
current version which should work ok.

Part 3: refdbd -a
As for upgrading from a main database version 2 to version 3, there was
indeed a bug caused by an incomplete migration to the latest libdbi
version. I've fixed that in svn, and I can successfully update a sqlite3
main database.

Other stuff:
I had forgotten to check in refdbrtfrc.  It should pop up next time you
upgrade your svn version.

regards,
Markus



----------------------------------------------------------------------

Comment By: Damien Jade Duff (damienjadeduff)
Date: 2008-04-29 16:51

Message:
Logged In: YES 
user_id=2066694
Originator: YES

Oh, hi
Incidentally, I should mention that the same stuff also happens if I don't
ever add the ~/simplerisx.risx file, which only is an older version of risx
because I used an older xml skeleton and haven't updated. I just was using
it to check that the system was working.
Peace
Damien

----------------------------------------------------------------------

Comment By: Damien Jade Duff (damienjadeduff)
Date: 2008-04-29 16:43

Message:
Logged In: YES 
user_id=2066694
Originator: YES

Hi there!

Thanks very much for your reply! I appreciate you taking a look!

I was, it is true, using 0.9.9-1 when I first started using refdb again
recently, but I'm now using the svn. But the thing is I put the refs into
the DB by adding an old dumped RISX file into an empty DB (I give an
example below).

I was thinking that it may be my route to installation that is specific?
Since 'refdbd -a' segfaults (not sure why, but details below - part *3) and
refdb complains that a DB created with refdb.2.dump.sqlite is an out of
date DB (again below, part *2 - though I think the manual still refers to
refdb.2.dump.sqlite), I was creating a basic refdb DB using the provided
sql file refdb.3.dump.sqlite (full details below, part *1, including a
replication of bug 1951835 after creating a new DB from scratch) - which
*seemed* to produce the desired results, except for the bugs I mentioned
which made themselves apparent later, so I had (perhaps foolishingly)
assumed it was the way to go.

The other two things that are unique about my install is that I'm using my
own database file directory for the embedded DB, and the whole install was
done onto a user owned file system (i.e. nothing from root). I'm not sure
if that would make any difference. ALSO, in the source directory I needed
to go to /etc and type "touch refdbrtfrc" as the make script seemed to need
it but it wasn't there, and I renamed the man and doc directories (and put
in dummy Makefiles) so that it would compile without the docs (again, I
don't think any of that should make a difference?).

Anyway, I'll just put the logs of my journey, from DB creation to
insertion, below, and hope the tale will amuse...

Cheerios!
Damien

**** FIRST PART *1 - REFDB.3.DUMP.SQLITE + DUPLICATED URLS ****

mycomp% ls

mycomp% sqlite3 refdb < ~/HD/binary/share/refdb/sql/refdb.3.dump.sqlite

mycomp% ls
refdb

** (start refdbd in another window) **

mycomp% refdbd -s -l 7 -e 0
dbi_driver_dir went to:

dbi is up using default driver dir
Available libdbi database drivers:
pgsql
sqlite3
Requested libdbi driver found:
sqlite3
Database directory:
/data/private/djd/Library/ReferenceDatabaseSqlite3/
application server started
share extended notes by default
use /tmp/refdbd_fifo8917 as fifo
server waiting n_max_fd=4

** (back to original window) **

mycomp% refdba
refdba: createdb djdphd
999:1 created:0 failed
refdba: quit

mycomp% ls
DB_VERSION  djdphd  refdb

mycomp% refdbc -u 132 -w 123 -C addref -A risx < ~/simplerisx.risx
999:1 added:0 skipped:0 failed
mycomp% refdbc -u 132 -w 123 -C addref -A risx < ~/thisisatest2.risx
999:1 added:0 skipped:0 failed
mycomp% refdbc -u 132 -w 123 -C updateref -A risx < ~/thisisatest.risx
999:1 updated:0 added:0 skipped:0 failed
mycomp% refdbc -u 132 -w 123 -C getref -t risx :ID:\>0 >
~/aftertesting.risx
999:2 retrieved:0 failed
mycomp% cat ~/aftertesting.risx
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN"
"http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="GEN" id="1" citekey="TESTY">
    <part>
      <title type="full"/>
    </part>
    <publication>
      <title type="full">test1</title>
      <author>
        <name>testa testb</name>
      </author>
      <pubinfo>
        <pubdate type="primary">
          <date><year>2008</year><month>00</month><day>00</day></date>
        </pubdate>
      </pubinfo>
    </publication>
  </entry>


  <entry type="CONF" id="2" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear
Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and
Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://tinyurl.com/4dqojq</link>
        <link
type="url">http://www.cs.unc.edu/~welch/kalman/media/pdf/Julier1997_SPIE_KF.pdf</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes>bibtex doesn't seem to like all the escape characters refdb
puts in the original URL so we switch to tinurl for now...</notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% cat ~/thisisatest2.risx

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN"
"http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear
Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and
Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link
type="url">http://www.cs.unc.edu/~welch/kalman/media/pdf/Julier1997_SPIE_KF.pdf</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes></notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% cat ~/thisisatest.risx

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.2.0//EN"
"http://refdb.sourceforge.net/dtd/risx-1.2.0/risx.dtd" [
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
<!ENTITY mdash "&#x2014;">
<!ENTITY lsquo "&#x2018;">
<!ENTITY rsquo "&#x2019;">
]>
<ris>



  <entry type="CONF" id="196" citekey="THISISATEST">
    <part>
      <title type="full">A New Extension of the Kalman Filter to Nonlinear
Systems</title>
      <author role="author">
        <name>Simon J. Julier</name>
      </author>
      <author role="author">
        <name>Jeffrey K. Uhlmann</name>
      </author>
    </part>
    <publication>
      <title type="full">Int. Symp. Aerospace/Defense Sensing, Simul. and
Controls</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>1997</year><month>00</month><day>00</day></date>
        </pubdate>
        <city>Orlando, Florida</city>
        <link type="url">http://tinyurl.com/4dqojq</link>
      </pubinfo>
    </publication>
    <libinfo user="djd">
      <notes>bibtex doesn't seem to like all the escape characters refdb
puts in the original URL so we switch to tinurl for now...</notes>
      <reprint status="INFILE"/>
      <availability type="useroot"/>
    </libinfo>
    <contents>
      <keyword>bayesian</keyword>
      <keyword>kalman</keyword>
      <keyword>non-linear</keyword>
      <keyword>nonlinear</keyword>
      <keyword>probability</keyword>
      <keyword>recursive estimation</keyword>
      <keyword>tracking</keyword>
      <keyword>unscented</keyword>
    </contents>
  </entry>
</ris>

mycomp% cat ~/simplerisx.risx

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ris PUBLIC "-//Markus Hoenicka//DTD Ris V1.0.2//EN"
"/data/private/djd/binary/share/refdb/dtd/risx.dtd"
[
<!ENTITY lt "&#38;#60;">
<!ENTITY gt "&#62;">
<!ENTITY amp "&#38;#38;">
]>
<ris>
        <entry type="GEN" citekey="TESTY">
                <publication>
                        <title type="full">test1</title>
                        <author>
                                <name>testa testb</name>
                        </author>
                        <pubinfo>
                                <pubdate>
                                        <date>
                                                <year>2008</year>
                                                <month></month>
                                                <day></day>
                                        </date>
                                </pubdate>

                        </pubinfo>
                </publication>

        </entry>
</ris>

mycomp%

**** SECOND PART *2 - REFDB.2.DUMP.SQLITE ****

(go to other window and close refdbd)
(then come back)

mycomp% pwd
/data/private/djd/Library/ReferenceDatabaseSqlite3
mycomp% rm *
mycomp% sqlite3 refdb < ~/HD/binary/share/refdb/sql/refdb.2.dump.sqlite

** (go back now and restart refdbd) **

mycomp% refdbd -s -l 7 -e 0
dbi_driver_dir went to:

dbi is up using default driver dir
Available libdbi database drivers:
pgsql
sqlite3
Requested libdbi driver found:
sqlite3
Database directory:
/data/private/djd/Library/ReferenceDatabaseSqlite3/
application server started
share extended notes by default
use /tmp/refdbd_fifo9031 as fifo
server waiting n_max_fd=4

** (and now back to original window) **

mycomp% refdba
refdba: createdb djdphd
main database version is not supported
refdba: quit

**** THIRD PART *3 - REFDBD -A ****

** (go to other window and close refdbd)** 
** (then come back) **

mycomp% pwd
/data/private/djd/Library/ReferenceDatabaseSqlite3

mycomp% rm *

mycomp% refdbd -a -e 0 -l 7
dbi_driver_dir went to:

dbi is up using default driver dir
Available libdbi database drivers:
pgsql
sqlite3
Requested libdbi driver found:
sqlite3
Database directory:
/data/private/djd/Library/ReferenceDatabaseSqlite3/
check main database version
localhost
djd



sqlite3
/data/private/djd/Library/ReferenceDatabaseSqlite3/
UTF-8
Segmentation fault
mycomp%

**** SYSTEM INFO ****

mycomp% refdbd -v
refdbd 1.0.0-pre1 built from svn revision 613 ma...@mh...
You may redistribute and modify this software under the terms of the GNU
General Public License.
mycomp% refdbc -v
refdbc 1.0.0-pre1 built from svn revision 613 ma...@mh...
You may redistribute and modify this software under the terms of the GNU
General Public License.
mycomp% refdba -v
refdba 1.0.0-pre1 built from svn revision 613 ma...@mh...
You may redistribute and modify this software under the terms of the GNU
General Public License.
mycomp% uname -a
Linux mycomp 2.6.9-67.0.7.ELsmp #1 SMP Sat Mar 15 06:54:55 EDT 2008 i686
i686 i386 GNU/Linux
mycomp%

LIBDBI:
libdbi-cvs-20080421
libdbi-drivers-cvs-20080421

mycomp% cat ~/HD/binary/etc/refdb/refdbdrc | sed s/^#.\*\$// | grep '.'
refdblib /data/private/djd/binary/share/refdb
main_db refdb
serverip        localhost
dbsport
dbserver        sqlite3
dbpath          /data/private/djd/Library/ReferenceDatabaseSqlite3/
port    9734
logfile /data/private/djd/binary/var/log/refdbd.log
logdest file
loglevel info
pidfile         /data/private/djd/binary/var/run/refdbd.pid
remoteadmin f
remoteconnect f
keep_pnames t
keyword_scan f
db_encoding     UTF-8
in_encoding     UTF-8

mycomp% cat ~/.refdbarc | sed s/^#.\*\$// | grep '.'
serverip        127.0.0.1
port    9734
pager   less
username  root
passwd
logdest file
loglevel info
logfile /data/private/djd/binary/var/log/refdba.log

mycomp% cat ~/.refdbcrc | sed s/^#.\*\$// | grep '.'
serverip        127.0.0.1
port    9734
pager   less
passwd *
defaultdb       djdphd
pdfroot /data/private/djd/Library
logdest file
loglevel info
logfile /data/private/djd/binary/var/log/refdbc.log
cssurl /data/private/djd/binary/share/refdb/css/refdb.css
fromencoding UTF-8
toencoding UTF-8



----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2008-04-27 20:48

Message:
Logged In: YES 
user_id=85809
Originator: NO

I guess this is sort of a duplicate of #1951049. If you missed the upgrade
notice from 0.9.8 or earlier to 0.9.9 or later, I reckon you'd see this
kind of problem. Please see the comments to bug #1951049 for further
instructions.

regards,
Markus

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=1951835&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 19:26
Message generated for change (Comment added) made by akusmin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

>Comment By: akusmin (akusmin)
Date: 2010-06-04 09:27

Message:
1) I checked again whether with refdb-0.9.9-1.tar.gz doing "updateref"
makes an user-added reserved word  without a dot in the bibliography. Yes,
it does. So, I was wrong when in the first post  I said updateref did not
help.

2)  Actually, from the practical point of view it is not a big issue: the
list of reserved words is indeed rather complete.  On a rare occasion when
one has to add a new reserved words one could just use updateref on all
citations. (Or delete databases and recreate them, that's what I did).  
It's just the necessity to run updateref must be mentioned/stressed in
docs.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-06-04 08:48

Message:
I see the problem. There was no way for you to know that you need to run
updateref after adding reserved words as I can't expect you to know the
innards of RefDB. However, the current behaviour is pretty much a design
issue. In terms of computing time, it is prudent to perform time-consuming
tasks once (when you add a reference) instead of multiple times (when you
retrieve references or build bibliographies). I do understand that it is
inconvenient if you add several references using words which are not yet
known to the database without realizing this fact after the first
reference. I personally run getref after each addref just to make sure the
datasets arrived ok. I'll try to figure out a better way to deal with this.
I could make refdbd run a background task to automatically update affected
journal titles after adding reserved words, just like it runs a background
task to check titles and abstracts for existing keywords after each addref
command.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2010-06-03 19:57

Message:
Hi. I found out why the bibliography generated after new reserved words
were added via "addword"  was exactly the same as before.
You said that you did "updateref" after you added a new reserved word.  I
did not.
At least in the manual for 0.9.9-1 there is 
nothing said about the necessity to run "updateref" whenever you use
addword/deleteword.

See, I thought that  in the process of generation of the bibliography
every citation is checked against the list of the reserved words.
Therefore, any change in the list of the reserved words does not require
updating citations. 
>From the fact that "updateref" is required I conclude that  1) the form in
which the citation is stored internally *depends* on the list of the
reserved words 2) hence, generation of the bibliography does not involve
consulting the list of reserved words.

In my opinion the necessity to use updateref is not convenient,   (I *have
to know* in which file I have the citation  to make the new reserved word
to have an effect on the freshly produced latex article). 


Anyway, revision 718 works for me on Slackware. Thank you) 


----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2010-05-26 07:43

Message:
Thank you, Markus. In the next several days I'll try to reproduce the
problem.  

Well, I use refdb-0.9.9-1.tar.gz , which is about  3 years old. On the
other hand, perhaps I could have introduced the problem myself by manually
changing permissions for some refDB directories in /var.  
OK, I'll write again when I have more info.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-25 22:07

Message:
I've checked the code again - there is nothing wrong with updating the
journal synonyms. The current (and correct) behaviour has been around for
at least three years. 

I've tried to reproduce your problem to no avail. I added a random journal
article containing "Solid" in the fake journal abbreviation. Next I've
added "SOLID" to the list of abbreviated words. I've then updated the
article without changing anything in the RIS dataset. Next time I retrieved
it, "Solid" was written without a trailing dot, as expected.

Could you please create a test kit with some sample data and an exact list
of commands which reproduces your problem. I'll be happy to try again.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 09:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 21:26
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-06-04 10:48

Message:
I see the problem. There was no way for you to know that you need to run
updateref after adding reserved words as I can't expect you to know the
innards of RefDB. However, the current behaviour is pretty much a design
issue. In terms of computing time, it is prudent to perform time-consuming
tasks once (when you add a reference) instead of multiple times (when you
retrieve references or build bibliographies). I do understand that it is
inconvenient if you add several references using words which are not yet
known to the database without realizing this fact after the first
reference. I personally run getref after each addref just to make sure the
datasets arrived ok. I'll try to figure out a better way to deal with this.
I could make refdbd run a background task to automatically update affected
journal titles after adding reserved words, just like it runs a background
task to check titles and abstracts for existing keywords after each addref
command.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2010-06-03 21:57

Message:
Hi. I found out why the bibliography generated after new reserved words
were added via "addword"  was exactly the same as before.
You said that you did "updateref" after you added a new reserved word.  I
did not.
At least in the manual for 0.9.9-1 there is 
nothing said about the necessity to run "updateref" whenever you use
addword/deleteword.

See, I thought that  in the process of generation of the bibliography
every citation is checked against the list of the reserved words.
Therefore, any change in the list of the reserved words does not require
updating citations. 
>From the fact that "updateref" is required I conclude that  1) the form in
which the citation is stored internally *depends* on the list of the
reserved words 2) hence, generation of the bibliography does not involve
consulting the list of reserved words.

In my opinion the necessity to use updateref is not convenient,   (I *have
to know* in which file I have the citation  to make the new reserved word
to have an effect on the freshly produced latex article). 


Anyway, revision 718 works for me on Slackware. Thank you) 


----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2010-05-26 09:43

Message:
Thank you, Markus. In the next several days I'll try to reproduce the
problem.  

Well, I use refdb-0.9.9-1.tar.gz , which is about  3 years old. On the
other hand, perhaps I could have introduced the problem myself by manually
changing permissions for some refDB directories in /var.  
OK, I'll write again when I have more info.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-26 00:07

Message:
I've checked the code again - there is nothing wrong with updating the
journal synonyms. The current (and correct) behaviour has been around for
at least three years. 

I've tried to reproduce your problem to no avail. I added a random journal
article containing "Solid" in the fake journal abbreviation. Next I've
added "SOLID" to the list of abbreviated words. I've then updated the
article without changing anything in the RIS dataset. Next time I retrieved
it, "Solid" was written without a trailing dot, as expected.

Could you please create a test kit with some sample data and an exact list
of commands which reproduces your problem. I'll be happy to try again.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 11:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 19:26
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2010-06-03 19:57

Message:
Hi. I found out why the bibliography generated after new reserved words
were added via "addword"  was exactly the same as before.
You said that you did "updateref" after you added a new reserved word.  I
did not.
At least in the manual for 0.9.9-1 there is 
nothing said about the necessity to run "updateref" whenever you use
addword/deleteword.

See, I thought that  in the process of generation of the bibliography
every citation is checked against the list of the reserved words.
Therefore, any change in the list of the reserved words does not require
updating citations. 
>From the fact that "updateref" is required I conclude that  1) the form in
which the citation is stored internally *depends* on the list of the
reserved words 2) hence, generation of the bibliography does not involve
consulting the list of reserved words.

In my opinion the necessity to use updateref is not convenient,   (I *have
to know* in which file I have the citation  to make the new reserved word
to have an effect on the freshly produced latex article). 


Anyway, revision 718 works for me on Slackware. Thank you) 


----------------------------------------------------------------------

Comment By: akusmin (akusmin)
Date: 2010-05-26 07:43

Message:
Thank you, Markus. In the next several days I'll try to reproduce the
problem.  

Well, I use refdb-0.9.9-1.tar.gz , which is about  3 years old. On the
other hand, perhaps I could have introduced the problem myself by manually
changing permissions for some refDB directories in /var.  
OK, I'll write again when I have more info.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-25 22:07

Message:
I've checked the code again - there is nothing wrong with updating the
journal synonyms. The current (and correct) behaviour has been around for
at least three years. 

I've tried to reproduce your problem to no avail. I added a random journal
article containing "Solid" in the fake journal abbreviation. Next I've
added "SOLID" to the list of abbreviated words. I've then updated the
article without changing anything in the RIS dataset. Next time I retrieved
it, "Solid" was written without a trailing dot, as expected.

Could you please create a test kit with some sample data and an exact list
of commands which reproduces your problem. I'll be happy to try again.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 09:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 19:26
Message generated for change (Comment added) made by akusmin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

>Comment By: akusmin (akusmin)
Date: 2010-05-26 07:43

Message:
Thank you, Markus. In the next several days I'll try to reproduce the
problem.  

Well, I use refdb-0.9.9-1.tar.gz , which is about  3 years old. On the
other hand, perhaps I could have introduced the problem myself by manually
changing permissions for some refDB directories in /var.  
OK, I'll write again when I have more info.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-25 22:07

Message:
I've checked the code again - there is nothing wrong with updating the
journal synonyms. The current (and correct) behaviour has been around for
at least three years. 

I've tried to reproduce your problem to no avail. I added a random journal
article containing "Solid" in the fake journal abbreviation. Next I've
added "SOLID" to the list of abbreviated words. I've then updated the
article without changing anything in the RIS dataset. Next time I retrieved
it, "Solid" was written without a trailing dot, as expected.

Could you please create a test kit with some sample data and an exact list
of commands which reproduces your problem. I'll be happy to try again.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 09:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 21:26
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-26 00:07

Message:
I've checked the code again - there is nothing wrong with updating the
journal synonyms. The current (and correct) behaviour has been around for
at least three years. 

I've tried to reproduce your problem to no avail. I added a random journal
article containing "Solid" in the fake journal abbreviation. Next I've
added "SOLID" to the list of abbreviated words. I've then updated the
article without changing anything in the RIS dataset. Next time I retrieved
it, "Solid" was written without a trailing dot, as expected.

Could you please create a test kit with some sample data and an exact list
of commands which reproduces your problem. I'll be happy to try again.

regards,
Markus

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 11:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 21:26
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: refdbd
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
>Assigned to: Markus Hoenicka (mhoenicka)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-05-17 11:56

Message:
I'll have to run a few tests, but it looks like there is a bug in the
insert_periodical() function. As far as I understand the source code, the
function adds additional synonyms when updating, but it won't touch
existing synonyms even if a corrected version is provided. Obviously,
updateref should update synonyms if they need to be changed. I'll look into
this. Also, adding reserved words is no big deal. Feel free to throw
further words my way .

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Feature Requests-3000131 ] "addword" - make new reserved words available

[SourceForge.net <no...@so...>]

Feature Requests item #3000131, was opened at 2010-05-11 19:26
Message generated for change (Tracker Item Submitted) made by akusmin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: akusmin (akusmin)
Assigned to: Nobody/Anonymous (nobody)
Summary: "addword" - make new reserved words available

Initial Comment:
Hello!
I had to add some reserved words using the addword command. 
The problem: after I added  new reserved words (e.g. Solid, State, and Ionics), even after I used the "updateref" commando,
the latex  bibliography is still created with "Solid.State.Ionics" as journal abbreviation.
The only solution I found so far is to delete the database and recreate it. 

Request/Question Could you add / Is there any simpler way to take into account new reserved words? 
If there is already such way, could add this information to the manual?

Thank you!

P.S.
please consider adding the following words into the default list (some of them may be in this list of the development version I guess)

MACROMOLECULES
MATTER
SOLID
STATE
IONICS


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385994&aid=3000131&group_id=26091

[Refdb-devel] [ refdb-Bugs-2945806 ] RISX of a conference entry should use "periodical name"

[SourceForge.net <no...@so...>]

Bugs item #2945806, was opened at 2010-02-04 09:48
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
Assigned to: Markus Hoenicka (mhoenicka)
Summary: RISX of a conference entry should use "periodical name"

Initial Comment:
Currently the T2 field is used as publication title in RISX exports of CONF entries.  According to Refman specs, this is the conference name, however, the proceedings title seems to be more appropriate which is in the JO/JF field.

----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-11 01:30

Message:
I've changed the risx DTD to include a conftitle element. I've also changed
the refdbd sources to properly import and export this element.

----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-10 00:50

Message:
Your analysis is correct. I've checked in a patch for backend.c which lets
the risx backend export the conference proceedings title rather than the
conference title. As you correctly point out, the conference title is lost
in the output at the moment. I think the proper way to fix this is to add a
"conftitle" element to the pubinfo element in the risx DTD.

----------------------------------------------------------------------

Comment By: Torsten Bronger (bronger)
Date: 2010-02-05 08:45

Message:
Unfortunately, it is even more complicated than in my first post.

Conferences have four titles: Article title, proceedings title, conference
name, and series title.  However, RISX has only three levels.  The question
is how to fill the title field in the second level, i.e. the publication
title.  Note that CONF is the only citation type with four titles, which is
probably the reason why this hasn't been a big deal so far.

Currently, RefDB takes the conference name for the pubtitle, i.e. the T2
field of the RIS dataset.  This is not bad, but: Any JO/JF field is not
exported to RISX, although it would contain the proceedings title, which is
certainly important, too.

I don't know exactly how to solve this.  A possible remedy can be to
export whatever is filled in JF/T2, with JF having higher priority, and to
document that RISX can't export both the conference name and the
proceedings title at the same time.  This is very compatible with current's
bahaviour and should do what people expect in almost any case.

You asked for an example.  The following RIS dataset:

TY  - CONF
ID  - Bronger2010
AU  - Bronger,T.
TI  - My Article's Title
JO  - Sup.Conf.Proc.
RP  - NOT IN FILE
T2  - Super Conference
PY  - 2010///
ER  - 

is exported to RISX as:

<ris>
  <entry type="CONF" id="4" citekey="Bronger2010">
    <part>
      <title type="full">My Article's Title</title>
      <author role="author">
        <lastname>Bronger</lastname>
        <firstname>T</firstname>
      </author>
    </part>
    <publication>
      <title type="full">Super Conference</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>2010</year></date>
        </pubdate>
      </pubinfo>
    </publication>
    <libinfo user="refdb">
      <reprint status="NOTINFILE"/>
    </libinfo>
  </entry>
</ris>

Thus, the proceedings title is lost.


----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-05 00:54

Message:
I seem to be a bit dense here. Could you please provide an example RIS
input file, along with the current risx output and the risx output that
you'd prefer? I'll be happy to look into this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

[Refdb-devel] [ refdb-Bugs-2945806 ] RISX of a conference entry should use "periodical name"

[SourceForge.net <no...@so...>]

Bugs item #2945806, was opened at 2010-02-04 09:48
Message generated for change (Comment added) made by mhoenicka
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
>Assigned to: Markus Hoenicka (mhoenicka)
Summary: RISX of a conference entry should use "periodical name"

Initial Comment:
Currently the T2 field is used as publication title in RISX exports of CONF entries.  According to Refman specs, this is the conference name, however, the proceedings title seems to be more appropriate which is in the JO/JF field.

----------------------------------------------------------------------

>Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-10 00:50

Message:
Your analysis is correct. I've checked in a patch for backend.c which lets
the risx backend export the conference proceedings title rather than the
conference title. As you correctly point out, the conference title is lost
in the output at the moment. I think the proper way to fix this is to add a
"conftitle" element to the pubinfo element in the risx DTD.

----------------------------------------------------------------------

Comment By: Torsten Bronger (bronger)
Date: 2010-02-05 08:45

Message:
Unfortunately, it is even more complicated than in my first post.

Conferences have four titles: Article title, proceedings title, conference
name, and series title.  However, RISX has only three levels.  The question
is how to fill the title field in the second level, i.e. the publication
title.  Note that CONF is the only citation type with four titles, which is
probably the reason why this hasn't been a big deal so far.

Currently, RefDB takes the conference name for the pubtitle, i.e. the T2
field of the RIS dataset.  This is not bad, but: Any JO/JF field is not
exported to RISX, although it would contain the proceedings title, which is
certainly important, too.

I don't know exactly how to solve this.  A possible remedy can be to
export whatever is filled in JF/T2, with JF having higher priority, and to
document that RISX can't export both the conference name and the
proceedings title at the same time.  This is very compatible with current's
bahaviour and should do what people expect in almost any case.

You asked for an example.  The following RIS dataset:

TY  - CONF
ID  - Bronger2010
AU  - Bronger,T.
TI  - My Article's Title
JO  - Sup.Conf.Proc.
RP  - NOT IN FILE
T2  - Super Conference
PY  - 2010///
ER  - 

is exported to RISX as:

<ris>
  <entry type="CONF" id="4" citekey="Bronger2010">
    <part>
      <title type="full">My Article's Title</title>
      <author role="author">
        <lastname>Bronger</lastname>
        <firstname>T</firstname>
      </author>
    </part>
    <publication>
      <title type="full">Super Conference</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>2010</year></date>
        </pubdate>
      </pubinfo>
    </publication>
    <libinfo user="refdb">
      <reprint status="NOTINFILE"/>
    </libinfo>
  </entry>
</ris>

Thus, the proceedings title is lost.


----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-05 00:54

Message:
I seem to be a bit dense here. Could you please provide an example RIS
input file, along with the current risx output and the risx output that
you'd prefer? I'll be happy to look into this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

[Refdb-devel] [ refdb-Bugs-2945806 ] RISX of a conference entry should use "periodical name"

[SourceForge.net <no...@so...>]

Bugs item #2945806, was opened at 2010-02-04 09:48
Message generated for change (Comment added) made by bronger
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: refdbd
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Torsten Bronger (bronger)
Assigned to: Nobody/Anonymous (nobody)
Summary: RISX of a conference entry should use "periodical name"

Initial Comment:
Currently the T2 field is used as publication title in RISX exports of CONF entries.  According to Refman specs, this is the conference name, however, the proceedings title seems to be more appropriate which is in the JO/JF field.

----------------------------------------------------------------------

>Comment By: Torsten Bronger (bronger)
Date: 2010-02-05 08:45

Message:
Unfortunately, it is even more complicated than in my first post.

Conferences have four titles: Article title, proceedings title, conference
name, and series title.  However, RISX has only three levels.  The question
is how to fill the title field in the second level, i.e. the publication
title.  Note that CONF is the only citation type with four titles, which is
probably the reason why this hasn't been a big deal so far.

Currently, RefDB takes the conference name for the pubtitle, i.e. the T2
field of the RIS dataset.  This is not bad, but: Any JO/JF field is not
exported to RISX, although it would contain the proceedings title, which is
certainly important, too.

I don't know exactly how to solve this.  A possible remedy can be to
export whatever is filled in JF/T2, with JF having higher priority, and to
document that RISX can't export both the conference name and the
proceedings title at the same time.  This is very compatible with current's
bahaviour and should do what people expect in almost any case.

You asked for an example.  The following RIS dataset:

TY  - CONF
ID  - Bronger2010
AU  - Bronger,T.
TI  - My Article's Title
JO  - Sup.Conf.Proc.
RP  - NOT IN FILE
T2  - Super Conference
PY  - 2010///
ER  - 

is exported to RISX as:

<ris>
  <entry type="CONF" id="4" citekey="Bronger2010">
    <part>
      <title type="full">My Article's Title</title>
      <author role="author">
        <lastname>Bronger</lastname>
        <firstname>T</firstname>
      </author>
    </part>
    <publication>
      <title type="full">Super Conference</title>
      <pubinfo>
        <pubdate type="primary">
          <date><year>2010</year></date>
        </pubdate>
      </pubinfo>
    </publication>
    <libinfo user="refdb">
      <reprint status="NOTINFILE"/>
    </libinfo>
  </entry>
</ris>

Thus, the proceedings title is lost.


----------------------------------------------------------------------

Comment By: Markus Hoenicka (mhoenicka)
Date: 2010-02-05 00:54

Message:
I seem to be a bit dense here. Could you please provide an example RIS
input file, along with the current risx output and the risx output that
you'd prefer? I'll be happy to look into this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=385991&aid=2945806&group_id=26091