agtk-devel — AGTK Developers Mailing List

Re: [agtk-devel] AGLIB tcl binding

[Haejoong L. <hae...@un...>]

> > I see.  However, the package name "ag" is too big for it.  How about
> > "ag_tcl"?  Does it need to be consistent with namespace name?
> 
> That would be ok, the directory name is irrelevant, it just needs to be in a 
> sibling directory to the tcl one.  How does the python package get installed? 

Currently, the python modules, ag.py and ag_python.so, are installed
in $prefix/lib. (prefix = /usr/local, by default.)

Kaz, one of AGTK developers, says that Python installation has a
directory named as "site-packages".  For example, in our file server,
I can see the following directory:

    /pkg/P/Python-2.1.1/lib/python2.1/site-packages

External packages can go to that directory.  Python expose another
mechanism to locate its packages; it reads an environment variable
called "PYTHONPATH".  Python searches directories in PYTHONPATH to
locate the requested packages.  I'm thinking about making the
former a default option.

Haejoong

Re: [agtk-devel] AGLIB tcl binding

[Steve C. <ste...@mq...>]

On Thu, 14 Feb 2002 08:25, Haejoong Lee wrote:
> > I've attached a version of ag.tcl which uses namespaces fyi.  I've put
> > everything into an AG namespace, including the AGF functions, I don't
> > know what the argument is for having them separate.  I've also
> > capitalised AG::Load and AG::Save for consistency with the rest of the
> > interface.
>
> Thanks, but I can't find any attached file. Could you please send it
> again?

Oops...done.


> I see.  However, the package name "ag" is too big for it.  How about
> "ag_tcl"?  Does it need to be consistent with namespace name?

That would be ok, the directory name is irrelevant, it just needs to be in a 
sibling directory to the tcl one.  How does the python package get installed? 

Steve

Re: [agtk-devel] AGLIB tcl binding

[Haejoong L. <hae...@un...>]

> I've attached a version of ag.tcl which uses namespaces fyi.  I've put 
> everything into an AG namespace, including the AGF functions, I don't know 
> what the argument is for having them separate.  I've also capitalised 
> AG::Load and AG::Save for consistency with the rest of the interface. 

Thanks, but I can't find any attached file. Could you please send it
again?

> > I agree with you. Since we have multiple wrappers (currently two),
> > the following would be better:
> >
> >     ag_wrapper/
> >         tcl/
> >             ag.tcl
> >             ag_tcl.so
> >             pkgIndex.tcl
> >         python/
> >             ag.py
> >             ag_python.so
> >
> 
> This wouldn't work at least with tcl since tcl will only look for packages in 
> sibling directories to it's own installation dir (eg all dirs in 
> /usr/local/lib). I imagine that python is similar.  The main thing is to get 
> the tcl package files into one directory that can be installed in the right 
> place or bundled up to form a binary extension package.

I see.  However, the package name "ag" is too big for it.  How about
"ag_tcl"?  Does it need to be consistent with namespace name?


> > So we have some options here:
> >
> >     (libag + libagf), (tcl wrapper), (python wrapper)
> >     (libag + libagf + tcl wrapper), (libag + libagf + python wrapper)
> >     (libag + libagf + tcl wrapper + python wrapper)
> >
> > I guess you meant the first choice. 
> 
> Yes, and even the second choice as a compile time option. This would give me 
> one big shared object I could deliver with my application if I only use AG 
> vial the tcl (or python) interface.  

I'll try to make that a configuration option.


Thanks,
Haejoong

Re: [agtk-devel] AGLIB tcl binding

[Steve C. <ste...@mq...>]

On Mon, 11 Feb 2002 21:52, Haejoong Lee wrote:
> > We're making use of the tcl binding just now. I'm wondering why it
> > doesn't use namespaces, eg AG::CreateAG rather than AG_CreateAG? 

> I think I'm the person who is responsible for most of the suggestions.
> I can't see exactly how "undo" stuff works. However, having a namespace
> sounds great.  To be honest, I didn't even know that Tcl support
> namespace. I'm not a Tcl programmer :)

I've attached a version of ag.tcl which uses namespaces fyi.  I've put 
everything into an AG namespace, including the AGF functions, I don't know 
what the argument is for having them separate.  I've also capitalised 
AG::Load and AG::Save for consistency with the rest of the interface. 

I did also put together an incr tcl class based interface but I'm currently 
thinking again about the best way to do that. 

The undo stuff works by redefining some of these procs to store an inverse 
command or set of commands on an undo stack. When you want to undo an 
operation in the editor you just run the commands of the stack and things are 
as they were.  Namespaces make things neater (so we can get a list of the 
commands in the interface easily) but our current implementation is based on 
an itcl class which defines all of the operations as methods. 

> I agree with you. Since we have multiple wrappers (currently two),
> the following would be better:
>
>     ag_wrapper/
>         tcl/
>             ag.tcl
>             ag_tcl.so
>             pkgIndex.tcl
>         python/
>             ag.py
>             ag_python.so
>

This wouldn't work at least with tcl since tcl will only look for packages in 
sibling directories to it's own installation dir (eg all dirs in 
/usr/local/lib). I imagine that python is similar.  The main thing is to get 
the tcl package files into one directory that can be installed in the right 
place or bundled up to form a binary extension package.

> > How hard (and desirable) would it be to combine the libraries into a
> > smaller number of shared objects.  
>
> So we have some options here:
>
>     (libag + libagf), (tcl wrapper), (python wrapper)
>     (libag + libagf + tcl wrapper), (libag + libagf + python wrapper)
>     (libag + libagf + tcl wrapper + python wrapper)
>
> I guess you meant the first choice. 

Yes, and even the second choice as a compile time option. This would give me 
one big shared object I could deliver with my application if I only use AG 
vial the tcl (or python) interface.  



Steve

Re: [agtk-devel] AGLIB tcl binding

[Claude B. <Cla...@li...>]

Haejoong Lee wrote:

>>We're making use of the tcl binding just now. I'm wondering why it doesn't 
>>use namespaces, eg AG::CreateAG rather than AG_CreateAG? Is it too late to 
>>change this now, it would be useful to us in one respect, we're creating a 
>>version of the API that stores undo information for certain operations and 
>>having the API as a namespace might make it easier to override the API calls 
>>we want to save undo info for.  
>>
> 
> I think I'm the person who is responsible for most of the suggestions.
> I can't see exactly how "undo" stuff works. However, having a namespace
> sounds great.  To be honest, I didn't even know that Tcl support
> namespace. I'm not a Tcl programmer :)


Hi folks,

I agree with Steve that using namespace would be more sensible for the Tcl
implementation (even if not crucial).

In fact, overriding Tcl calls by a modified version of the API for integration
of undo was also the way I intended using AG into Transcriber (cf our LREC paper:

http://www.etca.fr/CTA/gip/Projets/Transcriber/articles/Transcriber-LREC2000.ps.gz

) but it is still work in progress :-(

Anyway Steve: I have also some Tcl code and tests on tracing AG modifs so I
could share it... I only need to clean up a bit that piece of code!

Best,
   Claude

 

Re: [agtk-devel] AGLIB tcl binding

[Haejoong L. <hae...@un...>]

> We're making use of the tcl binding just now. I'm wondering why it doesn't 
> use namespaces, eg AG::CreateAG rather than AG_CreateAG? Is it too late to 
> change this now, it would be useful to us in one respect, we're creating a 
> version of the API that stores undo information for certain operations and 
> having the API as a namespace might make it easier to override the API calls 
> we want to save undo info for.  

I think I'm the person who is responsible for most of the suggestions.
I can't see exactly how "undo" stuff works. However, having a namespace
sounds great.  To be honest, I didn't even know that Tcl support
namespace. I'm not a Tcl programmer :)


> Secondly, the tcl wrapper doesn't install itself very nicely, I should be 
> able to say 'package require AG' to load the library.  I've begun to work out 
> how to do this but I'm having trouble comprehending the build system and 
> where the locations of libraries are specified.  Basically to make things 
> work in the Tcl Way the package should be installed in a subdirectory 
> adjacent to the tcl installation (eg /usr/local/lib/ag) looking like this:
> 
> ag/
>     ag.tcl
>     pkgIndex.tcl
>     ag_tcl.so *
> 
> at the moment the .tcl and .so files go in /usr/local/lib. Since the .so 
> files depend on other shared libraries (agf_tcl.so etc) then having them in 
> /usr/local/lib isn't unreasonable but it does make the whole thing a little 
> messy.   

I agree with you. Since we have multiple wrappers (currently two),
the following would be better:

    ag_wrapper/
        tcl/
            ag.tcl
            ag_tcl.so
            pkgIndex.tcl
        python/
            ag.py
            ag_python.so
    

> How hard (and desirable) would it be to combine the libraries into a smaller 
> number of shared objects.  Perhaps a core libag.so and then the language 
> bindings libag_tcl.so libag_python.so etc.  Since libag.so gets linked 
> against C++ code it would go in the standard lib directory, the others could 
> go where the scripting language could find them.  There might also be an 
> option to combine the lot into one shared object.  Then, when I'm shipping a 
> package based on AGLIB, the number of files and their interdependancies is 
> minimised.  

So we have some options here:

    (libag + libagf), (tcl wrapper), (python wrapper)
    (libag + libagf + tcl wrapper), (libag + libagf + python wrapper)
    (libag + libagf + tcl wrapper + python wrapper)

I guess you meant the first choice. That is probably a good idea.
The second doesn't look good because of the redundency.  The third
looks more complex. The single all-in-one library creates a large set
of dependencies. Python user may not want to install Tcl to use the
library.


> I don't know automake/libtool well enough to know how to make this happen. 
> I'm happy to help with code etc. to make the tcl package neater and more 
> useable. 

It would be great if you can give us more detailed direction about
namespace stuff. A sample modification would be also useful. After
discussion with ag team, I can work on ag wrapper installation and
library merging.

Thank you very much for the input.

Haejoong

[agtk-devel] AGLIB tcl binding

[Steve C. <ste...@mq...>]

We're making use of the tcl binding just now. I'm wondering why it doesn't 
use namespaces, eg AG::CreateAG rather than AG_CreateAG? Is it too late to 
change this now, it would be useful to us in one respect, we're creating a 
version of the API that stores undo information for certain operations and 
having the API as a namespace might make it easier to override the API calls 
we want to save undo info for.  

Secondly, the tcl wrapper doesn't install itself very nicely, I should be 
able to say 'package require AG' to load the library.  I've begun to work out 
how to do this but I'm having trouble comprehending the build system and 
where the locations of libraries are specified.  Basically to make things 
work in the Tcl Way the package should be installed in a subdirectory 
adjacent to the tcl installation (eg /usr/local/lib/ag) looking like this:

ag/
    ag.tcl
    pkgIndex.tcl
    ag_tcl.so *

at the moment the .tcl and .so files go in /usr/local/lib. Since the .so 
files depend on other shared libraries (agf_tcl.so etc) then having them in 
/usr/local/lib isn't unreasonable but it does make the whole thing a little 
messy.   

How hard (and desirable) would it be to combine the libraries into a smaller 
number of shared objects.  Perhaps a core libag.so and then the language 
bindings libag_tcl.so libag_python.so etc.  Since libag.so gets linked 
against C++ code it would go in the standard lib directory, the others could 
go where the scripting language could find them.  There might also be an 
option to combine the lot into one shared object.  Then, when I'm shipping a 
package based on AGLIB, the number of files and their interdependancies is 
minimised.  

I don't know automake/libtool well enough to know how to make this happen. 
I'm happy to help with code etc. to make the tcl package neater and more 
useable. 

Steve

[agtk-devel] tcl wrapper to aglib

[Claude B. <Cla...@li...>]

Hi folks,

I have started playing with the Tcl interface to aglib.

I have a few comments/requests/etc.:

* it exits immediately as soon as any kind of error
  is detected. It should be possible to propagate an
  error message to the Tcl client without stopping the
  process in many cases (except perhaps when an inconsistency
  of the internal data is detected)

  Else some error checking may be performed at Tcl level, eg:

  proc AG2_CreateAnnotation {id anchorId1 anchorId2 annotationType} {
    if {[ExistsAnnotation $id]} {
      error "Annotation '$id' already exists"
    }
    if {![ExistsAnchor $anchorId1]} { error "Anchor '$anchorId1' does not exist" }
    if {![ExistsAnchor $anchorId2]} { error "Anchor '$anchorId2' does not exist" }
    return [AG_CreateAnnotation $id $anchorId1 $anchorId2 $annotationType]
  }

* an inconsistency does not seem to be detected in following case:

   CreateAnnotation a n1 n2
   DeleteAnchor n1
  => n1 remains referenced in annotation a
  (delete op should have been forbidden)

* in the IDL specs, there seems to be some redundancy between 
   DeleteFeature vs. UnsetFeature ?
  (or else I may have forgotten their difference...)

* a function like "GetAnnotationType" seems to be lacking?

* there seems to be no way to see the difference between an unset
  offset and one set to -1; should we assume that no negative offset
  will be used? else there should be something like "HasOffset anchorId"

* in the ag.tcl there is a small typo for a $epsilon becoming $spsilon



As an application, I put below a piece of Tcl code checking that
an AG is indeed an acyclic, correctly oriented, anchored graph.
(here, unset offset is checked through -1 value)

Best,
  Claude


##########################################################

  # Check that a whole graph is well-formed:
  #   right temporal order of anchors, no loop.
  # Raise an error in case of loop or wrong temporal order.
  proc CheckAG {agId} {
    # For each anchor, we compute its left and right boundaries
    # recursively and store the result in an array.
    # As a side effect, loops are detected in this step.
    # Both arrays are reused as a cache for subsequent searchs,
    # so we don't parse the same arcs twice in the same direction.
    foreach id [AG_GetAnnotationSeqByOffset $agId 0.0 0.0] {
      # Get offset of start anchor or lower boundary instead
      set start [AG_GetStartAnchor $id]
      set l [AG_GetAnchorOffset $start]
      if {$l == -1} {
        set l [anchorBoundary $start "lower" left]
      }
      # Get offset of end anchor or upper boundary instead
      set end [AG_GetEndAnchor $id]
      set r [AG_GetAnchorOffset $end]
      if {$r == -1} {
        set r [anchorBoundary $end "upper" right]
      }
      # Check order of start/end anchor
      if {$end != $start && $l != -1 && $r != -1 && $l >= $r} {
        error "Wrong temporal order of start/end anchors for annotation $id"
      }
    }
  }

  # Returns nearest temporal boundary of $id anchor in $dir (upper or lower) direction
  proc anchorBoundary {id dir {arrayNam ""} {stack ""}} {
    # Prevent circular lock and multiple loops
    if {$arrayNam != ""} {
      upvar $arrayNam cycl
    }
    if {[info exists cycl($id)]} {
      if {[lsearch -exact $stack $id] >= 0} {
        error "Loop detected within graph (back to anchor $id)"
      }
      return $cycl($id)
    } else {
      set cycl($id) ""
      lappend stack $id
    }
    # Adjust direction of search
    if {$dir == "upper"} {
      set lst [AG_GetOutgoingAnnotationSet $id]
      set flag "AG_GetEndAnchor"
      set comp ">"
    } else {
      set lst [AG_GetIncomingAnnotationSet $id]
      set flag "AG_GetStartAnchor"
      set comp "<"
    }
    # Recursive search of the nearest timed anchor
    set nearest ""
    foreach arc $lst {
      set node [$flag $arc]
      if {$node == $id} continue
      set off [AG_GetAnchorOffset $node]
      if {$off == -1} {
        set off [anchorBoundary $node $dir cycl $stack]
      }
      if {$nearest == "" || ($off != -1 && [expr $nearest $comp $off])} {
        set nearest $off
      }
    }
    set cycl($id) $nearest
    if {$nearest == ""} {
      error "No $dir boundary found for '$id'"
    }
    return $nearest
  }

[agtk-devel] possible bug

[Joshua S. <si...@un...>]

[agtk-devel] AGLIB at Philips

[Steven B. <sb...@un...>]

Folks,

I've promised that we'll have AGLIB compiling cleanly on alpha by the time
of our 1.0 release.

The sourceforge compile farm doesn't have alpha with DEC-OSF, so we'll need
to try to find such a machine.  I'll ask around.

-Steven

------- Forwarded Message

From: hen...@ph...
Subject: aglib on DEC OSF
To: sb...@ld...
Date: Mon, 20 Aug 2001 17:59:36 +0200

Dear Mr. Bird,

we (Philips Research Lab. Aachen, Speech group) are currently regarding to
use the annotation graph library as IO- and data represenatation facility
within our NLP research software architecture. I am personally quite
fascinated by your ambitious project.

I had no problems compiling the library 0.99.2 on Linux (i386-redhat-linux,
Compiler egcs-2.91.66), but a lot of them on alpha (DEC-OSF 4.0, several
gcc-versions including the most recent 3.0): identifiers become too long
for linking and assembling, throw()-declarations are too loose...

Do you know of any experiences with compiling on different UNIX-platforms?
Maybe there are experts in your group for such difficulties?

I don´t want to bother you with my questions, but I hope that such
platform-independency topics are of interest for the general development of
aglib.

I attach the make-output of my "most successful" compilation (without
debugging flag -g, that does not work at all), for the case you are
interested in it.

Thanks a lot and best regards,    Henrik Botterweck

----------------------------------------------------------------------------
Dr. Henrik Botterweck
Research Scientist
Philips GmbH Reseachratories Aachen
52066 Aachen, Germany

Tel.: ++49 6003 506
Hen...@ph...
----------------------------------------------------------------------------

/vol/nlp_tools/ATLAS/aglib-0.99.2>make

Making all in ag
make[1]: Entering directory `/tmp_mnt/vol/nlp_tools/ATLAS/aglib-0.99.2/ag'
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c AGAPI.cc
mkdir .libs
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c AGAPI.cc  -DPIC -o AGAPI.o
mv -f AGAPI.o .libs/AGAPI.lo
mv -f .libs/AGAPI.lo AGAPI.o
(cd . && ln -s AGAPI.o AGAPI.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c AGSet.cc
rm -f .libs/AGSet.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c AGSet.cc  -DPIC -o AGSet.o
mv -f AGSet.o .libs/AGSet.lo
mv -f .libs/AGSet.lo AGSet.o
(cd . && ln -s AGSet.o AGSet.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c AG.cc
rm -f .libs/AG.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c AG.cc  -DPIC -o AG.o
mv -f AG.o .libs/AG.lo
mv -f .libs/AG.lo AG.o
(cd . && ln -s AG.o AG.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c AnnotationIndex.cc
rm -f .libs/AnnotationIndex.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c AnnotationIndex.cc  -DPIC -o AnnotationIndex.o
mv -f AnnotationIndex.o .libs/AnnotationIndex.lo
mv -f .libs/AnnotationIndex.lo AnnotationIndex.o
(cd . && ln -s AnnotationIndex.o AnnotationIndex.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Annotation.cc
rm -f .libs/Annotation.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Annotation.cc  -DPIC -o Annotation.o
mv -f Annotation.o .libs/Annotation.lo
mv -f .libs/Annotation.lo Annotation.o
(cd . && ln -s Annotation.o Annotation.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Region.cc
rm -f .libs/Region.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Region.cc  -DPIC -o Region.o
mv -f Region.o .libs/Region.lo
mv -f .libs/Region.lo Region.o
(cd . && ln -s Region.o Region.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Anchor.cc
rm -f .libs/Anchor.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Anchor.cc  -DPIC -o Anchor.o
mv -f Anchor.o .libs/Anchor.lo
mv -f .libs/Anchor.lo Anchor.o
(cd . && ln -s Anchor.o Anchor.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Identifiers.cc
rm -f .libs/Identifiers.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Identifiers.cc  -DPIC -o Identifiers.o
mv -f Identifiers.o .libs/Identifiers.lo
mv -f .libs/Identifiers.lo Identifiers.o
(cd . && ln -s Identifiers.o Identifiers.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Signal.cc
rm -f .libs/Signal.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Signal.cc  -DPIC -o Signal.o
mv -f Signal.o .libs/Signal.lo
mv -f .libs/Signal.lo Signal.o
(cd . && ln -s Signal.o Signal.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c InternalId.cc
rm -f .libs/InternalId.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c InternalId.cc  -DPIC -o InternalId.o
mv -f InternalId.o .libs/InternalId.lo
mv -f .libs/InternalId.lo InternalId.o
(cd . && ln -s InternalId.o InternalId.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c AGException.cc
rm -f .libs/AGException.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c AGException.cc  -DPIC -o AGException.o
mv -f AGException.o .libs/AGException.lo
mv -f .libs/AGException.lo AGException.o
(cd . && ln -s AGException.o AGException.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Timeline.cc
rm -f .libs/Timeline.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Timeline.cc  -DPIC -o Timeline.o
mv -f Timeline.o .libs/Timeline.lo
mv -f .libs/Timeline.lo Timeline.o
(cd . && ln -s Timeline.o Timeline.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Metadata.cc
rm -f .libs/Metadata.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Metadata.cc  -DPIC -o Metadata.o
mv -f Metadata.o .libs/Metadata.lo
mv -f .libs/Metadata.lo Metadata.o
(cd . && ln -s Metadata.o Metadata.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Content.cc
rm -f .libs/Content.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Content.cc  -DPIC -o Content.o
mv -f Content.o .libs/Content.lo
mv -f .libs/Content.lo Content.o
(cd . && ln -s Content.o Content.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.      -O2 -c Feature.cc
rm -f .libs/Feature.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -O2 -c Feature.cc  -DPIC -o Feature.o
mv -f Feature.o .libs/Feature.lo
mv -f .libs/Feature.lo Feature.o
(cd . && ln -s Feature.o Feature.lo)
/bin/ksh ../libtool --mode=link /usr/local/gcc-3.0/bin/gcc  -O2  -o libag.la -rpath /vol/nlp_tools/ATLAS/alpha/lib -no-undefined -version-info 0:0:0 AGAPI.lo AGSet.lo AG.lo AnnotationIndex.lo Annotation.lo Region.lo Anchor.lo Identifiers.lo Signal.lo InternalId.lo AGException.lo Timeline.lo Metadata.lo Content.lo Feature.lo -lstdc++
rm -fr .libs/libag.la .libs/libag.* .libs/libag.*
gcc -shared  AGAPI.o AGSet.o AG.o AnnotationIndex.o Annotation.o Region.o Anchor.o Identifiers.o Signal.o InternalId.o AGException.o Timeline.o Metadata.o Content.o Feature.o   -lstdc++  -Wl,-msym -Wl,-soname -Wl,libag.so `test -n "0.0.0:0.0" && echo -Wl,-set_version -Wl,0.0.0:0.0` -Wl,-update_registry -Wl,.libs/so_locations -o .libs/libag.so.0.0.0
/usr/ucb/ld:
Warning: Unresolved:
_ZSt4cerr
_Unwind_Resume
_ZSt20__throw_out_of_rangePKc
_ZNSt24__default_alloc_templateILb1ELi0EE12_S_free_listE
_ZdlPv
_Znwm
__cxa_allocate_exception
__cxa_throw
__cxa_begin_catch
__cxa_end_catch
_ZNSt10ostrstreamC1Ev
_ZNSt10ostrstream3strEv
_ZNSt10ostrstreamD1Ev
_ZSt18uncaught_exceptionv
_ZSt19__throw_ios_failurePKc
__cxa_rethrow
__cxa_call_unexpected
_ZNSs4_Rep11_S_terminalE
_ZNSt24__default_alloc_templateILb1ELi0EE22_S_node_allocator_lockE
_ZNSs4_Rep11_S_max_sizeE
_ZSt20__throw_length_errorPKc
_ZNSt13_Format_cacheIcEC1Ev
_ZNSt8ios_base17register_callbackEPFvNS_5eventERS_iEi
_ZNSt8ios_base13_M_grow_wordsEi
_ZNSt8ios_base6xallocEv
_ZNSt23__malloc_alloc_templateILi0EE26__malloc_alloc_oom_handlerE
_ZSt17__throw_bad_allocv
_ZNSt6localeC1ERKS_
_ZNSt6localeD1Ev
_ZNSt24__default_alloc_templateILb1ELi0EE11_S_end_freeE
_ZNSt24__default_alloc_templateILb1ELi0EE13_S_start_freeE
_ZNSt24__default_alloc_templateILb1ELi0EE12_S_heap_sizeE
_ZSt16__throw_bad_castv
_ZNSt8ios_base4InitC1Ev
_ZNSt8ios_base4InitD1Ev
_ZTVN10__cxxabiv117__class_type_infoE
__gxx_personality_v0
_ZSt4cout
(cd .libs && rm -f libag.so && ln -s libag.so.0.0.0 libag.so)
(cd .libs && rm -f libag.so && ln -s libag.so.0.0.0 libag.so)
ar cru .libs/libag.a  AGAPI.o AGSet.o AG.o AnnotationIndex.o Annotation.o Region.o Anchor.o Identifiers.o Signal.o InternalId.o AGException.o Timeline.o Metadata.o Content.o Feature.o
ranlib .libs/libag.a
creating libag.la
(cd .libs && rm -f libag.la && ln -s ../libag.la libag.la)
make[1]: Leaving directory `/tmp_mnt/vol/nlp_tools/ATLAS/aglib-0.99.2/ag'
Making all in agf
make[1]: Entering directory `/tmp_mnt/vol/nlp_tools/ATLAS/aglib-0.99.2/agf'
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.  -I../ag -I/home/botter/vb/philus/include/external/xerces    -O2 -c BAS.cc
mkdir .libs
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -I../ag -I/home/botter/vb/philus/include/external/xerces -O2 -c BAS.cc  -DPIC -o BAS.o
In file included from agfio.h:15,
                 from BAS.h:15,
                 from BAS.cc:12:
AgfioError.h:42:8: warning: extra tokens at end of #endif directive
In file included from BAS.h:15,
                 from BAS.cc:12:
agfio.h:78:8: warning: extra tokens at end of #endif directive
In file included from BASfile.h:14,
                 from BAS.h:16,
                 from BAS.cc:12:
Record.h:126:8: warning: extra tokens at end of #endif directive
In file included from BASfile.h:15,
                 from BAS.h:16,
                 from BAS.cc:12:
RE.h:106:8: warning: extra tokens at end of #endif directive
In file included from BAS.h:16,
                 from BAS.cc:12:
BASfile.h:61:8: warning: extra tokens at end of #endif directive
In file included from BAS.cc:12:
BAS.h:69:8: warning: extra tokens at end of #endif directive
mv -f BAS.o .libs/BAS.lo
mv -f .libs/BAS.lo BAS.o
(cd . && ln -s BAS.o BAS.lo)
/bin/ksh ../libtool --mode=compile /usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1  -I. -I.  -I../ag -I/home/botter/vb/philus/include/external/xerces    -O2 -c BASfile.cc
rm -f .libs/BASfile.lo
/usr/local/gcc-3.0/bin/gcc -DPACKAGE=\"aglib\" -DVERSION=\"0.99.2\" -DHAVE_DLFCN_H=1 -I. -I. -I../ag -I/home/botter/vb/philus/include/external/xerces -O2 -c BASfile.cc  -DPIC -o BASfile.o
In file included from Record.h:14,
                 from BASfile.h:14,
                 from BASfile.cc:9:
AgfioError.h:23: parse error before `{' token
AgfioError.h:33: destructors must be member functions
AgfioError.h:39: virtual outside class declaration
AgfioError.h:39: non-member function `const char* what()' cannot have `const'
   method qualifier
AgfioError.h:40: parse error before `}' token
In file included from Record.h:14,
                 from BASfile.h:14,
                 from BASfile.cc:9:
AgfioError.h:42:8: warning: extra tokens at end of #endif directive
In file included from BASfile.h:14,
                 from BASfile.cc:9:
Record.h:22: 'ifstream' is used as a type, but is not defined as a type.
Record.h:23: 'string' is used as a type, but is not defined as a type.
Record.h:24: syntax error before `*' token
Record.h:42: base class `AgfioError' has incomplete type
Record.h:44: parse error before `&' token
Record.h:62: parse error before `&' token
Record.h:73: `string' was not declared in this scope
Record.h:73: `line' was not declared in this scope
Record.h:73: invalid data member initialization
Record.h:73: (use `=' to initialize static data members)
Record.h:82: parse error before `&' token
Record.h:91: parse error before `)' token
Record.h:96: parse error before `)' token
In file included from BASfile.h:14,
                 from BASfile.cc:9:
Record.h:126:8: warning: extra tokens at end of #endif directive
In file included from BASfile.h:15,
                 from BASfile.cc:9:
RE.h:24: 'string' is used as a type, but is not defined as a type.
RE.h:31: base class `AgfioError' has incomplete type
RE.h:33: parse error before `&' token
RE.h:33: missing ';' before right brace
RE.h:34: missing ';' before right brace
RE.h:42: base class `AgfioError' has incomplete type
RE.h:44: parse error before `&' token
RE.h:44: missing ';' before right brace
RE.h:54: base class `AgfioError' has incomplete type
RE.h:56: parse error before `&' token
RE.h:56: missing ';' before right brace
RE.h:64: parse error before `const'
RE.h:65: destructors must be member functions
RE.h:72: parse error before `&' token
RE.h:85: parse error before `int'
RE.h:104: parse error before `}' token
In file included from BASfile.h:15,
                 from BASfile.cc:9:
RE.h:106:8: warning: extra tokens at end of #endif directive
In file included from BASfile.cc:9:
BASfile.h:23: syntax error before `*' token
BASfile.h:24: syntax error before `*' token
BASfile.h:25: `string' was not declared in this scope
BASfile.h:25: 'map' is used as a type, but is not defined as a type.
BASfile.h:27: parse error before `&' token
BASfile.h:28: parse error before `&' token
BASfile.h:29: parse error before `&' token
BASfile.h:30: parse error before `&' token
BASfile.h:43: parse error before `&' token
BASfile.h:50: parse error before `)' token
BASfile.h:52: parse error before `)' token
BASfile.h:54: parse error before `)' token
BASfile.h:56: parse error before `)' token
BASfile.h:58: parse error before `)' token
In file included from BASfile.cc:9:
BASfile.h:61:8: warning: extra tokens at end of #endif directive
BASfile.cc: In member function `void BASfile::init()':
BASfile.cc:20: `tierRE' undeclared (first use this function)
BASfile.cc:20: (Each undeclared identifier is reported only once for each
   function it appears in.)
BASfile.cc:20: parse error before `(' token
BASfile.cc:21: parse error before `(' token
BASfile.cc:22: parse error before `(' token
BASfile.cc:23: parse error before `(' token
BASfile.cc:25: `classMap' undeclared (first use this function)
BASfile.cc: At global scope:
BASfile.cc:53: parse error before `&' token
BASfile.cc:57: ISO C++ forbids declaration of `init' with no type
BASfile.cc:58: parse error before `}' token
BASfile.cc:71: parse error before `&' token
BASfile.cc: In member function `bool BASfile::tier_process1(...)':
BASfile.cc:73: `tier' undeclared (first use this function)
BASfile.cc: At global scope:
BASfile.cc:85: parse error before `&' token
BASfile.cc:99: parse error before `&' token
BASfile.cc: In member function `virtual void BASfile::preprocess()':
BASfile.cc:115: `string' undeclared (first use this function)
BASfile.cc:115: parse error before `;' token
BASfile.cc:116: `line' undeclared (first use this function)
BASfile.cc:116: `this->Record::readline' cannot be used as a function
BASfile.cc: In member function `virtual void BASfile::read_entry()':
BASfile.cc:123: parse error before `;' token
BASfile.cc:125: `this->Record::readline' cannot be used as a function
BASfile.cc:133: `cerr' undeclared (first use this function)
BASfile.cc:133: `get_filename' undeclared (first use this function)
BASfile.cc:134: `endl' undeclared (first use this function)
BASfile.cc: In member function `bool BASfile::read_record()':
BASfile.cc:160: `get_type' undeclared (first use this function)
BASfile.cc: At global scope:
BASfile.cc:165: syntax error before `::' token
BASfile.cc:171: syntax error before `::' token
BASfile.cc:177: syntax error before `::' token
BASfile.cc:183: syntax error before `::' token
BASfile.cc:189: syntax error before `::' token
make[1]: *** [BASfile.lo] Error 1
make[1]: Leaving directory `/tmp_mnt/vol/nlp_tools/ATLAS/aglib-0.99.2/agf'
make: *** [all-recursive] Error 1
Exit 2


------- End of Forwarded Message

[agtk-devel] Brian MacWhinney: AGTK on Windows

[Steven B. <sb...@un...>]

------- Forwarded Message

Return-Path: Co...@ma... 
Received: from mail.talkbank.org (MAIL.TALKBANK.ORG [128.2.57.175])
	by unagi.cis.upenn.edu (8.10.1/8.10.1) with SMTP id f66CBIv01313;
	Fri, 6 Jul 2001 08:11:18 -0400 (EDT)
Received: from hku.hk by mail.talkbank.org with SMTP; Fri, 6 Jul 2001
 08:11:18 -0400
User-Agent: Microsoft-Entourage/9.0.2509
Date: Fri, 06 Jul 2001 20:11:12 +0800
Subject: AGTK on Windows
From: Brian MacWhinney <mac...@hk...>
To: codon <Co...@ma...>
Message-ID: <B76BCBE0.2A01%mac...@hk...>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Sender: <Co...@ma...>
Precedence: Bulk

Dear Codon,

  Just now got around to installing the AGTK 0.98 from SourceForge on my
Windows98.  It installed fine and ran fine, although sound playback was
sometimes jerky.  I noticed that the sound became uncoupled from the
transcript, particularly in Demo 2, probably because my machine was weak.
Are Demo 1 and 2 primarily intended to demonstrate sound playback from a
Transcriber-like interface.  If so, they seem fine, except for the
jerkiness.
  The annotation tool also seemed to work fine, although I couldn't figure
out how to play any sound to annotate, but it was easy enough to enter
codes.  I poked around in the docs and libraries a bit.  After reading the
details of the Unix installation, I realized how nice it was to have a
Windows installation that just ran itself.
 I guess what I would love to see next is a player for CHAT files or perhaps
some LDC data set and maybe to better understand the shape of the
distribution in terms of what is where for both data and programmer's
resources.  I wonder if you need any other type of feedback on this now.

- --Brian MacWhinney


------- End of Forwarded Message

Re: [agtk-devel] Copy of License

[Kazuaki M. <ma...@un...>]

From: "Jason Reynolds" <Jas...@Ho...>
Subject: [agtk-devel] Copy of License
Date: Fri, 15 Jun 2001 11:18:48 -0500

> Can you make a copy of the license available either in the post or on your web-site for our reading pleasure?
> 
> J

Hi,

I am sorry for the delay in replying to this message.  The following is a
copy of the current license, which is also included in the distributions
and in the CVS repository.

Regards,
-Kazuaki Maeda
--------

This software is Copyright (C) 2001 Linguistic Data Consortium, U Penn, and
is licensed under the terms of the Common Public License, Version 0.5 or
(at your option) any subsequent version.

The license is approved by the Open Source Initiative, and is available
from their website at www.opensource.org.

--------

Common Public License Version 0.5

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC
LICENSE ("AGREEMENT").  ANY USE, REPRODUCTION OR DISTRIBUTION OF THE
PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1.  DEFINITIONS

"Contribution" means:  

a) in the case of the initial Contributor, the initial code and
   documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i)  changes to the Program, and
