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
Steps to Reproduce:
Love the docs but struggle with the implemenation
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:
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).
Marking as WORKSFORME
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.
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, ...).
Closing this bug as per Josh's request in gentoo-doc's ML.
*** Bug 339290 has been marked as a duplicate of this bug. ***