Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
 Hello,
 a svg graphic can apparently be imported into a Lyx document. However, 
 it seems it is converted into bitmap if exported eg by pdflatex. Is that 
 true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: svg graphic import in Lyx

[Benedict Holland]

I strongly encourage you to turn the SVG into a PS, EPS, or PDF file. I
think somewhere is the documentation is states that for SVG to correctly
work within the document is requires inkscape. Not at all a problem,
inkscape is one of the best vector editors out there but it is required as
Guenter stated.

~Ben


On Sun, Jul 13, 2014 at 6:00 AM, Guenter Milde mi...@users.sf.net wrote:

 On 2014-07-12, Wolfgang Engelmann wrote:
  Hello,
  a svg graphic can apparently be imported into a Lyx document. However,
  it seems it is converted into bitmap if exported eg by pdflatex. Is that
  true?

 This depends on the installed converters. With e.g. inkscape installed, it
 is converted to pdf. Bitmap is the fallback.

 You may have a look at the configuration log.
 More detail about SVG images in LyX should be available in the wiki.

 Günter

Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
 Hello,
 a svg graphic can apparently be imported into a Lyx document. However, 
 it seems it is converted into bitmap if exported eg by pdflatex. Is that 
 true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: svg graphic import in Lyx

[Benedict Holland]

I strongly encourage you to turn the SVG into a PS, EPS, or PDF file. I
think somewhere is the documentation is states that for SVG to correctly
work within the document is requires inkscape. Not at all a problem,
inkscape is one of the best vector editors out there but it is required as
Guenter stated.

~Ben


On Sun, Jul 13, 2014 at 6:00 AM, Guenter Milde mi...@users.sf.net wrote:

 On 2014-07-12, Wolfgang Engelmann wrote:
  Hello,
  a svg graphic can apparently be imported into a Lyx document. However,
  it seems it is converted into bitmap if exported eg by pdflatex. Is that
  true?

 This depends on the installed converters. With e.g. inkscape installed, it
 is converted to pdf. Bitmap is the fallback.

 You may have a look at the configuration log.
 More detail about SVG images in LyX should be available in the wiki.

 Günter

Re: svg graphic import in Lyx

[Guenter Milde]

On 2014-07-12, Wolfgang Engelmann wrote:
> Hello,
> a svg graphic can apparently be imported into a Lyx document. However, 
> it seems it is converted into bitmap if exported eg by pdflatex. Is that 
> true?

This depends on the installed converters. With e.g. inkscape installed, it
is converted to pdf. Bitmap is the fallback.

You may have a look at the configuration log.
More detail about SVG images in LyX should be available in the wiki.

Günter

Re: svg graphic import in Lyx

[Benedict Holland]

I strongly encourage you to turn the SVG into a PS, EPS, or PDF file. I
think somewhere is the documentation is states that for SVG to correctly
work within the document is requires inkscape. Not at all a problem,
inkscape is one of the best vector editors out there but it is required as
Guenter stated.

~Ben


On Sun, Jul 13, 2014 at 6:00 AM, Guenter Milde  wrote:

> On 2014-07-12, Wolfgang Engelmann wrote:
> > Hello,
> > a svg graphic can apparently be imported into a Lyx document. However,
> > it seems it is converted into bitmap if exported eg by pdflatex. Is that
> > true?
>
> This depends on the installed converters. With e.g. inkscape installed, it
> is converted to pdf. Bitmap is the fallback.
>
> You may have a look at the configuration log.
> More detail about SVG images in LyX should be available in the wiki.
>
> Günter
>
>

svg graphic import in Lyx

[Wolfgang Engelmann]

Hello,
a svg graphic can apparently be imported into a Lyx document. However, 
it seems it is converted into bitmap if exported eg by pdflatex. Is that 
true?
In case, somebody is familiar with xcos/scilab, can the text of a model 
figure be set (externally?) in latex?
Are there plans to call up scilab in lyx similar to lillypond or other 
external programs?

Wolfgang

svg graphic import in Lyx

[Wolfgang Engelmann]

Hello,
a svg graphic can apparently be imported into a Lyx document. However, 
it seems it is converted into bitmap if exported eg by pdflatex. Is that 
true?
In case, somebody is familiar with xcos/scilab, can the text of a model 
figure be set (externally?) in latex?
Are there plans to call up scilab in lyx similar to lillypond or other 
external programs?

Wolfgang

svg graphic import in Lyx

[Wolfgang Engelmann]

Hello,
a svg graphic can apparently be imported into a Lyx document. However, 
it seems it is converted into bitmap if exported eg by pdflatex. Is that 
true?
In case, somebody is familiar with xcos/scilab, can the text of a model 
figure be set (externally?) in latex?
Are there plans to call up scilab in lyx similar to lillypond or other 
external programs?

Wolfgang

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Gour]

On Mon, 19 Mar 2012 16:15:58 + (UTC)
Guenter Milde mi...@users.sf.net wrote:

 I don't know AsciiDoc, but know that Sphinx is not only for Python
 projects but also supports C and more.

Yeah, I know about that, but mentioned it's not Python 'cause many
projects nowadays choose reST/Sphinx which is de-facto becoming standard
tool within Python community.

 However, I don't think it is necessary to use LyX at all. Rather I
 suggest tweaking in the Sphinx configuration file (and possibly using
 raw LaTeX in the source).

You're right. After playing some time with AsciiDoc -- PDF (via
dblatex), it seems that the end result is good-enough so that, in this
case, there is really no need for LyX.


Sincerely,
Gour


-- 
While contemplating the objects of the senses, a person 
develops attachment for them, and from such attachment lust 
develops, and from lust anger arises.

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810


signature.asc
Description: PGP signature

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Gour]

On Mon, 19 Mar 2012 16:15:58 + (UTC)
Guenter Milde mi...@users.sf.net wrote:

 I don't know AsciiDoc, but know that Sphinx is not only for Python
 projects but also supports C and more.

Yeah, I know about that, but mentioned it's not Python 'cause many
projects nowadays choose reST/Sphinx which is de-facto becoming standard
tool within Python community.

 However, I don't think it is necessary to use LyX at all. Rather I
 suggest tweaking in the Sphinx configuration file (and possibly using
 raw LaTeX in the source).

You're right. After playing some time with AsciiDoc -- PDF (via
dblatex), it seems that the end result is good-enough so that, in this
case, there is really no need for LyX.


Sincerely,
Gour


-- 
While contemplating the objects of the senses, a person 
develops attachment for them, and from such attachment lust 
develops, and from lust anger arises.

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810


signature.asc
Description: PGP signature

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Gour]

On Mon, 19 Mar 2012 16:15:58 + (UTC)
Guenter Milde  wrote:

> I don't know AsciiDoc, but know that Sphinx is not only for Python
> projects but also supports C and more.

Yeah, I know about that, but mentioned it's not Python 'cause many
projects nowadays choose reST/Sphinx which is de-facto becoming standard
tool within Python community.

> However, I don't think it is necessary to use LyX at all. Rather I
> suggest tweaking in the Sphinx configuration file (and possibly using
> raw LaTeX in the source).

You're right. After playing some time with AsciiDoc --> PDF (via
dblatex), it seems that the end result is good-enough so that, in this
case, there is really no need for LyX.


Sincerely,
Gour


-- 
While contemplating the objects of the senses, a person 
develops attachment for them, and from such attachment lust 
develops, and from lust anger arises.

http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810


signature.asc
Description: PGP signature

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Guenter Milde]

On 2012-03-19, Gour wrote:

 We're considering which markup to use for writing user's manual for a
 multi-platform desktop application.

 It should produce nice HTML output which can be invoked from within
 application as 'help' file and it should be possible to generate
 hight-quality PDF output by importing it into LyX for final tweaking.

 We're considering two systems:

 a) AsciiDoc and

 b) reStructuredText/Sphinx

 and wonder which one would you recommend as more suitable for importing
 into Lyx?

 Let me say that, in general, I'm not fan of DocBook as authoring format,
 but believe that one can escape fiddling with it when using AsciiDoc and
 another thing is that the project will not be coded in Python (we'll use
 D).

I don't know AsciiDoc, but know that Sphinx is not only for Python projects
but also supports C and more.

LyX currently does not import any of the two formats directly.
However, I don't think it is necessary to use LyX at all. Rather I suggest
tweaking in the Sphinx configuration file (and possibly using raw LaTeX in
the source).

Günter

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Guenter Milde]

On 2012-03-19, Gour wrote:

 We're considering which markup to use for writing user's manual for a
 multi-platform desktop application.

 It should produce nice HTML output which can be invoked from within
 application as 'help' file and it should be possible to generate
 hight-quality PDF output by importing it into LyX for final tweaking.

 We're considering two systems:

 a) AsciiDoc and

 b) reStructuredText/Sphinx

 and wonder which one would you recommend as more suitable for importing
 into Lyx?

 Let me say that, in general, I'm not fan of DocBook as authoring format,
 but believe that one can escape fiddling with it when using AsciiDoc and
 another thing is that the project will not be coded in Python (we'll use
 D).

I don't know AsciiDoc, but know that Sphinx is not only for Python projects
but also supports C and more.

LyX currently does not import any of the two formats directly.
However, I don't think it is necessary to use LyX at all. Rather I suggest
tweaking in the Sphinx configuration file (and possibly using raw LaTeX in
the source).

Günter

Re: AsciiDoc or reST/Sphinx more suitable for import into LyX

[Guenter Milde]

On 2012-03-19, Gour wrote:

> We're considering which markup to use for writing user's manual for a
> multi-platform desktop application.

> It should produce nice HTML output which can be invoked from within
> application as 'help' file and it should be possible to generate
> hight-quality PDF output by importing it into LyX for final tweaking.

> We're considering two systems:

> a) AsciiDoc and

> b) reStructuredText/Sphinx

> and wonder which one would you recommend as more suitable for importing
> into Lyx?

> Let me say that, in general, I'm not fan of DocBook as authoring format,
> but believe that one can escape fiddling with it when using AsciiDoc and
> another thing is that the project will not be coded in Python (we'll use
> D).

I don't know AsciiDoc, but know that Sphinx is not only for Python projects
but also supports C and more.

LyX currently does not import any of the two formats directly.
However, I don't think it is necessary to use LyX at all. Rather I suggest
tweaking in the Sphinx configuration file (and possibly using raw LaTeX in
the source).

Günter

Re: Import into LyX

[Murat Yildizoglu]

Hi Rob,

Very nice initiative, thank you very much! Even importing/exporting only docx 
would be wonderful for collaboration with Oird people. 

Do you also plan a clean import option with which even these local styles would 
be dropped in order to have a clean Lyx document with just the structure and 
the components (body text, references, figures, tables and math)?

Murat

--
Murat Yildizoglu
yi...@u-bordeaux4.fr

Le 2 févr. 2012 à 19:53, Rob Oakes lyx-de...@oak-tree.us a écrit :

 
 On Feb 2, 2012, at 11:26 AM, Les Denham wrote:
 
 Supporting Styles and Figures is a major achievement as far as I am
 concerned. I assume you don't do much in deciphering the fingerpainting
 favored by most Word users. Such crass formatting is probably best left
 as Standard in LyX anyway.
 
 Right, I'm not getting into the game where I'm going to try and support all 
 of the formatting combinations that Word users can come up with. But I do 
 intend to support styles in all of their incarnations: paragraph, character, 
 and otherwise. To make this possible, what I'll probably do is use the 
 book/article classes as a basis for the import and then generate placeholder 
 entries for other styles in the LyX local layout.
 
 That will prevent errors and problems and allow for you to convert to the 
 document class of your choice without problems. Once there, you remove the 
 placeholder entries, or define them further.
 
 Cheers,
 
 Rob

Re: Import into LyX

[Murat Yildizoglu]

Hi Rob,

Very nice initiative, thank you very much! Even importing/exporting only docx 
would be wonderful for collaboration with Oird people. 

Do you also plan a clean import option with which even these local styles would 
be dropped in order to have a clean Lyx document with just the structure and 
the components (body text, references, figures, tables and math)?

