Now this is interesting! I wasn't considering huge image files, most just "ordinary" ones like photos, screenshots, or graphs that would be common images to want to include with, for example, a markdown document. I'll read up on your links. Thanks!
On Sunday, April 2, 2023 at 5:18:24 PM UTC-4 David Szent-Györgyi wrote: > On Sunday, April 2, 2023 at 3:55:31 PM UTC-4 tbp1...@gmail.com wrote: > > It seems to me that the main challenge would be for Leo to know just what > to have in the package. External files would be easy, but for example > image files - how to know about them could be a real challenge. I'm > thinking that an outline could contain an @resources node, where the user > could add anything that Leo didn't know about. Not ideal, but perhaps > necessary. > > > If you limit the scope of your work to compression and decompression of > files, you might consider the libraries available for 7-Zip > <https://en.wikipedia.org/wiki/7-Zip> - support for operating ystems > other than Windows requires one of the variants described there. If you > care about handling individual images or metadata from them, your task is > much greater and a great challenge. > > I know something of that challenge, since I earn my living supporting > software for life science microscopy. The number of formats used in that > field is enormous, the requirements that must be during acquisition are > distinct from those required thereafter for retrieval and analysis. > Acquisition can involve a great number of individual images, enough that > efficient writing to disk and reading back from disk can require a number > of individual files, with a separate file that describes the entire > dataset. > > Not that you would necessarily wish to use the formats designed for life > science microscopy of the open source software available for reading and > writing them, but here are links that might be of interest. > > OME-TIFF and OME-Big-TIFF: these support individual files with a great > number of images; the OME-Big-TIFF variant supports files larger than four > gigabytes. These, among others, are described under "OME Model and File > Formats <https://docs.openmicroscopy.org/ome-model/latest/>". Information > specific to OME-TIFF > <https://bio-formats.readthedocs.io/en/latest/formats/ome-tiff.html> is > available; documentation for the OME-TIFF file structure > <https://docs.openmicroscopy.org/ome-model/latest/ome-tiff/file-structure.html> > > is available also. > > Bio-Formats <https://bio-formats.readthedocs.io/en/latest/> is a > standalone Java library for reading and writing life sciences image file > formats. It is capable of parsing both pixels and metadata for a large > number of formats, as well as writing to several formats. C++ code is > available; I cannot speak to its condition and compliance with the current > standard for the format. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/bef585eb-b1bd-4b57-95dc-9c7a2884a27bn%40googlegroups.com.
