Hello. >>>>> Marcus Brinkmann <[EMAIL PROTECTED]> wrote: >>>>> in <[EMAIL PROTECTED]>
Have made up control files of separated package for an experiment. Fortunatery, makeinfo and info distributed could handle multi-byte characters. The deb package and packed source (which contains control files) are in the directry http://members.fortunecity.com/childstar/hurd-ja/ I intande to transrate the remnant tiny file ``navigating''. > > I add much elder version which known as The GNU Hurd Interface > > Manual. We know that it has been obsoleted, but it explains > the atomic (and deprecated) Hurd functions, like conch, Shared > I/O etc. > > Do you have a link to the english original? I am not sure if I know about > it. It is doc/hurd.texi of much formar GNU Hurd version 0.2. ftp://ftp.gnu.org/gnu/hurd/hurd-0.2.tar.gz HTMLlized file is on http://www.cs.pdx.edu/~trent/gnu/hurd/hurdint.html. Except for the chapter of Shared I/O, It is antecedents of today's documentation. > > The situation for whom are interestead in the Hurd to be able > > to find out nothing more than few documents in their language, > > is sad. > > No wonder, it's not easy to find things in any language ;) You are right. ^^; > > I think to be packed with the distribution of the Hurd is > > best for it. Or separated package is better. > > I may be to try to make out debianized package of it. Still > > I have no skills of doing so, however. ^^; > > The problem is not as much the packaging for Debian. It starts with how to > organize the source tree, so that it will be scalable when more translations > come. And how will we manage updates to the documentation when they appear? > Can you do some research on how other GNU projects manage this? OKUJI > Yoshinori and Jeff posted some useful hints where to look for this > information, it would be nice if you could pursue this track. To tell you the truth, there only are few projects those contain multilingualized documentations. Linux's Kernel does not, FreeBSD's Kernel does not and so on. So English was the united language in the world of computer developement that no one thought to pack documentations of other languages which does not mean much to people who use another language, with risks of data volume, time-consuming jobs for management. (As far as I know, only the projects of Emacs and the GIMP work with multilingualized documentations partly.) And the transration is personal and language-dependent work, thus far. Present plans are organized collections of individual languages's documents themselves. The same kind of project must be with German, you know. GNUj(apanese)doc which Mr.OKUJI mentiond seems like just so, too. But yeah, It may be a good chance to construct a scalable scheme as you said. So I make a little inquiry at Japanese Emacs Newsgroup and the GIMP ML-ja or the others. > You don't need to make a Debian package out of it. I can include it in the > next Debian package without it being a part of the official source. I just > have to remember it. Thank you very much. Best regards. -- mihi~star <[EMAIL PROTECTED]> You are Free. You can Fly. So, You may Hope.
