OGM: <font> tags in SRT doesn't work while <i> does work

[Liisachan]

I'd like to know how I can use <font> tags in SRT muxed in an ogg media file successfully.

<font> is one of the "Supported HTML tags," listed in
http://tobias.everwicked.com/subtit.htm
and DirectVobSub does support "the defined html tags in embedded OGM subtitles" as you can read in http://vobsub.edensrising.com/vobsub.php
(under the list titled "VobSub 2.16")

Indeed <i> tags are supported and will be parsed correctly
(i.e. making the "<i>-element" italic),
while <font> tags are not working fine for me, but just rendered as if they were a part of sub-texts.

(SAMPLE SRT)
1
00:00:01,000 --> 00:00:02,000
test

2
00:00:02,500 --> 00:00:10,000
You can complain because <font size="5">roses</font> have <font size=5>thorns</font>, or you can rejoice because <i>thorns</i> have roses.

(EOD)

In this case, <i>thorns</i> does work, while <font> does not work for me
nor for my friend who s using different language version of windows,
no matter whether or not I quote the value ("5" in this sample).
This picture shows what we see:
http://space34.tripod.co.jp/sample.jpg
http://space34.tripod.co.jp/sample.png

Please observe that <i> tags do work.
what's embarrassing is that you can read "<font>" as a string in subtitle.
The similar happens for <font color="..."> or <font face="...">
This sample OGM is zipped in
http://space34.tripod.co.jp/sample.zip
I ll attach it here too

My friend and I tried this sample file in:
- Windows 2000 Japanese version
- Windows 2000 Finnish version
- System Language = "Western Europe and United States" / "Japanese" / "Finnish"
- Locale = "English (US)" / "Japanese" / "Finland"

<font> tags in SRT don't work correctly for any combination of those so far....

I tried both GraphEdit and OggMux.
Possibly you dont have this problems in Windows English version.
Or probably I did something improper when I use tags in srt,
since I can mux OGMs without tags in SRT(s) without problem...

[Liisachan]

additional reports:

1) if you uninstall VobSub, then SubTitDS will handle
<font> tags to some extent, tho not being practical.

2) i ve just tried the newest version vobsub 2.22,
which however doesn't fix this problem....:(

I'd appreciate it if anyone of you would give me
any suggestions or hints. tyia

[Schultz]

I belive when gabest initially added support for Html comands in srt subs Tobias didn't have Support for <font> tag and that was added in a more recent build of Subtitds and so gabest hasn't updated his support for it.

[Liisachan]

thanks for reply, it s sad news:(
it seems that OGM has a long way to go
or, rather,
the fact that something like "you cant use it becase 'someone' doesnt do that" is possible is sad.:(
that s when I realize the MCF philosophy is really reasonable

how i wish there were this kind of specifications for Ogg too:
http://mcf.sourceforge.net/docbook/spec.html#0x11

i feel sad all the more because i want to support OGM

[ChristianHJW]

Originally posted by Liisachan that s when I realize the MCF philosophy is really reasonable

I probably shouldnt reply here, but here i am, sorry. And yes, an opensource project has always advantages here as anybody could make these changes and easily compile a new, improved version of the mcfparser.

Tobias' approach is very effective, he doesnt have to discuss a lot with other users, he simply does things the way he wants them to do, and its incredible what his format has achieved to become in such a short time, and with only one developer behind the basic format.

An opensource project like MCF wastes a lot of time in endless discussions, people get pissed, leave the team ( like happening recently with MCF ), etc. ... all very human ;) !!

But at the end you have something thats belonging to everybody, not just to one person who is granting you allowance to use it .... thats the beauty of making it open source !!


how i wish there were this kind of specifications for Ogg too:
http://mcf.sourceforge.net/docbook/spec.html#0x11

Actually, we are planning to drop this specs completely in favour of something much more powerful and exciting until MCF-1 release :D .. stay tuned !

i feel sad all the more because i want to support OGM

Well basically, as the OGM format structure is known by now and has been implemented on both Linux and in VirtualdubMod it should be possible to rewrite Tobias' Dshow filters in an opensource project ? Maybe a stupid idea, but certainly feasible ...

On the other hand we have to admit that Tobias has fixed all existing bugs in his filter over time, so maybe all you have to do is to be patient for some more time and it will work fine in the end.

If you feel like helping MCF a bit to become reality in the meantime you are of course more than welcome my friend, especially if you have some good background on subtitles, with respect to the upcoming changes .. :) !

[Schultz]

Originally posted by Liisachan
thanks for reply, it s sad news:(
it seems that OGM has a long way to go
or, rather,
the fact that something like "you cant use it becase 'someone' doesnt do that" is possible is sad.:(
that s when I realize the MCF philosophy is really reasonable

how i wish there were this kind of specifications for Ogg too:
http://mcf.sourceforge.net/docbook/spec.html#0x11

i feel sad all the more because i want to support OGM

Well the one thing is Srt don't natively support html attributes in them.. This was added by Tobias for his use with Ogm and he just recently added this to the list of elements that are supported.. I am sure if gabest actually read that the font tag is now used he would support it in DVobSub.