Does anybody know where I can get technical specifications for the .olm file produced by Outlook for Mac? I know there are conversion utilities but I need to write my own code for this.
Related
This is my last attempt before I completely give up. I am trying to use the Ace Editor; so far it has worked really well for existing languages but I do not find the documentation good enough to guide me on how to create a custom syntax highlighter.
I know this is a very broad question, but can anybody point me in the right direction of a decent tutorial or some pointers on how the hell to get this custom highlighter working!?
The Ace Editor tutorial just mentions two files, doesn't really explain the content very well, where to put the files (as the lib/ace/mode folder doesn't exist in the pre-packaged version), or how to change the formatting etc.
Appreciate any help.
If you want to write your mode in packed mode, then you need to copy one of existing mode files, rename it to mode-mymode.js and use define("ace/mode/mymode", define("ace/mode/mymode_highlight_rules" instead of using several files
We are using QT 5.5 successfully throughout our VC++ projects in VS2015.
Now, i am adding i18n thereto, using QTs Linguist tools to create my strings 2b translated and the resulting .qm files. I load the files through QTranslator object, the translation itself seems to work, but they get displayed wrongly.
As german is my mother tongue, I have to type several umlauts, beside any other special unicode-characters I definitely want to support.
As en example, I use linguist to translate over to über, and the resulting text in my application reads über. What I can surely recognize as an encoding mismatch.
I already had a look on the i18n example, which displays correctly for all of the provided languages, so I right now do not know what's wrong after I checked all file encodings.
Anyone any ideas? Or even has the same problems? Or had them but solved? Any suggestions were greatly appreciated!
This seems to be a Windows-specific problem.
Instead of using QString.toStdString() (what breaks the correct string), better use QString.toLatin1() at least for the languages to support yet.
I need some assistance trying to execute a demo print from jzebra to an ESC/P printer (epson tm88iv). I don't believe I am using the correct methods, but am wondering if anyone has sample text/data to use for the sample2.html file?
You will likely need to use esc/p formatted commands. Hit up the jzebra mailing list jzebra-users#googlegroups.com. Or download the proper programmers guide from the epson website.
I am new to Mac OS X programming and so I am going through an introductory text that includes building interfaces using Interface Builder (3.2.3) for both Cocoa and Carbon. Unfortunately I am having problems getting some of the examples I type in to run error free in the Cocoa and Carbon simulators. So I tried downloading the source code files from the publisher's website and found that they ran with no problems.
I'm trying to find the differences between the publisher's working and my non-working versions of the code. I started by just trying to compare the attribute settings as listed in Inspector but I could not find any differences. I then came across File Merge which I used to compare the .nib files for the two different versions. File Merge does show the differences but since I am unfamiliar with the markup language used in the .nib file and it lists too many differences to track down without being knowledgeable enough to know what is relevant or not, it really hasn't been very helpful.
My question is whether or not there is a tool or method available that will better show me the differences in the two versions of the code than what I can see in the Inspector window but also shows it in a more condensed and user friendly form than what is provided by File Merge. What is the recommended tool/methodology to debugging code in Interface Builder?
Also, can anyone recommend documentation where I can become familiar with reading and debugging the code in the .nib file in case that is the only way to find the differences?
Thanks
Check out nib2objc
Convert both yours and the example nibs to code.
It will convert nib files to what looks more like Obj-C code. Then just diff sections of them and see what's different. Should be pretty easy to read code vs NIB files.
The command line program ibtool can convert a nib into a text format, but I don't know if that will be sufficiently readable.
I'm looking for the best tool out there to extract any and all metadata embedded within the most popular image file formats (JPEG and PNG specifically). I would like to know about whatever is in there (XMP, Exif, IPTC/IIM, etc.). Ideally I am looking for an all-in-one solution that I can run from a command line, but am interested to hear about any other tools in this area that are of value.
I have found the following, each with advantages/disadvantages:
ExifTool is good, but the output is a little more roughshod that I would like.
DumpImage from the Metadata Working Group has good formatting of the metadata it does find, but doesn't support PNG.
I have recently released Binspector, the tool I ended up writing to answer this question to my own satisfaction. The basic premise of the tool is that it takes a format grammar and uses it to analyze a binary file. As long as the format grammar and the binary file are well-formed, one can inspect and analyze innumerable binary files and formats.
Code is hosted on GitHub, and a blog for the tool is here. (The overview post for the tool is here.)
As you did not mention any preferred programming language I take PHP as an example.
There is an Exif Extension for PHP which can be used to easily retrieve Metadata from an Image.
http://www.php.net/manual/en/function.exif-read-data.php
You could easily create a script that you can call from the command line. I must add that the extension only seems to provide support for JPEG and TIFF images.
You could try the official ADOBE XMP SDK. It is available for download at :
http://www.adobe.com/devnet/xmp.html
This is the complete SDK to read/write/manipulate metadata across a variety of formats.
In the SDK package there is one particular sample that might be of interest to you. Go to the "samples" folder build the samples as per documentation (available in the package). Look for the sample exe "DumpFile". This dumps all the metadata in the file to the console.