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 |
The <LMF> tags used for V2 books are supposed to be on-ops for printed documentation. However, DOCUMENT fails to ignore them when you process for the MAIL destination to make TXT files for installation guides and release notes that go on CONDIST. You have to edit the TXT file and delete the LMF information. DOCUMENT should be fixed so that the <LMF> tags don't appear in TXT files.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
223.1 | CLOSET::UTT | Wed Nov 15 1989 19:40 | 4 | ||
Are you using the symbols file CUP$ONLINE_DEFS.GDX? What errors do you get, undefined tag errors? Mary | |||||
223.2 | Got tags in output, not errors | AITG::WARNER | It's only work if they make you do it | Thu Nov 16 1989 09:53 | 2 |
I didn't use the GDX file. I don't think I got any DOCUMENT errors, but the tags appeared in the TXT file output. | |||||
223.3 | RAGMOP::UTT | Thu Nov 16 1989 14:56 | 14 | ||
I just tested the MAIL destination with the LMF tags. If I did *not* use /symbols=cup$online_defs.gdx, the tags were reported as being undefined and were put into the output. If I *did* use \symbols=cup$online_defs.gdx, the tags were defined as null, there were no complaints from the tag translator, and there were no LMF tags in the output. Please recheck this. If you are still having problems, please send a log file and a small test file that reproduces the problems and I will look into it. Thanks, Mary | |||||
223.4 | GDX file solves problem | AITG::WARNER | It's only work if they make you do it | Mon Nov 20 1989 09:32 | 3 |
Using the GDX file solved the problem. Sorry for the bother. Ross |