<br />Dear Leonid and dear all, <br />I retake this conversation. The command was very useful. Nevertheless, we had another issue: In some our files we have different codes in the same dependent tier, and not in two different dependent tiers. In any case, the message indicating that there is a duplicate tier saves a lot of time, although we were wondering whether there is an easier way<b> to include or copy codes from a dependent tier in a file to the very same dependent tier in another file. </b><br />Has anyone find a way to do so? <br />Many thanks in advance, <br />--<br />Remei <br /><div class="gmail_quote"><div dir="auto" class="gmail_attr">El viernes, 10 de marzo de 2023 a las 14:25:34 UTC+1, Remei González Manzanero escribió:<br/></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Dear Leonid, <div>Thank you for your fast reply. We are going to try this and see how it works. </div><div>Thank you and best regards, </div><div>--</div><div>Remei</div><div><br><br></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">El miércoles, 8 de marzo de 2023 a las 20:06:09 UTC+1, Leonid Spektor escribió:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="line-break:after-white-space">Remei,<div><br></div><div><span style="white-space:pre"> </span>CLAN does not have a command specifically dedicated to merging files. But there is RELY command that will allow adding one file's dependent tiers to another file. The speaker tiers have to be identical and all present in both files. If there is the same dependent tier in both files then RELY will insert message " ** Duplicate tier found around lines: " in the output file. The last limitation is that you would have to do this merging just two files at the time.</div><div><br></div><div> Here is an example of the command line:</div><div><br></div><div>rely +a file1.cha file2.cha +t% +t@<br><div>
<div style="color:rgb(0,0,0);font-family:Arial;font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><br><br></div><div style="color:rgb(0,0,0);font-family:Arial;font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">Leonid.</div>
</div>
<div><br><blockquote type="cite"></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>On Mar 8, 2023, at 04:18, Remei González Manzanero <<a rel="nofollow">remeig...@gmail.com</a>> wrote:</div><br></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>Dear all, <br><br>We are trying to unify two files into one. In our corpora, we have two different files for each text, with the same speaker tiers but with different dependent tiers in each of them. Although we can carry out two analysis, we would like to unify these two versions of each text into only one. <br><br>We tried some commands, such as CHSTRING doing replacements, but we don't seem to find the right one. In other words, we need to integrate the dependent tiers of one file into the other, resulting in a file containing the dependent tiers of both files. <br><br>Thank you in advance for your help, <br>--<br>Remei González Manzanero<br><div><br></div></div></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>
-- <br>
You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a rel="nofollow">chibolts+u...@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/6b8895e0-d47a-4afb-a3e6-bac1850b15efn%40googlegroups.com?utm_medium=email&utm_source=footer" rel="nofollow" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=es&q=https://groups.google.com/d/msgid/chibolts/6b8895e0-d47a-4afb-a3e6-bac1850b15efn%2540googlegroups.com?utm_medium%3Demail%26utm_source%3Dfooter&source=gmail&ust=1679651070235000&usg=AOvVaw3qT95HBjODFaqL7djH5Miv">https://groups.google.com/d/msgid/chibolts/6b8895e0-d47a-4afb-a3e6-bac1850b15efn%40googlegroups.com</a>.<br>
</div></blockquote></div><br></div></div></blockquote></div></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "chibolts" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/ba63c7d3-082e-426e-a464-708dbd75d8ban%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/ba63c7d3-082e-426e-a464-708dbd75d8ban%40googlegroups.com</a>.<br />