Adding numbered list to an imported docx causes export to not load in Word

[jkgfullstop]

What happened?

When importing a docx made in Word that does not contain a numbered list, then adding the first numbered list in the super-editor, and exporting the docx, the docx cannot be opened in Word and cannot be repaired. The docx renders fine in super editor. This has to do with how super editor is creating that numbered list without the w16cid namespace for w:numbering.

Steps to reproduce

1. Create a blank Word document
2. Import it into Super Editor
3. Add a numbered list
4. Export to DOCX
5. Open in Word - Fails to Open

SuperDoc version

1.43.1

Browser

Chrome

Additional context

This happens because the XML namespace for w:numbering does not contain the w16cid and w16cex namespaces in the <w:numbering> declaration, but uses at least w16cid:durableId.

Adding those namespaces to the NUMBERING_ROOT_ATTRS in packages/super-editor/src/editors/v1/core/parts/adapters/numbering-part-descriptor.ts makes things export properly.

  'xmlns:w16cid': 'http://schemas.microsoft.com/office/word/2016/wordml/cid',
  'xmlns:w16cex': 'http://schemas.microsoft.com/office/word/2018/wordml/cex',

[linear-code]

IT-1217

[teo-azzollini]

Hi @jkgfullstop thanks for reporting this! I am testing this and just want to make sure we are seeing the same behavior here. Once you export the document that contains the list created in SuperDoc and try to open in word do you get an unreadable content error from word with the option to "trust" the document with a "yes" and "no" button? Once you press "yes" do you then get another pop up titled "Show Repairs" where it calls out the list being the issue?

This is the behavior I am seeing on my end where you can technically open the document if you press "yes" to trust the document. Either way we will get this fixed so that no errors appear on initial load in word after exporting but I just wanted to check to see if this is the same behavior you are seeing. Thanks!

[jkgfullstop]

Thank you @teo-azzollini. You are absolutely right about the described behavior; I was mistaken that it was not repairable after doing the trust document yes.