From xemacs-m  Wed Nov 27 14:59:53 1996
Received: from noknic.nokia.com (noknic.nokia.com [131.228.6.10]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with SMTP id OAA15522 for <xemacs-beta@xemacs.org>; Wed, 27 Nov 1996 14:59:52 -0600 (CST)
Received: from zeus.tele.nokia.fi (zeus.tele.nokia.fi [131.228.134.50]) by noknic.nokia.com (8.6.9/8.6.9) with ESMTP id WAA07996; Wed, 27 Nov 1996 22:58:22 +0200
Received: from aapo.tele.nokia.fi (aapo.tele.nokia.fi [131.228.134.64]) by zeus.tele.nokia.fi (8.6.4/8.6.4) with ESMTP id XAA15396; Wed, 27 Nov 1996 23:03:20 +0200
From: Jari Aalto <jaalto@tre.tele.nokia.fi>
Received: from localhost (jaalto@localhost) by aapo.tele.nokia.fi (8.6.4/8.6.4) id PAA20495; Wed, 27 Nov 1996 15:49:18 -0500
Date: Wed, 27 Nov 1996 15:49:18 -0500
Message-Id: <199611272049.PAA20495@aapo.tele.nokia.fi>
To: tm-en@chamonix.jaist.ac.jp
CC: xemacs-beta@xemacs.org, mrb@Eng.Sun.COM
Subject: Re2: Building gnus-art-mime.elc
Reply-to: <jari.aalto@ntc.nokia.com> (pgp prefered ssjaaa@uta.fi | pgp -fka)
Mime-Version: 1.0 (generated by tm-edit 7.93)
Content-Type: text/plain; charset=ISO-8859-1
X-Pgp-Comment: Processed by TinyPgp.el 1.75
X-Pgp-Version: 2.6.3ia
X-Pgp-Charset: noconv
X-Pgp-Signed: 
	iQBVAwUBMpypR8C67dVHFB01AQETUQH/bLXjpkXGjNdy3uuldC1hk6hWfok5CAAl
	8x0m8dN9h3tgbo2gnpOrsnoOBUxvZ//PEkkvmoY1jWCpcIHByJD6Cg==
	=40N2
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by xemacs.cs.uiuc.edu id OAA15523

| 28.11.96, | From <morioka@jaist.ac.jp>
|
|   I think there is no need to bundle Japanese files for XEmacs 19.14.
| However for XEmacs 20.0 should have Japanese documents.  Maybe some
| XEmacs 20.0 users don't have Japanese or multilingual TeX, so I don't
| know which is better.
|
|   By the way, I'm rewriting new documents by SGML, and I defined sinfo
| DTD (DTD designed to convert Texinfo).  I think SGML may be better
| than Texinfo, because sgmls is not designed only for English.  Of
| course, there are problems to convert DVI.  But there are several
| implementations about localized or multilingual TeX, so to write
| several translator may solve it.  Of course it is important to write
| translator for HTML.
|

just a quick note to this SGML subject:
I think people should no more write any textinfo of TeX or LateX
files, whatever, because they are not portable. We don't have Tex or
dvi here and I have no way of printing the emacs docs currently.
(if the docs were in html, I could do .ps with my netbrowser!)

There is currently several programs that can convert SGML to any
of these formats including HTML from a single SGML source.

I hope that XEmacs documentation will be distributed in SGML in
the fututure (this is of course huge task to do, but start
now, and gradually work forward)

I don't have experience on SGML yet, but I recently run into it
and gave it a serious though because I was wondering if I have
to learn texinfo to write docs to my libs or f'coming TinyPgp.el

It seems that learning texinfo is not the way to go, but
doing the docs in SGML and using programs to convert those
documents into textinfo and html... ps whatever is needed. That
gives more portability and control over documents.

Tomohiko:
    I haven't yet studied how I integrate my PGP package to
    your TM, instead of using mailcrypt.el, because I have been busy
    in correction bugs and adding new features.

    I have saved your mails that you sent me where you pointed out
    which parts are controlled by mailcrypt now.

    I take a look at you posts closer as soon as I can.

/jari

Here is pointer to SGML software:

    http://www.sil.org/sgml/publicSW.html

Jrg Wittenberger's Typeset Package:
Wittenberger's typeset is a formatter for SGML documents. "Overview [March
..."Currently there are these DTD's: document (Simple ,,plain'' documents);
report (Technical reports, documentation etc.); bibdata (Bibliography
database); manpage (Pages for the Unix(TM) man command); brief (A letter
according to DIN). Currently the following output formats are supported:
PostScript (for english and german text); HTML (Hyper Text Markup Language);
Info (to be included into the on-line help of emacs); man suitable for roff
- -man; ASCII; limited support for RTF. Future output formats will include:
RTF, LaTeX."
<joerg.wittenberger@inf.tu-dresden.de>

"SDC is a well featured, free system aiming to make SGML suitable for day to
day use. SDC compiles SGML documents into representations as PostScript,
LaTeX, HTML, man pages, (emacs) info files and is a little RTF aware. The
goal of SDC is to be author friendly, easy to use without the need of
special editors and to hide as much of the backend as possible. Hence the
required markup is minimized, mixed content type allow you to type text
(almost) everywhere and get the desired meaning. There are no `special
characters' but those special to SGML (< and &)."

Links:

   * Announcement (July 02, 1996)
   * More Information [mirror copy, partial links only]
   * FTP: ftp.inf.tu-dresden.de/pub/people/jerry/sdc-1.0beta.tar.gz
   * Longer documentation [note Typeset origins]; [mirror copy (Date: June
     1996)]


DSSSL Software Tools

[CR: 19961118]

See the main DSSSL entry for fuller information about sample application
profiles, stylesheets, etc. In particular, see the DSSSL stylesheet for HTML
3.2 printouts, submitted by Jon Bosak.
   * Jade Home Page: http://www.jclark.com/jade/, Jade for "(James [Clark]'s
   * From David Megginson: announcement for a utility 'psgml-dsssl.el',
     which works with the free 'psgml' editor under Gnu Emacs. "This small
     package works together with the PSGML editor in XEmacs or Gnu Emacs to
     produce a skeleton DSSSL style spec automatically for the current
     document's DTD." See the mail link:
     http://www.uottawa.ca/~dmeggins/psgml-dsssl.el, or mirror copy, October
     20, 1996.

