refdb-users — List for RefDB users

Re: [Refdb-users] Usual trouble - runbib says "error"

[Markus H. <mar...@mh...>]

Hi Jeremy,

I'm really sorry to hear that this is "usual trouble" on your end. It shouldn't
be, and I'll try my best to fix this.

Jeremy Malcolm <Je...@Ma...> was heard to say:

> runbib is aborting for me again with the unhelpful message "error", and
> I've gone through all the usual reasons why this always happens (eg.
> obviously missing fields in references I've added recently, stray colons
> in citation keys) to no avail.

You may have tried this already, but does the bug depend on a particular
citation? Does runbib finish ok if you remove one or some of the citations you
added most recently?

> When I run refdbd in debugging mode the
> last lines it shows as runbib spits out its error are:
>
> SELECT
>
thesis.t_author.author_name,thesis.t_author.author_lastname,thesis.t_author.author_firstname,thesis.t_author.author_middlename,thesis.t_author.author_suffix,thesis.t_xauthor.xauthor_role
> FROM thesis.t_author, thesis.t_xauthor WHERE
> thesis.t_author.author_id=thesis.t_xauthor.author_id AND
> thesis.t_xauthor.xauthor_type='primary' AND
> thesis.t_xauthor.refdb_id=416 ORDER BY t_xauthor.xauthor_position
> child finished client on fd 5
> child exited with code 1
> server waiting n_max_fd=4
>
> That same SELECT query appears a few times further up, in fact it almost
> seems to be stuck in a loop.

You may gain this impression because the bibliography code needs to access the
author names several times while formatting a bibliography entry - once for the
real bibliographic data, up to twice for the in-text citation if you use an
author/year style, and once for each multi-head citation if you use an
author/year style.

> There is nothing unusual about this record though, because I have lots
> of authors without firstnames, middlenames or suffixes, and neither is
> that from a reference that I added recently.
>
> What can I do to troubleshoot this further?
>

The easiest way to troubleshoot this is to modify refdbd to provide additional
debug information. refdbd does not seem to crash (otherwise the child would
return 0, not 1), so it is a matter of finding the call that returns an error
code and to step back from there. I'd like to reproduce this problem on my box.
Could you send me your reference database (as a RIS or risx file) or make it
available for download on some webspace? In addition to that I'll need the
basename.id.xml file that runbib creates. What platform are you running anyway?

regards,
Markus


-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] Usual trouble - runbib says "error"

[Jeremy M. <Je...@Ma...>]

runbib is aborting for me again with the unhelpful message "error", and 
I've gone through all the usual reasons why this always happens (eg. 
obviously missing fields in references I've added recently, stray colons 
in citation keys) to no avail.  When I run refdbd in debugging mode the 
last lines it shows as runbib spits out its error are:

SELECT 
thesis.t_author.author_name,thesis.t_author.author_lastname,thesis.t_author.author_firstname,thesis.t_author.author_middlename,thesis.t_author.author_suffix,thesis.t_xauthor.xauthor_role 
FROM thesis.t_author, thesis.t_xauthor WHERE 
thesis.t_author.author_id=thesis.t_xauthor.author_id AND 
thesis.t_xauthor.xauthor_type='primary' AND 
thesis.t_xauthor.refdb_id=416 ORDER BY t_xauthor.xauthor_position
child finished client on fd 5
child exited with code 1
server waiting n_max_fd=4

That same SELECT query appears a few times further up, in fact it almost 
seems to be stuck in a loop.  Its results are:

+-------------+-----------------+------------------+
| author_name | author_lastname | author_firstname |
+-------------+-----------------+------------------+
| ACA         | ACA             | NULL             |
+-------------+-----------------+------------------+ ...

-------------------+---------------+--------------+
  author_middlename | author_suffix | xauthor_role |
-------------------+---------------+--------------+
  NULL              | NULL          |              |
-------------------+---------------+--------------+

There is nothing unusual about this record though, because I have lots 
of authors without firstnames, middlenames or suffixes, and neither is 
that from a reference that I added recently.

What can I do to troubleshoot this further?

Thanks.

-- 
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

[Refdb-users] ANN: refdb-0.9.8-pre5 available for download, fixing possible segfault

[Markus H. <mar...@mh...>]

