Luthiger Stoll Benno wrote:
> Hello all
>
> I found the cause of problem that turned the file 'corrupt'.
> In my application, I created the entry for manifest.xml as follows:
> ===
> "META-INF" + File.separator + "manifest.xml"
> ===
> On a Windows machine, this gives "META-INF\manifest.xml"
> L
Hi Luthiger,
On Friday, 2007-08-31 15:27:17 +0200, Luthiger Stoll Benno wrote:
> I found the cause of problem that turned the file 'corrupt'.
> In my application, I created the entry for manifest.xml as follows:
> ===
> "META-INF" + File.separator + "manifest.xml"
> ===
> On a Windows machine, th
They pointed me to the right direction.
Mathias: shall I still file an issue, to document the problem and it's solution?
Regards
Benno
From: Mathias Bauer [mailto:[EMAIL PROTECTED]
Sent: Thu 8/30/2007 9:17 AM
To: dev@openoffice.org
Subject: Re: [dev]
Luthiger Stoll Benno wrote:
> Hello
>
> Thanks for your responses.
> Concerning the mimetype entry:
>> ... it doesn't look like it is the first stream ...
> What does this mean? Do I have to write the JarEntry for the mimetype as
> first entry written to the output file?
If that can guarantee
Eike Rathke wrote:
> Hi Mathias,
>
> On Tuesday, 2007-08-28 18:45:59 +0200, Mathias Bauer wrote:
>
>> First I miss the "mimetype" stream.
>
> It's there, but it doesn't look like it is the first stream in the
> package that it ought to be following the ODF spec:
I must have been blind. :-[
>
Hi Luthiger,
On Wednesday, 2007-08-29 15:04:52 +0200, Luthiger Stoll Benno wrote:
> Concerning the mimetype entry:
> > ... it doesn't look like it is the first stream ...
> What does this mean? Do I have to write the JarEntry for the mimetype as
> first entry written to the output file?
Yes, a
content of the manifest.xml:
==
==
Regards,
Benno
> -Original Message-
> From: Eike Rathke [mailto:[EMAIL PROTECTED]
> Sent: Mittwoch, 29. August 2007 12:20
> To: dev@openoffice.org
> Subject: Re: [dev] ODT file created through XSL transformation is
Hi Mathias,
On Tuesday, 2007-08-28 18:45:59 +0200, Mathias Bauer wrote:
> First I miss the "mimetype" stream.
It's there, but it doesn't look like it is the first stream in the
package that it ought to be following the ODF spec:
> > Nametypesizeratio
Luthiger Stoll Benno wrote:
> Hello
>
> I have developed a Java application that holds data in XML and prints this
> data into an OpenOffice.odt file using XSL transformation. Unfortunately,
> when I open the created file, the message "The file 'xyz.odt' is corrupt and
> therefore cannot be op
Hi Juergen
>> Does anybody has a hint what could be corrupt with the file created with
>> XSLT?
>> Is there a log file that I can consult to learn more about what exactely is
>> corrupt with the file?
>> Is there a mailing list better suited for this problem?
> Probably the [EMAIL PROTECTED] mai
Hi Benno,
Luthiger Stoll Benno wrote:
Hello
I have developed a Java application that holds data in XML and prints this data into an
OpenOffice.odt file using XSL transformation. Unfortunately, when I open the created
file, the message "The file 'xyz.odt' is corrupt and therefore cannot be ope
Hello
I have developed a Java application that holds data in XML and prints this data
into an OpenOffice.odt file using XSL transformation. Unfortunately, when I
open the created file, the message "The file 'xyz.odt' is corrupt and therefore
cannot be opened. Should OpenOffice.org repair the fi
12 matches
Mail list logo
