Opened 18 years ago

Closed 15 years ago

#2402 closed defect (wontfix)

end of page, line spacing

Reported by: florian.pons@… Owned by: nobody@…
Priority: normal Milestone:
Component: converters Version: 1.4.0
Severity: major Keywords:
Cc: Juergen Spitzmueller, Uwe Stöhr

Description (last modified by Vincent van Ravesteijn)

when i exporte to PDF or DVI format(the document was created with lyx 1.3.6 and
modifide with 1.3.7), at the end of a pages (all pages) the text is not in the
page; i use lyx-1.4.1-pre_win32_setup_v1 (2006-03-19)
when i reopen the file with lyx1.3.7 it works well back.
compiled by Angus Leeming.

the same in french (my english is not very good):
lorsque j'exporte mon document aux formats PDF et DVI (un document en
particulier créé avec la version 1.3.6 puis modifié avec la version 1.3.7), le
text en fin de page sort de la feuille; j'utilise lyx-1.4.1-pre_win32_setup_v1
(2006-03-19)
compilé par Angus Leeming
lorsque je réouvre le fichié avec lyx1.3.7 les fiché exporté sont de nouveau de
bonne qualité.

Change History (22)

comment:1 by florian.pons@…, 18 years ago

i found where the problem come from:
document>settings>text layout
line spacing:

onehalf (don't work well)
single (no problem)

comment:2 by florian.pons@…, 18 years ago

Summary: end of pageend of page, line spacing

comment:3 by Uwe Stöhr, 18 years ago

Cc: leeming@… added
Severity: majornormal

j'utilise lyx-1.4.1-pre_win32_setup_v1 (2006-03-19)

C'est une version pour tester!
Nevertheless, I can reproduce this problem also with LyX 1.4.0.

comment:4 by Uwe Stöhr, 18 years ago

Cc: uwestoehr@… added

comment:5 by michael.gerz@…, 18 years ago

Milestone: 1.4.1
Severity: normalmajor

This looks like a major bug as many people (like me) use special line spacings.
1.3.7 and 1.4.X should definitely produce the same output.

Florian, could you please export your file to LaTeX with 1.3.7 and 1.4.0 and
check the differences LaTeX-wise?

comment:6 by michael.gerz@…, 18 years ago

Cc: georg.baum@… added

Ouch! This bug is nasty.

Here is what has changed from 1.3.7 to 1.4.0:

%% LyX 1.3 created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[frenchb]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage{a4wide}
\usepackage{setspace}
\onehalfspacing
...

%% LyX 1.4.1svn created this file. For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[french]{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}
\usepackage{setspace}
\onehalfspacing
\usepackage{amssymb}
...
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
\usepackage{a4wide}

Since 1.4.X no longer supports a4wide.sty natively. lyx2lyx adds a user-specific
command to the preamble. As a consequence, the order of setspace and a4wide is
reverted which causes the problem.

I have no idea how we can resolve this problem. Thank God the consequences of
the change are so radical that a user can't overlook it.

Maybe it would be better to raise a warning during lyx2lyx convertion rather
than adding a user-specified command that the user is not aware of (i.e., he may
not be able to fix the problem by himself unless he looks at the preamble (which
doesn't mean anything to an average user))

comment:7 by Georg Baum, 18 years ago

A warning during lyx2lyx conversion would not help, because it would be sent to
the terminal and never seen. Therefore I think the current situation is better,
or maybe one could work around the problem: Instead of \usepackage{a4wide},
lyx2lyx would output something like (pseudo code)

\usepackage{a4wide}
if not normalspacing

fix problems

endif

I guess the "if not normalspacing" would not be too difficult, but I the "fix
problems" part may be tricky.

comment:8 by florian.pons@…, 18 years ago

Document>settings>latex preamble
\usepackage{a4wide}
is write, if i delete it, the document seems to worke well with the line spacing
onehalf but it change margins (I have use little margine) so i have to change
back margins manualy.

comment:9 by Juergen Spitzmueller, 18 years ago

Cc: j.spitzmueller@… added

Note that the same also happens with headings (#2372). Too bad that we ever
supported that packages.
Could lyx2lyx check if a4[wide] is used, and if, place the setspace and
fancyhdr command to the user preamble instead of natively using it? I don't
know another solution.

comment:10 by Georg Baum, 18 years ago

That does unfortunately not work, because it is not possible to prevent the
automatic \usepackage{setspace}, but I have a different idea: Maybe it is
possible to achieve the same effect as a4wide.sty with another package that
does not clash with setspace?

comment:11 by Juergen Spitzmueller, 18 years ago

The problem is that there exist different versions of a4.sty and a4wide.sty,
so that I cannot even predict that a4wide.sty on your box has the same effect
than a4wide.sty on my box :-(

comment:12 by lasgouttes, 18 years ago

Milestone: 1.4.11.4.2

move bugs to 1.4.2. Sorry for the spam

comment:13 by lasgouttes, 18 years ago

Milestone: 1.4.21.4.x

comment:14 by Richard Heck, 17 years ago

Milestone: 1.4.x1.5.x

Moving all bugs targeted to before 1.5.0 to 1.5.x.

If these are yours, please check that they have not been fixed and, if so, close
them.

Otherwise, sorry for the spam.

comment:15 by Georg Baum, 17 years ago

Cc: georg.baum@… removed

comment:16 by Juergen Spitzmueller, 16 years ago

Milestone: 1.5.x1.6.x

1.5.x is frozen. Shifting all 1.5.x-targetted bugs to 1.6.x.

If you have reported this bug, please verify if it still occurs in 1.6.0 and
close the report, if not.

comment:17 by ps, 15 years ago

Priority: highnormal

comment:18 by Vincent van Ravesteijn, 15 years ago

Cc: Juergen Spitzmueller Uwe Stöhr added; leeming@… j.spitzmueller@… uwestoehr@… removed
Description: modified (diff)

This is about a lyx2lyx bug between versions 1.3.7 and 1.4.0..

.. shall we close this now ?

comment:19 by ps, 15 years ago

Keywords: infoneeded added

comment:20 by Uwe Stöhr, 15 years ago

.. shall we close this now ?

I vote to close this as WONTFIX.

comment:21 by Vincent van Ravesteijn, 15 years ago

Keywords: infoneeded removed
Milestone: 1.6.x
Resolution: wontfix
Status: newclosed

Me too.

comment:22 by Richard Heck, 10 years ago

Component: exportconverters
Note: See TracTickets for help on using tickets.