file-format

I am writing some code to read bitmap files. Here is the struct I am using to read the bitmap header. See also: https://msdn.microsoft.com/en-us/library/windows/desktop/dd183374(v=vs.85).aspx struct BITMAPFILEHEADER { WORD bfType; // 2 DWORD bfSize; // 6 WORD bfReserved1; // 8 WORD bfReserved2; // 10 DWORD bfOffBits; // 14 }; // should add to 14 bytes If I put the following code in my main function: std::cout << "BITMAPFILEHEADER: " << sizeof(BITMAPFILEHEADER) << std::endl; the program prints: BITMAPFILEHEADER: 16 It appears to be re-aligning the data in the struct on 4-byte boundaries,

I have a file with mac format, I know I can use :e! ++ff=mac to change to the correct fileformat. What I'd like to know is if there is a command line option I can pass when I open the file to open it directly with the correct fileformat. You can do this using the command line, try: $ vim -c "set fileformat=mac" -c <command> executes before loading the first file. As jammessan has noted, this will only affect the first file that is loaded, subsequent files will require that you change fileformat for each buffer. If that doesn't work, you can also try: $ vim -c "e ++ff=mac" But it's better to

An SVG file is basically an XML file so I could use the string <?xml (or the hex representation: '3c 3f 78 6d 6c' ) as a magic number but there are a few opposing reason not to do that if for example there are extra white-spaces it could break this check. The other images I need/expect to check are all binaries and have magic numbers. How can I fast check if the file is an SVG format without using the extension eventually using Python? XML is not required to start with the <?xml preamble, so testing for that prefix is not a good detection technique — not to mention that it would identify every

How to identify where the Excel file use Excel 95 or Excel 97 specifications? i.e., which version of BIFF they uses. You can find the necessary information in the MICROSOFT OFFICE EXCEL 97-2007 BINARY FILE FORMAT SPECIFICATION available from Microsoft. See page 11 for the following explanation: BIFF Microsoft Office Excel version --------------------------------------------------- BIFF5 Microsoft Excel version 5.0 (XL5) BIFF7 Microsoft Excel 95 (XL7) (also called Microsoft Excel version 7) BIFF8 Microsoft Excel 97 (XL8), Microsoft Excel 2000 (XL9), Microsoft Excel 2002 (XL10), Microsoft Office

Is there a way to tell Perforce to leave text files alone without setting the file-type as binary? Or barring that, is there a way to tell the Perforce client to diff binaries? Binary usually isn't desirable, because I lose the ability to diff. To clarify: If I edit and make changes to a *.txt file on my window client, newlines will have CR+LF as per the DOS format. But if I P4 sync on a Unix client, it will have LF only. I need Perforce to keep the format as-is, regardless of where the Perforce client lives. That said, I do have a work-around: Set file-type as binary; and/or create a branch