Murat

--
Murat Yildizoglu
yi...@u-bordeaux4.fr

Le 2 févr. 2012 à 19:53, Rob Oakes lyx-de...@oak-tree.us a écrit :

 
 On Feb 2, 2012, at 11:26 AM, Les Denham wrote:
 
 Supporting Styles and Figures is a major achievement as far as I am
 concerned. I assume you don't do much in deciphering the fingerpainting
 favored by most Word users. Such crass formatting is probably best left
 as Standard in LyX anyway.
 
 Right, I'm not getting into the game where I'm going to try and support all 
 of the formatting combinations that Word users can come up with. But I do 
 intend to support styles in all of their incarnations: paragraph, character, 
 and otherwise. To make this possible, what I'll probably do is use the 
 book/article classes as a basis for the import and then generate placeholder 
 entries for other styles in the LyX local layout.
 
 That will prevent errors and problems and allow for you to convert to the 
 document class of your choice without problems. Once there, you remove the 
 placeholder entries, or define them further.
 
 Cheers,
 
 Rob

Re: Import into LyX

[Murat Yildizoglu]

Hi Rob,

Very nice initiative, thank you very much! Even importing/exporting only docx 
would be wonderful for collaboration with Oird people. 

Do you also plan a clean import option with which even these local styles would 
be dropped in order to have a clean Lyx document with just the structure and 
the components (body text, references, figures, tables and math)?

Murat

--
Murat Yildizoglu
yi...@u-bordeaux4.fr

Le 2 févr. 2012 à 19:53, Rob Oakes  a écrit :

> 
> On Feb 2, 2012, at 11:26 AM, Les Denham wrote:
> 
>> Supporting Styles and Figures is a major achievement as far as I am
>> concerned. I assume you don't do much in deciphering the fingerpainting
>> favored by most Word users. Such crass formatting is probably best left
>> as Standard in LyX anyway.
> 
> Right, I'm not getting into the game where I'm going to try and support all 
> of the formatting combinations that Word users can come up with. But I do 
> intend to support styles in all of their incarnations: paragraph, character, 
> and otherwise. To make this possible, what I'll probably do is use the 
> book/article classes as a basis for the import and then generate placeholder 
> entries for other styles in the LyX local layout.
> 
> That will prevent errors and problems and allow for you to convert to the 
> document class of your choice without problems. Once there, you remove the 
> placeholder entries, or define them further.
> 
> Cheers,
> 
> Rob

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, stefano franchi wrote:

 Is this a tool that would prove useful to yourselves, your collaborators,
 and others?
 What features would you consider essential?

...

 Math, on the other hand, would not be very important. That is: I
 assume math would be finally produced by Latex, if camera-ready is
 required, or by the publishing house. A rough approximation would be
 sufficient (this from a Humanities perspective, of course).

As a physicist, I'd say math import is the most problematic part of the
Word-LyX interaction now and most needed.

(But you realize that even without math, there are users that would like to
see the tool.)

Günter

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 04:25, stefano franchi wrote:
 Hi Rob,

Hi Rob

I reply to Stefano's mail, as I agree with many points and don't want
to repeat them.
 
 first: great project! I constantly struggle with converting file
 to and from MS Word. I now use the Word--OOffice-- Latex-- Lyx
 Route, with the needed manual cleanup of Latex code and an
 additional cleanup of ERT code from LyX after LaTeX import. It is
 not fun. A project like yours would make LyX much, much easier to
 use in an academic environment.

Absolutely - I am working in biological sciences, and one can convince
some Journals to accept submission in LaTeX, but one can not convince
co-authors to use LyX 

 
 I am going to address your questions from the perspective of a 
 Humanities scholar. My observations may not be representative of
 the vast majority of current LyX/LaTeX users. On the other hand, a
 project like yours may potentially expand LyX's user base by an
 order of magnitude, in my opinion. So here we go:
 
 Is this a tool that would prove useful to yourselves, your
 collaborators, and others? What features would you consider
 essential?
 
 
 (Right now, styles based conversion looks pretty easy -- going
 from Heading 1 in Word to Chapter, for example. But I'm not sure
 how well it would convert maths. This is something I'll still
 need to look at, and may require writing an additional module.)
 
 
 As I said, it would be very important. In my experience, there are 
 three main scenarios where the tool would be precious:
 
 1. Conversion of personal legacy documents (all the stuff you
 wrote before you discovered LyX) 2. Collaboration with colleagues
 and students 3. Submission to journals (I don't know of a single
 journal in my field and related fields that accepts Latex. They all
 want MS Word.)

For me, scenarios 2 and 3 are the most important, and 2 would require
roundtrip conversion *with preservation of change tracking and
comments* would be *very* important! In addition, highlioghting should
also be maintained.

 
 
 1 and 3 are obviously one way (in opposite direction). 2 requires
 a Word--LyX roundtrip
 
 I think the most important scenarios are 2 and 3. And obviously 2 
 includes 3 and 1, so solving the collaboration scenario would be 
 optimal.
 
 Features:
 
 I think a good starting assumption is that final formatting will
 NOT be provided by MS Word. If you (or your team) has to produce 
 camera-ready output at the end of the collaborative work, LyX is a 
 much better tool. If you submit to a journal or a press, they will
 do the formatting.This means most Word-based typography can be 
 eliminated. I mean: margins, typefaces, font sizes, etc, with the 
 exception of different scripts, which are of course crucial
 (although with Unicode this problem should be solved now).  Only
 semantic formatting should be kept: emphasis/italics, sectioning
 info, lists, footnotes, etc. Plus all info about pictures and
 picture placement, tables (these are not trivial, I guess) and
 similar floats, and, mostly for books, indexing information.

Agreed here - Section - Heading 1 and so on, formating of individual
words (referred as semantic formatting) has to be maintained (italics
for species names *very* important.

 
 Preserving tracking info wold also be very useful.

See above.

 
 Cross-referencing would also be important (I have no idea how Word 
 does it, if at all).

Agreed.

 
 Math, on the other hand, would not be very important. That is: I 
 assume math would be finally produced by Latex, if camera-ready is 
 required, or by the publishing house. A rough approximation would
 be sufficient (this from a Humanities perspective, of course).

Also agreed - could be to image, from whatever source, and the
original one could be maintained in a special comment field behind, so
that on re-import this could be used? In Word, the LaTeX code could
even be edited.

 
 References would be very very important.

Essential I would say.
Problem might be to maintain BiBeX.

 
 What is the best tool to look at for guidance in creating a new
 script for word2lyx? tex2lyx?
 
 I would look at Word2Tex, which is proprietary, however. In
 general, though, most existing tools try hard to preserve the look
 of a document instead of following the approach I recommend,
 thereby getting into all sort of complications. There was a very
 useful tool for Framemaker -- LyX conversion that stuck to the
 semantic-only approach and worked pretty well (I was a Framemaker
 user before moving to LyX). It was very simple and I believe it is
 still available: http://pages.cs.brandeis.edu/~pablo/mif2lyx. It is
 a Perl script.
 
 
 Does the script need to support special cases, such as importing
 Word track changes?
 
 See above
 
 Just how important do you consider round-tripping a document,
 e.g., going from LyX to Word and back to LyX.

Very imortant - see above.

 
 Yes!
 
 Is there anyone who might

Re: Import into LyX

[Richard Heck]

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math 
to import somewhat well. That seems to be the biggest problem with 
most ways of converting doc to lyx. I understand it's very difficult, 
but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export Ultra-clean LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard

Re: Import into LyX

[UD]

IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.
EK

On 02/02/2012 10:55 AM, Richard Heck wrote:

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the 
math to import somewhat well. That seems to be the biggest problem 
with most ways of converting doc to lyx. I understand it's very 
difficult, but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export Ultra-clean LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard



--
Ehud Kaplan, Ph.D.
Jules and Doris Stein /Research to Prevent Blindness/ Professor
*Director*, The laboratory of Visual  Computational Neuroscience
*Director*, Center for Excellence in Computational  Systems Neuroscience
/Friedman Brain Institute/
Departments of Neuroscience, Ophthalmology, Structural  Chemical Biology,
The Mount Sinai School of Medicine
One Gustave Levy Place,
NY, NY, 10029

Re: Import into LyX

[David L. Johnson]

On 02/02/2012 11:04 AM, UD wrote:
IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.


Unfortunately, there are math-heavy documents that are produced using 
Word.  And not only is it difficult to translate such things into LyX or 
even LaTeX, they also don't load into Abiword or Open Office.  I 
actually am a co-author of a math paper that I could not read except 
when my collaborator printed it out for me, since he only used Word -- 
and he is a prolific writer, having written at least 4 advanced 
mathematical texts, all of which I am sure the publishers had to typeset 
from scratch into LaTeX in order to publish.  But I suspect that Word 
math translation will be a very difficult task which in the end will be 
pointless, anyway, since I am sure MS will continually change the 
encoding to prevent precisely this procedure.


--

David L. Johnson

A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines.
--Ralph Waldo Emerson

Re: Import into LyX

[Les Denham]

On Wed, 01 Feb 2012 12:59:33 -0700
Rob Oakes rob.oa...@oak-tree.us wrote:

 Any thoughts would be greatly appreciated.

One thing you do not mention is handling figures. The documents I work
with tend to be very heavily illustrated, and I like LyX because it
handles figures so much better than Word that there is no comparison.
But most of my collaborators refuse to consider anything but Word, and
hand me their contributions -- replete with figures on every page -- in
the form of a .docx file which is so messed up LibreOffice renders it
in a barely recognizable form. I usually end up asking for a PDF file,
and I go through it copying text from it and pasting it into LyX, and
using Acrobat Reader's snapshot tool to get the figures into Gimp.

A tool which could import figure-heavy Word documents into LyX would be
wonderful. A tool which would allow export of such documents into Word
would be even more wonderful (and also a miracle). The client for a
project currently near completion would like the final report (a 250
page document with over 200 figures, an index, and a bibtex
bibliography) in Word format as well as in PDF format and paper. My
current plan for that is to export the LyX to HTML and try to import it
into LibreOffice, but I'm not very hopeful about getting a useful
result.

Les

Re: Import into LyX

[Liviu Andronic]

Hello Rob
To echo others, it's great that you'd like to work on this.


On Wed, Feb 1, 2012 at 8:59 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 What features would you consider essential?

 (Right now, styles based conversion looks pretty easy -- going from Heading
 1 in Word to Chapter, for example. But I'm not sure how well it would
 convert maths. This is something I'll still need to look at, and may require
 writing an additional module.)

Reasonably fussless import of .doc in LyX, and reasonably fussless
export from LyX to .doc.


 Does the script need to support special cases, such as importing Word track
 changes?

Although I do appreciate others' arguments for having this, I would
believe that it's more of a perk. If your tool can simply translate
from Word to LyX, and vice-versa (I'm not talking of 'round-trip'),
the it would already be a great achievement. Accepting track changes
can be done in Word (and LibreOffice, I assume).


 Just how important do you consider round-tripping a document, e.g., going
 from LyX to Word and back to LyX.

I'm afraid this is more like chasing a wild goose. If LyX has a hard
time to round-trip to LaTeX, as it currently is more or less, then I'm
sceptical that round-trips to Word can be more reliable. It would be
great, however, to be able to reasonably import .doc in LyX, and
reasonably export from LyX to .doc. Reliable round-tripping should be
more of a secondary goal.

Regards
Liviu

Re: Import into LyX

[Rob Oakes]

Thank you everyone for the comments so far. I really appreciate hearing from 
others as it helps me to build out a more detailed use-case. In addition to the 
earlier questions, I have one more:

How important is support of .doc?

I know that it is the standard upon which the publishing industry is built, but 
… It's a real pain to parse. In contrast, docx (the default file format in Word 
2007 and 2010) is very parse. It's basically an XML document in a zipped folder 
with assets.

I've already got a working prototype that can take a very simple LyX document 
and converts it to docx. Here's what supported:

1.) Syles
2.) Images/Figures

