Author Topic: Config file documentation  (Read 371 times)

obetz

  • Sr. Member
  • ****
  • Posts: 252
Config file documentation
« on: March 10, 2020, 12:14:03 PM »
Hi Phil,

please consider an update of https://exiftool.org/config.html and example.config

Quote
To activate this file, rename it to ".ExifTool_config" and
place it in your home directory or the exiftool application
directory.  (On Windows and Mac systems this must be done via
the command line since the GUI's don't allow filenames to begin
with a dot.  Use the "rename" command in Windows or "mv" on the

Windows 10 Explorer can rename to .ExifTool_config

In Windows 7, one had to enter ".ExifTool_config.", but Windows 7 should not be used any more anyway.

Phil Harvey

  • ExifTool Author
  • Administrator
  • ExifTool Freak
  • *****
  • Posts: 16885
    • ExifTool Home Page
Re: Config file documentation
« Reply #1 on: March 10, 2020, 12:18:47 PM »
Thanks.  Changed to say "some Windows systems".

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

StarGeek

  • Global Moderator
  • ExifTool Freak
  • *****
  • Posts: 3964
Re: Config file documentation
« Reply #2 on: March 10, 2020, 12:34:09 PM »
How interesting.  I had re-tested this just a few months ago and it didn't work (Win 10 here).  But you're right, it works now.
Troubleshooting hints:
* When posting, include your OS, Exiftool version, and type of file you're processing (MP4, JPG, etc).
* Double all percent signs (%) in a Windows batch file.
* If your GPS coords are negative, make sure and set the GpsLatitudeRef and GpsLongitudeRef tags correctly.

obetz

  • Sr. Member
  • ****
  • Posts: 252
Re: Config file documentation
« Reply #3 on: March 10, 2020, 02:38:16 PM »
How interesting.  I had re-tested this just a few months ago and it didn't work (Win 10 here).  But you're right, it works now.

Thanks for the information. I'm using 19H1 (because Windows Search is broken in 19H2).

Windows slowly evolves...

Since a while, Windows Explorer even supports case sensitivity already present in NTFS since more than a decade.