kwal query

[Cathy Lonngren]

Dear Leonid and Brian,
 Thank you both for your answers. Leonid, following the command lines you
suggested I get the output I want (I just need to check in the manual to
understand how the +d3 switch works as that seems to be the key for the
first option). Brian, as my intention is to submit my corpus (presently
about 30 hours of longitudinal data of two bilingual children) as I near the
end of my PhD (still a few years away) I will carry out tests on a sample
from the Yip/Matthews corpus to see how I get on with the method you
suggest. Any queries and I'll bother you again.
Thanks once again,
Cathy

On Mon, Sep 8, 2008 at 6:34 PM, Brian MacWhinney <macw at cmu.edu> wrote:

>
> Dear Cathy,
>    I would like to add a bit to Leonid's reply.  Leonid showed you
> how to get the results you want, using the codes you are using.  My
> examples point instead in the direction of using newer methods for
> coding bilingual files.  If you don't want to do additional work on
> your files and don't want to contribute them to the database, you will
> probably want to stick with the older format and Leonid's
> suggestions.  However, if you want to redo your database to conform to
> the new guidelines, then you will want to make changes.  These
> principles are well illustrated in the YipMatthews corpus and
> elsewhere.  They are:
> 1.  The @Languages header tier lists the languages in the order for
> the transcript.  If English is primary, the order should be en, pt
> 2.  It is then not necessary to mark individual words as @en or @pt.
> All sentences are assumed to be English and Portuguese words in
> English sentences are marked as @s.
> 3.  However, precodes can be used to mark whole individual sentences
> as Portuguese.  The code is [- pt] and it is placed right at the
> beginning of the utterance.  In that case, the meaning of @s changes
> and becomes English inside Portuguese.
> 4.  If the transcript is primarily Portuguese, all of the above is
> reversed.
>
> --Brian MacWhinney
>
> On Sep 8, 2008, at 9:03 AM, Cathy Lonngren wrote:
>
> > Despite lots of attempts and experiments I am having problems
> > getting the output I want when using KWAL on my bilingual files.
> > Coded using <....>[@en] and <....[@pt] to separate the languages,
> > when I use FREQ to get word lists using the following command line I
> > get the output I desire i.e. the program performs analysis on only
> > the Portuguese or English material of a particular speaker
> > (e.g.JAM):  freq @ +t*JAM +s"<@pt>"  (gives me the Portuguese JAM
> > uses) and freq @ +t*JAM +s"<@en>" (gives me the English he uses).
> > These results indicate that my codes work. However, when I use KWAL
> > in a similar way the program does not give me the lines with just
> > the Portuguese or just the English, no matter which of the following
> > command lines I use. With all these commands I get the same results
> > (i.e all of JAM's utterances with no selection or exclusion being
> > performed):    kwal @ +t*JAM +s"<@pt>"      kwal @ +t*JAM
> > +s"<@en>"    kwal @ +t*JAM -s"<@en>"    Kwal @ +t*JAM -s"<@pt>"
> >
> > Three years ago I was able to use these commands and get the results
> > I wanted. I have the latest version of CLAN installed and am
> > thinking that something might have changed but if FREQ can
> > understand my codes why can't KWAL. I hope that there is something
> > simple I'm missing so I would appreciate any help. I've got an short
> > example file I can send for testing.
> >
> > Thank you,
> >
> > Cathy
> >
> > Cathy Lonngren Sampaio
> > University of Hertfordshire
> > England
> >
> > >
>
>
>  >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "chibolts" group.
To post to this group, send email to chibolts at googlegroups.com
To unsubscribe from this group, send email to chibolts+unsubscribe at googlegroups.com
For more options, visit this group at http://groups.google.com/group/chibolts?hl=en
-~----------~----~----~----~------~----~------~--~---

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/chibolts/attachments/20080908/65cf4fb7/attachment.htm>