Development of jed

[G. Milde]

On 19.05.08, J�rg Sommer wrote:
> Hallo G.,

> G. Milde schrieb am Mon 19. May, 10:01 (+0200):
> > On 19.05.08, Jörg Sommer wrote:
> > > how do we want to continue with the maintenance of the jed package? I've
> > > created a new branch jo-0.99.19 as a suggestion of how we could continue.
> > > I've merged in the upstream source and the changes from the 0.99.18
> > > series. Than I've done some changes. Maybe someone can review and comment
> > > on them.
> > 
> > 
> > > What do you think about the etch branch? 
> > ...
> > > I would like to drop this branch. This doesn't mean the tags are lost.
> > > Only these last two commits. Objections?
> > 
> > None (if the changes done in this commits are preserved in the current
> > trunk).

> These changes never go to trunk and they get lost. I'm talking about
> these changes:

> commit 41c868823990467734e6a6167191ff8b779f7a86
> Author: Rafael Laboissiere <rafael at debian.org>
> Date:   Wed Mar 7 09:44:40 2007 +0000

>     Added XS-Vcs-Svn and XS-Vcs-Browser fields to the debian/control files of
>     all active packages

I.e. we do not need these fields? Are they obsoleted, non-standard or simply
not such important (or useless)?


>     Fixed spelling "gl.po" -> "ja.po"

I.e. the spelling "gl.po" will be used in all further versions of the
changelog?


> > > I'm using the xjed version from unstable everyday and I suspect John
> > > releases 0.99.19 soon. What do you think about cleaning up the 0.99.19
> > > branch and upload this package? 
> > 
> > The last time I tried xjed from the experimental package (0.99-19-117),
> > it was (for me) unusable as every mouse-action had very unexpected
> > results. Is this fixed now?

> No. If we upload this package to unstable I would drop the patch and
> reopen the bug for missing multikey support.

OK then.


> > > This is the list of my changes. The commit script might have failed.

> > >     Remove in files in info/

> > OTOH, I think the info files are not that important and appear to
> > be no longer maintainged as well, so dropping them is OK with me.

> I'm still against dropping them, because they contain informations they
> aren't part of the manpage. Okay, they contain the same informations as
> the jed.tex file. :)

The missing part in your original post was:

> We can and we do rebuild the info files from the jed.tex file.

OK, lets replace the upstream info files with generated ones.


> > >     Replace (C) by © and update copyright year
...
> > >     The string ‘(C)’ or ‘(c)’ is not a valid copyright sign. A lawer treat
> > >     only the sign © as a valid copyright sign. See
> > >     http://en.wikipedia.org/wiki/Copyright
> > 
> > The given URL says: 
...
> Sorry, I remembered the wrong article.

> I've picked this issue from
> http://lists.debian.org/debian-devel/2008/02/msg00889.html

The `reliable link <http://www.copyright.gov/circs/circ03.html>`_
in the posting says:

  The use of a copyright notice is no longer required under U.S. law,
  although it is often beneficial. 

  ...
  Form of Notice
  ==============
  ...
  Visually Perceptible Copies
  ---------------------------
  The symbol © (the letter C in a circle), or the word “Copyright,” or
  the abbreviation “Copr.”; 
  
  and ... [name and year]

i.e.

* in the US, the form ``(c) Copyright 1989 Hans Huhn`` is valid
  despite of the wrong (c).

* in Europe, no notice is needed

* the only difference is in countries not following the Berne convention
  (automatic copyright) but member of the Universal Copyright Convention
  (UCC). The `reliable link`_ says:
  
    To guarantee protection for a copyrighted work in all UCC member
    countries, the notice must consist of the symbol © (the word
    “Copyright” or the abbreviation is not acceptable)


OK to change

The changelog.Debian should skip this minor change or just state

     Replaced (C) by © and updated copyright year

If you prefer more explanation, please use the `reliable link`_.


> > > commit a85635b8e500adc5c72dda03e32d9ae05ce753eb
...
> > >     Enable hardening support
... 
> > Is there some data available about the performance loss?

> No for jed. The average impact should be in the lower percent range.
> http://lists.debian.org/debian-devel/2008/03/msg00165.html

> > Is jed startup time affected?

> From my feeling, no.

OK then.

> > > commit 13958e4937c1c311febddedef3000a98c0dcdeac
...
> > >     Move the FAQ from README.Debian to jed_faq.txt
...

> > Some answers of the README.Debian faq are Debian specific - we should
> > split them off and document in README.Debian (not necesserily in FAQ
> > format).

> I found only two points:

>    emulation in jed.rc overwriting your bindings (see also
>                                                  ^^^^^^^^^
>    README.Debian-startup).
>    ^^^^^^^^^^^^^^^^^^^^^^

> I've dropped this part.

OK.

>    c) Install jed-extra and use newline_indent().
>               ^^^^^^^^^
>       See Help>Describe_Function newline_indent for details.

> I've changed this to 

>   3: Install txtutils [1] from jedmodes and use newline_indent().
>      See Help>Describe_Function newline_indent for details.
>      [1] http://jedmodes.sourceforge.net/mode/txtutils/

OK as well.

So I am looking forward to have a usable 0.99 on my system soon.

Günter