[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
[Thread Prev] | [Thread Next]
- Subject: Re: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
- From: John Hardy <johnhardy@johnhardyco.com>
- Date: Sun, 20 May 2012 00:48:37 -0500
- To: users@global.libreoffice.org
Marc;
BTW ... I downloaded your graphic. I am not all that familiar with Draw, how do I go about finding out the dimensions of your drawing so that I can compare its size to the EPS version?
The reference file file should look properly scaled when viewed in Draw. You can see it correctly scaled by visiting the product page and looking at the picture of the correctly scaled image as printed on the product:
http://www.johnhardyco.com/990OpAmpDetails.html
It is when you "Export" the file using the "EPS" file-type and view the EPS file with GIMP (and other viewers) that you can see that things are scaled incorrectly. The first clue when viewing the EPS file: Look at the model number, "990c". The "c" is overlapping the "0". It is not supposed to overlap. I created two separate text boxes, one for the "990" and one for the "c", so that I could control the spacing between the main part number ("990") and the suffix ("c"), as well as use different sizes for the text in each box. Somehow during the incorrect scaling everything gets about 10% bigger and the "c" overlaps the "0" as a result.
If you take the reference file and "Export as PDF", it should be correctly scaled when viewed as a PDF (the "c" does not overlap the "0"). So something is different between "Export as PDF", and "Export" with the "EPS" file-type chosen. Yet both methods work OK in OpenOffice 3.3.
Let me know if you need further information or example files. But comparing the results of ["Export as PDF"] and ["Export" with the "EPS" file-type] should reveal that the EPS approach is not scaling things correctly.
Thank you.
John
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
| [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement. | Marc Paré <marc@marcpare.com> |
| Re: [libreoffice-users] Bug #48365 filed six weeks ago. No sign of acknowledgement. | Tom Davies <tomdavies04@yahoo.co.uk> |
| Re: [libreoffice-users] Bug #48365 filed six weeks ago. No sign of acknowledgement. | John Hardy <johnhardy@johnhardyco.com> |
| [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement. | Marc Paré <marc@marcpare.com> |
| Re: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement. | John Hardy <johnhardy@johnhardyco.com> |
| [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement. | Marc Paré <marc@marcpare.com> |
- Prev by Date: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
- Next by Date: Re: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
- Previous by thread: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
- Next by thread: [libreoffice-users] Re: Bug #48365 filed six weeks ago. No sign of acknowledgement.
- Index(es):
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License (LGPLv3). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.