View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007586 | Scribus | Import / Export | public | 2008-11-01 14:08 | 2016-02-13 01:30 |
Reporter | Niels | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
OS | Linux | ||||
Product Version | 1.3.5svn | ||||
Summary | 0007586: Provide antialiasing options | ||||
Description | I'm using Scribus for web graphics rather than for printing, using "export to PNG". There are several problems, the main one being that the antialiasing used by Scribus is just too much. I sometimes use small fonts and even bitmapped fonts, and they come out all blurry. Likewise line art, eg. the sides of a box. It would be very preferable to be able to select antialias level on a per element basis. Or on each font. | ||||
Tags | No tags attached. | ||||
Patch | |||||
|
We could provide such an option when exporting to bitmap but selecting antialias level on a per element basis or on a font basis is just not doable. Seriously. |
|
That's too bad. Other programs that might fill this need (pixel based graphics) are nowhere near usable. Scribus is pretty close. |
|
It is possible to provide some antialias options on an per element basis, but they would be rather limited. Only option would be antialiasing on or off, nothing in between. If that would fit your needs there would be no problem to build that in, only question would be where to integrate that into the GUI. |
|
That would certainly be better than nothing! I hope you such a feature worthy for inclusion. Thanks! :-) |
|
>> It is possible to provide some antialias options on an per element basis No, in fact that works only in the most simple case. If cairo uses fallbacks, it will use the current antialias options not the one set on a specific element. That means that won't work with all surfaces when layers or group are used. |
|
I don't see a place where cairo could use fallbacks in our code, currently we are using cairo only with the image backend so it is already a "fallback". |
|
>> currently we are using cairo only with the image backend No, win32 printing uses it too and it does not use the image backend. You should also remember that the plan is to merge screen and (at least) win32 printing code at a point. |
|
Hmm, printing stuff isn't in the scope of the original bug, that is a complete different field. The bug reporter wanted the antialiasing switchable for the image related outputs. |
|
>> that is a complete different field. No as soon as screen and win32 printing code will be merged that will be exactly same field and that may occur as soon as 1.3.6. |
|
Franz, jghali...what's the verdict on this ? |
Date Modified | Username | Field | Change |
---|---|---|---|
2008-11-01 14:08 | Niels | New Issue | |
2008-11-01 14:29 | jghali | Note Added: 0020566 | |
2008-11-01 14:29 | jghali | Status | new => resolved |
2008-11-01 14:29 | jghali | Resolution | open => fixed |
2008-11-01 14:29 | jghali | Assigned To | => jghali |
2008-11-01 14:30 | jghali | Assigned To | jghali => |
2008-11-01 14:30 | jghali | Resolution | fixed => open |
2008-11-01 14:30 | jghali | Status | resolved => new |
2008-11-01 14:30 | jghali | Note Edited: 0020566 | |
2008-11-01 21:42 | Niels | Note Added: 0020567 | |
2008-11-02 09:17 | fschmid | Note Added: 0020569 | |
2008-11-02 09:31 | Niels | Note Added: 0020570 | |
2008-11-02 12:22 | jghali | Note Added: 0020571 | |
2008-11-02 12:23 | jghali | Note Edited: 0020571 | |
2008-11-02 12:25 | jghali | Note Edited: 0020571 | |
2008-11-02 12:26 | jghali | Note Edited: 0020571 | |
2008-11-02 13:35 | fschmid | Note Added: 0020572 | |
2008-11-02 13:39 | jghali | Note Added: 0020573 | |
2008-11-02 13:41 | jghali | Note Edited: 0020573 | |
2008-11-02 13:43 | jghali | Note Edited: 0020573 | |
2008-11-02 13:45 | fschmid | Note Added: 0020574 | |
2008-11-02 13:54 | jghali | Note Added: 0020575 | |
2016-02-13 01:30 | Kunda | Note Added: 0038690 |