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

Uoti Urpala uoti.urpala
Mon Mar 24 19:24:44 CET 2008

On Sun, 2008-03-23 at 21:44 +0100, Michael Niedermayer wrote:
> On Sun, Mar 23, 2008 at 04:48:44AM +0100, Aurelien Jacobs wrote:
> > Well, reinventing gettext is not so trivial. I think the main
> > disadvantage of gettext is that it forces you to have a copy
> > of english strings in every translation files. But I'm pretty
> > sure this can be fixed in gettext (as an optional feature).
> well after someone fixed gettext i wont mind considering it ...

If your main problem with gettext is the size of the current translation
file format why would that make it unsuitable for FFmpeg? AFAIK there is
nothing in the gettext interface that would prevent creating a somewhat
more compact file format for it, so why would that have to be optimized
BEFORE translation support is added to FFmpeg?

That nobody has created a more compact format is IMO an indication that
in practice the size of the files is not a problem for most people (or
would still be a problem after a less than 50% size reduction). Your
"embedded device" examples sound quite farfetched. And if someone does
need size-optimized translation files then IMO it's their job to create
the optimized format, not the job of people who want to add translation
support to FFmpeg (as long as the translation interface used on the
FFmpeg side doesn't prevent optimizations on the lookup side).

More information about the ffmpeg-devel mailing list