From 31bcbc3e5f3187b699fca5de75e8345759225433 Mon Sep 17 00:00:00 2001 From: zybi Date: Fri, 24 Aug 2001 10:05:46 +0000 Subject: Described encodings issues in more details. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@1677 b3059339-0415-0410-9bf9-f77b7e298cf2 --- TOOLS/subfont-c/README | 61 +++++++++++++++++++++++++++++++++----------------- 1 file changed, 41 insertions(+), 20 deletions(-) (limited to 'TOOLS') diff --git a/TOOLS/subfont-c/README b/TOOLS/subfont-c/README index dc1b78bd16..64d0402904 100644 --- a/TOOLS/subfont-c/README +++ b/TOOLS/subfont-c/README @@ -24,26 +24,47 @@ and user-supplied encodings (also multibyte) through custom encoding files. I prepared also Type 1 font `osd.pfb' for OSD characters based on bitmaps created by chass. -Subfont was tested with Korean fonts from truetype-fonts-ko-2.0-1k.noarch.rpm -I found on http://rpmfind.net/ and euc-kr encoding. Custom encoding file -for euc-kr was generated from charmap I found in /usr/share/i18n/charmaps/EUC-KR.gz -(glibc package). This should work with -unicode switch for mplayer -(though it is not Unicode encoding). -It took about 10 seconds to render over 8000 characters on P3 @ 600MHz. - -Custom encodings: -~~~~~~~~~~~~~~~~~ -For each character you want to render write the line consisting of: - hexadecimal Unicode character code, - followed by whitespace, - followed by hexadecimal number representing your encoding, - followed by new line character. - -Example: to render a single letter `aogonek' (Unicode 0x0105) and encode -it using iso-8859-2 encoding (0xB1), your custom encoding file will consist -of a sigle line: -0105 B1 +Encodings: +~~~~~~~~~~ +You can get any encoding and any charset. +1. If you want 8-bit charset, which is known to libc, encoded either in 8-bit + or Unicode (like ISO-8859-*, KOI8-*): + + Find correct encoding name using `iconv --list' (on RedHat) and use it. + For latin2 subtitles I would write: + ./subfont iso-8859-2 24 verdana.ttf + and for UTF-8 subtitles with latin2 charset: + ./subfont --unicode iso-8859-2 24 verdana.ttf + +2. If you want encoding not known to libc or non 8-bit (like EUC-KR): + + Create file describing your charset: + + For each character you want to render write the line consisting of: + hexadecimal Unicode character code + followed by whitespace + followed by hexadecimal number representing your encoding + followed by new line character + or (for UTF-8 subtitles): + hexadecimal Unicode character code + followed by new line character. + + Example: + To render a single letter `aogonek' (Unicode 0x0105) and encode + it using iso-8859-2 encoding (0xB1), your custom encoding file will consist + of a sigle line: + 0105 B1 + + or to get unicode font.desc, write only: + 0105 + + Subfont was tested with Korean fonts from truetype-fonts-ko-2.0-1k.noarch.rpm + I found on http://rpmfind.net/ and euc-kr encoding. Custom encoding file + for euc-kr was generated from charmap I found in /usr/share/i18n/charmaps/EUC-KR.gz + (glibc package). Simple script for this you will find in encodings directory. + This should work with -unicode switch for mplayer (though this is not Unicode). + It took about 10 seconds to render over 8000 characters on P3 @ 600MHz. New font.desc format (proposal): @@ -79,7 +100,7 @@ Notes: + Starting x position of each character and the bitmap width is aligned to multiple of 8 (required by mplayer). - + Currently subfont won't work on big-endian systems. + + Currently subfont won't work on big-endian systems. I need help. + My development platform is RedHat 7.1. FreeType versions tested are 2.0.1 through 2.0.4. -- cgit v1.2.3