File Diff problem

Laffs · #1 05-13-2005, 12:20 PM

In the attached zip file is 2 files..

Now the one thats labled "WORKING" is the one that was made in the UI builder
The other one was generated from VB

Everything tells me that the 2 files are identical !!

But yet the generated one just will not work, In game it has no frame or background and wont display the harvest info.... In the UI builder after notes page 5 it includes the rest of the mainhud files under the parent page..

Now I know from past exp that there is usualy either </Page> or /> missing for it to do that but far as win merge tells me and after comparing the 2 myself this does not seem to be the case

I would appriciate it if one of you guys could have a look at the 2 files for me and maybe spot what is wrong...

Thanks

***Dolby*** · #2 05-13-2005, 12:26 PM

Your right the files are identical... I checked them with beyond compare and there is no difference.

You got me, hopefuly some one else can figure it out.

Laffs · #3 05-13-2005, 12:46 PM

Thanks for running a check Dolby..

Anyone else got any ideas?

ger · #4 05-13-2005, 12:46 PM

The files are identical…except for one thing: they aren't saved in the same file format. One is in UTF-8 as expected, the other seems to be ASCII.

Laffs · #5 05-13-2005, 12:50 PM

How the hell did you find that out ?

I guess the working one is in UTF-8 huh ?

*EDIT*

Ah oks I see now how you figured that out look at the encoding lol

Hum problem now is how the hell to get the VB to output to UTF-8 ... The last one did np's

***Dolby*** · #6 05-13-2005, 03:13 PM

Quote:

Originally Posted by ger

The files are identical…except for one thing: they aren't saved in the same file format. One is in UTF-8 as expected, the other seems to be ASCII.

Ger is the man! Never thought to look at that.

Laffs · #7 05-13-2005, 04:08 PM

Yup I didnt think of looking at that either lol...

Well I checked and the VB should be making UTF-8 files me using all the right IO commands but they keep coming up as ANSI

Had a look at a few others they are in that encoding as well, but they seem to work fine its just this one lol

**Zonx** · #8 05-13-2005, 06:05 PM

Lol, first thing I thought to check but then I saw Ger beat me to it.

Laffs, its probably easier to have your VB write acceptable ASCII. Open the UTF-8 version in WordPad and save it ONCE. This should convert it to an ASCII format you can use as a basis for your script. Typical changes are quotes, apostrophies, ampersands.

Note: once a file is in ASCII, you don't want to save it in UIBuilder. Saving it in UIBuilder results in a progresive translation degeneration issue as it tries to re-convert the ASCII & into &

Laffs · #9 05-13-2005, 10:19 PM

Thanks for that... But that is somthing I know... (no disrespect ment)
the VB is set up to save in the correct format but it aint lol

I have cut the code from the VB output into the twin file.. and all works well ... of course because of the encoding issue... Eq just seems to have problems with whats contained within the harvesting pages.. Looks like I gotta just rewrite them insted of using existing... seems to be the </Page> /> tags still that cause the problems there.... This all go's well deep and I have tested / F%*^D about with them them all, and got some interesting results to say the least lol

Best of it is this has got to be the most basic VB exe ever, lamo I mean apart from the GUI , the code is only 1 line long on the button LOL ... the rest is either user text input or static / hardcoded if you like (Yeh thats it !! , Hardcoded, Hehe, Aka its not my F-up)

I can see me sending the source to Ger likes

, as he is the main man, for this stuff ....... Failing that Its rewrite the harvesting info in a format that will work =/

ger · #10 05-14-2005, 10:11 AM

I'm willing to take a look at the source if you'd like, although my grasp of VB is pretty basic (no pun intended.) I'm more of a C# kinda guy.

For the record, I noticed the format difference by doing a binary compare in UltraEdit-32, saw one file had a single-character linebreak (CR or LF) and the other had a twin-character linebreak (CR and LF.) From there it was a pretty short leap of logic.

Laffs · #11 05-14-2005, 10:35 AM

Thanks...

I will send you a linky to the source shortly... I had noticed that the linebreaks seem to have somthing to do with the type of encoding eg with or without a signature and stuff.. Only reason I used VB was it saved one hell of a lot of typing lol as I was able to paste over 90% of the output code into hidden textboxes

Anyways you will see this when you get time to have a look