Full Ack. Instead of introducing suppport for other languages we should
try to keep the documentation in English up2date. And as we have already
spreaded the documentation over so many places (man pages, users-guide,
developer-guide, README.developer, wiki) we don't need another one.
Any documentation about the VoIP Calls dialog should be moved to the wiki.
So I vote for reverting these changes to the VoIP Calls dialog.
Regards,
Lars
LEGO schrieb:
IMHO,
English is the only language worth being mantained. To get it clear:
In our field(s) documentation in other languages is scarse and/or
obsolete. That is: English in this field is not an option.
As I've told many people, first learn English which is (almost) a
prerequisite to learn everything else in this field. You won't go far
without it.
L
On 5/24/05, Ulf Lamping <ulf.lamping@xxxxxx> wrote:
Hi List!
Just had a look at the recent changes in the Voip Calls dialog.
It now contains a Help button which opens up another dialog with just
two buttons: "Go to spanish help page" and "Go to english help page"
IMHO: THIS IS COMPLETELY ODD for several reasons:
First: it doesn't make sense to have a program completely in english
only (menus, dialogs, documentation, ...) except for *exactly one* wiki
help page.
Second: Pressing a button just to get another dialog with just two
buttons is bad GUI design IMO.
Third: The user shouldn't be asked for it's preferred language somewhere
at a dialog box deeply in the hierarchy. If this model would be used all
over the GUI this would be just ridiculous.
Fourth: don't provide a dialog without a "Close" button, as on some
platforms you won't be able to close it.
Unless someone gives me a *very* good reason why it has to be that way,
I would ask the one who committed it, please remove at least the Spanish
part.
I don't have anything against the Spanish (or any other) language, but
adding multi language support should be agreed upon and thought about in
a more general way. But as we have problems keeping even the english
version uptodate (e.g. documentation), I don't think it's a good idea to
start provide support for other languages, without having the manpower
to maintain it.
Regards, ULFL
P.S: I was thinking about adding multi language support (german in my
case), but dismissed that idea as the effort wouldn't make much sense
and could better be spend elsewhere. Providing partly support (e.g. only
menus) is just odd, as this will promise things it cannot hold (and e.g.
mixing english and german in one program will look really odd). And
adding support for *all* protocol field descriptions would be a very
huge amount of work, and making it almost impossible to maintain IMHO.
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev