Related to issue #577, I would really like tectonic to give me the option to make warnings fatal.

The title says it all, I think. They used to be aligned in previous versions.

Custom citations do not format according to provided cls as they do with typical rmarkdown/ bookdown documents. Not sure if this is an issue with pagedown but further investigation is needed.

In deciding whether to use this library, it would be extremely helpful to see an example page using it that we can test on multiple screen sizes to experience the value added first hand

I followed the advice in https://pagedown.rbind.io/#the-css-overriding-mechanism but my font would not change. Having played around a bit with the settings and the CSS I realised that I needed to add

/* font location goes here:*/
@import 'https://fonts.googleapis.com/css?family=Comic+Neue';

Before the body to made the font available.

The whole of the CSS for custom font now

The first flowable on a page receives descender=0 on rendering. This causes a difference in the rendering of the two admonitions below:

.. Hint:: It's bigger than a bread box.

.. Hint:: It's bigger than a bread box.

When rendering a top border, the cursor should probably be moved by - descender and the descender passed to the content should equal 0.

Something similar ne

Currently Vivliostyle.js can load unzipped EPUB. Should also support normal (non-unzipped) EPUB.

Description

I feel like
these four lines
are out of order.
Should be in this order simeq, sime, nsimeq, nsime
or in this order sime, simeq, nsime, nsimeq.

I set up the A4 page, but if my page contains a wider picture, it will result in infinite paging

Unfortunately for TightenText, Safari rounds font sizes to whole pixels as soon as it crosses the half-pixel boundary. This leads to a significant jump in how wide the text is, and also potentially means the resulting text is smaller than the developer's desired minFontSize (if, say, they want it to be 0.97 ems, and that results in a font size of 15.49px, Safari will render 15px text).

Some

I was made aware of the fact that we don't have any example image for banding. This needs to be changed.

Also many other artifacts mentioned in https://guide.encode.moe/encoding/video-artifacts.html.

Maybe something to clarify in the doc: what is the advantage of caou over using pandoc directly?

Ie, what is the difference between:

pandoc doc.md -o doc.pdf

and

caou doc.md

Unicode has lots of built-in "fonts", like the mathematical alphanumeric characters [1, 2]. Include support for the numbers, Latin letters, and Greek letters. This should have a nice, user-friendly interface.

There are some other things like circled, full-width, and parenthesized l

By default just reversing the bleed value should work, but the cover renderings could include a safe zone box when in DRAFT mode as part of the design check process.

Be able to convert small images (like 150x150) to pixels could be used to reduce a lot of effort in manually producing shapes, boosting productivity. There are a lot of libraries in Python that could help in this task, like Pillow.