Home Forums Software ELAN Languages in .ecv

Languages in .ecv

Tagged: , ,

This topic contains 3 replies, has 2 voices, and was last updated by  Han 4 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
Author Posts
Author Posts
January 17, 2018 at 16:14 #11836

c_borstell

I am trying to create an .ecv that encompasses several annotation standards for Swedish Sign Language that are mapped to each other (1. dictionary ID, 2. dictionary glosses, 3. corpus glosses).

If I’ve understood it correctly, I can only attain this by creating a multilingual .ecv, which I have now done by writing a custom XML file based on a dictionary matching between 1,2,3. However, it seems that this requires me to use valid language iso codes and names in order to get this to work. That is, if I let 1=eng,2=nld,3=swe, ELAN recognizes these and I can happily shift between the standards by changing the language view; it does not work, however, if I use made-up language names (which would be an advantage for non-language dictionaries). Is this correct or am I doing something wrong?

January 19, 2018 at 17:26 #11842

Han

I never tried this actually, but if you say it doesn’t work, it probably doesn’t. The schema of EAF and ECV does allow other language names than iso language code, for the reason that it should be possible to use language identifiers that are not (yet) part of the ISO standard.
But maybe here or there in the user interface of ELAN and/or in some of the functions of ELAN, only the list of iso languages is used or allowed. I don’t know.

So, what actually happens if you use made up names, where does it go wrong? Can you still switch to such a ‘language’ in the Options menu or not even that?
Any messages in the log (View->View Log…)?

January 25, 2018 at 14:20 #11854

c_borstell

When I tried to use novel language names/codes, they did show up in the list of language choices in the Elan toolbar, but the Edit Controlled Vocabulary window did not recognize them and would not display them as a multilingual dictionary in separate columns. It’s possible that this was due to some error in my attempt to write the XML for the .ecv from scratch (and edited .eafs) based on fragments of other .ecv/.eaf files with similar features.

January 26, 2018 at 09:48 #11857

Han

I would have to check that in the code, maybe the Edit Controlled Vocabulary window performs different checks or applies different rules, which would be an inconsistency we should probably try to remove.

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

You must be logged in to reply to this topic.