Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
transformenator.jar | 2015-02-09 | 91.5 kB | |
readme.txt | 2015-02-09 | 1.6 kB | |
transformdirectory.bat | 2015-02-09 | 782 Bytes | |
transformdirectory.sh | 2015-02-09 | 699 Bytes | |
Totals: 4 Items | 94.6 kB | 0 |
New for this version: ===================== * New transforms: Canon ETW1 word processor, IBM Displaywriter, Multimate, Smith-Corona * New function: ExtractDisplaywriterFiles - extract EBCDIC files from Displaywriter 8" disk images * New function: ExtractSeawellFiles - extract files from Seawell DOS (early 6502-based DOS) 8" disk images * New function: ExtractMemoryWriterFiles - extract files from a disk image from an unknown word processor, possibly Xerox MemoryWriter * New function: ExtractSmithCoronaFiles - extract files from a disk image from Smith-Corona typewriters Transformenator introduction: ============================= Transformenation is something that should be possible to do with some rudimentary shell scripting. You should be able to run a binary file through sed or awk and have byte sequences change to different byte sequences. But you can't. You could probably run a file through a hex dumper, change hex values, then un-transform it back to binary. But that's kind of a pain too. The problem is that sed and awk work on lines, defined as things that are delineated by what they consider line ending characters like 0x0d or 0x0a. But what if your data stream contains 0x0d and 0x0a bytes - but you don't want them to count as line endings? What if you need to remove nulls, hex zeroes, or whatever you want to call them from a binary file or data stream? You're stuck. Maybe that's why you're here. Transformenator can help. Invocation: java -jar transformenator.jar transform infile outfile See http://transformenator.sourceforge.net for details.