Re: docbook5, getting started

Tim Arnold <jtim.arnold <at> gmail.com> was heard to say:

> As for the problem with the chapter vs book root element:
> When I have a source xml file (test1_full.xml) with chapter as the
> root and citations like this:
> <citation role="REFDB"><xref linkend="IDbart_m66-X"/></citation>.
>
> runbib gives me an error:
> -----------------------------------
> runbib -d saslatexbib -S Chicago -t db50x test1_full.xml
> Variable $SGML_CATALOG_FILES not set
> Please enter your password:
> Parse error at line 1:
> no element found
> error
> -----------------------------------
>

I see. This is caused by a limitation of  
/usr/local/share/refdb/xsl/citations.xsl. This stylesheet is used to  
extract the citations from the source document and write them into the  
foo.id.xml file. For reasons that I don't quite understand right now,  
the script limits itself to processing book and article elements. As a  
short term fix you could simply extend the regexp in line 39 like this  
(untested!):

         <xsl:template match="article|d:article|chapter|d:chapter">

I'll try to figure out if there was some obscure reason for this  

Re: docbook5, getting started

Tim Arnold writes:
 > Hi Markus,
 > Here are some notes:
 > Using refdbxp 0.9.9-1 built from svn revision 531 markus <at> mhoenicka.de
 > 
 > (1) invalid xml generated
 > This citation:
 >     <citation role="REFDB">bart_m66</citation>
 > 
 > After the command
 > refdbxp -t db50x < test1.xml > test1_full.xml
 > becomes (note the non-terminated xref)
 >     <citation role="REFDB"><xref linkend="IDbart_m66-X"></citation>
 > 

This is an odd inconsistency. As refdbxp need not be aware of the
DocBook or TEI version you're using, you can only choose between
DocBook SGML, DocBook XML, and TEI XML. The first one is the default
if no type or an incorrect type is specified. Try "-t db31x" instead
and you should get valid XML. See the man page for further
details. The default stems from the days of yore when XML was all
fresh and new and no one used it because the tools weren't as good as
they are now. XML should probably be the default these days, but I'm
always careful not to break old behaviour.

 > 
 > (2) documentation typo
 > Page 102 (section 10.3.1.2.3, step 1) the xinclude path is incorrect:
 > /usr/local/share/xsl should be
 > /usr/local/share/refdb/xsl

Re: docbook5, getting started

Tim Arnold writes:
 > failed to access style data

Hi Tim,

this usually means that you did not add that particular style to the
database. The style data have to be available to the application
server refdbd rather than to any of the clients. You'll have to run a
command along the lines of:

refdba -C addstyle APA.xml

although this should have been taken care of during the initial setup
of RefDB with refdb-init. You can list the available styles with the
command:

refdbc -C liststyle

regards,
Markus

--

-- 
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 

docbook5, getting started

hi, I must be doing something wrong since I can't get to the first
step of creating a DocBook5.0 raw bibliography.
I converted my bibtex database to ris format and I can use refdba, so
my installation is okay I think.

In my docbook test.xml file I have a couple of citations like this:
<citation role="REFDB">kuma_v92</citation>.

runbib -d mybib -r -t db50x test.xml
I get
Variable $SGML_CATALOG_FILES not set
Parse error at line 4 column 2:
syntax error

The terminal where the refdbd instance is running (refdbd -s -e 0 -l
7) says this when I exec the runbib in another terminal:
---------------------
sqlite3
/usr/local/var/lib/refdb/db

mybib
SELECT meta_app,meta_type,meta_dbversion FROM t_meta WHERE meta_type='risx'
connected to database server using database:
mybib
no character encoding conversion required
output encoding is:
UTF-8
XML parse error

child exited with code 1

DOI and edition

Hi!

I'm a somehow newbie to refdb, but I got it running and I'm impressed by 
the capabilities. I'm using the latest official version 0.9.9-1

Currently I've two questions I didn't found answers yet.

Is it possible or planned to include a
<biblioid class="doi">xxxx</biblioid>
when exporting to docbook5? I've imported RIS data sets including DO tags.

The second question is which RIS tag is the correct one for the 
"edition" of a book and is this tag already exported to an <edition> tag 
in docbook?

Kind regards,

Stephan

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

