On Thu, May 5, 2011 at 2:59 PM, Grant Edwards <grant.b.edwa...@gmail.com> wrote: >> Hmm, they work fine on my system, using Libreoffice 3.3.2 (with >> -templates). I get the "Fruit Depot" letterhead etc. :) > > I didn't enable Java support in Libreoffice, so that may be why the > wizards don't work.
Ah, I think you're right. I read recently that they are working on eliminating the reliance on Java (converting the wizards to Python, IIRC) but it's not there yet. These are my active USE flags for libreoffice: USE="cups dbus gtk java kde ldap nsplugin opengl templates" >> Looking at the config, I think it may only install the sun template >> pack for supported languages that are also in your LINGUAS. The sun >> packs are in en_US de it fr es hu. >> >> In my case, it is set to: >> >> LINGUAS="en en_US" > > Mine is "en_US". There are quite a few .ott files (329 to be exact), > but only two of them aren't underneath a directory named "wizard": > > $ equery files libreoffice | fgrep .ott | wc -l > 329 $ equery files libreoffice | fgrep .ott | wc -l 363 > $ equery files libreoffice | fgrep .ott | grep -v wizard > /usr/lib/libreoffice/basis3.3/share/template/en-US/forms/resume.ott > /usr/lib/libreoffice/basis3.3/share/template/en-US/officorr/project-proposal.ott Mine shows those two, plus all the Sun ones. Very strange! > It's sort of sad when you can't produce a business letter template > that's easy enough to use that it doesn't require "clippy" to step you > through it. The wizard is sort of a template-chooser-builder in the first step or two, you give it your specifications (do you want a logo? etc) and then it builds the blank template. You can skip the pages where it pre-fills in data with your name and address etc. I've not used it enough to say if it's good or bad. I suppose once you've created the layout that you like from the wizard, you could save it as a normal template. It doesn't look like the ebuild does anything other than enable the --with-sun-templates configure option, so any strange behavior beyond that is in the LO build system itself, I guess. But if the "templates" USE flag is dependent on some other condition, perhaps the ebuild should test for that to prevent this kind of thing.