While I obviously like EOPAS as a model for corpus presentation (see the earlier blog post about it here), I found a renewed enthusiasm for it today as I was checking the meaning of a word in a text I was translating from South Efate. The word lunak does not appear in any of my notes nor in the dictionary, but appears a few times in a story told by the late Kalsarap Namaf. I wrote to Joel Kalpram, who is from Erakor village and speaks the language, and asked him if he knew the word.
He did not, and his requests to other speakers suggest that lunak is an archaic form not known to current speakers. He wanted to know the context so I found the section of text it came from, saved it as an XML file in the form exported by Toolbox (see below for an example), and uploaded it with validation into EOPAS. The media file it referenced was already in EOPAS and had been transcoded to the format needed for streaming, so the media references in the file were resolved immediately. So, within about ten minutes I had a citable, playable form of the interlinear text available to send Joel. See it here http://www.eopas.org/transcripts/178#t=1003.0,1009.6.
Any text that is prepared in Toolbox or Fieldworks and that has media references should be playable in EOPAS.
This is the form of Toolbox XML output that is accepted by EOPAS:
[…] <aud>NT1-98001-B 1011.6600 1018.9601</aud>
<txGroup>
<tx>Elunak</tx>
<mr>Elunak</mr>
<mg>p.name</mg>
</txGroup>
<txGroup>
<tx>ne</tx>
<mr>ne</mr>
<mg>this</mg>
</txGroup>
<txGroup>
<tx>Trawot</tx>
<mr>Trawot</mr>
<mg>p.name</mg>
</txGroup>
<txGroup>
<tx>kin</tx>
<mr>kin</mr>
<mg>REL</mg>
</txGroup>
<txGroup>
<tx>ito</tx>
<mr>i=</mr>
<mg>3S.RS=</mg>
<mr>to</mr>
<mg>PROG</mg>
</txGroup>
<txGroup>
<tx>lunak</tx>
<mr>lunak</mr>
<mg>??</mg>
</txGroup>
<txGroup>
<tx>natam̃ol.</tx>
<mr>natam̃ol</mr>
<mg>person</mg>
</txGroup>
<fg>Elunak is where Trawot would [lunak??] people.</fg>
[…]
Follow
A video guide to using EOPAS:
A video guide to getting your own texts into EOPAS: