Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Terrence,

Terrence Enger schrieb:
Hello, all.

Now that my system holds more than one build from master, my
small mind is even more subject to confusion than it used to
be.  So, I wonder ...

(*) Is there an easy way to display the build id of
     soffice.bin to the sysout or syserr?  (Since I created
     my second work dir and did `git pull`, `git branch
     --verbose` in the first directory shows the later
     version.  Did I screw up creating the second work

(*) Is there an easy way to change the appearance of an
     execution of soffice, something like the application of
     a gnome theme changes all applications?

No answer to your questions, because I have only got WinXP. But other ideas:
You find the version information in the file program\version.ini (Windows here). It is a textfile, so it should be easily displayed.

You can edit the text, which is shown in the title bar of a running LO. This string is in share (that of top level)\registry\brand.xcd. It is node "Product" and therein node "ooName". So you can enter the information you want to see. That is shorter than opening Help>About.

In Windows I get the information via context menu from the file properties. Perhaps there exist something similar for Linux?

Kind regards

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.