diff options
Diffstat (limited to 'digikam/libs/dimg/README')
| -rw-r--r-- | digikam/libs/dimg/README | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/digikam/libs/dimg/README b/digikam/libs/dimg/README index 47e4a4c..4b13f3f 100644 --- a/digikam/libs/dimg/README +++ b/digikam/libs/dimg/README @@ -16,7 +16,7 @@ some imlib2 bugreports I reported to upstream have gone unfixed for long time now. Also, we need to think about 16bit imaging support. this won't come from -imlib2 and neither from qt. with qt4 there was hope of 16bit image +imlib2 and neither from tqt. with qt4 there was hope of 16bit image support, but trolltech has made it clear that imaging apps forms only 0.1% of their customer base and they are not interested in providing custom support for them. so the only solution I see (without depending on @@ -29,7 +29,7 @@ some of the working/planned features: * Native Image Loaders, for some imageformats which are of interest to us: JPEG (complete), TIFF (a rudimentary one currently), PNG (planned), PPM -(planned). for the rest qt's qimage is used. +(planned). for the rest tqt's qimage is used. * Metadata preservation: when a file is loaded, its metadata like XMP, IPTC, EXIF, JFIF are read and held in memory. now when you save back the @@ -39,7 +39,7 @@ imlib2 is on saving a file: we save the file to a temporary file, reread the exif info from the original file and then write to a second temporary file.) -* Explicitly Shared Container format (see qt docs): this is necessary for +* Explicitly Shared Container format (see tqt docs): this is necessary for performance reasons. * 8bit and 16bit support: if the file format is 16 bit, it will load up |