[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 128904] New: Character changes in source files
From:       Julien Torres <julien.torres () certess ! com>
Date:       2006-06-09 15:21:54
Message-ID: 20060609172153.128904.julien.torres () certess ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=128904         
           Summary: Character changes in source files
           Product: kdevelop
           Version: 3.3.2
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: julien.torres certess com


Version:           3.3.2 (using KDE KDE 3.5.2)
Installed from:    RedHat RPMs
Compiler:          gcc 4.02 
OS:                Linux

When editing a C file, if I type something like:

char* string = "éùçà ";   // some accentued chars
printf("%s\n",string);

It is perfectly allowed by the C compiler and the output is what I expect ("éùçà \
"). Nevertheless, depending on the encoding system, KDevelop may interpret and change \
these chars, leading to a wrong output of the program.

I think that KDevelop should NOT interpret or decode source file (or it may interpret \
or decode comments only). It should treat source files as "binary" files, not \
changing any chars of it, even if these chars have an ASCII code from 128 to 256.


[prev in list] [next in list] [prev in thread] [next in thread]