Ask Your Question

cosmos's profile - activity

2014-07-06 14:59:00 +0100 received badge  Nice Question (source)
2013-10-23 03:44:43 +0100 received badge  Famous Question (source)
2013-10-23 03:44:43 +0100 received badge  Notable Question (source)
2013-08-12 13:01:30 +0100 received badge  Popular Question (source)
2013-08-09 13:32:18 +0100 received badge  Scholar (source)
2013-08-09 13:32:01 +0100 received badge  Famous Question (source)
2013-08-09 11:55:07 +0100 received badge  Famous Question (source)
2013-08-09 11:55:07 +0100 received badge  Notable Question (source)
2013-08-09 11:55:07 +0100 received badge  Popular Question (source)
2013-08-09 11:50:08 +0100 asked a question LibO 4, gpo installations: what has changed over 3.6?

I have been deploying LibO (and Oo before that) in Active Directory networks for some time now. I always installed LibO as follows:

  1. First did a "msiexec -a <path to="" libo.msi="">" in order to perform an administrative install to a network path.
  2. Then, I opened the included smaller MSI file with Orca and made a huge number of changes in order to disable quickstarter and make sure only a single dictionary (Greek) got installed, since silent installations via gpo would cause ALL dictionaries to be installed.

I followed this approach till 3.6.6.2. Has anything changed in 4.1.0?

2013-08-09 11:50:08 +0100 received badge  Taxonomist
2013-07-18 21:43:00 +0100 received badge  Famous Question (source)
2013-02-19 02:23:37 +0100 received badge  Notable Question (source)
2013-02-19 02:23:37 +0100 received badge  Popular Question (source)
2013-02-17 05:49:11 +0100 received badge  Nice Question (source)
2012-11-27 22:39:07 +0100 received badge  Notable Question (source)
2012-07-25 19:03:43 +0100 received badge  Self-Learner (source)
2012-07-25 19:03:43 +0100 received badge  Teacher (source)
2012-06-22 11:31:07 +0100 received badge  Popular Question (source)
2012-06-20 00:14:14 +0100 received badge  Student (source)
2012-06-10 19:10:40 +0100 answered a question Re-creating windows search filters

This is a bug, that will be resolved at 3.5.1. See https://bugs.freedesktop.org/show_bug.cgi?id=47949

2012-06-10 19:08:25 +0100 commented answer Install via group policy: where are the language transform trans_xx.mst files

Yep, I'm sure.

2012-06-10 19:08:03 +0100 commented answer Install via group policy: where are the language transform trans_xx.mst files

Nope, it doesn't. Ever since installable files are MSI ones, there are not trans_XX files given

2012-06-10 19:07:12 +0100 commented answer Install via group policy: where are the language transform trans_xx.mst files

I know about the latter; I am one of the bug contributors. Seems like part of it is by design and the newer libo does not utilize trans_XX files anymore.

2012-05-04 07:29:22 +0100 received badge  Editor (source)
2012-05-04 07:23:15 +0100 answered a question Re-creating windows search filters

Okay, seems like I was eager to open a case here without searching: this has been reported at http://en.libreofficeforum.org/node/338?destination=node%2F338&1b76_name=6a

There is also an open bug report for 3.5.x as Bug 47805. A workaround, as presented by the bug reporter is the following:

Manually registering the following dlls (win admin rights) solves the problem: regsvr32 "C:\Program Files (x86)\LibreOffice 3.5\program\shlxthdl\ooofilt_x64.dll" regsvr32 "C:\Program Files (x86)\LibreOffice 3.5\program\shlxthdl\shlxthdl_x64.dll"

2012-05-04 07:11:24 +0100 asked a question Re-creating windows search filters

Hello all,

on a couple of Windows 7 systems I had installed a component from http://www.ifiltershop.com/sofilter.html to have windows search indexing for opendocument files. Unfortunately this never worked as promised. In fact, it seemed to index only some file properties and not the actual content of each file. At the time I considered this a limitation.

Some days ago, after making a new installation of LibO 3.5.2 I happened to see that now Windows search could index also the content of odf files by using c:\program files\libreoffice 3.5\program\shlxthdl\ooofilt.dll

With these good news, I went back to my 2 win7 boxes, uninstalled the so-called standalone Staroffice/openoffice ifilter and even uninstalled/re-installed Libreoffice. Now's the strange part. On one of the system everything went fine, in windows search odf files got associated with ooofilt.dll for indexing. However, on the other system nothing happened! In indexing properties of windows search and for all ODF files it is stated that "No associated IFilter exists". Any ideas on what can be done to repair this?

2012-05-04 07:01:40 +0100 answered a question Install via group policy: where are the language transform trans_xx.mst files

I am a network administrator for my LAN and have been downloading/installing Oo for the last 4 years or so. So I (think I) know the procedure pretty well more or less.

But for the record and to answer your question, I always download from http://www.libreoffice.org/download/. The specific file I had downloaded was named LibO_3.5.2_Win_x86_install_multi.msi

Does this MSI contain the trans_XX.mst transforms?

2012-05-02 07:37:40 +0100 asked a question Install via group policy: where are the language transform trans_xx.mst files

In the .exe bundled installation packages, one could unpack and find inside trans_XX.mst transform files, one for each support language. I used one of them to transform my group policy-based installation, as follows, in order to install Greek:

msiexec /i <libo.msi> TRANSFORMS=trans_el.mst /qn

(The installation was made via a group policy, but in essence that's what happened).

In LibO 3.5 no such files exist. How should I install a single language in this case?

2012-05-02 07:30:27 +0100 asked a question Can I set ODF 1.0 as default via group policy during installation?

There has been a policy to use ISO/IEC 26300:2006 OpenDocument files, which essentially corresponds to ODF 1.0. LibreOffice 3.5.2 will be installed on our systems via group policies.

Is it possible to set ODF 1.0/1.1 as the default format, by utilizing an MSI file property?