Hehe ;) No, I was merely suggesting that maybe someone tried too hard to
fix non-working urls becauase of other use cases.
Luckily it seems fixed now.
On 03/06/2014 10:17 AM, Andreas Leha wrote:
"R. Michael Weylandt" <michael.weyla...@gmail.com> writes:
On Tue, Mar 4, 2014 at 3:45 PM, Simon Thum <simon.t...@gmx.de> wrote:
This seems to be a question of objective. Do you want to encode, i.e.
maintain some reversible original in an url no matter what, or do you want
to fix url's which wouldn't otherwise be legal? In the latter case, the
question mark should probably be retained.
I am not sure, that I understand what you say here. But in case you
want to convince me, that exporting non-working links when the user
supplies working links is a feature and not a bug, you will have a hard
time ;-)
- Andreas
I believe the former. If the user types in a working link, the
exporter shouldn't break it.
This could be fixed by sprinkling org-url-decode through various
backends, but that suggests to me that the problem may be "upstream."
Michael
