<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, May 19, 2017 at 7:15 AM, Stefan Evert <span dir="ltr"><<a href="mailto:stefanML@collocations.de" target="_blank">stefanML@collocations.de</a>></span> wrote:</div><div class="gmail_quote"><br></div><div class="gmail_quote">Thanks again, Stefan.</div><div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No, my logic was quite simple: If there's a missing </text> tag in one of your files, this region isn't closed and will extend to the very end of the corpus (unless there is a superfluous </text> tag or a damaged <text> in another file). So there was a good change that the last <text> region in the corpus would be the critical one.<br></blockquote><div><br></div><div>Right on.</div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What you want is<br>
<br>
set PrintStructures text_id;<br></blockquote><div><br></div><div>Extremely useful command, this!</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">One of the advantages of -S text:0 is that it shows you there is a problem – with the "hotfix" solution, it's completely hidden.<br></blockquote></div><div class="gmail_extra"><br></div>Indeed. Fortunately, with the <font face="monospace, monospace">set PrintStructures</font> command I was able to ferret out what I hope is the last bad tag in the corpus, and I'm currently re-encoding using <font face="monospace, monospace">-S text:0</font>.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for all your help.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra">Scott</div></div>