From: George Williams <gww@si...> - 2005-10-24 00:56:56
On Sun, 2005-10-23 at 08:45, Daichi Kawahata wrote:
> I'm happy finally seeing directory `po' at the top level, although
> not going to be translator for this package (seems tough translator
> is already there), if you'll also add gettext support, maintenance
> works for the translation files will be drastically improved.
I'm a little confused by what you mean by this. gettext support is
available in the cvs tree and from the experimental source tarball on
Perhaps I'm misunderstanding?
> Here's an example POT file (FontForge.pot.bz2) from my modified
> source tree
There is a makefile entry for building pot files in the above code.
There is an example pot file on the website already.
> # These options get passed to xgettext.
> XGETTEXT_OPTIONS = \
> --keyword=_ \
> --keyword=N_ \
> --keyword=U_ \
> --keyword=NU_ \
> --keyword=S_ \
> --keyword=P_:1,2 \
> --from-code=UTF-8 <- this one
Unfortunately this must be a fairly new option to xgettext. It fails on
3 of the 4 machines on which I do builds.
> you don't have to create fontforge/fontforge/utf8.pot at all.
I'll keep track of it for future reference, but I think I'd better not
use it at the moment. Thank you for pointing it out to me.
> PS. I've been using since it was called PfaEdit, this
> application's really great, many thanks for the developers,
> and Japanese translator(s).
Glad you like it:-)
Get latest updates about Open Source Projects, Conferences and News.