scrollkeeper-devel — Developer discussion list for ScrollKeeper

[Scrollkeeper-devel] Re: converting omf files

[John F. <jf...@in...>]

On Sun, 2002-05-05 at 07:18, David Merrill wrote:
> On Sun, May 05, 2002 at 03:06:10AM -0700, Chris Lyttle wrote:
> > John,
> > I went thru this evening and updated the gnome-games omf files to be in
> > the same format as the document you mentioned below (in the writing omf
> > files doc).
> 
> We have a utility called db2omf that extracts omf data from docbook
> files. I don't know if you already have seen it and decided it wasn't
> useful for you or didn't meet your needs, but just in case I thought I
> would mention it. It might alleviate the drudge work of maintaining
> your omf files manually.
> 


Cool. I forgot about that. Has it been updated to reflect the changed
omf file format in 0.3.8?

Remind me where I get it.

Cheers,
John
-- 
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

[Scrollkeeper-devel] Re: converting omf files

[John F. <jf...@in...>]

On Sun, 2002-05-05 at 04:06, Chris Lyttle wrote:
> John,
> I went thru this evening and updated the gnome-games omf files to be in
> the same format as the document you mentioned below (in the writing omf
> files doc). I ran your omftransform.xsl on it and the result was well
> not at all like the current gdp-example2-manual-C.omf and seem to omit
> some information in the <rights> tag I had from the original file. Which
> is correct, your format or the gdp-example2-manual-C.omf?
> 
> Chris
> 


Unfortunately, it looks like gdp-example2-manual-C.omf has not been
updated to reflect the new SK dtd that Dan and Eric included in SK
0.3.8. Ugh.

The way to test if your dtd if valid is to run xmllint on it against the
new dtd, which is included in the SK 0.3.8 package:

xmllint --noout -dtdvalid       
/usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd    
gdp-example2-manual-C.omf

> PS I noticed that the SK main page has fairly complete docs on how to
> get things setup correctly.
> 

I don't believe the "how to write an OMF file" section of that has been
updated to reflect the new dtd.

Cheers,
John
-- 
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

[Scrollkeeper-devel] Re: converting omf files

[David M. <da...@lu...>]

On Sun, May 05, 2002 at 03:06:10AM -0700, Chris Lyttle wrote:
> John,
> I went thru this evening and updated the gnome-games omf files to be in
> the same format as the document you mentioned below (in the writing omf
> files doc).

We have a utility called db2omf that extracts omf data from docbook
files. I don't know if you already have seen it and decided it wasn't
useful for you or didn't meet your needs, but just in case I thought I
would mention it. It might alleviate the drudge work of maintaining
your omf files manually.

Regards,

-- 
David C. Merrill                         http://www.lupercalia.net
Linux Documentation Project                   da...@lu...
Lead Developer                                 http://www.tldp.org

Software evolves. It isn't designed. The only question is how strictly you
_control_ the evolution, and how open you are to external sources of
mutations.
		-- Linus Torvalds, lmkl

[Scrollkeeper-devel] Re: converting omf files

[Chris L. <ch...@wi...>]

John,
I went thru this evening and updated the gnome-games omf files to be in
the same format as the document you mentioned below (in the writing omf
files doc). I ran your omftransform.xsl on it and the result was well
not at all like the current gdp-example2-manual-C.omf and seem to omit
some information in the <rights> tag I had from the original file. Which
is correct, your format or the gdp-example2-manual-C.omf?

Chris

PS I noticed that the SK main page has fairly complete docs on how to
get things setup correctly.

On Sat, 2002-05-04 at 05:26, John Fleck wrote:
> On Sat, May 04, 2002 at 02:26:56AM -0700, Chris Lyttle wrote:
> > John,
> > It seems to me in the quick test I did on this that the file produced is
> > a start for the new format and quite a bit still has to be added, is
> > that correct?
> > 
> 
> Chris -
> 
> If you have a "complete" old OMF file (see
> http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html
> for an example) then the resulting OMF file also will be complete, but
> many of them are lacking elements which you'll have to add in
> manually, yeah.
> 
> 
> 
> 
> > PS It took me a bit of combing thru the SK mailing list to find the info
> > I needed about how to put together a OMF system for the docs, perhaps we
> > could use a 'HOWTO' for this sort of like what Sasha wrote for getting
> > docbook xml to work? Any takers?
> > 
> 
> That'd be great if someone has the time.
> 
> John
> 
> > On Mon, 2002-04-22 at 20:25, John Fleck wrote:
> > > Folks -
> > > 
> > > I've made an xsl stylesheet to convert old OMF files to the form
> > > required by ScrollKeeper's new dtd. This is tested against some of my
> > > old files, and also against Dan's "Complete OMF File" example (which
> > > is of the old type):
> > > 
> > > http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html
> > > 
> > > Run this using xsltproc at the command line:
> > > 
> > > [jfleck@jelloiii omfexamples]$ xsltproc omftransform.xsl complete.omf > testout.omf
> > > 
> > > Then by all means, you should validate the resulting output:
> > > 
> > > [jfleck@jelloiii omfexamples]$ xmllint --noout --dtdvalid /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd testout.omf 
> > > 
> > > Suggestions welcome, as my xslt skills are modest at best.
> > > 

[Scrollkeeper-devel] Clarification about language tag

[Christian M. <mar...@fr...>]

Hi,

Quoting the scrollkeeper documentation :

,----
| The standard OMF specifies the "language" element as optional and as
| having no attributes. For ScrollKeeper to relate documents with the
| locale of the user, the locale of the documents must be specified. This
| is done by using a new attribute, "code", of the "language" element. The
| language code should be a standard locale.
----

But unfortunately, if the language tag is set to "en", scrollkeeper is
unable to install that document.

If somedody can tell me why ?

Christian

[Scrollkeeper-devel] Re: converting omf files

[John F. <jf...@in...>]

On Sat, May 04, 2002 at 02:26:56AM -0700, Chris Lyttle wrote:
> John,
> It seems to me in the quick test I did on this that the file produced is
> a start for the new format and quite a bit still has to be added, is
> that correct?
> 

Chris -

If you have a "complete" old OMF file (see
http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html
for an example) then the resulting OMF file also will be complete, but
many of them are lacking elements which you'll have to add in
manually, yeah.




> PS It took me a bit of combing thru the SK mailing list to find the info
> I needed about how to put together a OMF system for the docs, perhaps we
> could use a 'HOWTO' for this sort of like what Sasha wrote for getting
> docbook xml to work? Any takers?
> 

That'd be great if someone has the time.

John

