doc-book-users — Helping users to install and configure DocBookWiki

Re: [doc-book-users] Problems with chapter and section ids

[Richard R. <ma...@ri...>]

Hello Dashamir,

Dashamir Hoxha schrieb:
> Hi Ritchi,
>
[...]
> 
> However I am curious to know which version of docbookwiki
> you have installed, in which distribution, how you plan to
> use it, what you expect from it, etc.
> 
We are running docbookwiki 0.9.1cvs on a debian squeeze system.
Installed out of the debian package.

We are a team of three persons developing software and want to write
the manuals for this software in a format that allows us to generate
different output formats like pdf, latex, html. Therefore is docbook the
right format to store the content.

On the other hand the writer is not a computer geek. She needs an
intuitive and easy to use environment. So docbookwiki with its
webfrontend seems to be an ideal solution. The first experience is that
docbookwiki is not soo intuitive to use ;). But our hope *was* that
this situation will maybe change in the future.

Now we are going on to check out docbookwiki and if no bigger issues 
appear we will use it for the daily work.

Thank you and regards
Ritchi

Re: [doc-book-users] Problems with chapter and section ids

[Dashamir H. <das...@gm...>]

Hi Ritchi,

You are right. Since it cannot handle the ids with spaces, it
should not accept them and the user should be notified.
It can be fixed, however I don't think it is so important.

If you don't encounter other problems bigger than this, then you
should consider yourself lucky. I don't want to discourage you
about trying it, but to be honest, right now I am not using it even
for myself.

However I am curious to know which version of docbookwiki
you have installed, in which distribution, how you plan to
use it, what you expect from it, etc.

Regards,
Dashamir


On Mon, Sep 21, 2009 at 11:41 AM, Richard Rafalski
<ma...@ri...> wrote:
> Hallo,
>
> thank you for the creation of docbookwiki. We want to use it within a
> software project to write the documentation. But just on the beginning
> we run into a useability problem.
>
> docbookwiki have problems to manage ids with spaces. One can create a
> chapter/section with the id 'test chapter' but docbookwiki is not able
> to manage such ids.
>
> Therefore docbookwiki should not accept ids with spaces. The user should
> get a warning and the input should be ignored.
>
> Are there chances that this issue will be solved?
>
> Cheers
> Ritchi
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>

[doc-book-users] Problems with chapter and section ids

[Richard R. <ma...@ri...>]

Hallo,

thank you for the creation of docbookwiki. We want to use it within a 
software project to write the documentation. But just on the beginning 
we run into a useability problem.

docbookwiki have problems to manage ids with spaces. One can create a 
chapter/section with the id 'test chapter' but docbookwiki is not able 
to manage such ids.

Therefore docbookwiki should not accept ids with spaces. The user should 
get a warning and the input should be ignored.

Are there chances that this issue will be solved?

Cheers
Ritchi

[doc-book-users] docbook to html

[jdd f. http://tldp.o. <jd...@do...>]

Hello,

I have problems translating hmtl to MoinMoin wiki markup.

in fact the html itself is generated from a docbook original by the
ldp jade based toolchain.

the source is the <screen><screen/> markup. The html produced is a
table with included <pre> html.

AFAIK, the <pre> itself is enough in the html code to render a <screen>.

What am I missing? is the table mandatory or is there a way to tell
jade not to includ one? The entire toolchain is pretty complicated.

thanks
jdd
-- 
jdd for the Linux Documentation Project
http://wiki.tldp.org
http://www.dodin.net

Re: [doc-book-users] docbook to html

[jdd <jd...@do...>]

jdd for http://tldp.org a écrit :
> Hello,
> 
> I have problems translating hmtl to MoinMoin wiki markup.

don't worry, in fact I found the solution right now! Th ldp toolchain
is probably a bit old, installing all the stuff on my brand new
openSUSE 11.1 gave ok result (no more table).

thanks anyway
jdd


-- 
http://www.dodin.net
http://valerie.dodin.org
http://www.youtube.com/watch?v=t-eic8MSSfM

Re: [doc-book-users] Bug: WebApp Error: Parser::parse_file(): file 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.

[Cyril D. <cyr...@gm...>]

I forgot to say you have to run 'search/make_index.sh' again after
making changes to global_index.cfg, "obviously".

On Mon, Nov 17, 2008 at 2:18 AM, Cyril DANGERVILLE
<cyr...@gm...> wrote:
> Hello,
> FYI, I solved the first bug 1) mentioned below with the following change:
>
> diff -ur docbookeasy-svn/search/global_index.cfg
> docbookeasy/search/global_index.cfg
> --- docbookeasy-svn/search/global_index.cfg     2005-04-15 07:32:01.000000000 +0200
> +++ docbookeasy/search/global_index.cfg 2008-11-17 01:38:44.000000000 +0100
> @@ -42,7 +42,7 @@
>  #ExtractPath *metaname* [replace|remove|prepend|append|regex]
>  ExtractPath book_id regex !^.*/books/xml/([^/]+)/.*$!$1!
>  ExtractPath lng regex !^.*/books/xml/[^/]+/([^/]+)/.*$!$1!
> -ExtractPath path regex !^.*/books/xml/[^/]+/[^/]+/(.*/)[^/]+$!$1!
> +ExtractPath path regex !^.*/books/xml/[^/]+/[^/]+/(.*)$!$1!
>
>  # This can be used with ExtractPath to set a default string to index under
>  # the given metaname if none of the ExtractPath patterns match.
> diff -ur docbookeasy-svn/templates/main/main.php
> docbookeasy/templates/main/main.php
> --- docbookeasy-svn/templates/main/main.php     2008-03-27 07:06:48.000000000 +0100
> +++ docbookeasy/templates/main/main.php 2008-11-17 02:05:19.000000000 +0100
> @@ -156,7 +155,8 @@
>       }
>     else
>       {
> -        $chunk = $event_args['chunk'];
> +        // remove '.xml'  extension from node_path
> +       $chunk = substr($event_args['node_path'], 0, -4);
>         $lng = $event_args['lng'];
>         if ($lng=='')
>           {
> ------------
>
> I hope it helps. Next time, I do a 'svn diff' to have a proper patch.
> Promised ;)
> -- Cyril
>
>
> On Thu, Nov 13, 2008 at 6:50 AM, Dashamir Hoxha <das...@gm...> wrote:
>> Hi Cyril,
>>
>> It is clearly a bug. You can expect many other things like this, since
>> docbookeasy 1.0 is
>> just an initial release, not a stable one (maybe the release number
>> should have been 0.1).
>>
>> If you are kind of a developer and don't mind to get hands dirty in
>> the code, I can give you
>> any hint and you can try to fix it yourself. Otherwise I will try to
>> fix it when I have time and
>> I will let you know when it is done.
>>
>> Regards,
>> Dashamir
>>
>> On Thu, Nov 13, 2008 at 2:45 AM, Cyril DANGERVILLE
>> <cyr...@gm...> wrote:
>>> Hello,
>>> I just installed docbookeasy 1.0. This application seems great overall.
>>> However, I am facing a couple of bugs that I'd like some help with:
>>>
>>> 1) When doing searches:
>>> Say I am searching "subversion" in the Docbookeasy docbook (just an
>>> example, the result is the same with search in general). I get "5
>>> nodes found", that's OK. But if I click on any of the results, say
>>> "General Overview" - the link reads
>>> "javascript:display('docbookeasy','docbookeasy/managing_content/','en')"
>>> in case this helps - I get this error message:
>>>
>>> ---
>>> WebApp Error: Parser::parse_file(): file
>>> 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.
>>> ---
>>>
>>> (Note: the title says "{up_title} -->  {this_title} ".)
>>> Something wrong with the node path?
>>>
>>> 2) Just for testing if I would get the same error, I tried to go to
>>> the node by entering the URL manually as told in the documentation:
>>> "xref.php?mode/book_id/sect_id/lng". In my example, this gives
>>> "xref.php?view/docbookeasy/managing_content/en" (correct me if I'm
>>> wrong). This time, I get this more meaningful error message:
>>>
>>> ---
>>> WebApp Error: Parser::parse_file(): file
>>> 'content/books/xhtml/docbookeasy/en/warning: failed to load external
>>> entity "xslt/edit/get_node_path.xsl" cannot parse
>>> xslt/edit/get_node_path.xsl .xhtml' does not exist.
>>> ---
>>>
>>> I could notice there is no such file as "xslt/edit/get_node_path.xsl"
>>> indeed. (I noticed this file exists in the former docbookwiki version.
>>> Has it been replaced with another xsl?)
>>>
>>> How to fix it?
>>>
>>> Thanks for the help.
>>>
>>> Regards,
>>> --Cyril
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in the world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> Doc-book-users mailing list
>>> Doc...@li...
>>> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>>>
>>
>

