On 03/17/10 01:25 PM, Nicolas Williams wrote:
> On Wed, Mar 17, 2010 at 11:04:47AM -0700, Suresh Chandrasekharan wrote:
>    
>> 4. Technical Description
>>
>>      Locale services library is a library for locale related information
>>      written Python planning tobe delivered to Solaris Next. Choice
>>      of Python as an implementation language for this library is
>>      influenced by
>>
>>      * A request from installer team, for inclusion in text-installer
>>        and auto installer are being re-written using python.
>>
>>      * Python's richer set of libraries and ease of coding will cut
>>        development time compared with writing these interfaces in C
>>
>>      * Though providing such a library in C may appeal to a wider set
>>        of projects, as of right now we do not have any such requirement.
>>      
> There's a number of projects that could greatly benefit from a C library
> (even if that were implemented using IPC to a python daemon that uses
> your python library).  For example, ssh(1) and sshd(1M) (which currently
> execute and parse the output of locale -a).  But also C implementations
> of a growing number of Internet protocols that provide globalization
> features.
>
> Also, there's a tight coupling between locale definitions and this
> library, which is a good reason to consider having this library in ON.
>
> I didn't see any functions for searching for locales given RFC5066
> language tags (and optional codeset, though in general when such a
> function is necessary one typically also cares only about UTF-8 as the
> codeset).
>    

Agree strongly.  I think there may be a call here for both C and Python 
bindings.

On another note, the case references man pages for section3c, which is 
really intended for things that are part of libc.  I think you might 
need to create another section, or put this in a Python specific 
section.  (Not sure what that would be.)

I have not had a chance to fully chew on everything spelled out here -- 
I  can do so if there is need, but it might be better if one of the 
former LSARC members could examine this a bit more closely.

     - Garrett

Reply via email to