[nut]: r581 - docs/nut.txt
Author: michael Date: Mon Feb 4 23:40:57 2008 New Revision: 581 Log: Dependancy info. Modified: docs/nut.txt Modified: docs/nut.txt ============================================================================== --- docs/nut.txt (original) +++ docs/nut.txt Mon Feb 4 23:40:57 2008 @@ -886,6 +886,17 @@ info packet types This stream is a superior alternative (higher resolution or otherwise) of the given stream. It should be preferred if the decoder is capable of decoding it. + "Depends" + v (stream id) + This stream depends on the specified stream. That is if its + unavailable then this stream cannot be decoded. This is used to store + dependancies for scalability for example. + "Uses" + v (stream id) + This stream can use the specified stream. But its existence is not + mandatory for decoding this stream. Although if its unavailable + quality might suffer. Examples are font attachments or higher quality + samples from music instruments. "UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?
On Mon, Feb 04, 2008 at 11:40:58PM +0100, michael wrote:
"UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?
Unrelated to this commit, but regarding fonts, FYI there is a unique identifier inside TrueType/OpenType fonts, usually generated randomly by the software writing the font. However font names may be adequate. I don't know if the APIs provide any easy way to lookup a font by its unique identifier and if it's only 32bit a name might have lower probability of collisions (i.e. P(some random luser-installed font collides with any standard font)). Rich P.S. Does anyone really envision Times New Roman being used for subtitles? EEW! :)
On Mon, Feb 04, 2008 at 05:49:24PM -0500, Rich Felker wrote:
On Mon, Feb 04, 2008 at 11:40:58PM +0100, michael wrote:
"UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?
Unrelated to this commit, but regarding fonts, FYI there is a unique identifier inside TrueType/OpenType fonts, usually generated randomly by the software writing the font. However font names may be adequate.
hmm, so "Arial" on win32 will have a different one than on macos ? [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No human being will ever know the Truth, for even if they happen to say it by chance, they would not even known they had done so. -- Xenophanes
Michael Niedermayer wrote:
On Mon, Feb 04, 2008 at 05:49:24PM -0500, Rich Felker wrote:
On Mon, Feb 04, 2008 at 11:40:58PM +0100, michael wrote:
"UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?
Unrelated to this commit, but regarding fonts, FYI there is a unique identifier inside TrueType/OpenType fonts, usually generated randomly by the software writing the font. However font names may be adequate.
hmm, so "Arial" on win32 will have a different one than on macos ?
Pretty much, still would be better use the font family so people with saner replacements can use their superior fonts instead the ugly ones... lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero
On Tue, Feb 05, 2008 at 12:01:13PM +0100, Luca Barbato wrote:
Michael Niedermayer wrote:
On Mon, Feb 04, 2008 at 05:49:24PM -0500, Rich Felker wrote:
On Mon, Feb 04, 2008 at 11:40:58PM +0100, michael wrote:
"UsesFont" "Times New Roman", "Arial", ... FIXME should we use the filename instead? is there some other unique way to identify fonts?
Unrelated to this commit, but regarding fonts, FYI there is a unique identifier inside TrueType/OpenType fonts, usually generated randomly by the software writing the font. However font names may be adequate.
hmm, so "Arial" on win32 will have a different one than on macos ?
Pretty much, still would be better use the font family so people with saner replacements can use their superior fonts instead the ugly ones...
I doubt a subtitle decoder will use a tag from the container to decide which font(s) to use. The tag is more intended to keep track of dependancies without having to look into codec specific data. Like for example in the case of an application deciding what fonts to include in an uploaded file. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle
participants (4)
-
Luca Barbato -
michael -
Michael Niedermayer -
Rich Felker