Markus Hoenicka writes:
 > You'll see the message "could not read to refdbd", usually after a few

Oh dear... s/read/write/

Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] ANN: refdb-0.9.8-pre5 available for download, fixing possible segfault

[Markus H. <mar...@mh...>]

Hi all,

get the latest prerelease of RefDB as usual:

http://refdb.sourceforge.net/pre/refdb-latest.tar.gz

This is a bugfix release for pre4. No new features, but a few memory
problems detected by valgrind were fixed. I recommend upgrading to
pre5 due to a possible segfault that affects 0.9.8-pre2 through
pre4. The symptoms and implications are described below.

regards,
Markus


Bug Alert
=========

Adding references with refdbc:addref may crash refdbd. The crash may
lead to the last reference before the crash being added incompletely,
thus causing a possible loss of data.

Symptoms:

You'll see the message "could not read to refdbd", usually after a few
references were added successfully. In addition, you should find a
refdbd dump file (refdbd.core on Unix-like systems,
refdbd.exe.stackdump on Windows) somewhere on your system.

Affected systems:

I never managed to bump into this problem on FreeBSD, but I
encountered it on Cygwin a couple of times. Other operating systems
may be affected as well.

Fix:

Avoid 0.9.8-pre2 through pre4 and upgrade to pre5 if you use one of
the affected prereleases. The latest release 0.9.7 is not affected.

If you ran into this problem previously, you can usually fix the
affected datasets by updating them (refdbc:updateref).



-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] ANN: refdb-0.9.8-dupcheck-pre1 available for testing

[Markus H. <mar...@mh...>]

Hi,

here's the first prerelease from the dupcheck branch of refdb, built
from repository revision 191:

http://refdb.sourceforge.net/pre/refdb-0.9.8-dupcheck-pre1.tar.gz

This prerelease is identical with 0.9.8-pre4, except for the new
checkref command which I'll explain shortly. I'd appreciate bug
reports and success stories with the dupcheck branch, as I'd like to
merge this code back to the trunk as soon as it turns out to be
functional and stable.

You don't need to install this prerelease in order to test it if you
have 0.9.8-pre4 installed. The new prerelease works with the same
databases and does not alter them when running checkref. All you need
to do is to download the tarball, configure and build it as usual, and
then run the server (./refdbd -s <other options>) and the client
(./refdbc <options>) from the src directory. Again, "make install"
should not be required, and I wouldn't recommend it at this time. If
you find some time, please export your references from your existing
database and add them to a new database using the new prerelease, then
query, update, and delete to your heart's content to check that
everything is working ok.

Now what is that new refdbc: checkref command? It is a simple way to
check your reference data for duplicates and faulty data before adding
them to your database permanently. The data will be added to temporary
tables in your database, using the same functions as when adding data
permanently. If your input data are somehow screwed up, you'll notice
this without altering your database. Once the tables are filled,
refdbd tries to find references in the permanent tables that are
likely to be duplicates of the ones in the temporary tables. Currently
the titles and the location (periodical, volume, issue, start page,
publication year) are compared which should work ok for books and
journal articles. Currently only identical matches are detected, but
more refined queries may be added later. refdbd also checks the
citation keys. If a citation key is already taken, you may choose to
specify a different one instead of letting refdbd create keys like
Miller1999c and so on.

In addition refdbd tries to find pairs of author names with full and
abbreviated first names which may point to the same person. If you get
a match, you may replace the abbreviated version with the full name,
as refdbd can always generate the initials from the full name, but
not vice versa.

The syntax of the checkref command is identical with the addref and
updateref commands. Currently there is only screen-readable output,
but other backends may be added later. I'd also like to get input from
people fiddling with RefDB frontends about how to return the data best
for graphical interfaces.

Finally, here is an example:

refdbc: checkref checkref.ris
406:1:Russwurm2002
408:1
406:2:Cerwinka2002
408:2
AUTHOR ABBREV: temp_id:1 temp_author:Mullershausen,F. author:Mullershausen,Flori
an
AUTHOR ABBREV: temp_id:1 temp_author:Russwurm,M. author:Russwurm,Michael
AUTHOR ABBREV: temp_id:1 temp_author:Koesling,D. author:Koesling,Doris
CITEKEY IDENT: temp_id:1 id:10
LOCATION IDENT: temp_id:1 id:10
TITLE IDENT: temp_id:1 id:10
AUTHOR ABBREV: temp_id:2 temp_author:Feelisch,M. author:Feelisch,Martin
CITEKEY IDENT: temp_id:2 id:21
TITLE IDENT: temp_id:2 id:21
999:2 checked:0 skipped:0 failed

