Posted: Mon Sep 26, 2005 1:28 am Post subject: NeoLight: problem with OpenOffice 2.0
Hi there!
Theres a lot of posts, articles describing that NeoLight also is able to index Open Documents documents, but I'm totally unable to get it to work. As I read it, the Info.plist contains everything neccasary for this to work, but I don't see any references to any .odt etc document types, so how is this to work?
Posted: Wed Sep 28, 2005 1:12 am Post subject: Re: NeoLight: problem with OpenOffice 2.0
perdalum wrote:
Theres a lot of posts, articles describing that NeoLight also is able to index Open Documents documents, but I'm totally unable to get it to work. As I read it, the Info.plist contains everything neccasary for this to work, but I don't see any references to any .odt etc document types, so how is this to work?
That's partially a misunderstanding between engineering and marketing
NeoLight does support indexing of OpenDocument files, but because OD support has not been extensively tested (it's based almost solely on reading the specs), OD support is not enabled by default (the missing .plist entries).
I *believe* that if you simply replicate the .plist entries and replace the extensions and MIME types with the OpenDocument ones and then re-initialize the importer, it should then find content in OpenDocument files. I'm not on 10.4 so I can't verify this, however. The wiki contains the most detailed technical info on NeoLight.
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Tue Jan 24, 2006 9:14 pm Post subject:
I have no idea what the X11 developers are doing with OOo 2.0, but I do have enough experience to know that having different applications and importers claiming the same UTI type mapping tends to really confuse the Spotlight importers.
If the OOo 2.0 X11 bundle plist claims the same UTI types, whether or not the NeoLight indexer gets invoked will depend on when the underlying LaunchServices database got last updated as to what application claims to be the "owner" of a UTI type.
Sorry to be so harsh, but if they're claiming types and not including my plugin, it's they're fault. It's If the extensions get appropriately mapped to the NeoLight importer OpenDocument formatted docs should work, to my knowledge.
I can't fix Apple bugs nor conflicts caused by our friends at OOo/Sun Microsystems.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
