From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: Bug: HTML export ignoring CUSTOM_ID properties Date: Sat, 18 Apr 2015 23:38:28 +0100 Message-ID: <87zj65jczm.fsf@gmail.com> References: <877ft9cmyk.fsf@jack.tftorrey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjbNm-00072f-0n for emacs-orgmode@gnu.org; Sat, 18 Apr 2015 18:38:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YjbNh-0006wB-0u for emacs-orgmode@gnu.org; Sat, 18 Apr 2015 18:38:37 -0400 Received: from mail-wi0-x229.google.com ([2a00:1450:400c:c05::229]:38143) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YjbNg-0006w0-OT for emacs-orgmode@gnu.org; Sat, 18 Apr 2015 18:38:32 -0400 Received: by wiun10 with SMTP id n10so54569469wiu.1 for ; Sat, 18 Apr 2015 15:38:31 -0700 (PDT) In-Reply-To: <877ft9cmyk.fsf@jack.tftorrey.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "T.F. Torrey" , Rasmus Cc: emacs-orgmode@gnu.org Hi Terry, I don=E2=80=99t think it=E2=80=99s necessary to be combative. Rasmus is do= ing his best, as are all the org developers. Sometimes things break by accident =E2=80=93 that is the nature of beta software. The problems you raised are important. Let=E2=80=99s try to figure out how to fix them. You wrote: > Links may work from inside Org, but the original intent of CUSTOM_ID was > to produce a stable ID for the HTML export that could be linked to from > outside Org. I think this is true. Looking at the pages in Worg, for example, provides ample evidence of this strategy in action. CUSTOM_ID is also sometimes needed for latex export (cf. org-latex-prefer-user-labels). It is important for IDs to be unique, and to conform to certain format restrictions. What if CUSTOM_ID properties were checked for these requirements when exporting, raising an error if they are not suitable and otherwise passing through to the export output? This would maintain CUSTOM_ID as an interface to labeling systems outside org (latex \ref{}, html #anchor links, ...), but would also make export more robust. It=E2=80=99s also in line with rec= ent changes to raise export errors for undefined macros, unresolvable links, etc. -- Aaron Ecay