forked from amazingfate/loongoffice
Despite the purpose of the new interoperability styles
added in commit b2d8093b19642038631dfb8f1ab6745a380a652c
(tdf#127499 added 9 new line styles all are (var) and in line with MSO),
collision with commit 57c9bdab377a00649299d1a4c9ed2f9e5e03b84e
(tdf#127166, tdf#123903 improve import/export of line styles)
resulted still missing interoperability on the user interface:
1) opening an OOXML document, preset styles weren't recognized
on the UI, also the preview was a solid line on the Drawing
Object Properties toolbar.
2) using the new compatibility preset styles, OOXML export
resulted custom styles instead of the intended preset styles.
On the UI, now the layout of the first 10 preset dash styles
follows the OOXML standard, see 20.1.10.49 ST_PresetLineDashVal
(Preset Line Dash Value) in ISO/IEC 29500-1, 2016:
dash pattern name (OOXML name)
10 "Dot" (sysDot)
1000 "Long Dot" (dot)
1110 "Dash" (sysDash)
1111000 "Long Dash" (dash)
11111111000 "Double Dash" (lgDash)
111010 "Dash Dot" (sysDashDot)
11110001000 "Long Dash Dot (dashDot)
111111110001000 "Double Dash Dot" (lgDashDot)
11101010 "Dash Dot Dot" (sysDashDotDot)
1111111100010001000 "Double Dash Dot Dot" (lgDashDotDot)
Note: add missing "Dash Dot Dot" (sysDashDotDot).
Remove "Double Dot": it really wasn't an OOXML-compatible preset
style, and it has a good replacement among the older styles,
the similarly loosely dotted "Fine dotted", which is still
supported for back-compatibility.
Note: to start the new UI test, use
$ (cd sw; make -srj8 UITest_writer_tests7 UITEST_TEST_NAME="tdf139301.tdf139301.test_tdf139301" SAL_USE_VCLPLUGIN=gen)
Change-Id: Ifc3fa634f2170aada61632e0a419d35dcaaf5ef6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110386
Tested-by: Jenkins
Reviewed-by: László Németh <nemeth@numbertext.org>
Contains templates, clipart galleries, palettes, symbol font, autocorrections, autotexts etc. How-to add a new gallery: + create a directory extras/source/gallery/foo/ + create a .str file extras/source/gallery/foo/foo.str + add a [foo] section to extras/source/gallery/share/gallery_names.ulf + add a Gallery_foo.mk at the top-level (and mention in Module_extra.mk) + add a new GALLERY_FILELIST statement in scp2/ How-to add a new autotext category + create a directory extras/source/autotext/lang/xx/foo/ where xx is your lang code. xx must exactly fit with an UI lang code. + unzip your foo.bau autotext file in this directory (including an empty mimetype file) + add xx/foo.bau in extras/AllLangPackage_autotextshare.mk + in extras/CustomTarget_autotextshare.mk: + add xx/foo in extras_AUTOTEXTSHARE_AUTOTEXTS + add all files contained in foo.bau (except mimetype) in extras_AUTOTEXTSHARE_XMLFILES + if foo.bau contains files with other extension than .xml, .rdf, .svm and .png + add a CPY call at the end of the file How-to add a new autotext to an existing category + create a directory extras/source/autotext/lang/xx/standard/FOO/ to add it in category standard of lang xx + add files of the autotext (at least FOO.xml for an unformatted autotext) + add autotext name in extras/source/autotext/lang/xx/standard/BlockList.xml + add all files of autotext in extras/source/autotext/lang/xx/standard/META-INF/manifest.xml + in extras/CustomTarget_autotextshare.mk: + add all files of autotext in extras_AUTOTEXTSHARE_XMLFILES + if some files have different extension from .xml, .rdf, .svm and .png + add a CPY call at the end of the file How-to add a new Impress template + clean-up template file as indicated on wiki https://wiki.documentfoundation.org/Documentation/HowTo/Impress/Make_template_language_independent + unzip Foo.otp in extras/source/templates/presnt/Foo (no space allowed in any file names) + add Foo.otp in Package_tplpresnt.mk + in CustomTarget_tplpresnt.mk: + add Foo / in extras_TEMPLATES_PRESENTATIONS + add files names contained in Foo.otp (except mimetype) in extras_PRESENTATIONS_XMLFILES + if Foo.otp contains files with other extension than .xml, .svm, .svg, .png and .jpg + add a CPY call at the end of file How-to add a new Writer template + clean-up template file as much as possible, and choose a template category <Category> + unzip Foo.ott in extras/source/templates/<Category>/Foo (no space allowed in any file names) + add Foo.ott in Package_<tplCategory>.mk + in CustomTarget_<tplCategory>.mk: + add Foo / in extras_TEMPLATES_<CATEGORY> + add files names contained in Foo.otp (except mimetype) in extras_<CATEGORY>_XMLFILES + if Foo.ott contains files with other extension than .xml, rdf, .svm, .svg, .png and .jpg + add a CPY call at the end of file How-to add a new template category + create a directory extras/source/templates/foo/ + unzip your foo0.ott template files in extras/source/templates/foo/foo0 + add Package_tplfoo and CustomTarget_tplfoo in Module_extras.mk + use other category Package_tplcategory.mk to create Package_tplfoo.mk + use other category CustomTarget_tplcategory.mk to create CustomTarget_tplfoo.mk + replace all category by foo and CATEGORY by FOO + add all files contained in foo0.ott (except mimetype) in extras_FOO_XMLFILES + if foo0.ott contains files with other extension than .xml, .rdf, .svm, .svg, .png and .jpg + add a CPY call at the end of the file + optionally, replace extension ott (4 places)