496197fe4d
Which means CT_NumFmt has to be a property resource, not a single value, and also ST_NumberFormat needs to recognize "custom" as a valid value. Adapt the RTF tokenizer to emit the new token format. This is needed (but not enough) to support markup like this: <w:numFmt w:val="custom" w:format="001, 002, 003, ..."/> Change-Id: I767e4b92fc41f9425f446d6eaad1d875e2233964 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/90578 Reviewed-by: Miklos Vajna <vmiklos@collabora.com> Tested-by: Jenkins |
||
---|---|---|
.. | ||
README | ||
rtfcharsets.cxx | ||
rtfcharsets.hxx | ||
rtfcontrolwords.cxx | ||
rtfcontrolwords.hxx | ||
rtfdispatchdestination.cxx | ||
rtfdispatchflag.cxx | ||
rtfdispatchsymbol.cxx | ||
rtfdispatchvalue.cxx | ||
rtfdocumentfactory.cxx | ||
rtfdocumentimpl.cxx | ||
rtfdocumentimpl.hxx | ||
rtffly.hxx | ||
rtflistener.hxx | ||
rtflookahead.cxx | ||
rtflookahead.hxx | ||
rtfreferenceproperties.cxx | ||
rtfreferenceproperties.hxx | ||
rtfreferencetable.cxx | ||
rtfreferencetable.hxx | ||
rtfsdrimport.cxx | ||
rtfsdrimport.hxx | ||
rtfskipdestination.cxx | ||
rtfskipdestination.hxx | ||
rtfsprm.cxx | ||
rtfsprm.hxx | ||
rtftokenizer.cxx | ||
rtftokenizer.hxx | ||
rtfvalue.cxx | ||
rtfvalue.hxx |
= Writerfilter-based RTF tokenizer == Mathematics At the time of writing, all control words understood by SmOoxmlImport are imported. To view the current status: ---- grep M_TOKEN starmath/source/ooxmlimport.cxx |sed 's/.*\(M_TOKEN(\) /\1/;s/ ).*/)/'|sort -u > ~/math-import-list grep '[^_]M_TOKEN' writerfilter/source/rtftok/rtfdocumentimpl.cxx |sed 's/.*\(M_TOKEN(\)/\1/;s/).*/)/'|sort -u > ~/wf-export-list diff -u ~/math-import-list ~/wf-export-list |grep ^-M_TOKEN ----