Tom Whitten wrote: > Shawn Walker writes: >> Liane Praza wrote: >>> Shawn Walker wrote: >>>> Liane Praza wrote: >>>>> Shawn Walker wrote: > [SNIP] >>>>>> 4. I have a need for users to be able to specify values to the >>>>>> program based on locale. This is not the locale that the program is >>>>>> running in, but the locale of the content being generated by the >>>>>> program. For example, I have a property group called "repository" >>>>>> and a propval called "name". What is the best way for them to be >>>>>> able to specify a value for "name" for each locale (e.g. en, fr, etc.)? >>>>> We currently do this with a convention of appending the locale name >>>>> to the property name. We don't have explicit formal support for it >>>>> at this point, though. >>>> That format would require me to specify a propval for each supported >>>> locale though would it not? Would it be better to use a >>>> multiple-value property instead and have the user pre-pend the locale >>>> to each value (e.g. en:value, fr:value)? >>> Why would you need to specify one a priori? The property would just be >>> created by your UI when it was specified by the user, I'd think. >> I have no such interface, it seems I can just document how to do it with >> svcprop for now and let the user take care of it. >> >> Thanks, >> -- >> Shawn Walker >> _______________________________________________ >> smf-discuss mailing list >> smf-discuss at opensolaris.org > > svcprop can only be used to read properties. You'll need to use svccfg to > create or modify properties. Since it is a general purpose too a typo can > produce unfortunate results. You may find that it would be easier for > your customer to at least provide a shell script to add the locale > information. This would allow you to insure that the proper values are > being set/modified. It would certainly save your customer some typing. > See Nico's example to get a feel for this.
As I said, "for now." An interface will definitely come later, but I needed to figure out if this was possible first and how. -- Shawn Walker
