On 2020-10-01 10:50, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 01:03 PM, Jim DeLaHunt wrote:
On 2020-10-01 06:27, Mark Filipak (ffmpeg) wrote:
On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:
On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:
Continuing with relatively non controversial entries:
d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
binary metadata:
720 samples/row: 'horizontal_size_value' = 0010 1101 0000
'horizontal_size_extension' = 00
480 rows: 'vertical_size_value' = 0001 1110 0000
'vertical_size_extension' = 00
4:3 DAR: 'aspect_ratio_information' = 0010
30/1.001 FPS: 'frame_rate_code' = 0100
'progressive_sequence' = 0 & 'progressive_frame' = 0
d-PAL [noun]: 1, The digital equivalent of PAL distinguished by
binary
metadata:
720 samples/row: 'horizontal_size_value' = 0010 1101 0000
'horizontal_size_extension' = 00
576 rows: 'vertical_size_value' = 0010 0100 0000
'vertical_size_extension' = 00
4:3 DAR: 'aspect_ratio_information' = 0010
25 FPS: 'frame_rate_code' = 0011
'progressive_sequence' = 0 & 'progressive_frame' = 0
It seems to me that these are no longer glossary entries — or, only
the first line of each is a glossary entry. ...
…The sentence is a statement followed by a list of metadata that
distinguishes the subject...
Do you have any suggestions? Should I just forget this glossary idea?
What makes sense to me is a glossary which includes the entries:
d-NTSC [noun]: 1, The digital equivalent of NTSC
d-PAL [noun]: 1, The digital equivalent of PAL
Then a table of XYZ metadata entries which have been found in the wild:
Actually, not in the wild. They are from H.262.
OK, then I think what you have — what you put in your text attachment
"d-NTSC & d-PAL .txt" in your previous message — is two single-line
glossary entries, conjoined with entries from a table mapping H.262
Metadata Values to video types d-NTSC and d-PAL.
I think it is clearer to have the mapping from H.262 Metadata Values in
a separate structure from the glossary. You seem to want to combine
them. I disagree with this editorial choice, but you hold the pen and I
don't care to pick it up.
[Display the following table with fixed-width font]
Actually, Jim, what you sent is not in fixed-width font. :-)
I won't try to explain the vagaries of how my client formats messages,
how the list reformats them, and how your client displays them. I think
it's more accurate to say that what I sent was plain text, which looks
better displayed in a fixed-width font, but maybe your client chose to
display it using a variable-width font.
Plain-text emails are only good for certain kinds of content. They can
represent some table layouts, but not others. This thread appears to be
taking tables beyond what plain-text emails can handle.
—Jim DeLaHunt
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