> On Mon, 2002-04-22 at 20:25, John Fleck wrote:
> > Folks -
> > 
> > I've made an xsl stylesheet to convert old OMF files to the form
> > required by ScrollKeeper's new dtd. This is tested against some of my
> > old files, and also against Dan's "Complete OMF File" example (which
> > is of the old type):
> > 
> > http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html
> > 
> > Run this using xsltproc at the command line:
> > 
> > [jfleck@jelloiii omfexamples]$ xsltproc omftransform.xsl complete.omf > testout.omf
> > 
> > Then by all means, you should validate the resulting output:
> > 
> > [jfleck@jelloiii omfexamples]$ xmllint --noout --dtdvalid /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd testout.omf 
> > 
> > Suggestions welcome, as my xslt skills are modest at best.
> > 
> 
> > <?xml version="1.0"?>
> > <xsl:stylesheet id="omf"
> >   version="1.0"
> >   xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> >    <xsl:strip-space elements="*"/>
> >    
> >    <xsl:template match="omf">
> >      <xsl:element name="omf">
> >        <xsl:text>
> >        </xsl:text>
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >    </xsl:template>
> > 
> >  
> >    <xsl:template match="resource">
> >      <xsl:element name="resource">
> >        <xsl:text>
> >        </xsl:text>
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >    
> >    <xsl:template match="creator">
> >      <xsl:element name="creator">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="maintainer">
> >      <xsl:element name="maintainer">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="contributor">
> >      <xsl:element name="contributor">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="type">
> >      <xsl:element name="type">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="title">
> >      <xsl:element name="title">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="date">
> >      <xsl:element name="date">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="version">
> >      <version xsl:use-attribute-sets="version-atts">
> >        
> >      </version>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:attribute-set name="version-atts">
> >      <xsl:attribute name="identifier"><xsl:value-of select="normalize-space(identifier)"/></xsl:attribute>
> >      <xsl:attribute name="date"><xsl:value-of select="normalize-space(date)"/></xsl:attribute>
> >      <xsl:attribute name="description"><xsl:value-of select="normalize-space(description)"/></xsl:attribute>
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="subject">
> >      <subject xsl:use-attribute-sets="subject-atts">
> >      
> >      </subject>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >   
> >    <xsl:attribute-set name="subject-atts">
> >      <xsl:attribute name="category"><xsl:value-of select="normalize-space(category)"/></xsl:attribute>
> > 
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="description">
> >      <xsl:element name="description">
> >        <xsl:apply-templates/>
> >      </xsl:element>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:template match="format">
> >      <format xsl:use-attribute-sets="format-atts">
> >        
> >      </format>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >   
> >    <xsl:attribute-set name="format-atts">
> >      <xsl:attribute name="mime"><xsl:value-of select="@mime"/></xsl:attribute>
> >      <xsl:attribute name="dtd"><xsl:value-of select="@dtd"/></xsl:attribute>
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="identifier">
> >      <identifier xsl:use-attribute-sets="identifier-atts">
> >      
> >      </identifier>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >    
> >    <xsl:attribute-set name="identifier-atts">
> >      <xsl:attribute name="url"><xsl:value-of select="@url"/></xsl:attribute>
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="relation">
> >      <relation xsl:use-attribute-sets="relation-atts">
> >        
> >      </relation>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >    
> >    <xsl:attribute-set name="relation-atts">
> >      <xsl:attribute name="seriesid"><xsl:value-of select="@seriesid"/></xsl:attribute>
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="language">
> >      <language xsl:use-attribute-sets="language-atts">
> >      
> >      </language>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> >   
> >    <xsl:attribute-set name="language-atts">
> >      <xsl:attribute name="code"><xsl:value-of select="@code"/></xsl:attribute>
> >    </xsl:attribute-set>
> > 
> >    <xsl:template match="rights">
> >      <rights xsl:use-attribute-sets="rights-atts">
> >      
> >      </rights>
> >      <xsl:text>
> >      </xsl:text>
> >    </xsl:template>
> > 
> >    <xsl:attribute-set name="rights-atts">
> >      <xsl:attribute name="type"><xsl:value-of select="normalize-space(type)"/></xsl:attribute>
> >      <xsl:attribute name="license.version"><xsl:value-of select="normalize-space(license.version)"/></xsl:attribute>
> >      <xsl:attribute name="holder"><xsl:value-of select="normalize-space(holder)"/></xsl:attribute>
> >    </xsl:attribute-set>
> >    
> >  </xsl:stylesheet>
> 
> 
> _______________________________________________
> gnome-doc-list mailing list
> gno...@gn...
> http://mail.gnome.org/mailman/listinfo/gnome-doc-list
> 

-- 
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

[Scrollkeeper-devel] Re: converting omf files

[Chris L. <ch...@wi...>]

John,
It seems to me in the quick test I did on this that the file produced is
a start for the new format and quite a bit still has to be added, is
that correct?

Chris

PS It took me a bit of combing thru the SK mailing list to find the info
I needed about how to put together a OMF system for the docs, perhaps we
could use a 'HOWTO' for this sort of like what Sasha wrote for getting
docbook xml to work? Any takers?

On Mon, 2002-04-22 at 20:25, John Fleck wrote:
> Folks -
> 
> I've made an xsl stylesheet to convert old OMF files to the form
> required by ScrollKeeper's new dtd. This is tested against some of my
> old files, and also against Dan's "Complete OMF File" example (which
> is of the old type):
> 
> http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html
> 
> Run this using xsltproc at the command line:
> 
> [jfleck@jelloiii omfexamples]$ xsltproc omftransform.xsl complete.omf > testout.omf
> 
> Then by all means, you should validate the resulting output:
> 
> [jfleck@jelloiii omfexamples]$ xmllint --noout --dtdvalid /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd testout.omf 
> 
> Suggestions welcome, as my xslt skills are modest at best.
> 
> Cheers,
> John
> 
> -- 
> John Fleck
> jf...@in... (h) jf...@ab... (w)
> http://www.inkstain.net http://www.abqjournal.com
> 
> "You don't want to die with the music still in you."
>  - John Gardner
> ----
> 

