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

List:       kde-bugs-dist
Subject:    [kcm_grub2] [Bug 319947] Crash - after  Click to applie Grub2 Changes
From:       Lux <luxexcudo () arcor ! de>
Date:       2013-06-05 9:23:00
Message-ID: bug-319947-17878-VTBUUIacUQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=319947

--- Comment #14 from Lux <luxexcudo@arcor.de> ---
Hi,

Thanks for taking time to explain it to me, it's ok with  the technical stuff,
(when i was programming linenummbers were used "GOTO" in Basic ;-)
Right now, i just do a bit Shell.
... Ubuntu 13.04 updates the complete  KDE 4.10.2 to 4.10.3  right now, 
big pack (299 Packages at once)! 
Have a nice day :-)

Phil[Lux]


Am Dienstag, 4. Juni 2013, 21:46:02 schrieben Sie:
> https://bugs.kde.org/show_bug.cgi?id=319947
> 
> --- Comment #13 from Konstantinos Smanis <konstantinos.smanis@gmail.com> ---
> ImageMagick expects strings using std::string (the string class defined in
> the standard C++ library). Qt on the other hand, and KDE as an extension,
> uses QString, a string class used universally within Qt. While converting
> from QString to std::string there was loss of information (in this case the
> umlaute). This was really my mistake, I never noticed this issue because I
> mostly use Latin-only filenames. In fact, there is a big fat warning in the
> developer's documentation about it:
> 
> "Returns a std::string object with the data contained in this QString. The
> Unicode data is converted into 8-bit characters using the toAscii()
> function. This operator is mostly useful to pass a QString to a function
> that accepts a std::string object.
> If the QString contains Unicode characters that the
> QTextCodec::codecForCStrings() codec cannot handle, using this operator can
> lead to loss of information."
> 
> In any case, I should have taken care of any exceptions thrown by
> ImageMagick, so that it would just fail, not crash the whole module. Sorry
> for the bit technical response, this issue will have been taken care of in
> the next release, whenever this will be.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]