[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: i18n for yacc backend messages

From: Hans Aberg
Subject: Re: i18n for yacc backend messages
Date: Sat, 16 Apr 2005 11:19:52 +0200

At 11:05 +0200 2005/04/16, Jan Nieuwenhuizen wrote:
Paul Eggert writes:

 and if you print that string you'll see this:


 and this is a C representation of an equivalent to the original

Ah, yes.  But I would rather not feed the average lilypond user a C
represenation of a string, most of our users are not programmers.

   %token BOOK "\\book"

is into this


which will print as error: syntax error, unexpected "\\book", expecting '{'

The extra backslash is not helpful.  Hmm.

I think it should be so that, in the final error message, the "..." put in the %token part is printed as if was enetered as a C-string in a C source. Thus:
  %token BOOK "\\book"
should print as
(no quotes). And
  %token SPECIAL "\\\'\?\"\a\b\f\n\r\t\v\001\377\x001\x0000ff"
should print as
i.e., no quotes, and the control, octal and hexadecimal values prints the characters they represent in the C language. This way, the write o erro messages gets maximum control over the output.
  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]