Wilson, Sandy schrieb:

I'm a veteran LaTeX user along with a few others who are trying to wean
other colleagues away from

Word and over to LaTeX.  Lyx was suggested as an alternative.  I've
tried importing working .tex files

to Lyx but it destroys some environments like verbatim, i.e. it removes
the linebreaks which are vital to

Can you please report this as bug in our database:
http://www.lyx.org/trac/wiki/BugTrackerHome
Please attach there an example TeX-file.

the working of the verbatim mode.  I read that Lyx supports the listings
package so I converted all my
code listings done with verbatim over to lstlisting environments but it
still destroys them on import.

The TeX import is not jet able to convert all LyX features from a TeX document. So instead of converting in the TeX-file, you have in this case convert them within LyX.

My .layout file for my non-standard .cls file includes all the standard
.inc files including stdinsets.  Is this a
fundamental design feature of Lyx that it can't deal with importing some
types of environments?

LyX's TeX import is not yet feature complete. It understands about 80% off all LyX features, but not all and listings is an example for that. We are however working to raise the percentage. But the TeX import doesn't lose any information: for things it cannot convert, it imports it to the LyX file as plain TeX, so that the PDF compiled out of the LyX file will look the same as if you would have compiled the PDF out of the TeX-file. if this is not the case, please help us to fix that by reporting these issues to our bugtracker.

Is there something I am missing in my .layout file that would import
them properly?  Is there a way of
scripting the import to put listings in what seems to be called an ERT?
What I'm trying to develop here is a way of
sharing the same .tex file between LaTeX users and Lyx users without it
getting corrupted in the import/export.

Collaborating between LyX ans TeX-users should be possible. The problem that will most probably arise is that plain TeX-users don't like the TeX-code created by LyX. But except from that my personal experience is that collaboration is possible.

If this is a fundamentally undoable operation, does anyone have any
suggestions for alternatives like
Texnicenter, Winshell, or TexWork that can do this.  Scientific Word is
probably out of the running due
to its high cost.  Any help would be appreciated.

TeXnicenter and friends are text editors optimized for TeX while LyX follows a completely different approach:
http://en.wikipedia.org/wiki/Wysiwym
Therefore LyX has its own fileformat (that will btw. the next time be transformed to XML).

regards Uwe

Reply via email to