Re: [doc-book-users] Bug: WebApp Error: Parser::parse_file(): file 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.

[Cyril D. <cyr...@gm...>]

Hello,
FYI, I solved the first bug 1) mentioned below with the following change:

diff -ur docbookeasy-svn/search/global_index.cfg
docbookeasy/search/global_index.cfg
--- docbookeasy-svn/search/global_index.cfg	2005-04-15 07:32:01.000000000 +0200
+++ docbookeasy/search/global_index.cfg	2008-11-17 01:38:44.000000000 +0100
@@ -42,7 +42,7 @@
 #ExtractPath *metaname* [replace|remove|prepend|append|regex]
 ExtractPath book_id regex !^.*/books/xml/([^/]+)/.*$!$1!
 ExtractPath lng regex !^.*/books/xml/[^/]+/([^/]+)/.*$!$1!
-ExtractPath path regex !^.*/books/xml/[^/]+/[^/]+/(.*/)[^/]+$!$1!
+ExtractPath path regex !^.*/books/xml/[^/]+/[^/]+/(.*)$!$1!

 # This can be used with ExtractPath to set a default string to index under
 # the given metaname if none of the ExtractPath patterns match.
diff -ur docbookeasy-svn/templates/main/main.php
docbookeasy/templates/main/main.php
--- docbookeasy-svn/templates/main/main.php	2008-03-27 07:06:48.000000000 +0100
+++ docbookeasy/templates/main/main.php	2008-11-17 02:05:19.000000000 +0100
@@ -156,7 +155,8 @@
       }
     else
       {
-        $chunk = $event_args['chunk'];
+        // remove '.xml'  extension from node_path
+	$chunk = substr($event_args['node_path'], 0, -4);
         $lng = $event_args['lng'];
         if ($lng=='')
           {
------------

I hope it helps. Next time, I do a 'svn diff' to have a proper patch.
Promised ;)
-- Cyril


On Thu, Nov 13, 2008 at 6:50 AM, Dashamir Hoxha <das...@gm...> wrote:
> Hi Cyril,
>
> It is clearly a bug. You can expect many other things like this, since
> docbookeasy 1.0 is
> just an initial release, not a stable one (maybe the release number
> should have been 0.1).
>
> If you are kind of a developer and don't mind to get hands dirty in
> the code, I can give you
> any hint and you can try to fix it yourself. Otherwise I will try to
> fix it when I have time and
> I will let you know when it is done.
>
> Regards,
> Dashamir
>
> On Thu, Nov 13, 2008 at 2:45 AM, Cyril DANGERVILLE
> <cyr...@gm...> wrote:
>> Hello,
>> I just installed docbookeasy 1.0. This application seems great overall.
>> However, I am facing a couple of bugs that I'd like some help with:
>>
>> 1) When doing searches:
>> Say I am searching "subversion" in the Docbookeasy docbook (just an
>> example, the result is the same with search in general). I get "5
>> nodes found", that's OK. But if I click on any of the results, say
>> "General Overview" - the link reads
>> "javascript:display('docbookeasy','docbookeasy/managing_content/','en')"
>> in case this helps - I get this error message:
>>
>> ---
>> WebApp Error: Parser::parse_file(): file
>> 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.
>> ---
>>
>> (Note: the title says "{up_title} -->  {this_title} ".)
>> Something wrong with the node path?
>>
>> 2) Just for testing if I would get the same error, I tried to go to
>> the node by entering the URL manually as told in the documentation:
>> "xref.php?mode/book_id/sect_id/lng". In my example, this gives
>> "xref.php?view/docbookeasy/managing_content/en" (correct me if I'm
>> wrong). This time, I get this more meaningful error message:
>>
>> ---
>> WebApp Error: Parser::parse_file(): file
>> 'content/books/xhtml/docbookeasy/en/warning: failed to load external
>> entity "xslt/edit/get_node_path.xsl" cannot parse
>> xslt/edit/get_node_path.xsl .xhtml' does not exist.
>> ---
>>
>> I could notice there is no such file as "xslt/edit/get_node_path.xsl"
>> indeed. (I noticed this file exists in the former docbookwiki version.
>> Has it been replaced with another xsl?)
>>
>> How to fix it?
>>
>> Thanks for the help.
>>
>> Regards,
>> --Cyril
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Doc-book-users mailing list
>> Doc...@li...
>> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>>
>

