VideoHelp Forum




+ Reply to Thread
Results 1 to 2 of 2
  1. Member Akagi Shigeru's Avatar
    Join Date
    Oct 2007
    Location
    United States
    Search Comp PM
    Ok I'm trying to convert this .MKV file I have to DVD. I've been doing hardsubbed videos using TMPGEnc Plus/DVD author for some time now so I'm just starting to get into softsubbed materials since .MKV is being increasingly used as a medium.

    So I've used .MKV extract and divided the .MKV into it's individual elements. The problem I'm having is that there are 11 different fonts being used in the source .MKV and I want to keep the font formatting. Certain fonts are being used at certain times in the video, and I want to get it that way on the DVD if possible. How would I go about doing this? The subtitles are an .ass file created in MEDUSA.

    If I can't do that on a DVD, then how would I go about hardsubbing the subs into the video source?
    I've never bet to gain anything.

    Dying meaninglessly from the outcome of a gamble - It's better that way. That gets closer to the true essence of gambling.

    I'll get closer to it's depths.

    That's where the real pleasure in gambling is.
    Quote Quote  
  2. Banned
    Join Date
    Jun 2007
    Location
    UNREACHABLE
    Search Comp PM
    If Medusa and Aegisub can pseudo-uuencode TTFs into .ssa files,
    then they *SHOULD* be able to do the inverse operation; but I do not know
    whether those apps are capable of extracting embedded fonts from the
    files that they themselves generated.


    [Fonts]
    This section contains text-encoded font files, if the user opted to embed non-standard fonts in the script. Only truetype fonts can be embedded in SSA scripts. Each font file is started with a single line in the format:

    fontname: <name of file>

    The word “fontname” must be in lower case (upper case will be interpretted as part of a text-encoded file).

    <name of file> is the file name that SSA will use when saving the font file. It is:
    the name of the original truetype font,
    plus an underscore,
    plus an optional “B” if Bold,
    plus an optional “I” if Italic,
    plus a number specifying the font encoding (character set),
    plus “.ttf”
    Eg.
    fontname: chaucer_B0.ttf
    fontname: comic_0.ttf

    The fontname line is followed by lines of printable characters, representing the binary values which make up the font file. Each line is 80 characters long, except the last one which may be less.

    The conversion from binary to printable characters is a form of Uuencoding, the details of this encoding is contained in "Appendix B", below.
    Appendix B: embedded font/picture encoding


    SSA’s font and picture file embeddeding is a form of UUEncoding.

    It takes a binary file, three bytes at a time, and converts the 24bits of those bytes into four 6-bit numbers. 33 is added to each of these four numbers, and the corresponding ascii character for each number is written into the script file.

    The offset of 33 means that lower-case characters cannot appear in the encoded output, and this is why the “filename” lines are always lower case.

    Each line of an encoded file is 80 characters long, except the last one, which may be shorter.

    If the length of the file being encoded is not an exact multiple of 3, then for odd-number filelengths, the last byte is multiplied by hexadecimal 100, and the most significant 12 bits are converted to two characters as above. For even-number filelengths, the last two bytes are multiplied by hexadecimal 10000, and the most significant 18 bits are converted to three characters as above.

    There is no terminating code for the embedded files. If a new [section] starts in the script, or if another filename line is found, or the end of the script file is reached then the file is considered complete.

    ++++++++++++++++++
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!