Bug 40519 - Using oor:op="replace" in XCU does not work
Summary: Using oor:op="replace" in XCU does not work
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Linguistic (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: All Linux (All)
: medium normal
Assignee: Thorsten Behrens (allotropia)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 09:46 UTC by andre.pietsch
Modified: 2013-11-30 22:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample Project for a spell check in Netbeans 6.9 (398.38 KB, application/zip)
2011-08-31 09:46 UTC, andre.pietsch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description andre.pietsch 2011-08-31 09:46:08 UTC
Created attachment 50756 [details]
Sample Project for a spell check in Netbeans 6.9

See attached Netbeans 6.9 project.


AddOn.oxt is a (dumb) Spellchecker.

It contains a Linguistic.xcu which should overwrite this registry entry on installation;
org/openoffice/Office/Linguistic/ServiceManager/SpellCheckerList 

This is a stringlist. But it does not get overwritten but merged ("fused") in spite of having set oor:op="replace".

Why is this?

After the installation there should only be my new spellchecker active for de-de, but the default spellchecker is active, too. This also is reflected in the registry.

I remember to have noticed that even if I try to set the registry setting programmatically, on opening the first document the setting is reverted. This is not proven in the test case and maybe it is a false observation, but it might help finding the cause of this issue.
Comment 1 retired 2013-09-01 11:47:45 UTC
Hi Andre,

is this bug still valid / reproducible with the latest LO release from http://www.libreoffice.org/download/ ?
Comment 2 Jean-Baptiste Faure 2013-11-30 22:10:14 UTC
No answer since 3 months and no activity during 2 years. I think we can consider this problem has been solved from a way or another.
So closing as INVALID.

Please, feel free to reopen this bug report if you still experience this problem.
That said, before to reopen, you should ask for help on the users mailing-list.

Best regards. JBF