[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Website translation

From: Ludovic Courtès
Subject: Re: Website translation
Date: Sun, 14 Jul 2019 16:12:41 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)


"pelzflorian (Florian Pelz)" <address@hidden> skribis:

> 3) We could write our own PO file writer and MO file reader and use it
> with either Christopher’s lego translation and sirgazil’s format
> strings to use whatever format we want for developers and translators.

Note that “lego translation” is what we should _not_ do because it gives
translators fragments of sentences, which does not allow them to
correctly translate text.

As long as we use xgettext, we have to stick to a format-string-like
approach like what sirgazil proposes.

Writing a custom xgettext kind of tool wouldn’t help much because
gettext is fundamentally text oriented: you give it a string and it
returns a string.

So I think the alternative is:

  • use gettext, and in that case stick to a format-string-like
    mechanism, or:

  • use a completely new tool that would be able to consume and produce
    sexps (trees).

The latter doesn’t seem reasonable to me.  :-)

BTW, there might also be ideas to borrow from GNUN:


reply via email to

[Prev in Thread] Current Thread [Next in Thread]