This output indicates the following:

- three authors of the first reference may already be known to the
  database with their full firstnames. If you can verify this, you
  might want to edit that reference before permanently adding it

- however, the (auto-generated) citation key and the title are
  identical with the reference ID=10 in the database. You should
  verify whether these datasets are the same and not add the new one
  if this turns out to be the case.

- the same holds true for one author of the second reference, as well
  as for the citation key and the title. This is most likely a
  duplicate of reference ID=21.

regards,
Markus



-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] ANN: Updated debian packages available

[David N. <dav...@sw...>]

Updated debian packages for svn (revision 189) and pre-release 
(0.9.8-pre4) are now available.

Both sets of packages use the refdbd server in maintenance mode to 
upgrade the main database.  As this feature is still experimental users 
are advised to back up their data before upgrading.

Regards,
David.

[Refdb-users] ANN: refdb-0.9.8-pre4 available for download

[Markus H. <mar...@mh...>]

Hi,

time for another prerelease:

http://refdb.sourceforge.net/pre/refdb-latest.tar.gz

The focus of this prerelease is the main database upgrading
stuff. Users upgrading from 0.9.8-pre2 and earlier will have to
upgrade their main databases. refdbd can now handle this for
you. While this works for me (tested with all database engines), I'd
be interested to hear reports from others. Fear not, you can always
create your main database manually by following the procedure in the
manual. To see how to use this new feature, please check out the
UPGRADING file.

Other notable changes are listed below.

regards,
Markus

Bugfixes:

- exclusive queries (e.g. :UR:!~"http") now work as expected for links
  (UR, L1-L4), authors, and keywords

- refdbd now modifies citation keys containing the string "-ID" as
  this may cause problems when creating bibliographies. "-ID" will be
  replaced with "_ID" to avoid problems.


Improvements:

- refdbd can now install and upgrade the main database without
  external tools. See the file UPGRADING and the refdbd man page for
  further information.

- refdbd can also be run to check the database connection and to
  retrieve the database version. This is mainly useful for
  package/ports builders.




-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] Id- in citation keys

[Markus H. <mar...@mh...>]

Hi,

I've fixed this problem in svn. It will also be available shortly in
the upcoming 0.9.8-pre4 prerelease. refdbd will now change the "-ID"
to "_ID" when checking or creating the citation key.

regards,
Markus

Jeremy Malcolm writes:
 > Hello.  I don't know if this deserves to be called a bug, but I had a 
 > citation key that said "Johnson2001The-Idea-of-ICA" (I have configured 
 > my bibliography manager to put as much information in the citation keys 
 > as it can, so they're easy to recognise.  Because this has "-Id" in it, 
 > it caused runbib to fail with this error:
 > 

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] Id- in citation keys

[Markus H. <mar...@mh...>]

Hi,

I consider it a bug because refdbd should not accept or construct
citation keys which cause this error. I'll look into this. Thanks for
reporting the problem.

regards,
Markus 

Jeremy Malcolm writes:
 > Hello.  I don't know if this deserves to be called a bug, but I had a 
 > citation key that said "Johnson2001The-Idea-of-ICA" (I have configured 
 > my bibliography manager to put as much information in the citation keys 
 > as it can, so they're easy to recognise.  Because this has "-Id" in it, 
 > it caused runbib to fail with this error:
 > 
 > 1146: Table 'idjohnson2001the.t_refdb' doesn't exist
 > SELECT refdb_id, refdb_type FROM idjohnson2001the.t_refdb WHERE 
 > refdb_citekey='EA-OF-ICA' AND refdb_type!='DUMMY'
 > select failed
 > 
 > Anyway, if it's worth reporting as a bug, consider it reported.  No need 
 > to fix it on my account, as it's easy to workaround now that I know what 
 > caused it.  Here's the full reference in RIS format:
 > 
 > TY  - ELEC
 > AU  - Johnson, David R
 > AU  - Crawford, Susan P
 > PY  - 2001//
 > TI  - The Idea of ICANN
 > UR  - http://www.icannwatch.org/archive/the_idea_of_icann.htm
 > ID  - JOHNSON2001THE-IDEA-OF-ICA
 > ER  -
 > 
 > Thanks.
 > 
 > -- 
 > Jeremy Malcolm LLB (Hons) B Com
 > Internet and Open Source lawyer, IT consultant, actor
 > host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'
 > -------------------------------------------------------------------------
 > Using Tomcat but need to do more? Need to support web services, security?
 > Get stuff done quickly with pre-integrated technology to make your job easier
 > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
 > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642_______________________________________________
 > Refdb-users mailing list
 > Ref...@li...
 > https://lists.sourceforge.net/lists/listinfo/refdb-users

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] Id- in citation keys

