Community
Participate
Working Groups
OS: Linux Build date: 20070516 Component name : CDT Blocking: NO Tester Name: Eriko Takahashi (Japanese tester) Testcase: 13.001560 -- CDT - DEBUG PERSPECTIVE Steps to recreate the problem: 1. Create C++ project 2. Right click on the project name, choose Build configurations ->set active ->debug 3. Right click on the project name, choose "Build project" 4. "Debug" folder is created in the file system Problem Description: "Debug" is shown translated in the file system. For Japanese, we do not use national characters in the file system. Please help to separate the string used in the menu and the string used as a folder name in the file system. I think it's the same thing for the string, "Release". Please separate both the strings, "Debug" and "Release". Thank you. This article was reassigned from Category:''TVT Testcases''. Changed status to Working in TCT.
Created attachment 67698 [details] Debug.png
Created attachment 67699 [details] debug2.png
<cde:tctdetail> Testcase: Project: WSW33 Component: CDE - CDT/cdt-debug Priority: 2 Subject: ja: "Debug" and "Release" shared in the menu and in the file system Article ID: 273 Originator: ERIKOT@jp.ibm.com </cde:tctdetail>
Mikhail, Oleg, How hard would it be to separate the name of a configuration from the name of the directory that gets created on the filesystem for it?
Actually, would it make more sense to leave the configuration name untranslated?
(In reply to comment #5) > Actually, would it make more sense to leave the configuration name > untranslated? I don't think it is an easy task since a lot of code in MBS is assuming the build output directory has the same name as the configuration
(In reply to comment #6) > (In reply to comment #5) > > Actually, would it make more sense to leave the configuration name > > untranslated? > I don't think it is an easy task since a lot of code in MBS is assuming the > build output directory has the same name as the configuration sorry Jason I meant to reply to your comment# 4, i.e. separating the configuration name and the build directory name does not seem very easy and I would not do this change for the 4.0
(In reply to comment #5) > Actually, would it make more sense to leave the configuration name > untranslated? The configuration name was translatable in the 3.x so I would not remove the capability to translate the config name in the 4.0. I agree we should not translate the configuration names for the case of Japanese. But this would not solve the problem completely since the user is able to create new configurations or rename configuration. So we have the same issue in case the configuration is given a Japanese name. Probably the "rename configuration" and "create configruation" dialogs should contain some message to warn users about this issue, e.g. the Japanese translations of the titles for those dialogs could specify this.
Thanks for the feedback, Mikhail. (In reply to comment #8) > Probably the "rename configuration" and "create configruation" dialogs should > contain some message to warn users about this issue, e.g. the Japanese > translations of the titles for those dialogs could specify this. I agree. I think we should also leave a note for the translators in the relevant properties files so that they know "Debug" and "Config" will be used as directory names.
I'll take this one. I'll post a patch in a bit.
Created attachment 67856 [details] Proposed patch Mikhail, this patch implements what we discussed above. Would you mind having a look? Thanks, Jason
Warning: Unable to attach Proposed_patch due to lack of extension on the filename.
I'll take a look.
I've made some changes to the patch and applied it to HEAD. Thanks Jay! Instead of putting a note to translators in the properties file and ask them to make sure translations for the default configuration names will work for their platform, I've just made the names "Debug" and "Release" not translatable. The translators probably won't be able to determine if their translations will work or not since they do not do testing themselves.
This problem is fixed. Thanks! Eriko Takahashi
