Subject: Re: Commit: More section break goodness.
From: Jesper Skov (jskov@redhat.com)
Date: Fri Aug 10 2001 - 08:32:59 CDT
>>>>> "Hubert" == Hubert Figuiere <hfiguiere@teaser.fr> writes:
Hubert> According to Martin Sevior
Hubert> <msevior@mccubbin.ph.unimelb.edu.au>:
>> Fix 1104 and other related section break bugs. Word Docs with lots
>> of section breaks are now imported much more sanely. Other Section
>> break fixes. Improvements in thread safety.
Hubert> Bug 1104:
Hubert> **** (1) Assert **** **** (1) iMaxWidth > 0 at
Hubert> fp_Line.cpp:1384 **** **** (1) Continue ? (y/n) [y] :
Hubert> **** (2) Assert **** **** (2) iMaxWidth > 0 at
Hubert> fp_Line.cpp:1408 **** **** (2) Continue ? (y/n) [y] :
Hubert> **** (3) Assert **** **** (3) iMaxWidth > 0 at
Hubert> fp_Line.cpp:1384 **** **** (3) Continue ? (y/n) [y] :
Hubert> **** (4) Assert **** **** (4) iMaxWidth > 0 at
Hubert> fp_Line.cpp:1408 **** **** (4) Continue ? (y/n) [y] :
This cannot be (easily) fixed. I asked a long time back how to cope
with for example a tab indent which is bigger than the page
width. This is what this assertion is about: there is not enough
(horizontal) space on the page to layout the Run.
IMO we should use something like the red squiggles to mark such layout
overruns, so the user knows something has gone wrong. In LaTeX one can
have a box rendered around text that spills beyond the limits, but
that would probably screw up scrolling:
|
|
|.......
dadasdasdsad sadadda |
|'''''''
Anyway, the end goal would be to make it easy for the user to see
where there are violations.
Jesper
This archive was generated by hypermail 2b25 : Fri Aug 10 2001 - 08:33:02 CDT