> <?xml version="1.0"?>
> <xsl:stylesheet id="omf"
>   version="1.0"
>   xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>    <xsl:strip-space elements="*"/>
>    
>    <xsl:template match="omf">
>      <xsl:element name="omf">
>        <xsl:text>
>        </xsl:text>
>        <xsl:apply-templates/>
>      </xsl:element>
>    </xsl:template>
> 
>  
>    <xsl:template match="resource">
>      <xsl:element name="resource">
>        <xsl:text>
>        </xsl:text>
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>    
>    <xsl:template match="creator">
>      <xsl:element name="creator">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="maintainer">
>      <xsl:element name="maintainer">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="contributor">
>      <xsl:element name="contributor">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="type">
>      <xsl:element name="type">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="title">
>      <xsl:element name="title">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="date">
>      <xsl:element name="date">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="version">
>      <version xsl:use-attribute-sets="version-atts">
>        
>      </version>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:attribute-set name="version-atts">
>      <xsl:attribute name="identifier"><xsl:value-of select="normalize-space(identifier)"/></xsl:attribute>
>      <xsl:attribute name="date"><xsl:value-of select="normalize-space(date)"/></xsl:attribute>
>      <xsl:attribute name="description"><xsl:value-of select="normalize-space(description)"/></xsl:attribute>
>    </xsl:attribute-set>
> 
>    <xsl:template match="subject">
>      <subject xsl:use-attribute-sets="subject-atts">
>      
>      </subject>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>   
>    <xsl:attribute-set name="subject-atts">
>      <xsl:attribute name="category"><xsl:value-of select="normalize-space(category)"/></xsl:attribute>
> 
>    </xsl:attribute-set>
> 
>    <xsl:template match="description">
>      <xsl:element name="description">
>        <xsl:apply-templates/>
>      </xsl:element>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:template match="format">
>      <format xsl:use-attribute-sets="format-atts">
>        
>      </format>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>   
>    <xsl:attribute-set name="format-atts">
>      <xsl:attribute name="mime"><xsl:value-of select="@mime"/></xsl:attribute>
>      <xsl:attribute name="dtd"><xsl:value-of select="@dtd"/></xsl:attribute>
>    </xsl:attribute-set>
> 
>    <xsl:template match="identifier">
>      <identifier xsl:use-attribute-sets="identifier-atts">
>      
>      </identifier>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>    
>    <xsl:attribute-set name="identifier-atts">
>      <xsl:attribute name="url"><xsl:value-of select="@url"/></xsl:attribute>
>    </xsl:attribute-set>
> 
>    <xsl:template match="relation">
>      <relation xsl:use-attribute-sets="relation-atts">
>        
>      </relation>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>    
>    <xsl:attribute-set name="relation-atts">
>      <xsl:attribute name="seriesid"><xsl:value-of select="@seriesid"/></xsl:attribute>
>    </xsl:attribute-set>
> 
>    <xsl:template match="language">
>      <language xsl:use-attribute-sets="language-atts">
>      
>      </language>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
>   
>    <xsl:attribute-set name="language-atts">
>      <xsl:attribute name="code"><xsl:value-of select="@code"/></xsl:attribute>
>    </xsl:attribute-set>
> 
>    <xsl:template match="rights">
>      <rights xsl:use-attribute-sets="rights-atts">
>      
>      </rights>
>      <xsl:text>
>      </xsl:text>
>    </xsl:template>
> 
>    <xsl:attribute-set name="rights-atts">
>      <xsl:attribute name="type"><xsl:value-of select="normalize-space(type)"/></xsl:attribute>
>      <xsl:attribute name="license.version"><xsl:value-of select="normalize-space(license.version)"/></xsl:attribute>
>      <xsl:attribute name="holder"><xsl:value-of select="normalize-space(holder)"/></xsl:attribute>
>    </xsl:attribute-set>
>    
>  </xsl:stylesheet>

Re: [Scrollkeeper-devel] A number of questions regarding ScrollKeeper

[Mikael H. <mi...@co...>]

ons 2002-05-01 klockan 20.29 skrev Mikael Hallendal:
> ons 2002-05-01 klockan 19.42 skrev John Fleck:
> > On Wed, May 01, 2002 at 06:11:10PM +0200, Mikael Hallendal wrote:
> > > 
> > > This is with Scrollkeeper 0.3.6 since someone seemed to change 0.3.8
> > > into validating all the documents making it impossible to get any
> > > documents for GNOME 2 into scrollkeeper database with these errors:
> > > 
> > >   Unable to register
> > > /gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf
> > > OMF file [/gnome/head/INSTALL/share/omf/gdp-example1/bug-buddy-C.omf]
> > > does not validate against ScrollKeeper-OMF DTD:
> > > /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd
> > > 
> > > (and yes, I have the latest of all GNOME2 packages).
> > > 
> > 
> > I have been making my way through the packages changing the OMF files so they
> > validate against the dtd included in 0.3.8. As a result, many (and
> > gnome-calculator is one of them) may not work with 0.3.6.
> > 
> > I don't know if this could be a source of the trouble you are describing. Dan?
> 
> I don't think those are related, and I haven't been able to use *any*
> (including gnome-calculator) with scrollkeeper 0.3.8

ARGH!!!

It didn't generate new files in /tmp/scrollkeeper-tmp... so I had an old
file there which had the wrong documents in them. This is definitely a
bug in scrollkeeper (at least 0.3.8).

Regards,
  Mikael Hallendal

> Regards,
>   Mikael Hallendal
> 
> -- 
> Mikael Hallendal                mi...@co...
> CodeFactory AB                  http://www.codefactory.se/
> Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel
> 
-- 
Mikael Hallendal                mi...@co...
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [Scrollkeeper-devel] A number of questions regarding ScrollKeeper

[Mikael H. <mi...@co...>]

ons 2002-05-01 klockan 19.42 skrev John Fleck:
> On Wed, May 01, 2002 at 06:11:10PM +0200, Mikael Hallendal wrote:
> > 
> > This is with Scrollkeeper 0.3.6 since someone seemed to change 0.3.8
> > into validating all the documents making it impossible to get any
> > documents for GNOME 2 into scrollkeeper database with these errors:
> > 
> >   Unable to register
> > /gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf
> > OMF file [/gnome/head/INSTALL/share/omf/gdp-example1/bug-buddy-C.omf]
> > does not validate against ScrollKeeper-OMF DTD:
> > /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd
> > 
> > (and yes, I have the latest of all GNOME2 packages).
> > 
> 
> I have been making my way through the packages changing the OMF files so they
> validate against the dtd included in 0.3.8. As a result, many (and
> gnome-calculator is one of them) may not work with 0.3.6.
> 
> I don't know if this could be a source of the trouble you are describing. Dan?

I don't think those are related, and I haven't been able to use *any*
(including gnome-calculator) with scrollkeeper 0.3.8

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal                mi...@co...
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [Scrollkeeper-devel] A number of questions regarding ScrollKeeper

[John F. <jf...@in...>]

On Wed, May 01, 2002 at 06:11:10PM +0200, Mikael Hallendal wrote:
> 
> This is with Scrollkeeper 0.3.6 since someone seemed to change 0.3.8
> into validating all the documents making it impossible to get any
> documents for GNOME 2 into scrollkeeper database with these errors:
> 
>   Unable to register
> /gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf
> OMF file [/gnome/head/INSTALL/share/omf/gdp-example1/bug-buddy-C.omf]
> does not validate against ScrollKeeper-OMF DTD:
> /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd
> 
> (and yes, I have the latest of all GNOME2 packages).
> 

I have been making my way through the packages changing the OMF files so they
validate against the dtd included in 0.3.8. As a result, many (and
gnome-calculator is one of them) may not work with 0.3.6.

I don't know if this could be a source of the trouble you are describing. Dan?


Cheers,

John

[Scrollkeeper-devel] A number of questions regarding ScrollKeeper

[Mikael H. <mi...@co...>]

Hi!

* Looking in the scrollkeeper_extended_cl.xml I find that all documents 
  TOC is insterted in this too. (should they be there?) If so, what's 
  the point of the /var/lib/scrollkeeper/TOC?

* Running scrollkeeper-update I (among other things) see:

