Gentoo Archives: gentoo-user

From: Stroller <stroller@××××××××××××××××××.uk>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Possibly OT: word-wrapping on
Date: Thu, 26 Jun 2008 19:37:09
Hi there,

Sorry if this is a dumb-ass question, but am I the only person who  
has problems with the word-wrapping on

For instance, comments 5 - 10 of < 
id=84011> are impossible to read for me, because the text overflows  
off the right of the page and if I want to read it I have to scroll a  
horizontal scrollbar at the bottom of the page. I have to scroll all  
the way right for each line, then all the way left to read the next  
one. This is frustrating to a degree that it makes the information on  
the page near-useless.

I have to admit that I'm using a Mac as my desktop computer, but I  
have tried this in Firefox as well as Safari and get the same thing.  
Do you also see this using the browsers available on your Linux  

I think it's always been this way, but in the past I have never  
needed to read a bug with so much information misformatted this way.  
Presumably there are workarounds available, can someone let me in on  
the secret? I had this idea that this was a common problem, but of  
course google for "word wrapping" returns word  
wrapping bugs with nano & kmail which happen to be filed on the site.

A bit more Googling finds:
   Server-Side Comment Wrapping

   In older Bugzillas, comments were wrapped to 80 characters by the
   user's web browser, and then stored in the database that way. This  
   problems because some browsers did not wrap comments properly.

   Now, Bugzilla stores comments unwrapped and wraps them at display  
time, so
   all new comments should be properly wrapped. Also, when you  
upgrade, Bugzilla
   will look for old "mis-wrapped" comments and attempt to wrap them  

But this does not seem effective against older comments in this  
particular bug report. <>
Do I simply have to live with it?


gentoo-user@l.g.o mailing list


Subject Author
Re: [gentoo-user] Possibly OT: word-wrapping on Kenneth Prugh <ken69267@×××××.com>