ii) additions to the Program;

where such changes and/or additions to the Program originate from and are
distributed by that particular Contributor.  A Contribution 'originates'
from a Contributor if it was added to the Program by such Contributor
itself or anyone acting on such Contributor's behalf.  Contributions do not
include additions to the Program which: (i) are separate modules of
software distributed in conjunction with the Program under their own
license agreement, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents " mean patent claims licensable by a Contributor which
are necessarily infringed by the use or sale of its Contribution alone or
when combined with the Program.

"Program" means the Contributions distributed in accordance with this
Agreement.

"Recipient" means anyone who receives the Program under this Agreement,
including all Contributors.

2.  GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free copyright license to
reproduce, prepare derivative works of, publicly display, publicly perform,
distribute and sublicense the Contribution of such Contributor, if any, and
such derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free patent license under
Licensed Patents to make, use, sell, offer to sell, import and otherwise
transfer the Contribution of such Contributor, if any, in source code and
object code form.  This patent license shall apply to the combination of
the Contribution and the Program if, at the time the Contribution is added
by the Contributor, such addition of the Contribution causes such
combination to be covered by the Licensed Patents.  The patent license
shall not apply to any other combinations which include the Contribution.
No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses
to its Contributions set forth herein, no assurances are provided by any
Contributor that the Program does not infringe the patent or other
intellectual property rights of any other entity.  Each Contributor
disclaims any liability to Recipient for claims brought by any other entity
based on infringement of intellectual property rights or otherwise.  As a
condition to exercising the rights and licenses granted hereunder, each
Recipient hereby assumes sole responsibility to secure any other
intellectual property rights needed, if any.  For example, if a third party
patent license is required to allow Recipient to distribute the Program, it
is Recipient's responsibility to acquire that license before distributing
the Program.

