| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 835.1 | Not really either | WRONGO::PARMENTER | What decade was this? | Thu Aug 20 1987 18:45 | 10 |
| This happened because we changed the input extension from GNC to
SDML. This only affects internal customers, naturally, since there
were never any external customers who had GNC files. It seemed
unfair to make everyone instantly rename all of their files from
GNC to SDML, so we decided to support both formats for the first
release. Please use SDML for all new files, because GNC will probably
not work in 1.2.
David
|
| 835.2 | | MARTY::FRIEDMAN | | Fri Aug 21 1987 10:13 | 5 |
| Many people have tripped over this because they were not aware of
DOCUMENT's subtle behavior. It seems more natural to assume that
the .SDML file would be used first.
Marty
|
| 835.3 | What about /SYMBOLS files? | CHGV04::ORZECH | Alvin Orzechowski @RDC | Fri Aug 21 1987 13:00 | 11 |
| >>> This happened because we changed the input extension from GNC to
>>> SDML. This only affects internal customers, naturally, since there
>>> were never any external customers who had GNC files. It seemed
>>> unfair to make everyone instantly rename all of their files from
>>> GNC to SDML, so we decided to support both formats for the first
>>> release. Please use SDML for all new files, because GNC will probably
>>> not work in 1.2.
Okay, but it seems to me that I had to specify the .SDML filetype when
using the /SYMBOLS= qualifier, but I didn't have to specify a filetype
if my symbols file had a .GNC type.
|
| 835.4 | rename your files and the problem goes away... | VAXUUM::PELTZ | �lvynstar Dun�dain | Mon Aug 24 1987 17:17 | 14 |
|
You have to supply the extension .SDML ONLY when there
are files name xxxx.GNC AND xxxx.SDML in the same directory.
This "feature" works the way it does so that any RMS error
messages will come out only with the .SDML file extention.
The results you all have been getting are due to you not
renaming ALL your .GNC files to .SDML files. This task of
renaming must be complete before the next version is
released, since .GNC will not be supported as a default
starting at that time.
Chris
|
| 835.5 | Still in V1.0 ... | UNTADA::CAAHANS | Hans Bachner, ADG Munich | Wed Sep 09 1987 04:57 | 4 |
| Unfortunately, this behaviour continues in the SDC version ...
I processed and printed a outdated version of a document yesterday
Hans. :-(
|
| 835.6 | two more cents on the pile | GNUVAX::SJONES | | Wed Sep 09 1987 17:34 | 17 |
| DOCUMENT's preference for the .GNC file over the .SDML file has tripped
up several writers using DOC$CONVERT here. If you take the following
steps (the natural progression), DOCUMENT processes the BL06
file rather than the Version 1 file:
$ DOC$CONVERT foo (leaves a BL06 FOO.GNC file
and a V1.0 FOO.SDML file
in the current directory)
$ DOCUMENT foo doctype destination (processes the BL06 file
and ruins your mood)
Previous versions of DOC$CONVERT used ".GNC_6" to identify a BL06 file.
If this were still the case, the above DOCUMENT command would ignore the
BL06 file (FOO.GNC_6) and process the V1.0 file (FOO.SDML) instead.
Could future versions (if any) of DOC$CONVERT give us back the .GNC_6
file extension?
|
| 835.7 | A Simple Solution | RDCV01::FSL | Rob Aldridge, FSL/BACIS | Thu Sep 10 1987 10:01 | 18 |
|
C'mon now...all this discussion about a simple little mistake.
People, I don't think the DOCUMENT group really has time to correct
this little "problem." Actually this "problem" was a "feature"
that saved you the headache of typing ".GNC" if you still had
unconverted documents lying around.
May I suggest the following?
$ DOC$CONVERT filename
$ RENAME *.GNC *.GNC_6
It's really not that difficult...
-Rob-
|
| 835.8 | It been reported before ... | CLOSET::DEVRIES | M.D. -- your Device Doctor | Thu Sep 10 1987 15:28 | 2 |
| The next version won't know about .GNC anyway. So the problem goes
away.
|