[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: i18n/l10n summary
From: |
Jean-Christophe Helary |
Subject: |
Re: i18n/l10n summary |
Date: |
Sat, 22 Jul 2017 21:48:29 +0900 |
> On Jul 18, 2017, at 8:22, Jean-Christophe Helary <address@hidden> wrote:
>>>> The discussion so far seems to point at modifying 'message' and
>>>> the likes so that developers don't have to bother with any l10n
>>>> mechanism on their part (besides for writing clean strings).
>>
>> Just as a reminder, we'll need to update all the texi files so that they
>> include:
>> @documentlanguage
>> @documentencoding
>
> Is it ok to proceed with that ?
I don't think there was a reply to that so I guess that's a yes. I'm going to
proceed and send a patch here and then wait for comments.
Jean-Christophe
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/01
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/17
- Re: i18n/l10n summary,
Jean-Christophe Helary <=
- Re: i18n/l10n summary, Eli Zaretskii, 2017/07/22
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/22
- Re: i18n/l10n summary, Eli Zaretskii, 2017/07/22
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/22
- Re: i18n/l10n summary, Eli Zaretskii, 2017/07/23
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/23
- Re: i18n/l10n summary, Eli Zaretskii, 2017/07/24
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/24
- Re: i18n/l10n summary, Eli Zaretskii, 2017/07/24
- Re: i18n/l10n summary, Jean-Christophe Helary, 2017/07/24