Formatting.

Cleaning up of ChangeLog.

* docs/license.txt: s/X Windows/X Window System/.

* src/raster/ftraster.c: Fix definition condition of MEM_Set().
* src/smooth/ftgrays.c (M_Y): Change value to 192.
* src/base/ftdbgmem.c (ft_mem_table_destroy): Fix printf() parameter.
Remove unused variable.
* src/cache/ftcimage.c (ftc_image_node_init,
ftc_image_node_compare): Remove unused variables.
* src/cache/ftcsbits.c (ftc_sbit_node_weight): Remove unused
variable.
* src/raster/ftraster.c (MEM_Set): Move definition down to avoid
compiler warning.
* src/autohint/ahhint.c (ah_hinter_hint_edges): Use UNUSED() to
avoid compiler warnings.
* src/pcf/pcfread.c (tableNames): Use `const'.
(pcf_read_TOC): Change counter name to avoid compiler warning.
Use `const'.
* src/pshinter/pshrec.c (ps_hints_close): Remove redundant
declaration.
* src/pshinter/pshalgo1.c (psh1_hint_table_init): Rename variables
to avoid shadowing.
* src/pshinter/pshalgo2.c (psh2_hint_table_activate_mask): Ditto.
* src/type1/t1objs.h: Remove double declarations of `T1_Size_Init()'
and `T1_Size_Done()'.

1 files changed, 36 insertions, 45 deletions

diff --git a/docs/BUGS b/docs/BUGS
index ba051706a..6d87e0ffb 100644
--- a/docs/BUGS
+++ b/docs/BUGS
@@ -12,7 +12,7 @@ we can use abbreviations here, like:
 
   "David" for David Turner
   "Werner" for Werner Lemberg
-   etc.
+  etc.
 
 "Reproduceable" indicates whether the bug could be reproduced by the
 development team or not (it can be specific to a given platform), whether it
@@ -108,7 +108,6 @@ BAD-TT-RENDERING
   bytecode-hinted glyphs!  Something seems to be really broken here!
 
 
-
 BAD-THIN-LINES
 
   It seems that the anti-aliased renderer in FreeType has problems rendering
@@ -116,7 +115,6 @@ BAD-THIN-LINES
   FT_Outline_Render() function.
 
 
-
 NOT-WINDOWS-METRICS
 
   FreeType doesn't always return the same metrics as Windows for ascender,
@@ -128,68 +126,61 @@ NOT-WINDOWS-METRICS
 BAD-T1-CHARMAP
 
   Type1 driver doesn't read "cacute" and "lslash" characters from iso8859-2
-  charset. Those characters are mapped as MAC-one in glnames.py, so they
+  charset.  Those characters are mapped as MAC-one in glnames.py, so they
   cannot be shown in Adobe Type1 fonts.
 
-  (this was due to a bug in the "glnames.py" script used to generate the
-   table of glyph names in 'src/psaux/pstables.h')
+  (This was due to a bug in the "glnames.py" script used to generate the
+  table of glyph names in 'src/psaux/pstables.h'.)
 
 
 BAD-UNIXXX-NAMES
 
-  Glyph names like uniXXXX are not recognized as they should be. 
-  It seems that code in psmodule.c for uniXXXX glyph names was
-  never tested. The patch is very simple.
+  Glyph names like uniXXXX are not recognized as they should be.  It seems
+  that code in psmodule.c for uniXXXX glyph names was never tested.  The
+  patch is very simple.
   
-  (a simple bug that was left un-noticed due to the fact that I don't have
-   any Postscript font that use this convention, unfortunately..)
+  (A simple bug that was left un-noticed due to the fact that I don't have
+  any Postscript font that use this convention, unfortunately.)
 
 
 ADVANCED-COMPOSITES
 
   Provided by George Williams <pfaedit@users.sourceforge.net>:
 
-    I notice that truetype/ttgload.c only supports Apple's 
-    definition of offsets for composit glyphs. Apple and 
-    Microsoft behave differently if there is a scale 
-    factor. OpenType defines some bits to disambiguate. 
+    I notice that truetype/ttgload.c only supports Apple's definition of
+    offsets for composite glyphs.  Apple and Microsoft behave differently if
+    there is a scale factor.  OpenType defines some bits to disambiguate.
     
-    (a problem in both 2.0.4 and 2.0.5) 
+    (A problem in both 2.0.4 and 2.0.5.)
     
-    Apple says 
-    (http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html) 
-    that if flags&ARGS_ARE_XY is set then the offsets 
-    should be scaled by the scale factors (as you have 
-    done), but they also say something very cryptic about 
-    what happens when the component is rotated at 45° 
-    (which you do not support)-- See the "Important" note 
-    at the bottom. 
+    Apple says (http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html) that if
+    flags&ARGS_ARE_XY is set then the offsets should be scaled by the scale
+    factors (as you have done), but they also say something very cryptic
+    about what happens when the component is rotated at 45° (which you do
+    not support) -- See the "Important" note at the bottom.
     
-    The old truetype spec from Microsoft did not mention 
-    this. The OpenType spec 
-    (http://www.microsoft.com/typography/otspec/glyf.htm, 
-    http://partners.adobe.com/asn/developer/opentype/glyf.html)
-    efines two new bits to disambiguate: 
-    SCALED_COMPONENT_OFFSET 11 
-    Composite designed to have the component offset scaled 
-    (designed for Apple rasterizer) 
-    UNSCALED_COMPONENT_OFFSET 12 
-    Composite designed not to have the component offset 
-    scaled (designed for the Microsoft TrueType rasterizer) 
+    The old truetype spec from Microsoft did not mention this.  The OpenType
+    spec (http://www.microsoft.com/typography/otspec/glyf.htm,
+    http://partners.adobe.com/asn/developer/opentype/glyf.html) defines two
+    new bits to disambiguate:
+
+      SCALED_COMPONENT_OFFSET 11 
+      Composite designed to have the component offset scaled (designed for
+      Apple rasterizer)
+
+      UNSCALED_COMPONENT_OFFSET 12 
+      Composite designed not to have the component offset scaled (designed
+      for the Microsoft TrueType rasterizer)
     
-    Perhaps you could add a load_flag to allow the user to 
-    define the default setting?
+    Perhaps you could add a load_flag to allow the user to define the
+    default setting?
 
   David says:
   
-    Wow, I was not even aware of this, it will probably take a little
-    time to implement since I don't have any font that implement these
-    "features", and also because I believe that we're running out of
-    bits for "load_flag", some other way to set preferences is probably
-    needed..
+    Wow, I was not even aware of this, it will probably take a little time
+    to implement since I don't have any font that implement these
+    "features", and also because I believe that we're running out of bits
+    for "load_flag", some other way to set preferences is probably needed.
 
 
- 
-  
-
 === end of file ===