| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
I can see no reason for having the reap lock now. We always
hold the ALLOC lock when we need it, so just live with that.
|
|
|
|
As seen with:
mutool draw -o out.ppm Bug697706.epub
|
|
|
|
|
|
More consistent with the rest of the code.
|
|
In keeping with the rest of the code.
|
|
Fits with the rest of the code.
|
|
It seems odd for a document writer to pass a device pointer
out, and then require it to be passed back in.
Hide that in the public API.
|
|
Avoids needing to access the internals of reference counting.
|
|
There is no need to hold a separate flag to say that
we need reaping, when this can be implied from the
store_key_refs and the normal refcount being equal.
In addition, I don't think we were ever actually
setting this, so the code was wrong to start with.
|
|
|
|
This enables people to access (say) a PNG writer without
pulling in every single document writer at link time. (Of
course, currently, without function level linking, even now
we'll pull everything in, but we can improve this by
splitting source files up).
|
|
Instead of having fz_new_XXXX(ctx, type, ...) macros that call
fz_new_XXXX_of_size etc, use fz_new_derived_...
Clearer naming, and doesn't clash with fz_new_document_writer.
|
|
Moves document_writers into the same style as
fz_new_{image,document,page} etc.
|
|
Allow mutool convert to output all image formats we can write.
Add sanity checks for pbm and pkm writers.
|
|
|
|
Move this into the same style as fz_new_document and
fz_new_image.
|
|
|
|
Emit characters with callbacks so we don't need to do two passes using
vsnprintf to count, format, and copy the result.
|
|
Call fz_append_string instead of fz_append_printf for static strings.
Call fz_write_string instead of fz_write_printf for static strings.
|
|
Rename fz_write to fz_write_data.
Rename fz_write_buffer_* and fz_buffer_printf to fz_append_*.
Be consistent in naming:
fz_write_* calls write to fz_output.
fz_append_* calls append to fz_buffer.
Update documentation.
|
|
Still need specialty tools for namedump and cmapdump.
|
|
|
|
Images, Document and Document Handlers.
|
|
This evenly spaces the sub-parts of a ligature.
|
|
|
|
harfbuzz puts all ligature component characters at the same coordinate
as the glyph.
|
|
Emit one <tspan> per line, so we only need to emit one 'y' coordinate
for the whole line, instead of repeating it for each character.
|
|
Update mutool to call it.
|
|
Annoyingly TGA requires lines to be written from bottom to top,
so require callers to flip the image.
Also fix TGA to cope with alpha or not.
Update mutool draw to use band writer interface for TGA.
|
|
Appears to have been broken since alphas were optional.
|
|
Remove needless parameter passing in fz_band_writer API.
We always know the bandstart, so why make the caller keep track
of it and pass it in?
Similarly, we know when we hit the end of the page, so why
require us to trigger the trailer writing manually?
|
|
Move implementation to be more in line with fz_streams. Much
closer parallels now.
|
|
fz_new_stream cleans up the passed in state if the allocation
fails, so don't free it in the caller too.
|
|
Use xml:space="preserve" to remove the whitespace workaround.
Fix output of glyph clusters.
|
|
When scaling a single row pixmap with a flip, I was getting
the offset to the far end of the line wrong due to forgetting
to allow for the alpha plane.
Fixed here.
|
|
Better to have this defined at the system level
rather than scattered about in various files.
|
|
Also add explicit viewBox and width/height to image symbol and use
elements, to work around a strange clipping/image scaling issue
with firefox.
|
|
We were emitting unbalanced quotes for the x and y attributes.
|
|
|
|
The aim is to put each tag on a line of its own.
|
|
Now mutool convert can write SVG documents.
|
|
When falling back from glyph cache based rendering to direct
rendering, we were applying the transform twice due to the
handling of dev->transform introduced in commit
ccaf716.
Fixed here.
|
|
|
|
Pointer arithmetic for final special case was going wrong.
|
|
Build with this defined, and we no longer send text as
reusable symbols, but instead send it as genuine text,
with all the potential problems (mismatching fonts etc)
that this entails.
Requested by a customer.
|
|
|
