Posted by
Fred Damen on
Apr 07, 2020; 5:51am
URL: http://imagej.273.s1.nabble.com/Re-Odp-microscope-name-retrieval-using-only-the-image-file-tp5023180p5023184.html
Greetings,
To look at, search, and figure out nonhuman readable files I use 'gvim',
vi improved, vim.org. Works on all platforms. Gvim has a readonly mode,
gvim -R or view, that will not overwrite the file. Once the image file is
opened, use Tools>Convert to HEX, which will show the file in standard
hexdump format allowing you to search for the string you are looking for.
For the hardcore you can also use this to edit these files (if you opened
them writable of course). Also check out File>Split Diff With...
Since I am on the subject of Gvim, I would like to make two requests: In
Compiler.java:
Please remove the line:
errors.setFont(new Font("Monospaced", Font.PLAIN, 12));
from void showErrors(String s).
The Editor window that the error messages are displayed in remembers what
font style and size that I told it to use before... but I have to use Make
bigger/Make smaller for it to display as such.
And, could there be an option to allow the compiler to send the error
messages to stderr, as it normally would when run from the command line.
I would like to use gvim as the edit/compile/run. Gvim has a nice
quickfix functionality, albeit requires access to the compiler syntax
error messages on stderr.
Note to do "Compile and Run..." from Gvim and/or to .gvimrc or just
execute: :map <silent> <F9> :silent w<bar>!imagej -o -e 'run("Compile and
Run...","compile=%:p");'<CR>
(one line) and then use F9 instead of Ctrl-r. It helps to run gvim from
the directory you want the File Browser to default to as ImageJ does not
seem to remember the last directory visited running the plugin in this
way.
Thanks in advance,
Fred
On Mon, April 6, 2020 11:14 am, gkowalsky6AtGmail wrote:
>>
>> As it was already said, which metadata is recorded is dependent on
> integrator/installer/end-user configuration and software defaults. However,
> my recollections from working with old and legacy integrated systems are
that some information was written into the headers or footers of the
image file itself. In these cases, I opened the image file in any
simplest ASCII/ANSI/Unicode text editor and just tried to find anything
resembled human language.
>
> For this, any code editor capable of opening large files as simple text
would work. On Windows, right-click on file icon, select "Open with..."
-> "Choose default program..." etc. Make sure always to UNCHECK the
"Always use the selected program to open this kind of file", in order
not to break local file associations.
>
> NOTE: for additional safety, open a copy or backup of file in question, not
> the originals. In this case, one's not risking to corrupt the original data
> file because of text editors' bugs or local workstation failure.
>
> I do understand it could be a time consuming task...
>
> Best of luck,
> Grr
>
> ----
> GK_at
http://gikscientific.com/...
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html