Community
Participate
Working Groups
Build Identifier: 20120216-1857 A {0}' pattern appears in project properties. It should be replaced to the project name with single quote. The bug is in "Babel Language Pack for eclipse in Chinese (Traditional)". Reproducible: Always Steps to Reproduce: 1. Project->Properties 2. [Run/Debug Settings] 3. You can see {0}' as the screenshot attached
Created attachment 212213 [details] screenshot
Created attachment 212252 [details] CDT - Traditional Chinese Fixed in: http://build.eclipse.org/technology/babel/babel_language_packs/N20120307-1100/indigo/BabelLanguagePack-tools.cdt-zh_TW_3.7.0.v20120307112539.zip
Looks good now. Thanks.
Created attachment 212292 [details] {0}' in error box Intensionally trying to debug a bad code, and then {0}' appears in the error box for binary not found.
Hi Kit, As I saw {0}' again in several msg boxes, could you use the technique you used in Bug 342795 to fix this bug? The screenshot is produced by intensionally trying to debug a bad code.
This one is not as easy to fix as Bug 342795. We cannot replace all {0}' with '{0}' because that will change good strings like '{0}' to ''{0}'. If you can provide screen captures of the other message boxes, I can fix them one at a time... until I can come up with a safe fix to fix all occurrenecs.
Created attachment 212339 [details] CDT Problem Occurred - Traditional Chinese I fixed the string in comment 4. I also translated the string "Program file does not exist". Please try these 2 language packs: http://build.eclipse.org/technology/babel/babel_language_packs/N20120308-1300/indigo/BabelLanguagePack-eclipse-zh_TW_3.7.0.v20120308010028.zip http://build.eclipse.org/technology/babel/babel_language_packs/N20120308-1300/indigo/BabelLanguagePack-tools.cdt-zh_TW_3.7.0.v20120308010028.zip Problems you saw in other error message dialogs may be from the same string. Please try the language packs and let me know other problems. In the meantime, I will investigate on how to safely fix this completely.
I have an idea. Two search & replace steps: 1. '{0}' => {0}' 2. {0}' => '{0}'
It's been a while form last fix and I don't see {0}' pattern anymore since then. I think we can say the bug is fixed.