From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: David Maus <dmaus@ictsoc.de>,
emacs-orgmode@gnu.org, Nick Dokos <ndokos@gmail.com>
Subject: Re: Encoding Problem in export?
Date: Mon, 29 Jul 2013 12:29:29 +0530 [thread overview]
Message-ID: <8738qxhmwe.fsf@gmail.com> (raw)
In-Reply-To: <87ehaj0vzu.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 28 Jul 2013 13:22:45 +0200")
Nicolas, David
I just interjected.
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> ...if that part cannot happen for some reason, links will be unusable
> outside Org.
Correctness should overrule compatibility. In practice, we may have to
strike a balance, with more weight thrown in favor of correctness.
I am stating the obvious here, but in a way that is practically useless
to the discussion at hand.
I trust that any solution that you come up with will be a good one.
Also the timing is right. We can always say Org-8.0 makes a clear
departure from earlier versions for reasons of robustness and
correctness.
----------------------------------------------------------------
Speaking from gut (aka making things up)
Link (un)escaping has also something to do with org-protocol and how the
URL in browser's address bar is "captured", "encoded"(?) and
"transferred" to the Emacs proper via the bookmarklet. So the browser
(don't forget the clipboard) acts as *active* intermediaries as the URL
makes it's way from the browser to the Org file either via hand or
through emacsclient. To complicate the issue, browser being user facing
may be expected to be very lenient with a URL or how it is "presented"
to the user.
ps-1: org-protocol to work on Windows is quite flaky.
ps-2: There are frequent posts to Emacs mailing lists where copying from
browser to a Emacs buffer will show up un-readable boxes.
----------------------------------------------------------------
Don't read further, if you are allergic to meta musings.
As far as Org is concerned, backward compatibility is not a issue. The
community is always being replaced *every* academic year. New scholars
come and the old scholars leave. The only steady lot of the population
is the college dons. They will not rely on Org *solely* for serious
publishing work. They do revise their course support material - like
beamer presentations etc - every term.
In summary, shelf-life of an Org source file that is actually exported
is unlikely to be beyond 4-5 years. The contents of such source file
has less of stable parts and more of moving parts.
next prev parent reply other threads:[~2013-07-29 6:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 23:17 Encoding Problem in export? Robert Eckl
2013-07-23 23:35 ` Nicolas Goaziou
2013-07-24 1:50 ` Robert Eckl
2013-07-24 7:34 ` Nicolas Goaziou
2013-07-24 8:46 ` Robert Eckl
2013-07-24 9:16 ` Nicolas Goaziou
2013-07-24 10:27 ` Robert Eckl
2013-07-24 9:39 ` Nick Dokos
2013-07-24 11:09 ` Nicolas Goaziou
2013-07-25 4:05 ` David Maus
2013-07-25 21:46 ` Nicolas Goaziou
2013-07-26 4:03 ` David Maus
2013-07-26 10:20 ` Nicolas Goaziou
2013-07-27 7:23 ` David Maus
2013-07-27 11:09 ` Nicolas Goaziou
2013-07-28 8:36 ` Jambunathan K
2013-07-28 8:54 ` Jambunathan K
2013-07-28 11:16 ` David Maus
2013-07-28 11:22 ` Nicolas Goaziou
2013-07-29 6:59 ` Jambunathan K [this message]
2013-11-16 15:16 ` Michael Brand
2013-11-16 20:43 ` Nicolas Goaziou
2013-11-17 11:06 ` Michael Brand
2013-11-17 11:46 ` Nicolas Goaziou
2013-11-17 11:51 ` Michael Brand
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=8738qxhmwe.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
--cc=ndokos@gmail.com \
/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).