| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
GIMP 3.04 opens with wind...
Forum: Windows
Last Post: subbareddy
Today, 07:47 AM
» Replies: 7
» Views: 3,702
|
Isolate, select and copy/...
Forum: General questions
Last Post: rich2005
Yesterday, 04:39 PM
» Replies: 7
» Views: 379
|
"Plug-in crashed" on GIMP...
Forum: General questions
Last Post: skullamrotis
Yesterday, 03:32 PM
» Replies: 4
» Views: 399
|
AIMAGoR - Artificial IMAg...
Forum: Other graphics software
Last Post: vitforlinux
Yesterday, 12:09 PM
» Replies: 23
» Views: 9,819
|
RapidRAW
Forum: Other graphics software
Last Post: denzjos
11-03-2025, 12:51 PM
» Replies: 2
» Views: 209
|
Tutoriel installer Drea...
Forum: Tutorials and tips
Last Post: meric57
11-03-2025, 07:45 AM
» Replies: 0
» Views: 92
|
Nouveau Arrivant sur le f...
Forum: Watercooler
Last Post: meric57
11-03-2025, 06:45 AM
» Replies: 0
» Views: 94
|
Accessing GIMP’s internal...
Forum: General questions
Last Post: rich2005
11-02-2025, 12:35 PM
» Replies: 1
» Views: 186
|
Can't find path plug-in
Forum: General questions
Last Post: programmer_ceds
11-01-2025, 04:47 PM
» Replies: 7
» Views: 485
|
Gimp shows blank black sc...
Forum: Windows
Last Post: rich2005
11-01-2025, 09:01 AM
» Replies: 1
» Views: 184
|
|
|
| Gimp 2.10 / Linux: Keyboard equivalent to Shift+Left-Mouse-Click |
|
Posted by: lawlist - 09-19-2022, 06:21 PM - Forum: General questions
- Replies (6)
|
 |
I'm running Gimp 2.10 on Linux (Ubuntu 20.04 LTS). Without using the mouse, is it possible to select a layer and make it visible, and hide all other layers? E.g., a sequence of keyboard entries that can accomplish the same thing as using the mouse to Shift+Left-Mouse-Click on the eye-icon area to the left of each layer in the applicable toolbox tab?
|
|
|
| Gimp 2.10 / linux: How to export PDF with searchable text. |
|
Posted by: lawlist - 09-19-2022, 06:15 PM - Forum: General questions
- Replies (2)
|
 |
I'm using Gimp 2.10 on Linux (Ubuntu 20.04 LTS). I import a multi-page PDF with searchable text into Gimp as layers. I add a signature JPG file to one or more of the pages and then Export as a FILE.PDF. The resulting PDF is not text searchable; e.g., I cannot select a sentence in the exported PDF with the mouse and then copy it to the clipboard. Is it possible to Export to PDF and have the resulting PDF searchable with text?
|
|
|
| Having trouble adding user interface options. |
|
Posted by: Albedo - 09-18-2022, 03:37 PM - Forum: Scripting questions
- Replies (4)
|
 |
Hi
I am having an issue adding UI stuff to my script. I am unable to use two UI of the same type. I think I'm missing something in my formatting. For example:
(PF_OPTION, "useRare", "Select N to Ignore Rare Percents. ", 0,
(
["N", "Y"]
)
)
That works fine. I am able to get the Y/N info passed into my useRare parameter. I am able to to pass it to scripts, no issue. The problem is I want to add another PF_OPTION. So I added
(PF_OPTION, "useColor", "Select Y to use color ", 0,
(
["N", "Y"]
)
)
And that breaks my script. I can add a PF_RADIO, or a PF_TOGGLE and they work fine too, but I cant add a duplicate for either of those. Can anyone explain to me how I can enter into duplicate PF types to the UI?
Thank you
|
|
|
| What is the basis for metadata contained in image files produced by GIMP? |
|
Posted by: ajax - 09-16-2022, 09:15 PM - Forum: General questions
- Replies (3)
|
 |
Have been using GIMP for long enough to remember when it just couldn't handle metadata. Have been pleased to see that change such that metadata is included. The documentation (i.e., User guide) on this subject has also been a work in progress and seems to lack reliability. For example, the User Guide includes text at the beginning of the main section which says "Note: ... PNG, JPEG, TIFF and WebP preserve existing metadata. ...". Then when reaching down into the more detailed explanations, for Exif data, there is text which says "It is not supported in JPEG 2000 or PNG.". Pretty much adds up to a direct contradiction.
When working with photographs, which is the basis for this post, the idea of simply preserving the metadata produced by the camera is desirable. In the case of Exif data there is a standard which is thought to apply to cameras (i.e., files produced by cameras). This means that post processing software like GIMP and lots of others ought NOT be changing it. Must admit it took a while to notice but that is NOT the case.
It seems that GIMP recognizes different types of metadata to include Exif, XMP, & IPTC. There is also something called Makernotes which is produced by cameras where the term "maker" is believed to mean that it is specific to a particular camera (i.e., proprietary rather than a universal standard). It appears as though post processing software, to include GIMP, treat this as though it is Exif data. For example, GIMP includes it when Exif inclusion is specified for image files to be created and excludes it otherwise.
The new finding is that the Exif metadata included in image files created by GIMP closely resembles what the camera produced. However, one discrepancy involves GIMP adding tags to describe the dimensions of the new image file along with bit depth which is flat out wrong (i.e., Bits per sample: 8 8 8 in the case of an image file with 16 bit precision). It has been noticed the cameras are prone to making this same mistake but that might could be reconciled by saying it applies to the preview image whereas in the example mentioned there is no thumbnail or preview image.
When it comes to Makernotes such minor discrepancies are no longer the case. The differences are major. For example, as much as 30% of tags are simply omitted. Given that Makernotes are particular to the camera it would be expected that GIMP ought NOT be changing anything. What scenario would call for GIMP making such alterations to be desirable? Thinking here is that it would be better for GIMP to omit the Makernotes rather than make changes. What reason might there be for doing this.
Afraid these new discoveries suggest that, at least for Exif data, GIMP's support is more destructive than productive.
|
|
|
|