Expanding this prototype is pretty easy. Trying to support doc is hard 
(painfully hard). There are pretty good import filters for OpenOffice and 
AbiWord for docx. docx is supported in Microsoft Word 2007 and 2010, and users 
of 2003 can download a plugin which is capable of reading it.

If I go ahead with support for docx, I think I can write a full featured 
import/export plugin, including:

1.) Bibliographies using Word's native format and (maybe) Endnote (I've found a 
python library that can parse BibTeX and building export for these two formats 
is do-able)
2.) Cross-references (I still need to figure out how this is done in Word, but 
so-far, the docx standard is pretty easy to follow)
3.) Comments and Change Tracking

How to deal with maths is still up in the air. LyX offers the ability to 
typeset nearly anything mathematical, which means there's a very large set of 
markup to support. Exporting to MathML might be one option, but that would 
require Word users to install a plugin. Exporting to Office Math Language (the 
new math language in Office 2007 and 2010) is another, but proprietary. 
Exporting to MathType is a third, which is both proprietary and requires that 
users install an add-in (which they have to pay for). I'm not particularly 
thrilled about any of the above. I'll continue to research and report what I 
find.

In the meantime, hearing about what features should be supported would be very 
nice. Hearing your opinions about doc support (versus only docx support) would 
also be very helpful.

Cheers,

Rob

Re: Import into LyX

[Les Denham]

On Thu, 2 Feb 2012 10:50:05 -0700
Rob Oakes rob.oa...@oak-tree.us wrote:

 In the meantime, hearing about what features should be supported
 would be very nice. Hearing your opinions about doc support (versus
 only docx support) would also be very helpful.

I would be quite happy with only .docx support. As time goes by more
and more of the people who insist on sending me Word documents get new
versions of Word which default to that format. For the .doc format
documents I can always use LibreOffice to convert to .docx.

Supporting Styles and Figures is a major achievement as far as I am
concerned. I assume you don't do much in deciphering the fingerpainting
favored by most Word users. Such crass formatting is probably best left
as Standard in LyX anyway.

Les

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 very nice. Hearing your opinions about doc support (versus only docx
 support) would also be very helpful.

If .docx-only support simplifies your task and helps ensure that your
tool would support a good deal of functionality, then I'm all for it.
Support for .doc can be worked around, not least by resaving the
document in LibreOffice.

Liviu

Re: Import into LyX

[stefano franchi]

On Thu, Feb 2, 2012 at 12:27 PM, Liviu Andronic landronim...@gmail.com wrote:
 On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 very nice. Hearing your opinions about doc support (versus only docx
 support) would also be very helpful.

 If .docx-only support simplifies your task and helps ensure that your
 tool would support a good deal of functionality, then I'm all for it.
 Support for .doc can be worked around, not least by resaving the
 document in LibreOffice.


Absolutely. Go for docx. Converting between .doc and .docx is
relatively painless.


Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 19:27, Liviu Andronic wrote:
 On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us
 wrote:
 very nice. Hearing your opinions about doc support (versus only
 docx support) would also be very helpful.
 
 If .docx-only support simplifies your task and helps ensure that
 your tool would support a good deal of functionality, then I'm all
 for it. Support for .doc can be worked around, not least by
 resaving the document in LibreOffice.

+1

Rainer

 
 Liviu


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8q23YACgkQoYgNqgF2egoqZgCeODGYVqc4jZaEvQUMyvnaVNXX
8awAnRjij2X9+qCDqatbz7BiAxYcukh0
=HXNt
-END PGP SIGNATURE-

Re: Import into LyX

[Rob Oakes]

On Feb 2, 2012, at 11:26 AM, Les Denham wrote:

 Supporting Styles and Figures is a major achievement as far as I am
 concerned. I assume you don't do much in deciphering the fingerpainting
 favored by most Word users. Such crass formatting is probably best left
 as Standard in LyX anyway.

Right, I'm not getting into the game where I'm going to try and support all of 
the formatting combinations that Word users can come up with. But I do intend 
to support styles in all of their incarnations: paragraph, character, and 
otherwise. To make this possible, what I'll probably do is use the book/article 
classes as a basis for the import and then generate placeholder entries for 
other styles in the LyX local layout.

That will prevent errors and problems and allow for you to convert to the 
document class of your choice without problems. Once there, you remove the 
placeholder entries, or define them further.

Cheers,

Rob

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, Rob Oakes wrote:

 How important is support of .doc?

IMO, you should concentrate on docx - lyx. One tool for one task.
If it turns out that parts can be reused for doc-lyx later, fine.

How good/bad is the doc - docx conversion in OpenOffice/LibreOffice?

 If I go ahead with support for docx, I think I can write a full
 featured import/export plugin, including:

Good news.


 How to deal with maths is still up in the air. LyX offers the ability
 to typeset nearly anything mathematical, which means there's a very
 large set of markup to support. Exporting to MathML might be one
 option, but that would require Word users to install a plugin.

MathML is already implemented in LyX, so this would be a start.

A converter between (La)TeX math and the `Unicode Nearly Plain Text
Encoding of Mathematics` (http://www.unicode.org/notes/tn28/) would be a
much valued tool also outside of LyX.


Thanks,

Günter

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 9:19 PM, Guenter Milde mi...@users.sf.net wrote:
 How good/bad is the doc - docx conversion in OpenOffice/LibreOffice?

My experience with OpenOffice and .docx isn't very good: I always had
the feeling that .doc support was better than .docx. The issues
concerned mainly disappearing formatting.

Liviu

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, stefano franchi wrote:

 Is this a tool that would prove useful to yourselves, your collaborators,
 and others?
 What features would you consider essential?

...

 Math, on the other hand, would not be very important. That is: I
 assume math would be finally produced by Latex, if camera-ready is
 required, or by the publishing house. A rough approximation would be
 sufficient (this from a Humanities perspective, of course).

As a physicist, I'd say math import is the most problematic part of the
Word-LyX interaction now and most needed.

(But you realize that even without math, there are users that would like to
see the tool.)

Günter

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 04:25, stefano franchi wrote:
 Hi Rob,

Hi Rob

I reply to Stefano's mail, as I agree with many points and don't want
to repeat them.
 
 first: great project! I constantly struggle with converting file
 to and from MS Word. I now use the Word--OOffice-- Latex-- Lyx
 Route, with the needed manual cleanup of Latex code and an
 additional cleanup of ERT code from LyX after LaTeX import. It is
 not fun. A project like yours would make LyX much, much easier to
 use in an academic environment.

Absolutely - I am working in biological sciences, and one can convince
some Journals to accept submission in LaTeX, but one can not convince
co-authors to use LyX 

 
 I am going to address your questions from the perspective of a 
 Humanities scholar. My observations may not be representative of
 the vast majority of current LyX/LaTeX users. On the other hand, a
 project like yours may potentially expand LyX's user base by an
 order of magnitude, in my opinion. So here we go:
 
 Is this a tool that would prove useful to yourselves, your
 collaborators, and others? What features would you consider
 essential?
 
 
 (Right now, styles based conversion looks pretty easy -- going
 from Heading 1 in Word to Chapter, for example. But I'm not sure
 how well it would convert maths. This is something I'll still
 need to look at, and may require writing an additional module.)
 
 
 As I said, it would be very important. In my experience, there are 
 three main scenarios where the tool would be precious:
 
 1. Conversion of personal legacy documents (all the stuff you
 wrote before you discovered LyX) 2. Collaboration with colleagues
 and students 3. Submission to journals (I don't know of a single
 journal in my field and related fields that accepts Latex. They all
 want MS Word.)

For me, scenarios 2 and 3 are the most important, and 2 would require
roundtrip conversion *with preservation of change tracking and
comments* would be *very* important! In addition, highlioghting should
also be maintained.

 
 
 1 and 3 are obviously one way (in opposite direction). 2 requires
 a Word--LyX roundtrip
 
 I think the most important scenarios are 2 and 3. And obviously 2 
 includes 3 and 1, so solving the collaboration scenario would be 
 optimal.
 
 Features:
 
 I think a good starting assumption is that final formatting will
 NOT be provided by MS Word. If you (or your team) has to produce 
 camera-ready output at the end of the collaborative work, LyX is a 
 much better tool. If you submit to a journal or a press, they will
 do the formatting.This means most Word-based typography can be 
 eliminated. I mean: margins, typefaces, font sizes, etc, with the 
 exception of different scripts, which are of course crucial
 (although with Unicode this problem should be solved now).  Only
 semantic formatting should be kept: emphasis/italics, sectioning
 info, lists, footnotes, etc. Plus all info about pictures and
 picture placement, tables (these are not trivial, I guess) and
 similar floats, and, mostly for books, indexing information.

Agreed here - Section - Heading 1 and so on, formating of individual
words (referred as semantic formatting) has to be maintained (italics
for species names *very* important.

 
 Preserving tracking info wold also be very useful.

See above.

 
 Cross-referencing would also be important (I have no idea how Word 
 does it, if at all).

Agreed.

 
 Math, on the other hand, would not be very important. That is: I 
 assume math would be finally produced by Latex, if camera-ready is 
 required, or by the publishing house. A rough approximation would
 be sufficient (this from a Humanities perspective, of course).

Also agreed - could be to image, from whatever source, and the
original one could be maintained in a special comment field behind, so
that on re-import this could be used? In Word, the LaTeX code could
even be edited.

 
 References would be very very important.

Essential I would say.
Problem might be to maintain BiBeX.

 
 What is the best tool to look at for guidance in creating a new
 script for word2lyx? tex2lyx?
 
 I would look at Word2Tex, which is proprietary, however. In
 general, though, most existing tools try hard to preserve the look
 of a document instead of following the approach I recommend,
 thereby getting into all sort of complications. There was a very
 useful tool for Framemaker -- LyX conversion that stuck to the
 semantic-only approach and worked pretty well (I was a Framemaker
 user before moving to LyX). It was very simple and I believe it is
 still available: http://pages.cs.brandeis.edu/~pablo/mif2lyx. It is
 a Perl script.
 
 
 Does the script need to support special cases, such as importing
 Word track changes?
 
 See above
 
 Just how important do you consider round-tripping a document,
 e.g., going from LyX to Word and back to LyX.

Very imortant - see above.

 
 Yes!
 
 Is there anyone who might

Re: Import into LyX

[Richard Heck]

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math 
to import somewhat well. That seems to be the biggest problem with 
most ways of converting doc to lyx. I understand it's very difficult, 
but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export Ultra-clean LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard

Re: Import into LyX

[UD]

IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.
EK

On 02/02/2012 10:55 AM, Richard Heck wrote:

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the 
math to import somewhat well. That seems to be the biggest problem 
with most ways of converting doc to lyx. I understand it's very 
difficult, but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export Ultra-clean LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard



--
Ehud Kaplan, Ph.D.
Jules and Doris Stein /Research to Prevent Blindness/ Professor
*Director*, The laboratory of Visual  Computational Neuroscience
*Director*, Center for Excellence in Computational  Systems Neuroscience
/Friedman Brain Institute/
Departments of Neuroscience, Ophthalmology, Structural  Chemical Biology,
The Mount Sinai School of Medicine
One Gustave Levy Place,
NY, NY, 10029

Re: Import into LyX

[David L. Johnson]

On 02/02/2012 11:04 AM, UD wrote:
IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.


Unfortunately, there are math-heavy documents that are produced using 
Word.  And not only is it difficult to translate such things into LyX or 
even LaTeX, they also don't load into Abiword or Open Office.  I 
actually am a co-author of a math paper that I could not read except 
when my collaborator printed it out for me, since he only used Word -- 
and he is a prolific writer, having written at least 4 advanced 
mathematical texts, all of which I am sure the publishers had to typeset 
from scratch into LaTeX in order to publish.  But I suspect that Word 
math translation will be a very difficult task which in the end will be 
pointless, anyway, since I am sure MS will continually change the 
encoding to prevent precisely this procedure.


--

David L. Johnson

A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines.
--Ralph Waldo Emerson

Re: Import into LyX

[Les Denham]

On Wed, 01 Feb 2012 12:59:33 -0700
Rob Oakes rob.oa...@oak-tree.us wrote:

 Any thoughts would be greatly appreciated.

One thing you do not mention is handling figures. The documents I work
with tend to be very heavily illustrated, and I like LyX because it
handles figures so much better than Word that there is no comparison.
But most of my collaborators refuse to consider anything but Word, and
hand me their contributions -- replete with figures on every page -- in
the form of a .docx file which is so messed up LibreOffice renders it
in a barely recognizable form. I usually end up asking for a PDF file,
and I go through it copying text from it and pasting it into LyX, and
using Acrobat Reader's snapshot tool to get the figures into Gimp.

A tool which could import figure-heavy Word documents into LyX would be
wonderful. A tool which would allow export of such documents into Word
would be even more wonderful (and also a miracle). The client for a
project currently near completion would like the final report (a 250
page document with over 200 figures, an index, and a bibtex
bibliography) in Word format as well as in PDF format and paper. My
current plan for that is to export the LyX to HTML and try to import it
into LibreOffice, but I'm not very hopeful about getting a useful
result.

Les

Re: Import into LyX

[Liviu Andronic]

Hello Rob
To echo others, it's great that you'd like to work on this.


On Wed, Feb 1, 2012 at 8:59 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 What features would you consider essential?

 (Right now, styles based conversion looks pretty easy -- going from Heading
 1 in Word to Chapter, for example. But I'm not sure how well it would
 convert maths. This is something I'll still need to look at, and may require
 writing an additional module.)

Reasonably fussless import of .doc in LyX, and reasonably fussless
export from LyX to .doc.


 Does the script need to support special cases, such as importing Word track
 changes?

Although I do appreciate others' arguments for having this, I would
believe that it's more of a perk. If your tool can simply translate
from Word to LyX, and vice-versa (I'm not talking of 'round-trip'),
the it would already be a great achievement. Accepting track changes
can be done in Word (and LibreOffice, I assume).


 Just how important do you consider round-tripping a document, e.g., going
 from LyX to Word and back to LyX.

I'm afraid this is more like chasing a wild goose. If LyX has a hard
time to round-trip to LaTeX, as it currently is more or less, then I'm
sceptical that round-trips to Word can be more reliable. It would be
great, however, to be able to reasonably import .doc in LyX, and
reasonably export from LyX to .doc. Reliable round-tripping should be
more of a secondary goal.

Regards
Liviu

Re: Import into LyX

[Rob Oakes]

Thank you everyone for the comments so far. I really appreciate hearing from 
others as it helps me to build out a more detailed use-case. In addition to the 
earlier questions, I have one more:

How important is support of .doc?

I know that it is the standard upon which the publishing industry is built, but 
… It's a real pain to parse. In contrast, docx (the default file format in Word 
2007 and 2010) is very parse. It's basically an XML document in a zipped folder 
with assets.

I've already got a working prototype that can take a very simple LyX document 
and converts it to docx. Here's what supported:

1.) Syles
2.) Images/Figures

