[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: i18n for yacc backend messages
From: |
Akim Demaille |
Subject: |
Re: i18n for yacc backend messages |
Date: |
Thu, 14 Apr 2005 10:57:09 +0200 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) |
>>> "Paul" == Paul Eggert <address@hidden> writes:
> Can you please explain why the token names should be translated? It's
> possible that this should be an option, rather than being an
> unconditional translation.
Token can be given a human readable string. INT can be integer, which
is to be translated in "entier" in French.
- Re: i18n for yacc backend messages, (continued)
- Re: i18n for yacc backend messages, Hans Aberg, 2005/04/14
- Re: i18n for yacc backend messages, Jan Nieuwenhuizen, 2005/04/14
- Re: i18n for yacc backend messages, Paul Eggert, 2005/04/16
- Re: i18n for yacc backend messages, Jan Nieuwenhuizen, 2005/04/16
- Re: i18n for yacc backend messages, Paul Eggert, 2005/04/16
- Re: i18n for yacc backend messages, Jan Nieuwenhuizen, 2005/04/16
- Re: i18n for yacc backend messages, Hans Aberg, 2005/04/16
- Re: i18n for yacc backend messages, Paul Eggert, 2005/04/17
- Re: i18n for yacc backend messages, Hans Aberg, 2005/04/17
- Re: i18n for yacc backend messages, Jan Nieuwenhuizen, 2005/04/18
- Re: i18n for yacc backend messages,
Akim Demaille <=
Re: i18n for yacc backend messages, Akim Demaille, 2005/04/14