d) Each Contributor represents that to its knowledge it has sufficient
copyright rights in its Contribution, if any, to grant the copyright
license set forth in this Agreement.

3.  REQUIREMENTS

A Contributor may choose to distribute the Program in object code form
under its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i)   effectively disclaims on behalf of all Contributors all warranties and
     conditions, express and implied, including warranties or conditions of
     title and non-infringement, and implied warranties or conditions of
     merchantability and fitness for a particular purpose; 

ii)  effectively excludes on behalf of all Contributors all liability for
     damages, including direct, indirect, special, incidental and consequential
     damages, such as lost profits; 

iii) states that any provisions which differ from this Agreement are
     offered by that Contributor alone and not by any other party; and

iv)  states that source code for the Program is available from such
     Contributor, and informs licensees how to obtain it in a reasonable
     manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and 

b) a copy of this Agreement must be included with each copy of the Program.  

Contributors may not remove or alter any copyright notices contained within
the Program.

Each Contributor must identify itself as the originator of its
Contribution, if any, in a manner that reasonably allows subsequent
Recipients to identify the originator of the Contribution.  

4.  COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities
with respect to end users, business partners and the like.  While this
license is intended to facilitate the commercial use of the Program, the
Contributor who includes the Program in a commercial product offering
should do so in a manner which does not create potential liability for
other Contributors.   Therefore, if a Contributor includes the Program in a
commercial product offering, such Contributor ("Commercial Contributor")
hereby agrees to defend and indemnify every other Contributor ("Indemnified
Contributor") against any losses, damages and costs (collectively "Losses")
arising from claims, lawsuits and other legal actions brought by a third
party against the Indemnified Contributor to the extent caused by the acts
or omissions of such Commercial Contributor in connection with its
distribution of the Program in a commercial product offering.  The
obligations in this section do not apply to any claims or Losses relating
to any actual or alleged intellectual property infringement.  In order to
qualify, an Indemnified Contributor must: a) promptly notify the Commercial
Contributor in writing of such claim, and b) allow the Commercial
Contributor to control, and cooperate with the Commercial Contributor in,
the defense and any related settlement negotiations.  The Indemnified
Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial
product offering, Product X.  That Contributor is then a Commercial
Contributor.  If that Commercial Contributor then makes performance claims,
or offers warranties related to Product X, those performance claims and
warranties are such Commercial Contributor's responsibility alone.  Under
this section, the Commercial Contributor would have to defend claims
against the other Contributors related to those performance claims and
warranties, and if a court requires any other Contributor to pay any
damages as a result, the Commercial Contributor must pay those damages.


