diff --git a/_layouts/main.html b/_layouts/main.html index e0b48ef28..0c84ad835 100644 --- a/_layouts/main.html +++ b/_layouts/main.html @@ -2,8 +2,8 @@ - beets: {% if page.shorttitle %}{{ page.shorttitle }} - {% else %}{{ page.title }}{% endif %} + beets: {% if page.shorttitle %}{{ page.shorttitle | xml_escape }} + {% else %}{{ page.title | xml_escape }}{% endif %} @@ -58,9 +58,9 @@ diff --git a/_posts/2016-06-19-sqlite-performance.md b/_posts/2016-06-19-sqlite-performance.md index 09293b05e..e89dc6c82 100644 --- a/_posts/2016-06-19-sqlite-performance.md +++ b/_posts/2016-06-19-sqlite-performance.md @@ -1,5 +1,5 @@ --- -title: "we're pretty happy with SQLite & not urgently interested in a fancier DBMS" +title: "we’re pretty happy with SQLite & not urgently interested in a fancier DBMS" --- Every once in a while, someone suggests that beets should use a "real database." I think this means storing music metadata in [PostgreSQL][] or [MySQL][] as an alternative to our current [SQLite][] database. The idea is that a more complicated DBMS should be faster, especially for huge music libraries. diff --git a/blog/atom.xml b/blog/atom.xml index bf376858e..1aff039bf 100644 --- a/blog/atom.xml +++ b/blog/atom.xml @@ -3,7 +3,7 @@ layout: null --- - + The beets blog. @@ -16,12 +16,12 @@ layout: null {% for post in site.posts %} - {{ post.title }} + {{ post.title | xml_escape }} {{ post.date | date_to_xmlschema }} {{site.url }}{{ post.id }} {{ post.content | xml_escape }} {% endfor %} - +