Re: [doc-book-users] Bug: WebApp Error: Parser::parse_file(): file 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.

[Dashamir H. <das...@gm...>]

Hi Cyril,

It is clearly a bug. You can expect many other things like this,
since docbookeasy 1.0 is just an initial release, not a stable one
(maybe the release number should have been 0.1).

If you are kind of a developer and don't mind to get hands dirty
in the code, I can give you any hint and you can try to fix it yourself.
Otherwise I will try to fix it when I have time and I will let you know
when it is done.

Regards,
Dashamir

On Thu, Nov 13, 2008 at 2:45 AM, Cyril DANGERVILLE
<cyr...@gm...> wrote:
> Hello,
> I just installed docbookeasy 1.0. This application seems great overall.
> However, I am facing a couple of bugs that I'd like some help with:
>
> 1) When doing searches:
> Say I am searching "subversion" in the Docbookeasy docbook (just an
> example, the result is the same with search in general). I get "5
> nodes found", that's OK. But if I click on any of the results, say
> "General Overview" - the link reads
> "javascript:display('docbookeasy','docbookeasy/managing_content/','en')"
> in case this helps - I get this error message:
>
> ---
> WebApp Error: Parser::parse_file(): file
> 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.
> ---
>
> (Note: the title says "{up_title} -->  {this_title} ".)
> Something wrong with the node path?
>
> 2) Just for testing if I would get the same error, I tried to go to
> the node by entering the URL manually as told in the documentation:
> "xref.php?mode/book_id/sect_id/lng". In my example, this gives
> "xref.php?view/docbookeasy/managing_content/en" (correct me if I'm
> wrong). This time, I get this more meaningful error message:
>
> ---
> WebApp Error: Parser::parse_file(): file
> 'content/books/xhtml/docbookeasy/en/warning: failed to load external
> entity "xslt/edit/get_node_path.xsl" cannot parse
> xslt/edit/get_node_path.xsl .xhtml' does not exist.
> ---
>
> I could notice there is no such file as "xslt/edit/get_node_path.xsl"
> indeed. (I noticed this file exists in the former docbookwiki version.
> Has it been replaced with another xsl?)
>
> How to fix it?
>
> Thanks for the help.
>
> Regards,
> --Cyril
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>

Re: [doc-book-users] Bug: WebApp Error: Parser::parse_file(): file 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.

[Dashamir H. <das...@gm...>]

Hi Cyril,

It is clearly a bug. You can expect many other things like this, since
docbookeasy 1.0 is
just an initial release, not a stable one (maybe the release number
should have been 0.1).

If you are kind of a developer and don't mind to get hands dirty in
the code, I can give you
any hint and you can try to fix it yourself. Otherwise I will try to
fix it when I have time and
I will let you know when it is done.

Regards,
Dashamir

On Thu, Nov 13, 2008 at 2:45 AM, Cyril DANGERVILLE
<cyr...@gm...> wrote:
> Hello,
> I just installed docbookeasy 1.0. This application seems great overall.
> However, I am facing a couple of bugs that I'd like some help with:
>
> 1) When doing searches:
> Say I am searching "subversion" in the Docbookeasy docbook (just an
> example, the result is the same with search in general). I get "5
> nodes found", that's OK. But if I click on any of the results, say
> "General Overview" - the link reads
> "javascript:display('docbookeasy','docbookeasy/managing_content/','en')"
> in case this helps - I get this error message:
>
> ---
> WebApp Error: Parser::parse_file(): file
> 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.
> ---
>
> (Note: the title says "{up_title} -->  {this_title} ".)
> Something wrong with the node path?
>
> 2) Just for testing if I would get the same error, I tried to go to
> the node by entering the URL manually as told in the documentation:
> "xref.php?mode/book_id/sect_id/lng". In my example, this gives
> "xref.php?view/docbookeasy/managing_content/en" (correct me if I'm
> wrong). This time, I get this more meaningful error message:
>
> ---
> WebApp Error: Parser::parse_file(): file
> 'content/books/xhtml/docbookeasy/en/warning: failed to load external
> entity "xslt/edit/get_node_path.xsl" cannot parse
> xslt/edit/get_node_path.xsl .xhtml' does not exist.
> ---
>
> I could notice there is no such file as "xslt/edit/get_node_path.xsl"
> indeed. (I noticed this file exists in the former docbookwiki version.
> Has it been replaced with another xsl?)
>
> How to fix it?
>
> Thanks for the help.
>
> Regards,
> --Cyril
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>

Re: [doc-book-users] Bug: WebApp Error: Parser::parse_file(): file 'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.

[Cyril D. <cyr...@gm...>]

Hello,
I just installed docbookeasy 1.0. This application seems great overall.
However, I am facing a couple of bugs that I'd like some help with:

1) When doing searches:
Say I am searching "subversion" in the Docbookeasy docbook (just an
example, the result is the same with search in general). I get "5
nodes found", that's OK. But if I click on any of the results, say
"General Overview" - the link reads
"javascript:display('docbookeasy','docbookeasy/managing_content/','en')"
in case this helps - I get this error message:

---
WebApp Error: Parser::parse_file(): file
'content/books/xhtml/docbookeasy/en/undefined.xhtml' does not exist.
---

(Note: the title says "{up_title} -->  {this_title} ".)
Something wrong with the node path?

2) Just for testing if I would get the same error, I tried to go to
the node by entering the URL manually as told in the documentation:
"xref.php?mode/book_id/sect_id/lng". In my example, this gives
"xref.php?view/docbookeasy/managing_content/en" (correct me if I'm
wrong). This time, I get this more meaningful error message:

---
WebApp Error: Parser::parse_file(): file
'content/books/xhtml/docbookeasy/en/warning: failed to load external
entity "xslt/edit/get_node_path.xsl" cannot parse
xslt/edit/get_node_path.xsl .xhtml' does not exist.
---

I could notice there is no such file as "xslt/edit/get_node_path.xsl"
indeed. (I noticed this file exists in the former docbookwiki version.
Has it been replaced with another xsl?)

How to fix it?

Thanks for the help.

Regards,
--Cyril

Re: [doc-book-users] Linux Documentation Project

[jdd <jd...@do...>]

Dashamir Hoxha a écrit :
> Hi jdd,
> 
> About difficulties of installing and configuring, they are relative.
> For example for me it is easy, for other people it can be more
> difficult.

