sorry I replied only to bulia.

Begin forwarded message:

The real problem is the insane bbox. I think this may happen to

...

other elements too, for any number of reasons. So perhaps the best way to address this is to ignore anything which is larger than, say, a million px in any dimension. For example scaling by keyboard already has the 1 million upper limit. However I'm reluctant to do that, as you never know what weird files people would want to edit. This arbitrary limit may bite us sometime.

what about scaling down or up the objects with "insane" bbox after issuing a warning/question when the file is opened? if it is a isolated case in the file (as the one attached in the bug I submitted) it will suppress the problem and focus the attention of the user on this (and if he knows about the xml editor he could delete the incriminated object). if the whole file has insane transform matrices (like the one to which I provided a link in the bug report) it will make its modification in inkscape easier. currently, in the second file, when I add anything it is insanely scaled (like strokes with 720 px of width) I think because all objects have transform matrices like this one: transform="matrix (2.007003e-3,0.000000,0.000000,-2.007003e-3,-6.079619e-2,1.461081)

I don't know if anything of this is meaningful but my impression was that, dealing with vector images, scaling won't be a problem.

JiHO --- Windows, c'est un peu comme le beaujolais nouveau : a chaque nouvelle cuvee on sait que ce sera degueulasse, mais on en prend quand meme par masochisme. --- http://jo.irisson.free.fr/