From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Meyer Subject: Using org-export-get-reference for strings Date: Thu, 30 Mar 2017 19:33:10 +0200 Message-ID: <87inmq6561.fsf@ofosos.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ctdwj-0002WH-V1 for emacs-orgmode@gnu.org; Thu, 30 Mar 2017 13:33:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ctdwg-0003Qy-Ng for emacs-orgmode@gnu.org; Thu, 30 Mar 2017 13:33:17 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:57461) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ctdwg-0003Px-FB for emacs-orgmode@gnu.org; Thu, 30 Mar 2017 13:33:14 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A78F720971 for ; Thu, 30 Mar 2017 13:33:12 -0400 (EDT) Received: from pericles (xd527869e.dyn.telefonica.de [213.39.134.158]) by mail.messagingengine.com (Postfix) with ESMTPA id 31880240CC for ; Thu, 30 Mar 2017 13:33:12 -0400 (EDT) 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" To: emacs-orgmode Hi list, In ox-epub I'm using several references to external stylesheets, starting with the external name in the user filesystem I transform these into a kind-of unique id that lives in the EPUB zip file. Currently I'm doing this using a counter, generating zip entries in the form of style-1.css. Can I use `org-export-get-reference' to generate these ids? I would likely pass a simple string as the object to get a reference to (the path the external stylesheet lives at). >From what I understand this would generate different references for `foobar.css' and `../foobar.css' even when these are identical documents. This should be fixed by passing `(expand-file-name style)' to `org-export-get-reference'. I'm not quite sure I understand `org-export-get-reference' correctly, can you elucidate this? Cheers, Mark -- Mark Meyer mark@ofosos.org