5.  NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON
AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER
EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR
CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Each Recipient is solely responsible for determining
the appropriateness of using and distributing the Program and assumes all
risks associated with its exercise of rights under this Agreement,
including but not limited to the risks and costs of program errors,
compliance with applicable laws, damage to or loss of data, programs or
equipment, and unavailability or interruption of operations.  


6.  DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY
CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION
LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.


7.  GENERAL

If any provision of this Agreement is invalid or unenforceable under
applicable law, it shall not affect the validity or enforceability of the
remainder of the terms of this Agreement, and without further action by the
parties hereto, such provision shall be reformed to the minimum extent
necessary to make such provision valid and enforceable.

If Recipient institutes patent litigation against a Contributor with
respect to a patent applicable to software (including a cross-claim or
counterclaim in a lawsuit), then any patent licenses granted by that
Contributor to such Recipient under this Agreement shall terminate as of
the date such litigation is filed.  In addition, If Recipient institutes
patent litigation against any entity (including a cross-claim or
counterclaim in a lawsuit) alleging that the Program itself (excluding
combinations of the Program with other software or hardware) infringes such
Recipient's patent(s), then such Recipient's rights granted under Section
2(b) shall terminate as of the date such litigation is filed. 

All Recipient's rights under this Agreement shall terminate if it fails to
comply with any of the material terms or conditions of this Agreement and
does not cure such failure in a reasonable period of time after becoming
aware of such noncompliance.  If all Recipient's rights under this
Agreement terminate, Recipient agrees to cease use and distribution of the
Program as soon as reasonably practicable.  However, Recipient's
obligations under this Agreement and any licenses granted by Recipient
relating to the Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but
in order to avoid inconsistency the Agreement is copyrighted and may only
be modified in the following manner. The Agreement Steward reserves the
right to publish new versions (including revisions) of this Agreement from
time to time. No one other than the Agreement Steward has the right to
modify this Agreement. LDC is the initial Agreement Steward.  LDC may
assign the responsibility to serve as the Agreement Steward to a suitable
separate entity.  Each new version of the Agreement will be given a
distinguishing version number.  The Program (including Contributions) may
always be distributed subject to the version of the Agreement under which
it was received. In addition, after a new version of the Agreement is
published, Contributor may elect to distribute the Program (including its
Contributions) under the new version.  Except as expressly stated in
Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to
the intellectual property of any Contributor under this Agreement, whether
expressly, by implication, estoppel or otherwise.  All rights in the
Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the
intellectual property laws of the United States of America. No party to
this Agreement will bring a legal action under this Agreement more than one
year after the cause of action arose.  Each party waives its rights to a
jury trial in any resulting litigation.

