public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Docbook tools
Date: Mon, 06 Sep 1999 13:43:00 -0000	[thread overview]
Message-ID: <99090621500603.00542@r12m10.cybercable.tm.fr> (raw)
In-Reply-To: <y9xpuzwm5gx.fsf@lacrosse.corp.redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2232 bytes --]

David,

Thanks for your kind answer.

Le Mon, 06 Sep 1999, David C. Mason a écrit :
> Eric Bischoff <ebisch@cybercable.tm.fr> writes:
> > What is the reason
> > for putting both the 3.0 version and the 3.1 version of the DocBook
> > DTD in the RPM archive? It makes the file bigger.
> 
> It is unfair to compare a system like RPM to tar.gz or other
> archiving/compression formats. RPMs *add* functionality, thus
> sometimes larger files. Mark is working on other packages.

Maybe you misunderstood me. I was wondering why putting both the 3.0 and the 3.1
versions in the same RPM. Why not only the 3.1 version ? I was in no way
comparing RPMs to tarballs. I should have said "RPM packages" and not "RPM
archives".

> This is actually a problem with TeX itself. The French style file
> (french.sty) now has some major licensing issues thanks to its creator
> changing the license. The file was removed from the CTAN repository
> and it breaks things like jadetex that still try to call it. This
> should be fixed in Mark's latest version but you might find older
> versions still rely on the style file. 

Thanks for the info.

> As to the CKVJ languages, there is now support for Japanese in DocBook
> but you will need to write language files for other languages. These
> files are part of the Stylesheets and are really quite easy to write
> as long as you have someone who knows the language.

We have such people at KDE. Errr... what does CKVJ stand for ?

> Good Luck, its great to see you guys moving to DocBook, this is a
> great step for your project and mine(GNOME) to start sharing things
> like a help browser backend.

I fully support the policy of making KDE and GNOME as much compatible as we
can, I am very happy to meet you on this mailing list, and I hope we will have
the occasion to help one another many times again. The BIG conversion from
linuxdoc to docbook at KDE is to take place in very short time now.

Greetings,

Eric
--
 __________________________________________________
     .~.    "Release of Windows 2000 has been
     /V\      postponed until January 1, 1901"
   //   \\
  /(     )\ 
    ^^-^^
 __________________________________________________
Eric Bischoff - mailto:ebisch@cybercable.tm.fr

  reply	other threads:[~1999-09-06 13:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-06  8:21 David C. Mason
1999-09-06 13:43 ` Eric Bischoff [this message]
1999-09-07  7:27   ` David C. Mason
1999-09-10  1:06     ` Eric Bischoff
1999-09-10  7:38       ` David C. Mason
1999-09-10  7:52         ` Edward C. Bailey
  -- strict thread matches above, loose matches on Subject: below --
2000-12-27  6:36 DocBook tools Clarissa Kao
2000-12-27  6:36 ` Mark Galassi
1999-09-06  5:31 Docbook tools Stephane Bortzmeyer
1999-09-06  8:55 ` Mark Galassi
1999-09-05 14:13 Eric Bischoff
1999-09-06  1:27 ` Guy Brand
1999-09-06 21:01 ` Mark Galassi
1999-09-06 21:07   ` Rahul Dave
1999-09-06 21:09     ` Mark Galassi
1999-09-10  0:39     ` Eric Bischoff
1999-09-10  0:30   ` Eric Bischoff
1999-09-06 22:43 ` Jason Molenda
1999-09-07  0:02   ` Derek Simkowiak
1999-09-07  0:16     ` Mark Galassi
1999-09-07  0:44       ` Jochem Huhmann
1999-09-07  1:59       ` Derek Simkowiak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99090621500603.00542@r12m10.cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).