[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | Online Bookbuilding |
| Notice: | This conference is write-locked: see note 1.3. |
| Moderator: | VAXUUM::UTT |
|
| Created: | Fri Aug 12 1988 |
| Last Modified: | Mon Jul 15 1991 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 440 |
| Total number of notes: | 2134 |
38.0. ""pgid" errors and glossaries" by MTWAIN::WARD (Pizzaholic) Wed Dec 07 1988 16:27
A problem I'd been having for a while with the latest version of the doctype
has been solved. Here is the error that had appeared in the log file, which
is believed to have caused the failure to generate proper book and bookshelf
files:
VOILA ERROR--The following symbols are undefined:
pgid = 185, offset = 24704, symbol = '_DECW_GLOSS_245'
pgid = 185, offset = 23851, symbol = '_DECW_GLOSS_236'
pgid = 185, offset = 23133, symbol = '_DECW_GLOSS_229'
pgid = 185, offset = 21909, symbol = '_DECW_GLOSS_217'
etc.
The problem was traced to glossaries used in our books. I noticed that the
highest number was 245, and there were 252 glossary definitions. Sure enough,
each line of error corresponded to a definition that had one of three problems.
The most common problem was a missing definition. The definition consisted
solely of:
<GDEF>()
The other problems were due to either an imbedded <reference> tag (used to pull
in the proper name of the product, or an open parenthesis which was on the line
*following* the <GDEF> tag.
Since there was an exact correlation between the "pgid" numbers and the terms
whose definitions had one of these problems, I hope this'll solve this problem
and allow getting on with the build. By the way, I put a "X" down for those
definitions that had none, just to make it happy.
Randy
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 38.1 | what baselevel? | CLOSET::FITZELL | put nifty saying here | Fri Dec 09 1988 11:19 | 5 |
| If you're running the NOV 11 baselevel of the bookbuilding tools
can you send me the file. With that release and that error the
bookbuild should have aborted with no book or bookshelf files created.
MiKE
|
| 38.2 | | VAXUUM::UTT | | Wed Dec 14 1988 14:20 | 12 |
| Yes, the glossary definition tags are rather sensitive because symbol
names are defined behind-the-scenes to create the hotspots and popups
(the symbol names are what the converter is complaining about when
things are miscoded).
I did not realize that the <reference> tag was a problem. That
fix will be available in the next baselevel of the bookbuilding
tools.
Thanks,
Mary
|