-
Notifications
You must be signed in to change notification settings - Fork 259
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
write_html(): homogenization in handling of tag_styles + new optional arg font_family #1217
Conversation
@gmischler, @lcgeneralprojects: this PR is ready for review if you want to have a look at it 🙂 I'm wondering if I should try to get rid of |
db9a009
to
c167f59
Compare
c167f59
to
80d01d1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's some stuff in there that I don't understand. Which may be me not looking straight, or there may actually be problems... 😉
27dbd88
to
8b9d685
Compare
8b9d685
to
a3792ea
Compare
66fd0a0
to
2c37f77
Compare
2c37f77
to
1a76aa7
Compare
This is a follow-up of the clean-up started in PR #1211
Now the following HTML tags are all handled similarly, by the same code blocks in
HTML2FPDF
:<b>
,<blockquote>
,<center>
,<code>
,<em>
,<i>
,<dd>
,<dt>
,<pre>
,<strong>
,<u>
.This PR also introduces a new optional
font_family
parameter toFPDF.write_html()
, in order to be able to set the default font family.Checklist:
The GitHub pipeline is OK (green), meaning that both
pylint
(static code analyzer) andblack
(code formatter) are happy with the changes of this PR.A unit test is covering the code added / modified by this PR
This PR is ready to be merged
[NA] In case of a new feature, docstrings have been added, with also some documentation in the
docs/
folder[NA] A mention of the change is present in
CHANGELOG.md