True. I included the glade file to be helpful. What's the best form for these messages to be in? They're in a CSV file right now that I can easily convert to just about anything. (Including simplistic patches.) But if the two sets of text are going to be separate then maybe a patch isn't the best form at the moment.
(BTW -- using separate strings for the primary text and the secondary text will certainly increase the number of strings to be translated and may make context less clear. Maybe they should continue to be long strings?) On Wed, 2004-03-31 at 22:22, Not Zed wrote: > 1. we have to split the error messages in the text, in many cases, so we > can automatically apply markeup in the code. We should not be including > markup in these strings for various reasons (translation load for one). > 2. we should have the boxes built by a standard method, and really, > using glade is just overhead that isn't worth it. > > On Wed, 2004-03-31 at 17:54 -0500, Benjamin Kahn wrote: > > The Evolution error messages and warning dialogs are fairly un-higgy. > > There are two issues. The first is that the text itself isn't hig-gy. > > The second issue is that the spacing and layout of the dialogs isn't > > hig-gy. I've attached a glade file which can be used to create hig-gy > > warning dialogs. Here's a screenshot: > > > > Notice that there are sets of text. Since I have not updated all the > > messages that Evolution can display, it's possible to see old > > messages. In this case, the HIG specifies that the message be > > displayed as the primary text (big and bold) and the secondary text be > > empty. > > > > I've created a number of re-written error messages as well. Please > > find it attached. -- Benjamin Kahn <[EMAIL PROTECTED]> W: 617 / 613 - 2024 F: 401 / 712 - 8649 _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution-hackers
