Bug 276441

Sorry but I do not understand what behavior of YaST modules do you require. What should be translated? YaST modules are already translated, do you mean some keys in smb.conf? Or parameter to some call?

The _value_ used for the global parameter 'workgroup' should be able to get a localized version under the conditions described in the initial comment.

Sorry, but I still don't understand. Do you mean that user should be able to enter localized version of workgroup? Or that YaST should show it somehow - but from where does it get the correct value?

YaST should use a localized default value derivated from the locale the user decided while the system install.  

A translation table is required to provide the localized strings.

Currently the table is:

language        translation of WORKGROUP
German          ARBEITSGRUPPE
*               WORKGROUP

While * is the default fallback if there is no translation available.

An argument why this isn't added to Samba upstream.

After adding the initial request I thought about adding this feature to the Samba code.  But this might lead to a changed configuration as soon as the administrator changes the locale of the system.  We can't expect from a Samba.org point of view to have a RPM or any other database which at least keeps track of the smb.conf file.

Samba already uses the default value WORKGROUP in param/loadparm.c to the call of set_global_myworkgroup().  Therefore it's possible to remove the global workgroup parameter at all.  Then it's possible for YaST even to track changes if WORKGROUP is used as the parameter.

Andreas, David, Ralf: We had some discussion regarding this feature brefore.  Please check if the suggestion isn't brain dead or at least if I didn't missed anything we discussed before.

'Therefore it's possible to remove the global workgroup parameter at all.' meant to remove the global workgroup setting from Novell's Samba packages smb.conf file.

The benefits of this feature are:

a) The YaST samba modules will be closer to the default behavior of Microsoft
   systems.
b) Any Samba configured with YaST will immediately be part of a potentially
   existing workgroup.

OK, but what if there exist a workgroup called WORKGROUP and YaST changes it to ARBEITSGRUPPE? This is typical problem of programs trying to be too clever.

Additinally, I think that if you want to have a certain default value in smb.conf (which is the point of this request, if I get it right finally), you should provide it by the package itself. What about setting it in rpm post-install script (where you should know the locale)?

a) If the user used Samba's nmbd, smbd, or winbindd there would be log files in
   /var/log/samba/log.*.  And yes, that's the reason why I made existing log files 
   a condition not to change anything with the initial comment.
b) Yes, the intention is to get a localized default value for the global workgroup 
   parameter in smb.conf.
c) By intention this will not be added to the post install script of the RPM.  By
   two reasons:
   aa) No configuration tasks in the RPM scripts (time and risk).
   bb) The change might not be wanted by the user.  The intention of a user
       starting YaST instead is to configure a particular service.

Well... I tend to disagree with aa and bb, but if you really want this behavior, it should be easy to implement (*). Jiri, do you agree with this request?


(*) BTW, there are pending needinfos at you in other cases (bug 240045, feature 120090), please react.

Let's see first if Ralf, Andreas, or David have some additional input.

Changing smb.conf once in the install case of RPM looks like an advantage even to me.

As far as what should or should not happen if the locale is changed after the initial install, perhaps we should do just what an MS server does.  For example, if you change the locale after a server is installed, does it change the actual localized string name representing that server in the corresponding name service, or does it just affect the UI and not the SMB server name?

I am still looking at what this change might do for Domain Services for Windows.

Responding to Lars request:

I have installed a "Windows XP SP2 Professional Portuguese Brasil" workstation. See the default translation configured by MS:

locale or country: Brazil Portuguese | pt_br
Workgroup field: GRUPO

If You need any further information, please contact me.

(In reply to comment #11)
[..]
> Changing smb.conf once in the install case of RPM looks like an advantage
> even to me.
To me that looks more like a source of confusion and possible bugs. Remember the post-install is executed every time you update/install the package. If you have a bug in there you might destroy the whole configuration. So it's IMO wise to keep that part as small and as straight forward as possible.
When it is implemented in YaST it is less likely to cause trouble for people who don't want that feature.

So, could you gather the list of translated entries?
Yes, I've seen your mail on some list, but here is actually only one response to it (comment #13).

Maybe Karl could help?

If you add some such POT file to the yast or lcn directory in the suse-i18n SVN, we will translate it, but only a few of us are familiar with other OSses but openSUSE.

If you want to add the file to the yast directory, talk Jiri (jsrain) who now submit the yast POT files.

A simple translation of the word workgroup doesn't help.

The same wording as used by Microsoft localized products has to be used instead.

Hi,

for Belgium / Dutch it's "WERKGROEP" ... probably likewise for the Netherlands.

Tx,

Jo

Lars, don't you want to create a feature from this one? Looks like this kind of asking doesn't lead to expected results...

Giving to samba maintainers to gather required info.

I agree with comment #14. Reassigning to Lars.

Move to fate #307622.