AZW to PDF - Convert file now View other document file formats Technical Details Each PDF file encapsulates a complete description of a 2D document (and, with the advent of Acrobat 3D, embedded 3D documents) that includes the text, fonts, images and 2D vector graphics that compose the document.

Some scanners mail the scanned pdf file as an application/octet-stream with pdf extension. These are indeed pdf files.

Currently, they are not opened as pdf, but I get the application chooser dialog, because no application is associated to application/octet-stream. I would like the system to (try and) open such files as pdf files, i.e., fall back to filename extension-based detection for application/octet-stream mimetyped files. Is this possible to configure in the file associations kcm or in another way? An octet-stream is random binary data. You can assign it to eg.

Okular, but that's 'wrong' since it's random binary data. What needs to happen is that whatever opens the file (kmail?) either prefers the suffix over the mimetype (ugghhh.) or (much better omits the (particular) mimetype, so that the system is forced to detect it. Dnevnik raboti biblioteki 1. -> File a bug against whatever opens it. A shorthand 'solution' would likely be to assign octet-stream data to always be openened by 'kioclient[4 5] exec%U' (which redirects the opening and scratches the mimetype), but I've never tried that. => 'kcmshell[4 5] filetypes'.

There's extra space allocated in the MemoryStream buffer by default (just like with e.g. This can be dealt with easily by using the overload that allows you to set capacity, but is only really useful if you don't expect to write any data to the stream (or if you know how much extra bytes you're likely to need). But I suspect that jitbit might be referring to the fact that a when you use the byte[] constructor, the array isn't copied - the MemoryStream refers to the array in the argument. This can be both good and bad, and it's a bit of a shame it isn't documented on MSDN:) – Aug 2 '17 at 8:10.