Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 42825

Summary: default web page style columns too wide, does not collapse, suggest alternate css method to advertize alternative
Product: [OLD] Docs-user Reporter: Aaron Peterson <alpeterson>
Component: OtherAssignee: Sven Vermeulen (RETIRED) <swift>
Status: VERIFIED LATER    
Severity: enhancement CC: docs-team, grant.b.edwards
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
URL: http://www.gentoo.org/doc/en/handbook/handbook.xml?part=1&chap=5
Whiteboard:
Package list:
Runtime testing required: ---

Description Aaron Peterson 2004-02-24 16:34:20 UTC
probably it's own bug, but can gentoo's pages/documentation be made to have narrower columns? or resizable columns by deafult?

I find myself attempting to read the howto or GWN with a temrinal open, reading from the guide and doing what the guide says,
however there is a lot of pagenation

also, even while reading the regular website while doing nothing else, I often sit far away from my monitor and have to increase the text size of my browser.  Making me have to scroll sideways for each line of the GWN or guide.

I went out and bought a 21 inch monitor to help with this problem, but it still occurs regularly/ people shouldn't have to go through that expense

 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




Love the docs but struggle with the implemenation
Comment 1 Sven Vermeulen (RETIRED) gentoo-dev 2004-02-25 00:30:19 UTC
Except for the GWN, all documentation should also be readable on a printerfriendly way. To go to such a rendered document, add "?style=printable" (or, if arguments are already passed, "&style=printable") to the URL, like this:

http://www.gentoo.org/doc/en/xml-guide.xml?style=printable
http://www.gentoo.org/doc/en/handbook/handbook.xml?part=1&chap=1&style=printable

This should allow the documentation to be viewable on a 80-char wide screen (as used on terminals). Most documents cannot be decreased to a lower amount as the Code Listings in our documentation prohibit line wrapping (which you can hopefully understand as Code Listings are verbatim copied from what a user should do/see).
Comment 2 Sven Vermeulen (RETIRED) gentoo-dev 2004-03-02 03:59:18 UTC
Marking as WORKSFORME
Comment 3 Aaron Peterson 2004-03-02 21:22:25 UTC
&style=printable
really does help, 
infact it makes it work!

however, I would very much like to see it as an alternate css file/style

Mozilla (or at least firefox) and konqueror... and opera if I remember...
all show an icon indicating that an alternate style sheet is available..

My needs are met, but I'm reopening because of "discoverability" issues... 

Also switched to enhansement severity.

This also lays the framework for other alternate style sheets... like ones that hide certain platforms! (if code specific to a platform is wrapped in a tag indicating it's platform)

It would be worth the effort.

It's not bad to have a lot of alternate style sheets... because they can be selected at will.
Comment 4 Sven Vermeulen (RETIRED) gentoo-dev 2004-03-02 23:55:13 UTC
I'm marking this one as LATER then. CSS isn't supported by links/lynx while those two browsers are used by many users during the installation. Our XSL stylesheets aren't CSS-ready in the sense that the whole website isn't designed to fully take on the CSS features. 

As long as I'm not confident that all browsers fully support CSS the way we want to, I'd rather have the documentation generated on the server-side using HTML that we know all browsers support. Hence the "?style=printable" approach.

Separating the architecture-specific instructions is part of a different bug (#42823).

The "LATER" would then refer to the fact that our entire website needs a fixup (i.e. rewrite of the XSL stylesheets, redesign of the layout, ...).
Comment 5 Marcelo Goes (RETIRED) gentoo-dev 2006-01-26 10:22:46 UTC
Closing this bug as per Josh's request in gentoo-doc's ML.
Comment 6 nm (RETIRED) gentoo-dev 2010-10-01 08:08:06 UTC
*** Bug 339290 has been marked as a duplicate of this bug. ***