Document the issues properly.

common.conf

@@ -75,7 +75,7 @@
     <include prefix="xdg">fontconfig/common/varela-round.conf</include>
 
     <!-- Baskerville, Baskerville Old Face, Baskerville PT.
-         Used on: https://www.the-scientist.com, https://puri.sm. -->
+         Used on: https://theconversation.com, https://www.the-scientist.com.-->
     <include prefix="xdg">fontconfig/common/libre-baskerville.conf</include>
 
     <!-- Brush Script MT -->

common/varela-round.conf

@@ -18,7 +18,7 @@
     </alias>
 
     <!-- Font substitution rules -->
-    <!-- embolden doesn't doesn't work in Chrome and Firefox. FIXME -->
+    <!-- Chrome and Firefox ignore embolden assignment. FIXME#4 -->
     <match target="pattern">
         <test qual="any" name="family">
             <string>Arial Rounded MT Bold</string>

fonts.conf

@@ -64,11 +64,9 @@
         <!-- Rules for low DPI screens only -->
 
     <!-- Settings and aliases for low DPI screens, covering "web safe" fonts.
-         Using <accept> for aliases doesn't work for Chromium. FIXME
-         Firefox doesn't load local fonts for some sites, e.g. on
-         https://e.foundation (both Century Gothic and Font Awesome). FIXME
-         WebKitGTK uses the default Sans alias for missing fonts. FIXME
-         WebKitGTK uses the same sizes for serif / sans / monospace. FIXME -->
+         Using <accept> for aliases doesn't work with Chrome. FIXME#1
+         Firefox doesn't load local fonts for some sites. FIXME#2
+         WebKitGTK only matches first option in a font stack. FIXME#3 -->
     <include prefix="xdg">fontconfig/lowdpi.conf</include>
     <!-- Disables antialiasing for fonts perfectly hinted at specific sizes. -->
     <include prefix="xdg">fontconfig/pixelperfect.conf</include>

lowdpi.conf

@@ -16,7 +16,7 @@
     <!-- Some fonts embed bitmaps for certain sizes. They are desirable on loDPI
          screens, but enabling them here can break fonts, e.g. Anonymous Pro.
          One solution is to set this as 'false', then disable AA for those sizes
-         in pixelperfect.conf, but Firefox/Chrome break Wine's Tahoma. FIXME -->
+         in pixelperfect.conf, but Firefox/Chrome break Wine's Tahoma. -->
     <match target="font" >
         <edit name="embeddedbitmap" mode="assign">
             <bool>true</bool>
@@ -55,13 +55,14 @@
         <family>monospace</family>
         <prefer>
             <!-- Liberation Mono's metrics match Courier / Courier New, and it
-                 also has italics, but its default line spacing is bad. FIXME-->
+                 also has italics, but its default line spacing is bad. -->
             <family>PT Mono</family>
             <family>Liberation Mono</family>
             <family>Ubuntu Mono</family>
         </prefer>
     </alias>
-    <!-- Cursive & Fantasy aliases only work consistenly on Firefox. FIXME -->
+    <!-- Chrome picks Cursive and Fantasy aliases by itself. FIXME#5 
+         Cursive and Fantasy aliases are ignored by WebKitGTK. FIXME#6 -->
     <alias binding="strong">
         <family>cursive</family>
         <prefer>

pixelperfect.conf

@@ -12,10 +12,7 @@
          But that can break fonts in subtle ways, e.g. for Anonymouse Pro. -->
 
     <!-- When there's no italic or bold font for a specified typeface, this
-         disables antialiasing for auto-generated italics and bolds. FIXME -->
-
-    <!-- Firefox uses smaller default sizes for the monospace aliases.
-         Somehow, this breaks the compare conditions for pixel sizes. FIXME -->
+         disables antialiasing for auto-generated italics and bolds. FIXME#7 -->
 
 
     <!-- Alegreya from Huerta Tipografica. The well-hinted version only. -->