From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: format of the ID property in the new HTML exporter Date: Tue, 12 Feb 2013 11:10:10 +0530 Message-ID: <87k3qegked.fsf@gmail.com> References: <878v6xjuqk.wl%n142857@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55519) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U58bh-0006dO-2Z for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 00:40:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U58bf-0005Yy-QK for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 00:40:40 -0500 Received: from mail-pa0-f52.google.com ([209.85.220.52]:60853) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U58bf-0005Yj-E8 for emacs-orgmode@gnu.org; Tue, 12 Feb 2013 00:40:39 -0500 Received: by mail-pa0-f52.google.com with SMTP id fb1so3519444pad.39 for ; Mon, 11 Feb 2013 21:40:38 -0800 (PST) In-Reply-To: <878v6xjuqk.wl%n142857@gmail.com> (Daniel Clemente's message of "Sat, 09 Feb 2013 17:51:47 +0100") 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: Daniel Clemente Cc: emacs-orgmode@gnu.org Daniel Clemente writes: > Hi, > in ox-html.el there's a line with an assert (the only one): > > (assert (org-uuidgen-p path)) > > > 1. I have some IDs like "o5y98600aze0" which don't conform to that uuidgen format; they were created by early versions of org. Should only UUIDs be accepted as ID? > 2. I think the ID should be editable by hand to what you like, as long as they are unique. If you don't need to export it you don't need a CUSTOM_ID, and having both ID and CUSTOM_ID is not the simplest way. > > So I think that assert is too strict. My short IDs seem as good as the long UUIDs. There is ID and then there is CUSTOM_ID. IIUC/IIRC, ID is a uuid and CUSTOM_ID can be whatever. Any reason why you cannot use CUSTOM_IDs here? --