Instead of embedding normalize gutenberg should probably say it's required in the documentation then users could use a newer version of normalize

As you see in the image, the background color is broken after True keyword appears.
How do I get around this problem?

You start printing classes like:

instance(MyClass): "<docstring>"
    "or maybe docstring here <docstring> "
   < your usual >

• PrettyPrinter version: 0.18.0
• Python version: 3.7
• Operating System: Fedora Linux

Description

Prettyprinting an IPython.core.magics.execution.TimeitResult crashes prettyprinter. That class is defined at https://github.com/ipython/ipython/blob/master/IPython/core/magics/execution.py.

What I Did

In IPython 7.8.0 with prettyprinter enabled:

In [1]: x = %timeit -o p

Screenshot of generated PDF:

Gitbook warning for all 3 file types (PDF, epub and mobi): warn: no summary file in this book.

Related issue might be: GitbookIO/gitbook-cli#74 (which came up after I tried

I see the documentation says "For iOS its possible to send the content directly to the printer without any dialog" so I take that to mean you can send print jobs programmatically without user input. Can this be done on Android or Windows?

We should explicitly strip out any vertical gravity and weights from the LinearLayout.LayoutParams that we get.

Should also see if the horizontal gravity is actually working.

In my day-to-day work, I write several different types of documents that could have different renders.

It could be interesting to be able to manage several export profiles, to be selected on PDF generation, each with a specific:

• CSS file
• Header
• Footer

What do you think?

(By the way, thanks for the great job already done!)

It would be really cool if it was possible to manually set the date format for document titles.
Currently the are two: DateTime and DateTime.yyyyMMddHHmmss.
Ideally something like the date format of google spreadsheets, where one can build the format they want by adding components.