OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [docbook-apps] How do I highlight inline text ?

It was big help.

The generic explanation followed by the specific example of wanting to
change from yellow to blue really hit the point home.

To follow your example, what I really want is

<emphasis role="key_words">some text</emphasis>

In "Using CSS to style HTML" in


it states to create a CSS stylesheet entry

.sqlsyntax {font-variant: small-caps;}

How do I go about figuring out the magic words for the CSS stylesheet entry

I am totally new to this stuff. I Googled around and found


selector {property: value; property: value; property: value; }

And now a worked example: p {color: blue; font-size: 120%; }

So, is it as easy as adding the following entry ?

.key_words {color: yellow}

I am attempting to be lazy and avoid working my way through


-----Original Message-----
From: Nathalie Sequeira [mailto:n@n-faktor.net]
Sent: Wednesday, April 07, 2010 5:31 PM
To: Robert Lucente
Cc: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] How do I highlight inline text ?

Hi Robert,

> Request help in figuring out how to highlight inline text.
> It seems that the way to go is to use something like <emphasis
> role="yellow">some text</emphasis>.
I think the way to go would rather be

<emphasis role="semantic_function_of_the_emphasis">some text</emphasis>

while your example actually is going

<emphasis role="how_the_emphasis_should_look">some text</emphasis>

> Pontification type of question: It seems like highlighting text w/ color
> should be a standard feature ? Since its not, I am missing the mind set
> associated w/ DocBook. What is the mind set w/ which to approach DocBook
> its processing chain such that it makes sense that color highlighting is
> built in ?
Yes, I'd say mind-set issue indeed :)

docBook handles information - the basic information plus the functions
single pieces of the information have within the whole (is this text a
title, for example, is it a list...or is it to be emphasized.).
Then come the docBook stylesheets, that will transform the docBook into
HTML for you (you can tweak how the result will be via customization layer).
And finally, colors and other aspects pertaining to styling are set in CSS.

The beauty of this is that (for example):
-  in a few years, you may get tired of all those yellow texts and may
want to make them blue or orange or purple instead. If you defined the
specific color via CSS, all you need to change is one single class, and
you're set up (instead of having to go through your docBook file and
edit all the instances of, say, "yellow" -- It's the same principle as
in separating content and form in plain old HTML & CSS).

- all texts you assign a certain role to (the name itself says it all -
"role", what is the role these words play in the text?) will be styled
in the same way,

- you can output your docBook-Information for different media, and can
use the SAME source for them all, defining how they should look
individually and OUTSIDE the docBook information itself.

also discusses the issue :)

Hoping that helps a bit,
Nathalie Sequeira

To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]