Registering
/gnome/head/INSTALL/share/omf/gnome-utils/gnome-calculator-C.omf

  but when trying to find this document in scrollkeeper_extended_cl.xml 
  (C locale) it doesn't contain information about this document, but
  when I get the scrollkeeper-get-content-list C file it contains it.

  The problem is that it contains a non-valid <docsource> and I have no 
  idea where it finds that path.

<docsource>file:/gnome/head/INSTALL/share/gnome/help/gnome-calculator/C/gcalc.xml</docsource>

  but nowhere in my OMF_DIR is there an omf-file including that path so 
  where does it come from?

This is with Scrollkeeper 0.3.6 since someone seemed to change 0.3.8
into validating all the documents making it impossible to get any
documents for GNOME 2 into scrollkeeper database with these errors:

  Unable to register
/gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf
OMF file [/gnome/head/INSTALL/share/omf/gdp-example1/bug-buddy-C.omf]
does not validate against ScrollKeeper-OMF DTD:
/usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd

(and yes, I have the latest of all GNOME2 packages).

Regards,
  Mikael Hallendal

-- 
Mikael Hallendal                mi...@co...
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

Re: [Scrollkeeper-devel] scrollkeeper problematic issues

[John F. <jf...@in...>]

On Mon, Apr 29, 2002 at 08:07:17PM +0200, Ali Akcaagac wrote:
> 
> yeah i know of that package you offering on your homepage, although i dont
> fully agree to you by setting up the fact that my docbook installation isnt
> correct. i am using the packages from the oasis homepage which comes with
> default catalogfiles that imo looks quite ok to me.
> 

The OASIS DocBook packages don't install xmlcatalogs, only sgml catalogs. They
are two separate beasts. SK needs xmlcatalogs.

Cheers,

John

Re: [Scrollkeeper-devel] scrollkeeper problematic issues

[Ali A. <ali...@st...>]

Hello Dan,

> I'm sorry to hear this has given you so much grief.  I think I need to
> include some information about these problems in the INSTALL file, or
> possibly in a FAQ.

yeah this would seriously help understanding this much better.

> It sounds like most of your problems (1, 4, and 5) are caused by not
> having adequate docbook packages.  This is not surprising, because until
> recently the only place that good docbook packages could be found was in
> Red Hat mirrors.  This is because nobody used to use the XML catalogs, and
> so distributions didn't bother actually registering docbook in the
> catalogs.  Now that we are starting to use the catalog to do processing of
> DocBook/XML documents, we are in a painful period where docbook
> distributors need to fix their packages. To help things out, I made we
> made our own packages which you can use:
>
>      http://scrollkeeper.sourceforge.net/docbook.shtml
>
> If you use this package, you should not have to worry about things being
> installed in strange paths where they aren't found or the need to be
> connected to the internet to build.  (It tries to find the DTD on the
> internet, since the catalog is missing or incomplete, preventing it from
> finding the DTD on your own computer.)

yeah i know of that package you offering on your homepage, although i dont
fully agree to you by setting up the fact that my docbook installation isnt
correct. i am using the packages from the oasis homepage which comes with
default catalogfiles that imo looks quite ok to me.

neverthless by using your package there is one more issue lets say i install
gnome-xml then libxslt but after i reach the installation of libglade it go=
es
and overwrites the /etc/catalog file _ONCE_AGAIN_ this makes my point 5) of=
 my
previous email obsolete (the 2nd paragraph in it)

i would be happy to hear whats wrong with the default catalogfile. i am rea=
lly
worried using your own package and the createcatalog scripts. anyways i wou=
ld
really like to see a selfrunning scrollkeeper that dont touch my docbooks,
catalogs or whatever.

> For #2, I believe the package is working properly.  I don't think
> localstatedir is supposed to track prefix.  For example, on a vanilla
> Linux installation, prefix is /usr, localstatedir is /var, and sysconfdir
> is /etc.  Things which go under localstatedir belong in /var, not
> /usr/var.  Similarly, things which go under sysconfdir belong in /etc, not
> /usr/etc.  So, if somebody is doing something unusual, such as parallel
> installations, they should customize not only prefix but also sysconfdir
> and localstatedir.  I think a lot of people overlook this since most
> programs don't actually use sysconfdir and localstatedir and so for many
> packages customizing prefix alone is adequate.

well i am using a clean new linux installation without any previous
scrollkeeper installation, neverthless i am too long on unix and linux syst=
ems
to know what i am doing. before replying why dont you just grab your own
scrollkeeper 0.3.8 package make a simple

=2E/configure

only and see what it spits out at the end. the $(prefix) wont be resolved
correctly.

> #3 would definitely be breakage on the part of ScrollKeeper if it behaves
> as you describe it.  Would you mind double-checking that it is doing what
> you describe?  What do "scrollkeeper-config --localstatedir"  and
> "scrollkeeper-config --pkglocalstatedir" give you?  It is running the same
> commands the same way when you install ScrollKeeper and when you update
> the database when new GNOME packages are installed, so I can't see how it
> could change the directory.

bash-2.05a$ scrollkeeper-config --localstatedir
/usr/local/var
bash-2.05a$ scrollkeeper-config --pkglocalstatedir
/usr/local/var/lib/scrollkeeper
bash-2.05a$

thank you for your help.

=2D-=20
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali...@st...
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa

Re: [Scrollkeeper-devel] scrollkeeper problematic issues

[Dan M. <mu...@al...>]

Hi Ali,

I'm sorry to hear this has given you so much grief.  I think I need to 
include some information about these problems in the INSTALL file, or 
possibly in a FAQ.

It sounds like most of your problems (1, 4, and 5) are caused by not
having adequate docbook packages.  This is not surprising, because until
recently the only place that good docbook packages could be found was in
Red Hat mirrors.  This is because nobody used to use the XML catalogs, and
so distributions didn't bother actually registering docbook in the
catalogs.  Now that we are starting to use the catalog to do processing of
DocBook/XML documents, we are in a painful period where docbook
distributors need to fix their packages. To help things out, I made we
made our own packages which you can use:

     http://scrollkeeper.sourceforge.net/docbook.shtml

If you use this package, you should not have to worry about things being 
installed in strange paths where they aren't found or the need to be 
connected to the internet to build.  (It tries to find the DTD on the 
internet, since the catalog is missing or incomplete, preventing it from 
finding the DTD on your own computer.)

For #2, I believe the package is working properly.  I don't think
localstatedir is supposed to track prefix.  For example, on a vanilla
Linux installation, prefix is /usr, localstatedir is /var, and sysconfdir
is /etc.  Things which go under localstatedir belong in /var, not
/usr/var.  Similarly, things which go under sysconfdir belong in /etc, not
/usr/etc.  So, if somebody is doing something unusual, such as parallel 
installations, they should customize not only prefix but also sysconfdir 
and localstatedir.  I think a lot of people overlook this since most 
programs don't actually use sysconfdir and localstatedir and so for many 
packages customizing prefix alone is adequate.

