On Tue, 24 Dec 2002 10:52, you wrote:
> I am in the process of writing a converter to convert Word RTF documents
> to LyX. When I brought this topic up before, I was told that the form of

Good to hear about people working for the greater good ;-)

> the .lyx files is evolving. Are there great differences between version
> 1.16 (which I use) and 1.2?

Yes there are. After I've discovered I prefer lyx-1.1.* to lyx-1.2.*, I've 
also discovered that I can not downgrade easily because lyx-1.1.* can't read 
lyx-1.2.* docs. I have written a backward converter which handles paragraph 
styles I use (i.e. it won't work for everyone). Write to me if you want to 
check it out (Do so privately, this list already knows about it and has more 
than enough traffic). As far as I know lyx 1.3 also has its own 
non-backward-compatible format.

What about conversion to tex instead. If you use reasonably standard/simple 
(?) tex, lyx should be able to import it. Some free word processors can 
export in tex format, though not very well...

>
> I have done the most difficult part of the work, converting RTF to valid
> XML. The script that performs this task will soon be available on
> Sourceforge. I am working with someone who is writing an xslt stylesheet
> to convert the XML to sdocbook. It shouldn't be too dificult to also
> write an xslt style sheet to convert the XML to LyX.
>

Ted is _very_ good for reading/writing/editing rtf files; much better than 
staroffice or openoffice, or any other linux office/word-proc. package I've 
tried. You should check out what formats it can export.

> this way, a user does not lose his/her styles. As long as the user moves
> the layout file to the right directory and reconfigures LyX, s/he will
> be able to have pull-down files that correspond to the pull-down styles
> available in Word for the same document.
>

sounds v. ambitious. Good luck!

Steve

-- 
Steven Homolya
School of Physics and Materials Engineering
Monash University VIC 3800
Australia
Tel: INT +61 3 9905 3694
Fax: INT +61 3 9905 3637

Reply via email to