Skip to content
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

replace ttm:role by daptm:scriptType #85

Merged
merged 1 commit into from
Dec 6, 2022
Merged

replace ttm:role by daptm:scriptType #85

merged 1 commit into from
Dec 6, 2022

Conversation

cconcolato
Copy link
Contributor

@cconcolato cconcolato commented Dec 2, 2022

close #24
close #32
close #33
close #54


Preview | Diff

Copy link
Contributor

@nigelmegitt nigelmegitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Can open an issue for my comment, or deal with it now, either way happy to merge.

Comment on lines +353 to +354
: "DUBBING_ORIGINAL_DIALOGUE_LIST"
| "DUBBING_TRANSLATED_DIALOGUE_LIST"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at these values, the suffix _LIST looks out of place. And since we're now being explicit about it possibly containing on screen text as well as dialogue, the DIALOGUE bit looks odd too. Happy to open as a separate issue, but I'm leaning towards just ORIGINAL_TRANSCRIPT and TRANSLATED_TRANSCRIPT, partly because I think they are clearer and also because I suspect they are likely to be more generally useful beyond just dubbing workflows.

I'd keep DUBBING_PRE_RECORDED and DUBBING_AS_RECORDED as they are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment