I'm trying to basically fold the relevant parts into the bug tracker. Can people
hint on which are these are still true ?
btw, why do we not allow X pastes from us when we've not done Edit->Copy ? Aslo
why does there seem to be a limit on how much is copied ?
thanks
john
> 1. The LyX keyboard mappings, including dead-keys, do not work in pop-up
> dialogs. You can try cut & paste from a text editor.
WONTFIX except for 224845
> 2. It is not possible to enter \dj{} or \DJ{} as LaTeX accent insets; this
> means that these characters are not available to people who want to use latin1
> as encoding.
>
> 3. On a very small (640\times 480?) screen, math panel pops up the subpanels
> off screen. It should check it's position, and put the panels somewhere
> visible.
XFORMS I'd say this is dead due to using FL_PLACE_MOUSE for these ...
> 4. The code which draws special accents not available in the current font does
> not work well with font encodings other than iso8859-1. In particular, the
> macron accent is not drawn correctly when using an iso8829-2 font.
> 5. LyX sometimes shows a strange/erroneous redraw of windows. The reason is
> probably that LyX uses the update/drawing mechanism in XForms wrongly. During
> normal operations this does not matter, but with resize and stuff like that it
> will show. In more detail: according to XForms documentation, all drawing on
> screen should use some XForms update/redraw callback/eventhandler. LyX is not
> (yet) doing this.
XFORMS
> 6. The vertical scroll bar of the preamble window is broken. If you resize the
> window, strange things can happen, including a fatal crash! This is a bug in
> XForms. [Note from Jean-Marc: things are a bit better now, but not perfect. ]
XFORMS
> 7. Sometimes, when you delete large sections of text, the screen will appear
> empty, and you have to use the scrollbar to make the cursor visible again.
yep, still there
> 8. When several insets are placed consecutively (this can happen with error
> insets), clicking on an inset can result in opening the wrong one. A workaround
> is to use C-o, with the cursor placed just before the desired inset.
>
> 9. The Citation Reference command doesn't escape "_" characters in the remarks
> field when generating TeX documents. You have to type "\_" by hand in these
> remarks if you want to use an underscore. Similar for other special characters.
>
> 10. If a figure is larger than one page down press would have taken you, the
> page down fails and you are left where you started. [Comment: behavior in this
> situation is improved but still imperfect. LyX now does the pageup or pagedown,
> but jumps from the top to the bottom of the figure, potentially skipping part
> of the middle.]
hidden currently by another bug
> 11. If you delete marked text, the text is not deleted, but "cut", which
> deletes the current text in the clipboard.
>
> 12. When copying from LyX to an external program (even another LyX instance),
> all formatting is lost (even paragraph breaks).
hmm why don't inter-lyx copies work properly ? just no one ever implemented it ?
> 13. If you have edited and then undo all changes, then the "Changed" status is
> not reset.
this seems a bit of a silly bug. is it worth mentioning it at all ?
> 14. If you have a margin note in itemize text and the first paragraph of the
> margin note is also itemize text it is possible to "depth-increment" and make
> the first itemize paragraph in the margin note deeper on-screen even though
> LaTeX doesn't permit this (and ignores this).
depth-increment just gets ignored in 1.2.0
> 15. A table which is larger than the screen manages to go outside the red lines
> drawn by a table float. Same goes for figures. A similar thing can happen with
> large mathematical equations. Resize your LyX window.
hmm
> 16. It is not possible to include footnotes in tables.
actually it is, but does lyx handle the necessary stuff for it ?
> 17. The numbering policy of LyX does not exactly match what LaTeX does for
> sections: for example, LyX resets subsection and subsubsection counters at a
> new section, while LaTeX does not reset the subsubsection counter. As a
> workaround, you can add \setcounter{subsubsection}{0}, marked as TeX, just
> after the section heading.
still true are recently discussed
> 18. LyX is not able to render correctly Paragraph and SubParagraph headings
> which, in standard LaTeX classes, are just placed at the start of the following
> paragraph. This can be confusing.
still true
> 19. LyX sometimes gets caught by TeX fonts ligatures: for example, in the
> sentence "He said 'Hello!'", the single and double closing quotes come out
> inverted (just try to preview this paragraph). The only solution is to write it
> as "He said 'Hello!'\textcompwordmark", which is admittedly not very nice.
>
> 20. When going into math text mode (which results in \mathrm{} in the LaTeX
> output) it is impossible to enter punctuation, as this is always put back into
> math mode.
not sure what this means.
> 21. When entering a multi-line equation, and the beginning of the second (or
> following) line begins with a "[" character, LaTeX sometimes gets confused. To
> avoid problems, it is necessary to add {} in TeX mode just before the bracket,
> as in the following example:x(t) & = & 1\nonumber \\ {}[x(t)+1] & = & 2
>
> The same applies for "*" at the beginning of an equation.
>
> 22. If a LaTeX command is partially bold, it doesn't generate correct LaTeX
> commands. LaTeX commands written using the LaTeX layout or the LaTeX font state
> should always use the standard font (this means no font changing commands
> should be allowed). Don't use font changing commands when you are in LaTeX
> mode.
here you are Lars some ammo for you :)
> 23. If you change font in a special word (like in "LaTeX"), the whole word will
> have the font of the first character in dvi output. This can be solved by using
> for example "L{}aTeX", thus disabling the automatic translation to the macro
> \LaTeX.
>
> 24. In a LyX-Code environment, you can't have an empty line. You'll have to
> type a single space to make it work.
>
> 25. In LyX-Code and in paragraphs written completely using the typewriter font,
> all spaces are protected so that LaTeX isn't able to perform correct formatting
> of the text. You'll have to insert linebreaks manually.
>
> 26. For default paragraphs, the option "no indent" works as expected. However,
> if you set the type of the paragraph to "description", the behaviour of "no
> indent" reverts, i.e. paragraph that should not be indented become indented and
> vice versa. [Comment: this is a LaTeX problem, where \noindent should not be
> used in lists; a good fix for this is not known yet]
>
> 27. It is possible to use the subfigure style to get two small figures
> (side-by-side), each with a caption and label, and then a common caption and
> label for the entire figure. LyX currently seems to support this in the pop-up
> menu for an eps figure. However, I am unable to successfully add labels to each
> of the subfigures. If I insert a label next to each subfigure, the labels
> appear fine and can be cross-referenced in the usual manner. However, the
> actual output (dvi or ps) does not distinguish between the two labels and any
> cross-reference gets the same number. You have to use plain old raw LaTeX mode
> and do this by hand.
>
> 28. Document that includes others: if LaTeX reports an error during the
> execution of LaTeX on a sub-document as a chain reaction of executing LaTeX on
> a higher level document, LyX places the error window on the correct position of
> the higher level doc, not of the lower one. There might be some spurious
> document corruption effects related to this. Be careful with raw LaTeX in
> sub-documents.
>
> 29. The pop-up browsers in the Preferences and Document Layout dialogs
> (Edit->Preferences->Usage->Language->Default language and
> Layout->Document->Document->Class respectively) will pop up in the wrong
> position on the display if the dialog is moved and the browser's tab folder is
> visible. This is the only only example so far discovered of a bug described in
> the xforms documentation as "A nested tabfolder might not work correctly at the
> moment".
I guess this one is xforms version specific, I couldn't reproduce (angus didn't you
add this reasonably recently ?)
