<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<ul>
</ul>
On 03/03/2012 12:26 PM, Bastien Montagne wrote:
<blockquote cite="mid:4F51FFE5.7030409@wanadoo.fr" type="cite">
<pre wrap="">In fact, rather than "noun", "verb" and "adjective" contexts (I doubt
the later would be much used, btw), I’d rather have an "operator"
context – theoretically, operators should always be verbs (as they *do*
something), while simple settings should always be nouns (as they *are*,
represent something). In your example, Group as verb should only be used
by grouping operator, while group as a noun should only be used by
settings controlling which groups are used/selected/etc. This would also
enforce good practices in labels themselves!
Note also that we will have a default, not-named context, used for most
common cases (e.g. "Volume" as space would be generic context, while
"Volume" as sound would have it’s "Audio" context…).
But agree this is a bit a tricky subject, as ideally we want to cover
all problems (in all languages!!!) with as few contexts as possible… So
let’s discuss a bit more, then I’ll start adding a few, most needed
contexts, and we’ll see how it goes, processing by tries and errors if
needed.
Another idea, we could end having a few (3, 4 at most) holdall
"disambiguation" contexts, to be used for corner cases when we can’t
find a better solution…</pre>
</blockquote>
<br>
I like the idea of having an "operator" context, I think represents
more closely the Blender terminology. :)<br>
I agree with most that you said.<br>
<br>
<br>
On 03/03/2012 04:39 PM, Gabriel Gazzán wrote:
<blockquote
cite="mid:CAE2cOoEU8=s3gzAMES0Ya5L64AwB0SjZumPDPGgOnyLQjbiTaw@mail.gmail.com"
type="cite">I've found the fact that the English words doesn't
determine the gender of the term causing problems too.<br>
For example "New (object)" in Spanish should be "Nuevo (objeto)",
but "New (texture)" should be "Nueva (textura)".<br>
That makes the use of a single text string problematic for
translating into languages with similar gender structures as
Spanish.<br>
<br>
Greetings,<br>
g<br>
</blockquote>
<br>
Gabriel, that's a quite good point. Are there more examples like
"New"? Would it solve the problem to have a context for each
occasion where "New" appears? (A "World" context, a "Texture"
context, ...)<br>
<br>
I created a small, incomplete list of ambiguous words:<br>
<br>
<ul>
<li>Scale -> operator, noun</li>
<li>Render -> operator, noun</li>
<li>Group -> operator, noun</li>
<li>Fill -> operator, noun</li>
<li>Mirror -> operator, noun</li>
<li>Change -> operator, noun</li>
<li>Set -> operator, noun</li>
</ul>
<br>
<ul>
<li>Manual -> noun, adjective</li>
<li>Light -> noun (sunlight), adjective (light fur)<br>
</li>
<li>Open -> operator, adjective</li>
<li>Clear -> operator, adjective</li>
</ul>
<br>
<ul>
<li>Delete -> operator, key context (on keyboard)</li>
<li>None -> context for each individual situation? (see "New"
above)<br>
</li>
<li>Volume -> no context (space), audio context<br>
</li>
<li>Rate -> no context, sampling context (or change to
"Sampling Rate" in code?)</li>
</ul>
<br>
What do you think about these solutions?<br>
<br>
<br>
Kind regards,<br>
Michael Färber<br>
</body>
</html>