-
Notifications
You must be signed in to change notification settings - Fork 10
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
Fix line break behavior of inline code/literals in PDF #427
Comments
@jfaltenbacher Can you try to find out what Stefan meant by this? If we can't verify what's behind this report we'd have to close it. |
Also, as we want to handle PDF generating differently in the future, we might not want to touch legacy PDF stylesheets at all. |
I will ask Patrick directly, if he can explain. Will ask Padraig first, if he has some conversation on this |
Hi all,
Stefan was suggesting running a S&R routine on the XML to replace occurrences of " So, the following:
I think we will have to rely on DTP QA to catch such occurrences, since these terms are not in
An example of text overflow can also be seen in the AutoYaST book, English, page 160: |
It seems, for SLE15SP4 tables are replaced by lists. Lists don't have these problems that Patrick described above. Need to investigate further. |
@ptinley-vt please check with current SLE 15 SP5 loc drop if the issue still occurs |
@jfaltenbacher, in SLE 15 SP5 I have used the zero-width-space character () to improve layout of a number of issues in the SLES AutoYaST Guide and the SLES and SLED Security Guides by breaking lines. These issues were found by QAing the PDFs. |
ptinley made us aware of the things they undertake to fix display of tables in the AY Guide (for 15 SP2), we should try to see what we can do to make this work less necessary, e.g. add zero-width spaces within literals in PDF.
(This is probably a dupe but I guess it bears repeating.)
The text was updated successfully, but these errors were encountered: