On Tue, May 04, 1999 at 07:26:29AM -0500, Gilbert Ramirez wrote:
> On Mon, May 03, 1999 at 11:45:33PM -0500, Frederic Peters wrote:
> >
> > I'd like to gettextize it but won't do it if you planned that for
> > later. If you don't know about gettext I can write a brief summary
> > (this is far from difficult) and I can also provide a french
> > translation.
>
> No, I don't believe anyone is working on I18N. I am coping this to
> ethereal-users and ethereal-dev because I was wondering which parts of
> ethereal might be translated. That is, for users whose first language is
> not English, which parts of ethereal should be translated? Should all
> packet information be translated, or just the menus and dialog boxes.
Imho nothing should be translated.
> I thought about this for a moment because all the RFCs are in English,
> and sometimes it might be easier to read packet information in the same
> language as the RFC is written than in your native language. But I
> really don't know since English is my native language.
>
> Please post all opinions!
It's easy. I saw quite a few translated Programs (mutt p.ex.) and still
have to see a single good translation. But then, I'm probably not the
target audience, as I understand english, and prefer a consistent
language in all my programs.
Also I think it makes reading the Programs a good deal uglier.
So please, if you add NLS, please make it at least compile-time
configurable so I can live without the cruft of gettext et al.
That said, recap'ing the arguments on the mutt mailinglists, the
people who want nationalized programs usually want everything the user
sees translated.
CU,
Sec
--
Treat your password like your toothbrush. Don't let anybody else use it,
and get a new one every six months. --Clifford Stoll
