> On Tuesday, July 16, 2002, at 09:32 PM, Joshua D.Orr wrote:
>> I am apparently having a extremely difficult time getting terminals
>> converted to the Aleph One format. When I do this Hex won't open it
>> and it is just a blank terminal in Aleph One but Pfhorge can read and
>> covert the terminal back from the Aleph One formated map just fine?
> Here's how Hex! works:
> It creates a two-fork file, with the data fork containing the
> terminal data to be included, and with the resource fork containing
> source information that Hex! uses for editing and for composing the
> includable terminal data.
> So that's why Hex! won't work on included terminal data; the
> original resource-fork contents are lost.
> I don't know if the creator of Hex! ever documented the
> resource-fork format, let alone released its source code, however; it
> might be helpful for constructing some new terminal-data editor.
Ok, I tried adding a terminal section with a type that uses a picture and
made it picture zero.
It seems that Aleph One can read it because it displays a blank section
(Information Section) and then a picture sections with picture zero not
found (there was no picture in the resource fork, so this is accurate). But
it does not display the text.
Pfhorge can read the text however, so I am thinking maybe the text is
encoded wrong? It seems like it is reading the terminal data, but not
reading the text. I am not sure what is happening. I will look further
-Joshua D. Orr-