> X-Unix-From: dgk at research.att.com Tue Feb 14 19:13:46 2006
> X-Original-To: ksh93-integration-discuss at opensolaris.org
> Delivered-To: ksh93-integration-discuss at opensolaris.org
> Date: Tue, 14 Feb 2006 22:13:39 -0500 (EST)
> From: David Korn <dgk at research.att.com>
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> To: ksh93-integration-discuss at opensolaris.org
> Subject: Re: Re: [ksh93-integration-discuss] comments on ksh93 migration plan
> X-BeenThere: ksh93-integration-discuss at opensolaris.org
> X-Mailman-Version: 2.1.4
> List-Id: Korn Shell 93 integration/migration project discussion
<ksh93-integration-discuss.opensolaris.org>
> List-Unsubscribe:
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>,
<mailto:ksh93-integration-discuss-request at
opensolaris.org?subject=unsubscribe>
> List-Archive:
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss>
> List-Post: <mailto:ksh93-integration-discuss at opensolaris.org>
> List-Help:
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=help>
> List-Subscribe:
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>,
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=subscribe>
>
>
> > and there
> > are features in the existing /usr/bin/ksh which are needed before
> > we can replace it, including internationalization with the proper hooks
> > for all the Sun-supported locales and multibyte character handling.
>
>
> ksh93 already has support for I18N and for multibyte character
> handling. If there is need for change, it should be minimal
> since currently all error message translation goes through a single
> interface.
>
> The multibyte character handling uses the POSIX mb*() interface.
I believe in ksh93 this may not be working in all respects.
An i18n engineer and I tried a few manual tests on ksh93 with
multibyte characters, and ksh93 did not appear to recognize some of
them which may have included an ASCII byte within the multibyte character.
>
> It would be a mistake to make major changes for I18N since
> these would be hard to keep in sync with the ksh93 source.
I want to minimize this as much as possible, so we can continue to
update from the ksh93 source in a timely manner.
But in Solaris utilities, we gettext() messages, and
this is the basis for generating messaging files which are automatically
passed onto the localization groups for translation. I admit that I
did not turn on the translation functions when building ksh93
and do not yet understand it enough to know if we can create some kind of
wrapper or macros for ksh93 to fit into the Solaris i18n framework.
It appears that other utilities in Solaris originating from open source--
perl, for instance--do not follow this gettexted message model, so
there may be alternate i18n methods in Solaris that can be used.
April
>
> With our current build procedure, we are able to produce all
> the phrases the need translation; both error messsages and
> man pages. These phrases would need translation for each
> of the locales.
>
> David Korn
> dgk at research.att.com
> _______________________________________________
> ksh93-integration-discuss mailing list
> ksh93-integration-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/ksh93-integration-discuss
