Hi Jeremy,

* No easy way to make a book other than
docbookwiki_guide the default

-> Fixed, set DEFAULT_BOOK at books.conf.

* Editing the menu using the Web interface still
doesn't seem to work

-> It works for me (I tested it with the latest svn
revision though).
   Make sure that you click "Apply Changes". Then,
make sure as well
   that you refresh the page where the menu is
displayed, otherwise
   the browser will use the cached menu, although the
menu on the
   server has been changed.

* No easy way to disable the menus if you only want to
use one document

-> I could provide an easy way for this, e.g. by
adding an additional
   variable at books.conf, however I think that
DocBookWiki is intended
   for many books, so whoever wants to use it for just
one book, he
   has to customize it manually. Anyway, I am going to
think about this.

* All the links are Javascript, it doesn't get indexed
by search engines

-> This is a feature request which most likely will
never be satisfied.
   DocBookWiki is based on the phpWebApp framework,
and this is how the
   framework works. To satisfy this request, either
the framework has to
   be modified or it has to be replaced by another
framework.

   However, DocBookWiki itself does index the content
and it can be searched.
   So, I think that the search engines could be
modified to get the
   index generated by DocBookWiki and to
integrate/merge it with their
   indexes. This would be even more efficient for them
because they
   don't have to crawl and index my content, instead
they get it ready.
   This would be something like distributed indexing
and searching.
   

* Graphics still don't work for me; here is my
original code:

-> Jeremy, I think that you import your document which
you have created by
   other tools. However you should know that
DocBookWiki does not support
   all the features of DocBook. It only supports a
very small subset of
   DocBook, and some of them should even follow
certain conventions (further
   restrictions). In general, DocBookWiki will never
be able to support all
   of the features of DocBook, and not even too many
of them; it will always
   be able to support a very small subset of DocBook.
One of the reasons is
   that wiki markup has restrictions in expressing too
many things and is
   difficult to be parsed.

   Comming back to your image problem, I think that
the @fileref of <imagedata>
   does not follow the DocBookWiki conventions. The
convention is:
  
fileref="media/chap_id/sect_id/sect_id/filename.png"
   The media files (images etc.) are imported in a tar
file, where they are
   stored in directories and subdirectories according
to the sections and
   subsections. I think that this is also explained
somehow in the guide. 

* No easy way for front matter not to appear on the
front page in full

-> Do you mean the "Preface"? You should organize it
as a chapter (or section)
   with id "preface" or something meaningfull. I do
the same thing for the
   appendix as well. Maybe it is possible to extend
DocBookWiki to handle
   other DocBook tags like <preface>, <appendix> etc.
but is it really neccessary?
   Anyway it cannot continue endless, the line has to
be drawn somewhere:
   some of the DocBookWiki features will be supported,
most of them will be not.

Dashamir

--- Jeremy Malcolm <[EMAIL PROTECTED]> wrote:

> I have played around with 0.9 a bit now (after
> installing from the 
> Debian package that I made), and I haven't found any
> new issues that 
> weren't in the old version that I was using (which
> was the last CVS 
> version).  Some of these are more like feature
> requests, anyway:
> 
> * No easy way to make a book other than
> docbookwiki_guide the default
> * Editing the menu using the Web interface still
> doesn't seem to work
> * No easy way for front matter not to appear on the
> front page in full
> * No easy way to disable the menus if you only want
> to use one document
> * All the links are Javascript, it doesn't get
> indexed by search engines
> * Graphics still don't work for me; here is my
> original code:
> 
> --- begins ---
> 
> <!ENTITY graph1001 "govmap">
> ...snip...
>     <mediaobject>
>        <imageobject>
>           <imagedata
> fileref="./images/&graph1001;.png" format="PNG" />
>        </imageobject>
>        <imageobject>
>           <imagedata fileref="&graph1001;.pdf"
> format="PDF" scale="75" />
>        </imageobject>
>        <imageobject>
>           <imagedata fileref="&graph1001;.eps"
> format="EPS" scale="75" />
>        </imageobject>
>        <imageobject>
>           <imagedata fileref="&graph1001;.bmp"
> format="BMP" />
>        </imageobject>
>        <textobject>
>           <phrase>Internet governance
> organisations</phrase>
>        </textobject>
>     </mediaobject>
> 
> --- ends ---
> 
>    And here is how it ends up:
> 
> --- begins ---
> 
>           <div align="center">
>              <table class="imageobject">
>                <tr>
>                  <td class="imagedata">
>                    <img 
>
src="content/books/xml/thesis/en/./chapter-02/section-012/sec-CURRENT-ARRANGEMENTS/"
> 
> width="" alt="Internet governance organisations" />
>                  </td>
>                </tr>
>              </table>
>            </div>
> 
> --- ends ---
> 
>    Would it be better if I was using simple XML
> code, eg. <graphic>,
>    and/or if I used the actual filename instead of
> the entity reference?
> 
> I have worked around most the issues above for my
> personal installation, 
> but I figure that it might be better if there was an
> easy way to do so.
> 
> PS. Dashamir, don't make those RefDB changes after
> all, but please just
>      tell me where you *would* make them if you were
> going to, because I
>      would like to experiment with them myself and
> then contribute them
>      upstream once I have them working.
> 
> -- 
> Jeremy Malcolm LLB (Hons) B Com
> Internet and Open Source lawyer, IT consultant,
> actor
> host -t NAPTR 1.0.8.0.3.1.2.9.8.1.6.e164.org|awk -F!
> '{print $3}'
> 
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2
> express and take
> control of your XML. No limits. Just data. Click to
> get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Doc-book-users mailing list
> [email protected]
>
https://lists.sourceforge.net/lists/listinfo/doc-book-users
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Doc-book-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doc-book-users

Reply via email to