#3 would definitely be breakage on the part of ScrollKeeper if it behaves
as you describe it.  Would you mind double-checking that it is doing what
you describe?  What do "scrollkeeper-config --localstatedir"  and
"scrollkeeper-config --pkglocalstatedir" give you?  It is running the same
commands the same way when you install ScrollKeeper and when you update
the database when new GNOME packages are installed, so I can't see how it
could change the directory.

Dan


On Sun, 28 Apr 2002, Ali Akcaagac wrote:

> hello,
> 
> please allow me to write a couple of lines related to scrollkeeper and the
> issues i got by using it. before i go into details lemme introduce my system
> here so you get a view for what i use it.
> 
> i am running a linux system here with openjade, latex, and a full docbook
> support sgml-3.1, sgml-4.1, xml-4.1.2, dssl-1.76, xsl-1.50. i use all that
> stuff to build the gnome 2 documentations and programming reference manuals.
> the catalog files are mostly these that comes with the original packages (from
> the correct webpages. no repacks, rebuilds, forks etc.). all the catalogs are
> beeing exported correctly so they can be found correctly. so far building
> gnome 2 using these packages works perfectly.
> 
> now the part where scrollkeeper takes action is something that is really
> troublesome. please let me explain the problems i have and i hope that some of
> you people could help solving these issues. either in a new scrollkeeper
> version or right now as is.
> 
> i use scrollkeeper 0.3.8 (i know its a development version). but i detected
> these issues in earlier versions too so i doubt that they will be solved any
> soon, if i dont write a few lines to point to them.
> 
> 1) i use scrollkeeper from source, compile it and install it (after libxml and
>    libxsl got installed). the problems with it is why does it search for
>    /etc/xml -> which is the same as xml-4.1.2 which is on the otherhand
>    located in my /usr/share/sgml/sgml/xml-4.1.2 directory. ok i solved this
>    issue by linking that directory to /etc/xml. i understand that people
>    install their docbook packages into different places so finding the right
>    path could be really problematic.
> 
>    i recommend adding a --path-to-xml-docbook=<path> to the configure script
>    so i dont need to link to /etc/xml and i make sure that the rest of
>    scrollkeeper get the right docbook i point to.
> 
> 2) something that also follows from one version to another. i dont use
>    /var/lib/scrollkeeper as localstatedir. i point my stuff to the same
>    prefix as scrollkeeper gets installed (default is) /usr/local where i
>    want my scrollkeeper to be installed. now if i do this.
> 
>    ./configure && make && make install
> 
>    then during configure the localstatedir wont be set correctly for the
>    scrollkeeper datafiles and configure spits out
>    $(prefix)/var/lib/scrollkeeper as it searchpath. the variable $prefix wasnt
>    changed to /usr/local as it should default to. i need to explicitely do
> 
>    ./configure --prefix=/usr/local --localstatedir=/usr/local/var
> 
>    so configure show
> 
>    /usr/local/var/lib/scrollkeeper
> 
>    after configuration. oki so far i was able solving this issues too. but
>    usually the configure script should take care if no --localstatedir was
>    defined that it at least point to the real prefix default. which it
>    currently doesnt do.
> 
> 3) another issue also point 2) related. lets say i installed scrollkeeper into
>    /usr/local/share and its database got installed to
>    /usr/local/share/var/lib/scrollkeeper. then after i compile more gnome
>    related packages, scrollkeeper doesnt use
>    /usr/local/share/var/lib/scrollkeeper to store its stuff, it puts
>    everything into a new directory named /usr/local/share/var/scrollkeeper.
>    oki since i know this happeneing, i symlink the lib/scrollkeeper dir to
>    ../scrollkeeper i know its poor but not the fault of the way i install
>    things.
> 
> 4) again this hits point 2) now after i did the /etc/xml symlink and
>    configured scrollkeeper, make and make installed it. i am getting errors
>    thrown out about not beeing able to connect to the net. or something that
>    tells me that it cant grab some stuff from net. the first time in my life
>    that i see some stuff grabbing some other stuff from net during
>    installation.
> 
>    oki solution is to make sure networkaccess is present. but anyways there
>    shouldnt be the need to have a newtwork connection to install something.
> 
> 5) related to point 2) and 4) oki now the network access is present and make
>    install throws out error messages about 'starttag not found' oki
>    investigation into this tells me that scrollkeeper has problems with the
>    the default catalogfile of xml-4.1.2. now i ask myself why does
>    scrollkeeper have problems with parsing the default catalogfile ?
> 
>    even worser on earlier versions, why is it required to generate a new
>    catalogfile so scrollkeeper understands it and even much more worse, why
>    does scrollkeeper do this on its own and trash a correct original
>    catalogfile ? i detected that my original xml catalogfile got overwritten
>    by a new made catalogfile from a previous scrollkeeper installation. i dont
>    want to say that i got really pissed by this. not to mention that i figured
>    this one out really late.
> 
> now i dont want to sound offending or something but if i had a decission i
> wouldnt use scrollkeeper at all unfortunately a lot of gnome packages requires
> it so i depend on it. i know that i will get answers like 'use a distro' use
> final 'packages' or whatever but that are all workarounds and dont cover the
> real problems.
> 
> i would be happy to get at least an answer to this. as it currently looks to
> me. scrollkeeper needs a lot of TWEAKING because it doesnt work correctly out
> of the box.
> 
> 

[Scrollkeeper-devel] scrollkeeper problematic issues

[Ali A. <ali...@st...>]

hello,

please allow me to write a couple of lines related to scrollkeeper and the
issues i got by using it. before i go into details lemme introduce my system
here so you get a view for what i use it.

i am running a linux system here with openjade, latex, and a full docbook
support sgml-3.1, sgml-4.1, xml-4.1.2, dssl-1.76, xsl-1.50. i use all that
stuff to build the gnome 2 documentations and programming reference manuals.
the catalog files are mostly these that comes with the original packages (f=
rom
the correct webpages. no repacks, rebuilds, forks etc.). all the catalogs a=
re
beeing exported correctly so they can be found correctly. so far building
gnome 2 using these packages works perfectly.

now the part where scrollkeeper takes action is something that is really
troublesome. please let me explain the problems i have and i hope that some=
 of
you people could help solving these issues. either in a new scrollkeeper
version or right now as is.

i use scrollkeeper 0.3.8 (i know its a development version). but i detected
these issues in earlier versions too so i doubt that they will be solved any
soon, if i dont write a few lines to point to them.

1) i use scrollkeeper from source, compile it and install it (after libxml =
and
   libxsl got installed). the problems with it is why does it search for
   /etc/xml -> which is the same as xml-4.1.2 which is on the otherhand
   located in my /usr/share/sgml/sgml/xml-4.1.2 directory. ok i solved this
   issue by linking that directory to /etc/xml. i understand that people
   install their docbook packages into different places so finding the right
   path could be really problematic.

   i recommend adding a --path-to-xml-docbook=3D<path> to the configure scr=
ipt
   so i dont need to link to /etc/xml and i make sure that the rest of
   scrollkeeper get the right docbook i point to.

2) something that also follows from one version to another. i dont use
   /var/lib/scrollkeeper as localstatedir. i point my stuff to the same
   prefix as scrollkeeper gets installed (default is) /usr/local where i
   want my scrollkeeper to be installed. now if i do this.

   ./configure && make && make install

   then during configure the localstatedir wont be set correctly for the
   scrollkeeper datafiles and configure spits out
   $(prefix)/var/lib/scrollkeeper as it searchpath. the variable $prefix wa=
snt
   changed to /usr/local as it should default to. i need to explicitely do

   ./configure --prefix=3D/usr/local --localstatedir=3D/usr/local/var

   so configure show

   /usr/local/var/lib/scrollkeeper

   after configuration. oki so far i was able solving this issues too. but
   usually the configure script should take care if no --localstatedir was
   defined that it at least point to the real prefix default. which it
   currently doesnt do.

3) another issue also point 2) related. lets say i installed scrollkeeper i=
nto
   /usr/local/share and its database got installed to
   /usr/local/share/var/lib/scrollkeeper. then after i compile more gnome
   related packages, scrollkeeper doesnt use
   /usr/local/share/var/lib/scrollkeeper to store its stuff, it puts
   everything into a new directory named /usr/local/share/var/scrollkeeper.
   oki since i know this happeneing, i symlink the lib/scrollkeeper dir to
   ../scrollkeeper i know its poor but not the fault of the way i install
   things.

4) again this hits point 2) now after i did the /etc/xml symlink and
   configured scrollkeeper, make and make installed it. i am getting errors
   thrown out about not beeing able to connect to the net. or something that
   tells me that it cant grab some stuff from net. the first time in my life
   that i see some stuff grabbing some other stuff from net during
   installation.

   oki solution is to make sure networkaccess is present. but anyways there
   shouldnt be the need to have a newtwork connection to install something.

5) related to point 2) and 4) oki now the network access is present and make
   install throws out error messages about 'starttag not found' oki
   investigation into this tells me that scrollkeeper has problems with the
   the default catalogfile of xml-4.1.2. now i ask myself why does
   scrollkeeper have problems with parsing the default catalogfile ?

   even worser on earlier versions, why is it required to generate a new
   catalogfile so scrollkeeper understands it and even much more worse, why
   does scrollkeeper do this on its own and trash a correct original
   catalogfile ? i detected that my original xml catalogfile got overwritten
   by a new made catalogfile from a previous scrollkeeper installation. i d=
ont
   want to say that i got really pissed by this. not to mention that i figu=
red
   this one out really late.

now i dont want to sound offending or something but if i had a decission i
wouldnt use scrollkeeper at all unfortunately a lot of gnome packages requi=
res
it so i depend on it. i know that i will get answers like 'use a distro' use
final 'packages' or whatever but that are all workarounds and dont cover the
real problems.

i would be happy to get at least an answer to this. as it currently looks to
me. scrollkeeper needs a lot of TWEAKING because it doesnt work correctly o=
ut
of the box.

=2D-=20
Name....: Ali Akcaagac
Status..: Student Of Computer & Economic Science
E-Mail..: mailto:ali...@st...
WWW.....: http://www.fh-wilhelmshaven.de/~akcaagaa

Re: [Scrollkeeper-devel] scrollkeeper 0.3.8 compilation on Solaris8

[John F. <jf...@in...>]

On Tue, Apr 23, 2002 at 11:30:13AM +0100, Damien Donlon wrote:

> Also at the end of the 'make install' it 
> attempts to open the docbookx.dtd definition from 
> http://www.oasis-open.org/ but our firewall stopped it
> as the function which attempts to do so doesn't know anything 
> about our LAN proxy servers :
> 
> /usr/local/bin/scrollkeeper-rebuilddb -q -p /usr/local/var/lib/scrollkeeper
> xmlNanoHTTPConnectHost:  Failed to resolve host 'www.oasis-open.org' - Authoritive host not foundxmlNanoHTTPConnectHost:  Failed to resolve host 'www.oasis-open.org' - Authoritive host not found/usr/local/share/scrollkeeper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.xml:14: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"
> 
> I am not sure how this will impact on the installation?
> In general, how do folks circumvent the firewall problem
> when validating against external DTDs when they are behind a 
> firewall? I cannot use xmllint for validation for this reason also.
> 
> Is there an env variable I ought to be setting? I have using them
> through socks but they don't appear to be socks aware.
> 

This problem should be solved by installing a local version of the
necessary dtd that is properly registered with xmlcatalog. Dan's made
some packages to do this:

 http://scrollkeeper.sourceforge.net/docbook.shtml

Cheers,
John
-- 
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

Re: [Scrollkeeper-devel] scrollkeeper 0.3.8 compilation on Solaris8

[Damien D. <Dam...@Su...>]

Dan Mueth wrote:
> =

> Damien,
> =

> Try adding this:
> =

>     #include <sys/types.h>
> =

> to scrollkeeper.h.in below the line:
> =

>     #include <libxml/tree.h>
> =

> If it isn't sufficient, you might add a line for <sys/stat.h> too, but =
I
> don't think this will be necessary.
> =

> Tell me if this fixes the problem for you.

It certainly did Dan! Thank you. Two additional things -
on Solaris I used GNU make because I ran into problems with
Solaris make. Also at the end of the 'make install' it =

attempts to open the docbookx.dtd definition from =

http://www.oasis-open.org/ but our firewall stopped it
as the function which attempts to do so doesn't know anything =

about our LAN proxy servers :

/usr/local/bin/scrollkeeper-rebuilddb -q -p /usr/local/var/lib/scrollkeep=
er
xmlNanoHTTPConnectHost:  Failed to resolve host 'www.oasis-open.org' - Au=
thoritive host not foundxmlNanoHTTPConnectHost:  Failed to resolve host '=
www.oasis-open.org' - Authoritive host not found/usr/local/share/scrollke=
eper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.=
xml:14: warning: failed to load external entity "http://www.oasis-open.or=
g/docbook/xml/4.1.2/docbookx.dtd"

I am not sure how this will impact on the installation?
In general, how do folks circumvent the firewall problem
when validating against external DTDs when they are behind a =

firewall? I cannot use xmllint for validation for this reason also.

Is there an env variable I ought to be setting? I have using them
through socks but they don't appear to be socks aware.

Thanks for your assistance!

Regards,
Damien


]>

> Dan
> =

> On Mon, 22 Apr 2002, Damien Donlon wrote:
> =

> >
> > Hi All,
> > While compiling 0.3.7 & 0.3.8 scrollkeeper on Solaris 8 I
> > persistently get the following during the make :
> >
> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/libxml2/libxml =
-I/usr/local/include/libxml2 -I/include -I/usr/local/include -I/usr/local=
/include/libxml2/libxml -I/usr/local/include/libxml2 -I/include -DSOLARIS=
 -g -O2 -c error.c  -fPIC -DPIC -o .libs/error.lo
> > In file included from error.c:22:
> > scrollkeeper.h:63: parse error before `mode_t'
> > *** Error code 1
> > make: Fatal error: Command failed for target `error.lo'
> > Current working directory /tmp/scrollkeeper-0.3.8/libs
> > *** Error code 1
> > make: Fatal error: Command failed for target `all-recursive'
> > Current working directory /tmp/scrollkeeper-0.3.8
> > *** Error code 1
> > make: Fatal error: Command failed for target `all-recursive-am'
> >
> > The function definition causing the problem appears to be :
> >
> > extern int sk_mkdir_with_parents(char *, mode_t, char);
> >
> > I am using :
> > basil% gcc -v
> > Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.3=
/specs
> > gcc version 2.95.3 20010315 (release)
> >
> > Do I need to install a 3.0+ version?
> >
> > Libxml2 is Gary Pennington's latest 64bit Solaris binary and libxslt =
is
> > 1.0.16.
> >
> > Suggestions?
> > Please email be directly as I am not on the alias.
> >
> > Thank you!
> >
> > Damien
> >
> >
> >
> > =A4=BA=FF=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=FF=B0=
`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=F8=A4=BA=B0`=B0=BA=FF=A4
> > Damien Donlon
> > dam...@su...
> > 00 353 1 8199225
> > x19225
> >
> > _______________________________________________
> > Scrollkeeper-devel mailing list
> > Scr...@li...
> > https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel
> >

-- =

=A4=BA=FF=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=FF=B0`=B0=
=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=F8=A4=BA=B0`=B0=BA=FF=A4
Damien Donlon
dam...@su...
00 353 1 8199225
x19225

[Scrollkeeper-devel] converting omf files

[John F. <jf...@in...>]

Folks -

I've made an xsl stylesheet to convert old OMF files to the form
required by ScrollKeeper's new dtd. This is tested against some of my
old files, and also against Dan's "Complete OMF File" example (which
is of the old type):

http://scrollkeeper.sourceforge.net/documentation/writing_scrollkeeper_omf_files/ar01s06.html

Run this using xsltproc at the command line:

[jfleck@jelloiii omfexamples]$ xsltproc omftransform.xsl complete.omf > testout.omf

Then by all means, you should validate the resulting output:

[jfleck@jelloiii omfexamples]$ xmllint --noout --dtdvalid /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd testout.omf 

Suggestions welcome, as my xslt skills are modest at best.

Cheers,
John

-- 
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

Re: [Scrollkeeper-devel] scrollkeeper 0.3.8 compilation on Solaris 8

[Dan M. <mu...@al...>]

Damien,

Try adding this:

    #include <sys/types.h>

to scrollkeeper.h.in below the line:
 =20
    #include <libxml/tree.h>

If it isn't sufficient, you might add a line for <sys/stat.h> too, but I=20
don't think this will be necessary.

Tell me if this fixes the problem for you.

Dan



On Mon, 22 Apr 2002, Damien Donlon wrote:

>=20
> Hi All,
> While compiling 0.3.7 & 0.3.8 scrollkeeper on Solaris 8 I=20
> persistently get the following during the make :
>=20
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/libxml2/libxml -I=
/usr/local/include/libxml2 -I/include -I/usr/local/include -I/usr/local/i=
nclude/libxml2/libxml -I/usr/local/include/libxml2 -I/include -DSOLARIS -=
g -O2 -c error.c  -fPIC -DPIC -o .libs/error.lo
> In file included from error.c:22:
> scrollkeeper.h:63: parse error before `mode_t'
> *** Error code 1
> make: Fatal error: Command failed for target `error.lo'
> Current working directory /tmp/scrollkeeper-0.3.8/libs
> *** Error code 1
> make: Fatal error: Command failed for target `all-recursive'
> Current working directory /tmp/scrollkeeper-0.3.8
> *** Error code 1
> make: Fatal error: Command failed for target `all-recursive-am'
>=20
> The function definition causing the problem appears to be :
>=20
> extern int sk_mkdir_with_parents(char *, mode_t, char);
>=20
> I am using :
> basil% gcc -v
> Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.3/s=
pecs
> gcc version 2.95.3 20010315 (release)
>=20
> Do I need to install a 3.0+ version?
>=20
> Libxml2 is Gary Pennington's latest 64bit Solaris binary and libxslt is
> 1.0.16.=20
>=20
> Suggestions?
> Please email be directly as I am not on the alias.
>=20
> Thank you!
>=20
> Damien
>=20
>=20
>=20
> =A4=BA=FF=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=FF=B0`=
=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=F8=A4=BA=B0`=B0=BA=FF=A4
> Damien Donlon
> dam...@su...
> 00 353 1 8199225
> x19225
>=20
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel
>=20

[Scrollkeeper-devel] scrollkeeper 0.3.8 compilation on Solaris 8

[Damien D. <Dam...@Su...>]

Hi All,
While compiling 0.3.7 & 0.3.8 scrollkeeper on Solaris 8 I =

persistently get the following during the make :

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/libxml2/libxml -I/u=
sr/local/include/libxml2 -I/include -I/usr/local/include -I/usr/local/inc=
lude/libxml2/libxml -I/usr/local/include/libxml2 -I/include -DSOLARIS -g =
-O2 -c error.c  -fPIC -DPIC -o .libs/error.lo
In file included from error.c:22:
scrollkeeper.h:63: parse error before `mode_t'
*** Error code 1
make: Fatal error: Command failed for target `error.lo'
Current working directory /tmp/scrollkeeper-0.3.8/libs
*** Error code 1
make: Fatal error: Command failed for target `all-recursive'
Current working directory /tmp/scrollkeeper-0.3.8
*** Error code 1
make: Fatal error: Command failed for target `all-recursive-am'

The function definition causing the problem appears to be :

extern int sk_mkdir_with_parents(char *, mode_t, char);

I am using :
basil% gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.3/spe=
cs
gcc version 2.95.3 20010315 (release)

Do I need to install a 3.0+ version?

Libxml2 is Gary Pennington's latest 64bit Solaris binary and libxslt is
1.0.16. =


Suggestions?
Please email be directly as I am not on the alias.

Thank you!

Damien



=A4=BA=FF=B0`=B0=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=A4=BA=FF=B0`=B0=
=BA=A4=F8,=B8=B8,=F8=A4=BA=B0`=B0=BA=A4=F8=F8=A4=BA=B0`=B0=BA=FF=A4
Damien Donlon
dam...@su...
00 353 1 8199225
x19225

Re: [Scrollkeeper-devel] ScrollKeeper 0.3.8 Released

[John F. <jf...@in...>]

On Sun, Apr 21, 2002 at 04:27:16PM +0200, Mikael Hallendal wrote:
> s=F6n 2002-04-21 klockan 05.37 skrev Dan Mueth:
> >=20
> > ScrollKeeper 0.3.8 is now available.
>=20
> Hmm .. with this version I get warning that none of my omf-files can be
> validated (this is gnome2 packages). So I don't get any TOC-files
> created.
>=20
> Copy of some of the output:
> OMF file [/gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf]
> does not validate against ScrollKeeper-OMF DTD:
> /usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd
> Unable to register
> /gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf
>=20

Yes, the omf files must all be modified to match the new dtd in this
version. :-(
That has not yet been done.
Cheers,
John

--=20
John Fleck
jf...@in... (h) jf...@ab... (w)
http://www.inkstain.net http://www.abqjournal.com

"You don't want to die with the music still in you."
 - John Gardner

Re: [Scrollkeeper-devel] ScrollKeeper 0.3.8 Released

[Mikael H. <mi...@co...>]

s=F6n 2002-04-21 klockan 05.37 skrev Dan Mueth:
>=20
> ScrollKeeper 0.3.8 is now available.

Hmm .. with this version I get warning that none of my omf-files can be
validated (this is gnome2 packages). So I don't get any TOC-files
created.

Copy of some of the output:
OMF file [/gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf]
does not validate against ScrollKeeper-OMF DTD:
/usr/share/xml/scrollkeeper/dtds/scrollkeeper-omf.dtd
Unable to register
/gnome/head/INSTALL/share/omf/glade-2/glade-user-guide-C.omf

Regards,
  Mikael Hallendal

> New in this release:
>=20
>   One requested feature added:
>    * Adding --with-omfdirs configure option for configure-time=20
>      customization of OMF file search paths.  (This could always be=20
>      configured after installation by editing=20
>      $sysconfdir/scrollkeeper.conf.)
>=20
>   Two major bugs fixed:
>    * Fixed bug introduced in 0.3.7 where contents list files weren't=20
>      populated.
>    * Fixed bug 544912 which could cause rampant file destruction
>=20
> You can get ScrollKeeper 0.3.8 at:
>         http://sourceforge.net/projects/scrollkeeper
>=20
> If you find any bugs, please submit them to the bug tracker at:
>         http://sourceforge.net/tracker/?group_id=3D11543&atid=3D111543
> Please be sure to include your name and email address in any bugs you
> enter so we can contact you if necessary.
>=20
> If you would like to contribute to ScrollKeeper:
> There are instructions for getting the latest source from CVS at:
>         http://scrollkeeper.sourceforge.net/cvs.shtml
> Look over the TODO list in the tarball or CVS and the bug list on the web=
,
> find something you're interested in working on, and email
> scr...@li... with your choice so that others
> don't duplicate your work.
>=20
> - The ScrollKeeper Team
>=20
>=20
>=20
> _______________________________________________
> Scrollkeeper-devel mailing list
> Scr...@li...
> https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel
>=20
--=20
Mikael Hallendal                mi...@co...
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918

OMF search paths (was: Re: [Scrollkeeper-devel] ScrollKeeper 0.3.7 Released)

[Dan M. <mu...@al...>]

Mikael,

ScrollKeeper 0.3.8 addresses this issue by having a new configure option,
--with-omfdirs.  Just specify all the paths you want ScrollKeeper to
search for OMF files, seperated by colons.  These paths will be put in
$sysconfdir/scrollkeeper.conf and searched whenever you update or rebuild
the database.

I expect the build scripts (eg. vicious-build-scripts and Garnome) can be
easily updated to configure ScrollKeeper as:

./configure --localstatedir=/gnome/head/INSTALL/var
--prefix=/gnome/head/INSTALL --sysconfdir=/gnome/head/INSTALL/etc
--with-omfdirs=/gnome/head/INSTALL/share/omf

or something of that sort, depending on where you are installing 
everything.

If this doesn't solve the problem for some reason, tell me why not and
which paths you'd like put into /etc/scrollkeeper.conf.

Dan


On 16 Apr 2002, Mikael Hallendal wrote:

> tis 2002-04-16 klockan 08.12 skrev Dan Mueth:
> > 
> > ScrollKeeper 0.3.7 is now available.
> 
> Thanks a lot!
> 
> Would it be possible to install the locations from vicious-build-scripts
> (/gnome/head/INSTALL/share/oaf) and the default locations for the
> various other buildscripts in /etc/scrollkeeper.conf. I see lots of
> weird locations in there now so I figure just adding a few extra
> shouldn't be a problem?
> 
> Regards,
>   Mikael Hallendal
> 
> 

[Scrollkeeper-devel] ScrollKeeper 0.3.8 Released

[Dan M. <mu...@al...>]

ScrollKeeper 0.3.8 is now available.

New in this release:

  One requested feature added:
   * Adding --with-omfdirs configure option for configure-time 
     customization of OMF file search paths.  (This could always be 
     configured after installation by editing 
     $sysconfdir/scrollkeeper.conf.)

  Two major bugs fixed:
   * Fixed bug introduced in 0.3.7 where contents list files weren't 
     populated.
   * Fixed bug 544912 which could cause rampant file destruction

You can get ScrollKeeper 0.3.8 at:
        http://sourceforge.net/projects/scrollkeeper

If you find any bugs, please submit them to the bug tracker at:
        http://sourceforge.net/tracker/?group_id=11543&atid=111543
Please be sure to include your name and email address in any bugs you
enter so we can contact you if necessary.

If you would like to contribute to ScrollKeeper:
There are instructions for getting the latest source from CVS at:
        http://scrollkeeper.sourceforge.net/cvs.shtml
Look over the TODO list in the tarball or CVS and the bug list on the web,
find something you're interested in working on, and email
scr...@li... with your choice so that others
don't duplicate your work.

- The ScrollKeeper Team

[Scrollkeeper-devel] Re: ScrollKeeper, OMF files, KDE, etc.

[Frederik F. <fo...@Co...>]

[...]

| I'd also like to revive the discussion of merging the OMF into DocBook.  
| This would make things a bit easier on people.  I think we can follow Éric
| Bischoff's suggestion of using a namespace mechanism to include the OMF
| metadata in DocBook without conflicts with existing DocBook tags.  Then we
| can write an XSLT stylesheet to generate an OMF file from a DocBook doc.  
| ScrollKeeper can include this stylesheet along with a short script to run
| it, and it can be called at build time to generate the OMF file and
| include it in the package.  It sounded like there was a rough concensus on
| this approach last spring when it was last discussed, although it would be
| good to go over this quickly again.  If people still like the idea, then 
| we should start by trying to finalize the DTD and then ask Norm to work it 
| into DocBook.

If I'm right, a subset of the Dublin Core will be in the next
DocBook DTD release (4.2), which is quite close: they have
Release Candidate 1 currently.  (The OMF extends on the Dublin
Core Meta Data.)  There is a mapping from Dublin Core elements to
DocBook elements available.  (See the DocBook web pages.)

I find it a bit worrying that there are now so many different
subset relations (DocBook meta data < Dublin Core Meta Data < OMF
<?  Scrollkeeper; < means here "subset of"), but subsets are
still better than only intersecting sets.  Extension are not
_really_ a problem, as long as they are _only_ extensions, or as
long as there is an unambiguous mapping from one into the other.
These mappings need to be defined "officially" - anything else
will lead to divergences in interpretation.

Greetings,

Frederik Fouvry
KDE DocBook