This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 119605 - Any other words instead of "at {0}. position"?
Summary: Any other words instead of "at {0}. position"?
Status: VERIFIED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-22 07:22 UTC by Masaki Katakai
Modified: 2007-10-26 04:07 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
I guess users may not think "5. position" means "the fifth position". Not a good way as a hint. (73.28 KB, application/octet-stream)
2007-10-22 12:46 UTC, Rebecca Liu 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Masaki Katakai 2007-10-22 07:22:12 UTC 
These messages are being displayed as hint on form editor and I understand that "{0}." means the Nth position on the
layout. Do we really need "."? How about just "at {0} position" ? or any good word to represent by not using "."?

form/src/org/netbeans/modules/form/assistant/Bundle.properties:
# Layout managers
boxLayout=Place the component at {0}. position.
flowLayout=Place the component at {0}. position.
gridLayout=Place the component at {0}. position.
toolbarLayout=Place the component at {0}. position.

Our translation tool divided this line
  - Place the component at {0}. position.
to
  - Place the component at {0}.
  - position.
Because "." is located after {0}. Translation vendor reported this issue.

So I'd like to ask not to use "." in these lines so that I want to avoid this situation. Any idea?
Comment 1 Patrick Keegan 2007-10-22 09:55:35 UTC 
Can these simply be enumerated up to a reasonable value? First/second/third/fourth/fifth/sixth/ etc.? I don't imagine
that this would be a case where the number would get very high
Comment 2 Jan Stola 2007-10-22 10:03:34 UTC 
I am sorry, I don't see any reason to change that. I don't know what tools you are using and what they should 
accomplish, but it sounds more like problem of your tools or the process you are using. None of these justify change in 
text presented to user.
Comment 3 Patrick Keegan 2007-10-22 11:09:01 UTC 
That said, this current construction is somewhat awkward in English as well. We don't really use the construction "1."
to refer to "first" in English.
Comment 4 Rebecca Liu 2007-10-22 12:46:19 UTC 
Created attachment 51401 [details]
I guess users may not think "5. position" means "the fifth position". Not a good way as a hint.
Comment 5 Jan Stola 2007-10-22 13:17:26 UTC 
> We don't really use the construction "1." to refer to "first" in English.

So, what do you suggest? Is 'Place the component at position {0}.' better?

> Can these simply be enumerated up to a reasonable value?

We can enumerate to some fixed value, but we still need general version if we exceed this value.
Comment 6 Patrick Keegan 2007-10-22 14:16:14 UTC 
"Is 'Place the component at position {0}.' better?"

Yes.
Comment 7 Jan Stola 2007-10-22 14:56:23 UTC 
Changed to: Place the component at position {0}.

Modified file:
/cvs/form/src/org/netbeans/modules/form/assistant/Bundle.properties
new revision: 1.10; previous revision: 1.9
Comment 8 Rebecca Liu 2007-10-26 04:07:25 UTC 
Verified.