[Jeremy M. <Je...@Ma...>]

Hello.  I don't know if this deserves to be called a bug, but I had a 
citation key that said "Johnson2001The-Idea-of-ICA" (I have configured 
my bibliography manager to put as much information in the citation keys 
as it can, so they're easy to recognise.  Because this has "-Id" in it, 
it caused runbib to fail with this error:

1146: Table 'idjohnson2001the.t_refdb' doesn't exist
SELECT refdb_id, refdb_type FROM idjohnson2001the.t_refdb WHERE 
refdb_citekey='EA-OF-ICA' AND refdb_type!='DUMMY'
select failed

Anyway, if it's worth reporting as a bug, consider it reported.  No need 
to fix it on my account, as it's easy to workaround now that I know what 
caused it.  Here's the full reference in RIS format:

TY  - ELEC
AU  - Johnson, David R
AU  - Crawford, Susan P
PY  - 2001//
TI  - The Idea of ICANN
UR  - http://www.icannwatch.org/archive/the_idea_of_icann.htm
ID  - JOHNSON2001THE-IDEA-OF-ICA
ER  -

Thanks.

-- 
Jeremy Malcolm LLB (Hons) B Com
Internet and Open Source lawyer, IT consultant, actor
host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F! '{print $3}'

Re: [Refdb-users] make error: /bin/sh: dtdparse: command not found

[Markus H. <mar...@mh...>]

Dominik Reusser <dre...@un...> was heard to say:

> This can be omitted using the --disable-docs option of configure or
> installing
> dtdparse. However, I'm wondering wether configure shouldn't avoid this
> problem and not build the docs if dtdparse is not present?
>

This is sort of a catch22. The release and prerelease archives contain the
prebuilt docs. make is not supposed to do anything in the /doc subdir, but in
order to install the prebuilt docs, make install should run in /doc even if
dtdparse and dtdformat are not present. This allows us to use the convenient
doc installation routines of the autotools, but it means that the lack of these
tools must not turn off the processing of /doc.

As you have noticed, this means for the svn version that make will attempt to
build the docs even if the necessary tools are not around. I consider this the
lesser of two evils, as someone building from svn can be expected to read the
manual which lists the prerequisites. The configure checks for these tools
should therefore be treated as a warning, not an error.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] make error: /bin/sh: dtdparse: command not found

[Dominik R. <dre...@un...>]

I just tried to compile the latest svn-version (165) of refdb on a debian 
testing system:
./autogen.sh
./configure
...
checking for dtdparse... no
checking for dtdformat... no
....

./make

