Thank you for your prompt reply. I did what you suggested and you are right. Inserting the full path to the document that is going to be translated makes things work when using java-gcj alternative.
However this is not entirely obvious, since even the application manual that comes with the writer2latex-manual package uses a syntax with no full paths. Furthermore, when using writer2latex with lyx the same problem occurs when importing a openoffice document. Checking the console output, it seems that lyx also fails to use a full path to the document, therefore only working "out of the box" when java-6-sun is the alternative (Although after taking into account your suggestion and changing lyx's preferences accordingly, everything comes back to normal). So my only suggestion would be that a Readme.Debian would document the way in which the app's syntax is slightly different depending on whether you are using java-gcj or sun's java. Other than that feel free to close the bug. I hope I haven't been much of a nuisance to you guys with my own shortcomings when it comes to bug reporting. Keep up the good work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
