From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: Re: The way tags are exported in HTML (without colons!) -- no workaround for searches! Date: Fri, 04 Feb 2011 21:56:56 +0100 Message-ID: <4D4C6818.8060506@christianmoe.com> References: <80lj4hitej.fsf@missioncriticalit.com> <87k4hhf2p1.fsf@gnu.org> <80zkqcq4vt.fsf@missioncriticalit.com> <80lj1wp4x5.fsf@missioncriticalit.com> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from [140.186.70.92] (port=57416 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PlSfP-00047L-Lh for emacs-orgmode@gnu.org; Fri, 04 Feb 2011 15:54:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PlSfN-0004KA-Ql for emacs-orgmode@gnu.org; Fri, 04 Feb 2011 15:54:07 -0500 Received: from mars.hitrost.net ([91.185.211.18]:47711) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PlSfN-0004Jo-JC for emacs-orgmode@gnu.org; Fri, 04 Feb 2011 15:54:05 -0500 In-Reply-To: <80lj1wp4x5.fsf@missioncriticalit.com> 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: =?UTF-8?B?U8OpYmFzdGllbiBWYXViYW4=?= Cc: emacs-orgmode@gnu.org This bookmarklet finds an Org tags in exported HTML in Firefox, at least (just a proof of concept). To try it just copy-paste the whole thing into the address field. javascript: t=window.prompt("Tag?", ""); e=document.getElementsByClassName(t); for(i=0;i Hi Jeff, > > Jeff Horn wrote: >> 2011/2/3 Sébastien Vauban: >>> What about really adding the colon marker, so that one can easily find tags in >>> the exported file? >> >> Use the CSS content property. >> >> http://www.w3schools.com/Css/pr_gen_content.asp > > If you read my post of [2010-11-25 Thu 11:34] in this thread, you'll see I did > try that, but it's not working for the searches: > >>>> * Workaround? >>>> >>>> Maybe adding a colon before and after the tag would help? CSS to the >>>> rescue: >>>> >>>> #+begin_src >>>> .tag:before { >>>> content: ":"; >>>> } >>>> >>>> .tag:after { >>>> content: ":"; >>>> } >>>> #+end_src >>>> >>>> Answer is: no! In the HTML display, we now do well see a ":me:", but >>>> searches on that same string fail to find it. >>>> >>>> * Solution? >>>> >>>> - Really add a colon marker in the exported file (to HTML) > > Best regards, > Seb >