this is not a real problem. I'm very glad to see you are responsive on 
this list (I already read your mails in the archives). The LDP is 
highly referenced and so we have a great work fighting the spam. our 
test (moinmoin) wiki was horribly spammed, even before being really 
online! new pages where created with lot of advertisement, and robots 
could even register to do so, horrible!

We could

> If you want a wiki where everybody can write and contribute
> something, then maybe this is not the right one. The reason is
> that it has a hierarchical structure of editors and permissions.
> There is a superuser who is able to register other users (editors).
> He can also assign administrators for each book. Then each book
> administrator can give permissions to other users (editors) to
> modify the whole book or branches of it.

this is not a problem. one of our coworker is evaluation docbookwiki 
on his own server. Moinmoin may be more fitted for large audience, we 
will see if we can use docbookwiki internally or elsewhere.

  (DocBookWiki supports just a small
> subset of DocBook tags)

I' not myself very clever about docbook :-(

> Performance issues must also be considered, since
> DocBookWiki (and DocBookEasy) have somehow high
> requirements of disk space. However disk size is not a problem
> nowadays.

we have a new server, plenty of power and room :-)

> 
> In case that you decide to give it a try, I would be happy to
> help you.

thank you, I'll pass this offer along :-))


sincerely
jdd
-- 
http://www.dodin.net
http://valerie.dodin.org

Re: [doc-book-users] Linux Documentation Project

[Dashamir H. <das...@gm...>]

Hi jdd,

About difficulties of installing and configuring, they are relative.
For example for me it is easy, for other people it can be more
difficult. I would be ready to help you for installing and configuring
it, especially if it is acceptable to access your server remotely.

About spam and other security related issues, I am not aware
that it has any, but maybe this is because I have not spent time
searching for them. Anyway, in case that any security problem
is discovered, I would be willing to fix it as soon as I can.

If you want a wiki where everybody can write and contribute
something, then maybe this is not the right one. The reason is
that it has a hierarchical structure of editors and permissions.
There is a superuser who is able to register other users (editors).
He can also assign administrators for each book. Then each book
administrator can give permissions to other users (editors) to
modify the whole book or branches of it.

The difference between the DocBookWiki and DocBookEasy is
that DocBookEasy cannot edit an DocBook document, it can
just display it on the web. However it supports more DocBook
features than DocBookWiki (DocBookWiki supports just a small
subset of DocBook tags). The only way to modify a document
in DocBookEasy is to modify the XML code of the document
and then to publish it again, but this cannot be done online yet
(from the web interface).

Performance issues must also be considered, since
DocBookWiki (and DocBookEasy) have somehow high
requirements of disk space. However disk size is not a problem
nowadays.

In case that you decide to give it a try, I would be happy to
help you.

Best regards,
Dashamir


