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

binary/text flags #3

Open
jonathanong opened this issue Aug 15, 2014 · 16 comments
Open

binary/text flags #3

jonathanong opened this issue Aug 15, 2014 · 16 comments
Assignees

Comments

@jonathanong
Copy link
Member

would be nice, especially for mime types that aren't text/. i want to know if i could treat a file as a string. might be able to get rid of charset as well.

@Fishrock123
Copy link
Member

Keep in mind that this isn't a flag for compressibility: tarballs are well known to work well with gzip.

@Fishrock123
Copy link
Member

Also note that partial text / binary files do exist.

@jonathanong
Copy link
Member Author

what would ew call this field? encoding? some values:

  • text
  • binary
  • ['text', 'binary']?

@dougwilson
Copy link
Contributor

representation?

@jonathanong
Copy link
Member Author

i'm wondering how we would name this field and how to represent all the possible values as @Fishrock123 stated

@dougwilson
Copy link
Contributor

i meant representation as a possible name, haha. sorry, was on a phone at that time, so didn't want to type a lot

@jonathanong
Copy link
Member Author

oh. that's not what i think of when i read "representation".

@jonathanong
Copy link
Member Author

so shall we use representation or what? i think it should be encodings or something. otherwise, we can delay this until after v1 since it shouldn't break anything

@mdedetrich
Copy link

+1

Just stating it would be incredibly handy for our webserver if we can differentiate whether a file has binary support or not.

Also confirming that compressable and binary are not related

Also happy with representation as a name

@dougwilson
Copy link
Contributor

I'm implementing this and going with encoding as the name, as it's what the IANA database uses.

@Fishrock123
Copy link
Member

Sounds good. But then is should be the actual encoding, not just binary / text.

Edit: oh, right, that doesn't make much sense for text.

Edit2: wrong damn button

@dougwilson
Copy link
Contributor

Darn the registry is so old, lol. SO many say 8bit or 7bit because of email and stuff.

@dougwilson
Copy link
Contributor

Apparently they come from ye olde RFC 1341, which specifies them as this:

  • base64
  • quoted-printable
  • 7bit "[...] means that the data is all represented as short lines of US-ASCII data."
  • 8bit "[...] means that the lines are short, but there may be non-ASCII characters (octets with the high-order bit set)"
  • binary "[...] means that not only may non-ASCII characters be present, but also that the lines are not necessarily short enough for SMTP transport"

@Fishrock123
Copy link
Member

wow, real useful lol

@dougwilson
Copy link
Contributor

So I think what I'm going to do is export a encoding property that is either "text" or "binary". If someone really wants to know about the above, we can always export a transferEncoding property or some such.

@DutchBoyScowden1
Copy link

      Also note that partial text / binary files do exist.

Are you in Instance talking of Binary Text such as Platform based, Given units of measurement Platform based units such as 3a3ec68c <--- in short until creating a name for the game server your name remains this, now this is Short or not a real Binary from anything I'm working on Just tagged partial from a file'
jonathanong wanted to know a good name for his Folder I have a good name if, this is a short example:

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

No branches or pull requests

5 participants