Expanding this prototype is pretty easy. Trying to support doc is hard 
(painfully hard). There are pretty good import filters for OpenOffice and 
AbiWord for docx. docx is supported in Microsoft Word 2007 and 2010, and users 
of 2003 can download a plugin which is capable of reading it.

If I go ahead with support for docx, I think I can write a full featured 
import/export plugin, including:

1.) Bibliographies using Word's native format and (maybe) Endnote (I've found a 
python library that can parse BibTeX and building export for these two formats 
is do-able)
2.) Cross-references (I still need to figure out how this is done in Word, but 
so-far, the docx standard is pretty easy to follow)
3.) Comments and Change Tracking

How to deal with maths is still up in the air. LyX offers the ability to 
typeset nearly anything mathematical, which means there's a very large set of 
markup to support. Exporting to MathML might be one option, but that would 
require Word users to install a plugin. Exporting to Office Math Language (the 
new math language in Office 2007 and 2010) is another, but proprietary. 
Exporting to MathType is a third, which is both proprietary and requires that 
users install an add-in (which they have to pay for). I'm not particularly 
thrilled about any of the above. I'll continue to research and report what I 
find.

In the meantime, hearing about what features should be supported would be very 
nice. Hearing your opinions about doc support (versus only docx support) would 
also be very helpful.

Cheers,

Rob

Re: Import into LyX

[Les Denham]

On Thu, 2 Feb 2012 10:50:05 -0700
Rob Oakes rob.oa...@oak-tree.us wrote:

 In the meantime, hearing about what features should be supported
 would be very nice. Hearing your opinions about doc support (versus
 only docx support) would also be very helpful.

I would be quite happy with only .docx support. As time goes by more
and more of the people who insist on sending me Word documents get new
versions of Word which default to that format. For the .doc format
documents I can always use LibreOffice to convert to .docx.

Supporting Styles and Figures is a major achievement as far as I am
concerned. I assume you don't do much in deciphering the fingerpainting
favored by most Word users. Such crass formatting is probably best left
as Standard in LyX anyway.

Les

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 very nice. Hearing your opinions about doc support (versus only docx
 support) would also be very helpful.

If .docx-only support simplifies your task and helps ensure that your
tool would support a good deal of functionality, then I'm all for it.
Support for .doc can be worked around, not least by resaving the
document in LibreOffice.

Liviu

Re: Import into LyX

[stefano franchi]

On Thu, Feb 2, 2012 at 12:27 PM, Liviu Andronic landronim...@gmail.com wrote:
 On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us wrote:
 very nice. Hearing your opinions about doc support (versus only docx
 support) would also be very helpful.

 If .docx-only support simplifies your task and helps ensure that your
 tool would support a good deal of functionality, then I'm all for it.
 Support for .doc can be worked around, not least by resaving the
 document in LibreOffice.


Absolutely. Go for docx. Converting between .doc and .docx is
relatively painless.


Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 19:27, Liviu Andronic wrote:
 On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes rob.oa...@oak-tree.us
 wrote:
 very nice. Hearing your opinions about doc support (versus only
 docx support) would also be very helpful.
 
 If .docx-only support simplifies your task and helps ensure that
 your tool would support a good deal of functionality, then I'm all
 for it. Support for .doc can be worked around, not least by
 resaving the document in LibreOffice.

+1

Rainer

 
 Liviu


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8q23YACgkQoYgNqgF2egoqZgCeODGYVqc4jZaEvQUMyvnaVNXX
8awAnRjij2X9+qCDqatbz7BiAxYcukh0
=HXNt
-END PGP SIGNATURE-

Re: Import into LyX

[Rob Oakes]

On Feb 2, 2012, at 11:26 AM, Les Denham wrote:

 Supporting Styles and Figures is a major achievement as far as I am
 concerned. I assume you don't do much in deciphering the fingerpainting
 favored by most Word users. Such crass formatting is probably best left
 as Standard in LyX anyway.

Right, I'm not getting into the game where I'm going to try and support all of 
the formatting combinations that Word users can come up with. But I do intend 
to support styles in all of their incarnations: paragraph, character, and 
otherwise. To make this possible, what I'll probably do is use the book/article 
classes as a basis for the import and then generate placeholder entries for 
other styles in the LyX local layout.

That will prevent errors and problems and allow for you to convert to the 
document class of your choice without problems. Once there, you remove the 
placeholder entries, or define them further.

Cheers,

Rob

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, Rob Oakes wrote:

 How important is support of .doc?

IMO, you should concentrate on docx - lyx. One tool for one task.
If it turns out that parts can be reused for doc-lyx later, fine.

How good/bad is the doc - docx conversion in OpenOffice/LibreOffice?

 If I go ahead with support for docx, I think I can write a full
 featured import/export plugin, including:

Good news.


 How to deal with maths is still up in the air. LyX offers the ability
 to typeset nearly anything mathematical, which means there's a very
 large set of markup to support. Exporting to MathML might be one
 option, but that would require Word users to install a plugin.

MathML is already implemented in LyX, so this would be a start.

A converter between (La)TeX math and the `Unicode Nearly Plain Text
Encoding of Mathematics` (http://www.unicode.org/notes/tn28/) would be a
much valued tool also outside of LyX.


Thanks,

Günter

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 9:19 PM, Guenter Milde mi...@users.sf.net wrote:
 How good/bad is the doc - docx conversion in OpenOffice/LibreOffice?

My experience with OpenOffice and .docx isn't very good: I always had
the feeling that .doc support was better than .docx. The issues
concerned mainly disappearing formatting.

Liviu

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, stefano franchi wrote:

>> Is this a tool that would prove useful to yourselves, your collaborators,
>> and others?
>> What features would you consider essential?

...

> Math, on the other hand, would not be very important. That is: I
> assume math would be finally produced by Latex, if camera-ready is
> required, or by the publishing house. A rough approximation would be
> sufficient (this from a Humanities perspective, of course).

As a physicist, I'd say math import is the most problematic part of the
Word-LyX interaction now and most needed.

(But you realize that even without math, there are users that would like to
see the tool.)

Günter

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 04:25, stefano franchi wrote:
> Hi Rob,

Hi Rob

I reply to Stefano's mail, as I agree with many points and don't want
to repeat them.
> 
> first: great project! I constantly struggle with converting file
> to and from MS Word. I now use the Word-->OOffice--> Latex--> Lyx
> Route, with the needed manual cleanup of Latex code and an
> additional cleanup of ERT code from LyX after LaTeX import. It is
> not fun. A project like yours would make LyX much, much easier to
> use in an academic environment.

Absolutely - I am working in biological sciences, and one can convince
some Journals to accept submission in LaTeX, but one can not convince
co-authors to use LyX 

> 
> I am going to address your questions from the perspective of a 
> Humanities scholar. My observations may not be representative of
> the vast majority of current LyX/LaTeX users. On the other hand, a
> project like yours may potentially expand LyX's user base by an
> order of magnitude, in my opinion. So here we go:
> 
>> Is this a tool that would prove useful to yourselves, your
>> collaborators, and others? What features would you consider
>> essential?
> 
>> 
>> (Right now, styles based conversion looks pretty easy -- going
>> from Heading 1 in Word to Chapter, for example. But I'm not sure
>> how well it would convert maths. This is something I'll still
>> need to look at, and may require writing an additional module.)
>> 
> 
> As I said, it would be very important. In my experience, there are 
> three main scenarios where the tool would be precious:
> 
> 1. Conversion of personal legacy documents (all the stuff you
> wrote before you discovered LyX) 2. Collaboration with colleagues
> and students 3. Submission to journals (I don't know of a single
> journal in my field and related fields that accepts Latex. They all
> want MS Word.)

For me, scenarios 2 and 3 are the most important, and 2 would require
roundtrip conversion *with preservation of change tracking and
comments* would be *very* important! In addition, highlioghting should
also be maintained.

> 
> 
> 1 and 3 are obviously one way (in opposite direction). 2 requires
> a Word<-->LyX roundtrip
> 
> I think the most important scenarios are 2 and 3. And obviously 2 
> includes 3 and 1, so solving the collaboration scenario would be 
> optimal.
> 
> Features:
> 
> I think a good starting assumption is that final formatting will
> NOT be provided by MS Word. If you (or your team) has to produce 
> camera-ready output at the end of the collaborative work, LyX is a 
> much better tool. If you submit to a journal or a press, they will
> do the formatting.This means most Word-based typography can be 
> eliminated. I mean: margins, typefaces, font sizes, etc, with the 
> exception of different scripts, which are of course crucial
> (although with Unicode this problem should be solved now).  Only
> semantic formatting should be kept: emphasis/italics, sectioning
> info, lists, footnotes, etc. Plus all info about pictures and
> picture placement, tables (these are not trivial, I guess) and
> similar floats, and, mostly for books, indexing information.

Agreed here - Section <-> Heading 1 and so on, formating of individual
words (referred as semantic formatting) has to be maintained (italics
for species names *very* important.

> 
> Preserving tracking info wold also be very useful.

See above.

> 
> Cross-referencing would also be important (I have no idea how Word 
> does it, if at all).

Agreed.

> 
> Math, on the other hand, would not be very important. That is: I 
> assume math would be finally produced by Latex, if camera-ready is 
> required, or by the publishing house. A rough approximation would
> be sufficient (this from a Humanities perspective, of course).

Also agreed - could be to image, from whatever source, and the
original one could be maintained in a special comment field behind, so
that on re-import this could be used? In Word, the LaTeX code could
even be edited.

> 
> References would be very very important.

Essential I would say.
Problem might be to maintain BiBeX.

> 
>> What is the best tool to look at for guidance in creating a new
>> script for word2lyx? tex2lyx?
> 
> I would look at Word2Tex, which is proprietary, however. In
> general, though, most existing tools try hard to preserve the look
> of a document instead of following the approach I recommend,
> thereby getting into all sort of complications. There was a very
> useful tool for Framemaker <--> LyX conversion that stuck to the
> semantic-only approach and worked pretty well (I was a Framemaker
> user before moving to LyX). It was very simp

Re: Import into LyX

[Richard Heck]

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math 
to import somewhat well. That seems to be the biggest problem with 
most ways of converting doc to lyx. I understand it's very difficult, 
but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export "Ultra-clean" LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard

Re: Import into LyX

[UD]

IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.
EK

On 02/02/2012 10:55 AM, Richard Heck wrote:

On 02/01/2012 03:11 PM, Xu Wang wrote:

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the 
math to import somewhat well. That seems to be the biggest problem 
with most ways of converting doc to lyx. I understand it's very 
difficult, but I think it's also the most important.


As far as I remember, the main complaint about writer2latex has been 
that it produces ugly LaTeX. In the latest versions of LibreOffice, 
however, there is an option to export "Ultra-clean" LaTeX, which works 
pretty well. Of course, this relies upon Libre's importing Word's math 
well. So for math heavy documents, that seems a good way to go at the 
moment.


Richard



--
Ehud Kaplan, Ph.D.
Jules and Doris Stein /Research to Prevent Blindness/ Professor
*Director*, The laboratory of Visual & Computational Neuroscience
*Director*, Center for Excellence in Computational & Systems Neuroscience
/Friedman Brain Institute/
Departments of Neuroscience, Ophthalmology, Structural & Chemical Biology,
The Mount Sinai School of Medicine
One Gustave Levy Place,
NY, NY, 10029

Re: Import into LyX

[David L. Johnson]

On 02/02/2012 11:04 AM, UD wrote:
IMHO it is unlikely that math-heavy documents are produced by anything 
but Latex/Lyx.
I applaud the initiative to make MS-WORD/Lyx conversion easier.  I am 
sure it will have

many appreciative users.


Unfortunately, there are math-heavy documents that are produced using 
Word.  And not only is it difficult to translate such things into LyX or 
even LaTeX, they also don't load into Abiword or Open Office.  I 
actually am a co-author of a math paper that I could not read except 
when my collaborator printed it out for me, since he only used Word -- 
and he is a prolific writer, having written at least 4 advanced 
mathematical texts, all of which I am sure the publishers had to typeset 
from scratch into LaTeX in order to publish.  But I suspect that Word 
math translation will be a very difficult task which in the end will be 
pointless, anyway, since I am sure MS will continually change the 
encoding to prevent precisely this procedure.


--

David L. Johnson

"A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines."
--Ralph Waldo Emerson

Re: Import into LyX

[Les Denham]

On Wed, 01 Feb 2012 12:59:33 -0700
Rob Oakes  wrote:

> Any thoughts would be greatly appreciated.

One thing you do not mention is handling figures. The documents I work
with tend to be very heavily illustrated, and I like LyX because it
handles figures so much better than Word that there is no comparison.
But most of my collaborators refuse to consider anything but Word, and
hand me their contributions -- replete with figures on every page -- in
the form of a .docx file which is so messed up LibreOffice renders it
in a barely recognizable form. I usually end up asking for a PDF file,
and I go through it copying text from it and pasting it into LyX, and
using Acrobat Reader's snapshot tool to get the figures into Gimp.

A tool which could import figure-heavy Word documents into LyX would be
wonderful. A tool which would allow export of such documents into Word
would be even more wonderful (and also a miracle). The client for a
project currently near completion would like the final report (a 250
page document with over 200 figures, an index, and a bibtex
bibliography) in Word format as well as in PDF format and paper. My
current plan for that is to export the LyX to HTML and try to import it
into LibreOffice, but I'm not very hopeful about getting a useful
result.

Les

Re: Import into LyX

[Liviu Andronic]

Hello Rob
To echo others, it's great that you'd like to work on this.


On Wed, Feb 1, 2012 at 8:59 PM, Rob Oakes <rob.oa...@oak-tree.us> wrote:
> What features would you consider essential?
>
> (Right now, styles based conversion looks pretty easy -- going from Heading
> 1 in Word to Chapter, for example. But I'm not sure how well it would
> convert maths. This is something I'll still need to look at, and may require
> writing an additional module.)
>
Reasonably fussless import of .doc in LyX, and reasonably fussless
export from LyX to .doc.


> Does the script need to support special cases, such as importing Word "track
> changes"?
>
Although I do appreciate others' arguments for having this, I would
believe that it's more of a perk. If your tool can simply translate
from Word to LyX, and vice-versa (I'm not talking of 'round-trip'),
the it would already be a great achievement. Accepting track changes
can be done in Word (and LibreOffice, I assume).


> Just how important do you consider "round-tripping" a document, e.g., going
> from LyX to Word and back to LyX.
>
I'm afraid this is more like chasing a wild goose. If LyX has a hard
time to round-trip to LaTeX, as it currently is more or less, then I'm
sceptical that round-trips to Word can be more reliable. It would be
great, however, to be able to reasonably import .doc in LyX, and
reasonably export from LyX to .doc. Reliable round-tripping should be
more of a secondary goal.

Regards
Liviu

Re: Import into LyX

[Rob Oakes]

Thank you everyone for the comments so far. I really appreciate hearing from 
others as it helps me to build out a more detailed use-case. In addition to the 
earlier questions, I have one more:

How important is support of .doc?

I know that it is the standard upon which the publishing industry is built, but 
… It's a real pain to parse. In contrast, docx (the default file format in Word 
2007 and 2010) is very parse. It's basically an XML document in a zipped folder 
with assets.

I've already got a working prototype that can take a very simple LyX document 
and converts it to docx. Here's what supported:

1.) Syles
2.) Images/Figures

Expanding this prototype is pretty easy. Trying to support doc is hard 
(painfully hard). There are pretty good import filters for OpenOffice and 
AbiWord for docx. docx is supported in Microsoft Word 2007 and 2010, and users 
of 2003 can download a plugin which is capable of reading it.

If I go ahead with support for docx, I think I can write a full featured 
import/export plugin, including:

1.) Bibliographies using Word's native format and (maybe) Endnote (I've found a 
python library that can parse BibTeX and building export for these two formats 
is do-able)
2.) Cross-references (I still need to figure out how this is done in Word, but 
so-far, the docx standard is pretty easy to follow)
3.) Comments and Change Tracking

How to deal with maths is still up in the air. LyX offers the ability to 
typeset nearly anything mathematical, which means there's a very large set of 
markup to support. Exporting to MathML might be one option, but that would 
require Word users to install a plugin. Exporting to Office Math Language (the 
new math language in Office 2007 and 2010) is another, but proprietary. 
Exporting to MathType is a third, which is both proprietary and requires that 
users install an add-in (which they have to pay for). I'm not particularly 
thrilled about any of the above. I'll continue to research and report what I 
find.

In the meantime, hearing about what features should be supported would be very 
nice. Hearing your opinions about doc support (versus only docx support) would 
also be very helpful.

Cheers,

Rob

Re: Import into LyX

[Les Denham]

On Thu, 2 Feb 2012 10:50:05 -0700
Rob Oakes  wrote:

> In the meantime, hearing about what features should be supported
> would be very nice. Hearing your opinions about doc support (versus
> only docx support) would also be very helpful.

I would be quite happy with only .docx support. As time goes by more
and more of the people who insist on sending me Word documents get new
versions of Word which default to that format. For the .doc format
documents I can always use LibreOffice to convert to .docx.

Supporting Styles and Figures is a major achievement as far as I am
concerned. I assume you don't do much in deciphering the fingerpainting
favored by most Word users. Such crass formatting is probably best left
as Standard in LyX anyway.

Les

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes  wrote:
> very nice. Hearing your opinions about doc support (versus only docx
> support) would also be very helpful.
>
If .docx-only support simplifies your task and helps ensure that your
tool would support a good deal of functionality, then I'm all for it.
Support for .doc can be worked around, not least by resaving the
document in LibreOffice.

Liviu

Re: Import into LyX

[stefano franchi]

On Thu, Feb 2, 2012 at 12:27 PM, Liviu Andronic  wrote:
> On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes  wrote:
>> very nice. Hearing your opinions about doc support (versus only docx
>> support) would also be very helpful.
>>
> If .docx-only support simplifies your task and helps ensure that your
> tool would support a good deal of functionality, then I'm all for it.
> Support for .doc can be worked around, not least by resaving the
> document in LibreOffice.
>

Absolutely. Go for docx. Converting between .doc and .docx is
relatively painless.


Stefano



-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas A University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Re: Import into LyX

[Rainer M Krug]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/02/12 19:27, Liviu Andronic wrote:
> On Thu, Feb 2, 2012 at 6:50 PM, Rob Oakes 
> wrote:
>> very nice. Hearing your opinions about doc support (versus only
>> docx support) would also be very helpful.
>> 
> If .docx-only support simplifies your task and helps ensure that
> your tool would support a good deal of functionality, then I'm all
> for it. Support for .doc can be worked around, not least by
> resaving the document in LibreOffice.

+1

Rainer

> 
> Liviu


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8q23YACgkQoYgNqgF2egoqZgCeODGYVqc4jZaEvQUMyvnaVNXX
8awAnRjij2X9+qCDqatbz7BiAxYcukh0
=HXNt
-END PGP SIGNATURE-

Re: Import into LyX

[Rob Oakes]

On Feb 2, 2012, at 11:26 AM, Les Denham wrote:

> Supporting Styles and Figures is a major achievement as far as I am
> concerned. I assume you don't do much in deciphering the fingerpainting
> favored by most Word users. Such crass formatting is probably best left
> as Standard in LyX anyway.

Right, I'm not getting into the game where I'm going to try and support all of 
the formatting combinations that Word users can come up with. But I do intend 
to support styles in all of their incarnations: paragraph, character, and 
otherwise. To make this possible, what I'll probably do is use the book/article 
classes as a basis for the import and then generate placeholder entries for 
other styles in the LyX local layout.

That will prevent errors and problems and allow for you to convert to the 
document class of your choice without problems. Once there, you remove the 
placeholder entries, or define them further.

Cheers,

Rob

Re: Import into LyX

[Guenter Milde]

On 2012-02-02, Rob Oakes wrote:

> How important is support of .doc?

IMO, you should concentrate on docx <-> lyx. One tool for one task.
If it turns out that parts can be reused for doc<->lyx later, fine.

How good/bad is the doc <-> docx conversion in OpenOffice/LibreOffice?

> If I go ahead with support for docx, I think I can write a full
> featured import/export plugin, including:

Good news.


> How to deal with maths is still up in the air. LyX offers the ability
> to typeset nearly anything mathematical, which means there's a very
> large set of markup to support. Exporting to MathML might be one
> option, but that would require Word users to install a plugin.

MathML is already implemented in LyX, so this would be a start.

