Created attachment 806906 [details] RHEV admin guide Description of problem: malformed PDF (example attached) The PDF renders at approximately half the size of the page, due to a series of long strings in a number of topics. Example: Table 1. v3_2_statistics_datacenters_resources_usage_daily\v3_2_statistics_datacenters_resources_usage_hourly\3_2_statistics_datacenters_resources_usage_samples Version-Release number of selected component (if applicable): [jbiddle@localhost publican]$ rpm -qi publican Name : publican Version : 3.2.1 Release : 0.fc19 Architecture: noarch Install Date: Tue 24 Sep 2013 10:52:48 AM EST Group : Applications/Publishing Size : 3140894 License : (GPLv2+ or Artistic) and CC0 Signature : RSA/SHA256, Thu 12 Sep 2013 02:19:23 AM EST, Key ID 07477e65fb4b18e6 Source RPM : publican-3.2.1-0.fc19.src.rpm Build Date : Mon 09 Sep 2013 09:21:45 AM EST Build Host : buildvm-10.phx2.fedoraproject.org Relocations : (not relocatable) How reproducible: 100% Steps to Reproduce: 1.Build locally or publish the book in question with the offending topics included 2. 3. Actual results: PDF is 50% of page size because the figure titles aren't wrapping correctly Expected results: Full page PDF with figure titles wrapping as necessary Additional info: Tested locally and via brew; confirmed that when the offending topics are commented out, the pdf builds correctly.
This title is a single word. Without a space, hyphen, or full stop there is nowhere safe for this word to be broken, the word is as likely to be broken in the middle of an English word as it is on an underscore or back slash; that would read horribly. IMO the bug is in the tool that is creating a title that is poorly structured. This bug should be moved to that product.
> IMO the bug is in the tool that is creating a title that is poorly > structured. This bug should be moved to that product. There should be a BZ component to cover "writer error". If the particular configuration of this string can't be broken, then we'll manually break it. Before I close-notabug, Jeff can you please confirm if space/hyphen/full stop are the only characters that will break a string appropriately? Are there any others?
I'm not sure of the complete list of word boundaries. http://www.w3.org/TR/css3-text/#soft-wrap-opportunity
At any rate, I'll make sure that long strings will at least contain a hyphen to break them up. Thanks for the assistance Jeff.