From: Luis Anaya <papoanaya@hotmail.com>
To: Avdi Grimm <groups@inbox.avdi.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org mode export to Groff MM. Feature Freeze
Date: Mon, 16 Jul 2012 22:50:32 -0400 [thread overview]
Message-ID: <BLU0-SMTP100CABE8EC818ADF2258CC0B7DB0@phx.gbl> (raw)
In-Reply-To: <CA+XG7-jthSpF+ZN_-kcMLXGB4M3Vt+DF=9bhMd0-VBdQPcLh_g@mail.gmail.com> (Avdi Grimm's message of "Mon\, 16 Jul 2012 21\:56\:28 -0400")
Avdi Grimm <groups@inbox.avdi.org> writes:
> Does this mean that creating manpages from org source is now a
> possibility?
Hmm...
Not right now... berause of the different macro package that man pages uses
for rendering compared to the one used in Org which is based on the MM
package.
However, one thing that got me thinking was to implement exporters for
other macro packages, like MOM and MS being that they
follow similar structure. The reason why I think this is useful is
because each macro language is geared for a slightly different purpose.
IMHO:
- MM is for business communications
- MOM for literary writings
- MS for general typesetting. (Word grinder uses it for rendering )
- MAN well, for man pages :)
The MAN macro package uses different commands for typesetting
even though is processed through GROFF. But many of the structure are
shared among all macros package and there is always the option to use
straight GROFF commands. Even though is an idea on how to use Org mode,
I have never thought of using it for writing MAN pages. I'm
not sure how many people would; but the idea does
not have merit and certainly deserves some thought.
But... before going all crazy, probably I want to make sure that the one
I wrote for MM works well before venturing into coding for other macro
packages. It would make porting to those packages a lot easier.
Something else to consider, if you're inclined to.
It might be easier to implement a typesetter for MAN pages in muse mode
because it has a simpler rendering framework. It may also be a more
appropriate platform considering that MAN pages do not have a lot of
formatting requirements, when they are compared to a document
with multiple levels, lists, equations and graphics which is what you
find in papers, letters or memorandum.
Luis
--
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
next prev parent reply other threads:[~2012-07-17 2:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.99.1342454425.6558.emacs-orgmode@gnu.org>
2012-07-16 16:38 ` Org mode export to Groff MM. Feature Freeze Luis Anaya
2012-07-16 17:06 ` Bastien
2012-07-16 17:20 ` Nicolas Goaziou
2012-07-16 18:35 ` Luis Anaya
2012-07-16 20:36 ` Nicolas Goaziou
2012-07-16 21:22 ` Luis Anaya
2012-07-17 1:35 ` Luis Anaya
2012-07-17 7:50 ` Nicolas Goaziou
2012-07-17 8:53 ` Luis Anaya
[not found] ` <BLU0-SMTP243814C6971CC983CEECAFBB7D40@phx.gbl>
2012-07-16 17:42 ` FW: " Luis Anaya
2012-07-16 20:18 ` Bastien
2012-07-17 1:56 ` Avdi Grimm
2012-07-17 2:50 ` Luis Anaya [this message]
2012-07-17 10:20 ` Nicolas Goaziou
2012-07-17 14:06 ` Luis Anaya
2012-07-17 18:08 ` Luis Anaya
2012-07-18 0:04 ` Luis Anaya
2012-07-18 1:23 ` Suvayu Ali
2012-07-19 15:33 ` Nicolas Goaziou
2012-07-19 19:09 ` Luis Anaya
2012-07-20 0:07 ` Luis Anaya
2012-07-20 1:46 ` Luis Anaya
2012-07-17 2:53 ` Luis Anaya
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU0-SMTP100CABE8EC818ADF2258CC0B7DB0@phx.gbl \
--to=papoanaya@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=groups@inbox.avdi.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).