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

Support for Merged Cell in Tables #49

Open
ccelestial opened this issue Oct 21, 2016 · 6 comments
Open

Support for Merged Cell in Tables #49

ccelestial opened this issue Oct 21, 2016 · 6 comments

Comments

@ccelestial
Copy link

ccelestial commented Oct 21, 2016

I have an html to be converted to word doc:

<table align="center" border="1" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Lorem Ipsum with Colspan 2</td>
</tr>
<tr>
<td><strong>Lorem Ipsum</strong></td>
<td><strong>Lorem Ipsum</strong></td>
</tr>
</tbody>
</table>

It suppose to look like this:
screen shot 2016-10-21 at 3 01 09 pm

But in my document it appears to be like this:
screen shot 2016-10-21 at 2 19 58 pm

Does anyone have a solution for this?

@frankvilhelmsen
Copy link

the table seems to be fine,, maybe there is something external, css styles or otherwise.

@ccelestial
Copy link
Author

ccelestial commented Oct 21, 2016

I think the gem is not supporting the conversion of colspan of HTML to "w:vmerge" or "w:hmerge" of WordprocessingML.

@ccelestial
Copy link
Author

@frankvilhelmsen I edited the description and added a screenshot of what I'm getting in my pdf conversion.

@stats
Copy link

stats commented Oct 26, 2016

You should be look at Tables.xslt which contains all of the code for styling tables. There is no vmerge or hmerge as part of the xslt. The tables code basically supports border properties and nothing else.

@ccelestial
Copy link
Author

Hi @stats, that's also the file I referred that's why I saw that the gem aren't supporting vmerge or hmerge yet.

@lukelex
Copy link

lukelex commented Mar 22, 2018

@ccelestial I agree that this might be a good feature to have but since we don't use it we won't be investing time on it in the near future. BUT you're more than welcome to create a PR and we'll merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants