>>> "Paul" == Paul Eggert <[EMAIL PROTECTED]> writes:
> Akim Demaille <[EMAIL PROTECTED]> writes: >> Why not keeping a colon? >> >> syntax error: unexpected %s >> syntax error: unexpected %s, expecting %s >> syntax error: unexpected %s, expecting %s or %s >> syntax error: unexpected %s, expecting %s or %s or %s >> syntax error: unexpected %s, expecting %s or %s or %s or %s > I thought it better to use the traditional message formats, unless > there's a good reason to change. If I recall correctly, GCC uses the > exact same wording in its own parsers (which are now hand-built for C > and C++, sigh) so translators can share the translations. Hum. I'm more used to informational messages starting with a clear label (warning, error, etc.), a colon, and then a description of the issue. But that's was just a short comment while flushing my messages (I still have to reach that about #line ;). > While we're on the subject, if Bison ever changes the wording of a > translatable message that goes into a generated parser, we'll need to > keep the old wording in the message translation table, so that older > programs will still be localized properly. I understand.
