| 2012-08-04 00:19:56 |
tester |
bug |
|
|
added bug |
| 2012-08-04 00:23:46 |
tester |
summary |
Disable transformations such as anti-aliasing for bitmap export |
Disable data-loss -prone -operations such as anti-aliasing for bitmap export |
|
| 2012-08-04 00:24:05 |
tester |
summary |
Disable data-loss -prone -operations such as anti-aliasing for bitmap export |
Disable information-loss -prone -operations such as anti-aliasing for bitmap export |
|
| 2012-08-04 00:26:05 |
tester |
description |
Transformations such as anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
The title is open with "Disable transformation" because it looks like that Inkscape comes with other data-loss -transformation in the exportation [2], some contrast -hard-coded-thing apparently also.
If I want to deploy something, I can easily do anti-aliasing with ImageMagick -- this makes sure I do it only once. Please, remove this clutter -feature, keep Inkscape simple! Thank you.
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
The term "transformation" means here an information-loss-prone -operations such as anti-aliasing that can result into information -loss, not mathematical things such as rotations, translations etc.
Transformations such as anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
The title is open with "Disable transformation" because it looks like that Inkscape comes with other data-loss -transformation in the exportation [2], some contrast -hard-coded-thing apparently also.
If I want to deploy something, I can easily do anti-aliasing with ImageMagick -- this makes sure I do it only once. Please, remove this clutter -feature, keep Inkscape simple! Thank you.
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
|
| 2012-08-04 00:27:35 |
tester |
summary |
Disable information-loss -prone -operations such as anti-aliasing for bitmap export |
Disable anti-aliasing for bitmap export |
|
| 2012-08-04 00:29:19 |
tester |
description |
The term "transformation" means here an information-loss-prone -operations such as anti-aliasing that can result into information -loss, not mathematical things such as rotations, translations etc.
Transformations such as anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
The title is open with "Disable transformation" because it looks like that Inkscape comes with other data-loss -transformation in the exportation [2], some contrast -hard-coded-thing apparently also.
If I want to deploy something, I can easily do anti-aliasing with ImageMagick -- this makes sure I do it only once. Please, remove this clutter -feature, keep Inkscape simple! Thank you.
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
|
| 2012-08-04 00:30:06 |
tester |
description |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed in the raster -exportation, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
|
| 2012-08-04 00:34:24 |
tester |
description |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to disable this automatic-antialising altogether because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed in the raster -exportation, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to kill this automatic-antialising because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed in the raster -exportation, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
|
| 2012-08-04 00:34:33 |
tester |
summary |
Disable anti-aliasing for bitmap export |
Kill automatic anti-aliasing for bitmap export |
|
| 2012-08-04 00:38:08 |
su_v |
tags |
|
bitmap exporting |
|
| 2012-08-04 00:43:24 |
tester |
description |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to kill this automatic-antialising because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle.
I phrased this request firstly open-endedly like `"Disable transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed in the raster -exportation, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
Anti-alias in exportation can mean a data-loss. The old request [1] asks for option, I request a feature to kill this automatic-antialising because it tends to result into poorer quality, antialising should be done only once in the deployment -- not during development -cycle. ImageMagick's `$ mogrify -antialias ./DeploymentDir/hello.png` with a bash -loop should handle antialiasing fine, InkScape needs no clutter -features -- if someone wants this automatically in InkScape, s/he should add some kind of macro to do this.
I phrased this request firstly open-endedly like `"Kill transformations such as anti-aliasing for bitmap export"` where my goal was to get all data-loss-prone -operations removed in the raster -exportation, it looks like Inkscape has more them [2].
References
[1] https://bugs.launchpad.net/inkscape/+bug/180612
[2] http://graphicdesign.stackexchange.com/questions/8021/how-to-batch-export-layers-of-inkscape-generated-svg-file-to-bitmap-for-sprites |
|
| 2015-11-10 16:43:35 |
su_v |
inkscape: importance |
Undecided |
Wishlist |
|
