From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: The way tags are exported in HTML (without colons!) -- no workaround for searches!
Date: Thu, 03 Feb 2011 20:45:10 +0100 [thread overview]
Message-ID: <80zkqcq4vt.fsf@missioncriticalit.com> (raw)
In-Reply-To: 87k4hhf2p1.fsf@gnu.org
Hi Bastien,
Bastien wrote:
> Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> - As well, clearly make a separation between the different tags, instead of
>> concatenating them as one big chunck, so that we could put a background
>> color that'd be cut between the consecutive tags:
>>
>> +----+ +----+ +----+
>> |tag1| |tag2| |tag3|
>> +----+ +----+ +----+
>
> Each tag in the HTML output comes with its own CSS class.
>
> For example:
>
> ,----
> | * Heading1 :tag1:tag2:
> `----
>
> is exported as
>
> ,----
> | <div id="outline-container-1" class="outline-2">
> | <h2 id="sec-1">Heading1
> | <span class="tag">
> | <span class="tag1">tag1</span>
> | <span class="tag2">tag2</span></span>
> | </h2>
> `----
>
> You can tweak your .css to visually separate the tags.
Thanks for the above. Much appreciated.
>> - Really add a colon marker in the exported file (to HTML)
What about really adding the colon marker, so that one can easily find tags in
the exported file?
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-02-03 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:34 The way tags are exported in HTML (without colons!) -- no workaround for searches! Sébastien Vauban
2011-02-03 17:27 ` Bastien
2011-02-03 19:45 ` Sébastien Vauban [this message]
2011-02-03 21:15 ` Jeff Horn
2011-02-04 8:21 ` Bastien
2011-02-04 8:41 ` Sébastien Vauban
2011-02-04 20:56 ` Christian Moe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80zkqcq4vt.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).