Re: underfull/ overfull badboxes
On 20/03/2012 10:43 a.m., stefano franchi wrote: On Mon, Mar 19, 2012 at 3:39 PM, Richard Heck wrote: On 03/19/2012 04:26 PM, Steve Litt wrote: On Mon, 19 Mar 2012 15:57:37 -0400 Richard Heckwrote: On 03/19/2012 12:17 PM, paul sutton wrote: 27,underfull \hbox (badness 10,000) in paragraph 31,underfull \hbox (badness 10,000) in paragraph 31underfull \hbox (badness 10,000) in paragraph These are warnings that LaTeX had to stretch the inter-word spacing more than it would like to do in order to fill the line. The first is the first paragraph of the Introduction and is probably caused by the newline, so you can ignore it. The second is the first line of the next paragraph, and if you look at it you can see how it is kind of stretched out. The way to fix it is to re-write the line a bit, or just not to bother. One man's opinion: If you ever start tweaking content to satisfy format, you'd might as well switch from LyX to Scribus or some other coffee-table-book-authoring-tool. This is a pure typesetting issue. I'm perfectly happy to re-write a line a teeny bit to get a better break, so it will look right. Or you can take it all the way, as philosopher/cognitive scientist Hofstadter. See enclosed png (I am too lazy to retype the quote and Amazon does not allow me to capture the fragment as text). Cheers, S. Thank you for the Hofstadter quote Stefano. When I first came into contact with equation editor in Word 95 in 1996 I became aware that it was much harder to use a slap-dash argument, much harder to deceive myself about the quality of an argument, when faced with an elegantly typeset equation. Andrew
Re: underfull/ overfull badboxes
On Thu, 22 Mar 2012 13:21:52 -0700 (PDT)
Marcelo Acuña wrote:
> > Jürgen
>
> > > \tolerance is [...]
> >
> > thanks
> >
> > >> I need a flexibilty in the page height (really text height)
> > >> because I have some problems with prematures page break for a few
> > >> milimeters but I don`t know how to get it. Is tolerance or
> > >> emergencystretch the way for get it?
> >
> > >I would try \enlargethispage{10pt} (or any value of your choice) on
> > >the respective page.
> >
> > Yes. I use it, but I want a global solution, not to go page for
> > page and put a command that may be a headhache. I don`t know if it
> > is possible.
> >
> > Marcelo
> [StevET]
> You basically mean Widow/Orphan protection, right?
>
>
> I get Widow/Orphan protection by mean of usual stuff in preamble.
>
> (This leads me to believe that Lyx could add the option for a single
> click add these commands to avoid problems for newbies.)
>
> My problem is: I have two columms in all works. Time to time, I get
> a premature page break (column break) and a huge and ugly blank space
> and disbalanced columns in a page.
> I need to get back some text from the next column. And I want to
> have a global solution in the preamble for this problem and not a
> case by case ERT workaround.
>
> Marcelo
Hi Marcelo,
Yes, case by case workarounds, whether ERT or content modifications,
reduce the quality of life.
Two columns is challenging because each column is narrow relative to
the number of characters in a line, so you have to settle for more
intercharacter and interword variation. Look carefully at any newspaper
and you'll see that even they have these almost unacceptable variations.
I'm not quite sure what would cause a huge vertical empty space except
a heading (section, subsection, etc) or a graphic. What I'd recommend
is to find each of these huge empty spaces and try to find what's in
common with each. Another troubleshooting technique might be to make a
small test document that incorporates one of those huge spaces and not
much else, then export to LaTeX, and then on the command line compile
with LaTeX and watch the warnings. Then try to fix it in LaTeX, and
once you can do that, see if you can find a global fix.
Re: underfull/ overfull badboxes
> Jürgen
> > \tolerance is [...]
>
> thanks
>
> >> I need a flexibilty in the page height (really text height)
> >> because I have some problems with prematures page break for a few
> >> milimeters but I don`t know how to get it. Is tolerance or
> >> emergencystretch the way for get it?
>
> >I would try \enlargethispage{10pt} (or any value of your choice) on
> >the respective page.
>
> Yes. I use it, but I want a global solution, not to go page for page
> and put a command that may be a headhache. I don`t know if it is
> possible.
>
> Marcelo
[StevET]
You basically mean Widow/Orphan protection, right?
I get Widow/Orphan protection by mean of usual stuff in preamble.
(This leads me to believe that Lyx could add the option for a single click add
these commands to avoid problems for newbies.)
My problem is: I have two columms in all works. Time to time, I get a
premature
page break (column break) and a huge and ugly blank space and
disbalanced columns in a page.
I need to get back some text from the next column. And I want to have a
global solution in the preamble for this problem and not a case by case ERT
workaround.
Marcelo
Re: underfull/ overfull badboxes
Marcelo Acuña wrote: > Yes. I use it, but I want a global solution, not to go page for page and put > a command that may be a headhache. I don`t know if it is possible. You might want to try \vfuzz I never played with that myself, though. Or simply enlarge the text height (via geometry). Maybe geometry even allows rubber lengths. I did not check that. Jürgen
Re: underfull/ overfull badboxes
On Tue, 20 Mar 2012 11:20:07 -0700 (PDT)
Marcelo Acuña wrote:
> Jürgen
> > \tolerance is [...]
>
> thanks
>
> >> I need a flexibilty in the page height (really text height)
> >> because I have some problems with prematures page break for a few
> >> milimeters but I don`t know how to get it. Is tolerance or
> >> emergencystretch the way for get it?
>
> >I would try \enlargethispage{10pt} (or any value of your choice) on
> >the respective page.
>
> Yes. I use it, but I want a global solution, not to go page for page
> and put a command that may be a headhache. I don`t know if it is
> possible.
>
> Marcelo
You basically mean Widow/Orphan protection, right?
StevET
Re: underfull/ overfull badboxes
>>> I need a flexibilty in the page height (really text height) because I have
>>> some problems with prematures page break for a few milimeters but I don`t
>>> know how to get it. Is tolerance or emergencystretch the way for get it?
>> I would try \enlargethispage{10pt} (or any value of your choice) on the>
>> respective page.
>Let me add that this:
> \enlargethispage{\baselineskip}
>is the easy way to get an extra line if you need it. Note that you can also do:
> \enlargethispage{-\baselineskip}
>to get one fewer line, which is sometimes better.
>Richard
I have two columms in all works. Time to time, I get a premature page break
(column break) and a huge and ugly blank space and disbalanced columns in a
page.
One fewer line is not usefull, I need to get back some text from the next
column.
I want to have a global solution in the preamble for this problem.
Marcelo
Re: underfull/ overfull badboxes
Jürgen
> \tolerance is [...]
thanks
>> I need a flexibilty in the page height (really text height) because I have
>> some problems with prematures page break for a few milimeters but I don`t
>> know how to get it. Is tolerance or emergencystretch the way for get it?
>I would try \enlargethispage{10pt} (or any value of your choice) on the
>respective page.
Yes. I use it, but I want a global solution, not to go page for page and put a
command that may be a headhache.
I don`t know if it is possible.
Marcelo
Re: underfull/ overfull badboxes
On 03/20/2012 02:02 PM, Jürgen Spitzmüller wrote:
I need a flexibilty in the page height (really text height) because I have
some problems with prematures page break for a few milimeters but I don`t
know how to get it. Is tolerance or emergencystretch the way for get it?
I would try \enlargethispage{10pt} (or any value of your choice) on the
respective page.
Let me add that this:
\enlargethispage{\baselineskip}
is the easy way to get an extra line if you need it. Note that you can
also do:
\enlargethispage{-\baselineskip}
to get one fewer line, which is sometimes better.
Richard
Re: underfull/ overfull badboxes
Marcelo Acuña wrote:
> What is the meaning of tolerance and emergencystretch.
\tolerance is a penalty value that defines how much "badness" (in line
setting) TeX accepts without yielding an error (and retrying to set the
paragraph differently). The higher the value, the more interword space is
tolerated.
\emergencystretch defines how much interword stretching TeX allows if
necessary.
Details are explained here:
http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull
> I need a flexibilty in the page height (really text height) because I have
> some problems with prematures page break for a few milimeters but I don`t
> know how to get it. Is tolerance or emergencystretch the way for get it?
I would try \enlargethispage{10pt} (or any value of your choice) on the
respective page.
Jürgen
Re: underfull/ overfull badboxes
>> I've often been able to use \begin{sloppy} and \end{sloppy} to make
>> LaTeX less pedantic about where to break a line, and thereby cure both
>> these warnings and the extra space.
>Read this "essential guide to LaTeX2e usage"
>http://mirror.ctan.org/info/l2tabu/english/l2tabuen.pdf
>
>which lists among "the most severe mistakes in using LaTeX2e":
>Section 1.8: "Should I use \sloppy?" (the answer is: "Frankly speaking, the
>\sloppy switch should not be used at all.")
>
>They suggest this preamble code, which works very well for me:
>\tolerance 1414
>\hbadness 1414
>\emergencystretch 1.5em
>\hfuzz 0.3pt
>\widowpenalty=1
>\vfuzz \hfuzz
>\raggedbottom
>Jürgen
What is the meaning of tolerance and emergencystretch.
I need a flexibilty in the page height (really text height) because I have some
problems with prematures page break for a few milimeters but I don`t know how
to get it.
Is tolerance or emergencystretch the way for get it?
Marcelo
Re: underfull/ overfull badboxes
Steve Litt wrote: > He then shows paragraphs with and without \sloppy. If I were reading > for information, and not as an artiste, I wouldn't notice the > difference. Really? To me, the typographic mess is quite obvious. Jürgen
Re: underfull/ overfull badboxes
On Tue, 20 Mar 2012 07:40:42 +0100
Jürgen Spitzmüller wrote:
> Steve Litt wrote:
> > I've often been able to use \begin{sloppy} and \end{sloppy} to make
> > LaTeX less pedantic about where to break a line, and thereby cure
> > both these warnings and the extra space.
>
> Read this "essential guide to LaTeX2e usage"
> http://mirror.ctan.org/info/l2tabu/english/l2tabuen.pdf
>
> which lists among "the most severe mistakes in using LaTeX2e":
>
> Section 1.8: "Should I use \sloppy?" (the answer is: "Frankly
> speaking, the \sloppy switch should not be used at all.")
>
> They suggest this preamble code, which works very well for me:
>
> \tolerance 1414
> \hbadness 1414
> \emergencystretch 1.5em
> \hfuzz 0.3pt
> \widowpenalty=1
> \vfuzz \hfuzz
> \raggedbottom
:-)
To me, Section 1.8 was written as an argument FOR use of \begin{sloppy}
\end{sloppy}. His #2 solution is to change your verbiage. All I can say
to that is that his priorities are very different from mine, and I
don't envy him if, after his tweaking, his editor suggests a change
before his tweak.
He then shows paragraphs with and without \sloppy. If I were reading
for information, and not as an artiste, I wouldn't notice the
difference.
I have no comments on his suggestions for the preamble code -- I might
try that myself.
Thanks
SteveT
Re: underfull/ overfull badboxes
Steve Litt wrote:
> I've often been able to use \begin{sloppy} and \end{sloppy} to make
> LaTeX less pedantic about where to break a line, and thereby cure both
> these warnings and the extra space.
Read this "essential guide to LaTeX2e usage"
http://mirror.ctan.org/info/l2tabu/english/l2tabuen.pdf
which lists among "the most severe mistakes in using LaTeX2e":
Section 1.8: "Should I use \sloppy?" (the answer is: "Frankly speaking, the
\sloppy switch should not be used at all.")
They suggest this preamble code, which works very well for me:
\tolerance 1414
\hbadness 1414
\emergencystretch 1.5em
\hfuzz 0.3pt
\widowpenalty=1
\vfuzz \hfuzz
\raggedbottom
Jürgen
Re: underfull/ overfull badboxes
On Mon, 19 Mar 2012 16:39:01 -0400
Richard Heck wrote:
> On 03/19/2012 04:26 PM, Steve Litt wrote:
> > On Mon, 19 Mar 2012 15:57:37 -0400
> > Richard Heck wrote:
> >
> >> On 03/19/2012 12:17 PM, paul sutton wrote:
> >>> 27,underfull \hbox (badness 10,000) in paragraph
> >>> 31,underfull \hbox (badness 10,000) in paragraph
> >>> 31underfull \hbox (badness 10,000) in paragraph
> >> These are warnings that LaTeX had to stretch the inter-word spacing
> >> more than it would like to do in order to fill the line. The first
> >> is the first paragraph of the Introduction and is probably caused
> >> by the newline, so you can ignore it. The second is the first line
> >> of the next paragraph, and if you look at it you can see how it is
> >> kind of stretched out. The way to fix it is to re-write the line a
> >> bit, or just not to bother.
> > One man's opinion: If you ever start tweaking content to satisfy
> > format, you'd might as well switch from LyX to Scribus or some other
> > coffee-table-book-authoring-tool.
> >
> This is a pure typesetting issue. I'm perfectly happy to re-write a
> line a teeny bit to get a better break, so it will look right.
But then you change something earlier in the book, and now your tweaked
line screws up again. It can go on forever.
>
> > I've often been able to use \begin{sloppy} and \end{sloppy} to make
> > LaTeX less pedantic about where to break a line, and thereby cure
> > both these warnings and the extra space. I've found this necessary
> > when a paragraph contains either a URL or a piece of monospaced
> > type.. I consider that acceptable if done in only a few instances.
> >
> If you're going to do this, then you can just ignore the warnings.
Except the sloppies often prevent your line from walking right off the
paper. I'm willing to subject the reader to a little ugliness, but
having to guess part of it is a little too much to expect :-)
Thanks
SteveT
Re: underfull/ overfull badboxes
Le 19/03/12 21:39, Richard Heck a écrit : This is a pure typesetting issue. I'm perfectly happy to re-write a line a teeny bit to get a better break, so it will look right. The microtype package can also help in some cases. JMarc
Re: underfull/ overfull badboxes
On 03/19/2012 04:26 PM, Steve Litt wrote:
On Mon, 19 Mar 2012 15:57:37 -0400
Richard Heck wrote:
On 03/19/2012 12:17 PM, paul sutton wrote:
27,underfull \hbox (badness 10,000) in paragraph
31,underfull \hbox (badness 10,000) in paragraph
31underfull \hbox (badness 10,000) in paragraph
These are warnings that LaTeX had to stretch the inter-word spacing
more than it would like to do in order to fill the line. The first is
the first paragraph of the Introduction and is probably caused by the
newline, so you can ignore it. The second is the first line of the
next paragraph, and if you look at it you can see how it is kind of
stretched out. The way to fix it is to re-write the line a bit, or
just not to bother.
One man's opinion: If you ever start tweaking content to satisfy
format, you'd might as well switch from LyX to Scribus or some other
coffee-table-book-authoring-tool.
This is a pure typesetting issue. I'm perfectly happy to re-write a line
a teeny bit to get a better break, so it will look right.
I've often been able to use \begin{sloppy} and \end{sloppy} to make
LaTeX less pedantic about where to break a line, and thereby cure both
these warnings and the extra space. I've found this necessary when a
paragraph contains either a URL or a piece of monospaced type.. I
consider that acceptable if done in only a few instances.
If you're going to do this, then you can just ignore the warnings.
Richard
Re: underfull/ overfull badboxes
On Mon, 19 Mar 2012 15:57:37 -0400
Richard Heck wrote:
> On 03/19/2012 12:17 PM, paul sutton wrote:
> > 27,underfull \hbox (badness 10,000) in paragraph
> > 31,underfull \hbox (badness 10,000) in paragraph
> > 31underfull \hbox (badness 10,000) in paragraph
> These are warnings that LaTeX had to stretch the inter-word spacing
> more than it would like to do in order to fill the line. The first is
> the first paragraph of the Introduction and is probably caused by the
> newline, so you can ignore it. The second is the first line of the
> next paragraph, and if you look at it you can see how it is kind of
> stretched out. The way to fix it is to re-write the line a bit, or
> just not to bother.
One man's opinion: If you ever start tweaking content to satisfy
format, you'd might as well switch from LyX to Scribus or some other
coffee-table-book-authoring-tool.
I've often been able to use \begin{sloppy} and \end{sloppy} to make
LaTeX less pedantic about where to break a line, and thereby cure both
these warnings and the extra space. I've found this necessary when a
paragraph contains either a URL or a piece of monospaced type.. I
consider that acceptable if done in only a few instances.
My most basic opinion is if your books' content is good, the reader
will accept formatting problems as long as they don't affect
legibility, so underfull and overfull boxes are usually no big deal.
My one exception to all of this is use of verbiage that will obviously
screw up the formatting. When tempted to use the word
"antidisestablishmentarianism", find a way to make it "people who don't
like those opposed to establishment" or some such.
HTH
SteveT
Re: underfull/ overfull badboxes
On 03/19/2012 12:17 PM, paul sutton wrote: Hi Following on from my previous questions on LaTex, the same file I have now figured out how to add tables of contents and indexes, which should be handy when I want to do this in LyX too, as I will have a better idea of what goes on underneath. My qestion now is around over / underfull boxes, the attached file (not sure if I needed to include the graphics here) but it compiles fine, only I get badbox errors on lines 27,underfull \hbox (badness 10,000) in paragraph 31,underfull \hbox (badness 10,000) in paragraph 31underfull \hbox (badness 10,000) in paragraph These are warnings that LaTeX had to stretch the inter-word spacing more than it would like to do in order to fill the line. The first is the first paragraph of the Introduction and is probably caused by the newline, so you can ignore it. The second is the first line of the next paragraph, and if you look at it you can see how it is kind of stretched out. The way to fix it is to re-write the line a bit, or just not to bother. I get an overfull \hox on line 62, (10,20177pt too wide) in paragraph This is more of an issue. It means the line overruns the margins. It's in (3) in your list. This is because LaTeX can't figure out how to hyphenate the line. It compiles fine, but LaTeX is telling you it doesn't look right. Richard
underfull/ overfull badboxes
Hi
Following on from my previous questions on LaTex, the same file I have
now figured out how to add tables of contents and indexes, which should
be handy when I want to do this in LyX too, as I will have a better idea
of what goes on underneath.
My qestion now is around over / underfull boxes, the attached file (not
sure if I needed to include the graphics here) but it compiles fine,
only I get badbox errors on lines
27,underfull \hbox (badness 10,000) in paragraph
31,underfull \hbox (badness 10,000) in paragraph
31underfull \hbox (badness 10,000) in paragraph
I get an overfull \hox on line 62, (10,20177pt too wide) in paragraph
I just wondered what has happened, as I said it compiles fine, so
despite 10,000 being high up the scale on badness it seems happy with
something.
I have looked this up just can't see what is wrong with my text, as I
start other paragraphs in the same way any they don't give issues.
I take it there are other ways I should be presenting that list at the
end perhaps as a table would be better, or don't i need to have url then
what it is next to it,
thanks,
Paul
--
--
http://www.zleap.net
http://www.ubuntu.com
skype : psutton111
http://www.linkedin.com/pub/paul-sutton/36/595/911
\documentclass[11pt]{report}
\usepackage{graphicx}
\usepackage{float}
\usepackage{makeidx}
\makeindex
\begin{document}
\begin{center}
\bf A SIMPLE GEANY HOW TO\\
\end{center}
\begin{center}
By Paul Sutton\\
\end{center}
\begin{center}
March 2012\\
\end{center}
\newpage
\tableofcontents
\newpage
\subsection*{Introduction}
\addcontentsline{toc}{subsection}{Introduction}
\index{Introduction}
The following paragraph is taken directly from the Geany Website [1]\\Geany is a text editor using the GTK2 toolkit with basic features of an integrated development environment.It was developed to provide a small and fast IDE,which has only a few dependencies from other packages.It supports many filetypes and has some nice features.\\
\subsection*{Getting Started}
\addcontentsline{toc}{subsection}{Getting Started}
\index{Getting Started}%
If Geany is not already installed you need to go to the Ubuntu software
centre [2] and install it. Or follow the instructions for your operating system
Once installed you can start the application from either the side bar
(software centre may give you the option to add to sidebar so please scroll
down to see what other options are available).\\
\begin{figure}[h]
\centering
\includegraphics[width=318pt,height=147pt]{./geany1.png}
% geany1.png: 1037x695 pixel, 72dpi, 36.58x24.52 cm, bb=0 0 1037 695
\caption{Geany Editor}
\end{figure}
\pagebreak
To start:-\\
a new file use: \\
{\bf File - New} \\
To Start a new file but use a template for a specific programming language use: \\
{\bf File - New (from template)} \\
You have quite a few options here, it is useful when programming however I would guess more experienced programmers won't bother, if you
look Liams Raspberry Pi Tutorials [3] he starts out with a template than deletes most of it anyway and just leaves the part he needs for the code and the first
line which points to where the python program resides.
\begin{figure}[h]
\centering
\includegraphics[width=318pt,height=147pt]{./geany2a.png}
% geany1.png: 1037x695 pixel, 72dpi, 36.58x24.52 cm, bb=0 0 1037 695
\caption{Geany Editor with python template}
\end{figure}
{\bf Further Reading}\\
\begin{enumerate}
\item http://www.geany.org/ Geany website
\item http://www.raspberrypi.org Raspberry PI website
\item http://www.youtube.com/user/RaspberryPiTutorials/videos Raspberry Pi tutorials
\end{enumerate}
\printindex
\end{document}
