On 01/17/2011 07:24 PM, NoOp wrote:
> On 01/17/2011 05:38 PM, NoOp wrote:
>> On 01/17/2011 12:59 PM, NoOp wrote:
...
>>> Thanks! I've been travelling, but I'm back now and will try to test
>>> later this evening on WinXP.
>>
>> OK. Briefly tested and here is what I've found so far:
>>
>> 1. LO &
On 01/17/2011 05:38 PM, NoOp wrote:
> On 01/17/2011 12:59 PM, NoOp wrote:
>> On 01/15/2011 03:43 AM, Jesús Corrius wrote:
>> ...
>>> I have made a full build with my patch, so anyone can test it. You can
>>> download it here:
>>>
>>> http://dl.dropbox.com/u/193133/LibO_3.3.0rc2_Win_x86_install_en-
On 01/17/2011 12:59 PM, NoOp wrote:
> On 01/15/2011 03:43 AM, Jesús Corrius wrote:
> ...
>> I have made a full build with my patch, so anyone can test it. You can
>> download it here:
>>
>> http://dl.dropbox.com/u/193133/LibO_3.3.0rc2_Win_x86_install_en-US.exe
>>
>> This build is from the current
On 01/15/2011 03:43 AM, Jesús Corrius wrote:
...
> I have made a full build with my patch, so anyone can test it. You can
> download it here:
>
> http://dl.dropbox.com/u/193133/LibO_3.3.0rc2_Win_x86_install_en-US.exe
>
> This build is from the current master unstable branch, not the stable
> 3.3,
Hi Jonathan,
On Mon, 2011-01-17 at 10:45 +0100, Jonathan Aquilina wrote:
> You mentioned incremental updates. how is this done. does LO have an
> update menu item that will check an update repository and apply the
> updates, or is a whole reinstall necessary?
That is platform dependent;
You mentioned incremental updates. how is this done. does LO have an
update menu item that will check an update repository and apply the
updates, or is a whole reinstall necessary?
On 01/17/2011 10:33 AM, Michael Meeks wrote:
Hi there,
On Fri, 2011-01-14 at 04:12 -0800, plino wrote:
Michael,
Hi there,
On Fri, 2011-01-14 at 04:12 -0800, plino wrote:
> Michael, please don't regard this as a personal complaint.
I take all bugs very personally ;-)
> I think it's a bad idea to cause grievance to users who are giving it a go.
> IMO it will make them stick to OOo...
So - I
Hi Jesús
After some extensive testing I found out that if I accept the defaults
(Install for All users instead of Only for me
which is what I always do) I can get the "Open with" option for ODFs as well
as MS Office files.
So the problem here is also where in the registry the keys are saved (HK
Hi Pedro,
2011/1/16 Pedro Lino :
> Hi Jesús
>
>> > I'm afraid it's not fixed yet. I think the problem is that e.g. ODS is
>> > associated with OOo's scalc as the default application and to LibO's
>> > scalc
>> > as an alternate program. These are not stored in the SAME registry Key.
>>
>> Yes, sho
I'm afraid it's not fixed yet. I think the problem is that e.g. ODS is
associated with OOo's scalc as the default application and to LibO's scalc
as an alternate program. These are not stored in the SAME registry Key.
For xls which is associated with MS Excel (on my system), both OOo and LibO
a
I'm afraid it's not fixed yet. I think the problem is that e.g. ODS is
associated with OOo's scalc as the default application and to LibO's scalc
as an alternate program. These are not stored in the registry Key.
For xls which is associated with MS Excel (on my system), both OOo and LibO
are alt
> I just tried cleaning it all (registry keys under Software included both for
> HKCU and HKLM) and after installing OpenOfice 3.3.0RC9 and your build, I get
> both options in the "Open with" menu IF I'm selecting an ODS or ODF file.
> The same doesn't happen for a DOC or XLS file where only the Op
I just tried cleaning it all (registry keys under Software included both for
HKCU and HKLM) and after installing OpenOfice 3.3.0RC9 and your build, I get
both options in the "Open with" menu IF I'm selecting an ODS or ODF file.
The same doesn't happen for a DOC or XLS file where only the OpenOffic
I'm testing several scenarios. I will report back ;)
The scenario that didn't work was:
OpenOffice RC8 > LibreOffice RC2 > OpenOffice 3.3.0rc9 > Your LibO
I couldn't "Open with" OpenOffice Writer because it was associated with LibO
Writer
--
View this message in context:
http://nabble.docume
Hi,
2011/1/15 Jesús Corrius :
> On Sat, Jan 15, 2011 at 3:59 PM, plino wrote:
>>
>> Jesús, thank you for the new build. Unfortunately it doesn't fix the problem.
>> Even if it did, the next time a user installs an OOo update wouldn't the
>> problem appear again? If you add your fix to LO only, OO
On Sat, Jan 15, 2011 at 3:59 PM, plino wrote:
>
> Jesús, thank you for the new build. Unfortunately it doesn't fix the problem.
> Even if it did, the next time a user installs an OOo update wouldn't the
> problem appear again? If you add your fix to LO only, OOo updates won't
> unfix it?
Yes, tha
Jesús, thank you for the new build. Unfortunately it doesn't fix the problem.
Even if it did, the next time a user installs an OOo update wouldn't the
problem appear again? If you add your fix to LO only, OOo updates won't
unfix it?
I can't see any other permanent solution than renaming the exes.
On Fri, Jan 14, 2011 at 1:12 PM, plino wrote:
>
> Michael, please don't regard this as a personal complaint.
>
> I think many users who are currently using OOo will have this problem when
> they try LO (and update any of them).
>
> I think it's a bad idea to cause grievance to users who are giving
On Fri, Jan 14, 2011 at 12:59 PM, Michael Meeks
wrote:
>
> On Fri, 2011-01-14 at 02:37 -0800, plino wrote:
>> Every time I update LibO or OOo (and like me most users who are experimenting
>> with LibO but want to keep up with the currently more stable OOo) the file
>> associations get messed up fo
Michael, please don't regard this as a personal complaint.
I think many users who are currently using OOo will have this problem when
they try LO (and update any of them).
I think it's a bad idea to cause grievance to users who are giving it a go.
IMO it will make them stick to OOo...
Changing
On Fri, 2011-01-14 at 02:37 -0800, plino wrote:
> Every time I update LibO or OOo (and like me most users who are experimenting
> with LibO but want to keep up with the currently more stable OOo) the file
> associations get messed up for the reasons explained by Jesús.
>
> Have the devs reached a
Every time I update LibO or OOo (and like me most users who are experimenting
with LibO but want to keep up with the currently more stable OOo) the file
associations get messed up for the reasons explained by Jesús.
Have the devs reached any decision on this?
--
View this message in context:
ht
Hi Thorsten,
2011/1/10 Thorsten Behrens :
> Jesús Corrius wrote:
>> 3. Use a completely different windows registry keys for LibO.
>>
> That's the right approach in my book. And, if you, or somebody else
> is volunteering to do that - it would be really great to have those
> name instances consolid
Jesús Corrius wrote:
> 3. Use a completely different windows registry keys for LibO.
>
That's the right approach in my book. And, if you, or somebody else
is volunteering to do that - it would be really great to have those
name instances consolidated to some $PRODUCTNAME placeholder or
somesuch ..
Hi Tor,
>> The attached patch fixes the issue for me,
>
> I don't think there is a need to abbreviate "LibreOffice" as "loffice" in the
> registry key names. We shouldn't use too many names for our baby.
>
> Otherwise, I'd say please do commit (to master).
The problem is that we are using the sa
> The attached patch fixes the issue for me,
I don't think there is a need to abbreviate "LibreOffice" as "loffice" in the
registry key names. We shouldn't use too many names for our baby.
Otherwise, I'd say please do commit (to master).
--tml
___
L
On 01/05/2011 02:55 AM, Jesús Corrius wrote:
> On Wed, Jan 5, 2011 at 5:38 AM, NoOp wrote:
...
>> Any progress on this? Would it help if I filed a bug report?
>>
>> This issue is (to me) critical regarding any further RC or full release
>> of LibO.
>
> Sorry, I have been in Norway for more than w
On Wed, Jan 5, 2011 at 5:38 AM, NoOp wrote:
> On 12/24/2010 03:26 PM, NoOp wrote:
>> On 12/24/2010 11:32 AM, Jesús Corrius wrote:
>> ...
>>> I see, I was able to reproduce it after making a few tests. Let me
>>> investigate this further.
>>>
>>> Scenarios that work (for me)
>>> ---
On 12/24/2010 03:26 PM, NoOp wrote:
> On 12/24/2010 11:32 AM, Jesús Corrius wrote:
> ...
>> I see, I was able to reproduce it after making a few tests. Let me
>> investigate this further.
>>
>> Scenarios that work (for me)
>> -
>>
>> OpenOffice 3.3 RC8 + LibO 3.3 RC2 = Wor
On 12/24/2010 11:32 AM, Jesús Corrius wrote:
...
> I see, I was able to reproduce it after making a few tests. Let me
> investigate this further.
>
> Scenarios that work (for me)
> -
>
> OpenOffice 3.3 RC8 + LibO 3.3 RC2 = Works
> OpenOffice 3.2.1 final + LibO 3.3 RC2 = Wo
On Fri, Dec 24, 2010 at 5:56 AM, NoOp wrote:
> On 12/23/2010 08:49 PM, NoOp wrote:
>> On 12/18/2010 03:48 AM, Jesús Corrius wrote:
Right-click the .odt and select 'Open With' (WinXPPro); the 'Programs'
window shows only option for LibO, not OOo. It does show options for
Word if MS W
On 12/23/2010 08:49 PM, NoOp wrote:
> On 12/18/2010 03:48 AM, Jesús Corrius wrote:
>>> Right-click the .odt and select 'Open With' (WinXPPro); the 'Programs'
>>> window shows only option for LibO, not OOo. It does show options for
>>> Word if MS Word is installed and has the odf converter installed
On 12/18/2010 03:48 AM, Jesús Corrius wrote:
>> Right-click the .odt and select 'Open With' (WinXPPro); the 'Programs'
>> window shows only option for LibO, not OOo. It does show options for
>> Word if MS Word is installed and has the odf converter installed. I've
>> repeated this on my WinXPro VM
On 12/18/2010 03:48 AM, Jesús Corrius wrote:
>> Right-click the .odt and select 'Open With' (WinXPPro); the 'Programs'
>> window shows only option for LibO, not OOo. It does show options for
>> Word if MS Word is installed and has the odf converter installed. I've
>> repeated this on my WinXPro VM
> Right-click the .odt and select 'Open With' (WinXPPro); the 'Programs'
> window shows only option for LibO, not OOo. It does show options for
> Word if MS Word is installed and has the odf converter installed. I've
> repeated this on my WinXPro VM by:
>
> 1. Uninstalling all instances of OOo and
On 12/17/2010 05:34 PM, Jesús Corrius wrote:
> On Sat, Dec 18, 2010 at 2:18 AM, NoOp wrote:
>> Installing LibORC1on a Windwows system[1] creates an issue with a
>> co-installed OOo install. Once LibO is installed it takes over all .odt
>> etc file properties associations.
>>
>> - LO takes over all
On Sat, Dec 18, 2010 at 2:18 AM, NoOp wrote:
> Installing LibORC1on a Windwows system[1] creates an issue with a
> co-installed OOo install. Once LibO is installed it takes over all .odt
> etc file properties associations.
>
> - LO takes over all OOo application defaults & icons.
> - LO uses the s
37 matches
Mail list logo
