Bug#355804: Proposed patch

2006-03-08 Thread Attilio Fiandrotti
Frans Pop wrote: On Wednesday 08 March 2006 16:26, [EMAIL PROTECTED] wrote: on the cutted text bug, as i said before, this is a GTKDFB (all versions) upstream bug There are _two_ issues with the info text: 1. the text is cut off 2. it is not displayed at all when install is running automated

Bug#355804: Proposed patch

2006-03-08 Thread Frans Pop
On Wednesday 08 March 2006 16:26, [EMAIL PROTECTED] wrote: > on the cutted text bug, as i said before, this is a GTKDFB (all > versions) upstream bug There are _two_ issues with the info text: 1. the text is cut off 2. it is not displayed at all when install is running automated For 1, that is up

Bug#355804: Proposed patch

2006-03-08 Thread [EMAIL PROTECTED]
Frans Pop wrote: > On Wednesday 08 March 2006 14:59, you wrote: > >>Yes, the buttons are now translated. Nice job. > > > Hmm. With one negative side effect: you now see the buttons "flicker" > quite often when they are refreshed. This happens when the progress bar > moves (or maybe when the

Bug#355804: Proposed patch

2006-03-08 Thread Frans Pop
On Wednesday 08 March 2006 14:59, you wrote: > Yes, the buttons are now translated. Nice job. Hmm. With one negative side effect: you now see the buttons "flicker" quite often when they are refreshed. This happens when the progress bar moves (or maybe when the text below the progress bar is upda

Bug#355804: Proposed patch

2006-03-08 Thread Frans Pop
On Wednesday 08 March 2006 10:53, [EMAIL PROTECTED] wrote: > Attached patch should take care of translating buttons even in the > case of fully automated installs ( when no questions are asked before > the progressbar runs ). Yes, the buttons are now translated. Nice job. But the info message is

Bug#355804: Proposed patch

2006-03-08 Thread [EMAIL PROTECTED]
Tags: patch Attached patch should take care of translating buttons even in the case of fully automated installs ( when no questions are asked before the progressbar runs ). About the "cutted text" problem: this seems to be the same GTKDFB upstream [1] bug already found some times ago (see also