Antwort: Re: Antwort: [PATCH] German translation, unixware.html .de (new file)

[Mi...@telekurs.com]

Hi Ken,


>> a) omit the color definitions in the <body> tag, i. e. use
>>    CSS to specify them (probably in some global file being
>>    used by the whole Apache documentation),
> Why?  AFAIK, we haven't (yet) moved the entire project to CSS,

does that explicitly mean the use of CSS is forbidden as
for now?

> so submissions shouldn't be forced to use it.

Full Ack.

The file I have posted contains CSS locally (in the <head>);
this _might_ be a way to use CSS until some global decision
about using external CSS files is done.

I would neither suggest doing this right now, nor am I
unhappy if you just throw away my version. All I wanted
to show is how little was missing for XHTML 1.1 ...

> However, this requires that the project as a whole conclude
> that the time has come to make the transition, and to figure
> out how.  As yet that hasn't happened (AFAIK).

... and by the way why not open a little discussion
about using CSS in all Apache docs? If you feel that it
is not the right time to think about this, just say so.

I thought it might well be the right time, as generating
these documents from XML sources might also provide a
way to specify references to CSS definitions there;
maybe the module docs would require different CSS defs
that the article docs or whatever.
But when I look at the HTML source of Apache docs, I don't
find too much of different formatting there, thus the
CSS definitions for this shouldn't be too complicated.

Regards, Michael



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org

Re: [PATCH] German translation, unixware.html.de (new file)

[Rodent of Unusual Size <Ke...@Golux.Com>]

Michael.Schroepl@telekurs.com wrote:
> 
> does that explicitly mean the use of CSS is forbidden as
> for now?

Not forbidden, but not encouraged instead of the older markup.
Adding it now will just mean changing it later, and with multiple
language-versions per file, that could get messy.

> > However, this requires that the project as a whole conclude
> > that the time has come to make the transition, and to figure
> > out how.  As yet that hasn't happened (AFAIK).
> 
> ... and by the way why not open a little discussion
> about using CSS in all Apache docs?

By all means.  What we really want to do, methinks, is rip out
all of the layout information and let the stylesheets apply
it when generating the HTML.  However, I don't think we're
doing the XML thing for the 1.3 documentation (though I personally
think it would be a Good Thing; any volunteers?).

Let me see..  Ah, yes, here it is.  Check out the page at
<URL:http://scarab.tigris.org/source/browse/scarab/www/ui/csi/style/>
with and without CSS enabled.  The L&F is quite similar so I think
we could take a clew from the way it was done to get the most out
of CSS without having to bog the source down with the old-fashioned
markup as well.

Let's definitely start working on a CSS stylesheet that does what
we want for the documentation.  I'm all in favour.  When we've hammered
out something with which we're consensually happy, we can retrofit
the docco to use it.  In the meantime, though, I think having CSS in
some files, and not in others, and even different CSS in different
files, is just a confusing morass that we'd do well to avoid. :-)
-- 
#ken	P-)}

Ken Coar, Sanagendamgagwedweinini  http://Golux.Com/coar/
Author, developer, opinionist      http://Apache-Server.Com/

"Millennium hand and shrimp!"

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org
For additional commands, e-mail: docs-help@httpd.apache.org