summaryrefslogtreecommitdiffstats
path: root/src/extension/internal/uemf_utf.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Move libuemf to a separate directory.Krzysztof Kosi??ski2013-08-311-552/+0
| | | | | Rename libunicode-convert to symbol_convert and put it in libuemf. (bzr r12490)
* 988601-changes_2013_03_20a.patchDavid Mathog2013-03-211-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | 1. Fixes the clang warnings noted in a post above, other than those associated with alignment caused by casting. 2. Fixes some minor rounding errors in both WMF and EMF input/output. Round trip open/save cycles are conservative for EMF and WMF files (excluding any features that are not full supported in inkscape or the target file format, for instance, gradients, which must be emulated.) 3. Fixed a missing break in the input WMF LINETO record handling, which was falling through into the MOVETO and generating a harmless extra "M" operation in a path. 4. WMF has no POLYPOLYLINE record. However input that maps into essentially a polypolyline record in SVG is common, for instance dashed lines that have been converted to line segments. These end up in SVG as a series of M L M L draw commands in the path. Earlier each M L pair was going out as a polyline record, now they go as a series of MOVETO/LINETO records. The primary reason for this change is that without this change the behavior described in (2) does not occur. 5. Fixed an issue where polyline and polygon records in some instances ended up with an extra copy of their last point. (bzr r11668.1.62)
* changes_2013_02_25a.patchDavid Mathog2013-03-081-2/+30
| | | | | | | | | | | | | | New: WMF import/export implements WMF (Windows Metafile) read and write. Inkscape previously supported that through uniconverter, which was not very good with WMF files. The new version now has a complete wmf-print/wmf-inout implementation, analogous to the previous emf-print/emf-inout. This handles images, patterns, and various other goodies to the extent that WMF does. WMF is a bit primitive, many fields are only 16 bits, so it even more resolution sapping issues than does EMF. Given the choice, always use the latter format. (bzr r11668.1.52)
* changes_2013_02_01b.patchDavid Mathog2013-02-131-5/+73
| | | | | | | | | | | | | | | | EMF import: - Fix for EMF files with MODIFYWINDOWTRANSFORM records containing rotations - Add support for embedded PNG and JPG images - Fix for PowerPoint patterns EMF export: - Rotated images are exported using MODIFYWINDOWTRANSFORM records - Add output option to allow unrotated output (e.g. for PowerPoint 2003) - Don't rotate hatch and image fills on export libTERE: - Fix bug with misplaced words in LTR text (fix for RTL untested) (bzr r11668.1.50)
* preliminary release of the EMF import text reassembly feature. David Mathog2012-12-131-0/+455
(based on libTERE (TExt REassembly), not yet published) libTERE examines all the text in an EMF file, which consists only of little chunks in different formats, and attempts to reassemble it into an editable SVG text object, with color, different fonts and so forth. (only tested with English) (bzr r11668.1.45)