-
Notifications
You must be signed in to change notification settings - Fork 12
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
Annotated sentences improvements #1234
Comments
The text fields for the translations seem to allow a limited number of characters. Can we expand it? I believe it might be 200 characters now, I'd like it to be 300. |
It should be possible for us to upload multiple sentences under one gloss. |
@uklomp Uploading multiple sentences under one gloss is already possible, or what do you mean? |
Ah, sorry! You're right! Ignore this. Another point: what did we decide again on the left hand glosses? When there's overlap, only the right hand is selected, but otherwise the left hand is also included? |
Yes, all glosses from the right hand tier are added and only those from the left hand tier if they don't have overlap with a gloss on the right hand tier |
Improvements for editing annotated sentences issue #1234
This is deployed on signbank and on signbank-dev |
@uklomp it's always tricky when sometimes it works and sometimes not, haha. Until I find out why this happens, it should help to just refresh the page when it does not work. I don't think it is related to your update. |
Refreshing doesn't work. Uploading it again also doesn't work. I can send you an email with two .eafs that I could upload today and two that I couldn't, maybe you can spot the difference? |
Yes please do! |
Thanks for the files, that really helped to debug this. It looks like the error was caused by a "_" that should have been "__" in my code... anyway I hope this solves it! |
@Jetske are you able to add the gettext to the feedback so that it will be added to the PO files for translation? (Eventually.) |
Ok, I will try again soon. I have a new request (please let me know if you want me to make separate issues for these things, now or in the future); And a question: I see that there's a field now, where I think it is possible to say something about the corpus / source, was it the idea that we put the link there? And should we do this manually for now, or were you maybe still looking into a way to do this automatically? |
.eaf 43 and 72 still don't really upload so I'm afraid the bug isn't solved yet! |
Zou het mogelijk zijn om de video, als die is geupload, nog links of rechts in te korten met een soort crop-functie? Ik kan me voorstellen dat dit ingewikkeld is maar ik vraag het toch maar even. |
@uklomp the changes are not online yet :) when it's gone from the pull requests you can try again. For new requests, please make a separate issue with some priority tag. Problems encountered afterwards can be added to the existing issue (like the bug you found here). Yes the corpus field was meant to add the corpus name or a link to the corpus. I wouldn't know how to add it automatically but if you have ideas about that let me know! For the question about cropping: I'll look into it a little bit but I think it is difficult to implement. |
For annotated sentences a difficulty with cropping is also that the annotations each have a start and end time. This would need to be adjusted when cropping from the beginning of a video. That's possible, just not very efficient maybe. |
Annotated sentence improvements #1234
This is live on master. |
Fix for other temporary file types #1234
I'm getting this warning after the new updates:
Maybe this function is needed in the Signbank Python files instead? |
@susanodd Any idea which function it occurred in? |
No idea. It was just a general run. It looks like print statement is in the frequency.py file. (Which is really old.) |
Yeah I think that it's unrelated to the new code |
I'm able to upload the files that I couldn't upload before, so that's great. I made a new issue for the source things. As for the cropping: you mean that we crop the video live on signbank, but then the .eaf-file doesn't fit anymore, right? So we would need to adjust the .eaf again. Maybe we make it ourselves a bit more easy and only crop in between sign boundaries. This would already be helpful because one of the common reasons to crop is that the video starts halfway a certain sign, that we don't need to include anyway. So then we just delete this gloss and crop the video online? |
@uklomp the cropping functionality crops both the video and eaffile, cutting out irrelevant annotations. Then I believe this issue can be closed. Other changes are still to be done in other issues. |
The following edits will be made:
The text was updated successfully, but these errors were encountered: