Bug 53137 - CVS module should use " instead of ' for better other-than-english language support ...
Summary: CVS module should use " instead of ' for better other-than-english language s...
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: cvs (show other bugs)
Version: 0.9.94
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-18 16:55 UTC by Mario Scalas
Modified: 2010-12-16 19:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Scalas 2003-01-18 16:55:33 UTC
Version:            (using KDE KDE 3.0.99)
Installed from:    Compiled From Sources
Compiler:          Gcc 3.2.1 
OS:          Linux

Being Italian, the character ' (apostrophe or single quote) is used in common language expressions. Since gideon uses the single quote for quoting cvs parameters as in "cvs -m 'my message goes here'" the command fails when I use some very frequent (and to me, obvious) words. I believe that:
1) gideon should use double quote (") for quoting messages for cvs command;
or 
2) the label in the cvs options dialog should be modified to explain to not to use some characters;
or 
3) a check should be done to replace all characters with escaped ones (that is replacing ' with \').

Hope it is clear enough ;)
Comment 1 Harald Fernengel 2003-03-02 12:57:13 UTC
Can you check whether the bug existst in CVS HEAD? We use KShellProcess::quote now. 
 
We have to use single ' quotes to prevent malicious code, the shell won't try to interprete anything 
that's in single quotes. 
Comment 2 Mario Scalas 2003-03-05 15:40:50 UTC
No .. it remains ...  
 
 
cvs -d $CVSROOT init && cd /home/mario/provacvs && cvs -d $CVSROOT import -m 'Questo e' un 
bel progetto da provare ...' provacvs vendor start  
* *** Exited with status: 2 *** 
 
(For your information "e'" means "is" in english) 
I agree that if security must be enforced than a "validation" of the sentence inserted as CVS message  
must be used to reject unallowed characters ;) 
 
Comment 3 Harald Fernengel 2003-03-05 16:11:02 UTC
ah, sorry, I thought you meant messages during "cvs commit". "cvs import" messages are now also 
quoted (CVS HEAD), so the bug should be gone. 
 
Thanks for the info, 
Harry 
Comment 4 Mario Scalas 2003-03-05 19:18:18 UTC
Ok, just updated from CVS of this afternoon ;) And ... ehmm ... I believe it still is open:  
 
if i use the words:  
	I'm very happy to say that I fixed the bug ... 
the wizard will quote it as: 
	'I'm very happy to say that I fixed the bug ...' 
which is obviously wrong (will produce error when executing the command)! Nothing prevents the 
user from using single quote (') in the string (I mean, no message box, no label, nothing). 
Now I know about the problem and will avoid it but a new user? If you point me where to look I could 
work out a patch for this ... 
I addition I see that _all_ strings are single-quoted and this prevent the user from using env vars, as I 
do (like $CVSROOT='/home/cvsroot').