-
Notifications
You must be signed in to change notification settings - Fork 0
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
(PDF) Breaking words in table cells through word-wrap when width is insufficient #154
Comments
@ReesePlews Thanks for raising this. @Intelligent2013 Can we automatically insert hyphenated word wraps in this case? A word extending beyond a table cell cannot be right... |
Apache FOP supports hyphenation via the 'Objects For Formatting Objects' project (https://xmlgraphics.apache.org/fop/2.10/hyphenation.html). I'll integrate hyphenation into the |
Hyphenation support added in mn2pdf v2.14 (https://github.com/metanorma/mn2pdf/releases/tag/v2.14) and in Plateau XSLT. To use it, need add these lines into
and execute |
hello @Intelligent2013 thank you for the modifications, that looks very nice! i will try a local build, with the updated Gemfile as you have shown above, later this week. i will report back here. thank you! |
hello @Intelligent2013 i was able to successfully build a local version of the document using the modifications to the gemfile you have listed above. in addition to this issue, the changes you made for the terminology clause: were also correctly shown. i think both of the issues are correctly fixed. however i have one observation. normally when i do a local build it takes about 40 minutes or so. this time it it felt like it took more than 1.5 hours. when will these revisions be updated to the main branch? |
ping @opoudjis
@ReesePlews these revisions updated in the main branch already (repositories |
hi @Intelligent2013 thank you for that update and the clarifications. i had created a list of fixed issues for Nick, but this information is helpful. thank you again for working on this fix, the output looks much better. i will check a build with the main branch today and if everything is ok, i will close this and any related issues. |
i think MS-Word has a special switch for handling these type of situations (shown in the image below) with non-dbcs strings.
when this happens in non-autogenerated tables i think it may be possible to hyphenate them manually (with a hyphen and carriage return), but i have never tried this. i do not know how this could be handled in an autogenerated table, perhaps a similar operation would work.
@ronaldtse can you of the other developers confirm or recommend a successful workaround for these situations? thank you.
The text was updated successfully, but these errors were encountered: