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\..).
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
I confirm this bug: LibO version: 5.2.0.0.alpha1; Build ID: 902b28a39528b6c92602e9b521a1d0861be1caf9 OS Version: Windows 5.2 x64
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
I confirm this bug. Версия: 5.4.0.0.beta1 ID сборки: 8672113ead4e403c55e31b1d9a3d1e0f3b299577 CPU threads: 4; OS: Linux 4.4; UI render: по умолчанию; VCL: gtk2; Локаль: ru-RU (ru_RU.UTF-8); Calc: group
Версия: 5.4.0.0.beta1 ID сборки: 8672113ead4e403c55e31b1d9a3d1e0f3b299577 CPU threads: 4; OS: Linux 4.4; UI render: по умолчанию; VCL: gtk2; Локаль: ru-RU (ru_RU.UTF-8); Calc: group I set value: Tools> Option> Load/Save> General> ODF_format_version = 1.2. LibreOffice-5.4.0.0.beta1 created fake SVM files too.
When the storage mode is set to "1.2", svm is saved instead of svg. So users that want strict ODF, do not get it.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6b3cc69fd2b2de5ace68f2739eb383267d66f76f Related tdf#72966 Provide replacement graphic also for metafiles It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=f6ce8116b14892e26549c2dc2d59044a961c1dff&h=libreoffice-6-0 Related tdf#72966 Provide replacement graphic also for metafiles It will be available in 6.0.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=2d3023c9713c4c7cac732a6831c69dec581a7751 Related tdf#72966 Provide replacement graphic also for metafiles It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Samuel Mehrbrodt committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e8f20a5c2731f3aecffa515dc73a3fc071af6d6&h=libreoffice-6-0 Related tdf#72966 Provide replacement graphic also for metafiles It will be available in 6.0.0.1. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
A polite ping to Samuel Mehrbrodt: is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Thanks
(In reply to Xisco Faulí from comment #18) > A polite ping to Samuel Mehrbrodt: is this bug fixed? if so, could you > please close it as RESOLVED FIXED ? Thanks Ping
Dear ape, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still reproducible in 版本：6.4.0.0.alpha1 組建 ID：cc57df8f942f239d29cb575ea5a7cb01405db787 CPU 執行緒：4; OS：Linux 5.2; UI 算繪：預設; VCL: kf5; 語言地區：zh-TW (zh_TW.UTF-8); UI-Language: zh-TW Calc: threaded But I wonder if it needs to be fixed or not...
The problem still exists in Version: 7.1.0.0.alpha0+ (x64) Build ID: 1e0cfd5662d95cea84e80e4fe10d52c3b1101ae6 CPU threads: 8; OS: Windows 10.0 Build 18362; UI render: Skia/Vulkan; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL
The behavior of LO is ODF conform. Because svm is a propriety format of StarOffice it could contain anything. There exists no specification of format "svm". If an application is not able to use it, it will use the png file. That is the intended behavior of having several draw:image elements. For the current ODF 1.3, LibreOffice saves the svg image and the png image. I see no sense in developing a changed behavior for export to ODF 1.1 and suggest to close it as "Wont Fix".
This seems like an old then justified bug, but with LO saving as 1.2 or 1.3, no repro. It's not necessary so I close per previous comment. Note bug 147248.