-
Notifications
You must be signed in to change notification settings - Fork 2
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
Transcripts, captioning and translations #15
Comments
Awesome idea, but I think it was @buildmaster that helped out here, not me 😄. Would also be interested in doing this once we get the node.js meetups recorded in Welly. |
Nope you wrote the first few minutes, remember? From: https://www.youtube.com/watch?v=1iwfxFnvKIk&feature=youtu.be&t=720
:) On Thu, Oct 8, 2015 at 8:35 AM Alex Gibson notifications@github.com wrote:
|
That was definitely me. Scanning the video and transcribing definitely made me have a new appreciation for how hard it is. No objections at all to this, my only real concern is time. It's of course valuable but we don't have a huge pot of cash and I don't have a clue how much this would set us back in terms of time/money. Whatever we can do to help though we should. |
I thought it'd be an excellent idea to make sure we do transcripts of the society meetings and any other videos that we do.
I am in the process of doing a demonstration for the first society meeting (thanks for helping @PrototypeAlex) in which I'll upload the source and such to here.
Regarding why we would do this:
One major translation we could do is Māori, seeing we're in New Zealand!
My ulterior motive though, is to be able to demonstrate and perhaps even improve code for captioning for the main purpose of educating developers / video producers as to why it's something worth doing. At the moment it's almost an afterthought, if it is one at all. Videos are becoming much more popular, and there's an incredible amount of great information on them that so many will miss out on otherwise.
Does anyone have any objections of me doing this, or any advice/constructive feedback?
The text was updated successfully, but these errors were encountered: