Bryce, I brought down the latest win build 0803241523 and tested the printing on some random scribbles.
Result: Sounds, lights, action but only a blank sheet of paper fed out. While this is better than an error message it is still not printing.
Is there a particular up-to-date build that win people can use to test the printing? Or is there something else I need to know to get printing?
PS. I also opened a pdf and tried to print it. Got an internal error message and Inkscape closed.
There must be other users such as myself who are willing to check the state of play but cannot help with the coding.
My system is win200. cheers, Erik kaver@...68...
----- Original Message ----- From: "Bryce Harrington" <bryce@...1798...> To: inkscape-devel@lists.sourceforge.net Sent: Tuesday, March 25, 2008 8:31 AM Subject: [Inkscape-devel] Status - Inkscape 0.46.0-1 Windows Package
I. Rygle, that round-up of Windows issues is quite handy!
II. Patches included so far
#179988 01_win32_printing.patch ?????? 02_win32_print_dialog_parent_window.patch (from Joel; no LP#) #183646 03_vista_turn_off_dashes.patch #168896 05_save_as_xaml.patch:
III. Patches/bugs not included due to problems
#165726 04_win32_remove_dialogs_on_top_preference.patch Fails to apply. See bug for details. #204779: ?? Not sure what to do here. A late comment refs to a patch in #187290 so maybe that patch needs inclusion? #187290: ?? I'm unclear if the patch here (comment #34) is ready, or needs additional testing/fixing.
IV. New Windows patch packaging system
I've added a debian-like patch setup for managing Windows patches. In other words, rather than apply patches directly, they are placed in inkscape/packaging/win32/patches/ and listed in the 'series' file in that directory. I've also written a simple script to apply the patches:
cd /packaging/win32/ && ./apply_patches.sh
This will need to be done by the Windows packagers when building 0.46.0 Windows packages (perhaps some scripts could be updated to include this step). Please someone update the Win32 docs to reflect this.
This may seem weird compared with just committing the patches directly onto the stable branch, however this is standard operating procedure on Linux distros, and makes managing the patches and future updates easier. By keeping the patches only applied for Windows, it also completely avoids the risk of windows patches breaking linux code (these patches look safe, but you never know...)
This also gives the windows packagers the flexibility to do 0.46.0-2, -3, etc. releases with more patches later on if they wish.
So the basic rule is that we should have one common 0.46.0 tarball, and then each distro (including the Windows package as a distro), applies their packaging patches against it before building their packages.
When we prepare for 0.46.1, we can look into incorporating some/all of the windows (and other distro) patches.
V. Packaging and Release Announcements
As mentioned before, March 24th is the day for sending out release announcements. This means we need to get all packages (including Windows) posted ASAP. Please let me know if anyone needs additional time for packaging, in case we need to delay the PR a bit.
Bryce
On Mon, Mar 24, 2008 at 08:30:29AM -0700, rygle wrote:
A few minor improvements have been made to the Win32 printing patch, and
it's
as ready as I think it will get for 0.46 release. Can someone please
commit
it? https://bugs.launchpad.net/inkscape/+bug/179988/comments/139
Here's the latest information on printing under Win32;
Non-printing - FIXED
Default page size problems - FIXED
Print Scaling problems - FIXED
White or black boxes over printing - FIXED - GTK uses the wrong call
in
Cairo (create_win32_surface, not the create_win32_printing_surface).
There
is a patch in the GTK bug tracker to fix this, but in the meantime we
have
bypassed that part of GTK. The code will revert to GTK automatically
when
GTK itself fixes the problem.
- All known crashes - FIXED
Adrian Johnson has patched the Cairo libs to fix a rare crash with
radial
gradients.
- There are two patched libs here (needs both) -
http://annarchy.freedesktop.org/~ajohnson/cairo/
- A patch has also been submitted to the Cairo git repository -
http://gitweb.freedesktop.org/?p=cairo;a=commit;h=ae9635bf33cb989f5c525800b8...
- If the cairo dlls for inkscape are built by patching 1.5.14 instead of
building from git head Adrian recommends also getting the PostScript bug
fix
as well:
http://gitweb.freedesktop.org/?p=cairo;a=commit;h=13e05bffd5cae5690fada24c7a...
Remaining problems with Windows printing are;
- Some blurs are misaligned/mis-scaled - see
https://bugs.launchpad.net/inkscape/+bug/205732 The workaround is to print to bitmap (under rendering in the print
dialogue)
- When printing falls back to bitmap, the bitmap is not always an ideal
resolution. Again the workaround is to print to bitmap (Print ->
Rendering
-> Bitmap).
-- View this message in context:
http://www.nabble.com/Win32-libs-tp16033417p16254450.html
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel