Created attachment 91121 [details] file as example LibreOffice-4 creates fake SVM file: 1. Run the program (LibO_4.0.0 ÷ 4.3.0.0+). 2. Set the value: Tools> Option> Load/Save> General> ODF_format_version = 1.0/1.1. 3. Create a new file and insert the SVG file as image and then save new document (the result – see an attachment). 4. Run the archiver. 5. Extract the SVM and PNG files from the ODF document. 6. Compare the file sizes - they are the same. 7. Open the SVM file from the simple bitmap editor. I used The Irfan View (Windows OS). It opened the file and informed me that the file is in PNG format.
There is no need to use svm. Older versions of OpenOffice can read the png file. That way it is done in AOO. It contains the svg image and a png file.
(In reply to comment #1) > There is no need to use svm. Older versions of OpenOffice can read the png > file. That way it is done in AOO. It contains the svg image and a png file. -- @Regina: Read the posts (bug 62461) please. It seems to me that the introduction of the AOO’s patch was a big mistake. PNG preview image (scale 30% of the original) can’t be a substitute for the full file. -- ape
(In reply to comment #1) > There is no need to use svm. Older versions of OpenOffice can read the png > file. That way it is done in AOO. It contains the svg image and a png file. At the bare minimum it would make sense to change file extension to reflect real format. To use SVM is definitely not a good idea -- outside StarOffice derivatives nobody supports it. At the same time the way LO adopted AOO patch doesn't seem to be well thought through.
I see, that dpi of the png has been reduced from OOo341 to LO41. But that is a different issue than using svm and effects the embedded .png file as well. What do you want to be the content of the .svm file? ODF1.0 makes only sense to be read from old OOo versions, and those cannot read .svg format. So you would need to break the .svg image into Draw objects.
(In reply to comment #4) > I see, that dpi of the png has been reduced from OOo341 to LO41. But that is > a different issue than using svm and effects the embedded .png file as well. > > What do you want to be the content of the .svm file? ODF1.0 makes only sense > to be read from old OOo versions, and those cannot read .svg format. So you > would need to break the .svg image into Draw objects. Regina, I have no problem if PNG is used instead of SVM. What I don't like though is to have PNG stored with SVM as an extension, while it's NOT svm. Plus what's the point to save PNG and its second copy with different extension?
Created attachment 91144 [details] ODT file with fake and native svm images @Regina: The SVM file is the drawing object. It has a nice view under magnification. But we have now a bitmap object PNG image, which has the wrong someone else's extension (*.svm). This fake SVM file is an exact copy of a low-quality preview PNG image. Open the file “fake&native_svm.odt” and set the zoom to 600%. Are you convinced now that “fake SVM” there is a bad substitute for the native SVM file or the high quality (pixel by pixel) PNG image? p.s. It is possible that you have forgotten. AOO-4 does not convert the SVG object to the Star View Metafile in the “Pictures” folder, when saves the file as ODF version 1.0/1.1.
(In reply to comment #4) > I see, that dpi of the png has been reduced from OOo341 to LO41. But that is > a different issue than using svm and effects the embedded .png file as well. > > What do you want to be the content of the .svm file? ODF1.0 makes only sense > to be read from old OOo versions, and those cannot read .svg format. So you > would need to break the .svg image into Draw objects. I saw that SVM format is also used in the charts. Look at this attachment 93391 [details] (Eckert.ods\Object 2\Pictures\..).
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.