| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
Tested on iPhone 6 Plus (both portrait and landscape).
|
|
|
|
|
|
|
|
|
|
|
|
| |
For better formatting.
The following screenshots illustrate the difference:
* https://i.imgur.com/ZfkUpBG.png
* https://i.imgur.com/S6cRK00.png
I also reduced the indentation on the left of each year's index from 2em
to 1em.
|
|
|
|
|
|
|
|
| |
Regenerate a page if the generator mtime is later than the page's
mtime (just like for the template).
Previewer still should be relaunched after modification to the
generator, since the generator won't be patched until the next run.
|
|
|
|
| |
variables (without temp file)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Explicitly specify the lxml parser to suppress warnings;
* Supposedly fix the
AttributeError: 'NoneType' object has no attribute 'next_element'
issue [1] with BeautifulSoup when finding elements after extracting
certain tags. I bet I've encountered that error before, but it seemed
to went away somehow. Not this time. Without digging into to much
detail (don't have time to file a bug or anything), this fix --
precompile a list of tags to extract, and only extract after done with
other processing -- seem to work.
* Add .nojekyll to root of build
dir (https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/).
[1]: Full traceback:
---------------------------------------------------------------------------
AttributeError Traceback (most recent call last)
<ipython-input-7-9d3d20b34e0c> in <module>()
----> 1 a.footer
/Users/zmwang/.pyenv/versions/3.4.3/lib/python3.4/site-packages/beautifulsoup4-4.4.0-py3.4.egg/bs4/element.py in __getattr__(self, tag)
995 # We special case contents to avoid recursion.
996 elif not tag.startswith("__") and not tag=="contents":
--> 997 return self.find(tag)
998 raise AttributeError(
999 "'%s' object has no attribute '%s'" % (self.__class__, tag))
/Users/zmwang/.pyenv/versions/3.4.3/lib/python3.4/site-packages/beautifulsoup4-4.4.0-py3.4.egg/bs4/element.py in find(self, name, attrs, recursive, text, **kwargs)
1232 criteria."""
1233 r = None
-> 1234 l = self.find_all(name, attrs, recursive, text, 1, **kwargs)
1235 if l:
1236 r = l[0]
/Users/zmwang/.pyenv/versions/3.4.3/lib/python3.4/site-packages/beautifulsoup4-4.4.0-py3.4.egg/bs4/element.py in find_all(self, name, attrs, recursive, text, limit, **kwargs)
1253 if not recursive:
1254 generator = self.children
-> 1255 return self._find_all(name, attrs, text, limit, generator, **kwargs)
1256 findAll = find_all # BS3
1257 findChildren = find_all # BS2
/Users/zmwang/.pyenv/versions/3.4.3/lib/python3.4/site-packages/beautifulsoup4-4.4.0-py3.4.egg/bs4/element.py in _find_all(self, name, attrs, text, limit, generator, **kwargs)
527 while True:
528 try:
--> 529 i = next(generator)
530 except StopIteration:
531 break
/Users/zmwang/.pyenv/versions/3.4.3/lib/python3.4/site-packages/beautifulsoup4-4.4.0-py3.4.egg/bs4/element.py in descendants(self)
1271 while current is not stopNode:
1272 yield current
-> 1273 current = current.next_element
1274
1275 # CSS selector code
AttributeError: 'NoneType' object has no attribute 'next_element'
|
|
|
|
|
| |
The tidy5 executable has been renamed to tidy for the 5.0.0 release. See
https://github.com/htacg/tidy-html5/commit/1e70fc6f15190a0ee497232daeb506241c6f9eba.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also update previous post
2015-05-06-searchable-settings-are-one-honking-great-idea-lets-do-more-of-those.md.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I just noticed that code font is crazy without Consolas installed (I
recently reinstalled my OS and got rid of Office for Mac 2011 — that's
probably why). The line numbers are all off (since the line heights are
carefully pre-calculated, and fallback fonts of different leadings won't
help). Therefore, I'm moving to the quite nice looking and controllable
Droid Sans Mono. Isn't as satisfactory as Consolas on the web, but
certainly better than Monaco.
Note: I originally copied my list Consolas, Monaco, 'Andale Mono',
monospace (I added Courier since I like it a lot as the primitive
monospace font) from MDN Wiki, but now it looks like a bad choice when I
don't have Consolas any more. By the way, MDN Wiki renders line numbers
using JS, so at least they are able to calculate the line heights. I'm
serving everything statically, so this is a problem.
|
| |
|
|
|
|
| |
the shabby and boring old bookmark system from Stone Age strikes back.
|
|
|
|
|
| |
Also added a 2048x2048 logo for submission to Apple News Publisher (just
curious).
|
|
|
|
| |
Each lxml.etree._Element.text needs a new CDATA.
|
|
|
|
|
|
| |
Specifically lxml.etree instead of xml.etree.ElementTree.
This allows CDATA without hack.
|
| |
|
|
|
|
|
| |
Subtitle was added along with RSS, but I accidentally used <title>
instead of <subtitle> for the tag.
|
| |
|
| |
|
|
|
|
| |
Fixes #2.
|
|
|
|
|
| |
Use canonical format for BLOG_HOME, and use urllib.parse.join for safe
concatenation.
|
|
|
|
|
|
| |
For one thing, the top attribute is not recommended in feeds (see
https://github.com/zmwangx/zmwangx.github.io/issues/2). Also, extracting
line numbers (which are useless in feeds) make the feeds smaller.
|
|
|
|
| |
turns to ==> turns into (not sure why I was thinking).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And other minor changes.
|
| |
|