Hi Slavek,
Anno domini 2021 Sun, 4 Jul 15:55:53 +0200 Slávek Banko via tde-users scripsit:
Dne so 3. července 2021 12:35:42 Dr. Nikolaus Klepp napsal(a):
Anno domini 2021 Sat, 3 Jul 18:45:02 +0900
Michele Calgaro via tde-users scripsit:
On 2021/07/03 6:02:04 PM, Dr. Nikolaus Klepp wrote:
These 4 files are the only reason for python2.7 on my system and I do not see why it's actually needed any more.
yeah..... dropping python 2 and move to p:ython 3 is one of the things we want/need to do .... it will come at some point :-) Cheers Michele
Hi Michele,
could you plese check on your system if /opt/trinity/bin/jpegorient is used? On my 14.1 it looks like it is totally ignored. orient.py/exif.py also look like they are totally dysfunctinal - not only from konquaror, but from the commandline, too. /opt/trinity/bin/jpegorient (if it is needed) should use exiftools to modify image orientation and drop orient.py + exif.py.
Nik
Hi Nik
the jpegorient script is referenced as a service for Konqueror, which is provided for JPEG files. This script uses an "orient.py" that internally uses "exif.py". If these scripts are not successful, "jpegtran" is searched and used.
orent.py & exif.py are quite disfunctional on jpegs without exif. But where are these files used? I did not find nor see any difference in konqueror with or without jpegtran.
Here it may be a question of whether to deal with the modification of these scripts in order to be compatible with Python3 or whether to discard them and rely exclusively on jpegtran.
I'd suggest exiftool for reading/writing the orientation and jpegtran for destructive modifications. BTW, jpegtan-mmx is gone for ~ a decade now, might be time to clean up that code anyway :)
But still I don't see where/when jpegorient is called. Do you have an example for me how I can see that in action?
Nik
Cheers