END

[agtk-devel] Copy of License

[Jason R. <Jas...@Ho...>]

Can you make a copy of the license available either in the post or on =
your web-site for our reading pleasure?

J

[agtk-devel] testing aglib

[Claude B. <Cla...@li...>]

Hi Steven,

I have just started installing and testing AG libs,
installation went without pb on my Linux box (RedHat6.1)
but it has grown a lot and I am not sure to jump into
the code, so I will start with only 2 little remarks...

I could also test the Tcl wrapper (for some reason I needed to
do a 'make install' in both ag_wrapper and agf subdirectories
for installing agf and ag_tcl shared libs) - I will probably
mainly focus on using this interface in the future.

Best,

 -  Claude



The demo/agdemo results in little garbage (some kind
of buffer overflow somewhere) at the end of the 2nd toXML
output - it may depend of my configuration :

-------------------------

change the offset of anchor1 to 5.00:
<?xml version="1.0"?>
<!DOCTYPE AGSet SYSTEM "ag.dtd">
(...
  some stuff cut here
...)
<Annotation id="TIMIT:AG1:Annotation2" type="timit" start="TIMIT:AG1:Anchor2" end="TIMIT:AG1:Anchor3">
<Feature name="sentence">We'll see you around 8 o'clock.</Feature>
</Annotation>
</AG>
</AGSet>
>
</AG>
</AGSet>
-------------------------


