Re: i18n/l10n summary

[Jean-Christophe Helary]

On Jul 22, 2017, at 22:06, Eli Zaretskii <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.

Actually, I didn't reply because I didn't understand what was the
question.  Can you remind me?

It was just about making sure that all the files (in fact only docstyle.texi) included "@documentlanguage en_US" and "@documentencoding UTF-8".

After checking the files I realized that all had "@include docstyle.texi" which already had "@documentencoding UTF-8", so I just added "@documentlanguage en_US" there.

Let me know if there is a problem with that.

Jean-Christophe 

documentlanguage.diff
Description: Binary data