Can not print the "Leadership Code Of Conduct"

[Charlie Kravetz]

The http://www.ubuntu.com/community/leadership-conduct is formatted in a way that prevents printing the entire page on my HP Laserjet 3200. Since the type is very small on this page and in a color not easily read with limited visual ability, I attempted to print the page out. The printout consists of two pages, page 1 of two prints the first two lines of the paragraph "Keeping the Personal Personal". I then got page 2 of 2, which consists only of the footer. Can we format pages on this official wiki in a way that allows full pages to print? It would also be better to change the way the font is specified to allow a users browser preferences to control the font, instead of the page.

[Laura Czajkowski (czajkowski)]

The LCoC will be signed and set up on LP so I don't think having it fixed on the wiki will make much of a difference as all of the information regarding signing it and agreeing to it will be moved to another place in the future during this cycle.

[Chris Johnston (cjohnston)]

What is the reason for printing it?

[qoiwejqioejqio (qioeujqioejqioe-deactivatedaccount)]

Using an alternate CSS stylesheet for the print media would solve this issue, making it possible to define better font sizes, columns widths and etc for reading on a paper. Also removing the menu and footer, as they're useless on a printed page.

As for the wrong printing, I'm not close to a printer to test it on a real one, but printing on a PDF works fine.

[Charlie Kravetz (cjkgeek)]

@Chris Johnston : Since the type is very small on this page and in a color not easily read with limited visual ability, I attempted to print the page out.

[Alan Bell (alanbell)]

Prints OK for me to a postscript printer on A4 paper. The font size is rather small though, just like it is on the web page.

[Matthew Nuzum (newz)]

Hi, I'm also considering this incomplete. I've tested in Firefox and Chrome and it looks fine. What browser are you using?

[Charlie Kravetz (cjkgeek)]

I use firefox. The issue is not how it looks, but how it prints.

[Charlie Kravetz (cjkgeek)]

I now fully understand the users that say bug reporting is frustrating. On this issue, which is about trying to print http://www.ubuntu.com/community/leadership-conduct , I have at least two people telling me it looks fine in the browser, and one telling us it prints fine to a PDF file. What part of "print to a hardware printer" got missed?

[Charlie Kravetz (cjkgeek)]

Would someone be so kind as to explain why printing this page was bad? I do not understand what is incomplete when I say I can not see the page clearly, the font is tiny and presents itself as many blurred lines of text, it is easier to read if I print it and use a magnifying glass to read it. What other information do you require to make this complete?

[Chris Johnston (cjohnston)]

I printed it, it is a little small, but ok to me.. The plan is to move the LCoC to LP, so I don't see a need to change it on the website.

A few things on the initial bug report: 1) It isn't a wiki page 2) Allowing user preferences to manage the fonts can mess up layouts.

[Charlie Kravetz (cjkgeek)]

Well, thank you. Since manage the fonts to make the page readable also makes it accessible, perhaps a warning the website that some pages will not be accessible could be managed. Go ahead and close this report if it makes you feel good.

[Matthew Nuzum (newz)]

Hi, Charlie, I think Chris got in touch with you via IRC, we should move this discussion to the ubuntu-website mailing list. This isn't a bug, per-se (though I realize you feel it is a problem with the website). Instead, it's a design decision and the people who can help resolve it participate on that list.

[Charlie Kravetz (cjkgeek)]

Obviously, then, the rhetoric about Accessibility being at least as important as design is just that? A design decision that makes the website inaccessible is still a design decision that says we don't actually care about being accessible if "it looks good".

[Michael Hall (mhall119)]

I think what he meant was that this is something that can only be resolved by getting an accessible design, which is not something the ubuntu-website project team can do.

[Charlie Kravetz (cjkgeek)]

Subscribing the Canonical Design team since this appears to be a bug in design, according the mailing list comments.

[Alan Bell (alanbell)]

It prints on paper just fine for me using Chromium and Firefox. The font size is small and it just prints in a column down the middle of the page but that is because of the use of the 960.gs system which is just a monumental travesty that has broken the web in order to make paper oriented designers feel better. Back to the point, there are no media="print" stylesheets, I thought there might be a broken print stylesheet that is being loaded on printing from some browser but it seems not. I can't reproduce the problem and I can't see anything in the source that points to a source of a potential problem on other systems. Here are the css files it loads, note media="all" so all media types should be equally impacted by the failings of titchy fonts and a rigid 960 width - including the totally arbitrary concept of what a pixel means on a postscript file targeted at at 2400dpi printer, I just wish it actually did print the whole thing in a strip 0.4 inches wide, that might encourage people to actually produce designs that work on more than one output device.

Here are the css files it calls.

<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/ninesixty/styles/framework/reset.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/ninesixty/styles/framework/text.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/ucbase/960.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/ninesixty/styles/framework/debug.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/node/node.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/defaults.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/system.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/system/system-menus.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/modules/user/user.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/cck/theme/content-module.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/ctools/css/ctools.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/lightbox2/css/lightbox.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/migrate/migrate.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/nice_menus/nice_menus.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/nice_menus/nice_menus_default.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/panels/css/panels.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/wysiwyg/editors/css/tinymce-3.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/default/themes/ubuntu10/ajax_overlay.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/views/css/views.css?w" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/ninesixty/styles/sty...

[Charlie Kravetz (cjkgeek)]

As quoted to me on the mailing list:

Take a look at: https://wiki.ubuntu.com/Bugs/Status

<https://wiki.ubuntu.com/Bugs/Status>"*Incomplete*:

   -

   If you have to ask the reporter questions, set the bug to Incomplete
   - Ask the submitter to provide any necessary information in a comment,
   and make sure you subscribe yourself to the bug report so you will get any
   updates to the bug via e-mail."

Based upon the triaging guidelines, the bug was set to incomplete. I do see
now, and may have misread/misunderstood initially that you said "Since the
type is very small on this page and in a color not easily read with limited
visual ability, I attempted to print the page out." So I do now understand
why you are trying to print the page. I have myself printed the page, and
the page printed properly, as has another user. Both stated that the text is
on the small side, however that is because it prints the same size as how it
is set on the website.

/end /

I am still waiting for the actual question to be given so that I might be able to answer it and get this issue resolved.

[Chris Johnston (cjohnston)]

Marking new... Still isn't confirmed.

[Mark Shuttleworth (sabdfl)]

I just printed the page without problems from Chromium.

Unless this bug can be confirmed with a particular printer/browser combination, I think we should close it.

It may be worth opening a second bug for a print-media CSS for the wiki (and other sites that share the same CSS).

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this issue. Others have attempted to reproduce this issue and can not. Perhaps there is a problem with the settings you are using for your own printer. We are setting the status as invalid until you can verify that the issue is indeed with the website page instead of your local settings. You can set the status above back to 'new' if you find this is not your local settings, however, until it can be reproduced by the developers, it can not be fixed.