> I'm seeing these warnings in tables that *aren't* breaking the right
> margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible to the
eye? Perhaps I can add some user-controlled fuzziness (similar to
TeX). If you don't think this is the cause please send m
Hi
Werner wrote:
> > No macro, register, or string name within standard macro
> > packages will ever end in * . Thus all user created names that
> > end in * will never collide with any within the standard macro
> > packages.
>
> Nice idea. Have you already verified that no mac
On Thu, Feb 04, 2010 at 10:11:59PM +0100, Werner LEMBERG wrote:
> > No macro, register, or string name within standard macro
> > packages will ever end in * . Thus all user created names
> > that end in * will never collide with any within the standard
> > macro packages.
>
> Nice
warning: around line 35: table wider than line width
warning: around line 35: table squeezed horizontally to fit line length
warning: around line 367: table wider than line width
warning: around line 367: column separation set to zero
I've included a patch to include the file name in the warnin
Mike Bianchi schrieb:
> On Thu, Feb 04, 2010 at 10:11:59PM +0100, Werner LEMBERG wrote:
>>> No macro, register, or string name within standard macro
>>> packages will ever end in * . Thus all user created names
>>> that end in * will never collide with any within the standard
>>>
Werner LEMBERG wrote:
> > I'm seeing these warnings in tables that *aren't* breaking the right
> > margin as well as ones that are.
>
> Hmm. Perhaps the overshoot is very small, thus not visible to the
> eye? Perhaps I can add some user-controlled fuzziness (similar to
> TeX). If you don't t
> > > I'm seeing these warnings in tables that *aren't* breaking
> > > the right margin as well as ones that are.
> > Hmm. Perhaps the overshoot is very small, thus not visible
> > to the eye? Perhaps I can add some user-controlled
> > fuzziness (similar to TeX). If you don't think this is the
Werner:
On Thu, Feb 04, 2010 at 05:11:25PM +0100, Werner LEMBERG wrote:
>
> > In trying to get "IMG" and "PIMG" to function, I noted that the
> > macro definitions seemed to have the arguments confused when
> > interpreting the width and height arguments. [...]
>
> Thanks for the report. It wo
>> > Hmm. Perhaps the overshoot is very small, thus not visible
>> > to the eye? Perhaps I can add some user-controlled
>> > fuzziness (similar to TeX). If you don't think this is the
>> > cause please send me such an offending table for further
>> > inspection.
>
>> That's pretty likely, the o
> I'm seeing these warnings in tables that *aren't* breaking
> the right margin as well as ones that are.
Hmm. Perhaps the overshoot is very small, thus not visible
to the eye?
>>> That's pretty likely, the overshoot is not easily noticed.
>> There appear to be two different
>> I was imprecise. I've meant to add some fuzziness control so that
>> a small squeeze doesn't cause a warning.
>
> Perhaps by "overshoot not visible to the eye" you did not mean that
> a table a little wider than the line length would not be noticed,
> but rather that a little squeezing wouldn
11 matches
Mail list logo