About Timit example: you have

<Timeline id="Timit:Timeline1">
<Signal id="Timit:Timeline1:Signal1" (...) xlink:href="LDC93S1:sa1.wav"></Signal>
</Timeline>

<AG id="Timit:AG1" timeline="Timit:Timeline1">
<Anchor id="Timit:AG1:Anchor1" offset="0" unit="16kHz" signals="Timit:Timeline1:Signal1"></Anchor>
...
</AG>

In the (widespread) case where you have a single signal in the
Timeline, each Anchor could inherit of the Signal from its Timeline
when remaining to a default empty value (thus avoiding some
redundancy and systematic consistency checking)?
We probably discussed about this already but I forgot the rationale...



-- 
Claude BARRAS                 e-mail: Cla...@li...
LIMSI-CNRS                    tel:    +33 1 69 85 80 61
bat. 508, BP 133              fax:    +33 1 69 85 80 88
91403 Orsay cedex France      web:    http://www.limsi.fr/Individu/barras/

[agtk-devel] installation problem: missing ag_tcl.so?

[Steven B. <sb...@un...>]

------- Forwarded Message

Date: Wed, 30 May 2001 14:45:53 -0700
From: Nicolas Garbe <ga...@et...>
To: sb...@un...
CC: Edouard Geoffrois <Edo...@et...>,
   sylvain soliman <Syl...@et...>
Subject: version 0.98

Dear Steven,
My name is Nicolas Garbe and I am working with Edouard Geoffrois at DGA
on Transcriber.
I am writing to you because I have a problem with version 0.98 of
Annotation Graph Tool.
I downloaded and installed aglib-0.98.1.tar.gz.
After I downloaded AGAPPL-0.98.1.tar.gz.
Then in the bin directory, I try 
demo1....
There is an error message...
We get the following error:

Error in startup script: couldn't load file "ag_tcl.so": ag_tcl.so:
cannot open shared object file: Aucun fichier ou répertoire de ce type
    while executing
"load ag_tcl.so"
    (file "./ag-main" line 38) 

I have checked that ag_tcl.so, libag.soand libagf.so are in
/usr/local/lib but ag_tcl.so isn't in /usr/local/lib...

ag_tcl.so isn't created by aglib-0.98.1.tar.gz, I checked in the
Makefile and ag_tcl isn't specified...
How could I have ag_tcl.so?
Do you have any idea of what could be the problem?

Best Regards,

Nicolas.

-- 
Nicolas GARBE				e-mail: ga...@et...
CTA/GIP/PRE				tel:    +33 1 42 31 97 84
16 bis av.prieur de la cote d'or        fax:    +33 1 42 31 99 64
94114 arcueil cedex

------- End of Forwarded Message

[agtk-devel] Welcome to AGTK-Devel

[Steven B. <sb...@un...>]

Welcome to the AGTK-Devel mailing list.
This is a test message.