| Number | 163
|
| Category | errata
|
| Synopsis | document formatting problems
|
| State | lrmdraft
|
| Class | errata-discuss
|
| Arrival-Date | Oct 14 2002
|
| Originator | Shalom.Bresticker@motorola.com
|
| Release | 2001a,b: passim
|
| Environment |
|
| Description |
I have recorded the following formatting problems. a. The "--" at the beginning of items in an unordered list disappeared. Example: 3.5. Fixed in 2001b. b. code lines which are too long, but were ok in Draft 6. Example: in 4.4.3, the first line of the simulator output. This is still not fixed in 2001b. Need to check what caused this. Is it font size or page width or something else? c. In expressions like a[3:0], there is an extra space, so it looks like a[ 3:0]. Ugly. Not fixed in 2001b. Was ok in Draft 6, so need to check what caused it. d. Many code lines in PLI are cut off at left. E.g., in Figure 67 in 23.7. This is fixed in 2001b. e. In some places, at least in PLI, smart quotes are used instead of regular quotes. E.g., 27.10. This is in 2001b also. This is presumably in the FrameMaker source. f. Apostrophes disappeared. E.g., 17.2.3, last sentence. Also in IEEE's 2001b. This is an IEEE problem. g. Other special characters also disappeared. E.g., footnote characters in Syntax 12-7 in 12.4. Not fixed. |
| Fix |
A. "em dashes": dealt with separately in issue #169. B. line overruns: The editor will search thru the document for all such cases, submit a list, and deal with each of them one by one. C. Extra space after "[" in code font: Change all CourierNew fonts to Courier font, globally. D. PLI code cut off: Fixed already in 2001b. Any unfixed places should be reported to the editor. E. Smart quotes in code text: The editor will change them to straight up-down quotes. See issue #116. F. Disappearing apostrophes: like part A. Editor will search for apostrophes in TimesNewRoman font, and change them to Times font. (fixed by #169) G. Other disappearing sepcial characters: The special footnote characters in Syntax 12-7 were fixed by changing them to letters. "Em dashes" and apostrophes are dealt with separately. Other special characters which did not print should be brought to attention of the editor. (fixed by #169) |
| Audit-Trail |
From: Shalom Bresticker <Shalom.Bresticker@motorola.com> To: etf-bugs@boyd.com Cc: Subject: Re: errata/163: document formatting problems Date: Wed, 16 Oct 2002 07:43:27 +0200 >Category: errata >Confidential: no >Originator: Shalom Bresticker <Shalom.Bresticker@motorola.com> >Release: 2001b >Class: TBD >Description: This applies to single quotes, double quotes, apostrophes, and forward and back tics. > e. In some places, at least in PLI, smart quotes are used > instead of regular quotes. E.g., 27.10. This is in 2001b > also. This is presumably in the FrameMaker source. Analyzed by Shalom.Bresticker@motorola.com on Thu Jan 2 01:09:26 2003 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. From: Shalom.Bresticker@motorola.com To: etf-bugs@boyd.com Cc: Subject: Re: errata/163: PROPOSAL - document formatting problems Date: Sun, 27 Apr 2003 20:57:47 +0300 (IDT) > B. line overruns: > The editor will search thru the document for all such cases, > submit a list, and deal with each of them one by one. Here is the list, by page number in 2001b, and number of times on the page, if more than one: 32 53 61 x 2 140 143 181 x 3 242 243 245 x 2 246 247 249 x 2 258 x 2 285 315 x 2 316 317 x 2 318 322 x 2 349 354 357 x 2 411 455 457 x 2 462 x 2 478 491 507 509 525 548 720 821 A small error seem our fault, rather than a result of page narrowing. From: Shalom.Bresticker@motorola.com To: etf-bugs@boyd.com Cc: Subject: Re: errata/163: PROPOSAL - document formatting problems Date: Thu, 1 May 2003 12:03:43 +0300 (IDT) > > B. line overruns: > > The editor will search thru the document for all such cases, > > submit a list, and deal with each of them one by one. > > A small error seem our fault, rather than a result of page narrowing. I meant: A small number of them seem our fault, rather than a result of page narrowing. |
| Unformatted |
|
Hosted by Boyd Technology