From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: COMMENTed Radio Targets: Any comments? Date: Sat, 06 Nov 2010 10:24:43 -0400 Message-ID: <871v6yr0lw.fsf@fastmail.fm> References: <814oc36acp.fsf@gmail.com> <87y697h563.fsf@fastmail.fm> <81wrorndkd.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=46116 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PEjhM-0006aR-0b for emacs-orgmode@gnu.org; Sat, 06 Nov 2010 10:24:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PEjhF-0008Bj-U8 for emacs-orgmode@gnu.org; Sat, 06 Nov 2010 10:24:46 -0400 Received: from out3.smtp.messagingengine.com ([66.111.4.27]:56199) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PEjhF-0008BZ-RD for emacs-orgmode@gnu.org; Sat, 06 Nov 2010 10:24:45 -0400 In-Reply-To: <81wrorndkd.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 06 Nov 2010 12:28:26 +0530") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K Cc: emacs-orgmode@gnu.org Hi Jambunathan, Jambunathan K writes: >> For stable links to particular headlines, I would recommend CUSTOM_IDs >> over radio targets. E.g., > > I am raising these questions or bugs or even aberrations as a result of > my work on OpenOffice. > > IOW, I am not looking at 'using them as a feature' but to 'understand > them as a feature' and 'cross-checking' my OpenOffice's exporter against > the HTML exporter. > > So the question of swithching to custom-ids doesn't arise in my case. > Thanks for clarifying. I misunderstood the context of the request. I think it would by helpful to mention such context (i.e., work on the OpenOffice exporter) in the original post. FWIW, the following commenting syntax correctly inserts an invisible target in the html: --8<---------------cut here---------------start------------->8--- * Heading # <<>> ** Subheading atarget --8<---------------cut here---------------end--------------->8--- exports as... --8<---------------cut here---------------start------------->8---

1 Heading

1.1 Subheading

atarget

--8<---------------cut here---------------end--------------->8--- Using the COMMENT keyword, by contrast, creates an orphaned link, as you note. > I see two options (that I think are consistent): > 1. In the Org file, references to 'Radioed Target' is still linkified > and clicking on it takes me to the right heading (although it is > COMMENTed out) > The corresponding thing for the HTML exporter is to 'ignore' the > COMMENT tag on the headline and (still) export it with refrences to > that headline as internal links. > 2. The exported HTML doesn't contain the radioed headline. So > references to radioed text shouldn't be linkified. I vote for #2. I expect org-export to clobber anything with a COMMENT keyword. But if the radio target is clobbered, then words pointing to it should not be "linkified." Note: I'm referring here only to automatic radio targets of the <<>> variety. If the user explicitly inserts links such as [[atarget]], they should remain even if the target does not exist. Best, Matt