-
Notifications
You must be signed in to change notification settings - Fork 49
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
Problem with changing <v speaker> to speaker: #61
Comments
Hi, thank you for the suggestions. At this point, I am trying to just support conversion between different formats without styles. And with limited time it would be too much work to add speaker support to all the converters and to properly test them. |
Thank you @mantas-done
|
Looking again at your issue. Your suggestion is actually very good. If you would be willing to implement storage of speakers in the internal_format, I would merge it. |
@mantas-done |
If you want, you can implement it just for vtt format at first.
I would suggest adding two additional array elements: speakers (as in your
example) and lines_without_speaker.
Vtt will be able to use those additional parameters. Other formats will use
what they are currently using. And later other formats can be also updated.
…On Tue, Aug 22, 2023, 18:07 vnali ***@***.***> wrote:
@mantas-done <https://github.com/mantas-done>
sure, I will take a look at the code to see if I can do it. I know how
speaker appears on the srt and vtt subtitles but is there any reference
about other formats?
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECVOJW3FX5KPMWEJBMTIMLXWTDKJANCNFSM6AAAAAAZPJOUUM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi.
First of all thank you for this very useful class,
I am trying to pass a vtt string with
<v speaker>
in it to this class and then add a new line to it and return vtt format again.the problem is vttConvertor changes
<v speaker>
to speaker: - in this case it should not, because i want the vtt format again -I have also a related suggestion/solution:
Maybe instead of changing the speaker and adding it to the body in
fileContentToInternalFormat
function, we should keep parsed speakers for each line in a new key in$internal_format
likeand decide later based on the destination format in
internalFormatToFileContent
function, how we want the speaker values in the body lines. -so in vttConverter we prepend it as to line[0] and on srtConverter we prepend it as speaker1:-Another good reason for this is some new formats like html subtitles or json subtitles have another separate tag for speaker value and they don't include the speaker in the body lines at all.
The text was updated successfully, but these errors were encountered: