Commit f0cf5185 authored by Gilles Caulier's avatar Gilles Caulier 🗼
Browse files

restore all from dev branch

parent dd989a79
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 4.0 International license.
https://creativecommons.org/licenses/by-sa/4.0/
DIGIKAM.ORG CHANGES WORKFLOW:
-----------------------------
A git "dev" branch was create to check changes online with https://staging.digikam.org before to push new revision officially in https://www.digikam.org
To process with git, follow step below :
1 - from up to date git master, create a new local "dev" branch : git checkout -b dev remotes/origin/dev
2 - optionaly, synchronize this branch with master, in case of : git merge master; git push
3 - made changes in dev branch and check the result with staging.digikam.org. This url is updated one minute after a commit to dev branch.
There is a Jenkins job for that:
https://binary-factory.kde.org/view/Websites/job/Website_staging-digikam-org/
4 - when all is fine backport your changes done in dev to master : git checkout master; git merge dev; git push.
5 - now all your last changes must be visible to www.digikam.org few minutes later.
There is a Jenkins job for that:
https://binary-factory.kde.org/view/Websites/job/Website_digikam-org/
FRONT PAGE CAROUSEL CONTENT UPDATE:
-----------------------------------
The carousel from front page is based on Foundation Orbit.
https://foundation.zurb.com/sites/docs/v/5.5.3/components/orbit.html
The images and caption text are included in the index.html file:
/themes/hugo-theme-digikam/layouts/index.html
Follow the same convention to add another .orbit-slide <li> element
and the associated <figcaption> text.
Don't forget to add another <button> below it, increment the
'data-slide="X"' value and add appropriate text for screen readers.
The carousel PNG image (1024x768) are located in /static/img/carousel/
NEW RELEASE CONTENT UPDATE:
---------------------------
When a new release is ready, the /data/release.yml just needs to be updated.
Update the 'version' value, and each binary file name.
b32/b64 stands for 32-bit and 64-bit respectively.
* Blockers
** DONE implement comments on news posts
** DONE blog post describing new site
** DONE edit meta pages
** DONE make the footer a bit more viable, as its a bit empty
** DONE replace the screenshot placeholder in the index
** DONE News post headers don't need to be anchor links
** DONE Link to google drive repo to download Pre-Release Bundles is missing.
** DONE Add an ability to subscribe to digikam news and posts on the website.
** DONE The Meta subchapters should not be hidden behind the main "Meta" topic in the bottom menu bar.
** DONE In my opinion the meta chapters would fit better under Documentation.
** DONE About subtopics should be alphabetically ordered (now it is maybe ordered by importance, but I think that's confusing).
* Nice-to-have
** TODO Run link checker and fix all broken links (Right now we don't resolve Drupal comment anchor links & misc other broken links, nothing major)
** TODO implement search capability
** TODO continue to refine and edit the content
** TODO migrate all images off flickr/imgur
** TODO (LOW PRIORITY) In the download page the two-line "Linux AppImage" resulting in non-aligned 64-/32-bit links looks not so nice.
** TODO Make legacy comments prettier
** TODO Restyle news/post meta (author, publish date stamp, social share links)
** TODO Center Recipes book image in sidebar
** TODO Towards the skinnier end of the medium grid layout size, the header doesn't look good
---
date: ""
title: ""
author: ""
description: ""
category: "news"
---
baseurl: "https://digikam.org/"
languageCode: en-us
title: digiKam
theme: "hugo-theme-digikam"
taxonomies:
tag: "tags"
category: "categories"
params:
custom_navbar: true
sidebar:
menu: ""
markup:
blackFriday:
fractions: false
goldmark:
renderer:
unsafe: true
---
date: "2017-03-22T13:13:45-06:00"
title: "About"
author: "digiKam Team"
description: "Learn about digiKam"
category: "about"
aliases: "/about"
menu: "navbar"
---
### What is digiKam?
digiKam is an advanced open-source digital photo management application that runs on Linux, Windows, and MacOS. The application provides a comprehensive
set of tools for importing, managing, editing, and sharing photos and raw files.
[![](/img/content/about/about_editor_albumview.png "Albums View and Image Editor")](/img/content/about/about_editor_albumview.png)
### Highlights
You can use digiKam's import capabilities to easily transfer photos, raw files, and videos directly from your camera and external storage devices (SD cards, USB disks, etc.).
The application allows you to configure import settings and rules that process and organize imported items on-the-fly.
digiKam organizes photos, raw files, and videos into albums. But the application also features powerful tagging tools that allow you to assign tags, ratings, and labels to
photos and raw files. You can then use filtering functionality to quickly find items that match specific criteria.
In addition to filtering functionality, digiKam features powerful searching capabilities that let you search the photo library by a wide range of criteria.
You can search photos by tags, labels, rating, data, location, and even specific EXIF, IPTC, or XMP metadata. You can also combine several criteria for more advanced searches.
digiKam rely on [Exiv2](http://www.exiv2.org/) library to handle metadata tag contents from files to populate the photo library.
digiKam can handle raw files, and the application uses the excellent [LibRaw](https://www.libraw.org/) library for decoding raw files.
The library is actively maintained and regularly updated to include support for the latest camera models.
digiKam can also manage video files for cataloging purpose, and the application uses the couple [FFmpeg](http://ffmpeg.org/)
and [QtAv](http://www.qtav.org/) libraries to extract metadata and play media.
The application provides a comprehensive set of editing tools. This includes basic tools for adjusting colors, cropping, and sharpening
as well as advanced tools for, curves adjustment, panorama stitching, and much more. A special tool
based on [Lensfun](https://lensfun.github.io/) library permit to apply lens corrections automatically on images.
Extended functionality in digiKam is implemented via a set of tools based of plugins mechanism (named **DPlugins** for digiKam Plugins).
Plugins can be written to import and export contents to remote web-services, add new features to edit image, and batch process photo.
[![](/img/content/about/about_albumview_itemmenu.png "Albums View and Item Menu")](/img/content/about/about_albumview_itemmenu.png)
This diff is collapsed.
---
date: "2017-03-22T13:14:13-06:00"
title: "Overview"
author: "digiKam Team"
description: "A brief description of the digiKam sotware."
category: "about"
aliases: "/about/overview"
---
![digiKam Pack](/img/content/about/overview_digikam_pack.png)
### A digiKam Overview
digiKam is an advanced digital **photo management application**, which makes importing and organizing digital photos a "snap".
The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections.
[![](/img/content/about/overview_tagsview.png "Tags View")](/img/content/about/overview_tagsview.png)
Tired of the folder constraints? Don’t worry, digiKam also provides **tagging**. You tag your images which can be spread out across
multiple folders, and digiKam provides fast and intuitive ways to browse these tagged images. You can also add comments to your images.
digiKam makes use of a fast and robust database to store these meta-informations which makes adding and editing of comments and tags very reliable.
digiKam include also many tools dedicated to import and export contents to remote web-services, as Flickr, GPhoto, ImgUr, Facebook, etc.
[![](/img/content/about/overview_import.png "Camera Import")](/img/content/about/overview_import.png)
An easy-to-use interface is provided that enables you to connect to your camera and preview, download and/or delete your images.
Basic auto-transformations can be deployed on the fly during image downloading.
Another tool, which most artists and photographers will be familiar with, is a **Light Table**. This tool assists artists and photographers
with reviewing their work ensuring the highest quality only. A classical light table will show the artist the place on the images to touch up.
Well in digiKam, the light table function provides the user a similar experience. You can import a photo, drag it onto the light table,
and touch up only the areas that need it.
[![](/img/content/about/overview_lighttable.png "Light Table")](/img/content/about/overview_lighttable.png)
The digiKam **Image Editor** provide some common tools e.g. red eye correction or colors correction. Additional tools are provided with the main application
to process advanced corrections on image like color management, noise reduction, or special effects. digiKam Image Editor supports all camera RAW file formats,
16 bits color depth, Exif/Makernote/IPTC/GPS/XMP metadata, Color management, tagging/rating/comments pictures, etc.
[![](/img/content/about/overview_imageeditor.png "Image Editor")](/img/content/about/overview_imageeditor.png)
A stand-alone image editor version named **ShowFoto** is also available. It runs without digiKam images database support, but provides all Image Editor functions.
Finally, digiKam include also a queue manager to batch operations on a set of images. This tool is perfect to play common photographer workflow previously
configured by end-user. The operations available on **Batch Queue Manager** are the same than Image Editor, but operations can be chained to process more than
one file at the same time.
[![](/img/content/about/overview_bqm.png "Batch Queue Manager")](/img/content/about/overview_bqm.png)
You want to know more about digiKam? Continue to [Features page](/about/features/)
---
date: "2017-03-21"
title: "Contribute"
author: "digiKam Team"
description: "Contribute to the digiKam project"
category: "contrib"
aliases: "/contrib"
menu: "navbar"
---
The easiest way to contribute is to spread the word about digiKam.
We also encourage you to test digiKam, report bugs, and submit feature requests.
You might also want to subscribe to the [digikam-users](https://mail.kde.org/mailman/listinfo/digikam-users) mailing list
and help other digiKam users with their questions and problems.
## Reporting Bugs and Submitting Feature Requests
Use the bug tracking system for all bug reports and new feature requests.
Take a look at the [support page](/support) for further information.
## Freezes and Other Run-Time Issues
### Linux host
Just run digiKam from the terminal command line to capture the text traces generated by the application.
Note that you need to turn on before all debug traces from digiKam with QT_LOGGING_RULES environment variable.
```
export QT_LOGGING_RULES="digikam*=true"
digikam
```
### Windows Host
On Windows, application text output is not sent to the terminal.
You need to install [DebugView tool](http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx) to capture text traces
generated by digiKam.
Before to start digiKam and DebugView, from your Windows System Info panel, add a new user variable with these criteria:
```
name: "QT_LOGGING_RULES"
value: "digikam*=true"
```
### MacOS Host
As under Linux, run the application from a terminal.
digiKam executable is installed in `/Applications/digiKam.org/digikam.app/Contents/MacOS/digikam`.
Just start it from the command line to view text traces.
Note that you need to turn on before all debug traces from digiKam with QT_LOGGING_RULES environment variable.
```
export QT_LOGGING_RULES="digikam*=true"
/Applications/digiKam.org/digikam.app/Contents/MacOS/digikam
```
## Dealing with Crashes in digiKam
### Linux host
In case digiKam crashes, you can provide a backtrace using GDB debugger.
digiKam needs to be compiled with all debug info; otherwise the backtrace will be useless.
If you installed digiKam using the packages provided by your distribution, make sure to install
the corresponding debug package. [The debugging guide](https://community.kde.org/Guidelines_and_HOWTOs/Debugging)
provides further information on debugging.
If you use a regular binary, i.e. no AppImage, use the following command to get into GDB and start digiKam:
```
gdb digikam
(gdb) catch throw
(gdb) run
```
If you use an AppImage bundle, replace the name of the AppImage with the one you have and run:
```
./digikam-7.2.0-x86-64.appimage debug
```
Instructions how to get into GDB are below. When you are in debugger and digiKam crashes, you will get to the
GDB command prompt. If digiKam "just" freezes, press ctrl-c to get to the GDB prompt.
Once you are at the prompt, use the "bt" command, copy the backtrace and exit GDB as shown here:
```
(gdb) bt
(gdb) _the backtrace is here_
(gdb) quit
```
### Windows Host
The binary installers comes with debug symbols and a [DrMinGw crash course handler](https://vroby.ddns.net/Public/sdlBasic/MinGW/doc/drmingw/drmingw.html),
which will generate a file backtrace in you home directory as below:
```
C:\Users\_user_name_\AppData\Local\digikam_crash.log
```
Just replace "_user_name_" with your Windows login account.
### MacOS Host
Mac users need to install [Apple XCode development tool](https://en.wikipedia.org/wiki/Xcode) which integrate **lldb**
debugger. Run it as follows to get a crash backtrace from the debugger:
```
lldb /Application/digiKam.org/digikam.app/Contents/MacOS/digikam
```
## Checking for Memory Leaks
To check for memory leaks in digiKam under Linux, use the [valgrind](http://valgrind.org) tool.
Run the command below, and report the trace to developers:
```
valgrind --tool=memcheck --leak-check=full --error-limit=no digikam
```
## Submitting Patches
To fix digiKam source code, you need to checkout current implementation from git following [intructions here](/download/git).
Before you submit patches, please read the [HACKING section](https://www.digikam.org/api) from online API documentation.
Send patches against the current version of the code (latest git/master revision) and not the stable release or
an old beta version. Patches can be created using the following command:
```
git diff HEAD > mydiff.patch
```
The patches must be attached to a new entry in [Bugzilla](https://bugs.kde.org/describecomponents.cgi?product=digikam).
Please do not use mailing lists or private mail.
Alternative: you can make a Pull Resquest (PR) on gitlab using a fork of [the project](https://invent.kde.org/graphics/digikam) with your modifications.
## Translations
If you want to contribute to the digiKam internationalization effort, contact the [translation teams](http://l10n.kde.org/).
Also, please read the [Translation HOWTO](http://l10n.kde.org/docs/translation-howto/) to know the workflow used by translators.
## Documentation
Help with digiKam documentation is always welcome.
For all documentation-related matters, write to [digiKam-devel mailing list](https://mail.kde.org/mailman/listinfo/digikam-devel).
Our [documentation](http://docs.kde.org/development/en/extragear-graphics/digikam/index.html) is based on the
[docbook format standard](http://l10n.kde.org/docs/doc-primer/index.html).
The [README](https://invent.kde.org/kde/digikam-doc/blob/master/README) file explains in detail how structure the documents, take screenshots, etc.
It's also possible to submit additions and changes in the ASCII format. To do this, create a new Bugzilla entry with a patch against git/master code, so it can be incorporated in the documentation.
## Pictures Samples
We need RAW, TIFF, and JPEG files from different manufacturers (Canon, Nikon, Sony, Olympus, Sigma, etc.).
We use these files to analyze embedded metadata to improve camera support in digiKam.
We also need sample files produced by different applications (including other platforms and proprietary
software like Adobe Photoshop) that include IPTC/XMP metadata. This can help us to improve compatibility
with other tools and implement automatic import of these data into the digiKam database.
## Splash Screens and Background Photo
As a photographer, you can submit your best photos for use as digiKam splash-screens and background photo.
Take a look [at this page](http://www.digikam.org/splashcreens) for further information.
This diff is collapsed.
---
date: "2017-03-21"
title: "FAQs"
author: "digiKam Team"
description: "Frequently asked questions about digiKam"
category: "documentation"
aliases: "/faq/digikam"
---
### My camera is not in the list of supported cameras in digiKam.
Can you add drivers for my camera ?
digiKam doesn't included any camera drivers. It makes use of <a href="http://www.gphoto.org/">gphoto2</a> to do camera operations. If your camera is not in the supported list, i would recommend doing some <a href="http://www.google.com">searching</a> around. Many of the new cameras actually provide a USB MassStorage Device Interface, so that you can access the camera like a hard disk. (See, the FAQ about using a USB MassStorage Camera with digiKam).
If you have still have no luck, i would recommend contacting the gphoto2 people.
### How can I inform you about bugs and wishes?
##### Reporting bugs and wishes
Please use the KDE bug tracking system for all bugreports and new feature wishlists. You can checkout the current bugreports and wishlists at these urls
* <a href="http://bugs.kde.org/buglist.cgi?product=digikam&amp;bug_status=UNCONFIRMED&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED">digiKam bugs and wishes</a>
### I have a USB Mass Storage Camera. How do I use it with digiKam ?
#### The Easy Way!
If you have a relatively modern Linux distribution that is pre-configured to work with USB Mass Storage Devices, there's nothing you need to set up!. It should be truly "plug and play":
#### Manual Setup
If you're running a Linux distribution that doesn't set up USB Mass Storage devices automatically, here are the steps you need to follow:
### Thumbnail generation fails on large files
Q: On all my albums, digiKam fails to generate thumbnails on some images. The only pattern I can spot is that it fails on largish files (bigger than 1MB). When the thumnails are generated, the ones that fail appear at first and then are replaced by the broken picture icon.
A: Check if the application generating the file include an IPTC preview as JPEG. digiKam use this embeded image to render quickly the thumbnail without to load whole image.
### Which file format should I use?
Most digital cameras store images in jpeg format on the memory card. JPEG is a compressed format, whose compression causes loss of quality. Heavy compression may make the loss of quality visible to the eye. Every time you open a JPEG image, edit it, save the file and close it, the image is compressed and quality is lost. Lost quality can not be regained.
To avoid this repeated loss of quality you should save your edited files in a lossless format. digiKam understands two of these: Tiff and png. In digiKam it is advisable to use png. digiKam supports the exif data in png files, whereas (currently) for tiff files, exif data are lost.
So the recommendation is to save any edited files as png.
You have now finished editing your photos and are content with the results. Should you keep the png-files or convert them to the far smaller JPEG files for storage?. If you are very concerned about storage space, you can do the latter. You could, however rather keep the lossless png files and only create JPEG copies in the moment you want to take your images to the print shop, send them by email or post them on the web.
Note: a format with better compression named HEIF can be used in place of PNG to gain compression ratio
### Why are my RAW images so dark?
In 16-bit mode, many are surprised that a relatively dark photograph shows up after RAW conversion with digiKam, even so the 'ColorManagement' and 'RAW Conversion' options have been meticulously set-up for the intended purpose. The simple reason is that digiKam uses <a href="http://www.libraw.org">Libraw</a> demosaisic method with linear conversion of RAW data, and if the ICC profile does not include gamma correction and/or tone mapping (most Canon profiles), the result is dark (in 8-bit mode the gamma correction is applied automatically). But nothing is lost, read on!
A RAW file is a container including the raw sensor data, EXIF metadata, and often a JPEG preview thumbnail. It does normally not include an ICC profile. The embedded JPEG file is used by digiKam to display RAW image thumbnails or in slide shows, and it can be used for TV display from the camera. This is fast, but a preview only, no raw data.
RAW conversion requires a couple of steps in order to produce a satisfying result, better adapted to your needs than JPEG out-of-the-camera images:
1. Choice of the internal working space in regard to the intended use
2. Adjust tonal range - define thresholds for highlights and shadows
3. Adjust gradation - adjust mid tones, for example using numerical numbers in the histogram or curves like features
4. Alter white balance if necessary
5. Color cast removal ideally using color temperature (or an according eyedropper tool) as well as a tint / tone slider. An according eye-dropper tool can be applied simply by clicking inside the image on neutral grey subject tones. This procedure doesn't always create the expected result, because quite often the light situation while capturing the image wasn't neutral either.
6. Smoothing and noise removal (if not done in the conversion process already)
7. Apply sharpening (refocus, unsharpmask)
8. Choose final color bitdepth (saving as JPEG always reverts to 8-bit depth, use PNG or TIFF for 16-bit)
9. Select output and pixel dimensions – upsampling on the RAW file often gives better results in comparison to already processed files
10. Continue editing for example retouching or small enhancements in the favorite imaging application
Now, most profiles that come with the camera OEM software are not so suited for linear conversion. If you'd like a good profile, do it yourself or via a service. It will be more precise than the standard profile and it will <b>include gamma correction</b> - no dark images anymore in 16-bit mode!
Some good reading on the subject:
* [digiKam documentation](https://docs.kde.org/trunk5/en/extragear-graphics/digikam/using-setup.html#using-setup-editor)
* [Primer for ColorManagement](http://www.scribus.net/index.php?name=Web_Links&amp;req=viewlink&amp;cid=4)
* [Wikipedia](http://en.wikipedia.org/wiki/Color_management)
* [OpenRAW.org](http://www.openraw.org/actnow/)
* [European Color Initative ECI](http://eci.org/eci/en/020_eci.php)
### digiKam doesn't work when album library is on a network share (nfs, samba)
digiKam freezes when I store my album library on a NFS server, NAS, windows shared folder, etc. What can I do ?
digiKam uses sqlite to store informations about images (tags, comments, rates, ...). Sqlite relies on file locking features provided by filesystems (check <a href="http://www.sqlite.org/faq.html#q5">this FAQ entry</a>). But, network file systems often have troubles with locking and this can cause unexpected problems with sqlite.
In order to solve this problem, try one of the following workarounds :
* Use a <a href="http://thoughtsonrails.wordpress.com/2007/03/03/digikam-albums-on-network-filesystem/">symlink for some albums stored on a network path</a>
* Use a <a href="http://lists.kde.org/?l=kde-bugs-dist&amp;m=117536777106366&amp;w=2">symlink for the sqlite database file</a>. This method is preferred if you want to have all your album library on a network path.
Note: the digiKam team is aware of this problem and is working on it. In the future, it will be possible to use another database backend to solve it.
### How to create a digiKam theme?
Color Scheme are based on INI text file format separated with sections and attributes defined by key value pairs.
The color specification is done by using standard HTML color format (RGB/hexadecimal).
System level installation of color schemes is done in $(INSTALLATION_PREFIX)/share/apps/digikam/colorschemes and user level installation in $(HOME)/.local/share/apps/digikam/colorschemes under Linux.
Theme names appear in the menu with the filename. Make sure to capitalize the first letter of the filename
Its not necessary to restart digiKam if you modify the theme. switch to a different theme and switch back. But if you add a new theme, you will have to restart digiKam for the new theme to be recognized.
Color scheme file are the same than ones used for Plasma desktop. You can find all details [at this url](https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/colors/index.html)
### Color Management with X on Linux
Color management of your monitor is possible with digiKam. The better and more fundamental way is to include the display color management in your X server using profiles. Then all other applications will profit as well.
This <a href="http://linux.vilars.com/">site</a> explains it all, go there for the installation procedure and the How-To's.
Note: the best way to color-manage the display is to establish a custom profile and use that one, a procedure to be repeated every other year or so for aging reasons. But if you go the easier way and use the profiles delivered from the manufacturer, it is paramount to do a normalization as described for example on the<a href="https://www.cambridgeincolour.com/tutorials/monitor-calibration.htm">cambridgeincolour</a> web site.
### Thumbnail generation fails on video files
#### Why don't I have thumbnails for my video files?
#### Why thumbnail generation stops at the first video file I have ?
digiKam uses [QtAV framework](http://www.qtav.org/) and [FFMpeg codecs](https://www.ffmpeg.org/) to generate thumbnails in background. Also, video support is optional at application compilation time.
So, you should check first if Video Support is present in the list from digiKam Help/Components Info dialog. If yes, you can install the stand alone QtAV media player
on your system and check if playing video work as expected. If it do not work, probably a ffmpeg codec is missing on your system.
### How can I change the default video player ?
#### When I double-click on a video thumbnail, it opens -unwanted video player-, how could I change it to another video player ?
digiKam embeded QtAV video player by default for a better portability and prevent external dependency. You can call an extra video player by the Open With contex menu entry
Under Linux, start Plasma system settings then go to Applications/File Associations, then click on video. Here you have a list of file types with the list of
applications that can open them.
E.g. if you want another video player for your .avi files, go to x-msvideo. The first application listed here will be the default one.
### How can I change the text font size ?
#### Size of fonts for text and menus is too big/too small in digiKam. How can I adjust it ?
Start Plasma system settings then go to Appearance/Fonts. Here you can adjust the font size but also choose another font.
Please be warned that this will change the font behavior of all Plasma applications !
Note: digiKam also includes fonts settings to customize icon-view, tree-view, and tooltips text size. Rendez-vous to the digiKam control pannel to change these settings.
### Single-click on a thumbnail opens digiKam editor
#### When I click on a thumbnail, it opens the digiKam editor. How can I disable that ?
Go to digiKam control pannel in Views/Icons section to change this behavior. Under Linux, Plasma desktop permit to change the simple to double click and vis-versa
into Workspace/Desktop Behavior and choose "double-click to open files and folders"
### Some "Properties" in digiKam sidebar are unknown or unavailable
#### Why can't I get Image Properties Dimensions or other items ?
digiKam uses [Exiv2 shared library](http://www.exiv2.org/) to display the file properties.
If the "Dimensions" value is "unknown", it means that relevant file format is not yet fully supported by the library.
Note: even if you have the "Dimensions" information, some other properties (Bits depth, Sensitivity, Compression, ...) can still be unavailable depending on the image file (and your digital camera).
#### In Map sidebar, when I click on "More Info...", it opens a Web browser, how could I change it to another browser (firefox or anything else) ?
Under Linux, start Plasma system settings), then go to "Application/Default", then click on "Web Browser" and choose "in the following browser" where you can put any command.
### How to deal with utf-8 encoding ?
##### I just upgraded my preferred linux distribution but now I have warnings about utf-8. I have a warning when starting digiKam about new character encoding. What should I do ?
Nowadays, most linux distributions use utf8 by default for the character encoding. It includes the content of files, but also the file names.
Look here to learn more about utf-8 and unicode :
<a href="http://en.wikipedia.org/wiki/UTF-8">http://en.wikipedia.org/wiki/UTF-8</a>
digiKam will warn you when you change your locale with a new encoding.
Eg, if you switched from iso latin1 (iso8859-1) to utf8, digiKam will send you this warning :
<pre><small>Your locale has changed from the previous time this album was opened.
Old Locale : ISO 8859-1, New Locale : UTF-8
This can cause unexpected problems. If you are sure that you want to
continue, click on 'Yes' to work with this album. Otherwise, click on 'No'
and correct your locale setting before restarting digiKam
</small></pre>
Before accepting this modification, you should migrate at least the file names in your albums to utf-8 or you might have troubles because digiKam won't be able to access directories which contains accents non encoded in utf-8.
For that purpose, linux distributions propose various solutions and tools, but mainly based on convmv :
</p>
###### Gentoo
Gentoo has a very nice page about using UTF-8 :
<a href="http://www.gentoo.org/doc/en/utf-8.xml">Using UTF-8 with Gentoo</a>
This could also be useful for users of other distributions.
###### Suse