emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jorge P. de Morais Neto <jorge+list@disroot.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: CUSTOM_ID vs ID
Date: Sun, 18 Aug 2019 11:24:15 -0300	[thread overview]
Message-ID: <87d0h28sc0.fsf@disroot.org> (raw)
In-Reply-To: <87sgpy3gf6.fsf@nicolasgoaziou.fr>

Hello,

Em 2019-08-18T12:40:29+0200, Nicolas Goaziou escreveu:

> That's because the text could contain anything, including invalid HTML
> characters. So we normalize them using only alphanum characters.

But could not we URL-encode the dedicated target text?  In my testing,
Org generates an ugly anchor even if the dedicated target text is just
"Target".

The current behavior does not harm my current use cases, but I looks to
me it would be simple to improve (for someone familiar with the
codebase) and help some users.  Then again, talk is cheap, so please
just take this as just a suggestion.

Regards
-- 
- I am Brazilian.  I hope my English is correct and I welcome feedback
- Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z
- Free/libre software for Android: https://f-droid.org/
- [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]]

  reply	other threads:[~2019-08-18 14:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 23:35 CUSTOM_ID vs ID Nathan Neff
2019-07-28  8:10 ` Nicolas Goaziou
2019-07-29  4:23   ` David Masterson
2019-07-29  6:38     ` Nicolas Goaziou
2019-08-02  4:54       ` David Masterson
2019-07-30  0:38   ` Nathan Neff
2019-08-01  7:55     ` Richard Lawrence
2019-08-09 11:13     ` Adam Porter
2019-08-02 14:53   ` Nathan Neff
2019-08-09 11:12     ` Adam Porter
2019-08-18  0:53   ` Jorge P. de Morais Neto
2019-08-18 10:40     ` Nicolas Goaziou
2019-08-18 14:24       ` Jorge P. de Morais Neto [this message]
2019-08-18 15:05         ` Nicolas Goaziou

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=87d0h28sc0.fsf@disroot.org \
    --to=jorge+list@disroot.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).