I get the following error:
SGML_CATALOG_FILES=""  dtdparse --title "citationlistx XML DTD" --output 
citationlistx.xml --declaration ../declarations/xml.dcl --system-id "http://refdb.sourceforge.net/dtd/citationlistx.dtd" ../dtd/citationlistx.dtd
/bin/sh: dtdparse: command not found
make[1]: *** [citationlistx.xml] Error 127
make[1]: Leaving directory `/home/admin/refdb/doc'
make: *** [all-recursive] Error 1


This can be omitted using the --disable-docs option of configure or installing 
dtdparse. However, I'm wondering wether configure shouldn't avoid this 
problem and not build the docs if dtdparse is not present?

But maybe, I'm just missing something
Thanks for your help.
Dominik

-- 
Dominik Reusser

Re: [Refdb-users] latin1 characters in RIS entries not converted to UTF-8 by runbib when creating .bib.xml bibliography file

[Markus H. <mar...@mh...>]

Hi Olivier,

the latest prerelease and the current SVN version use UTF-8 as the default
throughout (input/storage/output). On the long run you'll be better off if you
set up your editor to use UTF-8 as well. I've got this in my .emacs:

;; xml files, planner files, as well as files with "utf8" somewhere
;; in the path are opened as Unicode
(setq file-coding-system-alist
      (append (list
	       (cons "\\.xml$" 'utf-8)
	       (cons "utf8" 'utf-8)
	       (cons "Plans" 'utf-8))
	      file-coding-system-alist))

This covers risx files as long as they use the suffix ".xml", and RIS files as
long as you put "utf8" somewhere in the filename, like in "test.utf8.ris".

regards,
Markus

Olivier Berger <oli...@in...> was heard to say:

> Allright, sorry for previous message... in the meantime, I've been
> thinking of how it works, and checked... and apparently the issue is
> that I was editing the RIS entries as latin-1, whereas
> in /etc/refdb/refdbcrc, I have :
> fromencoding UTF-8
>
> So it seems my database records where containing latin-1 accentuations,
> which would be generated as such in the UTF8 XML...
>
> I updated the RIS entry to use UTF8 accents, and now I get everything
> clean and compiling...
>
> Maybe I should change my /etc/refdb/refdbcrc preferences, then (or see
> how to have emacs RIS mode handle everything as UTF8 by default ?)
>
> Sorry for bothering.
>



-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-users] latin1 characters in RIS entries not converted to UTF-8 by runbib when creating .bib.xml bibliography file

[Olivier B. <oli...@in...>]

Allright, sorry for previous message... in the meantime, I've been
thinking of how it works, and checked... and apparently the issue is
that I was editing the RIS entries as latin-1, whereas
in /etc/refdb/refdbcrc, I have :
fromencoding UTF-8

So it seems my database records where containing latin-1 accentuations,
which would be generated as such in the UTF8 XML...

I updated the RIS entry to use UTF8 accents, and now I get everything
clean and compiling...

Maybe I should change my /etc/refdb/refdbcrc preferences, then (or see
how to have emacs RIS mode handle everything as UTF8 by default ?)

Sorry for bothering.

Best regards,

Le lundi 04 septembre 2006 =E0 12:46 +0200, Olivier Berger a =E9crit :
> Le jeudi 31 ao=FBt 2006 =E0 15:27 +0200, Markus Hoenicka a =E9crit :
> > Hi,
> >=20
> > Olivier Berger <oli...@in...> was heard to say:
> >=20
> > > The .bib.xml output from runbib contains latin1 accentuated character=
s
> > > instead of UTF-8, for the titles in the bibliography elements, hence
> > > breaking the xsltproc done on the DocBook XML file afterwards, althou=
gh
> > > I invoke runbib with option "-E utf8"...
> > >
> >=20
> > Did you try "-E utf-8"? libdbi (the database abstraction layer used by =
RefDB)
> > uses the MIME names of the encodings. These names are case-insensitive,=
 but
> > "utf8" is different from "utf-8".=20
>=20
> Well, that hasn't changed anything to the output with -E utf-8 (or -E
> UTF-8).
>=20
> My RIS file contains latin1 (so I suppose the same in the database of
> refdb ?), the .bib file too, although it will be included in a utf8 XML
> doc....
>=20
> > If you are in doubt, check the file
> > README.encodings shipped with libdbi-drivers.
> >=20
>=20
> Just for future reference :
> http://libdbi-drivers.cvs.sourceforge.net/*checkout*/libdbi-drivers/libdb=
i-drivers/README.encodings
>=20
>=20
> If you have more hints on what could be wrong...
>=20
> Best regards,
>=20
--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

Re: [Refdb-users] latin1 characters in RIS entries not converted to UTF-8 by runbib when creating .bib.xml bibliography file

[Olivier B. <oli...@in...>]

Le jeudi 31 ao=FBt 2006 =E0 15:27 +0200, Markus Hoenicka a =E9crit :
> Hi,
>=20
> Olivier Berger <oli...@in...> was heard to say:
>=20
> > The .bib.xml output from runbib contains latin1 accentuated characters
> > instead of UTF-8, for the titles in the bibliography elements, hence
> > breaking the xsltproc done on the DocBook XML file afterwards, although
> > I invoke runbib with option "-E utf8"...
> >
>=20
> Did you try "-E utf-8"? libdbi (the database abstraction layer used by Re=
fDB)
> uses the MIME names of the encodings. These names are case-insensitive, b=
ut
> "utf8" is different from "utf-8".=20

Well, that hasn't changed anything to the output with -E utf-8 (or -E
UTF-8).

My RIS file contains latin1 (so I suppose the same in the database of
refdb ?), the .bib file too, although it will be included in a utf8 XML
doc....

> If you are in doubt, check the file
> README.encodings shipped with libdbi-drivers.
>=20

Just for future reference :
http://libdbi-drivers.cvs.sourceforge.net/*checkout*/libdbi-drivers/libdbi-=
drivers/README.encodings


If you have more hints on what could be wrong...

Best regards,

--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

[Refdb-users] need help to reproduce bug #1550514

[Markus H. <mar...@mh...>]

Hi all,

did anyone of you encounter a problem like this:

http://sourceforge.net/tracker/index.php?func=detail&aid=1550514&group_id=26091&atid=385991

In brief, chapter and book titles imported from RIS documents
sometimes get truncated, leading to an incorrectly assembled SQL query
which throws an error.

I can't reproduce this problem in the following environments:

- FreeBSD 5.4, 6.1: MySQL, PostgreSQL, SQLite, SQLite3
- WinXP, Cygwin: MySQL
- Debian 3.1: SQLite

If anyone can reproduce it with the test data provided in the bug
report, please get back to the list for further analysis.

thanks,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

Re: [Refdb-users] latin1 characters in RIS entries not converted to UTF-8 by runbib when creating .bib.xml bibliography file

[Markus H. <mar...@mh...>]

Hi,

Olivier Berger <oli...@in...> was heard to say:

> The .bib.xml output from runbib contains latin1 accentuated characters
> instead of UTF-8, for the titles in the bibliography elements, hence
> breaking the xsltproc done on the DocBook XML file afterwards, although
> I invoke runbib with option "-E utf8"...
>

Did you try "-E utf-8"? libdbi (the database abstraction layer used by RefDB)
uses the MIME names of the encodings. These names are case-insensitive, but
"utf8" is different from "utf-8". If you are in doubt, check the file
README.encodings shipped with libdbi-drivers.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] latin1 characters in RIS entries not converted to UTF-8 by runbib when creating .bib.xml bibliography file

[Olivier B. <oli...@in...>]

Hi.

I've been using the debian packages and generated bibliography for XML
docbook using runbib.

I have some french papers with accents in the title, which break the
bibliography parsing.

The RIS file contained latin1 characters, which are output as such in
queries in refdb mode in emacs.

The .bib.xml output from runbib contains latin1 accentuated characters
instead of UTF-8, for the titles in the bibliography elements, hence
breaking the xsltproc done on the DocBook XML file afterwards, although
I invoke runbib with option "-E utf8"...

Maybe I'm missing something here...

Anyway, I manage to convert it to UTF-8 with an additional iconv filter
in the Makefile... but I'd think of a better solution managed by
runbib...

Thanks in advance.

Regards,
--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

Re: [Refdb-users] Using user-defined "numbering"/abbrevs in citations for docbook

[Olivier B. <oli...@in...>]

Le mardi 29 ao=FBt 2006 =E0 14:17 +0200, Markus Hoenicka a =E9crit :
> Hi Olivier,
>=20
> your best bet would be to use the citation key as the custom abbreviation=
.=20

Yes, of course.

I forgot to say that it's what I had thought of initially, also ;)

But it didn't seem to be used, although it seemed to be well named :(

> This of course may require some thoughts before you add the data, but if =
a string
> composed of the last name and the publication year is sufficient, RefDB s=
hould
> have done the right thing anyway.
>=20
> I take from the citestylex documentation that RefDB currently does not al=
low to
> insert the citation key anywhere in the bibliographic output. Apparently =
no one
> asked for this yet, and I haven't thought of it either. Could you please =
add a
> feature request on the RefDB SourceForge project page to remind me?
>=20

Right away :
http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1548540&group_=
id=3D26091&atid=3D385994

Many thanks.

--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

Re: [Refdb-users] Using user-defined "numbering"/abbrevs in citations for docbook

[Olivier B. <oli...@in...>]

Le mardi 29 ao=FBt 2006 =E0 14:04 +0200, Olivier Berger a =E9crit :
> Hi
>=20
> I'd like to have my citations be referenced and listed with something
> like :
>=20
> ... in [Berger 2006]...
>=20
> [Berger 2006]   Berger O. "a title" in ...

I've tried and use USERDEF in the citestyle to be able to construct a
custom preceeding abbrev using contents of the U1 fields of my RIS
entries, but it fails on something else :(

I get an extra </bibliomset> in front of the </bibliomixed> for each
entry if I use something like this this in the style :	<USERDEF
ROLE=3D"1"></USERDEF>

Same thing with MISC, also.

Are these USERDEF and MISC working atm ?

Thanks in advance.
--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

Re: [Refdb-users] Using user-defined "numbering"/abbrevs in citations for docbook

[Markus H. <mar...@mh...>]

Hi Olivier,

your best bet would be to use the citation key as the custom abbreviation. This
of course may require some thoughts before you add the data, but if a string
composed of the last name and the publication year is sufficient, RefDB should
have done the right thing anyway.

I take from the citestylex documentation that RefDB currently does not allow to
insert the citation key anywhere in the bibliographic output. Apparently no one
asked for this yet, and I haven't thought of it either. Could you please add a
feature request on the RefDB SourceForge project page to remind me?

regards,
Markus

Olivier Berger <oli...@in...> was heard to say:

> Hi
>
> I'd like to have my citations be referenced and listed with something
> like :
>
> ... in [Berger 2006]...
>
> [Berger 2006]   Berger O. "a title" in ...
>
> There's apparently two forms of citations, defined by the citestyle
> used : numbered references, using <REFNUMBER>, and non-numbered...
>
> When generating docbook XML, it seems that only REFNUMBER use will
> produce some <abbrev> DBXML tags. Am I right ?
>
>
> My problem is that I can customize the format for non-numbered with
> INTEXTDEF and REFSTYLEs, but I can't find a way, then to have citations
> look like :
>
> [custom abbrev] authors, title, etc.
>
> where that custom abbrev would be produced out of author names, etc, and
> be placed in an <abbrev> docbook XML tag.
>
> All I can get is just have is the last part : the authors and the rest,
> without any <abbrev> before.

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] Using user-defined "numbering"/abbrevs in citations for docbook

[Olivier B. <oli...@in...>]

Hi

I'd like to have my citations be referenced and listed with something
like :

... in [Berger 2006]...

[Berger 2006]   Berger O. "a title" in ...

There's apparently two forms of citations, defined by the citestyle
used : numbered references, using <REFNUMBER>, and non-numbered...

When generating docbook XML, it seems that only REFNUMBER use will
produce some <abbrev> DBXML tags. Am I right ?


My problem is that I can customize the format for non-numbered with
INTEXTDEF and REFSTYLEs, but I can't find a way, then to have citations
look like :

[custom abbrev] authors, title, etc.

where that custom abbrev would be produced out of author names, etc, and
be placed in an <abbrev> docbook XML tag.

All I can get is just have is the last part : the authors and the rest,
without any <abbrev> before.


Thanks in advance for clarifications.

Best regards,
--=20
Olivier BERGER <oli...@in...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC

[Refdb-users] ANN: refdb-0.9.8-pre3 available

[Markus H. <mar...@mh...>]

Hi,

unfortunately 0.9.8-pre2 had build problems on non-BSD platforms. pre3
fixes these problems, so please forget about pre2 and use the new one
instead. This one was built from revision 142:

http://refdb.sourceforge.net/pre/refdb-latest.tar.gz

regards,
Markus
-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de

[Refdb-users] ANN: debian svn packages (rev. 141)

[David N. <dav...@sw...>]

Debian packages for svn refdb have been updated from repository revision 
141.

The refdb-doc package is once again included but has the refdb-manual in 
HTML format only -- the PDF version is still not available.  These 
documents are not registered with the help system.

Regards,
David.

Re: [Refdb-users] ANN: refdb-0.9.8-pre2 available

[David N. <dav...@sw...>]

Hi Markus,
> Big oops. The file was lacking two includes which I've added
> now. Could you please test revision 141?

Compiles OK now.

Regards,
David.