[HEADSUP] dialog4ports does not popup anymore only for global options
Andrew W. Nosenko
andrew.w.nosenko at gmail.com
Sat Jun 8 12:04:14 UTC 2013
On Fri, Jun 7, 2013 at 9:58 PM, Chris Rees <utisoft at gmail.com> wrote:
> On 7 June 2013 18:49, Andrew W. Nosenko <andrew.w.nosenko at gmail.com> wrote:
>> On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees <utisoft at gmail.com> wrote:
>>> I can see your point when talking about DOCS, but for NLS it's insanity
>>> *for general use*. Give me an example of where NLS non-globals are
>>> appropriate and I'll shut up.
>> The GIMP in Russian locale.
>> GNU Make in any non-English locale.
> I guess you mean the translations are bad?
Your guess is wrong. For some reason you are treating NLS as "black
and white" thing. Either completely enable, or completely disable.
Please, just belive that there are lot of grays in between.
But I'm completely against:
1. Poor or confusing translations (when easiest way to understand
something is to try to back-translate to English, or in some
pathological cases, start application in the English locale and match
UI elements by position);
2. Translations of tools, which are intended to or used to interact
with other tools, as opposed to the end users (GNU make, GCC, Git,
GnuPG are perfect examples)
3. Ports which do not provide the easy enough and consistent way to
disable NLS. Just because it deprives me a way to workaround cases #1
And the #3 is the reason, why I stand up in this thread.
I don't bother about popping-up dialogs. After all, I'm not in a
business of rebuilding the whole ports tree from scratch every day.
And even a machine will wait my answer the whole night -- not a
problem. Summary time required to build plus wasted time is
negligible in comparison to time spent in using application.
Therefore, the first thing, which I optimize, is a comfort of using
application, and other things are going only after that.
Andrew W. Nosenko <andrew.w.nosenko at gmail.com>
More information about the freebsd-ports