Bug 55067 - Viewing of auxiliary files and too big progress bar
Summary: Viewing of auxiliary files and too big progress bar
Status: RESOLVED DUPLICATE of bug 53832
Alias: None
Product: kbabel
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Stanislav Visnovsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-23 14:18 UTC by Axel Bojer
Modified: 2003-03-24 19:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Bojer 2003-02-23 14:18:59 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Debian testing/unstable Packages
OS:          Linux

I have some request for Kbabel (in KDE 3.1) :

 First:  On the right side you can view different tools as the 
 auxiliary files. On the top, the english text is viewed,
 and underneath it goes the translation in another language.
 Using this function I dont really need the english text to be shown
 as this is the same as the one in the main part of the window
 (because the english string I am working with is the same as the one 
 shown as a tool). It would be nice to be able to change the size of 
 the english text-window, possibly totally hide it. 
 As to now you only can do this for both the auxiliarity 
 translated string and the original english text above it as one.
 It would be nice if they were separed in case of moving.
 
 Second: As to now I have to scroll left-right to show all the
 text. Could it be possible to wrap the text automatically so that it
 did not have to scroll for each new text?
 
 Third: When I go from one string to the next, the whole visible
 display 
Comment 1 Stanislav Visnovsky 2003-03-03 14:21:56 UTC
Progress bar does not jump anymore in HEAD.
Comment 2 Stanislav Visnovsky 2003-03-24 19:10:14 UTC
Msgid/msgstr can be freely resized now, the rest is fixed.

The wordwrap is a duplicate of #53832.

*** This bug has been marked as a duplicate of 53832 ***