Hi, There is a bug I am trying to fix regarding line numbering. In Word, a line numbering node typically looks like this: It seems like the DOCX importer does not make use of the imported 'w:start' attribute (it is imported here<http://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/DomainMapper.cxx#1380> ). What I saw was that in the function "PropertyMap::CloseSectionGroup<http://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/PropertyMap.cxx#830>" there is a check if "m_nLnnMod" is set. The function also looks at "m_nLnnMin" when setting the "PROP_PARA_LINE_NUMBER_START_VALUE". However, this "m_nLnnMin" is set in only when the parser reads the NS_sprm::LN_SLnnMin<http://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/DomainMapper.cxx#2537>value. In addition, the "m_nLnnMod" is set only when the parser reads the NS_sprm::LN_SNLnnMod<http://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/DomainMapper.cxx#2519>value. Am I correct to assume that these values are read only in the DOC importer, and not in the DOCX importer? Is it true to say that DOCX attributes are always 'NS_ooxml::….' ? If I am correct – when I parse the 'start value' in the relevant ' NS_ooxml::LN_CT_LineNumber_start<http://opengrok.libreoffice.org/xref/core/writerfilter/source/dmapper/DomainMapper.cxx#1380>' node, should I simply mimick the behavior of the 'NS_sprm::LN_SLnnMin' parsing? Best, *Adam Fyne* *Office:* +972-77-517-5008 Twitter <http://www.twitter.com/cloudoninc> | LinkedIn<http://www.linkedin.com/company/cloudon> | Facebook <http://www.facebook.com/cloudoninc> | Blog<http://www.cloudon.com/>