On errno

[Randall Stewart]

P:

I like your original idea best... its simple and seems to me
a very positive way to go.  Things that get complex tend to
be avoided by application writers.. where simple things
get picked up ;-)


R
On Mar 31, 2009, at 2:48 AM, Poul-Henning Kamp wrote:

> In message <20090331063159.GA9265 at zim.MIT.EDU>, David Schultz writes:
>
>> You could get the extensibility you're looking for without
>> annoying the i18n folks by making the strings conform to a simple
>> machine-parsable grammar. For instance, the above might be:
>>   "geom:part:overlaps bootcode(3)"
>> A user-level library function could parse this, look up a natural
>> language translation in a locale-specific database, and fall back
>> on a generic format if no translation is available.
>
> Or maybe emit all messages in Esparanto and use automatic  
> translation ?
>
> Seriously, I don't see anybody advocating that dmesg(1) output be
> translated, so until such time as somebody starts that pointless
> project, I think we can leave error messages from the kernel in the
> same language as pretty much everything else in our system: English.
>
> Don't overengineer it guys.
>
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by  
> incompetence.
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch- 
> unsubscribe at freebsd.org"
>

------------------------------
Randall Stewart
803-317-4952 (cell)
803-345-0391(direct)