-On [20001022 10:55], [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
I seriously advice against directly importing the Citrus code.
It is very good work and a lot will be borrowed, but on my latest
investigations it also made a lot of unnecessary and gratuitous changes.
which part looks
On Thu, Oct 19, 2000 at 08:38:47PM +0200, Johan Granlund scribbled:
| On Thu, 19 Oct 2000, Michael C . Wu wrote:
| At the BSDCon I18N BOF, we discussed several things that could/should
| happen with the future of I18N(internationalization) in FreeBSD.
| We would like some inputs and comments
On Thu, Oct 19, 2000 at 01:16:12PM -0700, Jordan Hubbard scribbled:
|The advantages are :
| A. Easy bug reporting by users. (e.g. "I have error 2398423")
| B. I18N error messages
|
| Let me just say, as someone who's done "escalation tech support" for
| major ISVs (the people who
At the BSDCon I18N BOF, we discussed several things that could/should
happen with the future of I18N(internationalization) in FreeBSD.
We would like some inputs and comments regarding the following:
* Moving to message catalogue style error messages for the kernel and
userland. (AIX style)
On 10/19/00, Michael C . Wu wrote:
3. Itojun mentioned that the CITRUS Japanese people will be able
to import the wchar* and libxpg4 changes soon.
This is great! I believe many developers have spent too much unnecessary
time dealing with wchar.h. Is there a timeline yet?
BTW, are there
* Moving to message catalogue style error messages for the kernel and
userland. (AIX style) Each time the system outputs an error
either from the kernel or userland, the error message is a
formatted alphanumerica string mapped to verbose error messages.
The error messages can be
On Thu, 19 Oct 2000, Michael C . Wu wrote:
At the BSDCon I18N BOF, we discussed several things that could/should
happen with the future of I18N(internationalization) in FreeBSD.
We would like some inputs and comments regarding the following:
SNIP
2. Needing a graphics console to display
On Thu, Oct 19, 2000 at 05:17:38PM +, Terry Lambert scribbled:
| * Moving to message catalogue style error messages for the kernel and
|userland. (AIX style) Each time the system outputs an error
|either from the kernel or userland, the error message is a
|formatted
Hi,
"Michael C . Wu" [EMAIL PROTECTED]wrote:
1. The future of sysinstall (or whatever should replace it)
The future installer/management utility should be
able to handle arbitrary character sets.
In other words, it should be able to display Chinese/Japanese/etc.
with user
3. Itojun mentioned that the CITRUS Japanese people will be able
to import the wchar* and libxpg4 changes soon.
the code is there, but as i talked, we need more manpower for
babysitting.
cvs -d :pserver:[EMAIL PROTECTED]:/anoncvs/citrus co -P xpg4dl
itojun
To
The advantages are :
A. Easy bug reporting by users. (e.g. "I have error 2398423")
B. I18N error messages
Let me just say, as someone who's done "escalation tech support" for
major ISVs (the people who get called whenever front-line tech support
is confronted with a "I have error
11 matches
Mail list logo
