Help - Search - Members - Calendar
Full Version: Text2Hex
MSFN Forums > Coding, Scripting and Servers > Programming (C++, Delphi, VB, etc.)

   
Google Internet Forums Unattended CD/DVD Guide
sweept
Aug 5 2008, 08:38 PM
all welcome.gif im looking for something that can replace a text line to hex line 1 to 1
that also distinguishes between capital to none capital letters in conversions.

here is an example of what i need

input:
HeLlOwOrLD
hOwArEyOUtOdAY

output:
480065004c006c004f0077004f0072004c0044
68004f00770041007200450079004f00550074004f006400410059


instead of spaces, use "00"

some editors tools .etc only offer hexdump
or
they will make conversion but all in one line none separated ..
.etc

what ill be interested is in a tool a batch that can possibly offer doing so through a command
also would be interested in some conversion tool that deals with splitting the lines .. can be a web tool too so long as it it outputs lines separately !

TIA
Mijzelf
Aug 6 2008, 03:36 AM
Copy this script to a .js file. Drop the text file to be converted on it, and it will create a .hex file.

CODE
var fso = new ActiveXObject("Scripting.FileSystemObject");

function TextToHex( inputfile, outputfile )
{
    while( 1 )
    {
        try{
            var inputline = inputfile.ReadLine();
            var outputline = "-";
            
            for( var i=0; i<inputline.length; i++ )
            {
                var character = inputline.charAt( i );
                if( ' ' == character )
                {
                    outputline += "00";
                    continue;
                }
                outputline += inputline.charCodeAt( i ).toString(16);
            }
            outputfile.WriteLine( outputline );
        }
        catch( e )
        {
            return;
        }
    }
}

function Parse( objArgs )
{
    for( obj=0; obj<objArgs.length; obj++ )
    {
        try{        
            var inputfile = fso.OpenTextFile( objArgs( obj ), 1 );
            try{
                var outputfile = fso.CreateTextFile( objArgs( obj ) + ".hex", true );
                TextToHex( inputfile, outputfile );
                outputfile.Close();
            }
            catch( e )
            {
                WScript.Echo( "Could not create " + objArgs( obj ) + ".hex\n" + e );
            }
            inputfile.Close();          
        }
        catch( e )
        {
            WScript.Echo( "Could not open " + objArgs( obj ) + "\n" + e );
        }
    }
}

Parse( WScript.arguments );



sweept
Aug 6 2008, 07:20 AM
thanks Mijzelf this looks really clean by code as far as i can tell i checked it out and seems to be doing what i was looking for
now there are 2 request i have for you!

1) that "00" gets added after each letter in output i can see reference in the code for that but with out an impact
2) output without "-" @ the beginning of each line (ignore this if this turns a problem)

this i s great thanks a lot!

small question: using this in batch ..

on some machines that are picky on scripts using reg tweaks to disable *.js it gets impossible to share or use this!

so does this mean it needs another coding language compiled to exe
-or can these kind of script be compiled to exe strictly, meaning to avoid having restrictions on file extensions like *.js .etc

if there is a simple way to get around this , please someone explain

TIA
crahak
Aug 6 2008, 07:54 AM
QUOTE (sweept @ Aug 6 2008, 09:20 AM) *
1) that "00" gets added after each letter in output

Ideally you don't want that, but rather proper unicode support: that's where the 00's normally come from, it's not just padding (having 00's for no reason would be kind of dumb). This script doesn't return UTF-16 encoded strings, and if you try passing a unicode-encoded text file instead (probably not what you want in the first place), it only writes "0" instead of "00", plus, it writes the byte order mark and all that to the file too. It might be helpful to know what you're doing all this for.

QUOTE (sweept @ Aug 6 2008, 09:20 AM) *
2) output without "-" @ the beginning of each line

Then replace
CODE
var outputline = "-";
by
CODE
var outputline = "";


QUOTE (sweept @ Aug 6 2008, 09:20 AM) *
on some machines that are picky on scripts using reg tweaks to disable *.js it gets impossible to share or use this!

Why on earth would be .js files disabled? or .vbs files for that matter? All this accomplishes is making the scripting host useless... I can't think of a single good reason to do that.

One could "fix" the .js file for unicode encoded output, but seemingly you don't want a jscript file.

If you want a .exe, then yes, you'll have to use something else. Any other techs you can't use? This could easily be done in a dozen lines of C# (would be a .exe, but you'd need the .NET framework installed)
sweept
Aug 6 2008, 10:01 AM
QUOTE (crahak @ Aug 6 2008, 04:54 PM) *
QUOTE (sweept @ Aug 6 2008, 09:20 AM) *
1) that "00" gets added after each letter in output

Ideally you don't want that, but rather proper unicode support: that's where the 00's normally come from, it's not just padding (having 00's for no reason would be kind of dumb). This script doesn't return UTF-16 encoded strings, and if you try passing a unicode-encoded text file instead (probably not what you want in the first place), it only writes "0" instead of "00", plus, it writes the byte order mark and all that to the file too. It might be helpful to know what you're doing all this for.


the need of adding "00" to the right of each character is because some hex patching tools will do nothing without having those when using search or search replace by design. so if i know how to add it in the script that would help later

however I will be happy if this script can be further more perfecteed to my need

I would definitely settle having it convert anything between two quotes in a line that will act as margins for conversions & anything else on the line echo'd to the out put or use <...> <...>

for example:

"helloworld" this is a test "h l o r d" (&$^ " t esti ng"
68656c6c6f776f726c64 this is a test 68206c206f2020722064 (&$^ 20742065737469206e67


like this it can be possible to us a command line literally tho i would also settle for something without the echoing part

"helloworld" "h l o r d"

68656c6c6f776f726c64 68206c206f2020722064

thanks for your help

Mijzelf
Aug 6 2008, 11:37 AM
QUOTE
the need of adding "00" to the right of each character is because some hex patching tools will do nothing without having those when using search or search replace by design. so if i know how to add it in the script that would help later
Change line
CODE
outputline += inputline.charCodeAt( i ).toString(16);
in
CODE
outputline += inputline.charCodeAt( i ).toString(16) + "00";
and maybe you should change
CODE
outputline += "00";
to
CODE
outputline += "0000"
?

QUOTE
I would definitely settle having it convert anything between two quotes in a line that will act as margins for conversions & anything else on the line echo'd to the out put or use <...> <...>

for example:

"helloworld" this is a test "h l o r d" (&$^ " t esti ng"
68656c6c6f776f726c64 this is a test 68206c206f2020722064 (&$^ 20742065737469206e67
I think that is a bit difficult with a script. The scripting host takes the commandline and cuts it to pieces on each space. Two spaces are treated like one, so the script can't get the exact commandline.


crahak
Aug 6 2008, 11:53 AM
QUOTE (sweept @ Aug 6 2008, 12:01 PM) *
the need of adding "00" to the right of each character is because some hex patching tools will do nothing without having those when using search or search replace by design.

That would be because it only does unicode searches then. So that's what I was thinking, it's not padding, it's just encoded this way. Arguably, one could say the real fix here is a hex editor that isn't limited in that way (perhaps I'm not getting the big picture, converting text to hex, to then do text searches with a hex editor?), but anyhow...

As for the searching between quotes, the simplest thing would be to use a regular expression for that (e.g. "[^"]*"), and replacing in the original string all the matches by their hex representation (of the byte array returned when UTF-16 encoding it).

Still simple to do. I'll try to find some time tonight to write you something simple in C# (should only take 5-10 mins really).

You could still do it in JScript too. The biggest issue I can think of, is that .toString(16) doesn't return zero padded numbers (easily solved too).
sweept
Aug 6 2008, 08:40 PM
Mijzelf thats perfect now, great programming thanks ! smile.gif

crahak the padding part can be optional & predefined just so so the tool is more flexible

limiting it to do certain extra padding in patterns may help as well

text2hex.exe /p"00" strings.txt > Hex.txt returns "00" paddings

+ the others from here:

http://www.swingnote.com/tools/texttohex.php

this can be a simply good converter tool with the convert between quotes feature and the option to have the output padded as needed ....


thanks again for all the help, guys
crahak
Aug 7 2008, 02:47 AM
Sorry for the late reply, had a nap, and it was a LOT longer than expected laugh.gif

Try this app: http://www.zshare.net/download/1665788387ce49d0/

Syntax is: text2hex.exe sourcefile.txt destinationfile.txt

a input text file with:
CODE
"helloworld"  this is a test "h l o  r d" (&$^  " t esti ng"
"helloworld" "h l o  r d"

in it, would create another text file with:
CODE
680065006C006C006F0077006F0072006C006400  this is a test 680020006C0020006F0020002000720020006400 (&$^  200074002000650073007400690020006E006700
680065006C006C006F0077006F0072006C006400 680020006C0020006F0020002000720020006400

Which is exactly what you wanted if I understood what you wanted. Everything is proper unicode, and only the stuff between quotes is turned into hex.

If you want something else than a command line app, it would also be trivial to make it into an app with a GUI where you can paste strings into and have it convert them (or even a web app)... Anything else just ask. It could be turned into a jscript too. I'll post the final source code when you're happy with it...
sweept
Aug 7 2008, 05:59 AM
crahak i tried it out in various ways and it works perfectly.

finally there is a tool that can do a simple conversion without needing to look for combination ways or shareware tools, that still don't offer the simple conversion of getting the lines correct, the capital to none capital correct in translations .etc not to mention the padding aspect

what infact makes me sorry I'm not knowledgeable enough for coding , but Im happy proud and appropriative for the great help that went on this one...

there might be 2 things that comes to mind as to what exceptions this probably will need

* something for making quotes exceptional so it can have an output if needed


maybe by having a back slash attached to it
\" so it outputs "

\" = "

or any other workaround to adjust this

as to padding

I'd keep it simple by giving it some additional switch to have \no padding since the 16 bit "00" padding is default right now

i think it pretty much serves what i was looking for exactly!

turned out to be a real gem. thumbup.gif!
crahak
Aug 7 2008, 06:15 AM
QUOTE (sweept @ Aug 7 2008, 07:59 AM) *
* something for making quotes exceptional so it can have an output if needed

An option so it will ignore quotes and output *everything* in hex? Or an option to use a different character to delimit what is to be converted?

As for the zeros (everything being unicode), that could be optional if you wanted (I thought that's what you wanted in the first place). Simple to do anyways.

Just let me know exactly what you want, and I'll make the changes.
sweept
Aug 7 2008, 10:29 AM
allow me to emphasize that the goal has been reached & for what i needed of course

so the the 2 extra suggestions I had are maybe good in helping it become more of a qualified unix command line tool which i definitely wouldn't mind

but i can do without those side features added for now.

thanks again for the help i think you guys do amazing work

sweept
Sep 20 2008, 12:28 AM
[edit]
Google Internet Forums Unattended CD/DVD Guide
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.