Hello. I'm trying to read eclass howto. But I have screen with hight resolution so I prefer to increase font size of the text. The problem is with eclass HOWTO. I do not know why it uses <pre> teg in it's body so when I encrease font size some of text is out of the screen. It's very uncomfortable to read. I have to move text left and right with mouse... Most of other documentation is Ok. Here is the link to eclass HOWTO: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=2 Thank you for your attention. Reproducible: Always Steps to Reproduce:
We just handle the content, not the templates... Reassigning to the doc-team.
<pre> tags don't wrap the contents over multiple lines. This is enforced and should (will) not be changed. The main reason is because code listings frequently contain commands or code snippets that are invalid when the wrapping that would occur is really interpreted as wrapping. For instance, """ # ln -s linux-2.6.10 linux """ and """ # ln -s linux-2.6.10 linux """ result in different things when the user interpretes the last example differently. To fix this, the code listing can either be changed to wrap hard-coded (content-wise) or not at all. So, devrel: if there is no reason to rewrite the code listing to change the wrapping (this would mean the $Header line in Code Listing 1) then you can use CANTFIX/WONTFIX. Or pass it back to docs-team and we'll mark it CANTFIX/WONTFIX.
On a sidenote, it can be fixed by substituting the <!-- $Header .... --> line to """ <!-- $Header$ --> """ which will be displayed as a (short) <!-- $Header$ --> line. Just a thought.
$Header$ line fixed; update should reach the mirrors within an hour or two.
Well. I don't know what happened, but someone definitly changed odd behavour... Look. I've opened that page in konqueror and firefox with same result. I've posted bug about this on firefox's buglist and they told me that there is a problem with the document not the browser. SO the problem was!!! BUT Now. I can not reproduce it. So may be the problem was with <!-- $Header. I don't know. In any way. Thank you for your work.