A converter between (La)TeX math and the `Unicode Nearly Plain Text
Encoding of Mathematics` (http://www.unicode.org/notes/tn28/) would be a
much valued tool also outside of LyX.


Thanks,

Günter

Re: Import into LyX

[Liviu Andronic]

On Thu, Feb 2, 2012 at 9:19 PM, Guenter Milde  wrote:
> How good/bad is the doc <-> docx conversion in OpenOffice/LibreOffice?
>
My experience with OpenOffice and .docx isn't very good: I always had
the feeling that .doc support was better than .docx. The issues
concerned mainly disappearing formatting.

Liviu

Import into LyX

[Rob Oakes]

Dear Users and Developers,

Some time ago, I was experimenting with importing documents into LyX
(specifically about how to crack the import MS Word to LyX nut). In the
process, I got really excited about using OpenOffice to convert the word
document to HTML, running tidy on the HTML and then importing that way.
(The original blog article about this can be found at
http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)

Since I'm (re)writing a book chapter about this topic, I thought that I
would look at alternative strategies for importing Word (and other file
formats) into LyX. While doing research, I came across a (potentially)
much better solution.

Somewhat recently (in 2010), a group of Python libraries were written
that handle document conversions. They are part of the epub-tools
library (http://code.google.com/p/epub-tools/). (I've been experimenting
with ePub document creation from LyX, which is how I found them.)

One of the tools in the library is able to parse Microsoft word
documents and convert them to XHTML in preparation for generating an
ePub file. I think that the tool can be adapted for directly converting
Word docs to LyX. Not to LaTeX and then to LyX, but /directly to LyX/.

I'm putting together a library to experiment with direct conversions
(this is ostensibly being done for the never-ending book project, but
will be released as open code), but before getting too deep into
development, I wanted to poll:

 1. Is this a tool that would prove useful to yourselves, your
collaborators, and others?
 2. What features would you consider essential?

(Right now, styles based conversion looks pretty easy -- going from
Heading 1 in Word to Chapter, for example. But I'm not sure how well
it would convert maths. This is something I'll still need to look
at, and may require writing an additional module.)

 3. What is the best tool to look at for guidance in creating a new
script for word2lyx? tex2lyx?
 4. Does the script need to support special cases, such as importing
Word track changes?
 5. Just how important do you consider round-tripping a document,
e.g., going from LyX to Word and back to LyX.
 6. Is there anyone who might be interested in collaborating on this?

Any thoughts would be greatly appreciated.

Cheers,

Rob Oakes

Re: Import into LyX

[Xu Wang]

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math to
import somewhat well. That seems to be the biggest problem with most ways
of converting doc to lyx. I understand it's very difficult, but I think
it's also the most important.

I don't mean to discourage you, just my two cents. I don't think importing
track changes is important at all (they should be able to go through the
changes in word and get rid of them). And I don't think round-tripping is
important. Of course, if you could pull these features off they would be
nice additions.

I looked at the google code project and it looks like it's still under
development. Is that correct? It would be nice to choose a library that is
still being actively developed.

Good luck with it all and thanks for your effort on this. I think in the
end it would indeed help a lot of would-be LyXers or already-LyXers but
need to collaborate with a Word-er.

Xu

On Wed, Feb 1, 2012 at 2:59 PM, Rob Oakes rob.oa...@oak-tree.us wrote:

  Dear Users and Developers,

 Some time ago, I was experimenting with importing documents into LyX
 (specifically about how to crack the import MS Word to LyX nut). In the
 process, I got really excited about using OpenOffice to convert the word
 document to HTML, running tidy on the HTML and then importing that way.
 (The original blog article about this can be found at
 http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)

 Since I'm (re)writing a book chapter about this topic, I thought that I
 would look at alternative strategies for importing Word (and other file
 formats) into LyX. While doing research, I came across a (potentially) much
 better solution.

 Somewhat recently (in 2010), a group of Python libraries were written that
 handle document conversions. They are part of the epub-tools library (
 http://code.google.com/p/epub-tools/). (I've been experimenting with ePub
 document creation from LyX, which is how I found them.)

 One of the tools in the library is able to parse Microsoft word documents
 and convert them to XHTML in preparation for generating an ePub file. I
 think that the tool can be adapted for directly converting Word docs to
 LyX. Not to LaTeX and then to LyX, but *directly to LyX*.

 I'm putting together a library to experiment with direct conversions (this
 is ostensibly being done for the never-ending book project, but will be
 released as open code), but before getting too deep into development, I
 wanted to poll:

1. Is this a tool that would prove useful to yourselves, your
collaborators, and others?
2. What features would you consider essential?

(Right now, styles based conversion looks pretty easy -- going from
Heading 1 in Word to Chapter, for example. But I'm not sure how well it
would convert maths. This is something I'll still need to look at, and may
require writing an additional module.)

 3. What is the best tool to look at for guidance in creating a new
script for word2lyx? tex2lyx?
4. Does the script need to support special cases, such as importing
Word track changes?
5. Just how important do you consider round-tripping a document,
e.g., going from LyX to Word and back to LyX.
6. Is there anyone who might be interested in collaborating on this?

 Any thoughts would be greatly appreciated.

 Cheers,

 Rob Oakes

Re: Import into LyX

[stefano franchi]

Hi Rob,

first: great project! I constantly struggle with converting file to
and from MS Word. I now use the Word--OOffice-- Latex-- Lyx Route,
with the needed manual cleanup of Latex code and an additional cleanup
of ERT code from LyX after LaTeX import. It is not fun. A project like
yours would make LyX much, much easier to use in an academic
environment.

I am going to address your questions from the perspective of a
Humanities scholar. My observations may not be representative of the
vast majority of current LyX/LaTeX users. On the other hand, a project
like yours may potentially expand LyX's user base by an order of
magnitude, in my opinion. So here we go:

 Is this a tool that would prove useful to yourselves, your collaborators,
 and others?
 What features would you consider essential?


 (Right now, styles based conversion looks pretty easy -- going from Heading
 1 in Word to Chapter, for example. But I'm not sure how well it would
 convert maths. This is something I'll still need to look at, and may require
 writing an additional module.)


As I said, it would be very important. In my experience, there are
three main scenarios where the tool would be precious:

1. Conversion of personal legacy documents (all the stuff you wrote
before you discovered LyX)
2. Collaboration with colleagues and students
3. Submission to journals (I don't know of a single journal in my
field and related fields that accepts Latex. They all want MS Word.)


1 and 3 are obviously one way (in opposite direction). 2 requires a
Word--LyX roundtrip

I think the most important scenarios are 2 and 3. And obviously 2
includes 3 and 1, so solving the collaboration scenario would be
optimal.

Features:

I think a good starting assumption is that final formatting will NOT
be provided by MS Word. If you (or your team) has to produce
camera-ready output at the end of the collaborative work, LyX is a
much better tool. If you submit to a journal or a press, they will do
the formatting.This means most Word-based typography can be
eliminated. I mean: margins, typefaces, font sizes, etc, with the
exception of different scripts, which are of course crucial (although
with Unicode this problem should be solved now).  Only semantic
formatting should be kept: emphasis/italics, sectioning info, lists,
footnotes, etc. Plus all info about pictures and picture placement,
tables (these are not trivial, I guess) and similar floats, and,
mostly for books, indexing information.

Preserving tracking info wold also be very useful.

Cross-referencing would also be important (I have no idea how Word
does it, if at all).

Math, on the other hand, would not be very important. That is: I
assume math would be finally produced by Latex, if camera-ready is
required, or by the publishing house. A rough approximation would be
sufficient (this from a Humanities perspective, of course).

References would be very very important.

 What is the best tool to look at for guidance in creating a new script for
 word2lyx? tex2lyx?

I would look at Word2Tex, which is proprietary, however. In general,
though, most existing tools try hard to preserve the look of a
document instead of following the approach I recommend, thereby
getting into all sort of complications. There was a very useful tool
for Framemaker -- LyX conversion that stuck to the semantic-only
approach and worked pretty well (I was a Framemaker user before moving
to LyX). It was very simple and I believe it is still available:
http://pages.cs.brandeis.edu/~pablo/mif2lyx. It is a Perl script.


 Does the script need to support special cases, such as importing Word track
 changes?

See above

 Just how important do you consider round-tripping a document, e.g., going
 from LyX to Word and back to LyX.

Yes!

 Is there anyone who might be interested in collaborating on this?


I am afraid I cannot help with coding. But I am willing to help in
other ways if needed.

Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Import into LyX

[Rob Oakes]

Dear Users and Developers,

Some time ago, I was experimenting with importing documents into LyX
(specifically about how to crack the import MS Word to LyX nut). In the
process, I got really excited about using OpenOffice to convert the word
document to HTML, running tidy on the HTML and then importing that way.
(The original blog article about this can be found at
http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)

Since I'm (re)writing a book chapter about this topic, I thought that I
would look at alternative strategies for importing Word (and other file
formats) into LyX. While doing research, I came across a (potentially)
much better solution.

Somewhat recently (in 2010), a group of Python libraries were written
that handle document conversions. They are part of the epub-tools
library (http://code.google.com/p/epub-tools/). (I've been experimenting
with ePub document creation from LyX, which is how I found them.)

One of the tools in the library is able to parse Microsoft word
documents and convert them to XHTML in preparation for generating an
ePub file. I think that the tool can be adapted for directly converting
Word docs to LyX. Not to LaTeX and then to LyX, but /directly to LyX/.

I'm putting together a library to experiment with direct conversions
(this is ostensibly being done for the never-ending book project, but
will be released as open code), but before getting too deep into
development, I wanted to poll:

 1. Is this a tool that would prove useful to yourselves, your
collaborators, and others?
 2. What features would you consider essential?

(Right now, styles based conversion looks pretty easy -- going from
Heading 1 in Word to Chapter, for example. But I'm not sure how well
it would convert maths. This is something I'll still need to look
at, and may require writing an additional module.)

 3. What is the best tool to look at for guidance in creating a new
script for word2lyx? tex2lyx?
 4. Does the script need to support special cases, such as importing
Word track changes?
 5. Just how important do you consider round-tripping a document,
e.g., going from LyX to Word and back to LyX.
 6. Is there anyone who might be interested in collaborating on this?

Any thoughts would be greatly appreciated.

Cheers,

Rob Oakes

Re: Import into LyX

[Xu Wang]

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math to
import somewhat well. That seems to be the biggest problem with most ways
of converting doc to lyx. I understand it's very difficult, but I think
it's also the most important.

I don't mean to discourage you, just my two cents. I don't think importing
track changes is important at all (they should be able to go through the
changes in word and get rid of them). And I don't think round-tripping is
important. Of course, if you could pull these features off they would be
nice additions.

I looked at the google code project and it looks like it's still under
development. Is that correct? It would be nice to choose a library that is
still being actively developed.

Good luck with it all and thanks for your effort on this. I think in the
end it would indeed help a lot of would-be LyXers or already-LyXers but
need to collaborate with a Word-er.

Xu

On Wed, Feb 1, 2012 at 2:59 PM, Rob Oakes rob.oa...@oak-tree.us wrote:

  Dear Users and Developers,

 Some time ago, I was experimenting with importing documents into LyX
 (specifically about how to crack the import MS Word to LyX nut). In the
 process, I got really excited about using OpenOffice to convert the word
 document to HTML, running tidy on the HTML and then importing that way.
 (The original blog article about this can be found at
 http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)

 Since I'm (re)writing a book chapter about this topic, I thought that I
 would look at alternative strategies for importing Word (and other file
 formats) into LyX. While doing research, I came across a (potentially) much
 better solution.

 Somewhat recently (in 2010), a group of Python libraries were written that
 handle document conversions. They are part of the epub-tools library (
 http://code.google.com/p/epub-tools/). (I've been experimenting with ePub
 document creation from LyX, which is how I found them.)

 One of the tools in the library is able to parse Microsoft word documents
 and convert them to XHTML in preparation for generating an ePub file. I
 think that the tool can be adapted for directly converting Word docs to
 LyX. Not to LaTeX and then to LyX, but *directly to LyX*.

 I'm putting together a library to experiment with direct conversions (this
 is ostensibly being done for the never-ending book project, but will be
 released as open code), but before getting too deep into development, I
 wanted to poll:

1. Is this a tool that would prove useful to yourselves, your
collaborators, and others?
2. What features would you consider essential?

(Right now, styles based conversion looks pretty easy -- going from
Heading 1 in Word to Chapter, for example. But I'm not sure how well it
would convert maths. This is something I'll still need to look at, and may
require writing an additional module.)

 3. What is the best tool to look at for guidance in creating a new
script for word2lyx? tex2lyx?
4. Does the script need to support special cases, such as importing
Word track changes?
5. Just how important do you consider round-tripping a document,
e.g., going from LyX to Word and back to LyX.
6. Is there anyone who might be interested in collaborating on this?

 Any thoughts would be greatly appreciated.

 Cheers,

 Rob Oakes

Re: Import into LyX

[stefano franchi]

Hi Rob,

first: great project! I constantly struggle with converting file to
and from MS Word. I now use the Word--OOffice-- Latex-- Lyx Route,
with the needed manual cleanup of Latex code and an additional cleanup
of ERT code from LyX after LaTeX import. It is not fun. A project like
yours would make LyX much, much easier to use in an academic
environment.

I am going to address your questions from the perspective of a
Humanities scholar. My observations may not be representative of the
vast majority of current LyX/LaTeX users. On the other hand, a project
like yours may potentially expand LyX's user base by an order of
magnitude, in my opinion. So here we go:

 Is this a tool that would prove useful to yourselves, your collaborators,
 and others?
 What features would you consider essential?


 (Right now, styles based conversion looks pretty easy -- going from Heading
 1 in Word to Chapter, for example. But I'm not sure how well it would
 convert maths. This is something I'll still need to look at, and may require
 writing an additional module.)


As I said, it would be very important. In my experience, there are
three main scenarios where the tool would be precious:

1. Conversion of personal legacy documents (all the stuff you wrote
before you discovered LyX)
2. Collaboration with colleagues and students
3. Submission to journals (I don't know of a single journal in my
field and related fields that accepts Latex. They all want MS Word.)


1 and 3 are obviously one way (in opposite direction). 2 requires a
Word--LyX roundtrip

I think the most important scenarios are 2 and 3. And obviously 2
includes 3 and 1, so solving the collaboration scenario would be
optimal.

Features:

I think a good starting assumption is that final formatting will NOT
be provided by MS Word. If you (or your team) has to produce
camera-ready output at the end of the collaborative work, LyX is a
much better tool. If you submit to a journal or a press, they will do
the formatting.This means most Word-based typography can be
eliminated. I mean: margins, typefaces, font sizes, etc, with the
exception of different scripts, which are of course crucial (although
with Unicode this problem should be solved now).  Only semantic
formatting should be kept: emphasis/italics, sectioning info, lists,
footnotes, etc. Plus all info about pictures and picture placement,
tables (these are not trivial, I guess) and similar floats, and,
mostly for books, indexing information.

Preserving tracking info wold also be very useful.

Cross-referencing would also be important (I have no idea how Word
does it, if at all).

Math, on the other hand, would not be very important. That is: I
assume math would be finally produced by Latex, if camera-ready is
required, or by the publishing house. A rough approximation would be
sufficient (this from a Humanities perspective, of course).

References would be very very important.

 What is the best tool to look at for guidance in creating a new script for
 word2lyx? tex2lyx?

I would look at Word2Tex, which is proprietary, however. In general,
though, most existing tools try hard to preserve the look of a
document instead of following the approach I recommend, thereby
getting into all sort of complications. There was a very useful tool
for Framemaker -- LyX conversion that stuck to the semantic-only
approach and worked pretty well (I was a Framemaker user before moving
to LyX). It was very simple and I believe it is still available:
http://pages.cs.brandeis.edu/~pablo/mif2lyx. It is a Perl script.


 Does the script need to support special cases, such as importing Word track
 changes?

See above

 Just how important do you consider round-tripping a document, e.g., going
 from LyX to Word and back to LyX.

Yes!

 Is there anyone who might be interested in collaborating on this?


I am afraid I cannot help with coding. But I am willing to help in
other ways if needed.

Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas AM University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

Import into LyX

[Rob Oakes]

Dear Users and Developers,

Some time ago, I was experimenting with importing documents into LyX
(specifically about how to crack the import MS Word to LyX nut). In the
process, I got really excited about using OpenOffice to convert the word
document to HTML, running tidy on the HTML and then importing that way.
(The original blog article about this can be found at
http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)

Since I'm (re)writing a book chapter about this topic, I thought that I
would look at alternative strategies for importing Word (and other file
formats) into LyX. While doing research, I came across a (potentially)
much better solution.

Somewhat recently (in 2010), a group of Python libraries were written
that handle document conversions. They are part of the epub-tools
library (http://code.google.com/p/epub-tools/). (I've been experimenting
with ePub document creation from LyX, which is how I found them.)

One of the tools in the library is able to parse Microsoft word
documents and convert them to XHTML in preparation for generating an
ePub file. I think that the tool can be adapted for directly converting
Word docs to LyX. Not to LaTeX and then to LyX, but /directly to LyX/.

I'm putting together a library to experiment with direct conversions
(this is ostensibly being done for the never-ending book project, but
will be released as open code), but before getting too deep into
development, I wanted to poll:

 1. Is this a tool that would prove useful to yourselves, your
collaborators, and others?
 2. What features would you consider essential?

(Right now, styles based conversion looks pretty easy -- going from
Heading 1 in Word to Chapter, for example. But I'm not sure how well
it would convert maths. This is something I'll still need to look
at, and may require writing an additional module.)

 3. What is the best tool to look at for guidance in creating a new
script for word2lyx? tex2lyx?
 4. Does the script need to support special cases, such as importing
Word "track changes"?
 5. Just how important do you consider "round-tripping" a document,
e.g., going from LyX to Word and back to LyX.
 6. Is there anyone who might be interested in collaborating on this?

Any thoughts would be greatly appreciated.

Cheers,

Rob Oakes

Re: Import into LyX

[Xu Wang]

Hey Rob, that sounds like quite a nice project you have in mind!

My two cents: it's not worth carrying it out if you can't get the math to
import somewhat well. That seems to be the biggest problem with most ways
of converting doc to lyx. I understand it's very difficult, but I think
it's also the most important.

I don't mean to discourage you, just my two cents. I don't think importing
track changes is important at all (they should be able to go through the
changes in word and get rid of them). And I don't think round-tripping is
important. Of course, if you could pull these features off they would be
nice additions.

I looked at the google code project and it looks like it's still under
development. Is that correct? It would be nice to choose a library that is
still being actively developed.

Good luck with it all and thanks for your effort on this. I think in the
end it would indeed help a lot of would-be LyXers or already-LyXers but
need to collaborate with a Word-er.

Xu

On Wed, Feb 1, 2012 at 2:59 PM, Rob Oakes <rob.oa...@oak-tree.us> wrote:

>  Dear Users and Developers,
>
> Some time ago, I was experimenting with importing documents into LyX
> (specifically about how to crack the import MS Word to LyX nut). In the
> process, I got really excited about using OpenOffice to convert the word
> document to HTML, running tidy on the HTML and then importing that way.
> (The original blog article about this can be found at
> http://blog.oak-tree.us/index.php/2010/05/14/msword-lyx-import.)
>
> Since I'm (re)writing a book chapter about this topic, I thought that I
> would look at alternative strategies for importing Word (and other file
> formats) into LyX. While doing research, I came across a (potentially) much
> better solution.
>
> Somewhat recently (in 2010), a group of Python libraries were written that
> handle document conversions. They are part of the epub-tools library (
> http://code.google.com/p/epub-tools/). (I've been experimenting with ePub
> document creation from LyX, which is how I found them.)
>
> One of the tools in the library is able to parse Microsoft word documents
> and convert them to XHTML in preparation for generating an ePub file. I
> think that the tool can be adapted for directly converting Word docs to
> LyX. Not to LaTeX and then to LyX, but *directly to LyX*.
>
> I'm putting together a library to experiment with direct conversions (this
> is ostensibly being done for the never-ending book project, but will be
> released as open code), but before getting too deep into development, I
> wanted to poll:
>
>1. Is this a tool that would prove useful to yourselves, your
>collaborators, and others?
>2. What features would you consider essential?
>
>(Right now, styles based conversion looks pretty easy -- going from
>Heading 1 in Word to Chapter, for example. But I'm not sure how well it
>would convert maths. This is something I'll still need to look at, and may
>require writing an additional module.)
>
> 3. What is the best tool to look at for guidance in creating a new
>script for word2lyx? tex2lyx?
>4. Does the script need to support special cases, such as importing
>Word "track changes"?
>5. Just how important do you consider "round-tripping" a document,
>e.g., going from LyX to Word and back to LyX.
>6. Is there anyone who might be interested in collaborating on this?
>
> Any thoughts would be greatly appreciated.
>
> Cheers,
>
> Rob Oakes
>

Re: Import into LyX

[stefano franchi]

Hi Rob,

first: great project! I constantly struggle with converting file to
and from MS Word. I now use the Word-->OOffice--> Latex--> Lyx Route,
with the needed manual cleanup of Latex code and an additional cleanup
of ERT code from LyX after LaTeX import. It is not fun. A project like
yours would make LyX much, much easier to use in an academic
environment.

I am going to address your questions from the perspective of a
Humanities scholar. My observations may not be representative of the
vast majority of current LyX/LaTeX users. On the other hand, a project
like yours may potentially expand LyX's user base by an order of
magnitude, in my opinion. So here we go:

> Is this a tool that would prove useful to yourselves, your collaborators,
> and others?
> What features would you consider essential?

>
> (Right now, styles based conversion looks pretty easy -- going from Heading
> 1 in Word to Chapter, for example. But I'm not sure how well it would
> convert maths. This is something I'll still need to look at, and may require
> writing an additional module.)
>

As I said, it would be very important. In my experience, there are
three main scenarios where the tool would be precious:

1. Conversion of personal legacy documents (all the stuff you wrote
before you discovered LyX)
2. Collaboration with colleagues and students
3. Submission to journals (I don't know of a single journal in my
field and related fields that accepts Latex. They all want MS Word.)


1 and 3 are obviously one way (in opposite direction). 2 requires a
Word<-->LyX roundtrip

I think the most important scenarios are 2 and 3. And obviously 2
includes 3 and 1, so solving the collaboration scenario would be
optimal.

Features:

I think a good starting assumption is that final formatting will NOT
be provided by MS Word. If you (or your team) has to produce
camera-ready output at the end of the collaborative work, LyX is a
much better tool. If you submit to a journal or a press, they will do
the formatting.This means most Word-based typography can be
eliminated. I mean: margins, typefaces, font sizes, etc, with the
exception of different scripts, which are of course crucial (although
with Unicode this problem should be solved now).  Only semantic
formatting should be kept: emphasis/italics, sectioning info, lists,
footnotes, etc. Plus all info about pictures and picture placement,
tables (these are not trivial, I guess) and similar floats, and,
mostly for books, indexing information.

Preserving tracking info wold also be very useful.

Cross-referencing would also be important (I have no idea how Word
does it, if at all).

Math, on the other hand, would not be very important. That is: I
assume math would be finally produced by Latex, if camera-ready is
required, or by the publishing house. A rough approximation would be
sufficient (this from a Humanities perspective, of course).

References would be very very important.

> What is the best tool to look at for guidance in creating a new script for
> word2lyx? tex2lyx?

I would look at Word2Tex, which is proprietary, however. In general,
though, most existing tools try hard to preserve the look of a
document instead of following the approach I recommend, thereby
getting into all sort of complications. There was a very useful tool
for Framemaker <--> LyX conversion that stuck to the semantic-only
approach and worked pretty well (I was a Framemaker user before moving
to LyX). It was very simple and I believe it is still available:
http://pages.cs.brandeis.edu/~pablo/mif2lyx. It is a Perl script.


> Does the script need to support special cases, such as importing Word "track
> changes"?

See above

> Just how important do you consider "round-tripping" a document, e.g., going
> from LyX to Word and back to LyX.

Yes!

> Is there anyone who might be interested in collaborating on this?
>

I am afraid I cannot help with coding. But I am willing to help in
other ways if needed.

Cheers,

Stefano

-- 
__
Stefano Franchi
Associate Research Professor
Department of Hispanic Studies            Ph:   +1 (979) 845-2125
Texas A University                          Fax:  +1 (979) 845-6421
College Station, Texas, USA

stef...@tamu.edu
http://stefano.cleinias.org

How to import into lyx.

[william.croc...@analog.com]

Hello:

I have been using lyx to creation documentation.
Now, I would like to include a section which is generated
programatically. I see that latex has the /input{file}
construct, but I do not find an equivalent in lyx.
I do see the one-time insert/file capability, but that is
not what I want. I want the input to take place at the
time when I generate PDF or HTML.

Thanks.

Bill

RE: How to import into lyx.

[Vincent van Ravesteijn - TNW]

Hello:

I have been using lyx to creation documentation.
Now, I would like to include a section which is
generated programatically. I see that latex has
the /input{file} construct, but I do not find an
equivalent in lyx.

Try Insert-File-Child document... And select Input as the Include
Type.

Vincent

Re: How to import into lyx.

[william.croc...@analog.com]

I have been using lyx to creation documentation.
Now, I would like to include a section which is
generated programatically. I see that latex has
the /input{file} construct, but I do not find an
equivalent in lyx.



Try Insert-File-Child document... And select Input as the Include
Type.

  

That did the trick.
Thank you.
Bill

How to import into lyx.

[william.croc...@analog.com]

Hello:

I have been using lyx to creation documentation.
Now, I would like to include a section which is generated
programatically. I see that latex has the /input{file}
construct, but I do not find an equivalent in lyx.
I do see the one-time insert/file capability, but that is
not what I want. I want the input to take place at the
time when I generate PDF or HTML.

Thanks.

Bill

RE: How to import into lyx.

[Vincent van Ravesteijn - TNW]

Hello:

I have been using lyx to creation documentation.
Now, I would like to include a section which is
generated programatically. I see that latex has
the /input{file} construct, but I do not find an
equivalent in lyx.

Try Insert-File-Child document... And select Input as the Include
Type.

Vincent

Re: How to import into lyx.

[william.croc...@analog.com]

I have been using lyx to creation documentation.
Now, I would like to include a section which is
generated programatically. I see that latex has
the /input{file} construct, but I do not find an
equivalent in lyx.



Try Insert-File-Child document... And select Input as the Include
Type.

  

That did the trick.
Thank you.
Bill

How to import into lyx.

[william.croc...@analog.com]

Hello:

I have been using lyx to creation documentation.
Now, I would like to include a section which is generated
programatically. I see that latex has the /input{file}
construct, but I do not find an equivalent in lyx.
I do see the one-time insert/file capability, but that is
not what I want. I want the input to take place at the
time when I generate PDF or HTML.

Thanks.

Bill

RE: How to import into lyx.

[Vincent van Ravesteijn - TNW]

>Hello:
>
>I have been using lyx to creation documentation.
>Now, I would like to include a section which is
>generated programatically. I see that latex has
>the /input{file} construct, but I do not find an
>equivalent in lyx.

Try Insert->File->Child document... And select "Input" as the "Include
Type".

Vincent

Re: How to import into lyx.

[william.croc...@analog.com]

I have been using lyx to creation documentation.
Now, I would like to include a section which is
generated programatically. I see that latex has
the /input{file} construct, but I do not find an
equivalent in lyx.



Try Insert->File->Child document... And select "Input" as the "Include
Type".

  

That did the trick.
Thank you.
Bill

Re: Import RTF Lyx 1.6 error

[Joachim Kreimer-de Fries]

Am 04.12.2008 um 15:49 schrieb Konrad Hofbauer:

If there is no native os x version, then install macports (http:// 
www.macports.org/), and from there install the needed packages.


I made the same experience as Joachim K. Rennstich, so I followed the  
advice of Konrad Hofbauer, downloaded the Mac-OSX 10.4 Tiger version  
of MacPorts, made the standard MacPorts-1.6.0-10.4-Tiger.dmg  
installing, the installer program said MacPorts have been  
successfully installed at your system or the like,


but now I'm puzzling about:

== How to install the needed packages (i. e. the rtf2latex2e  
script or package) from there (MacPorts?).


Testwise I called in the Terminal
sudo port -d selfupdate
with the answer: sudo: port: command not found

Konrad or others, can you tell me how to install rtf2latex2e with  
MacPorts?

How can I proof if MacPorts is installed rightly, how to run it?

Hopefully, joachim

--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger

Re: Import RTF Lyx 1.6 error

[Joachim Kreimer-de Fries]

Am 04.12.2008 um 15:49 schrieb Konrad Hofbauer:

If there is no native os x version, then install macports (http:// 
www.macports.org/), and from there install the needed packages.


I made the same experience as Joachim K. Rennstich, so I followed the  
advice of Konrad Hofbauer, downloaded the Mac-OSX 10.4 Tiger version  
of MacPorts, made the standard MacPorts-1.6.0-10.4-Tiger.dmg  
installing, the installer program said MacPorts have been  
successfully installed at your system or the like,


but now I'm puzzling about:

== How to install the needed packages (i. e. the rtf2latex2e  
script or package) from there (MacPorts?).


Testwise I called in the Terminal
sudo port -d selfupdate
with the answer: sudo: port: command not found

Konrad or others, can you tell me how to install rtf2latex2e with  
MacPorts?

How can I proof if MacPorts is installed rightly, how to run it?

Hopefully, joachim

--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger

Re: Import RTF > Lyx 1.6 error

[Joachim Kreimer-de Fries]

Am 04.12.2008 um 15:49 schrieb Konrad Hofbauer:

If there is no native os x version, then install macports (www.macports.org/>), and from there install the needed packages.


I made the same experience as Joachim K. Rennstich, so I followed the  
advice of Konrad Hofbauer, downloaded the Mac-OSX 10.4 Tiger version  
of MacPorts, made the standard MacPorts-1.6.0-10.4-Tiger.dmg  
installing, the installer program said "MacPorts have been  
successfully installed at your system" or the like,


but now I'm puzzling about:

==> How to "install the needed packages" (i. e. the rtf2latex2e  
script or package) "from there" (MacPorts?).


Testwise I called in the Terminal
sudo port -d selfupdate
with the answer: "sudo: port: command not found"

Konrad or others, can you tell me how to install rtf2latex2e with  
MacPorts?

How can I proof if MacPorts is installed rightly, how to run it?

Hopefully, joachim

--
MacTeXLive 2008 - TeXShop 2.18-svn - LyX 1.6
MacBook Pro OSX 10.4.11 Tiger

Import RTF Lyx 1.6 error

[Dr. Joachim K. Rennstich]

I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5,  
Intel) through the File  Import  Rich Text Format... command but  
get the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it  
is not supported on Mac OS X unless you compile the UNIX version. My  
question is: how can I make the command work? What do I need to  
install in addition and how can I do that?


Thanks
- Joachim

Re: Import RTF Lyx 1.6 error

[Konrad Hofbauer]

Dr. Joachim K. Rennstich wrote:
I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5, 
Intel) through the File  Import  Rich Text Format... command but get 
the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it is 
not supported on Mac OS X unless you compile the UNIX version. My 
question is: how can I make the command work? What do I need to install 
in addition and how can I do that?


If there is no native os x version, then install macports 
(http://www.macports.org/), and from there install the needed packages.



$ port search rtf2latex
rtf2latex  tex/rtf2latex  1.5  Filter to convert 
RTF text into LaTeX code
rtf2latex2etex/rtf2latex2e 1.0fc1   Filter to convert 
rtf files into LaTeX2e code.


/Konrad

Import RTF Lyx 1.6 error

[Dr. Joachim K. Rennstich]

I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5,  
Intel) through the File  Import  Rich Text Format... command but  
get the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it  
is not supported on Mac OS X unless you compile the UNIX version. My  
question is: how can I make the command work? What do I need to  
install in addition and how can I do that?


Thanks
- Joachim

Re: Import RTF Lyx 1.6 error

[Konrad Hofbauer]

Dr. Joachim K. Rennstich wrote:
I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5, 
Intel) through the File  Import  Rich Text Format... command but get 
the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it is 
not supported on Mac OS X unless you compile the UNIX version. My 
question is: how can I make the command work? What do I need to install 
in addition and how can I do that?


If there is no native os x version, then install macports 
(http://www.macports.org/), and from there install the needed packages.



$ port search rtf2latex
rtf2latex  tex/rtf2latex  1.5  Filter to convert 
RTF text into LaTeX code
rtf2latex2etex/rtf2latex2e 1.0fc1   Filter to convert 
rtf files into LaTeX2e code.


/Konrad

Import RTF > Lyx 1.6 error

[Dr. Joachim K. Rennstich]

I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5,  
Intel) through the "File > Import > Rich Text Format..." command but  
get the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it  
is not supported on Mac OS X unless you compile the UNIX version. My  
question is: how can I make the command work? What do I need to  
install in addition and how can I do that?


Thanks
- Joachim

Re: Import RTF > Lyx 1.6 error

[Konrad Hofbauer]

Dr. Joachim K. Rennstich wrote:
I am trying to import a RTF document into Lyx 1.6 (Mac OS X 10.5.5, 
Intel) through the "File > Import > Rich Text Format..." command but get 
the following error:



An error occurred whilst running rtf2latex2e 'whateverfile.rtf'



I have been looking up rtf2latex2e and discovered that apparently it is 
not supported on Mac OS X unless you compile the UNIX version. My 
question is: how can I make the command work? What do I need to install 
in addition and how can I do that?


If there is no native os x version, then install macports 
(), and from there install the needed packages.



$ port search rtf2latex
rtf2latex  tex/rtf2latex  1.5  Filter to convert 
RTF text into LaTeX code
rtf2latex2etex/rtf2latex2e 1.0fc1   Filter to convert 
rtf files into LaTeX2e code.


/Konrad

Matlab code pretty print import to lyx?

[Andrew Morrison]

Does anyone know if there is a way to publish Matlab code in a lyx
document with the colors of the keywords, variables, comments and etc.
preserved?

I tried googling for lyx, code, and pretty print, but didn't really come
up with any solution that worked easily.  There are a few matlab scripts
that output a latex file of the code, but when I import them into lyx, I
get 27 errors when I try to view the PDF.

Thanks! 

-- 
Andrew Morrison [EMAIL PROTECTED]

Re: Matlab code pretty print import to lyx?

[Gunnar]

 Does anyone know if there is a way to publish Matlab code in a lyx
 document with the colors of the keywords, variables, comments and etc.
 preserved?

There is a package called listings that might be useful, but colors on the 
keywords, I'm not sure if that is supported.

A perl/sed script might do the trick if you're handy.

Matlab code pretty print import to lyx?

[Andrew Morrison]

Does anyone know if there is a way to publish Matlab code in a lyx
document with the colors of the keywords, variables, comments and etc.
preserved?

I tried googling for lyx, code, and pretty print, but didn't really come
up with any solution that worked easily.  There are a few matlab scripts
that output a latex file of the code, but when I import them into lyx, I
get 27 errors when I try to view the PDF.

Thanks! 

-- 
Andrew Morrison [EMAIL PROTECTED]

Re: Matlab code pretty print import to lyx?

[Gunnar]

 Does anyone know if there is a way to publish Matlab code in a lyx
 document with the colors of the keywords, variables, comments and etc.
 preserved?

There is a package called listings that might be useful, but colors on the 
keywords, I'm not sure if that is supported.

A perl/sed script might do the trick if you're handy.

Matlab code "pretty print" import to lyx?

[Andrew Morrison]

Does anyone know if there is a way to publish Matlab code in a lyx
document with the colors of the keywords, variables, comments and etc.
preserved?

I tried googling for lyx, code, and pretty print, but didn't really come
up with any solution that worked easily.  There are a few matlab scripts
that output a latex file of the code, but when I import them into lyx, I
get 27 errors when I try to view the PDF.

Thanks! 

-- 
Andrew Morrison <[EMAIL PROTECTED]>

Re: Matlab code "pretty print" import to lyx?

[Gunnar]

> Does anyone know if there is a way to publish Matlab code in a lyx
> document with the colors of the keywords, variables, comments and etc.
> preserved?
>
There is a package called "listings" that might be useful, but colors on the 
keywords, I'm not sure if that is supported.

A perl/sed script might do the trick if you're handy.