forked from amazingfate/loongoffice
Now the default for using the SVG tiny profile is false. Now the default for use native text decoration is true. Fixed the following issues: 1) Text decoration (underline, strike-out) was not exported. 2) Commit 0a4e913 (tdf#56467: improve export of formulas to SVG) had a side effect: all exported text portions have position attributes (x,y) even if they are on the same line (y_old == y_new): this caused that underlined text belonging to 2 different `tspan` element was not underlined by a continuous line but there was a gap where a `tspan` ended and the next `tspan` started. 3) In commit (tdf#37650: further improvement of svg export) StartTextShape method is invoked even when positioned characters are used but the `implWriteText` method always adds a `text` element by itself so there is no need to call StartTextShape. The changes for non-positioned characters have been embedded inside the `WriteTextPortion` method. Change-Id: Iee0d6a6816dcbd2d97f2fbdf969f012de678604e Reviewed-on: https://gerrit.libreoffice.org/19672 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Jan Holesovsky <kendy@collabora.com>
Filter registration and some simple filters (also descriptions). Desperate splitting of code into small shared libraries for historical reasons presumably (OS/2 and Windows 3.x). The libraries produced from the code in each subdirectory of filter/source/graphicfilter are graphic format import or export filters. But they don't have uniform API. Some have either an GraphicImport or GraphicExport entry point, and are loaded and used in a uniform fashion from code in svtools/source/filter/filter.cxx. Others have different API and are loaded from other places. For instance "icgm" has ImportCGM, and is loaded and used by sd/source/filter/cgm/sdcgmfilter.cxx (!). Svgreader is used for "File->Open" and then to choose the svg file. For "Insert->Picture->From File", see svgio/source/svgreader directory. ==================== filter configuration ==================== The filter configuration consists of two parts, the type definition in filter/source/config/fragments/types/ and the actual filter definition in filter/source/config/fragments/filters/. Each file type e.g. text file should be represented by exactly one type definition. This type can then be referenced by several different filters, e.g. calc text, writer text.