なかのにっき

• tarball は
  (http://www.linuxdoc.org/docs.html#howto)
  から辿れる (Ferguson)
  
• RPM distro には癖があるから、各 distributor に任せよう、 ということになっていた (Murphy)
  
  ドキュメントに関するかぎり、各 distro の違いはそれほどない (Prasanth Kumar)
  
  rpm のビルドスクリプトは書いてみようか (Aznar)
  
  deb は既にある (佐野)
  
  FHS や FSSTND に準拠するかたち？(David Merrill, et al.)
  
  
• 直接 CVS からとってもらうのもいいのでは。 例えば HOWTO-HOWTO なら
  (http://cvsweb.linuxdoc.org/index.cgi/LDP/howto/docbook/HOWTO-HOWTO/)
  から取れることになっている。 (Ferguson)
  
  
• ポチポチっと選んで一括ダウンロードできる webform みたいのはどうだろうか (Merrill)
  
  XML などの文書をスキーマレベルで DBMS に保管し、 適当なキーワードで文書を pickup、というような project もいろいろ聞いている(Murphy)

Basically, for a unified documentation browser/search
engine, we need a standard.

My idea would be putting the following hierarchy in a
dir, for ex /opt/doc :

lang/jp/html
lang/jp/pdf
lang/de (etc)
html/
pdf/
pdb/
txt/
info/
man/
(...)

We could just provide link for dirs (for ex,
/usr/man/man1 to man/man1) or for files (for ex
/usr/doc/XXXX in txt/XXXX) or put plain files in that
dir, as you suggested.

• これからは FHS だろう。 LDP 文書は /usr/share/doc 以下に置くべきだと思う (Gjoen)
  
  でもその下にもたくさん階層ができるから、短い /opt/ldp のほうがいいなあ (Aznar)
  
  
• SGI では

  /usr/doc/sgi/<prod>-<vrs>/<book_shorttitle>-<rev>/{html,ps,pdf,...}
  

  みたいにしてる (Ferguson)

    m> *Went to highschool area-wide poetry competition- one of two
    m> chosen from my school (yes, I'm an artsy-turned-geek. not that
    m> it really counts as 'experience' but it does show that I know
    m> what to do with words:)

Don't _turn_ geek, just add it.  Poetry is not just 'experience' you've
gained, but an essential skill, and no need to dump it or apologize for
it. Both Bucky Fuller and Marshall McLuhan said the future belongs to
the artist-scientist ... and I bet you may be surprised to find out
just how many of us fit this description.

We each have a soul
And the heart of a poet
That must be set free

It's chic to be geek
And write for the LDP
Haiku doesn't count.

• DSSSL for XML: Why not?
• Open-source XML projects/tools
• an open source (java) transformation engine that creates PDF from XML doc

Everyone seems to agree to use DocBook, very well. However, in the
opinion of the author himself, the jadetex processing tool is not suited
for professional books.

I am personally not really happy with jadetex and some others too I
know.
Do the other people here use it?
Are you happy with it?
Do you use something else?
Did you think in developing something else?

The LDP currently uses its own set of tools, the linuxdoctools
(the former sgmltools1) since docbook is not considered ready to use.

It's easier to add what we want in working tools (sgml2pdf, sgml2rpm for
ex) than waiting on docbook to be usable by each of our authors.

However, we have a team working on the docbook integration within the
LDP (docbooktools), and we provide docbook output from the current
linuxdoctools documents.

In the future, when docbook will be considered ready for production use
we will support both linuxdoctools and docbooktools, after which all our
documents will be in docbook.

Docbook documents are already accepted, but they are separated from the
linuxdoc HOWTOs.

states:

1) currently, DocBook -> professional print is not convenient
2) the base of a possible new tool should be XML and no more SGML
3) the new tool must handle many languages specificities correctly
4) none of the current free' processing tools meet the above points or
even took incompatible directions.
4) LaTeX gives professional prints for *many* languages and uses free'
tools

proposal:

1) Define the mean to pass from DocBook to LaTeX:
        - perl/Python
        - DSSSL
        - XSL
        - ...
2) Solve the stylesheets problem (depends on point 1)
        - use current .dsl ones
        - use LaTeX .sty ones
        - develop a [dsl2xsl, dsl2sty] script?

I have started a Bastille Linux HOWTO and would like some help with it. Is there anyone who would like to take some time over the next 2 weeks to help work with me on this HOWTO?

I've just finished a draft of the GIS-GRASS-HOWTO DocBook markup, and would appreciate it if someone would take a look at it, hopefully who knows DocBook better than I do. I did my best using DocBook: TDG, and think it's mostly okay. :)

OK, since it seems no one else had been doing this sort of thing, I've constructed an entire DocBook project template.

I think whatever happens, we still must maintain a degree of flexibility in what we accept: linuxdoc, docbook 3.x, docbook 4.x, docbook XML, etc.

something like a mini-mailing-list-HOWTO??

• Updated mini-HOWTO
• Linux Mailing Lists
• The Directory of Publicly Accessible Mailing Lists (paml)