Title: | DOCUMENT T1.0 |
Notice: | **New notesfile (DOCUMENT.NOTE) now available (see note 897)** |
Moderator: | CLOSET::ADLER |
Created: | Mon Feb 09 1987 |
Last Modified: | Thu Oct 31 1991 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 897 |
Total number of notes: | 4397 |
I was just tinkering with the MEMO doctype, which I haven't used much before, and noticed that a CC distribution list uses this syntax: <CCLIST> <CC>(Jim Bob) <CC>(John Boy) <CC>(Rose Girl) <ENDCCLIST> Seems to me that parens should not be required for each <CC>, just as they are not required for each <LE>. This is BL7 stuff, by the way. Rose
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
389.1 | consistency nit | BUNSUP::LITTLE | Todd Little NJCD SWS 323-4475 | Tue May 19 1987 01:25 | 13 |
Along the same lines, why isn't it: <LIST>(COPY) or <LIST>(CARBON_COPY) and <LE>Name1 <LE>Name2 <ENDLIST> At least for consistency sake. -tl | |||||
389.2 | CLOSET::ANKLAM | Tue May 19 1987 08:27 | 4 | ||
sigh, an oversight. | |||||
389.3 | Methinks you need a holiday, but how about this? | COOKIE::JOHNSTON | Tue May 19 1987 14:09 | 28 | |
Patti, m'dear, you sound *weary*. Such is the plight of heros and reluctant messiahs. Not to beat a dead horse, but assuming that you'll be looking at this in an upgrade, I'd like to offer two suggestions: 1. Use either <list>(carbon_copy) or <cclist>, but do ask a few secretaries what they think because they'll have a better handle on the user-friendliness of the tags than anyone (I think). 2. Continue to use the <cc> tag and allow it to accept 3 or 4 arguments so that you can get a multiple column distribution list; very long distribution lists waste a lot of space when they are one single column. name1 name2 name3 name4 name5 name6 name7 namenn Keeping the <cc> tag will distinguish this type of list element from the generic, single-column <le>. <cclist> is probably a better tag to keep with <cc> than <list>(carbon_copy) (my opinion only). Of course, the user must take responsibility for alphabetizing the list, unless that's a automatic capability you can provide. Rose |