Re: [Usability] markup in the statusbar messages, why not?



On Mon, 27 Sep 2004 21:05:55 +0100, Bastien Nocera <hadess hadess net> wrote:
> >
> > To be honest I can't think of any huge arguments against it (other than
> > the technical ones, like translation difficulties), in cases where it

>From translators' POV, this is not an issue at all. What translators concern
is, they have to translate tags enclosing the whole string, without any
change of word presentation in between. E.g.

msgid "<b>File Property</b>"

In this case, the tag could have been added by glade side but not included in
strings. This means translators are unnecessarily translating stuff. Another
example:

msgid "This file is <b>not</b> saved."

In second case, the tag is not enclosing the whole string; the word "not" is
stressed. Translators are happy to include the tags in this case.

Abel



> > genuinely improved legibility, provided we had guidelines for regulating
> > its usage.  However, I have to admit I can't think of any statusbar-type
> > messages off the top of my head that would be improved by it; they
> > shouldn't exactly be verbose.
> >
> > If the markup is just being used to try and draw attention to the
> > message, though, that's a different matter-- if it's important to demand
> > attention, then the status bar isn't the place for it.  (And I think
> > there is a guideline somewhere that says that.)
> 
> The question isn't why you wouldn't want markup in the statusbar, but
> why you would. As the statusbars aren't supposed to have any important
> messages, I don't see the point of having messages in bold or italics in
> the statusbar. And if the font is too small/not readable, you can
> increase the system font size, or tweak it just for the statusbar in the
> gtkrc.
> 
> In all cases, I don't see a reason at all for it...
> 
> ---
> Bastien Nocera <hadess hadess net> 
> 
> 
> 
> 
> _______________________________________________
> Usability mailing list
> Usability gnome org
> http://mail.gnome.org/mailman/listinfo/usability
>



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