<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><font face="Calibri">Dear Eline and all,<br>
        <br>
        As far as I can see, GRAID annotations would be mostly
        word-level annotations (not sentence-level), and FLEx only
        supports sentence-level custom tiers so far. Importing any kind
        of word analysis is very tricky (and not supported by FLEx
        itself as of now).<br>
        We're trying to import glosses but that's relying on the
        information stored in the lexicon (so we have to update the
        lexicon and also the word analyses). While annotations like
        grammatical functions or information status do not belong to the
        lexicon, they would need to be stored as "word glosses" in FLEx,
        and you'd probably need some extra writing systems to simulate
        extra word-level tiers.<br>
        An alternative would be to keep GRAID annotations in ELAN and
        merge them with the glossing when you're done with the rest of
        analysis in FLEx.</font></p>
    <font face="Calibri">Best,<br>
      Sasha<br>
    </font>
    <p></p>
    <div class="moz-cite-prefix">20/01/2023 10:07, Eline Visser пишет:<br>
    </div>
    <blockquote type="cite"
cite="mid:DrgBUc6nlaX-1jjIKWwuPqlaC0YpdMlOdBsLU72IbDvG_TLINmiHaIz4vxr2X_Cp2Z3Exk7ZTUVU3nFBoZFCetm4JcQroJewsy4DX-CPNWc=@pm.me">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div style="font-family: Arial; font-size: 14px;">Hi Alexander,</div>
      <div style="font-family: Arial; font-size: 14px;"><br>
      </div>
      <div style="font-family: Arial; font-size: 14px;">There are two
        things I'd like to do that require a second pass through FLEx:</div>
      <div style="font-family: Arial; font-size: 14px;"><br>
      </div>
      <div style="font-family: Arial; font-size: 14px;">
        <ol>
          <li><span>Add GRAID annotations in ELAN (<span><a
                  target="_blank" rel="noreferrer nofollow noopener"
                  href="https://core.ac.uk/display/144520140"
                  moz-do-not-send="true" class="moz-txt-link-freetext">https://core.ac.uk/display/144520140</a></span>),
              then continue/improve glossing in FLEx.<br>
            </span></li>
          <li><span>Improve transcriptions and translations during a
              second field trip in ELAN, then regloss in FLEx.<br>
            </span></li>
        </ol>
      </div>
      <div style="font-family: Arial; font-size: 14px;"><br>
      </div>
      <div style="font-family: Arial; font-size: 14px;">Eline<br>
      </div>
      <div class="protonmail_signature_block
        protonmail_signature_block-empty" style="font-family: Arial;
        font-size: 14px;">
        <div class="protonmail_signature_block-user
          protonmail_signature_block-empty"> </div>
        <div class="protonmail_signature_block-proton
          protonmail_signature_block-empty"> </div>
      </div>
      <div style="font-family: Arial; font-size: 14px;"><br>
      </div>
      <div class="protonmail_quote"> ------- Original Message -------<br>
        On Thursday, January 19th, 2023 at 8:24 PM, Alexander Rice
        <a class="moz-txt-link-rfc2396E" href="mailto:ax.h.rice@gmail.com"><ax.h.rice@gmail.com></a> wrote:<br>
        <br>
        <blockquote class="protonmail_quote" type="cite">
          <div dir="ltr">
            <div>Eline,</div>
            <div><br>
            </div>
            <div>I'm curious what it is you want to do, that requires a
              second pass through FLEx.</div>
            <div><br>
            </div>
            <div>I've had to think about this with my work, since some
              of my recordings are conversations, which FLEx doesn't
              handle very well, so generally I just have a separate EAF
              file per speaker, tag and gloss each separately in FLEx,
              then merge all of them together in a single ELAN file with
              the 'merge transcription' function. That ensures that any
              extra tiers you have that FLEx may ignore make into the
              final ELAN file.</div>
          </div>
          <br>
          <div class="gmail_quote">
            <div class="gmail_attr" dir="ltr">On Tue, Jan 17, 2023 at
              2:02 AM Eline Visser <<a href="mailto:eelienu@pm.me"
                rel="noreferrer nofollow noopener" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">eelienu@pm.me</a>>
              wrote:<br>
            </div>
            <blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px
              solid rgb(204,204,204);padding-left:1ex"
              class="gmail_quote">
              <div style="font-family:Arial;font-size:14px">Hi,</div>
              <div style="font-family:Arial;font-size:14px"><br>
              </div>
              <div style="font-family:Arial;font-size:14px">Has anyone
                hacked ELAN and FLEx yet so that one can go back and
                forth between the two programmes without losing
                annotations? Afaik one can go from ELAN to FLEx and back
                to ELAN, but not a second time to FLEx. There is a
                manual that involves a tier-renaming script at <span><a
                    target="_blank"
href="https://hughp.gitbooks.io/the-flex-anti-manual/content/chapter8.html"
                    rel="noreferrer nofollow noopener"
                    moz-do-not-send="true" class="moz-txt-link-freetext">https://hughp.gitbooks.io/the-flex-anti-manual/content/chapter8.html</a></span>,
                but I can't make it work. Is there a more fool-proof way
                yet?</div>
              <div style="font-family:Arial;font-size:14px"><br>
              </div>
              <div style="font-family:Arial;font-size:14px">Eline Visser<br>
              </div>
              <div style="font-family:Arial;font-size:14px">
                <div> </div>
              </div>
              _______________________________________________<br>
              Lingtyp mailing list<br>
              <a target="_blank"
                href="mailto:Lingtyp@listserv.linguistlist.org"
                rel="noreferrer nofollow noopener"
                moz-do-not-send="true" class="moz-txt-link-freetext">Lingtyp@listserv.linguistlist.org</a><br>
              <a target="_blank" rel="noreferrer nofollow noopener"
href="https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp"
                moz-do-not-send="true" class="moz-txt-link-freetext">https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp</a><br>
            </blockquote>
          </div>
        </blockquote>
        <br>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Lingtyp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lingtyp@listserv.linguistlist.org">Lingtyp@listserv.linguistlist.org</a>
<a class="moz-txt-link-freetext" href="https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp">https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp</a>
</pre>
    </blockquote>
  </body>
</html>