[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Website translation
From: |
Ricardo Wurmus |
Subject: |
Re: Website translation |
Date: |
Mon, 15 Jul 2019 14:59:42 +0200 |
User-agent: |
mu4e 1.2.0; emacs 26.2 |
Ludovic Courtès <address@hidden> writes:
> 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. :-)
I’m not sure I understand the problem well enough, but there seems to be
a middle way: using itstool with XML. When you squint really hard XML
is close to S-exprs.
--
Ricardo
- Re: Website translation, (continued)
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/15
- Re: Website translation, Ludovic Courtès, 2019/07/17
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/18
- Re: Website translation, Ricardo Wurmus, 2019/07/18
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/18
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/18
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/19
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/26
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/26
- Re: Website translation, sirgazil, 2019/07/18
- Re: Website translation,
Ricardo Wurmus <=
- Re: Website translation, pelzflorian (Florian Pelz), 2019/07/18
Re: Guix beyond 1.0: let’s have a roadmap!, P, 2019/07/09
Re: Guix beyond 1.0: let’s have a roadmap!, Ben Sturmfels, 2019/07/26