Re: TR: ARI warning list change Fri May 29 01:53:26 UTC 2009

[Vladimir Prus <vladimir at codesourcery dot com>]

On Friday 29 May 2009 10:52:19 Pierre Muller wrote:
> Here is another example of the email that is generated
> by my patch to update-web-ari.
> 
>   It seems like you have forgotten a bunch of _() 
> macros.
> 
>   A possible improvement would be to send this message directly to
> people that committed a change to the sources that
> generated a new warning.
> 
>   Is it possible to extract the commits
> from the last 24 hours to find out to whom this kind of message should be
> sent?
> 
> Pierre Muller
> Still trying to improve ARI.
> 
> 
> -----Message d'origine-----
> De : GDB Administrator [mailto:gdbadmin@sourceware.org] 
> Envoyé : Friday, May 29, 2009 3:53 AM
> À : muller@sourceware.org
> Objet : ARI warning list change Fri May 29 01:53:26 UTC 2009
> 
> 657a658,659
> > gdb/mi/mi-cmd-var.c:251: gettext: _ markup: All messages should be marked
> up with _.
> > gdb/mi/mi-cmd-var.c:256: gettext: _ markup: All messages should be marked
> up with _.
> 837a840,846
> > gdb/varobj.c:853: gettext: _ markup: All messages should be marked up with
> _.
> > gdb/varobj.c:859: gettext: _ markup: All messages should be marked up with
> _.
> > gdb/varobj.c:865: gettext: _ markup: All messages should be marked up with
> _.
> > gdb/varobj.c:882: gettext: _ markup: All messages should be marked up with
> _.
> > gdb/varobj.c:1386: gettext: _ markup: All messages should be marked up
> with _.
> > gdb/varobj.c:1457: gettext: _ markup: All messages should be marked up
> with _.
> > gdb/varobj.c:1470: gettext: _ markup: All messages should be marked up
> with _.
> 1204d1212
> < gdb/value.c:529: deprecated: deprecated value_address_hack: Do not use
> deprecated value_address_hack, see declaration for details
> 1395,1396d1402
> < gdb/value.h:278: deprecated: deprecated value_address_hack: Do not use
> deprecated value_address_hack, see declaration for details
> < gdb/value.h:279: deprecated: deprecated value_address_hack: Do not use
> deprecated value_address_hack, see declaration for details

I am missing context on this email, but at least in MI, it's not yet clear
which messages should be i18n and which are not. Some are results of frontend
coding bug and as such should be never presented to user and should not be
ever translated. And if they are translated, they won't help the user but
will make it harder to understand the error for developer.

- Volodya