[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: |
Mon, 5 Jun 2017 21:55:08 +0900 |
>> 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
Jean-Christophe
- Re: i18n/l10n summary, (continued)
- Re: i18n/l10n summary, Philipp Stephani, 2017/06/01
- Re: i18n/l10n summary, Paul Eggert, 2017/06/01
- Re: i18n/l10n summary, Philipp Stephani, 2017/06/02
- Re: i18n/l10n summary, Paul Eggert, 2017/06/03
- Re: i18n/l10n summary, Andreas Schwab, 2017/06/03
- Re: i18n/l10n summary, Philipp Stephani, 2017/06/03
- Re: i18n/l10n summary, Paul Eggert, 2017/06/04
- Re: i18n/l10n summary, Eli Zaretskii, 2017/06/04
- Re: i18n/l10n summary, Paul Eggert, 2017/06/04
Re: i18n/l10n summary, Eli Zaretskii, 2017/06/01
Re: i18n/l10n summary,
Jean-Christophe Helary <=