Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use -b to output a json string with base64 encoded binary blobs #2

Open
kapouer opened this issue Jan 29, 2016 · 5 comments
Open

use -b to output a json string with base64 encoded binary blobs #2

kapouer opened this issue Jan 29, 2016 · 5 comments

Comments

@kapouer
Copy link

kapouer commented Jan 29, 2016

so you can parse binary output even with JSON.parse ! (i noticed you already use json output)

@kapouer kapouer changed the title use -j -b to output a json string with base64 encoded binary blobs use -b to output a json string with base64 encoded binary blobs Jan 29, 2016
@crussell42
Copy link
Owner

Yes I can parse but often have to remove special characters before doing so.
Depends on the program used to insert the tags.
If you can be more specific about the problem I may be able to help.

On Fri, Jan 29, 2016 at 4:19 PM, Jérémy Lal [email protected]
wrote:

so you can parse using JSON.parse ?
Is there something in stay_open flag that forbids this ?


Reply to this email directly or view it on GitHub
#2.

@kapouer
Copy link
Author

kapouer commented Jan 29, 2016

I'm not reporting bugs, here. More like ideas for enhancements.

but often have to remove special characters before doing so.

Do you mean it's not UTF-8 output ?

@crussell42
Copy link
Owner

All good. I have not spent much time on this lately so am not up on the
exact reasons.
I use this package in a production system and know that I had to scrub some
of the
returned json (could be utf8 issue but I honestly cant remember...would
have to dig into the program that uses the library to refresh my memory).
Feel free to give the lib a try and make what ever branches or improvements
you want.
I will help if I can spare the time.
I will try and update the wiki with a real world example of the
promise/result usage.

On Fri, Jan 29, 2016 at 4:44 PM, Jérémy Lal [email protected]
wrote:

I'm not reporting bugs, here. More like ideas for enhancements.

but often have to remove special characters before doing so.
Do you mean it's not UTF-8 output ?


Reply to this email directly or view it on GitHub
#2 (comment)
.

@kapouer
Copy link
Author

kapouer commented Jan 29, 2016

That's cool. I'm using exiftool for https://github.com/kapouer/url-inspector and am investigating wether i can keep exiftool as a daemon and feed it with 50kb of file head then 100kb...and so on until it finds proper tags, to avoid downloading too much data. The -fast option is nice but not working on all file types. I'll tell you if i come up with something interesting.

@kapouer
Copy link
Author

kapouer commented Feb 7, 2016

In https://github.com/kapouer/node-streat
i'm implementing those ideas.

It's probably a bit leaky though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants