Community
Participate
Working Groups
<response_by> martine marin at 2008.06.04.14.20.53 </response_by> OS: Linux/Windows Build: 0602 Component: CDT testcase: 05.001650 Steps to reproduce Select General -> Keys. Type C++ to filter out non-CDT key bindings There is a space missing before the colon sign in expression between parenthesis (punctuation seemed to be added by the system) Thanks, Martine <response_by> Karl Mittmann at 2008.06.04.15.59.55 </response_by> This article was reassigned from Category:''TVT/Testing,Inbox''. <response_by> Karl Mittmann at 2008.06.04.16.00.20 </response_by> This comment was made to a similar previous case, "I will add special processing to our colon handling for this release for French locales. This will be removed in next release when we will remove all specialized colon processing. See bug 231675."
Created attachment 103650 [details] 05_001650.gif
<cde:tctdetail> Testcase: 05.001650 Project: WSW34 Component: Xfer - CDT/UI Priority: 2 Subject: TVT FR - CDT - Space missing before colon sign Article ID: 738 Originator: mmarin@fr.ibm.com </cde:tctdetail>
The strings in question are used in an extension point. So the concatenation of the strings (with the colon) are done by Platform.
That's not part of a sentence (and hence no grammar). It's simply specifying optional command parameters->possible values (map of tuples). Unless there's some specific examples of this that need to work differently, this is WONTFIX. PW
Paul, do you know if the parenthesis and colon are inserted programmatically or not? Is it possible to externalize a string like "{0} ({1}: {2})" and use MessageFormat to subsitute {0}, {1} and {2} with commandName, commandParm, and value? That way, if a language chooses to, they can add the space in front of the colon.
I could allow ParameterizedCommand getName() to use a ResourceBundle for the patterns in 3.5. (parm, parm, parm) is one pattern, and for each individual parm it is parmName: parmValue If it is a standard in French that these kind of tuple maps are parmName : parmValue. PW
Thanks Paul, that sounds good. Can that be done in 3.4.1?
(In reply to comment #7) > Thanks Paul, that sounds good. Can that be done in 3.4.1? > I'm waiting to hear that parmName : parmValue is a requirement in French first (i.e. no one would ever write parmName: parmValue). But no, it would not be done until 3.5 PW
<response_by> martine marin at 2008.06.09.09.10.39 </response_by> Can you give a status Deferred for this defect? Thanks a lot in advance, Martine
<response_by> martine marin at 2008.06.09.14.07.47 </response_by> Hi, Yes this is standard in French, there is always a space in front of the colon sign in French (also for question marks and other punctuation items). Please fix and/or defer this defect. Thanks, Martine
<response_by> John Ryding at 2008.06.12.10.13.05 </response_by> This has been deferred. It will be considered for the 3.4.1 service pack.
Updated as per http://wiki.eclipse.org/Platform_UI/Bug_Triage PW
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
