Issue 124867 - jpg options shows initially wrong estimated file size
Summary: jpg options shows initially wrong estimated file size
Status: RESOLVED FIXED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 3.4.1
Hardware: All All
: P3 Minor (vote)
Target Milestone: 4.2.0
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-10 13:12 UTC by owebmailo
Modified: 2016-06-06 17:18 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: 4.2.0-dev
Developer Difficulty: ---


Attachments
Screen capture (87.09 KB, image/png)
2014-05-10 13:16 UTC, owebmailo
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description owebmailo 2014-05-10 13:12:36 UTC
Export 1 --> jpg options --> qualité 100 --> taille du fichier 41.5 ko 

Export 2 --> JPG options --> qualité 100 --> taille du fichier 5.8 ko
Comment 1 owebmailo 2014-05-10 13:16:18 UTC
Created attachment 83369 [details]
Screen capture
Comment 2 Rainer Bielefeld 2014-05-11 07:05:07 UTC
@reporter:
Thank you for your feedback – unfortunately important information we will 
need to reproduce your problem is missing.
Englsh Language is mandatory here, if that is a problem for you please ask for help on the French language user mailing list
Please add all information requested in following:
a) Write a meaningful Summary describing exactly what the problem is
   "jpeg file size" is not the decription of a problem.
b) Attach a sample document (not only screenshot) or refer to an existing 
   sample document in an other Bug with a link; to attach a file to this 
   bug report, just click on "Add an attachment" right on this page.
   If you want to attach a test kit with multiple documents zip them into
   a single testkit.zip and attach the  testkit.zip
c) Contribute a document related step by step instruction containing every 
   key press and every mouse click how to reproduce your problem 
d) Your screenshot unfortunately tells me nothing.
   Attach screenshots with comments if you believe that that might explain the 
   problem better than a text comment. Best way is to insert your screenshots
   into a DRAW document and to add comments that explain what you want to show
e) if possible contribute an instruction how to create a sample document 
   from the scratch
f) add information 
   f1) what EXACTLY is unexpected. Too small, too beg, unexpected 
      because ... ?
   f2) and WHY do you believe it's unexpected (cite Help or Documentation!)
   f6) AOO settings that might be related to your problems 
      (video hardware acceleration, ...)
   f7) how you launch AOO and how you opened the sample document
   f9) Whether that worked in former OOO / AOO Versions 
   f10) whether (and how) a competitor's software (MSO, LibreOffice, ...)
        fulfills your needs

Please do not cite these hints in your reply, but cite the items like:
f7): Desktop-icon for soffice.exe / AOO File menu -> Open
Comment 3 j.nitschke 2014-07-02 11:21:02 UTC
as attachments 83369 shows the estimated file size file is initially with for a jpg quality of 1 and not the preselected value (in this case 100)

steps:
+ open draw
+ draw something
+ export
+ select file type JPEG

observe wrong estimated file size

after changing an option the size is calculated correctly

bug already in AOO 3.4.1

Impress shows same behavior as Draw, other components don't have JPEG export option
Comment 4 SVN Robot 2016-06-05 12:51:05 UTC
"damjan" committed SVN revision 1746906 into trunk:
#i124867#: jpg options shows initially wrong estimated file size
Comment 5 damjan 2016-06-05 12:52:46 UTC
Patch with explanation committed, resolving fixed.
Comment 6 SVN Robot 2016-06-06 14:16:04 UTC
"truckman" committed SVN revision 1747012 into trunk:
#i124867#:  bundled boost headers generate an excessive number of
Comment 7 orcmid 2016-06-06 17:18:40 UTC
(In reply to SVN Robot from comment #6)
> "truckman" committed SVN revision 1747012 into trunk:
> #i124867#:  bundled boost headers generate an excessive number of

This comment applies to Issue 126888 and not to the current Issue 124867.  Just ignore it.  The preceding comment provides the accurate status.