Rappa
Guest
|
|
« on: February 17, 2009, 10:04:15 pm » |
|
Hi
My table include some DTE like this
46=yo 5F=re
I have the script: you are
But Atlas don't insert it as 46XX Yy5F, it insert as: y+o+u a+re
How can I remedy this?
Also, I tried drawing 2 letters in the same tile, so I have 46=yo,... (notice this is NOT DTE, just 1 tile with 2 letters) but Atlas doesn't insert yo, too. It insert y+o.
I'm a hopeless sad panda!
|
|
|
|
Ryusui
Guest
|
|
« Reply #1 on: February 17, 2009, 11:37:43 pm » |
|
Atlas is powerful and flexible, but it isn't magical. Unless the game has been modified to recognize the dictionary codes and print the appropriate output, you'll get gibberish, no matter what you put in the table file.
|
|
|
|
KingMike
Guest
|
|
« Reply #2 on: February 18, 2009, 01:05:07 am » |
|
It sounds like he's saying Atlas doesn't support DTE. So, where he wants Atlas to insert $46, it inserts the single tile codes for y and o.
|
|
|
|
Ryusui
Guest
|
|
« Reply #3 on: February 18, 2009, 01:18:48 am » |
|
Which is odd, because it has no issue inserting MTE for Breath of Fire 2.
|
|
|
|
Lenophis
Guest
|
|
« Reply #4 on: February 18, 2009, 01:55:24 am » |
|
I don't know if this is the issue, but does your DTE come before or after the single-byte characters?
|
|
|
|
Jigglysaint
Guest
|
|
« Reply #5 on: February 18, 2009, 02:49:55 pm » |
|
Just do it by hand in a hex editor. Sometimes doing somthing by hand is the best way.
|
|
|
|
Karatorian
Guest
|
|
« Reply #6 on: February 18, 2009, 11:42:15 pm » |
|
Just do it by hand in a hex editor. Sometimes doing somthing by hand is the best way. Really now? I figured the best way was to write your own tools that do what you need. That's what I always do when the generic utils fail me.
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #7 on: February 19, 2009, 01:27:58 am » |
|
I don't know if this is the issue, but does your DTE come before or after the single-byte characters?
I remember I had an issue like that a while back. I don't remember how I fixed it, I only remember getting pissed off and rebuilding the table from scratch.
|
|
|
|
Rappa
Guest
|
|
« Reply #8 on: February 19, 2009, 03:02:15 am » |
|
I found a way to remedy this. My solution is to include the - character in DTE. For example, these are in my table 46=y-o 5F=r-e So my script is: y-ou ar-e This way Atlas can do the right way. 46XX YY5F. Thanks for reading. Just do it by hand in a hex editor. Well, this is a solution too. But I guess you'll need a ton of free time.
|
|
|
|
Ryusui
Guest
|
|
« Reply #9 on: February 19, 2009, 03:12:34 am » |
|
I just thought of what could be the problem: priorities.
Are the DTE codes before the individual letters in your table, or after them? If they're after, they need to be before.
|
|
|
|
Rappa
Guest
|
|
« Reply #10 on: February 19, 2009, 03:37:56 am » |
|
I just thought of what could be the problem: priorities.Yes, I think so. Now the problem is over.
|
|
|
|
Tauwasser
Guest
|
|
« Reply #11 on: February 19, 2009, 04:12:59 am » |
|
I don't know if this is the issue, but does your DTE come before or after the single-byte characters?
Just wanted to make sure everybody got that Reply #4 was the magic solution, already. cYa, Tauwasser
|
|
|
|
Kajitani-Eizan
Guest
|
|
« Reply #12 on: February 20, 2009, 10:09:52 am » |
|
I found a way to remedy this. My solution is to include the - character in DTE.
For example, these are in my table
46=y-o 5F=r-e
So my script is: y-ou ar-e
ughh. this way makes things way too painful >_> I just thought of what could be the problem: priorities.
already beaten to the punch, there I don't know if this is the issue, but does your DTE come before or after the single-byte characters?
|
|
|
|
DaMarsMan
Guest
|
|
« Reply #13 on: February 20, 2009, 11:45:57 am » |
|
I never knew Atlas used table order for priorities. That makes things easier.
|
|
|
|
Klarth
Guest
|
|
« Reply #14 on: February 22, 2009, 05:36:31 am » |
|
I never knew Atlas used table order for priorities. That makes things easier.
I never did either. "It's not a bug, it's a feature." *wonders how that happened instead of the "pick the longest entry" methodology*
|
|
|
|