Bugzilla – Bug 351387
Yast uses 'Bearbeiten' and 'Konfigurieren' inconsitently.
Last modified: 2008-01-30 16:51:17 UTC
German translation bug and typo. See attached screenshot of Modemkonfguration. The dialog suggests 'Drücken Sie Konfigurieren um es zu konfigurieren' It should read 'Drücken Sie Bearbeiten, um es zu konfigurieren' There is no button 'Konfigurieren in this dialog. See attached screenshot of Netzwerkeinstellungen. This looks very similar to the above, but it has a button 'Konfigurieren' instead of 'Bearbeiten'. The spacing in 'Drücken SieKonfigu rieren um' needs some adjustment, here. Both dialogs (and possibly others) should agree on either 'Konfigurieren' or 'Bearbeiten'.Mixing two interchangable words is not helpful.
Created attachment 189193 [details] Screenshot of Modemkonfiguration
Created attachment 189194 [details] Screenshot of Netzwerkeinstellungen
I fixed the network card related translation bug in SVN. I guess the modem related bug is caused by the English strings (I cannot test because of the lack of modem devices here). I guess in the modem related dialog you must use <LI>Press <B>Edit</B>... instead of <LI>Press <B>Configure</B>... Alternatively, you could replace the Edit button with Configure and change the help text accordingly. Katarina, does this make sense?
Reassigning failed... Repeating comment #3: I fixed the network card related translation bug in SVN. I guess the modem related bug is caused by the English strings (I cannot test because of the lack of modem devices here). I guess in the modem related dialog you must use <LI>Press <B>Edit</B>... instead of <LI>Press <B>Configure</B>... Alternatively, you could replace the Edit button with Configure and change the help text accordingly. Katarina, does this make sense?
We use unified descriptions, independent of device type. But yast2-lan (network card) module creates its own user interface (using Add-Configure-Delete) while all other modules (modem, isdn,...) use hardware wizard (using Add-Edit-Delete). That's where the inconsistency comes from.
Anyway, fixed in svn now