_______________________________________________

Re: RefDB chooses NOT to communicate with latest version of PostgreSQL

Hi Frank,

Frank M Salter writes:
 > main database version is not supported

this in fact indicates that the libdbi driver somehow doesn't manage
to talk to the PostgreSQL engine properly.

 > At some point: I was using a number of terminal screens and did not
 > see the exact moment
 > when the following (transcribed by me) appeared:
 > =======================================================
 > *** glibc detected  *** refdb *** munmap_chunk(): invalid pointer
 > 0xb75f48e0  ***
 > =======  Backtrace:  =======
 > /lib/libc.so.6(+0x6f68a)[0xb76f068a]
 > /usr/local/lib/libdbi.so.1(dbi_result_free + 0x14c)[0xb782827c]
 > refdbd[0x804d9a5]
 > /lib/libc.so.6(__libc_start_main+0xe6)[0xb7697db6]
 > refdbd[0x804aa21]

This looks like a crash in libdbi. This may be caused by some
incompatibility between the driver and the engine, or it's just a
plain libdbi bug. However, I've never had any such crashes with any of
the drivers that I've used, so I still suspect the pgsql driver does
not work well with the latest PostgreSQL releases.

 > Thank you for your prompt reply. If you need any more information,
 > please let me know.

RefDB chooses NOT to communicate with latest version of PostgreSQL

Refdb complains about the version number of the latest version of
PostgreSQL 9.0.4 and does not continue.

Is there real incompatibility?

Is there a workaround to allow access?

If not, what is the latest version of PostgreSQL with which RefDB will
work successfully?

Regards

Frank Salter

------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev

Problems with adduser

Hallöchen!

I use RefDB SVN-747 with PostgreSQL.  With refdba, I experience the
following:

bronger <at> wilson:~$ refdba -u chantal
Please enter your password:
refdba: listuser -d biblio
main database version is not supported
refdba: listuser -d biblio
chantal
drefdbuser1
refdb
999:3
refdba: adduser -d biblio toll
238:toll:biblio
999:1 added:0 failed
refdba: listuser -d biblio
chantal
drefdbuser1
refdb
999:3

(The first "main database version is not supported" is stange
because a second try works.  But this is not the main reason for my
posting.)

My problem is that I cannot see the user "toll" after having added
him.  The user "chantal" is allowed to add new users.  And what does
"238 - revoke user permissions successful" mean in this context?

Ubuntu packages

Hallöchen!

I just updated the Ubuntu packages to

* Refdb SVN-747
* Ubuntu 11.04

Installation is as easy as

       sudo apt-get install python-software-properties
       sudo add-apt-repository ppa:bronger/ppa
       sudo apt-get update
       sudo apt-get install refdb

Sometimes, the very first starting of the server fails.  However, a
re-start fixes this.  The package depends on sqlite3 and uses it as
default.

Tschö,
Torsten.

--

-- 
Torsten Bronger    Jabber ID: torsten.bronger <at> jabber.rwth-aachen.de
                                  or http://bronger-jmp.appspot.com

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev

FreeBSD: After several updates (PHP included) SRU/webinterface doesn't present search results in particular

Hello,
after a lot of updates on recent FreeBSD ports one of our RefDB servers 
doesn't present search results anymore when using the web-based SRU 
PHP-scripts. I was expecting search results listet in particular after 
the header of presenting how many results have been found, but I only 
get Matching Results number, not any reference to edit, print or whatsoever.

I guess since the main setup of the server hasn't change since the 
massive ports-update this problem can be solved easily - but I don't know.

Can anyone help?

Regards,
Oliver

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo

refdbib: multiple occurence of the same reference ends up in multiple entries in .bib file

Dear Sirs,
I have some trouble in creating my bibliography using a refdb-database. 
My text is spread over several files, connected via \input{} statements 
in a main head-file. Running latex/pdflatex on the head file, creates an 
.aux files, which is used by refdbib as input. refdbib then retrieves 
for each entry the appropriate reference from the SQL DB (postgresql 8.4 
server on a FreeBSD 8.0-STABLE platform) - but there a multiple 
occurences of the same reference, exactly as many as \cite't in the main 
text. Is this a feature or a bug?

Regards,

Oliver

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev