🚀 go-pugleaf

jrbd@craycos.com (James Davies) writes:

>In article <1992Oct13.063649.2027@RedBrick.COM> jfr@RedBrick.COM writes:
>>In article <1992Oct12.182241.11112@magnus.acs.ohio-state.edu> jgeniec@magnus.acs.ohio-state.edu (Joseph A Geniec) writes:
>>>     I am a new shareware developer, and I intend to upload my
>>>software to BBS's. What is the best way I can go about
>>>copyrighting shareware?
>>>
>>>                                             J.G.
>>
>>  Simple inclusion of a copyright notice:
>>
>>        Copyright (c) MeMyself AndI, 1992
>>        All rights reserved
>>
>>  is totally sufficient to secure copyright *protection*.

>I have a tangential question here;  what is the current status of
>c-in-parentheses as a substitute for c-in-a-circle as a copyright symbol?
>It's widely used, but does it have any effect on the validity of the
>copyright notice (for good or bad)?

Will not address use of (c) directly except to say it is not accepted
yet by C/R office.

However, since we (the U.S.) joined the Berne convention (March 1, 1989),