Git commit a1702999743fd7a692fa28620d9c14d4eee2a84f by Gilles Caulier. Committed on 01/01/2017 at 21:50. Pushed by cgilles into branch 'master'.
polish M +1 -1 CMakeLists.txt M +1 -1 digikam/CMakeLists.txt M +1 -1 digikam/annexes-credits.docbook M +2 -2 digikam/index.docbook M +1 -1 showfoto/CMakeLists.txt M +48 -48 showfoto/index.docbook https://commits.kde.org/digikam-doc/a1702999743fd7a692fa28620d9c14d4eee2a84f diff --git a/CMakeLists.txt b/CMakeLists.txt index 74583eb..ba26726 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -1,5 +1,5 @@ # -# Copyright (c) 2010-2016, Gilles Caulier, <caulier dot gilles at gmail dot com> +# Copyright (c) 2010-2017, Gilles Caulier, <caulier dot gilles at gmail dot com> # # Redistribution and use is allowed according to the terms of the BSD license. # For details see the accompanying COPYING-CMAKE-SCRIPTS file. diff --git a/digikam/CMakeLists.txt b/digikam/CMakeLists.txt index 1797bb6..69b1b90 100644 --- a/digikam/CMakeLists.txt +++ b/digikam/CMakeLists.txt @@ -1,5 +1,5 @@ # -# Copyright (c) 2010-2016, Gilles Caulier, <caulier dot gilles at gmail dot com> +# Copyright (c) 2010-2017, Gilles Caulier, <caulier dot gilles at gmail dot com> # # Redistribution and use is allowed according to the terms of the BSD license. # For details see the accompanying COPYING-CMAKE-SCRIPTS file. diff --git a/digikam/annexes-credits.docbook b/digikam/annexes-credits.docbook index b0703f0..e67372f 100644 --- a/digikam/annexes-credits.docbook +++ b/digikam/annexes-credits.docbook @@ -10,7 +10,7 @@ </para> <para> - Program copyright 2001-2016, <ulink url="http://www.digikam.org";>digiKam</ulink> developers team + Program copyright 2001-2017, <ulink url="http://www.digikam.org";>digiKam</ulink> developers team </para> <para> diff --git a/digikam/index.docbook b/digikam/index.docbook index 496b976..16cd6ae 100644 --- a/digikam/index.docbook +++ b/digikam/index.docbook @@ -204,7 +204,7 @@ <title>The &digikam; Handbook</title> <copyright> <year>2001</year> - <year>2016</year> + <year>2017</year> <holder>The <ulink url="http://www.digikam.org";>digiKam</ulink> developers team</holder> </copyright> @@ -212,7 +212,7 @@ <!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook and in the FDL itself on how to use it. --> <legalnotice>&FDLNotice;</legalnotice> - + <date>Summer 2016</date> <releaseinfo>5.0</releaseinfo> diff --git a/showfoto/CMakeLists.txt b/showfoto/CMakeLists.txt index 19953cf..af4f3bc 100644 --- a/showfoto/CMakeLists.txt +++ b/showfoto/CMakeLists.txt @@ -1,5 +1,5 @@ # -# Copyright (c) 2010-2016, Gilles Caulier, <caulier dot gilles at gmail dot com> +# Copyright (c) 2010-2017, Gilles Caulier, <caulier dot gilles at gmail dot com> # # Redistribution and use is allowed according to the terms of the BSD license. # For details see the accompanying COPYING-CMAKE-SCRIPTS file. diff --git a/showfoto/index.docbook b/showfoto/index.docbook index e7dcb5c..aeb85bf 100644 --- a/showfoto/index.docbook +++ b/showfoto/index.docbook @@ -116,7 +116,7 @@ <title>The &digikam; Handbook</title> <copyright> <year>2001</year> - <year>2016</year> + <year>2017</year> <holder>The <ulink url="http://www.digikam.org";>digiKam</ulink> developers team</holder> </copyright> @@ -124,7 +124,7 @@ <!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook and in the FDL itself on how to use it. --> <legalnotice>&FDLNotice;</legalnotice> - + <date>Summer 2016</date> <releaseinfo>5.0</releaseinfo> @@ -181,49 +181,49 @@ </sect2> <sect2> - <title>Reporting Bugs</title> - <para> - &digikam; is an Open Source project. This means that it relies on its users to play their part by, at least, reporting problems and suggesting possible improvements. - </para> - - <para> - &digikam; makes it as easy as possible for you to report bugs or suggest improvements. Wherever you are in the application the Help menu will include a Report Bugs option. This will display a message box with a highlighted link. Click on the link and your web browser will open the page for the reporting system. All the information required will already be filled in, just follow the instructions for completing your report. - </para> - - </sect2> - - <sect2> - <title>Support</title> - - <para> - &digikam; is a community supported project, which means that users and developers support one another. If you become a regular user of &digikam; you are encouraged to join the &digikam; Users Mailing List. You can start off by asking questions to other &digikam; users and hopefully soon you will be answering the support questions of others. - </para> - - <para> - <ulink url="https://mail.kde.org/mailman/listinfo/digikam-users";>&digikam; Users Mailing - List joining instructions.</ulink> - </para> - - <para> - You can also visit the <ulink url="http://www.digikam.org";>&digikam; Home Page.</ulink> for news of new releases and other &digikam; related information. - </para> - - </sect2> - - <sect2> - <title>Getting Involved</title> - - <para> - There are many ways that you can get involved with the continued development of &digikam;. You do not need to be a software developer. You can help with documentation, translation and user interface design or just contribute really good ideas to the wish-list. You can also get involved by testing early development code as it is being developed and providing feedback to the developers. Of course, if you are a software developer then you can help to make &digikam; the best digital photograph application there is. - </para> - - <para> - The best way to start getting involved with &digikam; is to join the Developers Mailing List. - <ulink url="https://mail.kde.org/mailman/listinfo/digikam-devel";>&digikam; Developer Mailing - List joining instructions.</ulink> - </para> - - </sect2> + <title>Reporting Bugs</title> + <para> + &digikam; is an Open Source project. This means that it relies on its users to play their part by, at least, reporting problems and suggesting possible improvements. + </para> + + <para> + &digikam; makes it as easy as possible for you to report bugs or suggest improvements. Wherever you are in the application the Help menu will include a Report Bugs option. This will display a message box with a highlighted link. Click on the link and your web browser will open the page for the reporting system. All the information required will already be filled in, just follow the instructions for completing your report. + </para> + + </sect2> + + <sect2> + <title>Support</title> + + <para> + &digikam; is a community supported project, which means that users and developers support one another. If you become a regular user of &digikam; you are encouraged to join the &digikam; Users Mailing List. You can start off by asking questions to other &digikam; users and hopefully soon you will be answering the support questions of others. + </para> + + <para> + <ulink url="https://mail.kde.org/mailman/listinfo/digikam-users";>&digikam; Users Mailing + List joining instructions.</ulink> + </para> + + <para> + You can also visit the <ulink url="http://www.digikam.org";>&digikam; Home Page.</ulink> for news of new releases and other &digikam; related information. + </para> + + </sect2> + + <sect2> + <title>Getting Involved</title> + + <para> + There are many ways that you can get involved with the continued development of &digikam;. You do not need to be a software developer. You can help with documentation, translation and user interface design or just contribute really good ideas to the wish-list. You can also get involved by testing early development code as it is being developed and providing feedback to the developers. Of course, if you are a software developer then you can help to make &digikam; the best digital photograph application there is. + </para> + + <para> + The best way to start getting involved with &digikam; is to join the Developers Mailing List. + <ulink url="https://mail.kde.org/mailman/listinfo/digikam-devel";>&digikam; Developer Mailing + List joining instructions.</ulink> + </para> + + </sect2> </sect1> @@ -265,16 +265,16 @@ &doc-using-setup-metadata-views; </sect2> - + <sect2 id="using-setup-editor"> <title>Editor Settings</title> &doc-using-setup-editor-iface; &doc-using-setup-editor-save; &doc-using-setup-editor-raw; - + </sect2> - + &doc-using-setup-cm; &doc-using-setup-slideshow;
