Date: prev next · Thread: first prev next last


Hello,

My name is Bartosz, and I'm LibreOffice developer, which mostly working on EMF+, xls, xlsx, docx 
import/export features:
https://wiki.documentfoundation.org/User:Gang65

I have started improving Visio import, for example with Pull Request:
https://gerrit.libreoffice.org/#/c/74743/14

To fix next Visio issues I need to improve librevenge library first:

The RVNGDoubleProperty property is supporting one format conversion to
string. It is "%.4f". It print as a floating point with a precision
of four characters after the decimal point.
 
Example:
 Number: 3.14 will be converted to string "3.1400"
 
In some libraries (libvisio), there is a need to convert double
type property to different formats.
 
For example with different precision after decimal point, or without
trailing zeros:
Example:
 - 3.14    (format:  "%.3g"
 - 3.140 (format:  "%.3f"
 
This patch adds new method to RVNGProperty:
   virtual RVNGString getStr(const char* format) const;
 
It allows to change default string format of every property:
https://pastebin.com/GTruzDS3

Thanks in advance 
Bartosz

-- 
To unsubscribe e-mail to: devel+unsubscribe@documentliberation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentliberation.org/www/devel/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


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 Mozilla Public License (MPLv2). "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.