Skip to content
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

Rendering/Display issues using cfr.xsl #63

Open
anuraggulati opened this issue Aug 19, 2020 · 2 comments
Open

Rendering/Display issues using cfr.xsl #63

anuraggulati opened this issue Aug 19, 2020 · 2 comments

Comments

@anuraggulati
Copy link

anuraggulati commented Aug 19, 2020

  1. Font changes from sans-serif family (Helvetica) to serif-family Times New Roman
  2. The space between section and the title. (between section 43.1 and the Purpose, Scope and rules of construction, for example. Happens consistently for all section numbers and section headings)

See screenshots.
Screenshot 2020-08-19 at 6 38 08 am

Screenshot 2020-08-19 at 6 37 53 am

@jonquandt
Copy link
Member

Thanks for reporting this. We'll take a look at it. It appears that the space between the section number and the section title is intentional, though it is acting in a responsive manner, so the wider your window is, the wider the gap. That may not be ideal. The equivalent PDF has a gap as well, but the pdf is in a two column layout, which would force a smaller space.

See via the UI:
Details
xml
pdf

Note that the xml for the UI is broken down to the section level compared to the volume level breakdown in the bulkdata repository.

Need to do a little investigation on the sans-serif to serif issue, since the xsl doesn't reference serif fonts at all. all of the font-family declarations simply state "sans-serif", though one for .GID has Sans-serif. I don't think that would affect anything, but may be an issue.

Adding to our backlog to address.

I also discovered a slight discrepancy between the cfr.xsl used in our bulkdata repository and the UI (/content/pkg) version . Will look at that as well.

@anuraggulati
Copy link
Author

anuraggulati commented Aug 28, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants