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

text formatting in footer boxes #121

Closed
aausch opened this issue Sep 11, 2013 · 4 comments
Closed

text formatting in footer boxes #121

aausch opened this issue Sep 11, 2013 · 4 comments

Comments

@aausch
Copy link

aausch commented Sep 11, 2013

this chunk of CSS:

@page{      
   @bottom-center {
    content: "Some content <i>Some italic content</i>  Some other content";
  }
}

should probably generate text that looks like so:

Some content Some italic content Some other content

instead of the attached image:
weasyprint-footer-format

@SimonSapin
Copy link
Member

No, it should not. String values in the content property are just text, definitely not HTML.

I agree that something similar should be possible, we just don’t yet have a good solution. And HTML in CSS string is not it. What you can try is to work around this by using multiple page-margin boxes, eg. combine @bottom-left, @bottom-center and @bottom-right, and tweaking widths and margins.

@aausch
Copy link
Author

aausch commented Sep 12, 2013

Right. It would be unusual behaviour to have the content string interpreted as html.

I'm looking at some fairly complex footers, and just the three bottom page-margin boxes aren't enough to handle all of the formatting.

Is there any direction you'd suggest for implementing this? If it's not too much work, I can take a crack at implementing it

@SimonSapin
Copy link
Member

It’s not about doing the implementation work, it’s about coming up with a good design for a new CSS feature. These discussions happen on the www-style@w3.org mailing list, but to be honest the Working Group is not actively working on Paged Media at the moment :/

@liZe
Copy link
Member

liZe commented Dec 30, 2013

Workarounds available in #92. I close this "bug" as we can consider it as a duplicate of #92.

@liZe liZe closed this as completed Dec 30, 2013
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

3 participants