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

List:       kde-bugs-dist
Subject:    [Bug 138524] New: Krita does not properly parse GIMP palettes with no
From:       Juan Carlos Torres <carlosdgtorres () gmail ! com>
Date:       2006-12-08 8:24:27
Message-ID: 20061208092425.138524.carlosdgtorres () gmail ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=138524         
           Summary: Krita does not properly parse GIMP palettes with no tab
                    whitespace
           Product: krita
           Version: 1.6.1
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: krita-bugs-null kde org
        ReportedBy: carlosdgtorres gmail com


Version:           1.6.1 (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages
OS:                Linux

Krita's parser does not process lines in GIMP palette files that use spaces instead \
of a tab to separate the RGB color codes from the color name. 

The code is in kis_palette.cc, line 241:
 if (lines[i].contains("\t") > 0)

The parser recognizes only a tab as a valid separator to split the RGB code and the \
color name when checking whether the line is a valid palette entry. The GIMP, \
however, allows both tabs and spaces to be used in separating each component and \
parses the line correctly.

An example of GIMP palette that doesn't always use tabs is the Oxygen color palette. \
Only some of the lines use a tab, while others use spaces. As a result, only those \
lines with a tab are parsed and imported into Krita. The GIMP parses and imports all \
colors properly.

http://www.kde-artists.org/Oxygen-palette


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