Add Objective-C files to git's list of files to use tab indents.
Don't sort cbz entries.

Rely on the document creator to have sorted them rather than risk
getting the wrong page order.
Import URW fonts version 1.10 converted to CFF by FontForge.
Add fz_advance_glyph and fz_encode_character functions.
Add const keyword to some font function parameters.
Bug 694113: Solve double free causing valgrind warnings.

In case of an unknown function type, we free 'func'. Then we later
read func->type out of the block, and drop the block.

Simple solution is not to free the block initially and to let the
drop of the block do it for us.
iOS: some fixes for iOS 7
Bug 694114: Fix valgrind issue.

I believe the implementation for revision 3 is wrong.

From pdf_reference17.pdf, step 5 of Algorithm 3.5 says:

5. Do the following 19 times: Take the output from the
   previous invocation of the RC4 function and pass it
   as input to a new invocation of the function; use an
   encryption key generated by taking each byte of the
   original encryption key (obtained in step 1) and
   performing an XOR (exclusive or) operation between
   that byte and the single-byte value of the iteration
   counter (from 1 to 19).

"the original encryption key (obtained in step 1)" is pwbuf
(32 bytes) not key. Even if it was key, it wouldn't be n
bytes long, but only 16.
Bug 694116: Solve valgrind issues in draw device.

The actual issue here is that a pixmap is dropped more times than
it should be due to an error in the rendering pipeline.

The problem arises because we fail to push a clip image mask, but
still pop the mask off the stack later. This puts us off by 1 in
the stack handling.

The simplest solution to this (that will be safe no matter what
mistakes are made by the caller too) is to add some simple tests
in the draw device to ensure we do not free too early.
fix memory leak introduced with a2c945506ea2a2b58edbde84124094c6b4f69eac

fz_new_font_from_buffer keeps the buffer for the font, so callers which
no longer need the data have to drop the buffer themselves explicitly.
track font path in fz_font

ft_file was removed in a2c945506ea2a2b58edbde84124094c6b4f69eac even
though it might still be needed by downstream consumers (such as
SumatraPDF) for allowing devices to load fonts again when a font has
been loaded by fz_new_font_from_file which doesn't maintain a buffer.
fix regression from da277059b37380d57028ff79a636f4d725c96e8f

The changes to fz_render_glyph cause the scissor rectangle to no longer
match the transformation matrix which causes Type 3 glyphs to be
clipped at larger resolutions.