Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix for #383: Strange behavior of cloneRow with multiple tables #392

Closed
wants to merge 1 commit into from
Closed

Bugfix for #383: Strange behavior of cloneRow with multiple tables #392

wants to merge 1 commit into from

Conversation

scmember
Copy link

@scmember scmember commented Oct 4, 2014

Added a check for the end of table, for correct processing of multiple tables with spanned rows

Added a check for the end of table, for correct processing of multiple tables with spanned rows
@Progi1984
Copy link
Member

May be @RomanSyroeshko could take a look to this ?

@FBnil
Copy link

FBnil commented Oct 21, 2017

@scmember Can you close this pull request, problem has been identified and I have a patch request ready.

Your proposal for a fix is not quite correct, it would match MSWord docx documents, but not LibreOffice docx documents due to them not having extra spaces just before a close (/>).
i.e. This works: preg_match('#<w:vMerge ?/>#', $tmpXmlRow) (idem with the others preg_matches)

Because of this, tables made with OpenOffice would never match and go outside the table. Making cloneRow() not that useful when w:vMerge was encountered.

Superseded by #1147

@scmember
Copy link
Author

@FBnil agree, close this pr

@scmember scmember closed this Jan 14, 2018
@scmember scmember deleted the scmember-383-patch branch January 14, 2018 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants