Can we, yet, format images so that they are set off to the set (see Knowing Home, chapter 7); one set of images?
- At this time, with the current limitations of Pressbooks, we recommend that all images are centered and do not exceed 400-500 px in width and 600 px in height. Sometimes the images need to be smaller so that they display well on both the web version and PDF file.
Can we have a “select all” box for Export on Text page?
- Not yet. Have add this idea to our “wish” list.
Problem (again): how do we address referencing between pages (PDF vs web version)?
Ask about headings and styling with all 6 different levels. Why caps? Who set this up?
- this styling was set up awhile back; test this in the different themes; does this happen with the OTB Theme? Other PBs themes?
- This creates a div tag for the classic textbox. It allows you to fill in your own requirements for a class, e.g. “shaded” textbox.
- The icons were developed by our developer specifically for open textbooks. The icons in the dropdown menu are stock features released by Pressbooks, and are not formatted the same way.
- Not easily. Theoretically, it can be done in the Text view using html. However, unless the code has been tested and is xhtml compatible, there is no guarantee that the desired layout will stay intact in the exported files.
- Yes. We have done this for other books when creating sidebars or have wanted to highlight a section. We have use both plain and shaded textboxes (selected from the Textboxes dropdown list.) Typically, these textboxes contain both text and the image, which supplements the text. If you add a description to the ALT TEXT field for the image, I’m not sure how the textbox will affect the ability of screen readers to access the ALT TEXT.
- This is possible, but complicated and not recommended.
- Can do it; have to copy a lot of html. If try to link using short code, doesn’t work. Need to copy code from rendered page and from the bottom of the page.
- This is not required. It’s there to offer another option for styling. The fields describe in which outputs these additional items appear.
- Sometimes a symbol won’t render because it is not in the font library. It might render as a question mark or diamond if it’s not in the library. If you want to check how it will look, examine the Book view for the web version and try exporting a sample chapter to check the various file types.
Tables: see Part 1 and chapter 1, section 4
- This section has 2 tables and one image.
- We tried adding tables to see if the content would work better. The tables on the web interface are showing scroll bars.
- In the PDF, the table is mushed into the paragraph below.
- What to do?
We checked the html and found the vertical scrollbar appears because whoever coded the table set its height to 220px: <table class=”lines undefined aligncenter” style=”height: 220px” width=”550″>.
To fix this, just remove [style=”height:220px”] . Right now that’s capping the table’s height at 220px. Since the table holds enough rows to extend past 220px by default, it creates a scrollbar, instead of letting the table extend down naturally.
When links are made from one chapter to another, they work well for the web interface. The same links don’t work for the pdf version. The link takes the person to the web version of the document instead of the location in the pdf. Is there a way to handle this?
- Yes. The Pressbooks Guide (created by pressbooks.com, not our team) has a good description of this on the chapter called: Adding Hyperlinks, Internal and External
- See the section called “Internal Links”. Here is an example:
- Instead of using this: <a href=”http://opentextbc.ca/abealf6/back-matter/appendix/”>Appendix 3</a>
- You would use this: <a href=”/back-matter/appendix/”>Appendix 3</a>
- This will work for both the web version and PDF.