You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(50) |
Nov
(117) |
Dec
(38) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(7) |
Feb
(7) |
Mar
(40) |
Apr
(83) |
May
(72) |
Jun
(15) |
Jul
(8) |
Aug
(1) |
Sep
(29) |
Oct
|
Nov
(6) |
Dec
(4) |
| 2002 |
Jan
(8) |
Feb
(4) |
Mar
(18) |
Apr
(27) |
May
(70) |
Jun
(21) |
Jul
(13) |
Aug
(27) |
Sep
(2) |
Oct
(26) |
Nov
(1) |
Dec
(6) |
| 2003 |
Jan
(17) |
Feb
(9) |
Mar
(4) |
Apr
(14) |
May
(18) |
Jun
(25) |
Jul
(4) |
Aug
(11) |
Sep
(14) |
Oct
(6) |
Nov
(5) |
Dec
(22) |
| 2004 |
Jan
(16) |
Feb
(3) |
Mar
(7) |
Apr
(2) |
May
(4) |
Jun
|
Jul
(3) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
(5) |
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
(2) |
Oct
(3) |
Nov
(7) |
Dec
(6) |
| 2006 |
Jan
(3) |
Feb
(3) |
Mar
(1) |
Apr
(2) |
May
(6) |
Jun
(21) |
Jul
(12) |
Aug
(7) |
Sep
(10) |
Oct
(34) |
Nov
(21) |
Dec
(28) |
| 2007 |
Jan
(29) |
Feb
(39) |
Mar
(25) |
Apr
(39) |
May
(26) |
Jun
(12) |
Jul
(16) |
Aug
(42) |
Sep
(24) |
Oct
(11) |
Nov
(8) |
Dec
(6) |
| 2008 |
Jan
(10) |
Feb
(9) |
Mar
(30) |
Apr
(19) |
May
(16) |
Jun
(10) |
Jul
(27) |
Aug
(22) |
Sep
(23) |
Oct
(18) |
Nov
(21) |
Dec
(51) |
| 2009 |
Jan
(56) |
Feb
(39) |
Mar
(45) |
Apr
(49) |
May
(108) |
Jun
(109) |
Jul
(66) |
Aug
(33) |
Sep
(26) |
Oct
(41) |
Nov
(13) |
Dec
(14) |
| 2010 |
Jan
(6) |
Feb
(7) |
Mar
(36) |
Apr
(50) |
May
(74) |
Jun
(61) |
Jul
(33) |
Aug
(58) |
Sep
(29) |
Oct
|
Nov
(1) |
Dec
|
| 2011 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
(3) |
Feb
|
Mar
(3) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(6) |
Oct
(6) |
Nov
(5) |
Dec
(1) |
| 2015 |
Jan
(2) |
Feb
(3) |
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(3) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(2) |
| 2019 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
|
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2020 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(2) |
Mar
(6) |
Apr
(4) |
May
(3) |
Jun
(2) |
Jul
(5) |
Aug
(18) |
Sep
(13) |
Oct
(19) |
Nov
(35) |
Dec
(23) |
| 2022 |
Jan
(6) |
Feb
(10) |
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
(5) |
Dec
(4) |
| 2026 |
Jan
(1) |
Feb
(4) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mikael H. <mi...@co...> - 2002-03-13 16:45:05
|
ons 2002-03-13 klockan 10.21 skrev Mikael Hallendal: > ons 2002-03-13 klockan 08.43 skrev Dan Mueth: > > > > I just found out that Kjartan is experiencing the same problem. I wonder > > if this could be tied to locale or a particular distribution in some way? > > What versions of libxml2 and libxslt are you using, and are they from DV > > or from a distribution? > > Hi! > > Both me and rhult is experiencing this. We are both using Red Hat 7.2 > and running in sv_SE locale. I think that the proposed solution worked > for Richard (I haven't had time to check it out). Hi again! Trying some at my machine, the proposed fix didn't help but running with LC_ALL="C" helped. When running LC_ALL="C" scrollkeeper-rebuilddb LC_ALL="C" scrollkeeper-update -p /var/lib/scrollkeeper -o /gnome/head/INSTALL/share/omf things worked as they should. Regards, Mikael Hallendal > > Regards, > Mikael Hallendal > > > Kjartan - Could you also try the two suggestions below and see if they > > help at all? > > > > Dan > > > > On Sun, 10 Mar 2002, Dan Mueth wrote: > > > > > > > > I can't reproduce this problem, so I'm not sure what is causing it. > > > > > > Here are a couple things you might try doing to the stylesheet to see if > > > it helps: > > > > > > (1) > > > Try removing the 9 lines: > > > <xsl:param name="toclevel"/> > > > > > > from /usr/share/scrollkeeper/stylesheets/toc.xsl. > > > > > > (2) > > > Try replacing these lines with: > > > <xsl:param name="toclevel" select="0"/> > > > > > > Technically (2) is the best, although all 3 forms work fine for me. Do > > > these help? > > > > > > Does the index stylesheet work okay for you? > > > > > > Dan > > > > > > > > > > > > On 5 Mar 2002, Mikael Hallendal wrote: > > > > > > > Hi! > > > > > > > > ScrollKeeper keeps generating broken TOC-files for me, this is how they > > > > look: > > > > > > > > <?xml version="1.0"?> > > > > <toc> > > > > <tocsect1, linkid="intro">Introduction > > > > </tocsect1,> > > > > <tocsect1, linkid="usage">Using GNOME Calculator > > > > <tocsect2, linkid="mainwin">Basic usage > > > > </tocsect2,> > > > > <tocsect2, linkid="menubar">Menus > > > > </tocsect2,> > > > > <tocsect2, linkid="buttons">Buttons > > > > </tocsect2,> > > > > </tocsect1,> > > > > <tocsect1, linkid="bugs">Known Bugs and Limitations > > > > </tocsect1,> > > > > <tocsect1, linkid="authors">Authors > > > > </tocsect1,> > > > > <tocsect1, linkid="license">License > > > > </tocsect1,> > > > > </toc> > > > > > > > > notice the , in the end of all tocsectX tags. > > > > > > > > What is causing this (others have problems with it too?). > > > > > > > > Regards, > > > > Mikael Hallendal > > > > > > > > > > > > > > > > > _______________________________________________ > > > Scrollkeeper-devel mailing list > > > Scr...@li... > > > https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel > > > > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 |
|
From: Mikael H. <mi...@co...> - 2002-03-13 09:22:03
|
ons 2002-03-13 klockan 08.43 skrev Dan Mueth: > > I just found out that Kjartan is experiencing the same problem. I wonder > if this could be tied to locale or a particular distribution in some way? > What versions of libxml2 and libxslt are you using, and are they from DV > or from a distribution? Hi! Both me and rhult is experiencing this. We are both using Red Hat 7.2 and running in sv_SE locale. I think that the proposed solution worked for Richard (I haven't had time to check it out). Regards, Mikael Hallendal > Kjartan - Could you also try the two suggestions below and see if they > help at all? > > Dan > > On Sun, 10 Mar 2002, Dan Mueth wrote: > > > > > I can't reproduce this problem, so I'm not sure what is causing it. > > > > Here are a couple things you might try doing to the stylesheet to see if > > it helps: > > > > (1) > > Try removing the 9 lines: > > <xsl:param name="toclevel"/> > > > > from /usr/share/scrollkeeper/stylesheets/toc.xsl. > > > > (2) > > Try replacing these lines with: > > <xsl:param name="toclevel" select="0"/> > > > > Technically (2) is the best, although all 3 forms work fine for me. Do > > these help? > > > > Does the index stylesheet work okay for you? > > > > Dan > > > > > > > > On 5 Mar 2002, Mikael Hallendal wrote: > > > > > Hi! > > > > > > ScrollKeeper keeps generating broken TOC-files for me, this is how they > > > look: > > > > > > <?xml version="1.0"?> > > > <toc> > > > <tocsect1, linkid="intro">Introduction > > > </tocsect1,> > > > <tocsect1, linkid="usage">Using GNOME Calculator > > > <tocsect2, linkid="mainwin">Basic usage > > > </tocsect2,> > > > <tocsect2, linkid="menubar">Menus > > > </tocsect2,> > > > <tocsect2, linkid="buttons">Buttons > > > </tocsect2,> > > > </tocsect1,> > > > <tocsect1, linkid="bugs">Known Bugs and Limitations > > > </tocsect1,> > > > <tocsect1, linkid="authors">Authors > > > </tocsect1,> > > > <tocsect1, linkid="license">License > > > </tocsect1,> > > > </toc> > > > > > > notice the , in the end of all tocsectX tags. > > > > > > What is causing this (others have problems with it too?). > > > > > > Regards, > > > Mikael Hallendal > > > > > > > > > > > > _______________________________________________ > > Scrollkeeper-devel mailing list > > Scr...@li... > > https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel > > > > > _______________________________________________ > 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 |
|
From: Dan M. <mu...@al...> - 2002-03-13 07:43:30
|
I just found out that Kjartan is experiencing the same problem. I wonder if this could be tied to locale or a particular distribution in some way? What versions of libxml2 and libxslt are you using, and are they from DV or from a distribution? Kjartan - Could you also try the two suggestions below and see if they help at all? Dan On Sun, 10 Mar 2002, Dan Mueth wrote: > > I can't reproduce this problem, so I'm not sure what is causing it. > > Here are a couple things you might try doing to the stylesheet to see if > it helps: > > (1) > Try removing the 9 lines: > <xsl:param name="toclevel"/> > > from /usr/share/scrollkeeper/stylesheets/toc.xsl. > > (2) > Try replacing these lines with: > <xsl:param name="toclevel" select="0"/> > > Technically (2) is the best, although all 3 forms work fine for me. Do > these help? > > Does the index stylesheet work okay for you? > > Dan > > > > On 5 Mar 2002, Mikael Hallendal wrote: > > > Hi! > > > > ScrollKeeper keeps generating broken TOC-files for me, this is how they > > look: > > > > <?xml version="1.0"?> > > <toc> > > <tocsect1, linkid="intro">Introduction > > </tocsect1,> > > <tocsect1, linkid="usage">Using GNOME Calculator > > <tocsect2, linkid="mainwin">Basic usage > > </tocsect2,> > > <tocsect2, linkid="menubar">Menus > > </tocsect2,> > > <tocsect2, linkid="buttons">Buttons > > </tocsect2,> > > </tocsect1,> > > <tocsect1, linkid="bugs">Known Bugs and Limitations > > </tocsect1,> > > <tocsect1, linkid="authors">Authors > > </tocsect1,> > > <tocsect1, linkid="license">License > > </tocsect1,> > > </toc> > > > > notice the , in the end of all tocsectX tags. > > > > What is causing this (others have problems with it too?). > > > > Regards, > > Mikael Hallendal > > > > > > > _______________________________________________ > Scrollkeeper-devel mailing list > Scr...@li... > https://lists.sourceforge.net/lists/listinfo/scrollkeeper-devel > |
|
From: Dan M. <mu...@al...> - 2002-03-11 04:01:44
|
I can't reproduce this problem, so I'm not sure what is causing it. Here are a couple things you might try doing to the stylesheet to see if it helps: (1) Try removing the 9 lines: <xsl:param name="toclevel"/> from /usr/share/scrollkeeper/stylesheets/toc.xsl. (2) Try replacing these lines with: <xsl:param name="toclevel" select="0"/> Technically (2) is the best, although all 3 forms work fine for me. Do these help? Does the index stylesheet work okay for you? Dan On 5 Mar 2002, Mikael Hallendal wrote: > Hi! > > ScrollKeeper keeps generating broken TOC-files for me, this is how they > look: > > <?xml version="1.0"?> > <toc> > <tocsect1, linkid="intro">Introduction > </tocsect1,> > <tocsect1, linkid="usage">Using GNOME Calculator > <tocsect2, linkid="mainwin">Basic usage > </tocsect2,> > <tocsect2, linkid="menubar">Menus > </tocsect2,> > <tocsect2, linkid="buttons">Buttons > </tocsect2,> > </tocsect1,> > <tocsect1, linkid="bugs">Known Bugs and Limitations > </tocsect1,> > <tocsect1, linkid="authors">Authors > </tocsect1,> > <tocsect1, linkid="license">License > </tocsect1,> > </toc> > > notice the , in the end of all tocsectX tags. > > What is causing this (others have problems with it too?). > > Regards, > Mikael Hallendal > > |
|
From: Dan M. <mu...@al...> - 2002-03-10 07:20:59
|
Kevin, Thanks for pointing out the duplicate use of that id string. I'm a bit disturbed that the warning goes to STDOUT. I don't get this warning at all on my system, even in the ScrollKeeper log file where warnings are typically sent. Do you get the error if you do: (a) /usr/bin/scrollkeeper-extract /usr/share/scrollkeeper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.xml /usr/share/scrollkeeper/stylesheets/index.xsl /tmp/foo or (b) /usr/bin/scrollkeeper-extract /usr/share/scrollkeeper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.xml /usr/share/scrollkeeper/stylesheets/toc.xsl /tmp/foo2 Which versions of libxml2 and libxslt do you have? Dan On 27 Feb 2002, Kevin Breit wrote: > Dan, > Whats up with this? > > rpm -[root@kbreit kbreit]# rpm -Uvh scrollkeeper-0.3.5-1.i386.rpm > Preparing... ########################################### > [100%] > 1:scrollkeeper ########################################### > [100%] > /usr/share/scrollkeeper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.xml:783: validity error: ID skomf-seriesid already defined > <sect2 id="skomf-seriesid"> > ^ > > > Kevin > |
|
From: Mikael H. <mi...@co...> - 2002-03-05 12:19:14
|
Hi! ScrollKeeper keeps generating broken TOC-files for me, this is how they look: <?xml version="1.0"?> <toc> <tocsect1, linkid="intro">Introduction </tocsect1,> <tocsect1, linkid="usage">Using GNOME Calculator <tocsect2, linkid="mainwin">Basic usage </tocsect2,> <tocsect2, linkid="menubar">Menus </tocsect2,> <tocsect2, linkid="buttons">Buttons </tocsect2,> </tocsect1,> <tocsect1, linkid="bugs">Known Bugs and Limitations </tocsect1,> <tocsect1, linkid="authors">Authors </tocsect1,> <tocsect1, linkid="license">License </tocsect1,> </toc> notice the , in the end of all tocsectX tags. What is causing this (others have problems with it too?). 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 |
|
From: Kevin B. <mrp...@xi...> - 2002-02-27 21:13:23
|
Dan,
Whats up with this?
rpm -[root@kbreit kbreit]# rpm -Uvh scrollkeeper-0.3.5-1.i386.rpm
Preparing... ###########################################
[100%]
1:scrollkeeper ###########################################
[100%]
/usr/share/scrollkeeper/doc/writing_scrollkeeper_omf_files/C/writing_scrollkeeper_omf_files.xml:783: validity error: ID skomf-seriesid already defined
<sect2 id="skomf-seriesid">
^
Kevin
|
|
From: Dan M. <mu...@al...> - 2002-02-27 06:58:09
|
ScrollKeeper 0.3.5 is now available.
New in this release:
* Rewritten output and logging system to allow better control of where
messages are sent.
* Many improved and new output and log messages to help users identify
problems or bugs and keep track of things.
* New "Writing ScrollKeeper OMF Files" document.
* Removed dependency on openjade package.
* Added -q (quiet) flags to some administrative commands, since they
now give more output by default.
* Updated URL for DocBook DTD resource to point to new page and
tarballs on ScrollKeeper web site at
http://scrollkeeper.sourceforge.net/docbook.shtml
* Small improvements to build setup and RPM spec file.
* Updated TODO file.
You can get ScrollKeeper 0.3.5 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
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
|
|
From: Dan M. <mu...@al...> - 2002-02-17 20:04:05
|
Hi, We have a new batch of tarballs for the latest DocBook DTD and stylesheets. These are the standard Norman Walsh packages with a couple scripts and Makefiles added to make sure everything gets registered in the XML catalogs. Grab them from: http://scrollkeeper.sourceforge.net/docbook.shtml Thanks to Norman Walsh (author and maintainer of DocBook), Daniel Veillard (author of XML catalog registration script and libxml), and Eric Baudais (author of the Makefile and edits to the scripts). Please report any problems you find. The next stable releases of GNOME2 and ScrollKeeper will require DocBook DTDs and stylesheets be registered in the XML catalog. -Dan PS: At a minimum, you should get paths from the two commands: (a) xmlcatalog /etc/xml/catalog "-//OASIS//DTD DocBook XML V4.1.2//EN" and (b) xmlcatalog /etc/xml/catalog http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl and the files they refer to should actually exist on your machine. |
|
From: Dan M. <mu...@al...> - 2002-02-16 06:01:29
|
I just finished a new document on writing OMF files for use with ScrollKeeper. You can find it online at: http://scrollkeeper.sf.net/documentation/writing_scrollkeeper_omf_files/index.html Feedback is welcome. Dan |
|
From: Dan M. <d-...@uc...> - 2002-01-24 08:50:35
|
ScrollKeeper 0.3.4 is now available. All developers and testers
are encouraged to upgrade to 0.3.4.
The main change from 0.3.3 is that index and TOC extraction has been
temporarily disabled for SGML documents. This was done because many
distributions do not register the SGML DTDs with the catalog properly and
ScrollKeeper wasn't checking the validity of the generated XML document
before passing it to libxml2. Thus, a lot of ugly error messages were
being produced on many systems. After we add the appropriate error
handling and some distributions start registering their SGML DTDs with the
catalog, we will re-enable these features.
Note that ScrollKeeper requires that the DocBook XML 4.1.2 DTD be
installed and registered in the XML catalog, and it still extracts the TOC
and index for DocBook/XML documents.
You can get ScrollKeeper 0.3.4 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
- The ScrollKeeper Team
|
|
From: Dan M. <d-...@uc...> - 2002-01-16 08:38:59
|
ScrollKeeper 0.3.3 is now available. This release fixes a few build issues
and nasty little bugs in 0.3.1 and 0.3.2 (which never quite got released).
If you had any problems building 0.3.1, try out 0.3.3.
New in this release:
* Fixed problems in 0.3.1 with tarball.
* Several improvements and fixes to RPM spec file scripts, including
a nasty problem where upgrading SK leaves the user without a SK
database.
* configure script now uses xmlcatalog to detect DocBook DTD presence.
* A couple other configure script improvements.
* Corrected system identifier in generated documents.
* Updated TODO file.
You can get ScrollKeeper 0.3.3 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
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
|
|
From: Dan M. <d-...@uc...> - 2002-01-14 04:34:15
|
ScrollKeeper 0.3.1, the second release in the unstable development series,
is now available for your testing and development pleasure.
New in this release:
* Now uses intltool instead of xml-i18n-tools.
* New TODO file which lists many of the top bugs and tasks which need to
be done, as well as some less high-priority ones.
* More detailed log entries, including time and date stamps and log
entries for more document registration and unregistration events.
* Several updated translations.
* Log file now tracks @localstatedir@.
* Added man page for scrollkeeper.conf and updated some older man pages.
* Fixed bug where RPM didn't remove ScrollKeeper log files when
ScrollKeeper is uninstalled.
You can get ScrollKeeper 0.3.1 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
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 file 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
|
|
From: Dan M. <d-...@uc...> - 2002-01-11 05:00:36
|
I just put together a page listing the help browsers which I know of which use ScrollKeeper at: http://scrollkeeper.sourceforge.net/browsers.shtml If anybody knows of any others or have suggestions for improved blurbs, screenshots, URL's, or additional info, please send them to me or this list and I'll update the page. Dan |
|
From: Dan M. <d-...@uc...> - 2002-01-03 03:59:46
|
On 2 Jan 2002, Alexander Kirillov wrote: > Thanks! > BTW, I tried to find it on scrollkeeper.sourceforge.net, and not only I > couldn't find the tree itself but even its existence was hidden deep > inside ScrollKeeper 0.2 Specifications. All other pages (e.g., the top > level page) just referred to 16-element OMF specification from metalab, > which says nothing about the category tree. IMHO, existence of this tree > - and the fact that it should be strictly enforced when writing OMF > files - should be prominently posted on scrollkeeper web page. That is a really good idea. In fact, we really should have a little mini-tutorial on writing OMF files with an example OMF file and explanation of how to use each field, in the context of ScrollKeeper. Part of this would be a list of all the categories. And since you mention it, I guess we should start writing up the 0.4 Specifications pretty soon. The changes from 0.2 are pretty well contained to a list of feature improvements which has been added, although the database file formats have matured somewhat. I'm adding these to my TODO list, which I'll put into CVS after I clean it up somewhat. If anybody is looking for something to do before I get it checked in, feel free to email me or just pick anything which interests you. Dan |
|
From: David M. <da...@lu...> - 2002-01-02 23:33:54
|
On Wed, Jan 02, 2002 at 12:18:36AM -0600, Dan Mueth wrote: > > On Tue, 1 Jan 2002, David Merrill wrote: > > > On Tue, Jan 01, 2002 at 06:50:02PM -0500, Alexander Kirillov wrote: > > > Hi guys: > > > can anyone tell me where I can find the tree of categories to use in OMF > > > files? > > > > On a side note, how cast in stone is the tree? I will need to merge > > the LDP into it soon, so I expect I will uncover problems. > > The categories are specified in an XML file installed by ScrollKeeper, > typically at /usr/share/scrollkeeper/Templates/C/scrollkeeper_cl.xml. > This is then translated into other locales at > /usr/share/scrollkeeper/Templates/<locale>/scrollkeeper_cl.xml. > > Developing a much improved category tree is really a small project in > itself which could use some work. We should maintain backward > compatibility, expanding on the categories which are presently used. > Nobody is presently working on this, so help is welcome. > > One of the new features of the 0.3/0.4 release cycle is that we use > categorycodes to allow scrollkeeper to identify analogous sections in > different locales. This is useful for including multiple locales in a > single category tree and also allows translators to not translate the > categories in OMF files if they don't want to (saves time and reduces risk > of errors). So, if you want to work on the category tree, make sure you > get the current development version, 0.3.0. I asked for a volunteer on the LDP list to help with this. I'll let you know if I find anyone. Also, Colin Watson, who packages the LDP for Debian, just wrote me about it. So he might be willing to help some. For now, I recommended he install all of the LDP under General/Other and then we'll work through them to move them elsewhere. -- David C. Merrill http://www.lupercalia.net Linux Documentation Project da...@lu... Collection Editor & Coordinator http://www.linuxdoc.org A wise and frugal government, which shall restrain men from injuring one another; shall leave them otherwise free to regulate their own pursuits of industry and improvement. -- Thomas Jefferson |
|
From: Alexander K. <kir...@ma...> - 2002-01-02 15:50:09
|
Thanks! BTW, I tried to find it on scrollkeeper.sourceforge.net, and not only I couldn't find the tree itself but even its existence was hidden deep inside ScrollKeeper 0.2 Specifications. All other pages (e.g., the top level page) just referred to 16-element OMF specification from metalab, which says nothing about the category tree. IMHO, existence of this tree - and the fact that it should be strictly enforced when writing OMF files - should be prominently posted on scrollkeeper web page. Sasha On Wed, 2002-01-02 at 01:18, Dan Mueth wrote: > > On Tue, 1 Jan 2002, David Merrill wrote: > > > On Tue, Jan 01, 2002 at 06:50:02PM -0500, Alexander Kirillov wrote: > > > Hi guys: > > > can anyone tell me where I can find the tree of categories to use in OMF > > > files? > > > > On a side note, how cast in stone is the tree? I will need to merge > > the LDP into it soon, so I expect I will uncover problems. > > The categories are specified in an XML file installed by ScrollKeeper, > typically at /usr/share/scrollkeeper/Templates/C/scrollkeeper_cl.xml. > This is then translated into other locales at > /usr/share/scrollkeeper/Templates/<locale>/scrollkeeper_cl.xml. > > Developing a much improved category tree is really a small project in > itself which could use some work. We should maintain backward > compatibility, expanding on the categories which are presently used. > Nobody is presently working on this, so help is welcome. > > One of the new features of the 0.3/0.4 release cycle is that we use > categorycodes to allow scrollkeeper to identify analogous sections in > different locales. This is useful for including multiple locales in a > single category tree and also allows translators to not translate the > categories in OMF files if they don't want to (saves time and reduces risk > of errors). So, if you want to work on the category tree, make sure you > get the current development version, 0.3.0. > > Dan > > > _______________________________________________ > gnome-doc-list mailing list > gno...@gn... > http://mail.gnome.org/mailman/listinfo/gnome-doc-list |
|
From: Dan M. <d-...@uc...> - 2002-01-02 06:18:50
|
On Tue, 1 Jan 2002, David Merrill wrote: > On Tue, Jan 01, 2002 at 06:50:02PM -0500, Alexander Kirillov wrote: > > Hi guys: > > can anyone tell me where I can find the tree of categories to use in OMF > > files? > > On a side note, how cast in stone is the tree? I will need to merge > the LDP into it soon, so I expect I will uncover problems. The categories are specified in an XML file installed by ScrollKeeper, typically at /usr/share/scrollkeeper/Templates/C/scrollkeeper_cl.xml. This is then translated into other locales at /usr/share/scrollkeeper/Templates/<locale>/scrollkeeper_cl.xml. Developing a much improved category tree is really a small project in itself which could use some work. We should maintain backward compatibility, expanding on the categories which are presently used. Nobody is presently working on this, so help is welcome. One of the new features of the 0.3/0.4 release cycle is that we use categorycodes to allow scrollkeeper to identify analogous sections in different locales. This is useful for including multiple locales in a single category tree and also allows translators to not translate the categories in OMF files if they don't want to (saves time and reduces risk of errors). So, if you want to work on the category tree, make sure you get the current development version, 0.3.0. Dan |
|
From: Dan M. <d-...@uc...> - 2001-12-31 02:11:57
|
On Mon, 24 Dec 2001, David Merrill wrote: > I've worked on the scripts that generate OMF from the LDP data. It is > available from db.linuxdoc.org if you want to look at it. I'm trying > to provide as complete an omf structure as possible. > > I'll be doing some testing with my omf to make sure sk doesn't barf on > it. I'll let you know how it goes. I'm happy to hear the LDP documents will get OMF metadata, hopefully without too much effort. I'm curious... How much of the LDP documentation is available in DocBook? Also, do people index many of their DocBook documents? Support for indexing is now in the development version of ScrollKeeper, although I imagine most DocBook documentation still needs to be indexed. Dan |
|
From: David M. <da...@lu...> - 2001-12-24 06:42:45
|
I've worked on the scripts that generate OMF from the LDP data. It is available from db.linuxdoc.org if you want to look at it. I'm trying to provide as complete an omf structure as possible. I'll be doing some testing with my omf to make sure sk doesn't barf on it. I'll let you know how it goes. -- Dr. David C. Merrill http://www.lupercalia.net Linux Documentation Project da...@lu... Collection Editor & Coordinator http://www.linuxdoc.org We all come from the Goddess And to Her we shall return Like a drop of rain Flowing to the ocean |
|
From: Ismael O. <is...@ol...> - 2001-12-24 02:52:51
|
FYI. It looks that it is something like a e-publishing system based on RDF. Parece que esta gente est=E1 trabajando en un sistema de publicaci=F3n-e basado en RDF. --=20 A.Ismael Olea Gonz=E1lez mailto:is...@ol... http://www.olea.org El mundo debe empezar a tener miedo a un planeta OLEA |
|
From: Dan M. <d-...@uc...> - 2001-12-05 06:29:04
|
Due to popular demand, ScrollKeeper 0.3.0 is now available. Thanks to lots of hard work by Laszlo and Mary, version 0.3.0 has a number of new features. These include: Support for both XML and SGML DocBook documents, improved i18n, index extraction from DocBook documents, and configurable OMF paths using a system-wide configuration file and user-configurable shell variables. This is the first release in the 0.3.x (development) series and should not be used on end-user machines. The current stable release is 0.2. ScrollKeeper 0.3.0 has undergone minimal testing. I am hoping that various developers will test it in different environments and help us to quickly reach a stable 0.4.0 release. Be warned that this release is very bumpy and the requirements may be difficult to satisfy on certain distributions. You can get ScrollKeeper 0.3.0 at: http://sourceforge.net/projects/scrollkeeper Please send any questions, patches, bug reports, and information which may be useful to others to scr...@li.... Instructions on how to satisfy the dependencies on particular distributions would also be helpful, since it requires the newer XML/docbook setup and tools. - The ScrollKeeper Team |
|
From: Rich M. <rd...@cf...> - 2001-11-30 16:30:03
|
Thanks for the nice write-up on SK. I have been watching it evolve for a while now, hoping that it can serve as a component in the Meta Project (http://www.cfcl.com/Meta), my exploration into integrating system metadata and documentation. As you note, a typical *nix system contains many thousands of files. At some level, the system "knows" what each of the files is for, how it is formatted, etc. After all, if it didn't, it couldn't use them. Unfortunately, this knowledge is largely unavailable to the user. If I want to know the purposes and format of /etc/frammitz, I may have a bit of work ahead of me. Sometimes there will be a man page; other times there will only be a FILES reference in a man page, if that. As a way of exploring this issue, I have prototyped a "browser" for files and man pages. Using mechanically-derived data, hand-edited annotation files, and a small set of "rules", I generate a graph of the files in an operating system distribution. Then, when someone asks for information on a given file or manual page, a CGI script can explore the local neighborhood of the file in the graph, printing out a list of (putatively :-) relevant items. I have been using *nix systems for ~20 years, so I am quite familiar with the system file tree. Nonetheless, I find that the browser frequently comes up with useful relationships I hadn't suspected. A newer user would, of course, find even more "new" information. As a way of using this information (and funding further efforts), I have decided to start publishing documentation collections. See the DOSSIER (http://www.ptf.com/dossier) web page for more information. While some of the volumes are merely printed versions of substantial sets of Open Source documentation (e.g., the PostgreSQL manuals), I have also pulled together some topical sets of papers and man pages: Email: Mail and Sendmail File Systems: FreeBSD Manual Pages Kernel: FreeBSD Manual Pages Text: Manual Pages If even a tiny fraction of the user community decides that these are useful, I will be able to continue creating and publishing new sets. This, in turn, should allow me to move on to the next generation of the browser, using ScrollKeeper and other appropriate technologies. -r -- email: rd...@cf...; phone: +1 650-873-7841 http://www.cfcl.com/rdm - home page, resume, etc. http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser http://www.ptf.com/tdc - Prime Time Freeware's Darwin Collection |
|
From: <las...@Su...> - 2001-11-30 09:38:53
|
Very good article indeed:-) Thanks Kendall. Laszlo |
|
From: Dan M. <d-...@uc...> - 2001-11-29 20:46:09
|
On Thu, 29 Nov 2001, Kendall Clark wrote: > ScrollKeeper: Open Source Document Management > http://www.xml.com/pub/a/2001/11/28/scrollkeeper.html > > Best, > Kendall Clark Thanks a lot for the link and for writing such a nice article. I really enjoyed reading it and got a new perspective on the project :) Dan |