On Thu, Aug 21, 2008 at 10:48 AM, jdd <jd...@do...> wrote:
> I write here for the Linux Documentation Project. (http://tldp.org,
> http://wiki.tldp.org)
>
> We are evaluating a wiki for LDP workshop. This wiki *have* to cope
> with Docbook, as all our documentation have to be stored in Docbook.
>
> right now, we have moinmoin wiki, but we experiment some difficulties
> configuring it. We also have seen docbookwiki (and docbook easy) but
> we a somewhat concerned to know if this last wiki is fitted for a long
> term and very exposed project as ours.
>
> You must know that spam is a major problem for us, our wiki, even
> before being online is already constantly attacked.
>
> can you give us comments on this?
>
> sincerely yours
> jdd
> --
> http://www.dodin.net
> http://valerie.dodin.org
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users
>

[doc-book-users] Linux Documentation Project

[jdd <jd...@do...>]

I write here for the Linux Documentation Project. (http://tldp.org,
http://wiki.tldp.org)

We are evaluating a wiki for LDP workshop. This wiki *have* to cope
with Docbook, as all our documentation have to be stored in Docbook.

right now, we have moinmoin wiki, but we experiment some difficulties
configuring it. We also have seen docbookwiki (and docbook easy) but
we a somewhat concerned to know if this last wiki is fitted for a long
term and very exposed project as ours.

You must know that spam is a major problem for us, our wiki, even
before being online is already constantly attacked.

can you give us comments on this?

sincerely yours
jdd
-- 
http://www.dodin.net
http://valerie.dodin.org

Re: [doc-book-users] DocBookEasy version 0.1 released

[N. A. C. <nes...@gm...>]

Really cool!! I'm sending you comments as I'm testing it.

2008/3/28, Dashamir Hoxha <das...@gm...>:
> Hi,
>
>  I have made an initial release of DocBookEasy. I have tried to make the
>  installation easy, so that it can be installed without too much efforts.
>
>  Importing a book into the system and displaying it should work for any
>  DocBook document. Converting it to other formats should work as well.
>  However, edit/approve does not work yet, adding media files (images)
>  does not work, etc.
>
>  DocBookEasy has basically the same idea as DocBookWiki, however it
>  chunks the document in a different way. The new way of chunking the
>  document is by using the &lt;xi:include&gt; tags, so the chunks connect
>  naturally to each-other and all of them form a stand-alone DocBook
>  document (while each of them remains a valid DocBook document on
>  itself). So, there is no need for imploding (concating all the chunks),
>  in order to process the whole document (for example converting to
>  another format). It can be done simply by processing the root chunk.
>  This eliminates the need for some "tricks" that are used in DocBookWiki.
>
>  Another difference with DocBookWiki is that DocBookEasy uses
>  customizations of the standard DocBook XSL stylesheets for processing
>  (for example for chunking, for converting to html, etc.). DocBookWiki,
>  on the other hand, uses its own XSL stylesheets.
>
>  One advantage of using customizations of the standard DocBook XSL
>  stylesheets is that DocBookEasy supports all (or most) of the DocBook
>  tags, and most (or many) of the features that are supported by the
>  standard stylesheets. For example, DocBookWiki does not support tables,
>  however, DocBookEasy should support them immediately, as long as the
>  standard stylesheets support them.
>
>  Another advantage is that people who are familiar with the standard
>  stylesheets may understand and customize DocBookEasy easily.
>
>  I am making this initial release hoping that somebody may be interested
>  in playing with it and probably may help me to fix any thing. One thing
>  that can be changed, for example, is improving the display of the
>  content (by customizing the DocBook XSL stylesheets and the CSS files),
>  converting to other formats, etc.
>
>  Regards,
>  Dashamir
>
>  -------------------------------------------------------------------------
>  Check out the new SourceForge.net Marketplace.
>  It's the best place to buy or sell services for
>  just about anything Open Source.
>  http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>  _______________________________________________
>  Doc-book-users mailing list
>  Doc...@li...
>  https://lists.sourceforge.net/lists/listinfo/doc-book-users
>


-- 
Néstor Amigo Cairo
+34 687 96 74 81
nes...@gm...

[doc-book-users] DocBookEasy version 0.1 released

[Dashamir H. <das...@gm...>]

Hi,

I have made an initial release of DocBookEasy. I have tried to make the 
installation easy, so that it can be installed without too much efforts.

Importing a book into the system and displaying it should work for any 
DocBook document. Converting it to other formats should work as well.
However, edit/approve does not work yet, adding media files (images) 
does not work, etc.

DocBookEasy has basically the same idea as DocBookWiki, however it 
chunks the document in a different way. The new way of chunking the 
document is by using the <xi:include> tags, so the chunks connect 
naturally to each-other and all of them form a stand-alone DocBook 
document (while each of them remains a valid DocBook document on 
itself). So, there is no need for imploding (concating all the chunks), 
in order to process the whole document (for example converting to 
another format). It can be done simply by processing the root chunk. 
This eliminates the need for some "tricks" that are used in DocBookWiki.

Another difference with DocBookWiki is that DocBookEasy uses 
customizations of the standard DocBook XSL stylesheets for processing 
(for example for chunking, for converting to html, etc.). DocBookWiki, 
on the other hand, uses its own XSL stylesheets.

One advantage of using customizations of the standard DocBook XSL 
stylesheets is that DocBookEasy supports all (or most) of the DocBook 
tags, and most (or many) of the features that are supported by the 
standard stylesheets. For example, DocBookWiki does not support tables,
however, DocBookEasy should support them immediately, as long as the
standard stylesheets support them.

Another advantage is that people who are familiar with the standard 
stylesheets may understand and customize DocBookEasy easily.

I am making this initial release hoping that somebody may be interested 
in playing with it and probably may help me to fix any thing. One thing 
that can be changed, for example, is improving the display of the 
content (by customizing the DocBook XSL stylesheets and the CSS files), 
converting to other formats, etc.

Regards,
Dashamir

Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

[Bolton, F. <fin...@io...>]

Hello Dashamir,

This is an interesting question, though, for potential users of DocBook Wiki. This is because it would be considerably easier to get DocBook Wiki deployed in a live project if it could piggy-back on a well-known Wiki.

If I get the time, I might try to make an informal assessment of how much effort it might take to perform such an integration. But I appreciate that you are probably right in saying that it would be difficult.

Regards,
Fintan

-----Original Message-----
From: doc...@li... [mailto:doc...@li...] On Behalf Of Dashamir Hoxha
Sent: 11 March 2008 12:35
To: Helping the users of DocBookWiki to install and use it.
Subject: Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

Hi Fintan,

Thanks for the suggestion. However, I am not worried about
"dominating the market" or becoming famous. As long as it
works for me, and as long as the others who use it are satisfied,
I don't worry about fixing or improving it.

So, if you wish, you can try to make such a package, but I think
that it should be very difficult and the chances that you
succeed are very low. Even if I have tried it myself, the chances
that I would succeed would be low. However I don't have time to
try it, because I am already trying something else with it.

Regards,
Dashamir

Bolton, Fintan wrote:
> Hello Dashamir,
> 
> I wonder if you have ever considered re-packaging DocBook Wiki as a
> plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?
> 
> It is a peculiar paradox that, although DocBook Wiki has much better
> DocBook support than any other Wiki out there, it has failed to gain
> much traction in the Wiki space. I suspect the reason for this is that
> there is currently a rather high threshold to getting a new Wiki flavour
> accepted. For example, on a typical open source project, you would have
> very little prospect of persuading an open source community to drop
> Moin-Moin or Confluence in favour of a little-known product like DocBook
> Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
> probably be an uphill battle.
> 
> In marketing terms, therefore, it would be much easier to get DocBook
> Wiki accepted if it came in the form of a Confluence or Moin-Moin
> plug-in. Adding plug-ins to Wikis is a routine procedure that would be
> unlikely to arouse much controversy in an open source community.
> 
> Of course, I am glossing over the technical difficulties here, which
> might be considerable. But the integration would not have to be perfect.
> The main goal would be to make DocBook Wiki look similar enough to the
> host Wiki, so that it can gain acceptance. On a technical level,
> probably the main priorities would be to integrate user administration
> with the host Wiki and to change the appearance of the pages to look
> more like the host Wiki.
> 
> Regards,
> Fintan
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ----------------------------
> IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
> Registernummer: HRB 7939
> Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Doc-book-users mailing list
Doc...@li...
https://lists.sourceforge.net/lists/listinfo/doc-book-users

----------------------------
IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
Registernummer: HRB 7939
Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 

Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

[Pierce T. <pi...@xt...>]

Hi, Dashamir:

You could be right about the relative difficulties. Maybe extending 
MoinMoin would be easier. But as with any open source project, it's easy 
to wish for things--harder to make change happen. Somebody (or some 
people) have to step up and either sponsor the development or do it 
themselves.

I will say, in case people haven't been tracking this, MoinMoin just 
last week did merge some DocBook code from a 1.6 branch into the main 
1.7 trunk. You can read more about that here:

http://moinmo.in/DocBook

However, these updates are by no means the complete DocBook solution for 
MoinMoin--and more work still needs to be done. In fact, MoinMoin on 
their website is actively trying to recruit a DocBook champion to steer 
and take ownership of their DocBook development.

It appears to be a wide open field. Extending MoinMoin with a DocBook 
Wiki plug-in could be on the table--or not, depending on who steps up to 
do (or sponsor) the work.

Regards,
Pierce


Dashamir Hoxha wrote:
> Pierce,
> 
> I don't regret that you have selected MoinMoin. I like it myself.
> However it could be more easy to extend DocBook features of MoinMoin
> than to integrate MoinMoin and DocBookWiki.
> 
> Regards,
> Dashamir
> 
> Pierce Tyler wrote:
>> Hi, Fintan:
>>
>> That is a very interesting idea. It would give users the best of both 
>> worlds, really.
>>
>> We recently finished evaluating wikis for implementation at our site. 
>> And the choice came down to MoinMoin vs. DocBook Wiki. It was an 
>> extremely tough choice. Both packages have strengths and weaknesses. But 
>> in the end we went with MoinMoin because the community is larger and 
>> more active and development is moving forward.
>>
>> While MoinMoin does offer some DocBook support, that support is not 
>> nearly as extensive as DocBook Wiki's. Also, the backend SVN support 
>> offered by DocBook Wiki is something MoinMoin does not currently offer.
>>
>> I suppose integrating a PHP-based application with MoinMoin, which is 
>> written in Python, could pose some challenges. But, again, I really like 
>> this idea if it were possible--or if people were interested in trying to 
>> make it happen.
>>
>> Best regards,
>> Pierce
>>
>>
>> Bolton, Fintan wrote:
>>> Hello Dashamir,
>>>
>>> I wonder if you have ever considered re-packaging DocBook Wiki as a
>>> plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?
>>>
>>> It is a peculiar paradox that, although DocBook Wiki has much better
>>> DocBook support than any other Wiki out there, it has failed to gain
>>> much traction in the Wiki space. I suspect the reason for this is that
>>> there is currently a rather high threshold to getting a new Wiki flavour
>>> accepted. For example, on a typical open source project, you would have
>>> very little prospect of persuading an open source community to drop
>>> Moin-Moin or Confluence in favour of a little-known product like DocBook
>>> Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
>>> probably be an uphill battle.
>>>
>>> In marketing terms, therefore, it would be much easier to get DocBook
>>> Wiki accepted if it came in the form of a Confluence or Moin-Moin
>>> plug-in. Adding plug-ins to Wikis is a routine procedure that would be
>>> unlikely to arouse much controversy in an open source community.
>>>
>>> Of course, I am glossing over the technical difficulties here, which
>>> might be considerable. But the integration would not have to be perfect.
>>> The main goal would be to make DocBook Wiki look similar enough to the
>>> host Wiki, so that it can gain acceptance. On a technical level,
>>> probably the main priorities would be to integrate user administration
>>> with the host Wiki and to change the appearance of the pages to look
>>> more like the host Wiki.
>>>
>>> Regards,
>>> Fintan
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> ----------------------------
>>> IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
>>> Registernummer: HRB 7939
>>> Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Doc-book-users mailing list
>>> Doc...@li...
>>> https://lists.sourceforge.net/lists/listinfo/doc-book-users
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users
> 

-- 
Pierce Tyler
xTuple
119 West York Street
Norfolk, VA 23510
email: pi...@xt...
www.xtuple.com

Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

[Dashamir H. <das...@gm...>]

Pierce,

I don't regret that you have selected MoinMoin. I like it myself.
However it could be more easy to extend DocBook features of MoinMoin
than to integrate MoinMoin and DocBookWiki.

Regards,
Dashamir

Pierce Tyler wrote:
> Hi, Fintan:
> 
> That is a very interesting idea. It would give users the best of both 
> worlds, really.
> 
> We recently finished evaluating wikis for implementation at our site. 
> And the choice came down to MoinMoin vs. DocBook Wiki. It was an 
> extremely tough choice. Both packages have strengths and weaknesses. But 
> in the end we went with MoinMoin because the community is larger and 
> more active and development is moving forward.
> 
> While MoinMoin does offer some DocBook support, that support is not 
> nearly as extensive as DocBook Wiki's. Also, the backend SVN support 
> offered by DocBook Wiki is something MoinMoin does not currently offer.
> 
> I suppose integrating a PHP-based application with MoinMoin, which is 
> written in Python, could pose some challenges. But, again, I really like 
> this idea if it were possible--or if people were interested in trying to 
> make it happen.
> 
> Best regards,
> Pierce
> 
> 
> Bolton, Fintan wrote:
>> Hello Dashamir,
>>
>> I wonder if you have ever considered re-packaging DocBook Wiki as a
>> plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?
>>
>> It is a peculiar paradox that, although DocBook Wiki has much better
>> DocBook support than any other Wiki out there, it has failed to gain
>> much traction in the Wiki space. I suspect the reason for this is that
>> there is currently a rather high threshold to getting a new Wiki flavour
>> accepted. For example, on a typical open source project, you would have
>> very little prospect of persuading an open source community to drop
>> Moin-Moin or Confluence in favour of a little-known product like DocBook
>> Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
>> probably be an uphill battle.
>>
>> In marketing terms, therefore, it would be much easier to get DocBook
>> Wiki accepted if it came in the form of a Confluence or Moin-Moin
>> plug-in. Adding plug-ins to Wikis is a routine procedure that would be
>> unlikely to arouse much controversy in an open source community.
>>
>> Of course, I am glossing over the technical difficulties here, which
>> might be considerable. But the integration would not have to be perfect.
>> The main goal would be to make DocBook Wiki look similar enough to the
>> host Wiki, so that it can gain acceptance. On a technical level,
>> probably the main priorities would be to integrate user administration
>> with the host Wiki and to change the appearance of the pages to look
>> more like the host Wiki.
>>
>> Regards,
>> Fintan
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ----------------------------
>> IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
>> Registernummer: HRB 7939
>> Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 
>>
>>
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Doc-book-users mailing list
>> Doc...@li...
>> https://lists.sourceforge.net/lists/listinfo/doc-book-users
> 

Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

[Pierce T. <pi...@xt...>]

Hi, Fintan:

That is a very interesting idea. It would give users the best of both 
worlds, really.

We recently finished evaluating wikis for implementation at our site. 
And the choice came down to MoinMoin vs. DocBook Wiki. It was an 
extremely tough choice. Both packages have strengths and weaknesses. But 
in the end we went with MoinMoin because the community is larger and 
more active and development is moving forward.

While MoinMoin does offer some DocBook support, that support is not 
nearly as extensive as DocBook Wiki's. Also, the backend SVN support 
offered by DocBook Wiki is something MoinMoin does not currently offer.

I suppose integrating a PHP-based application with MoinMoin, which is 
written in Python, could pose some challenges. But, again, I really like 
this idea if it were possible--or if people were interested in trying to 
make it happen.

Best regards,
Pierce


Bolton, Fintan wrote:
> Hello Dashamir,
> 
> I wonder if you have ever considered re-packaging DocBook Wiki as a
> plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?
> 
> It is a peculiar paradox that, although DocBook Wiki has much better
> DocBook support than any other Wiki out there, it has failed to gain
> much traction in the Wiki space. I suspect the reason for this is that
> there is currently a rather high threshold to getting a new Wiki flavour
> accepted. For example, on a typical open source project, you would have
> very little prospect of persuading an open source community to drop
> Moin-Moin or Confluence in favour of a little-known product like DocBook
> Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
> probably be an uphill battle.
> 
> In marketing terms, therefore, it would be much easier to get DocBook
> Wiki accepted if it came in the form of a Confluence or Moin-Moin
> plug-in. Adding plug-ins to Wikis is a routine procedure that would be
> unlikely to arouse much controversy in an open source community.
> 
> Of course, I am glossing over the technical difficulties here, which
> might be considerable. But the integration would not have to be perfect.
> The main goal would be to make DocBook Wiki look similar enough to the
> host Wiki, so that it can gain acceptance. On a technical level,
> probably the main priorities would be to integrate user administration
> with the host Wiki and to change the appearance of the pages to look
> more like the host Wiki.
> 
> Regards,
> Fintan
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ----------------------------
> IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
> Registernummer: HRB 7939
> Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users

-- 
Pierce Tyler
xTuple
119 West York Street
Norfolk, VA 23510
email: pi...@xt...
www.xtuple.com

Re: [doc-book-users] DocBook Wiki as Confluence plug-in?

[Dashamir H. <das...@gm...>]

Hi Fintan,

Thanks for the suggestion. However, I am not worried about
"dominating the market" or becoming famous. As long as it
works for me, and as long as the others who use it are satisfied,
I don't worry about fixing or improving it.

So, if you wish, you can try to make such a package, but I think
that it should be very difficult and the chances that you
succeed are very low. Even if I have tried it myself, the chances
that I would succeed would be low. However I don't have time to
try it, because I am already trying something else with it.

Regards,
Dashamir

Bolton, Fintan wrote:
> Hello Dashamir,
> 
> I wonder if you have ever considered re-packaging DocBook Wiki as a
> plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?
> 
> It is a peculiar paradox that, although DocBook Wiki has much better
> DocBook support than any other Wiki out there, it has failed to gain
> much traction in the Wiki space. I suspect the reason for this is that
> there is currently a rather high threshold to getting a new Wiki flavour
> accepted. For example, on a typical open source project, you would have
> very little prospect of persuading an open source community to drop
> Moin-Moin or Confluence in favour of a little-known product like DocBook
> Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
> probably be an uphill battle.
> 
> In marketing terms, therefore, it would be much easier to get DocBook
> Wiki accepted if it came in the form of a Confluence or Moin-Moin
> plug-in. Adding plug-ins to Wikis is a routine procedure that would be
> unlikely to arouse much controversy in an open source community.
> 
> Of course, I am glossing over the technical difficulties here, which
> might be considerable. But the integration would not have to be perfect.
> The main goal would be to make DocBook Wiki look similar enough to the
> host Wiki, so that it can gain acceptance. On a technical level,
> probably the main priorities would be to integrate user administration
> with the host Wiki and to change the appearance of the pages to look
> more like the host Wiki.
> 
> Regards,
> Fintan
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ----------------------------
> IONA Technologies GmbH (registriert in Deutschland, AG Darmstadt)
> Registernummer: HRB 7939
> Geschäftsadresse: Im Leuschnerpark 4, D- 64347 Griesheim, Deutschland 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Doc-book-users mailing list
> Doc...@li...
> https://lists.sourceforge.net/lists/listinfo/doc-book-users

[doc-book-users] DocBook Wiki as Confluence plug-in?

[Bolton, F. <fin...@io...>]

Hello Dashamir,

I wonder if you have ever considered re-packaging DocBook Wiki as a
plug-in to one of the mainstream Wikis, such as Confluence or Moin-Moin?

It is a peculiar paradox that, although DocBook Wiki has much better
DocBook support than any other Wiki out there, it has failed to gain
much traction in the Wiki space. I suspect the reason for this is that
there is currently a rather high threshold to getting a new Wiki flavour
accepted. For example, on a typical open source project, you would have
very little prospect of persuading an open source community to drop
Moin-Moin or Confluence in favour of a little-known product like DocBook
Wiki. Even persuading the community to adopt it as an 'extra' Wiki would
probably be an uphill battle.

In marketing terms, therefore, it would be much easier to get DocBook
Wiki accepted if it came in the form of a Confluence or Moin-Moin
plug-in. Adding plug-ins to Wikis is a routine procedure that would be
unlikely to arouse much controversy in an open source community.

Of course, I am glossing over the technical difficulties here, which
might be considerable. But the integration would not have to be perfect.
The main goal would be to make DocBook Wiki look similar enough to the
host Wiki, so that it can gain acceptance. On a technical level,
probably the main priorities would be to integrate user administration
with the host Wiki and to change the appearance of the pages to look
more like the host Wiki.

Regards,
Fintan

Re: [doc-book-users] Evaluating DocBook Wiki

[N. A. C. <nes...@gm...>]

Yes, I must say that I also think it's good but difficult stuff. I'm
trying to use it for my own project, but it's not easy to manage, even
to install... It's a pity, because it rock otherwise.

2008/3/4, Dashamir Hoxha <das...@gm...>:
> Hi Pierce,
>
>  The last release of docbookwiki, books-0.9.1 was made
>  almost one year ago, and as far as I know it is stable.
>  I am using it for myself to document my things, and I
>  haven't noticed anything that does not work. Of course,
>  there may be many things that can be improved or that
>  can be done better, but these do not prevent it from being
>  used. In case that there are any bugs, I am still willing
>  to try and fix them.
>
>  However, I have stopped developing DocBookWiki, in the sense
>  that I am not trying to add any new features to it. Instead,
>  I have started a new branch of it that I have called DocBookEasy.
>
>  The difference between them is how the chunks are handled.
>  In DocBookWiki I have written my own XSL stylesheets to do
>  chunk processing. In DocBookEasy I try to use customizations
>  of the standard XSL stylesheets (those that convert XML docbook
>  document into html, pdf etc.). This way I try to achieve support
>  for almost the full syntax of the DocBook, because this support
>  is already present in the XSL DocBook stylesheets.
>
>  DocBookEasy also has the benefit that it could be more easily
>  understood and customized by people, provided that they are familiar
>  with XSL DocBook stylesheets. DocBookWiki, on the other hand, is
>  like a bunch of tricks, which are somewhat difficult to understand,
>  modify and improve.
>
>  However, editing in DocBookEasy may not be as efficient as in
>  DocBookWiki. This is why I have decided to make them separate
>  branches, and not to consider DocBookEasy as an improvment of
>  DocBookWiki. There may be cases when DocBookEasy can be more
>  preferable, and other cases when DocBookWiki can be more preferable.
>
>  I am still working to prepare a first release of DocBookEasy,
>  an many things are still not clear. After I make the first release,
>  I think that things will be more clear, and I also hope that I will
>  get some help for improving it. On the contrary, I have had very
>  little help with DocBookWiki, and I think that it is because of the
>  tricky nature of it.
>
>  But I also intend to support DocBookWiki, in the sense that I will try
>  to fix any bugs that are not too difficult to be fixed. So, do give it
>  a try. Don't wait for DocBookEasy, because it may take long until it
>  becomes usable.
>
>  Regards,
>  Dashamir
>
>
>  Pierce Tyler wrote:
>  > Hi, Dashamir:
>  >
>  > We are seriously evaluating your DocBook Wiki project for our PostBooks
>  > project docs:
>  >
>  > http://sourceforge.net/projects/postbooks
>  >
>  > I just want to ask if your project is still alive and well. I know you
>  > have a SourceForge site and a small number of downloads each day. But I
>  > am curious to know if the developers are still active. Do you plan to
>  > continue supporting this project in the future? Are future versions
>  > planned? Or are you done releasing updates? (The copyright notice in
>  > your user guide says 2004-2005, so I wasn't sure.)
>  >
>  > Thanks for any information you can provide.
>  >
>  > Best wishes,
>  > Pierce
>  >
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>  _______________________________________________
>  Doc-book-users mailing list
>  Doc...@li...
>  https://lists.sourceforge.net/lists/listinfo/doc-book-users
>


-- 
Néstor Amigo Cairo
+34 687 96 74 81
nes...@gm...

Re: [doc-book-users] Evaluating DocBook Wiki

[Dashamir H. <das...@gm...>]

Hi Pierce,

The last release of docbookwiki, books-0.9.1 was made
almost one year ago, and as far as I know it is stable.
I am using it for myself to document my things, and I
haven't noticed anything that does not work. Of course,
there may be many things that can be improved or that
can be done better, but these do not prevent it from being
used. In case that there are any bugs, I am still willing
to try and fix them.

However, I have stopped developing DocBookWiki, in the sense
that I am not trying to add any new features to it. Instead,
I have started a new branch of it that I have called DocBookEasy.

The difference between them is how the chunks are handled.
In DocBookWiki I have written my own XSL stylesheets to do
chunk processing. In DocBookEasy I try to use customizations
of the standard XSL stylesheets (those that convert XML docbook
document into html, pdf etc.). This way I try to achieve support
for almost the full syntax of the DocBook, because this support
is already present in the XSL DocBook stylesheets.

DocBookEasy also has the benefit that it could be more easily
understood and customized by people, provided that they are familiar
with XSL DocBook stylesheets. DocBookWiki, on the other hand, is
like a bunch of tricks, which are somewhat difficult to understand,
modify and improve.

However, editing in DocBookEasy may not be as efficient as in
DocBookWiki. This is why I have decided to make them separate
branches, and not to consider DocBookEasy as an improvment of
DocBookWiki. There may be cases when DocBookEasy can be more
preferable, and other cases when DocBookWiki can be more preferable.

I am still working to prepare a first release of DocBookEasy,
an many things are still not clear. After I make the first release,
I think that things will be more clear, and I also hope that I will
get some help for improving it. On the contrary, I have had very
little help with DocBookWiki, and I think that it is because of the
tricky nature of it.

But I also intend to support DocBookWiki, in the sense that I will try
to fix any bugs that are not too difficult to be fixed. So, do give it
a try. Don't wait for DocBookEasy, because it may take long until it
becomes usable.

Regards,
Dashamir


Pierce Tyler wrote:
> Hi, Dashamir:
> 
> We are seriously evaluating your DocBook Wiki project for our PostBooks 
> project docs:
> 
> http://sourceforge.net/projects/postbooks
> 
> I just want to ask if your project is still alive and well. I know you 
> have a SourceForge site and a small number of downloads each day. But I 
> am curious to know if the developers are still active. Do you plan to 
> continue supporting this project in the future? Are future versions 
> planned? Or are you done releasing updates? (The copyright notice in 
> your user guide says 2004-2005, so I wasn't sure.)
> 
> Thanks for any information you can provide.
> 
> Best wishes,
> Pierce
> 

Re: [doc-book-users] Broken books drop-down list on admin.php page?

[Dashamir H. <das...@gm...>]

Fintan,

It is working for me.

Have a look at 'templates/admin/access_rights/users'. The books
are appended at the end of the user line. Then close the Firefox
and open it again to make sure that you are logging in as the user
that you are testing.

Make sure also that you have the release 'books-0.9.1' and that
you have made a `svn update` inside it.

Regards,
Dashamir

Bolton, Fintan wrote:
> In my installation of DocBooks Wiki, there appears to be a broken
> drop-down list on the admin.php page.
> 
> I created a user with privileges to administer more than one book. I
> then navigate to the books/admin.php page and log in as this user (I'm
> using a FireFox browser). In the top-right hand corner of the page, I
> click on the 'Books' button to start administering the books. I then get
> a page filled with options for administering the first book
> (docbook_wiki, in this case). However, it is not possible to switch to
> administering any of the other books. I noticed there is an *empty*
> drop-down menu just under the 'Books' button (and on the same horizontal
> level as the book title). I assume that this drop-down menu is meant to
> let you switch focus to the other books, but in my installation this
> menu has nothing in it.
> 
> All of the other drop-down menus and form elements are working fine on
> this page, by the way. It's only the drop-down menu for switching books
> that doesn't work. Is this a known bug?
> 
> Regards,
> Fintan Bolton

[doc-book-users] Broken books drop-down list on admin.php page?

[Bolton, F. <fin...@io...>]

In my installation of DocBooks Wiki, there appears to be a broken
drop-down list on the admin.php page.

I created a user with privileges to administer more than one book. I
then navigate to the books/admin.php page and log in as this user (I'm
using a FireFox browser). In the top-right hand corner of the page, I
click on the 'Books' button to start administering the books. I then get
a page filled with options for administering the first book
(docbook_wiki, in this case). However, it is not possible to switch to
administering any of the other books. I noticed there is an *empty*
drop-down menu just under the 'Books' button (and on the same horizontal
level as the book title). I assume that this drop-down menu is meant to
let you switch focus to the other books, but in my installation this
menu has nothing in it.

All of the other drop-down menus and form elements are working fine on
this page, by the way. It's only the drop-down menu for switching books
that doesn't work. Is this a known bug?

Regards,
Fintan Bolton