Home Forums Software ELAN Translation issues, multilingual ECV

Translation issues, multilingual ECV

This topic contains 1 reply, has 2 voices, and was last updated by  Han 1 year ago.

Viewing 2 posts - 1 through 2 (of 2 total)
Author Posts
Author Posts
January 25, 2018 at 15:11 #11855


I managed to write an .ecv with different annotation conventions as the “languages” of the multilingual setting. However, I encounter two problems when applying this .ecv to .eaf files that have already been annotated using the values of one “language” but from an internal CV:

1. Some files do not seem to automatically switch between the language options, even though all values are in the .ecv and all the .eaf files have been updated with “CVE_REF” set to the correct CVE_ID in the .ecv (all entries have unique ids). I can’t seem to figure out why this is the case, as some files happily toggle between the languages, others are fixed (and the default language setting for the tiers and tier types are identical across files).

2. Some values in one language A correspond to the same value in language B, but these have still been assigned separate CVE_ID numbers in the .ecv, for example:


However, if the .eaf file allows toggling between the languages (see point 1 above), such that XXX–>n/a and ZZZ–>n/a when changing from language A to B, it seems such values do not return to their unique values when going from language B to A. It is as if the conversion between the languages is done partly on the annotation values rather than the CVE_REF link to the .ecv CVE_ID. Is this the case?

January 26, 2018 at 09:54 #11858


This I would also have to check in the code, but I would be surprised if the switching between languages is sometimes based on values rather than CVE_ID’s.

If you could share with me your .ecv file and one eaf file in which the toggling doesn’t work, that would be helpful in figuring out what is going on. You could send it to (han.sloetjes AT mpi.nl).

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.