errata/163: ANALYZED - document formatting problems

From: Shalom.Bresticker@motorola.com
Date: Thu Jan 02 2003 - 01:09:28 PST

  • Next message: Shalom.Bresticker@motorola.com: "errata/166: PROPOSAL - 2001b, 1.4: "Clause 2" missing clause title"

    Precedence: bulk

    A. "em dashes": See issue #169.

    B. line overruns: Reason is that text column width was
    narrowed. Need to find and make list of such places. I have
    reviewed most of the document and noted each such case I
    saw. I will finish reviewing the document and submit a list
    of the cases I found.

    C. "[ ": It appears that the reason is CourierNew font
    instead of Courier font. Similar to #169. Solution is to
    change all code to Courier font. Although this is a change
    that needs to be made on the entire document at once and
    not one by one, it appears to be a safe change, since code
    uses only basic character set.

    D. PLI code cut off: Already fixed unless someone finds an
    unfixed place.

    E. smart quotes: Probably need to search all smart quotes
    one by one and check one by one which ones to change to
    regular quotes. Looks manageable.

    F,G: special characters not printed: Again, like 169, reason
    appears to be use of TimesNewRoman font instead of Times.
    Need to consider converting all TimesNewRoman to Times.
    The reduced solution is to look for the apostrophes in
    TimesNewRoman one by one and solve each individually.
     

    http://boydtechinc.com/cgi-bin/issueproposal.pl?cmd=view&pr=163

    This archive was generated by hypermail 2.1.4 : Thu Jan 02 2003 - 01:10:05 PST and
    sponsored by Boyd Technology, Inc.