You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user should be able to compare different orthographies for the same corpus, and see the translations side-by-side (or underneath) the target language.
In Korp, this is achieved with the "Parallel Corpora" feature. This isn't really about "parallel corpora"; it's more about side-by-side displays of different views of the same set of data. However, in order to accomplish this, the data do in fact have to be encoded as distinct corpora.
Potential Solutions
Display translation and alternative orthographies in the Info Box. This seems less than ideal, because it requires the user to click on each token they'd like to see translations / other orthographies for.
Korp's Parallel Corpora feature. This would require a process for encoding the same database in different ways, so it would complicate the text import pipeline and maintenance.
Allow the user to choose which orthography / orthographies the data are displayed in. Potentially allow the user to see interlinearized data.
The text was updated successfully, but these errors were encountered:
The user should be able to compare different orthographies for the same corpus, and see the translations side-by-side (or underneath) the target language.
In Korp, this is achieved with the "Parallel Corpora" feature. This isn't really about "parallel corpora"; it's more about side-by-side displays of different views of the same set of data. However, in order to accomplish this, the data do in fact have to be encoded as distinct corpora.
Potential Solutions
Display translation and alternative orthographies in the Info Box. This seems less than ideal, because it requires the user to click on each token they'd like to see translations / other orthographies for.
Korp's Parallel Corpora feature. This would require a process for encoding the same database in different ways, so it would complicate the text import pipeline and maintenance.
Allow the user to choose which orthography / orthographies the data are displayed in. Potentially allow the user to see interlinearized data.
The text was updated successfully, but these errors were encountered: