| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| | |
called Inkscape::Pixbuf. Replace usage in the code as appropriate.
(bzr r12531)
|
| |/
|
| |
(bzr r12475.1.16)
|
| |
|
| |
(bzr r12499)
|
| |
|
|
|
| |
Rename libunicode-convert to symbol_convert and put it in libuemf.
(bzr r12490)
|
| |
|
| |
(bzr r11668.1.76)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Resolves issue of bug #988601 message 170 (Support of 'Unset' styles in EMF export).
2. Implements CSS 3 (and CSS 2) text-decoration support.
Note that it does not yet provide any method of adding these features - at present it just shows whatever is in the SVG. This new code is also used to display EMF/WMF strike-through and underline text decorations when these files are read in. Those decorations may also be written out to EMF/WMF. Other text decoration features, like overline, or dotted lines, are dropped. For SVG text-decoration -line, -style, -color are all implemented. CSS3 provides two ways to represent the same state, this code uses the compound text-decoration method rather than the 3 fields method. Also it leaves out keywords that are not needed and would break backwards compatibility. For instance:
text-decoration: underline solid
is valid, but would break CSS2. Solid is the default, so that sort of case is written as:
text-decoration: underline
If the state is CSS3 specific all of the needed fields are of course include, like
text-decoration: underline wavy red
3. It incorporates the fix for bug 1181326 (Text edit mishandles span of just colored spaces)
4. It incorporates further changes to text editing so that style can be changed on spans consisting of only spaces when text decorations are present in the span.
5. It incorporates code to disable text decorations when text so marked is mapped onto a path.
6. Fixed more bugs in Hebrew language support than I can remember. Hebrew language export/import to EMF now works quite well. (See the examples in libTERE v 0.7.) WMF does not support unicode and for all intents and purposes Inkscape has no way to read or write Hebrew to it. Some of more important things that now work that didn't (or didn't always): Hebrew diacritical marks, R/L/center justification, and bidirectional text. The Hebrew fonts "Ezra SIL" and "EZRA SIL SR" should be installed before viewing the libTERE examples, otherwise font substitutions will cause some text shifts.
7. Implemented font failover in Text Reassemble, which makes the process more robust. (Again, see the examples in libTERE. )
(bzr r11668.1.71)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This set of patches does the following:
1. Fixed a typo ( where "+ sizeof()" should have been "* sizeof()")
which caused a memory problem for EMF/WMF files with very large numbers
of hatches.
2. Added support for background mode, background color, and textcolor
in hatches. EMF/WMF files change these parameters but the change may
be silent until many records later. This has the odd effect that a
stroke or fill may be defined (in SVG) and then it is ignored later
and replaced with one with a different background color.
3. Fixed WMF output so that it wasn't adding +1 to the number of pixels
for Width and Height. (Allows WMF files to go through several cycles
of save as, open without changing sizes.)
4. Cleaned up indenting of [ew]mf-{print|inout}.* files, to make
them compliant with the inkscape standard. All indents are (I hope)
now 4*i deep.
5. Added underline/strikeout support for text read from EMF/WMF files.
Inkscape itself cannot currently render this, but it makes it into the
SVG, and it shows up correctly when that SVG is read by Opera.
6. Took out all the "throw" calls, replacing them with g_error(). If
this comes up again in debugging a define can be used to remap the
g_error to temporarily reintroduce the throw so that gdb can catch them.
7. Took out the "%6lf" format changes from patch 11724, retained the
"127" length limit in the same sscanf.
8. Put the C type casts back in, reversing those changes from patch
11724. This is a style issue, and I could not find clear guidance for
which way to go. (Nor a good rationale for keeping the lengthier C++
syntax.) So I reviewed a large swath of other inkscape code to see if
there was a trend and found a very large number of other sections that
were using C style casts instead of the more verbose C++ forms. So I
kept it the way it has been.
9. The locale changes from 11724 were of course retained.
(bzr r11668.1.59)
|
| |
|
| |
(bzr r11668.1.56)
|
|
|
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)
|
