From: Terje Kvernes <terjekv@math.uio.no>
To: Colin Morey <moreyc@realder.demon.co.uk>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] documenting using LVM during the install.
Date: 18 Aug 2002 02:20:23 +0200 [thread overview]
Message-ID: <wxx1y8xaugo.fsf@nommo.uio.no> (raw)
In-Reply-To: <1029628048.3371.10.camel@kidney.random-chaos.org.uk>
Colin Morey <moreyc@realder.demon.co.uk> writes:
> On Sat, 2002-08-17 at 23:46, Terje Kvernes wrote:
>
> > okay, last night was interesting. I found out that adding a
> > doctype to the standard documentation for Gentoo breaks apart the
> > top images (gtop-s and gtop-b) in Gecko-based user agents. I'm
> > not quite sure of what to do about that, yet. suggestions are
> > welcome.
>
> interesting.. do you mean a doctype to the xml? as the main Gentoo
> front page at http://www.gentoo.org has a Doctype, and yet the
> images look fine for me with Galeon v1.2.5
ah. interesting. you give the doctype as:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
while xsltproc[1] gives:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
which breaks the images. hm, I'm not sure if you can omit the
URI[2]. maybe I'll fiddle with this and see what happens. the big
issue is that the image breaks with the doctype xsltproc returns,
since setting the doctype yourself isn't trivial, since it's not
valid XML, and can't be used in the xsl-document. maybe one can
fiddle with CDATA or something? hmpf. not my cup of tea.
> > input on <url: http://terje.kvernes.no/lvm.html > is also welcome.
>
> looking good so far..
well, I'm not sure what is missing from that document. it is as you
can see produced with the standard xsl.
> however I'd be tempted to move the paragraph that's in the
> right-hand column of the page,(the summary), into a forward/preface,
> otherwise it will cause the right-hand bar to take up a large amount
> of screen space on low-res browsers.
I totally agree, but this is the standard Gentoo layout. I'd be
_happy_ to fix some visual aspects like this, and remove some table
usage, and maybe some other small fixes, if people are interested.
[1] xsltproc returns html doctypes when given a proper xsl:output,
like this:
<xsl:output encoding="iso-8859-15"
method="html"
version="4.01"
media-type="text/html"
omit-xml-declaration="yes"
indent="yes"/>
[2] W3.org on HTML version info:
<url: http://www.w3.org/TR/html4/struct/global.html#version-info >
--
Terje
next prev parent reply other threads:[~2002-08-18 0:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 0:19 [gentoo-dev] documenting using LVM during the install Terje Kvernes
2002-08-09 0:30 ` Jon Nelson
2002-08-09 1:37 ` Terje Kvernes
2002-08-10 0:10 ` Terje Kvernes
2002-08-10 7:55 ` Tony Clark
2002-08-10 10:19 ` Terje Kvernes
2002-08-10 11:23 ` Terje Kvernes
2002-08-10 12:03 ` Tony Clark
2002-08-10 13:41 ` Terje Kvernes
2002-08-10 22:22 ` Colin Morey
2002-08-11 15:25 ` Terje Kvernes
2002-08-11 6:54 ` Colin Morey
2002-08-17 22:46 ` Terje Kvernes
2002-08-17 23:47 ` Colin Morey
2002-08-18 0:20 ` Terje Kvernes [this message]
2002-08-18 10:36 ` Colin Morey
2002-08-09 2:59 ` Matthew Kennedy
2002-08-09 3:36 ` Jack Morgan
2002-08-09 4:34 ` Terje Kvernes
-- strict thread matches above, loose matches on Subject: below --
2002-08-09 5:50 [gentoo-dev] Documenting " Frederic Soulier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wxx1y8xaugo.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--cc=gentoo-dev@gentoo.org \
--cc=moreyc@realder.demon.co.uk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox