From: D. M. M. <mic...@ro...> - 2009-07-30 04:59:42
|
I just untangled a mess somebody made. I don't know who. I didn't run svn blame, and I'm not going to point any fingers. I do want to take this opportunity to remind everyone that we should always wrap user-visible strings in tr() calls. The compiler won't help with this one. Where this shows up is when someone runs Rosegarden in another language, and there are random English words for some strange reason. It just so happened this particular place was unusually nasty to track down too, and I found the whole experience more than a little irritating. What dumb rookie so and so screwed that up? But no, I won't look, I don't want to know, and I'm not pointing any fingers. Just keep it in mind from now on. If in doubt, use tr(). In fact, even if you're sure you don't need tr(), use tr() anyway. Thank you ladies and gentlemen for the outstanding job you do here at Rosegarden. Please carry on. -- D. Michael McIntyre |
From: Alexandre P. <ale...@gm...> - 2009-07-30 11:54:32
|
On Thu, Jul 30, 2009 at 8:59 AM, D. Michael McIntyre wrote: > I just untangled a mess somebody made. I don't know who. I didn't run svn > blame, and I'm not going to point any fingers. > > I do want to take this opportunity to remind everyone that we should always > wrap user-visible strings in tr() calls. The compiler won't help with this > one. Where this shows up is when someone runs Rosegarden in another language, > and there are random English words for some strange reason. > > It just so happened this particular place was unusually nasty to track down > too, and I found the whole experience more than a little irritating. What > dumb rookie so and so screwed that up? But no, I won't look, I don't want to > know, and I'm not pointing any fingers. > > Just keep it in mind from now on. If in doubt, use tr(). In fact, even if > you're sure you don't need tr(), use tr() anyway. "When in danger or in doubt, run in circles, scream and shout" (c) folklore :) Not being able to check myself atm... Do you changes covers ruler related menus and menu items? The MIDI device dialog that is still visible? Alexandre |
From: D. M. M. <mic...@ro...> - 2009-07-30 14:34:46
|
On Thursday 30 July 2009, Alexandre Prokoudine wrote: > Not being able to check myself atm... Do you changes covers ruler > related menus and menu items? The MIDI device dialog that is still > visible? The rulers are still under heavy construction, and I haven't even looked at any of those strings yet. I'm not sure what we will do with them when this is all over, so I would avoid translating them for now. I have no idea about the translation status of the device manager dialog, but I haven't worked on that. I just made a few small changes to tooltips. Shall I look into translating this dialog to hunt down the strings that don't translate then? -- D. Michael McIntyre |
From: Alexandre P. <ale...@gm...> - 2009-07-30 17:01:00
|
On Thu, Jul 30, 2009 at 6:34 PM, D. Michael McIntyre wrote: > Shall I look into translating this dialog to hunt down the strings that don't > translate then? If you wish :) My impression is that Rosegarden/Qt4 is like Scribus/Qt4: porting to Qt4 triggered refactoring and this is going to take ages to get the thing done, so I'm not in all but hurry really :) Alexandre |
From: Chris C. <ca...@al...> - 2009-07-30 17:06:27
|
On Thu, Jul 30, 2009 at 6:00 PM, Alexandre Prokoudine<ale...@gm...> wrote: > If you wish :) My impression is that Rosegarden/Qt4 is like > Scribus/Qt4: porting to Qt4 triggered refactoring and this is going to > take ages to get the thing done You're only about a year late with that observation! Yes, it's proving a pretty big job with a lot of domino effects. Chris |
From: Alexandre P. <ale...@gm...> - 2009-07-30 17:24:31
|
On Thu, Jul 30, 2009 at 9:06 PM, Chris Cannam wrote: > On Thu, Jul 30, 2009 at 6:00 PM, Alexandre > Prokoudine<ale...@gm...> wrote: >> If you wish :) My impression is that Rosegarden/Qt4 is like >> Scribus/Qt4: porting to Qt4 triggered refactoring and this is going to >> take ages to get the thing done > > You're only about a year late with that observation! I just didn't say that earlier :) > Yes, it's proving a pretty big job with a lot of domino effects. Well, no worries. Qt5 isn't going to be released until 2011 ;-) Alexandre |
From: D. M. M. <mic...@ro...> - 2009-07-31 01:09:32
|
On Thursday 30 July 2009, Alexandre Prokoudine wrote: > >> If you wish :) My impression is that Rosegarden/Qt4 is like > >> Scribus/Qt4: porting to Qt4 triggered refactoring and this is going to > >> take ages to get the thing done Indeed. > Well, no worries. Qt5 isn't going to be released until 2011 ;-) I'm going to ignore that comment and take another sip of beer. -- D. Michael McIntyre |