The Visualisation Toolkit (VTK) release is currently version 9.0.0., see here. VTK website provides this file format description, which is titled "VTK Version 4.2". Paraview also links this github page, which seems to be the same as the Version 4.2 description, and to the 4.2-description.
What is the most recent VTK-File Format description? Or is the linked 4.2-description the one that is used in the most recent release version (currently 9.0.0)?
This is the most recent version of the format and what is being used in VTK 9.0.0.
This information is not documented anywhere yet.
Related
Some time ago (some years) my company purchased a license for the library called LibXL.
Previously the application was built on CentOS 6.5 without troubles.
I have currently set up a new system (Ubuntu 16.04) but LibXL returns a warning:
Created by LibXL trial version. Please buy the LibXL full version for removing this message.
Version of this library is exactly the same - I just copied .so file.
Application is built using C language.
License setting code:
xlBookSetKey(book,"<name>", "linux-<characters>");
Do we need to buy a new license key?
Maybe some operating system settings are wrong? or maybe I missed some configuration file? (I just copied the libxl.so file to the right place).
A couple years ago I wrote a small utility program for my employer, which accessed a Couchbase cluster via the Couchbase C SDK. I've just returned to it to add some new features, installed the Couchbase C SDK on my Ubuntu 20.04 development system via the instructions found here, and tried to compile my code, and it complains that it can't find libcouchbase/n1ql.h. When I checked, sure enough, the file is nowhere to be found on my machine.
I've tried installing all of the packages provided by their repository, none of which seem to provide that file. I've also tried removing them all and installing libcouchbase from source, with no luck (the instructions seem completely out of date); searched it manually but that file isn't in there either. Even grepping for other items that I know have to be in there, like lcb_N1QLHANDLE, doesn't turn up anything.
There's obviously something I'm missing, but I can't even see the shape of it. Have they moved the N1QL code to a separate repository? Gotten rid of it entirely? Renamed it without updating the documentation?
The utility you wrote was probably built using an older version of libcouchbase than what's in the "master" branch on GitHub. If you check out the tag 2.10.7 you can see the n1ql.h header here:
https://github.com/couchbase/libcouchbase/tree/2.10.7/include/libcouchbase
Installation instructions and other documentation for version 2.10 are here:
https://docs.couchbase.com/c-sdk/2.10/start-using-sdk.html
GIMP's native file format has evolved during the years. If there is an external tool that is capable to read *.xcf files then it still can happen that the tool cannot read the file, complaining about unknown file format, or something like this:
read XCF: unsupported file version: v011
How can I save the image into the older version of the *.xcf format?
GIMP is smart enough and alerts you when you save the file.
This alert is displayed when your image contains something that GIMP cannot save into the old format, therefore the new version is needed. If you want to save the old format then you need to remove everything from your image that is too modern and impossible to store in an older format of *.xcf.
GIMP also tells what feature in the image is/are exactly the one/ones that make GIMP to use the newer version.
In the above picture, you can see that the layer mode setting is not compatible with the old format, therefore GIMP will use the new one.
In order to get rid of this message, you need to change the layer mode by right-clicking each layer, and change them in the Edit Layer Attributes -> Mode drop-down from Normal to Normal (l) or similar. The drop-down shows only the Default layer modes by default but if you click the little icon on the right side of the drop-down then you can switch to the Legacy layer modes.
If you try to save the *.xcf again then the above message disappears and the older version of *.xcf format will be used.
Maybe you still have some other settings in your image that are not compatible with the old file format. You need to hunt them down one-by-one but sooner or later you will be able to save in the older format.
Firefox store its default configuration information in omni.jar (older version) or omni.ja (later versions). Both omni.jar and omni.ja just are zip file format. So we can use many programs/libraries to compress or decompress them.
I want to get some default information of Firefox. So I must read some file in those omni file. I have used 7zip program to see the content of omni or MiniZip/Zlib library to read omni in my program.
With later version, omni.ja, it is read well. But with older versions, MiniZip cannot open the omni.jar file. Then I use 7zip to open those file: omni.ja was ok, omni.jar was fail. But with some other program, ex: WinRar, WinZip, ... both omni file is opened well.
I was google and get some information: with older version, Firefox has created the omni.jar file (a zip file format) with no zip standard. blah blah. But why WinRar or WinZip can read.
Anyone can help me to get MiniZip read omni.jar file with no error?
Thank you very much.
The solution is pretty simple: Your "old" omni.jar is broken. My omni.jar starts with PK.
I suggest to download Firefox from the official archive once more.
[EDIT] It seems that different builds of Firefox use different tools to built the ZIP archive. The en-US version uses a ZIP-like format which doesn't start with PK. While in theory the file format is valid (it contains data followed by the list of entries), almost no tool really supports this format (so WinZIP and WinRAR are the exceptions).
This intention is reflected by the rename of omni.jar to omni.ja: It's not encrypted, it's just a ZIP format that isn't widely supported and the US Firefox developers don't want to change this.
The other developers (for example for the de version) use official tools to build the omni archive so those versions can be modified with any tool.
You will need to find a way to update the archive using WinZIP / WinRAR or you need to download the original firefox sources and add your patches to the build process.
I have one library using one function in the PnP configuration manager library. Therefor, the cfgmgr32.lib is included in our build.
But I don't know where it came from, nor do I know what license is attached to it. I assume it was in the DDK.
Could one label this as "Proprietary" software?
First I assume that you are talking about a lib that is part of the windows driver kit:
http://msdn.microsoft.com/en-us/windows/hardware/gg487428
Per: http://msdn.microsoft.com/en-us/windows/hardware/gg487463 "How to get the Windows DDK"
I end up there http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff and a download url of: http://download.microsoft.com/download/4/A/2/4A25C7D5-EFBE-4182-B6A9-AE6850409A78/GRMWDK_EN_7600_1.ISO ...
This is a large ISO image.
Once you have that, the terms of the license should be detailed in the ISO somewhere.
Per: http://www.microsoft.com/taiwan/whdc/devtools/wdk/RelNotesW7.mspx#EPD
"The contents included in the Windows Driver Kit (WDK) are licensed to you, the end user. Your use of the WDK is subject to the terms of an End User License Agreement (EULA) that accompanies the WDK and is located in the WDK installation directory. The name of the file is License.rtf. Before you access or use the WDK, you must read and accept the terms of the EULA. If you do not agree to the terms of the EULA, you are not authorized to use the WDK."
So get the ISO, install and get the exact license.
Also the doc is there:
http://msdn.microsoft.com/en-us/windows/hardware/gg487458
this is smaller and should also contain license terms.