Return-Path: 
 <docs-return-3452-apmail-httpd-docs-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-docs-archive@httpd.apache.org
Received: (qmail 53422 invoked by uid 500); 5 Aug 2002 09:15:30 -0000
Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:docs-help@httpd.apache.org>
list-unsubscribe: <mailto:docs-unsubscribe@httpd.apache.org>
list-post: <mailto:docs@httpd.apache.org>
Reply-To: docs@httpd.apache.org
Delivered-To: mailing list docs@httpd.apache.org
Received: (qmail 53405 invoked from network); 5 Aug 2002 09:15:29 -0000
X-Lotus-FromDomain: TELEKURS DEUTSCHLAND GMBH
From: Michael.Schroepl@telekurs.de
To: docs@httpd.apache.org
Message-ID: <C1256C0C.0031CB12.00@detkw004.dnotes.telekurs.com>
Date: Mon, 5 Aug 2002 11:16:28 +0200
Subject: Antwort: RE: Antwort: Wacky new docs style
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


Hi Vincent,


> Basically, everything that can be done wiht HTML, can
> be done with XML/XSLT. Please keep in mind that XSLT
> _transforms_ the XML into HTML (if you ask your browser
> to open XML, it will do the XSLT locally). If we would
> be using CSS with XML, things would be more difficult.

do I have any chance to see which HTML code has been
generated? If I use the "view source" feature of the
browser, I can only see the XML source code.

> I also would like to see CSS and JS linked in (<LINK />
> and <SCRIPT href="..." />. This keeps the XSLT cleaner
> as well.

Yep. Editing the CSS class and tag attributes should
be able with CSS knowledge only, and without having
to understand the XSLT transformation process.
(On my pages the CSS definitions are linked into
the original "source" pages, but the ones that are
online have been "compiled" because my server can
serve static documents in compressed form and then
saving another HTTP access improves response speed.)

>> Also, this absolute positioning currently has no effect
>> in the Internet Explorer, where the behaviour would be
>> just like your current solution, so only Mozilla and
>> Opera would profit from it.
> I wouldn't bother to fix problems with non-standard compliant
> browsers. We should write code that complies to HTML 4.01
> or XHTML, CSS, ECMAScript and DOM. Most modern browsers
> would render this properly or satisfactory (Mozilla, IE 5+,
> Netscape 6+ and Opera).

Full Ack - I am doing the same on my pages.

> The most important thing should be to <DIV> the menu and
> top and set {display: none;} for them while printing.

+1 (I am already doing that myself, just forgot to
mention it here).

> I would suggest creating a sepparate print.css that is
> loaded last and only overrides the styles that need to
> be adjusted.

I am not sure whether this would exclude some current
browsers that cannot understand the appropriate parameter
of the <link> tag. (Internet Explorer?)
Thus I currently use the @media mechanism in my CSS
files and use one file only; if the printing specific
modifications are small then this rather keeps all
related informations at one point.



Regards, Michael



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