Adding some numbers to illustrate my concerns (it's not about the number of expected bug reports but the number of frustrated users...)
By frustration, do you mean you expect them to complain about large file sizes or do you mean they'll complain about large file sizes potentially causing other problems like out of memory, etc?
For me, I'd still be OK will being frustrated in the short term with large files sizes if their downstream effect wasn't to crash my system or other nasty effects. My primary concerns are to keep the quality and keep my system stable. I'll deal with file sizes for the short term. I hope I'm representative of other Windows users and not leading you down the wrong path.
On 3/11/09 23:18, Jon wrote:
- Keep the quality of the PDF high even if (in the short term) the
exported file size is large
bug #271695: 632 KB (osx) vs. 24 MB (win32) (EPS export)
bug #431314: 80 KB (osx) vs. 3.8 MB (win32) (PDF export) (and this is only a reduced case of a one-page-document, the original file doesn't even get exported on win32)
I better see your concern. I'm going to test more PDF exports on my Vista w/0.47pre4 today.
- Don't make me remember some hacky 'Path > Object to Path' before
saving as EPS/PS/PDF workaround that goes away when you fix things. This is much uglier marketing wise than a short term file size issue in my opinion.
Without applying this 'hack' when using the current 0.47pre version you get *both* bad text/font quality and even bigger file size when exporting with the 'Convert texts to paths' option:
bug #271695: 2.7 MB (0.46) vs. 411 MB (0.47pre3) (EPS export) (but with lower text/font quality due to bug #388257)
Yikes.
I almost hate to even suggest this idea as the downstream impacts may be horrible, but that said, is is possible to hard-code your best pragmatic (high text/font quality) workaround into the "save as EPS/PS/PDF code path" *only* for Windows systems to limit the exposure and only until you can do a point release fix?
How close (time wise) do you feel you are in determining true root cause and implementing a tested fix?
Jon