9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] OpenDocument to troff converter
Date: Tue, 10 Oct 2006 16:36:56 +0200	[thread overview]
Message-ID: <82c890d00610100736p38891e5cpdadc82422b884f21@mail.gmail.com> (raw)
In-Reply-To: <452bad5a.rQQKB1/Cnt773x7B%gunnarr@acm.org>

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

Hello

I hope it is interesting for someone.

slds.

gabi

---------- Forwarded message ----------
From: Gunnar Ritter <gunnarr@acm.org>
Date: Oct 10, 2006 4:25 PM
Subject: [Groff] OpenDocument to troff converter
To: groff@gnu.org

Hi,

I announce the availability of an import filter to convert
OpenDocument files to troff input. I have released it as
part of my Heirloom Documentation Tools package, but since
it is not actually specific to a troff variant, it may be
useful with groff as well.

As most of you probably know, OpenDocument is the native
file format of OpenOffice 2. Since OpenOffice itself can
import many other word processor formats, e.g. Word or RTF,
it is thus also possible to derive troff documents from
such files.

The filter is aimed at a process where authors hand in
word processor files for producing a typeset document.
It has thus been written with the intent of creating
troff code that can be comfortably edited further;
on the other hand, it discards specific measurement
data such as point sizes or page offsets since it is
expected that the typesetter will introduce his own
consistent scheme for them.

Usage instructions can be found at the beginning of the
converter script.

        Gunnar


_______________________________________________
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff

[-- Attachment #2: Type: text/html, Size: 1791 bytes --]

           reply	other threads:[~2006-10-10 14:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <452bad5a.rQQKB1/Cnt773x7B%gunnarr@acm.org>]

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=82c890d00610100736p38891e5cpdadc82422b884f21@mail.gmail.com \
    --to=gabidiaz@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).