| 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 |
I need to know if there are any file naming conventions for the
bookreader with regard to international products. I am currently
suggesting that we in ALL-IN-1 land do the following:
LIBRARY.DECW$BOOKSHELF
A1Llangnnn.DECW$BOOKSHELF
A1Llangnnn.DECW$BOOKSHELF
A1nnn_AG.DECW$BOOK
A1nnn_DIFFS.DECW$BOOK
A1nnn_MG.DECW$BOOK
A1nnn_MMG.DECW$BOOK
A1nnn_MPT.DECW$BOOK
A1nnn_API_GS.DECW$BOOK
A1nnn_API_GUIDE.DECW$BOOK
A1nnn_API_MINI_REF.DECW$BOOK
A1nnn_API_REF_V1.DECW$BOOK
A1nnn_API_REF_V2.DECW$BOOK
A1nnn_API_UI.DECW$BOOK
A1Llangnnn_QL.DECW$BOOK
A1Llangnnn_UR.DECW$BOOK
A1 is the ALL-IN-1 product identifier
nnn is the version number
lang is the name of the language version of the product
The file names of the bookshelves and books include the product
identifier and version number, as well as the book title. Also, those
that are translated will include the name of the language in the file
name.
Each Bookreader CD is Market-specific, and contains a bookshelf for all
the language versions supported by that market. (This is the strategy we
are adopting for the ALL-IN-1 V2.4 kit CDROM.)
Has anybody else had to consider this, and if so, what solution did
you implement.
regards,
Phil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 253.1 | Why underscores? | MARVIN::KNOWLES | Running old protocol | Mon Jan 15 1990 04:56 | 29 |
Why not hyphens?
I've said this elsewhere, so if you're bored tune out now:
1 Hyphens are easier to type.
2 Hyphens make for quicker editing of recalled command lines:
a hyphen stops a <delete word> (F13) command; an underscore doesn't.
3 In real English, a hyphen links ideas; an underscore doesn't.
4 On a line printer, a hyphen in a filename disappears; an under-
score doesn't.
It also strikes me that underscores are ugly and hard on the
eyes, especially on a VDT, but that's a personal preference.
I realize that there is an enormous weight of precedent in
favour of underscores, and that developers learn to use (or
adopt the habit of using) underscores to link ideas in filenames
from an early age. But shouldn't we think more about the convenience
of our users than about the convenience of Digital employees?
I'm not impressed by the `weight of precedent' argument. "No gain
without pain."
(In other respects I think your proposal in .0 is fine.)
Bob
| |||||
| 253.2 | Yes. I Must hy-phen-ate. | IOSG::GEE | What can be, will be | Mon Jan 15 1990 05:23 | 7 |
Bob,
Thanks for your reply. You're correct about the hyphens. I must get
into the habit of using them in file names.
Phil
| |||||
| 253.3 | File Naming | LEZAH::CICALESE | Mon Jan 15 1990 15:49 | 19 | |
Hi Phil,
Re: note 253.0, file naming
Generally, you are right, a file naming convention is needed. It
is more difficult that what appears at the surface because of
DEC standards, part numbering, file naming, hard copy and online
differences.
CUP, SQM, and SW MAN have been working on a file naming convention
for the last two months. It is completed and has been approved by all
groups associated with this process. The policy should be announced no
later than this month. Please stay tuned.
Regards,
Michele' Cicalese
CUP OLD Program Manager
| |||||