Constraint Grammar

Fixed, and nightly packages rebuilt with the fix. -- Tino Didriksen On Fri, 10 May 2024 at 15:44,

Dear all, Good news: The proceedings of the CG-MTA 2023 workshop, held in connection with NoDaLiDa in

Despite being the one to implement this, I had already forgotten that the relevant specifier was w

I have now tried the WITH construction (with vislcg3 freshly compiled from the newest git source),

G'day everyone, CC mailing list, Thank you for participating in last week's Constraint

A new release of CG-3 has been tagged v1.4.5 (binary rev 13897). Haven't made done one of these

Dear Colleagues, It has come to our attention that Constraint Grammar's activities are seriously

============================================================================= CONSTRAINT GRAMMAR

The documentation says: Rule option SUB:N tells a rule which sub-reading it should operate on and

Hi, Firstly, you should write to the CG mailing list instead of CC'ing us all - https://groups.

Latest nightly version of CG-3 has a couple of new features regarding deleted and delayed readings,

A new release of CG-3 has been tagged v1.3.0 (r13684), in preparation for the NoDaLiDa 2019

Second Call for Papers =============================================================================

============================================================================= CONSTRAINT GRAMMAR

Tino, in the following am I using the stream command correctly? So far, every way I've tried it

Robert Reynolds čálii: [...] > I found this github repo <https://github.com/ljos/pyvislcg3>

Yes, if you have a dependency tree grouping the noun phrase you can use Move WithChild https://visl.

Sorry, I incorrectly wrote "Prpers" and "Avea" instead of "prpers" and

And first update already: In the cohort recipe, * now means copy all the target cohort's tags to

Replied inline... On 24 January 2018 at 15:07, Edward Garrett <e.ga...@soas.ac.uk> wrote: can

Hi - I'd like to do something very boring. For every reading, I'd like to add a dependency

Dunno if you ever figured this out, but here are some solutions: First, you could just write two

The proceeding of this year's CG workshop, held in conjunctin with NoDaLiDa 2017 in Gothenburg,

Tino Didriksen <ma...@tinodidriksen.com> čálii: > Implemented in svn and latest nightly. ADD/

On 06/14/2017 01:24 PM, Tino Didriksen wrote: > - /__A__B__/l will match input tags ACDEB but not

Hello! I think feature attribute pairs should stay implicit in CG itself, as they are now, but they

Great! And one can always move on to STRICT-TAGS later, for grammars with a stable set of definitions

Hi Tino, it's nice to see that so much development is going on! I have made some minor additions

replied inline; sorry for possible confusion upcoming ... I can't think of a clean way to say all

With apologies for cross-postings: ==================================================================