Print

Print


I do the same things as Jessica - separate line, put in middle of sentence,
etc.  It is a difficult thing to wrestle with sometimes.  Some of our
emails don't use bold, italics, other fonts, or colors, so the prior 2
things are often necessary.  Lynn



At 10:25 AM 7/24/01 -0400, you wrote:
>On Tue, 24 Jul 2001, Geoffrey Duke wrote:
>
>...
>
>> PS. Is there any consensus about the disambiguation of code and correct
>> punctuation? My last line should have been '12hjbjla.doc.' The punctuation
>> goes inside the quotation marks. But that could lead to misreading. Any
>> thoughts?
>
>No easy answer there.  I tend to avoid putting periods after URLs or
>filenames.  Sometimes I rearrange the entire sentence, just to make sure
>that the quoted area doesn't appear at the end of a sentence.  To make
>literal text stand out, I often offset the text on its own line - such as:
>
>        12hjbjla.doc
>
>so that punctuation is not relevant and I don't need to use quotes or
>brackets.  I do that a lot with URLS, such as:
>
>        http:/www.uvm.edu
>
>I sometimes omit the period at the end of a sentence like that.. just
>because it would look silly.  If putting text on its own line isn't
>practical, you could use bold or italics, or put it in a non-proportional
>font like courier to make the text stand out.  I don't think there is one
>clear convention on this, though.  It's hard to read a document I've
>created from the perspective of a non-geek.  Sometimes I'm better off
>getting a co-worker who has less experience reading computer documentation
>to test it for readability.  I'm sometimes surprised at the answers.
>
>                                                        - Jessica
>