| 2014-11-05 14:41:53 |
LucaDC |
bug |
|
|
added bug |
| 2014-11-05 14:54:08 |
su_v |
inkscape: milestone |
|
0.92 |
|
| 2014-11-05 14:55:02 |
su_v |
tags |
|
units |
|
| 2014-11-05 15:50:02 |
LucaDC |
attachment added |
|
square.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4253943/+files/square.svg |
|
| 2014-11-05 18:52:05 |
Alvin Penner |
inkscape: status |
New |
Confirmed |
|
| 2014-11-05 19:12:42 |
Alvin Penner |
attachment added |
|
rect0485.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254044/+files/rect0485.svg |
|
| 2014-11-05 19:13:32 |
Alvin Penner |
attachment added |
|
rect_trunk.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254047/+files/rect_trunk.svg |
|
| 2014-11-05 19:43:51 |
Alvin Penner |
attachment added |
|
rect0485_after9096.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254056/+files/rect0485_after9096.svg |
|
| 2014-11-06 19:37:16 |
Jabiertxof |
inkscape: assignee |
|
Jabiertxof (jabiertxof) |
|
| 2014-11-06 19:39:55 |
Jabiertxof |
attachment added |
|
90to96.inx https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254704/+files/90to96.inx |
|
| 2014-11-06 19:42:06 |
Jabiertxof |
attachment removed |
90to96.inx https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254704/+files/90to96.inx |
|
|
| 2014-11-06 19:55:14 |
Jabiertxof |
attachment added |
|
90-96-90.tar.gz https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4254705/+files/90-96-90.tar.gz |
|
| 2014-11-08 03:22:36 |
Jabiertxof |
attachment added |
|
dpiswitcher.zip https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4255543/+files/dpiswitcher.zip |
|
| 2014-11-08 03:56:05 |
su_v |
inkscape: importance |
Undecided |
High |
|
| 2014-11-08 03:56:05 |
su_v |
inkscape: status |
Confirmed |
In Progress |
|
| 2014-11-08 13:05:25 |
Alvin Penner |
attachment added |
|
default_mm_0485.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4255783/+files/default_mm_0485.svg |
|
| 2014-11-08 13:42:24 |
Alvin Penner |
attachment added |
|
rect0485_after_extension.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4255809/+files/rect0485_after_extension.svg |
|
| 2014-11-08 17:25:44 |
Alvin Penner |
attachment added |
|
rect0485_rev13680_1.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4256047/+files/rect0485_rev13680_1.svg |
|
| 2014-11-08 17:26:25 |
Alvin Penner |
attachment added |
|
rect0485_rev13680_2.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4256048/+files/rect0485_rev13680_2.svg |
|
| 2014-11-08 20:43:14 |
su_v |
description |
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.)
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2014-11-08 20:43:22 |
su_v |
tags |
units |
blocker units |
|
| 2014-11-08 21:31:44 |
Alvin Penner |
attachment added |
|
rect0485_rev13682_2.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4256161/+files/rect0485_rev13682_2.svg |
|
| 2014-11-09 04:24:54 |
su_v |
description |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.)
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.)
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2014-11-09 23:50:36 |
Alvin Penner |
attachment added |
|
rect0485_rev13696_Case2.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4256910/+files/rect0485_rev13696_Case2.svg |
|
| 2014-11-10 23:04:17 |
Alvin Penner |
attachment added |
|
rect0485_rev13701.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4257742/+files/rect0485_rev13701.svg |
|
| 2014-11-30 21:00:29 |
Jabiertxof |
attachment added |
|
dpiswitcher.inx https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4271572/+files/dpiswitcher.inx |
|
| 2014-11-30 21:01:11 |
Jabiertxof |
attachment added |
|
dpiswitcher.py https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4271573/+files/dpiswitcher.py |
|
| 2014-11-30 21:06:23 |
Jabiertxof |
attachment added |
|
linea_ajuste_ergopad.ai https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4271574/+files/linea_ajuste_ergopad.ai |
|
| 2014-11-30 21:20:39 |
Jabiertxof |
inkscape: assignee |
Jabiertxof (jabiertxof) |
|
|
| 2014-12-01 10:42:12 |
su_v |
inkscape: status |
In Progress |
Triaged |
|
| 2014-12-10 08:04:06 |
su_v |
description |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.)
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2014-12-10 08:14:12 |
su_v |
description |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates).
- The ability to switch document units should be disabled (it's broken in several ways).
- Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates). For guides, grids, 3dbox see bug #1400702.
√ The ability to switch document units should be disabled (it's broken in several ways).
√ Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
See also:
=========
Related mailing list threads:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/44423>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/45073>
Related wiki page:
<http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape>
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2015-02-24 18:06:58 |
su_v |
description |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
- Everything should use only pixels as is (mostly) done in 0.48 (including templates). For guides, grids, 3dbox see bug #1400702.
√ The ability to switch document units should be disabled (it's broken in several ways).
√ Font size should be stored in pixels.
- Some templates in 0.48 templates do use 'mm' so there does need to be a script to convert files based on those templates to 96dpi.
See also:
=========
Related mailing list threads:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/44423>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/45073>
Related wiki page:
<http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape>
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
√ Everything should use only pixels as is (mostly) done in 0.48 (including templates). For guides, grids, 3dbox see bug #1400702.
√ The ability to switch document units should be disabled (it's broken in several ways).
√ Font size should be stored in pixels.
See also:
=========
Related mailing list threads:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/44423>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/45073>
Related wiki page:
<http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape>
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2016-06-05 16:01:04 |
su_v |
description |
Roadmap for 0.92: (this bug)
=================
- Non-pixel units are allowed but everything in a document should use the same units including guides and grids.
- (Guides and grids need code to do this.) --> see bug #1400702
- An extension that saves a document in pixels should be added to allow backwards compatability with 0.91.
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
√ Everything should use only pixels as is (mostly) done in 0.48 (including templates). For guides, grids, 3dbox see bug #1400702.
√ The ability to switch document units should be disabled (it's broken in several ways).
√ Font size should be stored in pixels.
See also:
=========
Related mailing list threads:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/44423>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/45073>
Related wiki page:
<http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape>
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
Roadmap for 0.92: (this bug)
=================
√ Non-pixel units are allowed but everything in a document should use the same units including guides and grids. (Guides and grids need code to do this --> see bug #1400702).
- An extension that saves a document in pixels should be added to allow backwards compatibility with 0.91.
- Optionally add viewBox if document is affected as described here:
http://wiki.inkscape.org/wiki/index.php/CSS96#Affected_files
It should be possible to avoid overwriting Inkscape version until any necessary conversion is done. If a conversion appears to be needed, a pop-up can ask the author if it should be done.
Roadmap for 0.91: (bug #1387864)
=================
√ Everything should use only pixels as is (mostly) done in 0.48 (including templates). For guides, grids, 3dbox see bug #1400702.
√ The ability to switch document units should be disabled (it's broken in several ways).
√ Font size should be stored in pixels.
See also:
=========
Related mailing list threads:
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/44423>
<http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/45073>
Related wiki page:
<http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape>
<http://wiki.inkscape.org/wiki/index.php/CSS96>
Original description:
=====================
Merging of experimental branch has introduced the change of px from 90 DPI as 96 DPI.
Being px the internal unit used by Inkscape to save almost everything, all measures in documents created with the 90 DPI convention are now interpreted with the new 96 DPI convention and this causes a rescaling of the entire document by 90/96 (93.75%) if compared with the physical units they were created with.
Even the page is resized, so the problem is not visually evident after opening an old document unless there is an underlying grid which has been specified with an absolute unit (e.g. mm) so objects are no more aligned to it; or until an object whose length is known is measured with a unit different than px.
This lack of evidence could cause a user to start modifying an old document and realizing there is a problem only after a while. In this situation the document has become corrupted as there are now objects rescaled and new objects with correct dimensions. Such a situation could be not easily fixable so the work done so far could be lost.
An important aspect about this issue is that many users never cared (or knew) about the 90 DPI internals of Inkscape and are probably not going to care (or to know) about the change to 96 DPI. They are only going to find their documents corrupted.
The proposed solution is to find a way to recognize old documents (differentiating the news?) and, at least, warn the user upon opening them that a rescaling has occurred. Better would be to offer an automatic way to fix this unwanted rescaling, if it's the case; in fact for some documents it would be inappropriate, for example a document whose default unit was intended to be px no matter at what DPI hence it does not have any reference to physical units inside.
Lack of doing anything about this issue could result in document corruption and data loss. |
|
| 2016-06-05 16:01:23 |
su_v |
bug |
|
|
added subscriber su_v |
| 2016-08-06 10:34:54 |
Jabiertxof |
attachment added |
|
attempt-to-bug#1389723 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4715442/+files/attempt-to-bug%231389723 |
|
| 2016-08-26 16:56:53 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.1 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4728477/+files/bug%231389723-dpiswitcher.0.92-v0.1 |
|
| 2016-08-26 17:38:43 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.2 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4728479/+files/bug%231389723-dpiswitcher.0.92-v0.2 |
|
| 2016-08-26 21:19:45 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.3 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4728542/+files/bug%231389723-dpiswitcher.0.92-v0.3 |
|
| 2016-11-14 20:55:42 |
Jabiertxof |
inkscape: assignee |
|
Jabiertxof (jabiertxof) |
|
| 2016-11-18 17:09:05 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.4 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4779420/+files/bug%231389723-dpiswitcher.0.92-v0.4 |
|
| 2016-12-01 03:09:17 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.5 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4785549/+files/bug%231389723-dpiswitcher.0.92-v0.5 |
|
| 2016-12-02 12:51:50 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.6 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4786410/+files/bug%231389723-dpiswitcher.0.92-v0.6 |
|
| 2016-12-02 13:44:12 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.7 https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4786451/+files/bug%231389723-dpiswitcher.0.92-v0.7 |
|
| 2016-12-02 14:13:01 |
Jabiertxof |
attachment added |
|
bug#1389723-dpiswitcher.0.92-v0.7.patch https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4786461/+files/bug%231389723-dpiswitcher.0.92-v0.7.patch |
|
| 2016-12-10 05:20:28 |
su_v |
attachment added |
|
0000-fix-dpiswitcher-scaling-content-v1.diff https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4789827/+files/0000-fix-dpiswitcher-scaling-content-v1.diff |
|
| 2016-12-12 16:50:43 |
su_v |
attachment added |
|
0000-fix-dpiswitcher-scaling-v1.diff https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4790772/+files/0000-fix-dpiswitcher-scaling-v1.diff |
|
| 2016-12-12 17:36:45 |
LucaDC |
attachment added |
|
doc.svg https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4790805/+files/doc.svg |
|
| 2017-01-14 11:15:36 |
zoqaeski |
attachment added |
|
Screenshot https://bugs.launchpad.net/inkscape/+bug/1389723/+attachment/4804197/+files/img-2017-01-14-214619.png |
|
| 2017-01-15 20:58:29 |
Jabiertxof |
inkscape: status |
Triaged |
Fix Released |
|
