From: Carsten Dominik <carsten.dominik@gmail.com>
To: Wes Hardaker <wjhns209@hardakers.net>
Cc: Org Mode <emacs-orgmode@gnu.org>, rpgoldman@sift.info
Subject: Re: Re: OrgmodeOrg-export-generic and wikis...
Date: Thu, 29 Apr 2010 16:14:27 +0200 [thread overview]
Message-ID: <C0147A87-4BE8-4C3D-9000-1430C14B0DFF@gmail.com> (raw)
In-Reply-To: <sd4oiuwecz.fsf@wjh.hardakers.net>
On Apr 29, 2010, at 3:57 PM, Wes Hardaker wrote:
>>>>>> On Wed, 28 Apr 2010 14:38:47 -0500, Robert Goldman <rpgoldman@sift.info
>>>>>> > said:
>
> RG> 1. Would it be reasonable to move the documentation for
> RG> org-export-generic into the contrib/ directory of org-mode? It
> RG> seems ... suboptimal to have this package be maintained in the org
> RG> git repo, but its documentation in the worg git repo. At least
> from
> RG> my PoV this raises the bar for keeping the documentation up-to-
> date
> RG> and synchronized to a pretty high level.
>
> I'll let Carsten answer questions like that ;-)
The reason for this is the following.
Many of the contributed packages where written by people who were active
in Org-mode for a while and then less so. Many of these package had no
documentation at all. So I started a page on WOrg where this
documentation can be added and edited by other users, with quite
some success - now most package do have documentation.
Keeping documentation for a contributed package the the org-repo would
be OK, but there would be no mechanism to automatically put the latest
version up on on the web.
Changing this would require a volunteer who commits to keep the
documentation
of contributed packages in a consistent and web-publishable way in the
contrib directory.
- Carsten
>
> RG> 2. Is the existing "handle each line separately" algorithm going
> to
> RG> permit us to handle faces correctly? Seems like we'll need a
> lot of
> RG> hair to handle, e.g., a phrase in italics that straddles a line-
> break,
> RG> won't we?
>
> Well, that's a good question and one I don't have a great answer for.
> We could switch the parser to be multi-line based regexp matches but I
> suspect the complexity of when to stop those regexps will get rather
> harry too!
> --
> Wes Hardaker
> My Pictures: http://capturedonearth.com/
> My Thoughts: http://pontifications.hardakers.net/
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-04-29 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 19:38 Org-export-generic and wikis Robert Goldman
2010-04-29 13:57 ` OrgmodeOrg-export-generic " Wes Hardaker
2010-04-29 14:14 ` Carsten Dominik [this message]
2010-04-29 15:18 ` Robert Goldman
2010-05-14 7:16 ` Carsten Dominik
2010-05-21 13:02 ` Robert Goldman
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=C0147A87-4BE8-4C3D-9000-1430C14B0DFF@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
--cc=wjhns209@hardakers.net \
/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).