willysr,

Your blog post states that installpkg causes the problem,
not rpm2tgz. Or perhaps, I can't understand your English.

Thank you, willysr. Like many, I am rather inertial and unwilling to learn, that's why I did not try out the SlackBuild script so far.

By the way, I checked if some other OpenOffice related *.xml files were cut to *xm files.
Simple way to check (after updatedb is done): slocate .xm |grep open|sed /xml/d

showed that there are many *xm files in:
/opt/openoffice.org/basis3.0/share/config/soffice.cfg/modules/

I renamed them back to *.xml, just in case.
Anyway, this did not help me to get spell checking.

I have just reinstalled OO3 (with import of OO2 settings) using the original Slackbuild script build of the package after first doing removepkg and manually deleting /opt/openoffice.org3 and ~/.openoffice.
I then opened Writer and used Tools -> Options -> Language Settings -> Languages -> Locale setting to set my locale as English (Australia) followed by Tools -> Extention Manager -> Get more extensions here to download my preferred English(Australia) dictionary which I then moved to /opt/openoffice.org3/share/extension/install/
After restarting Writer, I used Tools -> Extention Manager -> Add to install the dictionary (and associated thesaurus and hyphenation dictionary) and checked with Tools -> Options -> Language Settings -> Languages as well as Writing Aids that all was OK.
I have looked and found no *.xm files.

My conclusion is that the original Slackbuild was fine ( Thanks rworkman!). My initial problem came from a lack of a documented procedure which was not helped by the outdated and so misleading documentation within OO3.

That never worked for me, only setting it in the menu system got it going.

I don't think it matters where you download the actual dictionary .oxt file, and you shouldn't have to place it in /opt/openoffice.org3/share/extension/install/. When you install it via the extension browser you just navigate to where the file is under your home directory and then add it. The files that are actually used will be under ~/.openoffice.org in a directory called unopkg or something similar. Basically it mirrors what you see in the global installation directory, but just for one user.

i'm sorry. Which part?

I'm sorry. I must have set it enabled on OOo 2 and the settings were transferred during migration to OOo 3.

After changing this, you should delete your .openoffice.org and restart your OOo. If it doesn't help, then i guess manual installation of the dictionary files are the only way

I now tried your tip to get spell check.
***if the autospellcheck does not work, then you can install the dictionary manually via Tools > Extensions Manager***
and it worked.

Summary for people who do not like changes:
Use rpm2tgz on RPMS from openoffice.org as you did before;
after installation of the so-produced packages,
rename *xm files in /opt/openoffice.org/basis3.0/share/config/soffice.cfg/modules/
into *.xml files, and add dictionary as described above from /opt/openoffice.org3/share/extension/install/

Thanks, willysr.

your welcome
updated on my blog as well

I understand English very well. Your blog was incorrect.
It is not installpkg that caused the problem. Perhaps it
was rpm2tgz. I've built OOo-3.0 with a couple of different
SlackBuilds, and installpkg'ed each one, and have not had
one single .xml file changed to .xm

well, if you could point the location, i will correct it. Anyways, i have updated the blog for the solution for users who uses rpm2tgz. I hope it makes it clearer

Hello all, I'm Vinicius of willy's blog. At first, sorry about my english, I'm from Brazil.

I think I'm wrong about the "installpkg problem" affirmation. Maybe I just miss the right words, language problem
Follow my line of reasoning:

When using rpm2tgz and installpkg with the OOo RPMS, some file names get truncated, as akus noted. Renaming that default.xml file and removing OOo user profile solves the keys problem.

-> In my tests, using rpm2tgz and tar to unpack the tgz file doesn't cause the truncating. So I thought installpkg is the problem.
-> Changing installpkg to use tar-1.16.1 instead of tar-1.13 does not cause the file renaming, so I concluded tar-1.13 is the problem.
-> Unpacking the tgz file generated by rpm2tgz with tar-1.13 does also doesn't cause the problem, so I thought the problem is installpkg again.
-> Creating a tgz file with just that default.xml file at the same path and using installpkg with tar-1.13 doesn't cause the problem too, so I thought the problem is me

Sorry about something, and about writing errors...
Regards,

Vinicius

Vinicius,

Welcome to LQ!

We're glad to have you here!

I believe OpenOffice-3.0 is like most of the new releases. It
has some fresh bugs. We can count on our fellow Slackers to
find those bugs. And usually they also post a fix.

This thread for me is another affirmation of FOSS. If a minor bug is discovered it is usually patched in hours or days. Can other OSs claim this? ****cough, winders, cough*****
I do know how busy you are, man. Thanks for fixing this issue, Robby:-)
Slackware rules:-)