| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I accidentally removed syntax highlighting in 94f82685672bcd4e5731de3c1c61e79f7edc07b2.
|
| |
|
|
|
|
| |
Use web font to draw icons.
|
|
|
|
|
| |
Open Sans Light 300 turns out to be too thin when antialiased (e.g., in
mobile Safari.)
|
|
|
|
|
| |
Using web font Open Sans (light) instead of Helvetica Neue. Text is
thinner, but close enough and feels about right.
|
|
|
|
| |
Make page source a little bit more readable.
|
|
|
|
| |
I forgot to update print.css to match the updated DOM last time.
|
| |
|
| |
|
| |
|
|
|
|
| |
To distinguish long captions from article paragraphs.
|
| |
|
| |
|
|
|
|
| |
That will lead to Dropbox constantly syncing the file under preview mode.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The main aim is a more logical DOM structure and more performant CSS.
|
|
|
|
| |
Also adjusted some margins.
|
|
|
|
|
|
|
|
|
| |
New:
* Greater than 1440px: load theme-wide.css, content width: 50%;
* Between 1024 and 1440px: standard theme.css, content width: 60%;
* Lower than 1024px: load theme-narrow.css, content width: 90% (and
floating nav element moves up to page top to make space).
|
|
|
|
| |
Again using -webkit-image-set.
|
| |
|
|
|
|
| |
200x200 icon wastes too much valuable screen estate on a smart phone.
|
|
|
|
| |
icon.tex was modified in bbaf880.
|
| |
|
|
|
|
|
| |
This way we can deliver the right size based on the window size (wide or
narrow), rather than deliver a universal one then scale down.
|
| |
|
|
|
|
|
| |
400x400 is a waste, given that the size of the logo set by CSS is either
100x100 (wide) or 200x200 (narrow).
|
|
|
|
|
|
| |
Round icon with transparent filling doesn't work well on iOS's home
screen, because the transparent part will be filled in black. Also, the
letters ZW have been enlarged to look better in a square icon.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add class and variation selector (# U+FE0E: VARIATION SELECTOR-15) to
U+21A9: LEFTWARDS ARROW WITH HOOK to fix outstanding font issue of
footnote backlinks on mobile.
Updated styles accordingly.
Trick learned from Daring Fireball.
Before: https://i.imgur.com/eUbL1k8.png
After: https://i.imgur.com/msv3INn.png
|
|
|
|
| |
Yay.
|
|
|
|
|
|
|
|
|
|
| |
Viewport configuration per Google's mobile usability suggestions. It not
only provides a consistent experience by using device independent
pixels, but also help me get rid of theme-enlarge.css, which could
result in unexpectedly large font when one accidently resize to a
portrait window on the desktop. Thanks Google!
See https://developers.google.com/speed/docs/insights/ConfigureViewport.
|
| |
|
|
|
|
|
|
|
|
| |
Previously there's only one postprocessing function `number_code_lines`,
which directly reads an HTML file, and after processing, writes
back. Now the reading and writing is handled by a dedicated dispatcher
`postprocess_html_file`, which can call multiple postprocessors that
operates on a soup object.
|
| |
|
|
|
|
| |
\pi is eaten by Pandoc.
|
|
|
|
|
| |
Add a `>` between paragraphs so that a multi-paragraph block quote is
inside one <blockquote> tag. Otherwise the left bar would be broken.
|
|
|
|
| |
The bar is the same as that for pre. Horizontal padding reduced to 1em.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Global font size in each style sheet has been tweaked very carefully so
that the precise line height is very close to a whole number of pixels,
so that precision alignment using em, which aligns something
precise (top: 13.5em) to something inprecise (line heights, with
accumulated errors due to rounding in every line), is not lost.
Note that Firefox is NOT supported, since each line seems to always
occupy one more pixel than the calculated line height.
For some reason line numbers in the print view are still rather
problematic at a page continuation. In Chrome and Safari, the first two
line numbers on a new page tend to overlap, so everything afterwards are
off (and on Firefox line numbers do not show up on the second page at
all). Anyway, printing shouldn't be a big concern.
|