1. a good ASCII Character map?
Heya all!
Unfortunatly, all the ASCII character maps I see are all the standard
ASCII-127 maps (Which Windows decides to use) and in these I
can't seem to find what character EOF is... (My dad said it was FF,
but that didn't come out true... might've been in ASCII-255...)
So, if I can't use the EOF character, how would I stick EOF at a
certain part of the file?
TIA,
--"LEVIATHAN"
2. Re: a good ASCII Character map?
On 13 Jan 2001, at 15:21, LEVIATHAN wrote:
> Heya all!
>
> Unfortunatly, all the ASCII character maps I see are all the standard
> ASCII-127 maps (Which Windows decides to use) and in these I
> can't seem to find what character EOF is... (My dad said it was FF,
> but that didn't come out true... might've been in ASCII-255...)
>
> So, if I can't use the EOF character, how would I stick EOF at a
> certain part of the file?
I'm not sure what you are trying to do, cause if you put in a DOS EOF, dos
may not read the entire file. But if you are using one file to hold many
bitmaps, and defining your own eof, here's several options:
1) make all the bitmaps the same size, by padding them out, and then
each bitmap will begin at multiples of size and end at multiples of size.
This will make replacing, deleting, or rearranging bitmaps a lot easier too.
2) when you save the files, make sure there is no byte 255 (for example),
then you can use a 255 as your terminator. Or use any byte you wish that
will not appear in your bitmaps.
3) don't save all the bitmaps as one file, use as many files as you want on
the harddrive. When the program starts, read them all in, each as a
subsequence in your main bitmap sequence. That way, you can organise
them when you read them in, they are all in memory, and the difference in
size is not a factor. So the road texture is MainSeq[Road][Texture], road
edging is MainSeq[Road][Edge], and the lawn is MainSeq[Lawn], etc..
Kat
3. Re: a good ASCII Character map?
- Posted by Euman <euman at BELLSOUTH.NET>
Jan 13, 2001
-
Last edited Jan 14, 2001
ASCII
dec = 255 hex = FF name = EO (end of)
sometimes refered to as phantom space
EDCDIC
dec = 55 hex = 37 name = EOT (end of txt/transmit)
or IBM
dec = 3 hex = 03 name = ETX (end of txt)
etc..etc.. BS
There are alot of real easy ways to do what I think
your trying to do, the easiest being.
seek to the end of the file, grab the length of the file (in bytes) and
store the length value in the file
i.e: {{{3}123},{{4}1234}}
I want to help, so give me an example.
euman at bellsouth.net
----- Original Message -----
From: "Kat" <gertie at PELL.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Saturday, January 13, 2001 18:53
Subject: Re: a good ASCII Character map?
> On 13 Jan 2001, at 15:21, LEVIATHAN wrote:
>
> > Heya all!
> >
> > Unfortunatly, all the ASCII character maps I see are all the standard
> > ASCII-127 maps (Which Windows decides to use) and in these I
> > can't seem to find what character EOF is... (My dad said it was FF,
> > but that didn't come out true... might've been in ASCII-255...)
> >
> > So, if I can't use the EOF character, how would I stick EOF at a
> > certain part of the file?
>
> I'm not sure what you are trying to do, cause if you put in a DOS EOF, dos
> may not read the entire file. But if you are using one file to hold many
> bitmaps, and defining your own eof, here's several options:
>
> 1) make all the bitmaps the same size, by padding them out, and then
> each bitmap will begin at multiples of size and end at multiples of size.
> This will make replacing, deleting, or rearranging bitmaps a lot easier
too.
>
> 2) when you save the files, make sure there is no byte 255 (for example),
> then you can use a 255 as your terminator. Or use any byte you wish that
> will not appear in your bitmaps.
>
> 3) don't save all the bitmaps as one file, use as many files as you want
on
> the harddrive. When the program starts, read them all in, each as a
> subsequence in your main bitmap sequence. That way, you can organise
> them when you read them in, they are all in memory, and the difference in
> size is not a factor. So the road texture is MainSeq[Road][Texture], road
> edging is MainSeq[Road][Edge], and the lawn is MainSeq[Lawn], etc..
>
> Kat
>
4. Re: a good ASCII Character map?
Your question would be, "What is the DOS EOF character?".
The answer to the question is character 26.
On Sat, 13 Jan 2001 15:21:28 -0800, LEVIATHAN <leviathan at USWEST.NET> wrote:
>Heya all!
>
>Unfortunatly, all the ASCII character maps I see are all the standard
>ASCII-127 maps (Which Windows decides to use) and in these I
>can't seem to find what character EOF is... (My dad said it was FF,
>but that didn't come out true... might've been in ASCII-255...)
>
>So, if I can't use the EOF character, how would I stick EOF at a
>certain part of the file?
>
>TIA,
>
>--"LEVIATHAN"
5. Re: a good ASCII Character map?
Leviathan:
You may want to check the ExtendedCharacterMap, by Sony Arianto Kurniawan
(AriTech Development Indonesia). Very complete and flexible. Available at
most download sites, and also at his home page,
http://aritechdev.hypermart.net/ecm.htm. Req. Win95, no install -just unzip
& copy.
Gerardo E. Brandariz
----- Original Message -----
From: LEVIATHAN <leviathan at USWEST.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Saturday, January 13, 2001 8:21 PM
Subject: a good ASCII Character map?
> Heya all!
>
> Unfortunatly, all the ASCII character maps I see are all the standard
> ASCII-127 maps (Which Windows decides to use) and in these I
> can't seem to find what character EOF is... (My dad said it was FF,
> but that didn't come out true... might've been in ASCII-255...)
>
> So, if I can't use the EOF character, how would I stick EOF at a
> certain part of the file?
>
> TIA,
>
> --"LEVIATHAN"
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
6. Re: a good ASCII Character map?
Heya!
> seek to the end of the file, grab the length of the file (in bytes) and
> store the length value in the file
>
> i.e: {{{3}123},{{4}1234}}
>
> I want to help, so give me an example.
Basically, I'm trying to stick an EOF before the EOF, aka "trimming
the file". Nothing I tried, including 26 and 255 and even -1 worked,
so I'm pretty stuck on trying to trim the file like that. Can you help?
TIA,
--"LEVIATHAN"
7. Re: a good ASCII Character map?
Hello LEVIATHAN
I submitted the below example to the list for a prior question on reading 80
bytes at a time from a file
I'm still confused as to why you would need an
EOF Char before the end of the file.
Because, if there were an EOF Char there would be no
way to read past that point, rendering the rest of the file
useless.
I am not sure but, you could try to useing seek.
Kat mentioned one way, Pad the file to a certain length
that way you could use the below example real easy
by replaceing 80 (in the example) with the length you need.
</snip>
include get.e
include file.e
object junk
atom ad
integer fn, file_length, last_n_bytes
sequence seq
seq = {}
fn = open(" filename_here.ext" , "rb")
junk=seek(fn,-1)
file_length=where(fn)
junk=seek(fn,0)
ad = floor(file_length / 80 )
last_n_bytes = file_length - (ad * 80)
for x = 1 to ad do
seq = append(seq, get_bytes(fn, 80))
end for
seq = append(seq, get_bytes(fn, last_n_bytes))
<snip\>
if this still isnt what you want, send me a couple of the
files your working with and I certainly will take a look.
euman at bellsouth.net
----- Original Message -----
From: "LEVIATHAN" <leviathan at USWEST.NET>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Sunday, January 14, 2001 06:28
Subject: Re: a good ASCII Character map?
> Heya!
>
> > seek to the end of the file, grab the length of the file (in bytes) and
> > store the length value in the file
> >
> > i.e: {{{3}123},{{4}1234}}
> >
> > I want to help, so give me an example.
>
> Basically, I'm trying to stick an EOF before the EOF, aka "trimming
> the file". Nothing I tried, including 26 and 255 and even -1 worked,
> so I'm pretty stuck on trying to trim the file like that. Can you help?
>
> TIA,
>
> --"LEVIATHAN"
>
8. Re: a good ASCII Character map?
Now I understand. I didn't know why you wanted EOF.
That won't work. This is my best explanation.
1. Create a small text file named test.txt
2. Now open the file set the value of the first byte to 26.
3. Close the file. (The file size will still be the same.)
4. Issue the following DOS command.
"C:\>type test.txt>test2.txt"
5. Look at the size of the new file. (test2.txt)
You should now be aware that the file was created in a
non-binary method.
The file size will be either 1 or 0 bytes.
I don't know how you can shorten the length of a file without.
making a copy of it excluding the unwanted portion. :(
I would like to know the solution if you find it.
Lucius L. Hilley III
On Sun, 14 Jan 2001 03:28:42 -0800, LEVIATHAN <leviathan at USWEST.NET> wrote:
>Heya!
>
>> seek to the end of the file, grab the length of the file (in bytes) and
>> store the length value in the file
>>
>> i.e: {{{3}123},{{4}1234}}
>>
>> I want to help, so give me an example.
>
>Basically, I'm trying to stick an EOF before the EOF, aka "trimming
>the file". Nothing I tried, including 26 and 255 and even -1 worked,
>so I'm pretty stuck on trying to trim the file like that. Can you help?
>
>TIA,
>
>--"LEVIATHAN"
