-
Notifications
You must be signed in to change notification settings - Fork 23
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
Proper text wrapping of long descriptions #85
Comments
Thank you for the compliment. A schema is rendered by creating a grid table for it. Thus a schema is transformed into
(didn't check for validity, I'm sure you understand what I'm trying to say). In fact all parts of a schema are expressed using existing reStructuredText elements. There is no support assigning css classes to individual tables. I had the same problem as you and my solution is to make extensive use of One thing I do not really understand is why the regular text in the descriptions isn't wrapped within the available width. I'm sorry I cannot be of more help at the moment. |
Hi @lnoor, Thank you for the extended information! We are indeed already using We have a custom CSS, but as far as I know, text wrapping shouldn't be disabled. With best regards, |
Hi @lnoor, FYI: I found and solved the issue: It was related to the See also https://stackoverflow.com/questions/69359978/grid-table-does-not-word-wrap |
Hi @tomghyselinck, I'm glad you found the cause and a work-around. With regards, |
Hi,
We like this project very much!
One thing which makes documentation hard to read for our users is when the description contains long lines of text.
It seems that those are not properly wrapped (like is done in a normal section in sphinx documentation).
Instead we get a scroll bar below the schema. For large schema's this becomes quite cumbersome to read the documentation:
For example:
Can you tell us how to avoid this? Is there some styling (CSS?) parameter we can add / change to our documentation? Is there a different option we can set?
The text was updated successfully, but these errors were encountered: