[OpenIndiana-discuss] Translation and localization (was: Re: Manpages and documentation -- where to start?)
dpayno at gmail.com
Sat Oct 2 21:51:39 UTC 2010
First of all, good habit from my FidoNet days, Hi, I'm Daniel, aka Pay. Long term Debian user, using Solaris (nevada,10,...) for the last 4 years.
I was involved with the kde-es translation and localization proyect in the last years of the past century and have experience working with kbabel and editing of typical gettext .po files etc.. Does illumos/openindiana use po getext style messaging? Is this planned for the libc re-coding effort? If not, pointers to the system used, appreciated.
I am very grateful to Garret, Alasdair et al involved in this movement and want to add my few skills to the proyect,being as I am, more of a sysadmin, and less of a coder, except for bash scripts etc. I offer myself to form part of the spanish translation of system and messages.
Any useful pointers to mailing lists? Any planned idea of a uplinks/openindiana-l10n@ mailing list for these efforts?
Daniel Payno Jiménez-Ugarte
El 01/10/2010, a las 12:29, Guido Berhoerster <gber at openindiana.org> escribió:
> * Alasdair Lumsden <alasdairrr at gmail.com> [2010-10-01 00:32]:
>> On 30 Sep 2010, at 09:41, Paul Johnston wrote:
>>> In terms of what could do with being more up to date may I venture the
>>> zpool and zfs entries as starters?
>>> They are fairly quick moving facets of the OS and the ones (man pages)
>>> on my machine are over 9 months old.
>>> Regards Paul
>> Hi Paul,
>> We definitely could do with people working on the documentation
>> side of things. Unfortunately I personally don't know exactly
>> what the state of play is with the documentation; I'm not sure
>> which consolidations they live in (if they're centralised in a
>> single manpage consolidation, or if they're spread out).
>> So I'm not sure how to advise on where to start. We definitely
>> would appreciate the help with it, but it might involve a
>> "research project" first, including "documenting the state of
> Changes to ONNV documentation (that is non-OpenIndiana spcific
> stuff) should be made in an Illumos subproject. They already have
> a documentation project although I can't see if there is any
> The main problem with ONNV manpages is that their sources have
> not been made available, so the Illumos project needs to agree on
> a way to maintain these.
> The most current ONNV manpage drop (from September 2009) can be
> obtained here:
> Guido Berhoerster
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
More information about the OpenIndiana-discuss