[FFmpeg-devel] GSoC with FFMpeg waht a combination!

Ronald S. Bultje rsbultje
Sun Mar 23 03:54:34 CET 2008


On Sat, Mar 22, 2008 at 7:58 PM, Michael Niedermayer <michaelni at gmx.at>

> The memory this needs is the same memory the pixel operations use. And
> that
> is limited on embeded systems
> strings ffmpeg | grep  '[a-z][a-z][a-z][a-z][a-z]'|wc -c
> says
> 129897
> 130kb is not that little for an embeded system, gettext would need
> twice that for each additional language in addition to the 130kb english
> strings.
> With 5 languages thats 1.3mb, this is 1/4 of ffmpegs size. This _does_
> matter.

Not every av_log() will be translated, that's insane. Most generally, all
debug messages that users would normally not see will not be translated,
because they are there for the developer more than for the user. If the
developer needs a translation before he can "parse" the user's error output,
it doesn't help at all for the user to read "error pts %lld < %lld
non-linear" in his own language, because he doesn't know what a pts is. What
you translate is those strings that convey useful information to the end
user, such as an errno return value from a system call (e.g. "host not
found" when reading a http stream). That is not 130kb.

Anyway, it's besides the point, because embedded systems will strip down
both ffmpeg and the i18n'ed to fit whatever size their stick happens to be
anyway. Your special gettext implementation will take additional binary
space also (rather than using the system-default gettext), which probably
already negates half of the gain.

I'm willing to do the work, but it has to be reasonable. Linux happens to
have a standard for this kind of stuff, let's please use it.


More information about the ffmpeg-devel mailing list