Hi Regina,
On Fri, 2011-01-14 at 23:23 +0100, Regina Henschel wrote:
> I use the German LibO RC3 on WinXP and the filters are not there.
Riight - we fixed this bug; having said that Pierre's work should make
the binfilter tolerably small, instead of another handful of megabytes
that the
> there is something wrong actually. Removing *Export*-filter is
> reasonable, but now in LibO RC3 I cannot *read* my SO5 files.
That is caused by the build having been done without --enable-binfilter, I
think. Not on purpose, and not related to this "making binfilter formats
read-only" discuss
Hi Pierre-André,
Pierre-André Jacquod schrieb:
Hi,
On 01/14/2011 07:33 PM, Regina Henschel wrote:
Hi all,
there is something wrong actually. Removing *Export*-filter is
reasonable, but now in LibO RC3 I cannot *read* my SO5 files.
Kind regards
Regina
Up to now, nothing has been committed. On
Hi,
On 01/14/2011 07:33 PM, Regina Henschel wrote:
> Hi all,
>
> there is something wrong actually. Removing *Export*-filter is
> reasonable, but now in LibO RC3 I cannot *read* my SO5 files.
>
> Kind regards
> Regina
Up to now, nothing has been committed. On trunk master, all is OK, I
just teste
Hi all,
there is something wrong actually. Removing *Export*-filter is
reasonable, but now in LibO RC3 I cannot *read* my SO5 files.
Kind regards
Regina
Pierre-André Jacquod schrieb:
Hello,
these days, I have tried (and not really with full success) to
understand how binfilter works...
My
Hi Pierre,
On Sat, 2011-01-08 at 00:15 +0100, Pierre-André Jacquod wrote:
> >> The filter, despite write is not usable (no export). ...
> >> So ideally could it be: not export, READONLY and pop-up ?? :- /
> > I'd still prefer not to set the read-only flag if possible, it is a
>
> After playing a b
Michael Meeks wrote:
> Anyhow - just wondering how this is progressing ? :-) and looking
> forward to having it integrated.
I haven't checked details, but it seems this might overlap with the work
done (and possibly still being done) in the OOo trunk, see
http://www.openoffice.org/issues/sho
Hi Jan / Hi Michael,
some more testing and code reading. Here some answers.
[I was writing this mail while testing, mostly written before Michael's
mail. Hence this will answers both mails. ]
> This is a good point - as you say, I agree we can omit the creation of
> the lock file. It would be go
Hi Pierre,
This looks like a really useful start :-)
On Mon, 2011-01-03 at 13:27 +0100, Jan Holesovsky wrote:
> > Second issue I see: (I just though of it right now, did not yet test /
> > investigate): with opening in read/write and without EXPORT filter, what
> > happens with the auto-s
Hi Pierre-Andre,
On 2010-12-30 at 17:30 +0100, Pierre-André Jacquod wrote:
> Thus, there is a major difference: With READONLY, no lock-file is
> generated when the file is openend. With filter without the EXPORT, the
> lock-file is still generated This comes during the load process,
> where t
Hi,
>> in binfilter as read-only filters (using as filter flag
>> SFX_FILTER_OPENREADONLY defined as 0x0001L) This will make the
>> opening read-only. By this way, this is not possible any more to save
> IIRC the resolution was a bit different ;-)
you are right:-)
> This way the user will
Hi Pierre-Andre,
On 2010-12-27 at 21:31 +0100, Pierre-André Jacquod wrote:
> An easy (and clean) possibility would be to change the filters defined
> in binfilter as read-only filters (using as filter flag
> SFX_FILTER_OPENREADONLY defined as 0x0001L) This will make the
> opening read-only. B
Hello,
these days, I have tried (and not really with full success) to
understand how binfilter works...
My goal: since it is an old legacy format, make StarOffice formats
read-only, and clean binfilter component of all code used for writing files.
Reason: with read-only, you will still be able to
13 matches
Mail list logo
