-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
translate glossary #290
translate glossary #290
Conversation
For example, if you want to evaluate a region segmentation algorithm, you need evaluation data with regions annotated. If you want to evaluate a word-based post-correction tool, you need word-level annotations etc.
Yes, these are "Kustoden" in German. For once, the german word is prettier (i.e. a word that "guards" against messing up the "Lagen" of the print) :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very thorough, thank you @lena-hinrichsen. Since the glossary is part of the specs, we need to add it there as well, once review is finished.
Co-authored-by: Konstantin Baierer <kba@users.noreply.github.com>
new description Evaluation data (mostly provided by @tboenig )
superseded by #291 |
Translation Glossary eng > ger
I changed the order and also changed minor stuff when I noticed something odd in the original english glossary. I didn't make changes in the english glossary, yet. I would adapt the changes there later, as soon as we merged this PR (and maybe discussed before).
There are also a few things where I'm not sure or which I either don't understand or like:
It would be helpful if you could have a look at it and tell me if it still makes sense. I also tried to be logical in what to translate and what not to translate but feedback regarding that is also appreciated.