* Michael C . Wu <[EMAIL PROTECTED]> [001206 01:46] wrote:
> On Wed, Dec 06, 2000 at 05:28:28PM +0900, Tatsumi Hosokawa scribbled:
> | I've ported Multilingual sysinstall to -current.  I put the latest
> | source and binaries (Japanese/Englush only) is at
> | http://people.freebsd.org/~hosokawa/boot-ja/5.0-CURRENT/release-20001206-1/
> | (please note that non-English docuemnt files are based on 4.2-RELEASE)
> |
> | Currently, this implementation supports Japanese, Korean, Traditional
> | Chinese, and Russian.  The status of translation work is:
> |
> | Japanese:             finished
> | Korean:                       finished
> | Traditional Chinese:  about to finish
> | Russian:              only *.hlp files have been translated
> |
> | This code has some minor problems, but it works.  I think it's better
> | to change the development of this project to open style.  I would like
> | to import this code to -current CVS repositry soon if there's no
> | objections.
> 
> As we wait for libh development, I do not think we should exert
> efforts to try for another solution.  This tends to allow for
> slack in further development of better products.

No, this motivates those working for a greater good to produce
more than just promises of what's to come.

> A good example would be a proposal by Alfred Pernstein to slightly
> modify RELENG_4 SMP for the duration of SMPNG development.  The proposal
> was not well accepted due to the reason I stated above.

The proposal was only rejected as something that wasn't going to
be the be all and end all of our threading system.  As a middle
ground it would have many advantages over what's currently in place.
The same applies here.  Sure libh is supposed to be an order of
magnitude better than internationalized sysinstall, but at the
current time libh is as much vapourware as KSEs are.

> We really should concentrate on libh as a complete and _clean_ solution.

Yes, and no, you should continue doing so, and I have high hopes that
it's the best installer system ever, however an interm solution
would be a great way to attract new users and developers.

> In addition, the purpose of putting localized sysinstall in -CURRENT
> is rather dubious.  -CURRENT/HEAD is a developers' branch, people
> who use this branch should be able to read English and the system
> error messages.  If they cannot install the system with English
> sysinstall, I would have doubts on their programming and testing ability.
>
> People who run -CURRENT should be able to read and write English to
> understand the code comments, report bugs, and post to the lists in English.

Why?  It's my native tongue and even I have issues on occasion with
comments and manpage additions that forieners correct (Bruce, Eivind,
Asmodai and Sheldon to name a few.)  Having a problem with english
doesn't make anyone less of an intellectual.

> I would have no objections to L10N'ized sysinstall being maintained in
> the same way that PAO is maintained.  The boot floppies and iso images
> can be put up somewhere for download, and maintained in RELENG_4.

Maybe after libh is released... since you guys aren't basing your
work on sysinstall, it's not like you'd have to deal with a code
merger.

> Normally, I would welcome any I18N/L10N efforts in FreeBSD.
> However, the FreeBSD Project's official position paraphrased is
> "If you don't know what to do with -CURRENT, don't install it."
> Combined with the point that we should not divert efforts from libh,
> I hold the opinion that we should not import this.

I think it should be brought in and quickly MFC'd for the next
4.3 release.

I see no conflict between these two efforts and since one seems
pretty much completed, I'd like to see it in the base system.

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to