Properly fix #1148 by always parsing optional tables in TrueTypeFontParser and remove Type 0 font hack

Author: BobLd

src/UglyToad.PdfPig.Fonts/TrueType/Parser/TrueTypeFontParser.cs

@@ -121,10 +121,10 @@ private static TrueTypeFont ParseTables(float version, IReadOnlyDictionary<strin
 
                 // glyf
                 builder.GlyphDataTable = GlyphDataTable.Load(data, glyphHeaderTable, builder);
-
-                OptionallyParseTables(tables, data, builder);
             }
 
+            OptionallyParseTables(tables, data, builder);
+
             return new TrueTypeFont(version, tables, builder.Build());
         }
 

src/UglyToad.PdfPig/PdfFonts/Composite/Type0Font.cs

@@ -131,18 +131,7 @@ public CharacterBoundingBox GetBoundingBox(int characterCode)
 
             var width = CidFont.GetWidthFromFont(characterIdentifier);
 
-            double scale = fontMatrix.A;
-            if (Math.Abs(scale - 0.001) < 0.0001)
-            {
-                // BobLD: The value of scale is close enough to 0.001 to be able to use 0.001.
-                // Still not sure what is the correct logic, but this hack fixes issue #1148 (while not breaking "Old Gutnish Internet Explorer.pdf")
-                // 
-                // Based on https://martin.hoppenheit.info/blog/2018/pdfa-validation-and-inconsistent-glyph-width-information/
-                // which quotes: section 6.2.11.5 of ISO 19005-2:2011 (PDF/A-2) clarifies this issue: “For ISO 19005, consistent is defined to be a difference of no more than 1/1000 unit.”
-                scale = 0.001;
-            }
-
-            var advanceWidth = scale * width;
+            var advanceWidth = fontMatrix.TransformX(width);
 
             var result = new CharacterBoundingBox(boundingBox, advanceWidth);