From: Xiao-Yong Jin <xj2106@columbia.edu>
To: emacs-orgmode@gnu.org
Subject: Re: XHTML export - etc.
Date: Fri, 09 Nov 2007 18:40:33 -0500 [thread overview]
Message-ID: <871wazoumm.fsf@columbia.edu> (raw)
In-Reply-To: <b71b18520711091437h668c52caw9fb6f84bdcb1cdf8@mail.gmail.com> (Eddward DeVilla's message of "Fri\, 9 Nov 2007 16\:37\:58 -0600")
"Eddward DeVilla" <eddward@gmail.com> writes:
> I feel tempted to bring up my suggestion of [markup|text] format
> again, but I've been resisting because I feel like a develish nag. So
> [*|at-syntax] could still be html specific if you really want
> something html specific, but there would be something that could be
> portable to all export formats. It would just be a matter of deciding
> what 'org' marks should be supported and making sure exporters try to
> support them. And of course there are other ways to get around *at
> syntax*.
I would vote against heavily mark-up format like that. I
guess the original design of org-mode is to make a simple
text file that can make personal information organization
much simpler in emacs, as opposed to those half-mark-up
languages like emacs-muse.
I would suggest to keep current method, which is converting
everything that could be converted. To resolve the
complication in some circumstances where conversion of `[1]'
or `_', `^' and etc. is not wanted, I would propose that we
can just use one of the mark-ups, `=code=', and make it be
actually `=verbatim='.
These are just what I think. Probably there is another way
to go: merge with emacs-muse!
Xiao-Yong
--
c/* __o/*
<\ * (__
*/\ <
next prev parent reply other threads:[~2007-11-09 23:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 12:13 XHTML export - customizing via local variables Adam Spiers
2007-11-02 12:20 ` XHTML export - etc Adam Spiers
2007-11-02 15:26 ` Bastien
2007-11-02 15:19 ` Adam Spiers
2007-11-02 15:33 ` Daniel Clemente
2007-11-02 15:34 ` Daniel Clemente
2007-11-02 19:21 ` Bastien
2007-11-02 18:50 ` William Henney
2007-11-02 20:20 ` Daniel Clemente
2007-11-03 0:06 ` Bastien
2007-11-04 0:00 ` Daniel Clemente
2007-11-04 12:45 ` Bastien
2007-11-07 16:09 ` Daniel Clemente
2007-11-07 17:39 ` Bastien
2007-11-07 18:04 ` Daniel Clemente
2007-11-08 0:48 ` Bastien
2007-11-09 19:51 ` Daniel Clemente
2007-11-09 19:59 ` Daniel Clemente
2007-11-09 22:37 ` Eddward DeVilla
2007-11-09 23:40 ` Xiao-Yong Jin [this message]
2007-11-12 5:07 ` Bastien
2007-11-12 5:22 ` Bastien
2007-11-03 6:10 ` William Henney
2007-11-03 13:51 ` Bastien
2007-11-03 14:23 ` William Henney
2007-11-03 15:51 ` Bastien
2007-11-03 16:46 ` William Henney
2007-11-03 0:04 ` Bastien
2007-11-02 18:46 ` Bastien
2007-11-02 15:45 ` XHTML export - customizing via local variables Bastien
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=871wazoumm.fsf@columbia.edu \
--to=xj2106@columbia.edu \
--cc=emacs-orgmode@gnu.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).