Comments on: Version 1 – Notes,Bugs,Requests

By: Reem Hora

Reem Hora — Wed, 25 May 2011 00:04:00 +0000

When I saw your page was like wow. Thanks for putting your effort in publishing this site.

By: Eva I. Siegel

Eva I. Siegel — Sat, 21 May 2011 20:55:31 +0000

An interesting discussion is worth comment. I feel that you need to write extra on this matter, it won’t be a taboo subject but generally persons are not enough to speak on such topics. To the next. Cheers

By: Feri

Feri — Fri, 13 May 2011 09:20:48 +0000

Hi,
Really like the site, very easy to use. I have one remark: why doesn’t it uses UTF-8 as export coding? I wanted to add accented characters, and after export I had to redo the copy and paste because of it…

By: resan

resan — Wed, 06 Apr 2011 11:18:23 +0000

this is actually the fifth time i go through the site, good post as usually! all the best, resan

By: Reynaldo Grudem

Reynaldo Grudem — Thu, 13 Jan 2011 16:53:32 +0000

Site visitors Mayhem Review- the content articles on this post is really a single of the most effective substance that i?ve truly are out there throughout. I really like your article, I will are accessible again to confirm for new posts.

By: antek

antek — Tue, 28 Dec 2010 09:15:04 +0000

Hallo
its possible to export capions with polish signs?
best regards

By: Delmar Kaea

Delmar Kaea — Sat, 27 Nov 2010 14:34:32 +0000

It sounds interesting as far as I read , but if anyone could translate this to Italian, it would be so good for me to get the idea better

By: Ken

Ken — Fri, 03 Apr 2009 16:43:13 +0000

Hi Gabriel,

RE: two line captions: Often it’s the case where there are brief interchanges between speakers and you want something like:

Jim: Hi.
Bill: Howdy, Jim.

And you don’t want it broken over two pop-ons because readability is negatively affected.

Also, when you have relatively long spoken instances, it is a plus for usability/readability if you can control line breaks, so that each line is semantically complete within a single pop-on/chunk–your not splitting infinitives, ending lines with prepositions, etc.

I experimented and YouTube is not supporting either hard returns or [br] (or any variant) within the SubViewer file to produce a manual break.

However, if you use SubRip instead, hard line breaks are accepted. I urge you to consider going with SubRip over Subviewer–the syntax is very close and it shouldn’t be a big change in terms of your backend.

If you try this, in Subviewer:

00:00:02.23
Jim: Hi.
Bill: Howdy, Jim.

YouTube sticks it all on one line. But with SubRip:

3
00:00:02,23 –> 00:00:04,34
Jim: Hi.
Bill: Howdy, Jim.

YouTube will accept and properly render out the break. For the end user, the effect is preferable.

Cheers,
k

By: gabrielm

gabrielm — Wed, 01 Apr 2009 19:48:42 +0000

@Ken,
I have updates in the works that should be live later this week. Specifically, I have been working on the loop – since, as you say, it really is needed to be practical. The code will also be cleaned up and optimized.

And for the specifics:
1. I agree. This will be an option soon.

2. Two line captions? Why not just split it into 2 sequential captions? YouTube will automagically break long captions into multiple lines. Maybe I am missing the intention…

I did not know about ‘accessify’, but it looks like a good alternative to magpie. However, I think we can still do better My goal is to make captioning so easy that people won’t have an excuse.

By: gabrielm

gabrielm — Wed, 01 Apr 2009 19:39:18 +0000

@Melany,
When in the video focus, you can use the standard youtube access keys. For instance “spacebar” should pause/play.

However, it would also be nice to be able to pause play while editing the grid. I will add “universal access keys” to the list. Thanks!