Photini Documentation Release 2017.6.0.dev819
Jim Easterbrook
Jun 02, 2017
Contents
1 Introduction 3 1.1 Features...... 4 1.2 Dependencies...... 5 1.3 Getting help...... 6 1.4 Internationalisation...... 6 1.5 Licence...... 6
2 Installation 9 2.1 All-in-one installer (Windows)...... 9 2.2 Package manager (some Linux distributions)...... 10 2.3 Dependencies package (some Linux distributions)...... 10 2.4 Piecemeal installation...... 11 2.5 Essential dependencies...... 11 2.6 Installing Photini...... 12 2.7 Running Photini...... 14 2.8 Photini documentation...... 14
3 User manual 17 3.1 Image selector...... 17 3.2 Descriptive metadata...... 23 3.3 Technical metadata...... 29 3.4 Geotagging...... 39 3.5 Flickr uploader...... 53 3.6 Google Photos / Picasa uploader...... 60 3.7 Facebook uploader...... 66 3.8 Image importer...... 77 3.9 Configuration...... 82 3.10 Tag reference...... 84
4 Typical workflow 89 4.1 Make a backup copy...... 89 4.2 Load images...... 89 4.3 Set text metadata...... 90 4.4 Save your work so far...... 90 4.5 Set geolocation...... 90
5 “Localisation” 91
i 5.1 Join Transifex...... 92 5.2 Translating Photini...... 92 5.3 Testing your translations...... 93
6 Miscellaneous 95 6.1 Change Log...... 95 6.2 GNU General Public License...... 98 6.3 GNU Free Documentation License...... 110
7 Further reading 119
ii Photini Documentation, Release 2017.6.0.dev819
Welcome to the documentation of Photini, an easy to use photograph metadata editor. For a quick introduction to Photini and its features I suggest you read the introduction. More detail about its capabilities can be found in the user manual.
Contents 1 Photini Documentation, Release 2017.6.0.dev819
2 Contents CHAPTER 1
Introduction
A free, easy to use, digital photograph metadata (EXIF, IPTC, XMP) editing application. “Metadata” is said to mean “data about data”. In the context of digital photographs this means information that isn’t essential in order to display the image, but tells you something about it. For example a title and description of the scene or the date & time and the GPS coordinates of the camera’s position when the picture was taken. “[Photini] doesn’t try to be an all-singing, all-dancing image management powerhouse - it just lets you add information to photos, quickly and easily.” —Linux Format magazine, January 2013 Why is it called Photini? Read my blog post on how I chose a name.
3 Photini Documentation, Release 2017.6.0.dev819
Features
• Easy to use graphical interface. • Set photo title, description, keywords, copyright and creator fields. • Spell checking of some fields (optional). • Can set metadata for multiple images simultaneously. • Can adjust picture date & time and time zone (of multiple images simultaneously). • Reads EXIF, IPTC and XMP metadata, writes all three to maximise compatibility with other software. • Writes metadata to image files or to XMP “sidecar” files. • Can import photographs from many digital cameras. • Upload to Flickr and/or Facebook and/or Google Photos with reuse of metadata.
4 Chapter 1. Introduction Photini Documentation, Release 2017.6.0.dev819
• Geotagging - search map to find named places. • Choice of map providers - instantly switch to compare details. • Drag and drop images on to map to set GPS location. • Edit coordinates if required, or clear to unset GPS data. • Suggestions for further development welcome.
Dependencies
An “all in one” installer for Windows is available that installs Photini and all its dependencies. Users of other operating systems will need to install the following: • Python, version 2.6+ (including Python 3): http://python.org/ • PyQt, version 4 or 5: http://www.riverbankcomputing.co.uk/software/pyqt/intro • six, version 1.5+: https://pypi.python.org/pypi/six/ • appdirs, version 1.3+: http://pypi.python.org/pypi/appdirs/ • gexiv2 (GObject Exiv2 wrapper), version 0.5+: https://wiki.gnome.org/Projects/gexiv2
1.2. Dependencies 5 Photini Documentation, Release 2017.6.0.dev819
• Python GObject bindings: – PyGObject: https://wiki.gnome.org/Projects/PyGObject or – pgi: https://pypi.python.org/pypi/pgi/ For details of how to download and install these, please see the installation documentation.
Getting help
If you encounter any problems installing or running Photini, please email [email protected] and I’ll respond as soon as I can. If you discover a bug and have a GitHub account then please file a bug report on the GitHub “issues” page.
Internationalisation
Work has begun on providing Photini in multiple languages. I rely on users to do the translation, as I am not fluent in any language other than English. If you’d like to help, please join the Photini team on Transifex. For more details, see the localisation documentation.
Licence
Photini - a simple photo metadata editor. http://github.com/jim-easterbrook/Photini Copyright (C) 2012-17 Jim Easterbrook [email protected]
German translation by Jan Rimmek Spanish translation by Esteban Martinena & Cristos Ruiz Polish translation by “itdawid”
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http: //www.gnu.org/licenses/.
Service terms and conditions
Use of the Google map tab is subject to the Google Maps Terms of Use and Google Privacy Policy. Use of the Bing map tab is subject to the Microsoft Bing Maps Terms of Use and Microsoft Privacy Statement. The Flickr upload tab uses the Flickr API but is not endorsed or certified by Flickr.
6 Chapter 1. Introduction Photini Documentation, Release 2017.6.0.dev819
Privacy statement
Photini does not directly gather any information from its users, but the online services it can use (maps, Flickr, Face- book, and Google Photos) may do so. You should read these services’ privacy policies before using them. Photini stores user preferences in a text file on the user’s computer. This file can be found in $HOME/.config/ photini/ (Linux) or %USERPROFILE%\AppData\Local\photini\ (Windows). OAuth access tokens for Flickr, Facebook, and Google Photos are securely stored on the user’s computer using Python keyring.
Documentation licence
Permission is granted to copy, distribute and/or modify the Photini documentation under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the documentation section entitled “GNU Free Documentation License”.
1.5. Licence 7 Photini Documentation, Release 2017.6.0.dev819
8 Chapter 1. Introduction CHAPTER 2
Installation
There are three ways to install Photini. On Windows you can use an all-in-one installer. On some Linux distributions you might be able to use your package manager to install everything, or you may be able to use the package manager to install Photini’s dependencies and pip to install Photini. On other platforms you need to install several dependencies before installing Photini.
All-in-one installer (Windows)
The Windows installer creates a standalone Python installation with all the dependencies needed to run Photini. The standalone Python interpreter is only used to run Photini, and should not conflict with any other Python version installed on your computer. You can download the latest Windows installer from the GitHub releases page. It’s the file photini-win32-setup.exe included in the “downloads” section of the latest release. The installer is suitable for 32 bit and 64 bit Windows, and should work on any version since Windows XP. The installer should finish by running the Photini program. If this works then you have successfully installed Photini and can ignore the rest of these instructions. If not, see the troubleshooting section below.
Upgrading all-in-one installation
Before upgrading Photini you should check the change log to see if a new installer has been released since you last downloaded it. If it hasn’t, then you can use the “upgrade Photini” command in the start menu. This needs to be run as administrator. Click on the “Start” icon, then select “All Programs”, then “Photini”, then right-click on “upgrade Photini” and choose “Run as administrator” from the context menu. If there is a new installer available then you should download it and use it to create a fresh installation, after using the “Programs and Features” control panel item to uninstall the old version of Photini.
9 Photini Documentation, Release 2017.6.0.dev819
Verifying the Windows installer
The Windows installer is digitally signed using a “self-signed Certificate Authority”. If you add my certificate to your computer you will get fewer security warnings when you install Photini. You can download the certificate file jim_easterbrook_CA.cer from the GitHub releases page and install it by running cmd.exe and issuing the following command: certutil-user-addstore Root jim_easterbrook_CA.cer
If you want to check the validity of the certificate file, you can do so using GnuPG. The file jim_easterbrook_CA.cer.asc contains a digital signature that can be checked with my public keys 0x959AF9B6 or 0x4748AD59 (a subkey of 0x2036BBF6). These keys’ fingerprints are 05A7 0CD9 380D 8EAA 97AE FD3F 56D7 01F5 959A F9B6 and 45A2 B27B AC1D 12B2 5C33 655C 7CF4 E704 2036 BBF6. If the above means nothing to you, don’t worry about it. The security warnings when you install Photini can safely be ignored.
Package manager (some Linux distributions)
Note: These Linux packages are maintained by other people and may not install the latest version of Photini. You may also need to install missing dependencies, as described below.
Ubuntu and derived systems
Dariusz Duma (https://launchpad.net/~dhor) has added Photini to his PPA (personal package archive). See the instruc- tions at http://linuxg.net/how-to-install-photini-15-01-1-on-ubuntu-14-10-ubuntu-14-04-and-derivative-systems/. Pascal Mons (https://launchpad.net/~anton+) also has a PPA with many photo applications, including Photini. See https://launchpad.net/~anton+/+archive/ubuntu/photo-video-apps/.
OpenSUSE 42.2 or newer
Photini is available from the Packman community repository. It can be installed by clicking on this link: http:// packman.links2linux.org/install/Photini
OpenSUSE and Fedora
Togan Muftuoglu (https://build.opensuse.org/user/show/toganm) has created a python-photini package. See https: //build.opensuse.org/package/show/home:toganm:photography/python-photini for more information.
Dependencies package (some Linux distributions)
This is the easiest way to install Photini’s dependencies and the latest release of Photini. You use your package manager to install the non-Python dependencies, then use pip to install the latest versions of all the Python packages.
10 Chapter 2. Installation Photini Documentation, Release 2017.6.0.dev819
OpenSUSE (and other Red Hat derived distributions?)
The Photini project includes a .spec file that lists the required dependencies. Download the .spec file and use it to build a .rpm file:
wget https://raw.githubusercontent.com/jim-easterbrook/Photini/master/src/linux/
˓→python3-photini-meta.spec rpmbuild-ba python3-photini-meta.spec
Note where rpmbuild wrote its output file, then install that file. For example:
sudo zypper install/home/jim/rpmbuild/RPMS/noarch/python3-photini-meta-1-0.noarch.rpm
Now you can install Photini using pip as described below.
Piecemeal installation
This is the hardest way to install Photini, mainly because of the libraries required to access photographs’ metadata. The installation process is different for Windows, Linux and MacOS, and there are variations with different versions of those operating systems. If you run into problems, please let me know (email [email protected]) and once we’ve worked out what needs to be done I’ll be able to improve these instructions.
Essential dependencies
These are all required for Photini to be usable.
Python
Photini should work with all versions of Python from 2.6 onwards. Python may already be installed on your computer. To find out, open a terminal window (Windows users run cmd. exe) and try running python by typing this command:
python-V
If Python is installed this should show you the version number. Linux users should use their system’s package manager to install Python. Windows and MacOS users can download an installer from https://www.python.org/downloads/. Windows users should install the 32 bit version of Python, even on a 64 bit machine. This is because some of the required libraries are not available in 64 bit builds.
PyQt
The PyQt application framework provides the graphical user interface elements used by Photini. Version 4 or 5 is required. You can check if PyQt is already installed with one of these commands:
python-c"import PyQt5"
or
2.4. Piecemeal installation 11 Photini Documentation, Release 2017.6.0.dev819
python-c"import PyQt4"
If PyQt is installed then one of these will run without generating any error message. Linux users should use their package manager to install python-qt4 or python-qt5. On some Linux systems you may also need to install the Qt WebKit package, e.g. qt5-webkit. Windows users can download a binary installer from http://www.riverbankcomputing.co.uk/software/pyqt/download (make sure you choose the installer for your version of Python). gexiv2
Several libraries are needed to access photograph metadata from Python. Exiv2 is the core “C” library. gexiv2 is a GObject wrapper around the Exiv2 library. It has extra “introspection bindings” that allow it to be used by other languages. PyGObject (also known as PyGI) provides a Python interface to the introspection bindings of the GObject wrapper around the Exiv2 library. Got that? Linux users should use their package manager to install these, but note that the package names may not be obvious. The core gexiv2 wrapper is probably called libgexiv2 or similar, but on my OpenSUSE system the introspection bind- ings are called typelib-1_0-GExiv2-0_4 whereas on Ubuntu systems they are called gir1.2-gexiv2-0.4. The PyGObject interface probably appears in the package manager as python-gobject or python-gi. Windows users should download and run the latest “pygi-aio” (PyGI all-in-one) installer from http://sourceforge.net/ projects/pygobjectwin32/files/. You should install the “Base packages” & “GExiv2” packages, and the “Enchant- extra-dicts” non-GNOME library. pip
The remaining dependencies are Python packages that are easily installed with pip. You may already have pip installed on your computer. You can check with the pip list command: pip list
Linux users should use their package manager to install python-pip. Windows and MacOS users can use the installer from https://pip.pypa.io/en/latest/installing.html#install-pip. All users should then upgrade pip.
Installing Photini
The easiest way to install the latest release of Photini is with the pip command: sudo pip install photini
This will install Photini and any Python packages it requires. You can also use pip to install the optional dependencies when you install Photini: sudo pip install photini[flickr,google,facebook,importer,spelling]
If you prefer to install the development version you can use git to clone the GitHub repository or download it as a zip file and then unpack it. Either way, you then need to build and install Photini: python setup.py build sudo python setup.py install
You will also need to install the remaining Python packages.
12 Chapter 2. Installation Photini Documentation, Release 2017.6.0.dev819
Essential Python packages
There are two small Python packages needed to run Photini. They can be installed with one command: sudo pip install six appdirs
Note that sudo is not required on Windows, or if you have root privileges. In this case you just run pip install six appdirs.
Optional Python packages
Some of Photini’s features are optional - if you don’t install these libraries Photini will work but the relevant feature will not be available.
Spelling
PyEnchant is a Python interface to the Enchant spell-checking library. If it is installed then spell checking is available for some of Photini’s text entry fields. Use pip to install it: sudo pip install pyenchant
Flickr
Photini’s Flickr uploader requires python-flickrapi and python-keyring. These are easily installed with pip: sudo pip install flickrapi keyring
Google Photos / Picasa
The Google Photos / Picasa uploader requires requests, requests-oauthlib and python-keyring. These are also installed with pip: sudo pip install requests requests-oauthlib keyring
The Facebook uploader requires requests, requests-oauthlib, requests-toolbelt and python-keyring. These are also installed with pip: sudo pip install requests requests-oauthlib requests-toolbelt keyring
The Optimise image size option requires the Python Imaging Library, which is also installed with pip: sudo pip install Pillow
2.6. Installing Photini 13 Photini Documentation, Release 2017.6.0.dev819
Importer
Photini can import pictures from any directory on your computer (e.g. a memory card) but on Linux and MacOS systems it can also import directly from a camera. This requires libgphoto2, which is often already installed, and its python-gphoto2 Python bindings, version 0.10 or greater:
sudo pip install-v gphoto2
Installation of python-gphoto2 will require the “development headers” versions of Python and libgphoto2. You should be able to install these with your system package manager.
pgi
If you find the PyGObject bindings to be unreliable (I found they sometimes crash when using Python 3) you can use pgi instead:
sudo pip install pgi
Note that pgi may also have problems. If you need to go back to using PyGObject you should uninstall pgi:
sudo pip uninstall pgi
Running Photini
If the installation has been successful you should be able to run Photini from the “Start” menu (Windows) or application launcher (Linux).
Troubleshooting
If Photini fails to run for some reason you may be able to find out why by trying to run it in a command window. On Windows you need to open the folder where Photini is installed (probably C:\Program Files (x86)\Photini) and run the WinPython Command Prompt.exe program. On Linux you can run any ter- minal or console program. Start the Photini program as follows. If it fails to run you should get some diagnostic information:
python-m photini.editor
If you need more help, please email [email protected]. It would probably be helpful to copy any diagnostic messages into your email. If Photini runs but you have some other problem with it then I would find it useful to know what version you are running. You can find out with the --version option:
python-m photini.editor--version
Photini documentation
If you would like to have a local copy of the Photini documentation, and have downloaded or cloned the source files, you can install Sphinx and use setup.py to “compile” the documentation:
14 Chapter 2. Installation Photini Documentation, Release 2017.6.0.dev819
sudo pip install sphinx python-B setup.py build_sphinx
Open doc/html/index.html with a web browser to read the local documentation.
2.8. Photini documentation 15 Photini Documentation, Release 2017.6.0.dev819
16 Chapter 2. Installation CHAPTER 3
User manual
This manual attempts to cover every part of Photini in detail, but still be usable as a tutorial. I suggest you read the image selector and descriptive metadata sections first, then read other sections when you start using the relevant features.
Image selector
When you start the Photini editor it displays a GUI (graphical user interface) as shown below. The exact appearance will depend on your operating system and window manager preferences, but the same functional elements should be present.
17 Photini Documentation, Release 2017.6.0.dev819
The Photini editor GUI has two main areas. The upper part has a set of tabs to select different functions. The lower part is an image selector that is common to all the tabs. In between the two is a divider that can be dragged with the mouse to change the relative sizes of the two parts. The overall size of the window can also be changed by dragging its edges or corners with the mouse.
18 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Now load some images using the File menu Open images item (or its keyboard shortcut Ctrl+O) or by “drag and drop” from a file manager window. The loaded images are displayed as thumbnail images in the image selector part of the GUI. Note that the thumbnail size can be changed with the slider control just beneath the thumbnail display area. The images can also be sorted by name or date by clicking on the appropriate button.
3.1. Image selector 19 Photini Documentation, Release 2017.6.0.dev819
Clicking on any thumbnail selects that image. The selected image is highlighted by a red border. Double clicking on a thumbnail should display the full size image, using your default image viewing application.
20 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Multiple images can be selected by holding down the ‘shift’ key while clicking on a second image.
3.1. Image selector 21 Photini Documentation, Release 2017.6.0.dev819
To select multiple images that are not adjacent, hold down the ‘control’ key while clicking on the images.
22 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The keyboard shortcut Ctrl+A selects all the loaded images.
Descriptive metadata
The Descriptive metadata tab (keyboard shortcut Alt+D) allows you to edit basic information about your photographs, such as the title and description.
3.2. Descriptive metadata 23 Photini Documentation, Release 2017.6.0.dev819
The first thing I usually do with a new set of photographs is to set the copyright and creator/artist metadata. Select all the images (keyboard shortcut Ctrl+A) then click on the Auto button next to the Copyright text entry box. The first time you do this Photini asks you to provide the name of the copyright holder. This should probably be your name, but could be the name of a company. Type in the name and click OK. The Auto button generates a standard copyright notice, but if you prefer a different wording you can edit the text manually.
24 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Next click on the Creator / Artist field’s Auto button. Now Photini will ask for the name of the creator. Edit the name if required, then click OK. Note that all the image thumbnails now have a warning symbol () displayed next to them. This shows that they have unsaved metadata edits. The File menu Save images with new data item (keyboard shortcut Ctrl+S) saves your edits and clears the warning symbols, as shown below. I do this frequently to avoid losing any of my work.
3.2. Descriptive metadata 25 Photini Documentation, Release 2017.6.0.dev819
Next I set the title. Select all the images that should have the same title, then type the title in the Title / Object name text editing box. Note that the title (and keywords) are stored in XMP but not in Exif, so may not be visible to software that only handles Exif metadata (see Tag reference for more detail). You may prefer to leave the title and keywords fields blank. The Title / Object name field has an optional spell checker, enabled with the Spelling menu. The word “Château-Gontier” is not in the British English dictionary, as indicated by the red underlining. Right-clicking on a misspelled word shows a list of suggested alternatives, one of which can be chosen by clicking on it.
26 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Now you can add more detail in the Description / Caption box. There are probably only one or two pho- tographs that share the same description, so select those images first.
3.2. Descriptive metadata 27 Photini Documentation, Release 2017.6.0.dev819
Finally you can set a list of keywords for the image by typing them in the Keywords box. Keywords should be separated by semi-colon (;) characters. The
28 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Technical metadata
The Technical metadata tab (keyboard shortcut Alt+T) allows you to edit ‘technical’ information about your photographs, such as the date & time they were taken and the lens that was used (if your camera has interchangable lenses). Usually you do not need to edit any of this data, but I like to set the time zone of all my pictures, especially when I’m holidaying in another country.
3.3. Technical metadata 29 Photini Documentation, Release 2017.6.0.dev819
The GUI shows three date/time entries - taken, digitised and modified. These are often the same, and are linked by the link ... check boxes. These allow you to change all three when you change the taken date/time. You may wish to unlink the three entries and adjust the dates or times separately. For example, you could use the modified entry to note when you have edited the metadata with Photini. If you scan some old photographs you should set the taken entry to when the photographs were taken and the digitised entry to when you scanned them. The date can be picked from a calendar widget that pops up when you click on the down arrow in a date/time entry. Clicking on any of the numbers allows them to be adjusted with your keyboard up & down arrow keys. You can also double click on any of the numbers to select it and type a new value in directly.
30 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
To the right of each date/time is a widget to adjust the time zone. The time a photograph was taken is assumed to be “local time”. The time zone records how many hours & minutes offset from UTC (or GMT) the local time zone was when the photograph was taken, digitised or modified.
3.3. Technical metadata 31 Photini Documentation, Release 2017.6.0.dev819
The Adjust times field allows a constant offset to be applied to the time stamps of several pictures at once. This can be useful if you are in a different time zone to your camera’s setting or you forgot to set your camera’s clock before a day’s shooting! Set the required offset hours, minutes & seconds, then use the + or - button to add or subtract that amount from each selected picture’s timestamp.
32 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
You can also offset the time zone. In this example my camera clock was set to British Summer Time (+01:00) but records timestamps without zone information. I was on holiday in mainland Europe (+02:00) so I need to add 1 hour to each timestamp and 2 hours to the time zone. The Adjust times values are stored in Photini’s configuration file, so each day’s photos can be given the same offset with just one button click.
3.3. Technical metadata 33 Photini Documentation, Release 2017.6.0.dev819
Below each date/time is a slider that allows you to set the precision. At its maximum value the time is shown to a precision of 1 millisecond. Cameras that can take more than one photograph per second need this precision! Moving the slider to the left removes parts of the date & time. For example, you may know the date when an old photograph was taken but not the time. You might only know the year it was taken in. Setting the precision allows you to record this uncertainty. The Orientation value sets the required rotation or reflection to display the image. Note that this does not actually transform the image data. Image display programs should rotate or reflect the image according to the orientation metadata, but not all of them do. The Lens model dropdown list allows you to change the lens specification stored in the image metadata. This should usually be left blank for cameras with non-removable lenses, but may be useful if you have an SLR that you use with lenses that its electronics doesn’t recognise. Lens details already in a photograph’s metadata are automatically added to the list when the photograph is loaded. If your camera doesn’t record the details of some lenses you can add them by selecting
34 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
This brings up a dialog box for you to enter the lens details. Type all the relevant information into the appropriate boxes, leaving blank any information you don’t have such as the serial number. Only the Model name and Minimum focal length are required.
3.3. Technical metadata 35 Photini Documentation, Release 2017.6.0.dev819
The data you enter is stored in the Photini configuration file so you can easily apply it to images in future by selecting the lens you have defined from the dropdown list. To remove a lens from the list right-click on it to bring up its context menu. This includes options to delete any lens but the one currently in use.
36 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Adjusting the lens metadata is useful if, like me, you use your camera with 3rd party lenses and/or telescopes via a T-thread adaptor. My adaptor identifies itself to the camera as a 50mm f/1.8 lens. Here I’ve used it with my 500mm mirror lens to take some pictures of the moon.
3.3. Technical metadata 37 Photini Documentation, Release 2017.6.0.dev819
When I set the lens model via the drop down list Photini offers the option to adjust the focal length and aperture used for each image, if the current values are inconsistent with the new lens. In this case I definitely do want to update these parameters so I click on Yes.
38 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Geotagging
The Map (Google) (keyboard shortcut Alt+G), Map (Bing) (keyboard shortcut Alt+B)& Map (OSM) (key- board shortcut Alt+O) tabs allow you to set the location of where a photograph was taken. (Some people argue that it should be the location of the subject of the photograph, but what about photographs of the Moon?) All three tabs have similar functionality, but use different providers of map data and imagery.
3.4. Geotagging 39 Photini Documentation, Release 2017.6.0.dev819
When you first select one of the map tabs you need to click the Load map button. This helps reduce the load on the map providers’ servers by not having them contacted every time you run Photini.
40 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Once the map is loaded, the Load map button is replaced by legal notices and a button (or buttons) to display the terms of use in your web browser. The map initially displays the previously used location. You can change the view by zooming in or out, or by panning the map by dragging it with the mouse. However, it’s usually easier to find a specific location by using the search facility.
3.4. Geotagging 41 Photini Documentation, Release 2017.6.0.dev819
Click on the
42 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Having found the right town, you can then zoom in and pan around to find the exact location where your photograph was taken. Using aerial / satellite imagery (if it’s available) can help with this.
3.4. Geotagging 43 Photini Documentation, Release 2017.6.0.dev819
Now you can drag and drop your photograph onto the map to set its location. To set the same location on multiple images, select them all and then drag and drop one of them.
44 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Note that photographs that have location data are shown with a flag symbol () in the image selector area. The location coordinates are shown in the Lat, long: box. These values are editable, so you can set the location of photographs directly, e.g. by copying and pasting from another one.
3.4. Geotagging 45 Photini Documentation, Release 2017.6.0.dev819
When several photographs have location metadata Photini will pan the map (and zoom out if required) to ensure all the selected images are shown on the map. Selected images are shown with coloured markers. Unselected images are shown with grey markers.
46 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Selecting another map tab, and loading the map, will show the same location but with data from a different provider.
3.4. Geotagging 47 Photini Documentation, Release 2017.6.0.dev819
Address lookup
Photograph metadata can include textual address elements as well as the latitude & longitude. These are stored in a 5-level hierarchy: street, city, province, country and region. The meaning of these terms is rather loose, especially when out in the countryside, and there’s no requirement to fill them all in. Typically city can be anything from a village to a metropolis, and street is a more specific location, e.g. “23 Abdication Avenue”. Province would be a state in the USA or a county in the UK. Country is stored as a name and a 2 or 3 letter ISO code. Region appears to be rarely used but could be a continent or sub-continent. Photini stores two addresses: camera is where the photographer was positioned and subject is the location being photographed. For example, a general view of the Eiffel Tower will almost certainly have been taken from somewhere else in Paris. This separation of camera and subject addresses was added to the IPTC specification in 2009, but you may still have software that only recognises “legacy” address metadata. In this case you should not use the subject column or region row. (Note that although the address metadata is standardised by the IPTC, it’s actually stored in the XMP data.)
48 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The address button uses the map provider’s “reverse geolocation” service to convert latitude & longitude into a hierarchical address. This is a rather imprecise process so you may need to edit the results yourself.
3.4. Geotagging 49 Photini Documentation, Release 2017.6.0.dev819
In this example Google and Bing disagree about the street address and are using different languages for the state element.
50 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
With OpenStreetMap we get more information. This is more visible if you expand the address area by dragging its border with the map to the right.
3.4. Geotagging 51 Photini Documentation, Release 2017.6.0.dev819
OpenStreetMap is the only provider to include the fact that the location is a church. There are many different types of premises (shops, cafés, parks, etc.) included in OSM addresses. Photini adds all the information supplied to the street element. You can edit it out if it’s not appropriate. The button exchanges the camera and subject addresses. This may be useful if you have files with “legacy” address metadata that should really be in the subject column.
52 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Flickr uploader
The Flickr upload tab (keyboard shortcut Alt+F) allows you to upload your photographs to Flickr. Flickr is a popular online photograph sharing service. The Flickr upload tab uses the Flickr API but is not endorsed or certified by Flickr. Unlike some other Flickr uploaders, Photini uses the descriptive metadata you’ve created to set Flickr’s title, descrip- tion and tags. This means you don’t have to retype all that information! Note that the Flickr upload tab is only enabled if you have installed python-flickrapi. See installation for more detail.
3.5. Flickr uploader 53 Photini Documentation, Release 2017.6.0.dev819
Initially most of the Flickr uploader tab is disabled. It’s only usable after you’ve authorised Photini to access your Flickr account by clicking the Connect button.
54 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first time you click Connect Photini connects your web browser to Flickr, from where you can log in and give Photini permission to access Flickr on your behalf. You then copy a verification code from your browser to Photini.
3.5. Flickr uploader 55 Photini Documentation, Release 2017.6.0.dev819
If the authorisation is successful Photini displays your Flickr user name and profile picture. You should not need to redo this authorisation process unless you click the Log out button. Your current Flickr albums are shown on the right hand side of the Flickr uploader tab. You can add a new album with the New album button. This opens a pop-up dialog as shown below.
56 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
3.5. Flickr uploader 57 Photini Documentation, Release 2017.6.0.dev819
Type in the album details and click OK. Note that the album will not be created on Flickr until you upload a photo to it.
58 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
To upload one or more photographs to Flickr, select them in the image selector area, then choose which (if any) of your albums to add them to and set any of the other attributes, then click on the Start upload button.
3.5. Flickr uploader 59 Photini Documentation, Release 2017.6.0.dev819
During uploading Photini displays a progress bar. Uploading takes place in the background, so you can continue to use other tabs while the upload is in progress. The upload can be stopped by clicking the Stop upload button.
Google Photos / Picasa uploader
Attention: In early 2017 Google disabled many of the API functions used by this uploader. Creation and deletion of albums is no longer possible and the relevant GUI buttons have been removed. Editing album details is also no longer possible. You can still upload photos to an existing album though. Further changes to the GUI will be made if and when Google release a new API with suitable functionality.
The Google Photos upload tab (keyboard shortcut Alt+P) allows you to upload your photographs to Google Photos and Picasa Web Albums. Although it was originally written as a Picasa uploader, it also uploads to Google Photos. Unlike some other uploaders, Photini uses the descriptive metadata you’ve created to set the photo’s title and tags. This means you don’t have to retype all that information! Note that the Google Photos upload tab is only enabled if you have installed the relevant libraries. See installation for more detail.
60 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first time you select Photini’s Google Photos upload tab it will ask you to authorise Photini to access Google Photos. It does this by connecting your web browser to Google, from where you can log in and give Photini permission to access Google Photos on your behalf. You then copy a verification code from your browser to Photini, as shown below.
Every image uploaded to Google Photos has to be stored in a “collection” or “album”. You can select one of your existing albums from the drop down list (next to the “title” label) or you can create a new album by clicking on the New album button.
3.6. Google Photos / Picasa uploader 61 Photini Documentation, Release 2017.6.0.dev819
62 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The title, description and other attributes of an album can be changed simply by editing the appropriate fields. Note that Google Photos does not display the description or location of a collection / album. (The album cover photograph cannot be changed due to a restriction in the API. You need to log into Picasa with a web browser to change it.)
3.6. Google Photos / Picasa uploader 63 Photini Documentation, Release 2017.6.0.dev819
To upload one or more photographs to Google Photos, select them in the image selector area, then click on the Start upload button. During uploading Photini displays a progress bar. Uploading takes place in the background, so you can continue to use other tabs while the upload is in progress.
64 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first image uploaded to a new album becomes the album’s cover image.
3.6. Google Photos / Picasa uploader 65 Photini Documentation, Release 2017.6.0.dev819
Facebook uploader
The Facebook tab (keyboard shortcut Alt+k) allows you to upload photographs to Facebook. Your photos’ de- scriptive metadata is used to generate a caption. Note that the tab is only available if you have installed the relevant libraries. See installation for more detail. Initially most of the Facebook uploader tab is disabled, as shown below. It’s only usable after you’ve authorised Photini to access your Facebook account by clicking the Connect button.
66 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first time you connect to Facebook a pop-up browser window opens for you to log in to your Facebook account. You may need to enlarge or maximise this window.
3.7. Facebook uploader 67 Photini Documentation, Release 2017.6.0.dev819
Photini requests permission to see your photos. It needs this to get details of your current photo albums – title, description, location and cover photo.
68 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Once permission is granted the tab is enabled. Your Facebook user name and profile picture are shown whenever Photini is connected to Facebook. You won’t need to login via the pop-up window again for up to two months unless you click on the Log out button or you remove Photini’s permissions in your Facebook settings apps page.
3.7. Facebook uploader 69 Photini Documentation, Release 2017.6.0.dev819
The album title widget shows a drop-down list of all your albums. (Those that Photini is not yet authorised to upload to are disabled.) The special title
70 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
You can create a new album by clicking on the New album button. This opens a pop-up dialog where you can set the album properties. These are optional except for the title. Note the privacy drop-down which controls the visibility of all photos uploaded to the album.
3.7. Facebook uploader 71 Photini Documentation, Release 2017.6.0.dev819
After typing in the album details, click OK.
72 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first time you create an album or upload a photo a pop-up browser window opens asking you to authorise Photini to post to Facebook.
3.7. Facebook uploader 73 Photini Documentation, Release 2017.6.0.dev819
You should allow Photini to share things publicly as you can always specify a more restricted visibility when you create an album.
74 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The newly created album is added to your album list and can be selected as the upload destination. There are three more options to set before uploading any photos. The Suppress news feed story option allows you to upload photos without generating a “Jim has uploaded 10 photos to the album Holiday 2012/07” type announcement on your Facebook timeline. You will receive a notifica- tion that Photini has uploaded photos but this will not be visible to your friends. The Set "city" from map coordinates option uses your photos’ location data (if present) to choose a “city” (or region, neighbourhood or country) from Facebook’s places directory. It may not always give the results you expect, so if you use this option you should check your photos after upload and change their location if necessary. The Optimise image size option is only available if you have installed the Python Imaging Library. It resizes images to one of Facebook’s preferred sizes, usually the maximum permitted 2048 pixels. Doing this before upload may result in better image quality and makes uploading faster.
3.7. Facebook uploader 75 Photini Documentation, Release 2017.6.0.dev819
After selecting some photos you can click on the Start upload button. The tab is mostly disabled during upload but other Photini tabs can be used. The upload can be stopped at any time by clicking on the Stop upload button.
76 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
The first picture uploaded to a new album becomes the album’s cover photo.
Image importer
The Import photos tab (keyboard shortcut Alt+I) allows you to copy photographs from your digital camera or anywhere else on your computer (for example, a camera memory card if your computer has a card reader). Whilst there are many other programs to do this, I’ve never found one that does things the way I want, so I added one to Photini. Note that you can only import directly from cameras if you have installed python-gphoto2 (which is not available on Windows). See installation for more detail. The key part of the importer is the Target format field. This provides a very flexible way to specify where on your computer imported images should be stored. It uses % formats to generate file and directory names based on the image capture date & time. The most useful ones are %Y (year), %m (month number) and %d (day of the month) but many more are available. See the Python documentation for a complete list. As well as the date & time format strings, bracketed keywords can be used to manipulate parts of the file name:
3.8. Image importer 77 Photini Documentation, Release 2017.6.0.dev819
keyword meaning example (camera) the camera model name Canon_PowerShot_A1100_IS (name) the complete file name IMG_9999.JPG (number) the numeric part of the file name 9999 (root) the filename without its extension IMG_9999 (ext) the filename extension .JPG Below the Target format field is an example generated from the current format to help you edit it correctly. Note that Photini stores a different target format for each camera or source folder that you use. This can be useful if you have two cameras that use the same file names. For example, I use /home/jim/Pictures/from_camera/ %Y/%Y_%m_%d/IMGe(number)(ext) for my DSLR to rename files from IMG_9999.JPG to IMGe9999.JPG so they don’t clash with files from my compact camera, which also uses names like IMG_9999.JPG.
After connecting one or more cameras and pressing the refresh button, a camera can be chosen from the
78 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
When the Target format has been set to match where previous images were put, images that have already been copied to the computer are non selectable (shown in light grey).
3.8. Image importer 79 Photini Documentation, Release 2017.6.0.dev819
The remaining images can be selected by clicking on them, or by using the Select all button (to select all uncopied images) or Select new button (to select images newer than the last ones copied).
80 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Clicking the Copy photos button copies the selected images to the computer and loads them into Photini. To avoid overloading Photini you should be careful not to select too many images before clicking on Copy photos.
3.8. Image importer 81 Photini Documentation, Release 2017.6.0.dev819
Configuration
If there are tabs in the Photini GUI that you don’t use, you can remove them by deselecting their entry in the Options menu. The Options menu also has a Settings item which opens the dialog shown below.
82 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
This allows you to edit the names used to auto-generate some descriptive metadata, reset the Flickr or Picasa authori- sation (requiring you to re-authenticate next time you use them) and adjust how Photini uses “sidecar” files and IPTC metadata. Sidecar files allow metadata to be stored without needing to write to the actual image file. If you deselect “write to image” then sidecars will always be created. Otherwise, you can choose to have them always created (storing data in parallel with the image file), only created when necessary (e.g. an image file is write protected), or deleted when possible (if metadata can be copied to the image file the sidecar is deleted). New in version 15.08.0.dev311: The Metadata Working Group recommends that IPTC metadata is not written to files unless already present. Photini has an option to always write IPTC metadata. You may need this if you use some other software that reads IPTC but not Exif or XMP.
Spell checking
The Spelling menu allows you to enable or disable spell checking on Photini’s text fields, and to select the lan- guage dictionary to use. The available languages depend on what dictionaries you have installed. See the PyEnchant documentation for details of how to add dictionaries.
3.9. Configuration 83 Photini Documentation, Release 2017.6.0.dev819
Tag reference
This section lists the “mapping” from Photini’s field names (such as “Title / Object Name”) to the Exif / XMP / IPTC tags the data is stored in. The tag names are those used by the Exiv2 library. See http://exiv2.org/metadata.html for more detail. As far as possible Photini follows the Metadata Working Group (MWG) Guidelines for Handling Image Metadata. These specify the mapping between tags in Exif, XMP and IPTC, and say how software should reconcile any differ- ences between information stored in equivalent tags.
Primary tags
These tags are where Photini stores its metadata. (IPTC tags are only used if they already exist in the file, in line with the MWG guidelines, unless the “write unconditionally” user setting is enabled.) Note that “Title / Object Name” and “Keywords” are not stored in Exif. You may prefer not to use these fields to ensure compatibility with software that only handles Exif.
84 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Pho- Exif tag XMP tag IPTC tag tini field Title Xmp.dc.title Iptc.Application2.ObjectName / Ob- ject Name De- Exif.Image.ImageDescription Xmp.dc.description Iptc.Application2.Caption scrip- tion / Cap- tion Key- Xmp.dc.subject Iptc.Application2.Keywords words Copy- Exif.Image.Copyright Xmp.dc.rights Iptc.Application2.Copyright right Cre- Exif.Image.Artist Xmp.dc.creator Iptc.Application2.Byline ator / Artist Date Exif.Photo.DateTimeOriginal Xmp.photoshop.DateCreated Iptc.Application2.DateCreated / Exif.Photo.SubSecTimeOriginal Iptc.Application2.TimeCreated time Exif.Image.TimeZoneOffset Taken Date Exif.Photo.DateTimeDigitized Xmp.xmp.CreateDate Iptc.Application2.DigitizationDate / Exif.Photo.SubSecTimeDigitized Iptc.Application2.DigitizationTime time Digi- tised Date Exif.Image.DateTime Xmp.xmp.ModifyDate / Exif.Photo.SubSecTime time Mod- ified Ori- Exif.Image.Orientation enta- tion Aper- Exif.Photo.FNumber ture Fo- Exif.Photo.FocalLength cal Exif.Photo.FocalLengthIn35mmFilm length Lens Exif.Photo.LensMake maker name Lens Exif.Photo.LensModel model name Lens Exif.Photo.LensSerialNumber se- rial num- ber Lens Exif.Photo.LensSpecification spec- ifica- tion 3.10. Tag reference 85 Lati- Exif.GPSInfo.GPSLatitude tude, Exif.GPSInfo.GPSLatitudeRef lon- Exif.GPSInfo.GPSLongitude gi- Exif.GPSInfo.GPSLongitudeRef tude Cam- Xmp.iptcExt.LocationCreated Iptc.Application2.SubLocation era Xmp.iptc.Location Iptc.Application2.City ad- Xmp.photoshop.City Iptc.Application2.ProvinceState dress Xmp.photoshop.State Iptc.Application2.CountryName Xmp.photoshop.Country Iptc.Application2.CountryCode Xmp.iptc.CountryCode Sub- Xmp.iptcExt.LocationShown ject ad- dress Photini Documentation, Release 2017.6.0.dev819
Secondary tags
Photini may read information from these tags and merge it with information from the primary tags. These tags are deleted when the corresponding primary tags are saved. Photini Exif tag XMP tag IPTC tag field Title / Exif.Image.XPTitle Iptc.Application2.Headline Object Name Description Exif.Image.XPComment Xmp.tiff.ImageDescription / Caption Exif.Image.XPSubject Keywords Exif.Image.XPKeywords Copyright Xmp.tiff.Copyright Creator / Exif.Image.XPAuthor Xmp.tiff.Artist Artist Date / time Exif.Image.DateTimeOriginal Xmp.exif.DateTimeOriginal Taken Date / time Xmp.exif.DateTimeDigitized Digitised Date / time Xmp.tiff.DateTime Modified Orientation Xmp.tiff.Orientation Aperture Exif.Image.FNumber Xmp.exif.FNumber Exif.Image.ApertureValue Xmp.exif.ApertureValue Exif.Photo.ApertureValue Focal length Exif.Image.FocalLength Xmp.exif.FocalLength Xmp.exif.FocalLengthIn35mmFilm Lens maker name Lens model Exif.Canon.LensModel name Exif.OlympusEq.LensModel Lens serial Exif.OlympusEq.LensSerialNumber number Lens speci- Exif.Image.LensInfo Exif.CanonCs.Lens fication Exif.Nikon3.Lens Latitude, Xmp.exif.GPSLatitude longitude Xmp.exif.GPSLongitude
Read only tags
Photini may read information from these tags and merge it with information from the primary tags. These tags are not deleted when the corresponding primary tags are saved. Photini field Exif tag XMP tag IPTC tag Time zone offset[1] Exif.Image.TimeZoneOffset Exif.NikonWt.Timezone [1] The time zone offset is not directly presented to the user. It is applied to the Date / time Taken, Date / time Digitised and Date / time Modified fields if no other time zone information is available.
Delete only tags
These tags are not read but are deleted when the corresponding primary tags are saved.
86 Chapter 3. User manual Photini Documentation, Release 2017.6.0.dev819
Photini field Exif tag XMP IPTC tag tag Lens model Exif.CanonCs.LensType name Lens Exif.CanonCs.ShortFocal Exif.CanonCs.MaxAperture specification Exif.CanonCs.MinAperture
3.10. Tag reference 87 Photini Documentation, Release 2017.6.0.dev819
88 Chapter 3. User manual CHAPTER 4
Typical workflow
This is a suggestion for how to use Photini. It roughly reflects what I do, but is just a guideline for beginners. As you gain experience you may choose to do things differently. There is no requirement to fill in all the metadata fields, nor to do them in any particular order.
Make a backup copy
Before editing any of your images’ metadata you should make a backup copy. Even if I could guarantee that Photini was bug free and would never corrupt an image file, you still might have a power cut or other computer failure at just the wrong time and ruin a photograph you can never take again. Before you start, please make a backup copy of your photographs.
Load images
Select the File menu Open images item (keyboard shortcut Ctrl+O). This opens a file selection dialog with which you can navigate to your image folder and select one or more image files to open. If you prefer, you can “drag and drop” image files from a file manager window to the Photini editor’s image selector. Photini doesn’t set a limit to the number of files you can open simultaneously, but it’s probably sensible not to open more than 30 or 40, depending on the memory capacity and processing power of your computer. I usually load all the photographs taken on one day, or in one place. Each image file is shown as a thumbnail image in the lower half of the Photini editor GUI. You can adjust the space allocated to this area by clicking and dragging the bar between it and the upper tab area. The thumbnails can be made larger or smaller with the thumbnail size slider. Choose a size that allows you to see a reasonable number of images, yet still tell one from another. Double click on any thumbnail to view the full size image in your default picture viewing program.
89 Photini Documentation, Release 2017.6.0.dev819
Set text metadata
I usually start by setting the fields that are the same for all the photos I’ve loaded - Creator / Artist, Copyright and Title / Object Name. First you need to select the images whose metadata you want to change. Images are selected by clicking on their thumbnails. Shift+click and Ctrl+click can be used to select multiple images in the usual way. The quickest way to select all the images is the keyboard shortcut Ctrl+A. The Creator / Artist and Copyright fields have Auto buttons to help fill them in. The first time you use these buttons Photini will ask for the names of the creator and the copyright owner. For amateur photographers these will probably be the same person, but in some cases the copyright might be owned by a company or some other organisation. The values you supply are saved for future use in Photini’s configuration file. If all your selected pictures have the same title then type it into the Title / Object Name field now. Otherwise it’s time to start selecting single images, or groups of images, and filling in the remaining text fields. The Keywords field expects a list of words or short phrases, separated by semi-colon (;) characters.
Save your work so far
As you proceed it’s a good idea to save the images that have new metadata with the File menu Save images with new data item (keyboard shortcut Ctrl+S). Any images with unsaved metadata have thumbnails marked with a warning symbol ().
Set geolocation
Amongst the commonly used image metadata items are the latitude and longitude of the position from which the photograph was taken. (Some people argue that it should be the position of the subject of the photograph, but what about photographs of the Moon?) Photini makes it easy to set the latitude and longitude of any photograph by dragging and dropping it onto a map. There are currently three map tabs in the Photini editor, each of which gets maps (or aerial photographs) from a different provider: Google, Microsoft Bing and Open Street Map. (Each of these providers has terms and conditions you should read and accept before using their maps.) The maps differ in appearance, and show different levels of detail for different parts of the world. You should use the one that you like best, but it’s very easy to switch to another at any time. Start by clicking the Load map button to connect to the map server and load an initial map. You may be able use the map’s navigation and zoom controls to find the area you want, but usually you will need to use the search box. Click the drop down box arrow and select
90 Chapter 4. Typical workflow CHAPTER 5
“Localisation”
Photini can be made easier to use for people who don’t speak English. There are two parts to this – the text used within the program and the documentation. I rely on users to do the translation as I can not write any other language with any fluency. If your computer is configured to use a language other than English, and Photini has already been translated into that language, then Photini should use the translation automatically. For example, this is what it looks like if your computer is configured to use Spanish.
91 Photini Documentation, Release 2017.6.0.dev819
If you’d like to help by translating Photini into another language, or by improving an existing translation, this is what you need to do.
Join Transifex
The Photini project uses Transifex to host its translations. This provides an online editor, making it easy for individuals to contribute as much or as little effort as they wish. Follow the link to the Transifex Photini page and click on “help translate Photini”. From here you can create a free account and sign in. If your language is not included in the Photini project languages list you can request it to be added by clicking on “request language”. Each language is represented by a code, e.g. nl or en_CA. The longer codes are usually regional or national variations of a common language. You should choose the common language if it’s not already available in Photini, moving on to the variations once the common language is done. Once your language is added you can ask to join the language team and then start translating.
Translating Photini
Transifex is quite easy to use, but there are a few things to be aware of when working on the Photini project. On the Transifex site there are several “resources” for Photini. The one called photini contains the text strings used by the Photini program. The others, beginning with doc, contain the Photini documentation.
92 Chapter 5. “Localisation” Photini Documentation, Release 2017.6.0.dev819
photini resource
Things to be aware of: Words with special meanings Some of Photini’s GUI elements such as Title / Object Name are named after the metadata items in the Exif, XMP or IPTC specifications. If information about these standards is available in your language it may help with translating these words. Formatting strings In Python curly braces are used to include other data in a string. For example, Copyright ©{0:d} {1}. All rights reserved. includes the year and copyright holder’s name when the pro- gram is run. You should take care not to change what’s inside the braces, but you can reorder them if it’s appropriate for your language. HTML markup Strings such as
Upload to Flickr has not finished.
include HTML markup which must be copied to your translated string. The Transifex web page includes a “copy source string” button that can help with this. Keyboard shortcuts Some strings include a single ampersand character & immediately before a letter that is used as a keyboard shortcut. You should choose a suitable letter in your translation and place the ampersand appropriately.doc.xxx resources
The Photini documentation is written in reStructuredText. This is a markup language that looks very like plain text, but uses certain characters to give extra meaning to some parts. You need to take extra care when the string to be translated includes such markup. Double backquotes `` These usually mark words that are used in the Photini GUI. You may wish to include the English equivalent in brackets after your translation to help users read the documentation as the screen grabs are all from the English version. Special characters, e.g. (|hazard|) These refer to Unicode symbols and should not be translated. Short cross references, e.g. :doc:`tags` These should not be translated. Long cross references, e.g. :ref:`installation
Testing your translations
To test your translated strings you will need to have a local copy of the Photini source files to build and install. See installation for more detail. You will also need to install the Transifex client program:
sudo pip install transifex-client
The Transifex client is used to download your translated strings. For example, if you’ve been working on a Dutch translation with the language code nl:
tx pull-l nl
This will download several files. src/lang/photini.nl.ts is the Dutch translation of the Photini program strings. src/lang/doc/nl/LC_MESSAGES/xxx.po are the Dutch translations of the Photini documentation. (Replace nl with the language code you are translating for.)
5.3. Testing your translations 93 Photini Documentation, Release 2017.6.0.dev819
Testing the photini resource
The src/lang/photini.nl.ts file needs to be “compiled” (converted from .ts format to .qm format) before it can be used by the Photini program. This requires the lrelease program, which is part of the libqt4-linguist package on some Linux systems. The lrelease command can be used directly to compile a single language file:
lrelease src/lang/photini.nl.ts-qm src/photini/data/lang/photini.nl.qm
Or you can easily compile all the language files with setup.py:
python setup.py build_messages
Now you can install Photini with your new translation(s):
python setup.py build sudo python setup.py install
Photini should use your new language if your computer’s LANG environment variable is set appropriately. You can force this when running Photini from the command line:
LANG=nl photini
Photini should now be using your translations. If all is well, please email [email protected] with the good news that another language can be added to the next Photini release.
Testing the doc.xxx resources
If you install Sphinx (See installation) you can build a local copy of the documentation using your translation. For example, to build Dutch documentation:
LANG=nl python setup.py build_sphinx
Open doc/html/index.html with a web browser to read the translated documentation.
94 Chapter 5. “Localisation” CHAPTER 6
Miscellaneous
Change Log
Photini - a simple photo metadata editor. http://github.com/jim-easterbrook/Photini Copyright (C) 2012-17 Jim Easterbrook [email protected]
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see
Changes in v2017.6.0: 1/ Add location address metadata to map tabs. 2/ Fix bug in Flickr uploader if user hasn't set a "buddy" icon. 3/ Use OpenCage Data for OSM map search and address lookup.
Changes in v2017.5.0: 1/ Migrate Bing map from v7 to v8 of Bing API. 2/ Many other map improvements. 3/ Time adjustment offset now includes time zone.
Changes in v2017.03.0: 1/ Fix bugs in Google Photos uploader and remove disabled functionality. 2/ Improve error handling in Flickr uploader.
95 Photini Documentation, Release 2017.6.0.dev819
3/ Updated German translation.
Changes in v2016.12.0: 1/ Started adding support for video files. 2/ Improved compatibility with files written by other software. 3/ Fixed several annoying bugs.
Changes in v2016.10.0: 1/ Added a drop down list of favourite keywords. 2/ Improved spell checking of words with hyphens or apostrophes. 3/ Fix failure to open image viewer on some Windows versions. 4/ Fixed several minor bugs in map tabs. 5/ Fixed (I hope) segfault on exit bug.
Changes in v2016.06.0: 1/ Added option to resize photos for Facebook upload. 2/ Improved handling of various 'raw' image formats. 3/ Store time zone offset in Exif data. 4/ Read time zone offset from some cameras. 5/ Improved reading and display of lens specification. 6/ Fixed several minor bugs and annoyances.
Changes in v2016.05.0: 1/ Added a Facebook uploader tab. 2/ Display logged in user details on uploader tabs. 3/ Added 35mm equivalent focal length to 'technical' tab. 4/ Added German translation of program strings. 5/ Allow image file names to be given when running from command line. 6/ Fixed several minor bugs and annoyances.
Changes in v2016.02.1: 1/ Replace accidentally invalidated Google maps API key.
Changes in v2016.02.0: 1/ Made 'year' part of version number 4 digits. 2/ Made it easier to drag multiple photos to map. 3/ Changed 'Picasa' to 'Google Photos'. 4/ Fixed problem with Picasa authentication. 5/ Fixed some Python 3 incompatibilities. 6/ Fixed several minor bugs and annoyances.
Changes in v15.11.0: 1/ Added time zone to 'technical' tab. 2/ Allow setting of date/time 'resolution'. 3/ Flickr uploader sets date 'granularity'. 4/ Dropped use of pyexiv2 library.
Changes in v15.10.0: 1/ Added error handling to Flickr & Picasa uploaders. 2/ Added spell checking to most text entry fields. 3/ Speeded up importing photos from a camera. 4/ Fixed several minor bugs and annoyances.
Changes in v15.09.1: 1/ Fix bug with importer not recognising some image types
Changes in v15.09.0: 1/ Fix bugs with Qt4 and Python 3 introduced in last release.
96 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
2/ Improved widgets on 'technical' and 'descriptive' tabs.
Changes in v15.08.1: 1/ Added Spanish translation of program strings. 2/ Added option to always write IPTC data. 3/ Improved speed on slow computers. 4/ Use PyQt5 if installed, PyQt4 otherwise. 5/ Fixed several minor bugs and annoyances.
Changes in v15.07.1: 1/ Convert incompatible image formats before upload to Picasa/Flickr. 2/ Added lens selector to 'technical' tab. 3/ Improved internal handling of image metadata. 4/ Include subseconds in time stamps.
Changes in v15.06.0: 1/ No longer store Picasa/Flickr login data in plain text file. 2/ Restructured Picasa and Flickr uploaders. 3/ Moved documentation to readthedocs.org.
Changes in v15.05.0: 1/ Added aperture and focal length to 'technical' tab. 2/ Expanded range of file types that can be opened. 3/ Fixed several minor bugs and annoyances.
Changes in v15.01.1: 1/ Fixed several minor bugs and annoyances. 2/ Removed need for 2to3 conversion when installing with Python3.
Changes in v15.01.0: 1/ Removed Picasa uploader dependency on gdata-python-client. 2/ Several minor bug fixes.
Changes in v14.10.0: 1/ Improved drag and drop of images on to map. 2/ Fixed some map bugs caused by '\' in Windows file paths.
Changes in v14.09.0: 1/ Importer can now copy from any directory on the computer. 2/ Linux installer now adds a menu shortcut.
Changes in v14.08.1: 1/ Added stuff to build a Windows all-in-one installer. 2/ Fixed some bugs, mostly when running on Windows.
Changes in v14.08.0: 1/ Major rewrite of metadata handling to be more compliant with MWG guidelines. 2/ Improved handling of metadata in non utf-8 character sets.
Changes in v14.07.0: 1/ Changed version numbering scheme, again. 2/ Minor bug fix in camera image importer.
Changes in v14.06.dev108: 1/ Now Python 3 compatible. 2/ Added ability to import pictures from a camera. 3/ Much improved documentation.
6.1. Change Log 97 Photini Documentation, Release 2017.6.0.dev819
4/ Simplified Picasa uploader. 5/ Uploaders now have just one progress bar. 6/ Simplified installation process.
Changes in v14.04.dev63: 1/ Changed version numbering scheme. 2/ Added ability to offset several photo timestamps by same amount. 3/ Added a logging window to display error messages. 4/ Can now create Flickr sets/albums. 5/ Can now use XMP sidecar files. 6/ Flickr uploader can now use v2 of flickrapi. 7/ Switched to a different map tile provider for Open Street Map. 8/ Simplified documentation build process.
Changes in v13.09_r20: 1/ Added Google Picasa uploader. 2/ Added menu option to select which tabs to use.
Changes in v13.05_r7: 1/ Changed version numbering scheme. 2/ Added ability to drag and drop files to image list area. 3/ Numerous bug fixes.
Changes in v13.02_a515056: 1/ Fixed bug with GPS accuracy.
Changes in v13.01_f2bbd24: 1/ Started writing a user manual. 2/ Started using GExiv2 instead of deprecated pyexiv2.
Changes in v13.01_43a0943: 1/ Changed version numbering scheme. 2/ Added ability to change image orientation. 3/ Added a Flickr uploader.
GNU General Public License
The Photini software is licensed under the GNU General Public License.
GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc.
Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to
98 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS
0. Definitions.
6.2. GNU General Public License 99 Photini Documentation, Release 2017.6.0.dev819
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based on the Program.
To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to
100 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to
6.2. GNU General Public License 101 Photini Documentation, Release 2017.6.0.dev819
the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
102 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product
6.2. GNU General Public License 103 Photini Documentation, Release 2017.6.0.dev819
is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
104 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
6.2. GNU General Public License 105 Photini Documentation, Release 2017.6.0.dev819
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted
106 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may
6.2. GNU General Public License 107 Photini Documentation, Release 2017.6.0.dev819
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
108 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
6.2. GNU General Public License 109 Photini Documentation, Release 2017.6.0.dev819
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read
GNU Free Documentation License
The Photini documentation is licensed under the GNU Free Documentation License.
GNU Free Documentation License Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
0. PREAMBLE
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals;
110 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
6.3. GNU Free Documentation License 111 Photini Documentation, Release 2017.6.0.dev819
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
The "publisher" means any person or entity that distributes copies of the Document to the public.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover
112 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice
6.3. GNU Free Documentation License 113 Photini Documentation, Release 2017.6.0.dev819
giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
114 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the
6.3. GNU Free Documentation License 115 Photini Documentation, Release 2017.6.0.dev819
electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions
116 Chapter 6. Miscellaneous Photini Documentation, Release 2017.6.0.dev819
will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.
11. RELICENSING
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A "Massive Multiauthor Collaboration" (or "MMC") contained in the site means any set of copyrightable works thus published on the MMC site.
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.
"Incorporate" means to publish or republish a Document, in whole or in part, as part of another Document.
An MMC is "eligible for relicensing" if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.
ADDENDUM: How to use this License for your documents
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU
6.3. GNU Free Documentation License 117 Photini Documentation, Release 2017.6.0.dev819
Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.
118 Chapter 6. Miscellaneous CHAPTER 7
Further reading
• The best explanation of what should be put in each metadata field I’ve found is the Guide to Photo Metadata Fields. • Metadata Working Group (MWG) Guidelines for Handling Image Metadata. • Google Maps JavaScript API v3 tutorial. • Bing Maps AJAX Control, Version 7.0. • Leaflet, An Open-Source JavaScript Library for Mobile-Friendly Interactive Maps by CloudMade. Copyright (C) 2012-17 Jim Easterbrook. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
119