Hi,
Thanks for your efforts for the translations for the ucf
package. This is much appreciated. Unfortunately, I will not be
applying the patches unmodified, since I do not agree with some of the
changes suggested. (I am also not fully in agreement with the
antiseptic tone being advocated wrt user interaction; but that is a
discussion for another time)
One of the first changes suggested is changing "keep your
currently-installed version" to "keep the currently installed version",
which I think is less clear. The version I woulds use would be "keep
the local version currently installed" instead; which emphasizes the
fact that we are talking about the version local to the machine.
Secondly, if you are to hyphenate the currently-installed in
the choices; not hyphenating it in the default will break things; the
default has to be one of the choices. I suggest adding this to the
review guidelines, so mistakes like this are not made.
Next, I still consider it perfectly fine to personalize the
computer human interaction; I really liked HAL in 2001. There have been
other studies that indicate that user experience in enhanced by a less
sterile and formal dialogue.
Mayer (2002) articulated eight principles of multimedia design:
Personalisation principle: Deeper learning occurs when words are
presented in a conversational style rather than a formal style. It is
recommended that designers use conversational rather than expository
style language, and the first and second person rather than the third
person where appropriate.
"DEVELOPING A COMPUTER INTERACTION TO ENHANCE STUDENT UNDERSTANDING IN
STATISTICAL INFERENCE" , Kay Lipson, Glenda Francis, and Sue Kokonis
Swinburne University of Technology, Australia ([EMAIL PROTECTED])
Mayer, R. E. (2002). Cognitive theory and the design of multimedia
instruction: An example of the two-way street between cognition and
instruction. New Directions for Teaching and Learning, 89(Spring),
55-71.
So the question is going to remain the same.
The differences" --> "File differences" does not really add much
clarification. "Line by line differences between versions" adds
some clarity.
"Debian policy states" --> "The Debian policy states". "The Debian
Technical Policy Manual states"; if you want to be pedantic. I don't
think there is a "The" Debian policy. We have the Debian X policy, The
Debian Web policy, The Debian Menu policy ....
Also, configuration files do not preserve changes. Entities
acting on configuration files must act in a manner that user initiated
changes to configuration files must be preserved; if we are being
pedantic, we should be consistently pedantic.
Next, cannot and can not are both correct -- in different
contexts. If the usage is opposite can -- if I am unable to perform
some task, then I cannot do it. This is not the case here -- I
obviously _can_ label the file a conffile, as long as I am wiling to
forego some desirable aspects of the situation. I also can _not_ make
it a conffile.
When written as two words, one may imagine an emphasis being
placed on the word not. In this case, writing it out as two words
correctly conveys the nuances it was meant to convey.
However, since this is obviously creating some distress, how
about:
This script attempts to provide conffile-like handling for files that
may not be labelled as conffiles.
Next, in one place the replacement for `' is '', in another it
is "" (obviously, it should be ‘’, since debconf templates can handle
utf-8, right?).
Do you want me to upload a version of UCF with the new version
of the templates, and feed those to the translators?
manoj
--
Colorless green ideas sleep furiously.
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
