Re: Kubuntu 24.04 LTS startup.and general maintenance

[Yuri Chornoivan]

понеділок, 3 червня 2024 р. 09:51:52 EEST Brian L Murphy написано:
> With K torrent, I do as you say, and select quit. ut The question is,
> How do I stop it from happening every time it boots up?

Uncheck "Restore previous session" in the System Settings "Startup and 
Shutdown" module. Or disable the system tray icon in the KTorrent settings.
> 
> On 3/06/24 18:46, Yuri Chornoivan wrote:
> > Hi,
> > 
> > This list is for documentation writers. So you quaestions are slightly off
> > topic here. Please refer
> > 
> > https://userbase.kde.org/Getting_Help
> > 
> > понеділок, 3 червня 2024 р. 02:18:20 EEST Brian L Murphy написано:
> >> Can you please tell me 1.how to stop the system from stopping me from
> >> using other programs once I e.g.leave the music player running for a
> >> long period, E.g say, Clementine for about,1/2hr the whole system
> >> becomes in operable unless I reboot. This can be quite a nuisance
> > 
> > Please report bug here
> > 
> > https://launchpad.net/ubuntu/+bugs
> > 
> >> 2.how do I stop k torrent from running every time I boot up the system,
> > 
> > Click on the KTorrent tray icon and select "Quit".
> > 
> >> Regards Brian.
> > 
> > Best regards,
> > Yuri

Re: Kubuntu 24.04 LTS startup.and general maintenance

[Yuri Chornoivan]

Hi,

This list is for documentation writers. So you quaestions are slightly off 
topic here. Please refer

https://userbase.kde.org/Getting_Help

понеділок, 3 червня 2024 р. 02:18:20 EEST Brian L Murphy написано:
> Can you please tell me 1.how to stop the system from stopping me from
> using other programs once I e.g.leave the music player running for a
> long period, E.g say, Clementine for about,1/2hr the whole system
> becomes in operable unless I reboot. This can be quite a nuisance

Please report bug here

https://launchpad.net/ubuntu/+bugs

> 2.how do I stop k torrent from running every time I boot up the system,

Click on the KTorrent tray icon and select "Quit".

> 
> Regards Brian.

Best regards,
Yuri

[sdk/kdesrc-build/docbook_historied_per_file] doc/cmdline: closing parenthesis in sentence

[Yuri Chornoivan]

Git commit b8457e5b329cc525f43af66639a95e2580f02286 by Yuri Chornoivan.
Committed on 28/08/2010 at 06:02.
Pushed by ashark into branch 'docbook_historied_per_file'.

closing parenthesis in sentence

svn path=/trunk/KDE/kdesdk/doc/scripts/kdesrc-build/; revision=1169007

Original commit: d9c3c910
https://invent.kde.org/sdk/kdesrc-build/-/commit/d9c3c91087acf766b54298dfad3a213448124c6f

M  +1-1doc/cmdline/supported-cmdline-params.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/b8457e5b329cc525f43af66639a95e2580f02286

diff --git a/doc/cmdline/supported-cmdline-params.docbook 
b/doc/cmdline/supported-cmdline-params.docbook
index 3e64fdc3..7a3e1e0f 100644
--- a/doc/cmdline/supported-cmdline-params.docbook
+++ b/doc/cmdline/supported-cmdline-params.docbook
@@ -164,7 +164,7 @@ Do not automatically install packages after they are built.
 
 This option explicitly disables skipping the build process (an optimization
 controlled by the build-when-unchanged option. This is
+linkend="conf-build-when-unchanged">build-when-unchanged option). This 
is
 useful for making  run the build when you have changed something
 that  cannot check.
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/using-kdesrc-build: Add missing parenthesis

[Yuri Chornoivan]

Git commit 1aadb3aa66e3e7ab310702e9ddac0e4118b0acec by Yuri Chornoivan.
Committed on 16/03/2014 at 09:59.
Pushed by ashark into branch 'docbook_historied_per_file'.

Add missing parenthesis

Original commit: db494368
https://invent.kde.org/sdk/kdesrc-build/-/commit/db4943687395973c7efb57b92a3129ce41921e28

M  +1-1doc/using-kdesrc-build/advanced-features.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/1aadb3aa66e3e7ab310702e9ddac0e4118b0acec

diff --git a/doc/using-kdesrc-build/advanced-features.docbook 
b/doc/using-kdesrc-build/advanced-features.docbook
index 62a2b38b..00f0d335 100644
--- a/doc/using-kdesrc-build/advanced-features.docbook
+++ b/doc/using-kdesrc-build/advanced-features.docbook
@@ -354,7 +354,7 @@ use the --resume 
command line option,
 which resumes the last build starting at the module that failed. The source and
 metadata updates are skipped as well (but if you need these, it's generally
 better to use --resume-from
-instead.
+instead).
 
 
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/kdesrc-buildrc: Fix typos

[Yuri Chornoivan]

Git commit 15842995b15afe6706a696abfa592e1e63503a59 by Yuri Chornoivan.
Committed on 23/12/2013 at 16:17.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix typos

Original commit: 49033a7d
https://invent.kde.org/sdk/kdesrc-build/-/commit/49033a7dc322920c17c07aa339fe12b356f3f2a6

M  +5-5doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/15842995b15afe6706a696abfa592e1e63503a59

diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook 
b/doc/kdesrc-buildrc/conf-options-table.docbook
index 867208b1..94ca9119 100644
--- a/doc/kdesrc-buildrc/conf-options-table.docbook
+++ b/doc/kdesrc-buildrc/conf-options-table.docbook
@@ -490,12 +490,12 @@ on also use that proxy server, if possible, by setting the
 ignore-kde-structure
 Module setting overrides global
 This option is used to store the source and the build files 
directly
-in the name of the module. Fir example:
-source/extragear/network/telepathy/ktp-text-ui
+in the name of the module. For example,
+source/extragear/network/telepathy/ktp-text-ui
 becomes
-source/ktp-text-ui.
-This option is disabled by default, if you want to enable this you need to set 
this
-option to true
+source/ktp-text-ui.
+This option is disabled by default. If you want to enable this option you need 
to set it
+to true.
 
 This option was introduced with  1.16.
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/kdesrc-buildrc: Fix XML

[Yuri Chornoivan]

Git commit c87bce363568a41f669a3edc2c20d140f1bc7a47 by Yuri Chornoivan.
Committed on 29/01/2024 at 13:53.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix XML

Original commit: 3f5708b4
https://invent.kde.org/sdk/kdesrc-build/-/commit/3f5708b4b27983980e3d4456af67c97e8789d048

M  +1-1doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/c87bce363568a41f669a3edc2c20d140f1bc7a47

diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook 
b/doc/kdesrc-buildrc/conf-options-table.docbook
index 63adbf01..345ef74e 100644
--- a/doc/kdesrc-buildrc/conf-options-table.docbook
+++ b/doc/kdesrc-buildrc/conf-options-table.docbook
@@ -1300,8 +1300,8 @@ installations. However this only works on build systems 
that support
 
 
 
-
 These options do not require any value (except "filter-out-phases"). 
They are applied if they are presented in a section.
+
 Phase selection options
 
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/cmdline: Fix XML and minor typos

[Yuri Chornoivan]

Git commit d1f31832049cbacbb3fd1c9e45025ffa43ea532f by Yuri Chornoivan.
Committed on 08/01/2024 at 08:31.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix XML and minor typos

Original commit: 70d00640
https://invent.kde.org/sdk/kdesrc-build/-/commit/70d00640fd642476dd6904b311e1cf9e96c72a9b

M  +3-3doc/cmdline/supported-cmdline-params.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/d1f31832049cbacbb3fd1c9e45025ffa43ea532f

diff --git a/doc/cmdline/supported-cmdline-params.docbook 
b/doc/cmdline/supported-cmdline-params.docbook
index 3114de5f..f27563dd 100644
--- a/doc/cmdline/supported-cmdline-params.docbook
+++ b/doc/cmdline/supported-cmdline-params.docbook
@@ -165,7 +165,7 @@ specify other module names on the command line.
 
 
 If you want to avoid source updates
-when resuming, simply pass --no-src
+when resuming, simply pass --no-src
 in addition to the other options.
 
 
@@ -572,7 +572,7 @@ Enable or disable colorful output. By default, this option 
is enabled for intera
 
 
 
---nice (or 
--niceness)value
+--nice (or --niceness) 
value
 
 This value adjusts the computer CPU priority requested by , and
 should be in the range of 0-20. 0 is highest priority (because it is the
@@ -730,11 +730,11 @@ prove useful in bug reports or when asking for help in 
forums or mailing lists.
 
 
 
-
 
 
 Any other command-line options are assumed to be modules to update and build.
 Please, do not mix building with installing.
 
 
+
 

[sdk/kdesrc-build/docbook_historied_per_file] doc: Fix minor typo

[Yuri Chornoivan]

Git commit e8caa045139cd576f7b0c9b63b2ad1bbeee83b63 by Yuri Chornoivan.
Committed on 13/11/2023 at 16:00.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix minor typo

Original commit: 883f068e
https://invent.kde.org/sdk/kdesrc-build/-/commit/883f068eabace140d44e3bd9b68d415fc1c4f80d

M  +2-2doc/appendix-profile/old-profile-setup.docbook
M  +1-1doc/getting-started/environment.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/e8caa045139cd576f7b0c9b63b2ad1bbeee83b63

diff --git a/doc/appendix-profile/old-profile-setup.docbook 
b/doc/appendix-profile/old-profile-setup.docbook
index 925f7cb0..b1210648 100644
--- a/doc/appendix-profile/old-profile-setup.docbook
+++ b/doc/appendix-profile/old-profile-setup.docbook
@@ -109,7 +109,7 @@ create it if necessary. Add the line:
 On some distributions, it may be necessary to perform the same
 steps with the .xsession file, also in the home directory.
 This is especially true when using graphical login managers such as
-ssdm, gdm, or xdm.
+sddm, gdm, or xdm.
 
 
 
@@ -122,7 +122,7 @@ text terminals and the following six are graphical displays.
 
 If when you start your computer you are presented to the graphical display
 manager instead, you can use the new  environment, even if it is not 
listed
-as an option. Most display managers, including ssdm, have an option to use
+as an option. Most display managers, including sddm, have an option to use
 a Custom Session when you login. With this option, your session 
settings are
 loaded from the .xsession file in your home directory. If
 you have already modified this file as described above, this option should load
diff --git a/doc/getting-started/environment.docbook 
b/doc/getting-started/environment.docbook
index 47112ade..bf606dd6 100644
--- a/doc/getting-started/environment.docbook
+++ b/doc/getting-started/environment.docbook
@@ -22,7 +22,7 @@ configuration file option.
 in pretend mode.
 
 This driver works by setting up a custom 
xsession
-session type. This type of session should work by default with the ssdm login
+session type. This type of session should work by default with the sddm login
 manager (where it appears as a Custom session), but other login
 managers (such as LightDM and
 gdm) may require additional files installed to

[sdk/kdesrc-build/docbook_historied_per_file] doc/getting-started: Fix XML

[Yuri Chornoivan]

Git commit cea2d7b4656bdefcdbaca9ebf21d8cd8e5782ef3 by Yuri Chornoivan.
Committed on 22/01/2018 at 20:07.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix XML

Original commit: d263c448
https://invent.kde.org/sdk/kdesrc-build/-/commit/d263c4482ae0febc78886823c39f8df00423c4e4

M  +5-6doc/getting-started/before-building.docbook
M  +2-4doc/getting-started/building-and-troubleshooting.docbook
M  +1-1doc/getting-started/kde-modules-and-selection.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/cea2d7b4656bdefcdbaca9ebf21d8cd8e5782ef3

diff --git a/doc/getting-started/before-building.docbook 
b/doc/getting-started/before-building.docbook
index bd9ac1ab..dc6b6277 100644
--- a/doc/getting-started/before-building.docbook
+++ b/doc/getting-started/before-building.docbook
@@ -19,7 +19,7 @@ to be unusable.
 
 
 You can do also setup to install to a system-wide directory ( /usr/src/local) if you wish. This document
+class="directory">/usr/src/local) if you wish. This document
 does not cover this installation type, since we assume you know what you are 
doing.
 
 
@@ -69,9 +69,9 @@ least Perl 5.14), but you will also need some additional 
modules (
 will warn if they are not present):
 
 
-IO::Socket::SSL
-JSON::PP or JSON::XS
-YAML::PP, YAML::XS, or YAML::Syck
+IO::Socket::SSL
+JSON::PP or JSON::XS
+YAML::PP, YAML::XS, or YAML::Syck
 
 
 
@@ -175,7 +175,6 @@ included sample configuration file
 linkend="kdesrc-buildrc"/> will be a useful reference for this, especially its
 table of configuration options.
 
-
 
  contains many recommended configuration files to support
  Frameworks 5,  5, and other  applications.  The 
kdesrc-build-setup refers to these files in the 
configuration file it generates, but you can also use them
@@ -186,7 +185,7 @@ to use other configuration files from your own 
~/.kdesrc-buildrcconfiguration file in  and in .
 
-
+
 
 
 
diff --git a/doc/getting-started/building-and-troubleshooting.docbook 
b/doc/getting-started/building-and-troubleshooting.docbook
index 44c7ad5a..71926cc0 100644
--- a/doc/getting-started/building-and-troubleshooting.docbook
+++ b/doc/getting-started/building-and-troubleshooting.docbook
@@ -38,8 +38,6 @@ linkend="cmdline-pretend">--pretend command 
line option.
 nothing was actually built).  If there were no significant problems shown, 
you can proceed
 to actually running the script.
 
-
-
 
  kdesrc-build 
--stop-on-failure
 
@@ -85,6 +83,7 @@ Built 200 modules
 Your logs are saved in /home/kde-src/kdesrc/log/2018-01-20-07
 
 
+
 
 
 Resolving build failures
@@ -129,13 +128,12 @@ solutions, as well as general tips and strategies to 
build  in the
 Build from Source.
 
 
-
-
 On the other hand, assuming everything went well, you should have a new
  install on your computer, and now it is simply a matter of running
 it, described next in .
 
 For more information about 's logging features,
 please see .
+
 
 
diff --git a/doc/getting-started/kde-modules-and-selection.docbook 
b/doc/getting-started/kde-modules-and-selection.docbook
index ee64cc76..60c45f15 100644
--- a/doc/getting-started/kde-modules-and-selection.docbook
+++ b/doc/getting-started/kde-modules-and-selection.docbook
@@ -192,7 +192,6 @@ end module-set
 
 This kde-projects module set construct is the 
main method
 of declaring which modules you want to build.
-
 
 All module sets use the repository
 and use-modules options.  repository value, 
but other types of
 module sets also will use the git-repository-base option.
 
+
 
 
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/getting-started: Fix minor typo

[Yuri Chornoivan]

Git commit 593f6f9f6f8c68ef40b806c042a6acefc5e0f437 by Yuri Chornoivan.
Committed on 22/01/2018 at 19:33.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix minor typo

Original commit: 5ee62b00
https://invent.kde.org/sdk/kdesrc-build/-/commit/5ee62b00615154e0e1b920a0d67f863e345092a0

M  +1-1doc/getting-started/building-specific-modules.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/593f6f9f6f8c68ef40b806c042a6acefc5e0f437

diff --git a/doc/getting-started/building-specific-modules.docbook 
b/doc/getting-started/building-specific-modules.docbook
index cf7bed9d..d0e30a76 100644
--- a/doc/getting-started/building-specific-modules.docbook
+++ b/doc/getting-started/building-specific-modules.docbook
@@ -53,7 +53,7 @@ caused  to include the dependencies listed for
 linkend="conf-include-dependencies">include-dependencies option).
 
 
-The dependency resolution worked in this case only becase
+The dependency resolution worked in this case only because
 dolphin happened to be specified in a
 kde-projects-based module set (in this example, named
 base-apps). See .

[sdk/kdesrc-build/docbook_historied_per_file] doc/cmdline: Make docbook translatable

[Yuri Chornoivan]

Git commit c5b1ba301d1b480e81059e8165430c56ff6a9768 by Yuri Chornoivan.
Committed on 20/02/2013 at 17:45.
Pushed by ashark into branch 'docbook_historied_per_file'.

Make docbook translatable

Original commit: ec81dd2b
https://invent.kde.org/sdk/kdesrc-build/-/commit/ec81dd2bc871c063878e5d5bd75b5d1e02502ef5

M  +2-2doc/cmdline/supported-cmdline-params.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/c5b1ba301d1b480e81059e8165430c56ff6a9768

diff --git a/doc/cmdline/supported-cmdline-params.docbook 
b/doc/cmdline/supported-cmdline-params.docbook
index 346c495f..19a94467 100644
--- a/doc/cmdline/supported-cmdline-params.docbook
+++ b/doc/cmdline/supported-cmdline-params.docbook
@@ -261,7 +261,7 @@ module.
 This command line option is used to stop the normal build process just
 before a module would ordinarily be built.
 
-For example, if the normal build list was 
+For example, if the normal build list was 
 
moduleAmoduleBmoduleC,
 then --stop-before=moduleB would 
cause
  to only build moduleA.
@@ -276,7 +276,7 @@ This command line option was added with  1.16.
 This command line option is used to stop the normal build process just
 after a module would ordinarily be built.
 
-For example, if the normal build list was 
+For example, if the normal build list was 
 
moduleAmoduleBmoduleC,
 then --stop-after=moduleB would 
cause
  to build moduleA and 
moduleB.

[sdk/kdesrc-build/docbook_historied_per_file] doc/getting-started: Fix typo: nothing->noting

[Yuri Chornoivan]

Git commit c7b7f575484a7419085ff546d8f8795f882bb2a5 by Yuri Chornoivan.
Committed on 11/02/2013 at 05:24.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix typo: nothing->noting

Original commit: d5edaefc
https://invent.kde.org/sdk/kdesrc-build/-/commit/d5edaefcc0ef3659dd15205ce9f8f08fda4c2c18

M  +1-1doc/getting-started/kde-modules-and-selection.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/c7b7f575484a7419085ff546d8f8795f882bb2a5

diff --git a/doc/getting-started/kde-modules-and-selection.docbook 
b/doc/getting-started/kde-modules-and-selection.docbook
index 3d6ca15a..7af9af7f 100644
--- a/doc/getting-started/kde-modules-and-selection.docbook
+++ b/doc/getting-started/kde-modules-and-selection.docbook
@@ -290,7 +290,7 @@ list more than once. This allows us to manually set
 
 
 
-It is worth nothing that  will try to build modules
+It is worth noting that  will try to build modules
 in the right order, such as if only kdegraphics/* had been
 listed above, but this depends on other databases being kept up-to-date.  You
 can manually list modules in the proper order if necessary by using the

[sdk/kdesrc-build/docbook_historied_per_file] doc: Fix XML.

[Yuri Chornoivan]

Git commit e2adb1cf92db77282b053a6dc9f586129a82cd78 by Yuri Chornoivan.
Committed on 27/05/2012 at 17:50.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix XML.

Original commit: 496b5cea
https://invent.kde.org/sdk/kdesrc-build/-/commit/496b5cea6f03db014b0902ed9ca51da7240ee319

M  +7-7doc/appendix-modules/module-concept.docbook
M  +2-2doc/getting-started/before-building.docbook
M  +2-2doc/getting-started/configure-data.docbook
M  +4-4doc/introduction/brief-intro.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/e2adb1cf92db77282b053a6dc9f586129a82cd78

diff --git a/doc/appendix-modules/module-concept.docbook 
b/doc/appendix-modules/module-concept.docbook
index a5a0c53b..b223fe0a 100644
--- a/doc/appendix-modules/module-concept.docbook
+++ b/doc/appendix-modules/module-concept.docbook
@@ -3,8 +3,8 @@
 
  groups its software into modules of various size.
 This was initially a loose grouping of a few large modules, but with the
-introduction of the http://git-scm.com/;>Git-based https://projects.kde.org/;>source code repositories, these large
+introduction of the http://git-scm.com/;>Git-based https://projects.kde.org/;>source code repositories, these large
 modules were further split into many smaller modules.
 
 
@@ -23,14 +23,14 @@ file.
 
 
 module kdefoo
-cmake-options 
-DCMAKE_BUILD_TYPE=Debug
+cmake-options 
-DCMAKE_BUILD_TYPE=Debug
 end module
 
 
-This is a Subversion-based module since it doesn't use a This is a Subversion-based module since it doesn't use a repository option. Also, the
 cmake-options option is listed as an example only, it is not
-required.
+required.
 
 
 
@@ -49,10 +49,10 @@ module-set base-modules
 end module-set
 
 
-You can leave the module set name (base-modules
+You can leave the module set name 
(base-modules
 in this case) empty if you like. This repository setting tells
  where to download the source from, but you can also use a
-git:// URL.
+git:// URL.
 
 One special feature of the repository
 kde-projects is that  will
diff --git a/doc/getting-started/before-building.docbook 
b/doc/getting-started/before-building.docbook
index 3e3a7414..67a2ec3a 100644
--- a/doc/getting-started/before-building.docbook
+++ b/doc/getting-started/before-building.docbook
@@ -129,10 +129,10 @@ program.
 Or, you can obtain  from its source repository,
 by running:
 
-$ git clone 
git://anongit.kde.org/kdesrc-build 
~/kdesrc-build
+$ git clone 
git://anongit.kde.org/kdesrc-build ~/kdesrc-build
 
 
-Replace ~/kdesrc-build with
+Replace ~/kdesrc-build with
 the directory you would like to install to.
 
 
diff --git a/doc/getting-started/configure-data.docbook 
b/doc/getting-started/configure-data.docbook
index 580c10cc..9c6266c3 100644
--- a/doc/getting-started/configure-data.docbook
+++ b/doc/getting-started/configure-data.docbook
@@ -55,8 +55,8 @@ selects what  to download the sources from. This is 
useful if you are a
 developer with a http://techbase.kde.org/Contribute/First_Steps_with_your_KDE_SVN_Account;>
  account.
 
-You will probably want to select different modules to build, which
-is described in .
+You will probably want to select different modules to build, 
which
+is described in .
 
 
 
diff --git a/doc/introduction/brief-intro.docbook 
b/doc/introduction/brief-intro.docbook
index a31c7136..ac82d1c6 100644
--- a/doc/introduction/brief-intro.docbook
+++ b/doc/introduction/brief-intro.docbook
@@ -31,16 +31,16 @@ sequence is followed:
 
 
 
- reads in the command
+ reads in the command
 line and configuration file, to
 determine what to build, compile options to use, where to install,
-etc.
+.
 
- performs a source update for each  performs a source update for each module. The update continues until all modules
 have been updated. Modules that fail to update normally do not stop the build
  you will be notified at the end which modules did not
-update.
+update.
 
 
 

[sdk/kdesrc-build/docbook_historied_per_file] doc: fix typos in documentation: opiton->option, specific->specify

[Yuri Chornoivan]

Git commit a743a707eeb6811ee8a78af6ec8eba5e156b18bc by Yuri Chornoivan.
Committed on 02/02/2011 at 14:22.
Pushed by ashark into branch 'docbook_historied_per_file'.

fix typos in documentation: opiton->option, specific->specify

Original commit: 5735e9eb
https://invent.kde.org/sdk/kdesrc-build/-/commit/5735e9eb719c36078c6d67d8b464a462d8997bcc

M  +1-1doc/getting-started/kde-modules-and-selection.docbook
M  +1-1doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/a743a707eeb6811ee8a78af6ec8eba5e156b18bc

diff --git a/doc/getting-started/kde-modules-and-selection.docbook 
b/doc/getting-started/kde-modules-and-selection.docbook
index ae86ee46..665fc8f5 100644
--- a/doc/getting-started/kde-modules-and-selection.docbook
+++ b/doc/getting-started/kde-modules-and-selection.docbook
@@ -132,7 +132,7 @@ module based just on the module name. Because of this, a 
concept called
 
 By using a module set, you can quickly declare many Git modules to be
 downloaded and built, as if you'd typed out a separate module declaration for
-each one. The repository opiton is
+each one. The repository option is
 handled specially to setup where each module is downloaded from, which every
 other option contained in the module set is copied to every module generated
 in this fashion.
diff --git a/doc/kdesrc-buildrc/conf-options-table.docbook 
b/doc/kdesrc-buildrc/conf-options-table.docbook
index fcebb341..e977bf9f 100644
--- a/doc/kdesrc-buildrc/conf-options-table.docbook
+++ b/doc/kdesrc-buildrc/conf-options-table.docbook
@@ -318,7 +318,7 @@ name to reference a specific Git repository base URL in 
later module set declarations, which is useful for
 quickly declaring many Git modules to build.
 
-You must specific two things (separated by a space): The name to assign
+You must specify two things (separated by a space): The name to assign
 to the base URL, and the actual base URL itself. For example:
 
 

[sdk/kdesrc-build/docbook_historied_per_file] doc/using-kdesvn-build: Fix typos

[Yuri Chornoivan]

Git commit 5bb61901072e45bfc13b3c088bd29bd032698cf6 by Yuri Chornoivan.
Committed on 22/02/2009 at 18:55.
Pushed by ashark into branch 'docbook_historied_per_file'.

Fix typos

svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=930155

Original commit: 172f3f99
https://invent.kde.org/sdk/kdesrc-build/-/commit/172f3f9924429665a8f4349870d4fc47b12626db

M  +1-1doc/using-kdesvn-build/advanced-features.docbook
M  +1-1doc/using-kdesvn-build/other-features.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/5bb61901072e45bfc13b3c088bd29bd032698cf6

diff --git a/doc/using-kdesvn-build/advanced-features.docbook 
b/doc/using-kdesvn-build/advanced-features.docbook
index 920a1d6e..c001786e 100644
--- a/doc/using-kdesvn-build/advanced-features.docbook
+++ b/doc/using-kdesvn-build/advanced-features.docbook
@@ -117,7 +117,7 @@ into the  build system and improve the build process 
by replacing some of
 the tools normally used (including  and ). It is especially 
useful for those who
 are performing distributed compilation as it is much faster than the normal
 build system in this situation. However, even for a single computer build,
- is faster than the competition.
+ is faster than the competitors.
 
 
 In addition,  includes support for estimating the progress of
diff --git a/doc/using-kdesvn-build/other-features.docbook 
b/doc/using-kdesvn-build/other-features.docbook
index 484dad7a..60ef4660 100644
--- a/doc/using-kdesvn-build/other-features.docbook
+++ b/doc/using-kdesvn-build/other-features.docbook
@@ -31,7 +31,7 @@ debugging information for many functions.
 
 Color output
 When being run from  or a different terminal, 
-will normally display with colorized test.
+will normally display with colorized text.
 
 You can disable this by using the --no-color on the
 command line, or by setting the  option in the configuration file to

[utilities/konsole] doc/manual: Fix minor typo

[Yuri Chornoivan]

Git commit 392ede3008cd233289ce87a3841f982d67ca6397 by Yuri Chornoivan.
Committed on 24/04/2024 at 07:57.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/manual/index.docbook

https://invent.kde.org/utilities/konsole/-/commit/392ede3008cd233289ce87a3841f982d67ca6397

diff --git a/doc/manual/index.docbook b/doc/manual/index.docbook
index c93fb3cc9..167d45dbc 100644
--- a/doc/manual/index.docbook
+++ b/doc/manual/index.docbook
@@ -509,7 +509,7 @@ A vertical line at column 80 (or another). This is 
configured in the M
  Line numbers may be displayed as an overlay of the terminal 
text. Line numbers appear in red on the right end of each line.
 The line are numbered consecutively from the first (top) line in the 
scrollback. Displaying the line numbers can be configured in
 the Advanced page in the Edit 
Profile dialog.
-Cycling between the three displayed mode can also be done by a keyboard 
shortcut. The default shortcut is
+Cycling between the three displayed modes can also be done by a keyboard 
shortcut. The default shortcut is
 \
 
 

[network/smb4k] doc: Fix minor typo

[Yuri Chornoivan]

Git commit ecbd7eeaa932f60c6637eee30c00ff8126093b36 by Yuri Chornoivan.
Committed on 05/04/2024 at 12:31.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/index.docbook

https://invent.kde.org/network/smb4k/-/commit/ecbd7eeaa932f60c6637eee30c00ff8126093b36

diff --git a/doc/index.docbook b/doc/index.docbook
index 2273a26d..69f17331 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -1501,7 +1501,7 @@ server min protocol = NT1
 ...
 
   
-  If you want to fix this issue for a  server, please 
contact the sysadmin and tell her or him that NTLMv1 authentication and the SMB 
1.0/ protocol should be swtiched on (if possible).
+  If you want to fix this issue for a  server, please 
contact the sysadmin and tell her or him that NTLMv1 authentication and the SMB 
1.0/ protocol should be switched on (if possible).
 
   It is not advisable to enable the SMB 1.0/ protocol on 
a server, because it is considered insecure (see  https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-smb1/ba-p/425858;>here)
 and was thus disabled in newer  and  versions (see  https://learn.microsoft.com/en-us/archive/blogs/josebda/the-deprecation-of-smb1-you-should-be-planning-to-get-rid-of-this-old-smb-dialect;>here
 and https://www.samba.org/samba/history/samba-4.11.0.html;>here).
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 213420d9005ba2745e31a5e2eb4ce2143f5571d3 by Yuri Chornoivan.
Committed on 01/04/2024 at 12:57.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/213420d9005ba2745e31a5e2eb4ce2143f5571d3

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 85703a8ede..976ab2f61e 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -236,7 +236,7 @@
 
  When a new Optical Train is created, Focus will attempt to default 
parameters from
 other, similar Optical Trains. The attributes that must match for this are 
the Focuser and
-the scope type. If this is the first train for the seclected Focuser and 
scope type then
+the scope type. If this is the first train for the selected Focuser and 
scope type then
 default parameters are created.
 
  It is recommended to use the
@@ -1034,7 +1034,7 @@
 
   
  Average HFR check: Similar idea to 
Average Over but in this case
-it it the HFR Check datapoint that is averaged over the selected 
number of frames. In addition, if the
+it is the HFR Check datapoint that is averaged over the selected 
number of frames. In addition, if the
 Algorithm is Linear 1 Pass then the last 
datapoint of an Autofocus run, which is the
 in-focus datapoint, is also averaged over this number of frames. Set a 
value of 1 to start. This can be increased
 if there are issues with HFR Check Autofocus runs being triggered by 
outlying datapoints when the HFR Check runs.

Re: delete entire page in Okular

[Yuri Chornoivan]

вівторок, 5 березня 2024 р. 12:39:05 EET CCT Team написано:
> Hello there,
> 
> I am a big fan of the program and I use it quite a bit. Now, I wanted to
> delete a blank page from a pdf document, but a 5 Min research did not
> find any clues, can you help please?
> 
> Kind regards,
> 
> Petra

Hi,

Okluar is not a PDF editor (that's the developer's point of view).

Please use simple editors (PDF Arranger) to remove pages.

Best regards,
Yuri

[education/kstars] doc: Fix XML

[Yuri Chornoivan]

Git commit 3166a6a4501527ecf3a3a20be5db09e5d8a6d5e8 by Yuri Chornoivan.
Committed on 19/02/2024 at 06:46.
Pushed by yurchor into branch 'master'.

Fix XML

M  +1-0doc/config.docbook

https://invent.kde.org/education/kstars/-/commit/3166a6a4501527ecf3a3a20be5db09e5d8a6d5e8

diff --git a/doc/config.docbook b/doc/config.docbook
index a65cf581f1..5fd733635d 100644
--- a/doc/config.docbook
+++ b/doc/config.docbook
@@ -1628,6 +1628,7 @@ from the 
SettingsFOV Symbols
   
 If your instrument is using an erecting prism, typically used on 
Schmidt-Cassegrain and refracting type telescopes, the view through the 
eyepiece will be mirrored horizontally. You can have the sky map match this by 
checking the Mirrored View option under the 
View menu.
+  
   
 Next, to rotate the sky map freely, you can hold down the  key and 
drag the mouse on the sky map. A temporary overlay will appear showing the 
direction of north and zenith at the point, and displaying the angle they make 
with the vertical in a counterclockwise sense. The orientations of zenith and 
north will update as you rotate the sky map. Letting go of  or the mouse 
button will stop the rotation operation. As you pan the sky map or focus it on 
different objects, the rotation you set is retained as an offset from the 
reference direction. The reference direction is north when using Equatorial 
Coordinates and zenith when using Horizontal Coordinates. As a reminder, the 
reference direction is solid and brighter in the temporary overlay. For the two 
common orientations of erect and inverted, the rotation can be set / reset 
using the ViewSkymap 
Orientation submenu. Select "North Down" or "Zenith 
Down" as is applicable to set an orientation of 180 degrees.
   

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit d8ea2a0546ed7ad7a5a80efcc077b90b4572af39 by Yuri Chornoivan.
Committed on 08/02/2024 at 07:23.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +5-5doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/d8ea2a0546ed7ad7a5a80efcc077b90b4572af39

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index f306a3e0e3..4cc44180b1 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -609,7 +609,7 @@
   
 
 
-Mask Section Paramters:
+Mask Section Parameters:
 
 These controls relate to Masking 
Options
 to be used when in Full Field mode. The effect of 
Masking Options can be seen in the
@@ -1024,7 +1024,7 @@
 moves out to take its first datapoint, an exposure of 2s * 4 = 8s is 
used. On each successive datapoint the
 exposure is reduced down to 2s around the point of optimum focus. As 
the focuser moves through focus, so the
 exposure is scaled upwards to 8s for the last datapoint.
- The purpose of this feature is to increase the brighness of out 
of focus datapoints which will be dimmer than
+ The purpose of this feature is to increase the brightness of 
out of focus datapoints which will be dimmer than
 in-focus datapoints and therefore harder for star detection to resolve 
from the background noise.
  This feature assumes Autofocus is run from near to optimum 
focus.
 
@@ -1252,7 +1252,7 @@
   
 
 
- Focus CFZ Parameters:.
+Focus CFZ Parameters:
 
   
   
@@ -1274,9 +1274,9 @@
 Focus 
Mechanics
 
  It is necessary to specify the Step Size 
parameter which specifies in microns how far one tick
-moves the focal plane. For refractors there is uaually a 1-to-1 
relationship between moving the focuser which moves the
+moves the focal plane. For refractors there is usually a 1-to-1 
relationship between moving the focuser which moves the
 telescope draw-tube mechanism and the focal plane movement. For other 
types of telescope the relationship is likely to be
-more complex. Refer to details of your telescope / manufacturer for this 
inmformation.
+more complex. Refer to details of your telescope / manufacturer for this 
information.
 
  The following algorithms are available:
 

[sdk/kdesrc-build] doc: Fix XML

[Yuri Chornoivan]

Git commit 3f5708b4b27983980e3d4456af67c97e8789d048 by Yuri Chornoivan.
Committed on 29/01/2024 at 13:53.
Pushed by yurchor into branch 'master'.

Fix XML

M  +1-1doc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/3f5708b4b27983980e3d4456af67c97e8789d048

diff --git a/doc/conf-options-table.docbook b/doc/conf-options-table.docbook
index 63adbf01..345ef74e 100644
--- a/doc/conf-options-table.docbook
+++ b/doc/conf-options-table.docbook
@@ -1300,8 +1300,8 @@ installations. However this only works on build systems 
that support
 
 
 
-
 These options do not require any value (except "filter-out-phases"). 
They are applied if they are presented in a section.
+
 Phase selection options
 
 

[education/kstars] doc: Fix links in documentation

[Yuri Chornoivan]

Git commit 5d6ed6b40b105f5d8ff826951d8ea766f7e88af8 by Yuri Chornoivan.
Committed on 11/01/2024 at 08:28.
Pushed by yurchor into branch 'master'.

Fix links in documentation

M  +2-2doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/5d6ed6b40b105f5d8ff826951d8ea766f7e88af8

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 6d8ee36371..6d6a5edcea 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -545,8 +545,8 @@ Approaches to imaging can vary greatly in the selection of 
exposure times, and n
 
 
 Sky Quality: The 
Sky Quality selector sets the measurement of the magnitude 
per square arc-second of the background sky.
-The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Sky_brightness;>Wikipedia 
Sky Brightness  
-https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
+The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Sky_brightness;>Wikipedia 
Sky Brightness
+https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
 
All light scattered in the background sky is 
considered to be light pollution regardless of its source, so the effects of 
moonlight should be considered as "natural" light pollution. But weather 
conditions can also impact Sky Quality, as humidity or cloud cover can reflect 
and scatter any source of light through the atmosphere
 

[sdk/kdesrc-build] doc: Fix XML and minor typos

[Yuri Chornoivan]

Git commit 70d00640fd642476dd6904b311e1cf9e96c72a9b by Yuri Chornoivan.
Committed on 08/01/2024 at 09:31.
Pushed by yurchor into branch 'master'.

Fix XML and minor typos

M  +3-3doc/supported-cmdline-params.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/70d00640fd642476dd6904b311e1cf9e96c72a9b

diff --git a/doc/supported-cmdline-params.docbook 
b/doc/supported-cmdline-params.docbook
index 3114de5f..f27563dd 100644
--- a/doc/supported-cmdline-params.docbook
+++ b/doc/supported-cmdline-params.docbook
@@ -165,7 +165,7 @@ specify other module names on the command line.
 
 
 If you want to avoid source updates
-when resuming, simply pass --no-src
+when resuming, simply pass --no-src
 in addition to the other options.
 
 
@@ -572,7 +572,7 @@ Enable or disable colorful output. By default, this option 
is enabled for intera
 
 
 
---nice (or 
--niceness)value
+--nice (or --niceness) 
value
 
 This value adjusts the computer CPU priority requested by , and
 should be in the range of 0-20. 0 is highest priority (because it is the
@@ -730,11 +730,11 @@ prove useful in bug reports or when asking for help in 
forums or mailing lists.
 
 
 
-
 
 
 Any other command-line options are assumed to be modules to update and build.
 Please, do not mix building with installing.
 
 
+
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 8000761333e5751f749ba84372aacb420f1b7373 by Yuri Chornoivan.
Committed on 25/12/2023 at 07:48.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/8000761333e5751f749ba84372aacb420f1b7373

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 3779c182e9..597cd5bf25 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -370,7 +370,7 @@
 
 
 
-The overlay options button opens a dialog that allows arbitary and 
flexible creation of ellipses (including circles), rectangles and lines, as 
well as anchor points which act as global drawing offsets. Each defined element 
has it's own size, offset, repetition, thickness and color (including 
transparency).
+The overlay options button opens a dialog that allows arbitrary 
and flexible creation of ellipses (including circles), rectangles and lines, as 
well as anchor points which act as global drawing offsets. Each defined element 
has its own size, offset, repetition, thickness and color (including 
transparency).
 
 
 

Re: [doc-primer] Update copyright information

[Yuri Chornoivan]

пʼятниця, 8 грудня 2023 р. 17:49:18 EET Jason Yundt написано:
> Hi,
> 
> I noticed that the doc-primer says that it’s copyright 2004 [1].
> Attached is a patch that adds copyright years for each year in the svn
> log. It should be applied to /trunk/www/areas/l10n/docs/doc-primer.
> 
> I couldn’t find any documentation for how to contribute to KDE
> Subversion repos, so I’m not sure if this is the correct way to submit a
> patch. If there’s anything that I should have done differently, please
> let me know. After this patch gets reviewed, I want to update the KDE
> Community Wiki’s Subversion page [2], and add instructions for how to
> propose changes even if you don’t have commit access.
> 
> Thanks in advance,
> Jason Yundt
> 
> [1]: 
> [2]: 

Hi,

It seems that what you have done is the correct way to post patches to these 
files. There is no other way because you should have permissions to write into 
the svn branches.

Applied anyway. Many thanks for your work.

Best regards,
Yuri

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 16796ae7aa45f7dcd7e975cae605e3ec86ae9f0b by Yuri Chornoivan.
Committed on 06/12/2023 at 08:06.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/index.docbook

https://invent.kde.org/education/kstars/-/commit/16796ae7aa45f7dcd7e975cae605e3ec86ae9f0b

diff --git a/doc/index.docbook b/doc/index.docbook
index b5d78d59ab..6b7efa7144 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -247,7 +247,7 @@ For students and teachers, it supports adjustable 
simulation speeds in order to
 
  

- Ekos is a complete astrophotography solution that provides everything 
needed for automated or manual deep-sky imaging.  It can control all INDI 
devices including numerous telescopes, CCD and CMOS astronomy cameras, DSLRs, 
focusers, filters, rotators, domes and a lot more. Ekos supports highly 
accurate tracking using online and offline astrometry solvers, autofocus and 
autoguiding capabilities, and capture of single or multiple images using its 
powerful built in scheduler.  It integrates well with the skymap, and FITS 
Viewer. It also has tools for polar alignment and measuing optical aberrations.
+ Ekos is a complete astrophotography solution that provides everything 
needed for automated or manual deep-sky imaging.  It can control all INDI 
devices including numerous telescopes, CCD and CMOS astronomy cameras, DSLRs, 
focusers, filters, rotators, domes and a lot more. Ekos supports highly 
accurate tracking using online and offline astrometry solvers, autofocus and 
autoguiding capabilities, and capture of single or multiple images using its 
powerful built-in scheduler.  It integrates well with the skymap, and FITS 
Viewer. It also has tools for polar alignment and measuring optical aberrations.
   
  
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 0a8c955febd324a24ccd9ced549017cbebefb472 by Yuri Chornoivan.
Committed on 05/12/2023 at 14:22.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/ekos.docbook
M  +1-1doc/obsplanner.docbook

https://invent.kde.org/education/kstars/-/commit/0a8c955febd324a24ccd9ced549017cbebefb472

diff --git a/doc/ekos.docbook b/doc/ekos.docbook
index 89a2eeecf7..794a3dd486 100644
--- a/doc/ekos.docbook
+++ b/doc/ekos.docbook
@@ -35,7 +35,7 @@
 
 
 
-Measure  Correct Polar Alignment errors using astromety.net 
solver.
+Measure  Correct Polar Alignment errors using astrometry.net 
solver.
 
 
 
diff --git a/doc/obsplanner.docbook b/doc/obsplanner.docbook
index 54384bdc08..e9f5e3023a 100644
--- a/doc/obsplanner.docbook
+++ b/doc/obsplanner.docbook
@@ -138,7 +138,7 @@ it could be a bit more detailed. Here you can see the same 
categories of objects
   
 
   
-  You can choose the treshold of magnitude for the objects to be shown. 
In astronomy, absolute magnitude (also known as absolute visual magnitude when 
measured in the standard V photometric band) measures a celestial objects 
intrinsic brightness.
+  You can choose the threshold of magnitude for the objects to be shown. 
In astronomy, absolute magnitude (also known as absolute visual magnitude when 
measured in the standard V photometric band) measures a celestial objects 
intrinsic brightness.
   
 
   

[education/kstars] doc: Fix XML

[Yuri Chornoivan]

Git commit c59528b137412891f57df0f7933988171b5b8438 by Yuri Chornoivan.
Committed on 05/12/2023 at 14:16.
Pushed by yurchor into branch 'master'.

Fix XML

M  +2-0doc/index.docbook

https://invent.kde.org/education/kstars/-/commit/c59528b137412891f57df0f7933988171b5b8438

diff --git a/doc/index.docbook b/doc/index.docbook
index 3065056719..b5d78d59ab 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -234,6 +234,7 @@
  is free, open source, cross-platform astronomy software. It provides 
the  skymap, a digital planetarium with overlays and simulation tools, 
the Ekos astrophotography suite which acts as a client for INDI device drivers, 
and the FITS Viewer which displays captured sky images.
 
 
+
 
  

@@ -257,6 +258,7 @@ For students and teachers, it supports adjustable 
simulation speeds in order to
  
 
 
+
 

 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 44e5086501f8c6513bfd00e321b42d4c5ef0b46d by Yuri Chornoivan.
Committed on 02/12/2023 at 22:23.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +4-4doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/44e5086501f8c6513bfd00e321b42d4c5ef0b46d

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 5f816339a7..3f48da3f16 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -520,12 +520,12 @@ Approaches to imaging can vary greatly in the selection 
of exposure times, and n
 
 Sky Quality: The 
Sky Quality selector sets the measurement of the magnitude 
per square arc-second of the background sky.
 The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia 
Sky Brightness  
-https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
+https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
 
All light scattered in the background sky is 
considered to be light pollution regardless of its source, so the effects of 
moonlight should be considered as "natural" light pollution. But weather 
conditions can also impact Sky Quality, as humidity or cloud cover can reflect 
and scatter any source of light through the atmosphere
 
-   A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter 
(SQM)
- can provide the most accurate reading of sky quality if used during an 
imaging session, but an estimated value from sky quality surveys may also be 
found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or 
https://clearoutside.com/;>www.clearoutside.com. But these 
on-line sources for estimated light pollution generally do not account for the 
effects of moonlight or local weather conditions.  So the values from light 
pollution web sites should only be considered as a “best case scenario” for a 
cloudless night during a new moon. 
+   A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter 
(SQM)
+ can provide the most accurate reading of sky quality if used during an 
imaging session, but an estimated value from sky quality surveys may also be 
found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or 
https://clearoutside.com/;>www.clearoutside.com. But these 
on-line sources for estimated light pollution generally do not account for the 
effects of moonlight or local weather conditions.  So the values from light 
pollution web sites should only be considered as a “best case scenario” for a 
cloudless night during a new moon. 
 
If a light pollution map value is used for the 
input value of SQM, but imaging will be performed with a partial moon, then a 
decrease in the input of the SQM value should be applied in the calculator.  
Moonlight can be overwhelming; at a location where a light pollution map showed 
an SQM value of 19.63. An SQM reading was made on a night with a waxing 
crescent, shortly before half-moon, (moon age 5.4, and KStars moon magnitude = 
-10). The SQM reading at zenith showed the sky to be much brighter with 
measured value of 18.48. A reading taken on a night with a waxing gibbous, 
shortly before a full moon, (moon age 12.4, and KStars moon magnitude = -12). 
The SQM reading at zenith showed a measured SQM value of 15.95.
 The value of Sky Quality has a drastic impact on the calculated exposure 
because of the logarithmic scale involved.  An image taken from a location with 
heavy light pollution (a low sky quality value), especially when filtering is 
not applied, may result in a very short exposure time to prevent light 
pollution from overwhelming the target signal. An image taken from a location 
with very little light pollution (a high Sky Quality value) may result in an 
sub-exposure time of several hours.
@@ -559,7 +559,7 @@ Even within the bands that filters are intended to pass, 
filters are not 100% ef
 Camera sensors are one of two types: "Charge Coupled Device" (CCD) or 
"Complementary Metal-Oxide Semiconductor" (CMOS).  For the exposure calculation 
the main difference between these sensor types is that CCD sensors do not have 
a variable gain setting that would impact the read 

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 5112379ddb1c55bb4f10e227e3543a639486034e by Yuri Chornoivan.
Committed on 02/12/2023 at 22:20.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/5112379ddb1c55bb4f10e227e3543a639486034e

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 6610f9cb33..5f816339a7 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -519,7 +519,7 @@ Approaches to imaging can vary greatly in the selection of 
exposure times, and n
 
 
 Sky Quality: The 
Sky Quality selector sets the measurement of the magnitude 
per square arc-second of the background sky.
-The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia 
Sky Brightness  
+The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia 
Sky Brightness  
 https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
 
All light scattered in the background sky is 
considered to be light pollution regardless of its source, so the effects of 
moonlight should be considered as "natural" light pollution. But weather 
conditions can also impact Sky Quality, as humidity or cloud cover can reflect 
and scatter any source of light through the atmosphere

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 397fcc66b4cb982045868a16c6d5d40bbfda5401 by Yuri Chornoivan.
Committed on 02/12/2023 at 22:18.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/397fcc66b4cb982045868a16c6d5d40bbfda5401

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 10d53f6ef0..459e9a4d46 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -2162,7 +2162,7 @@
 autofocus-(datetime).txt files from a few nights of observing into a 
spreadsheet and graph focus position against temperature
 for each filter. Review the data and remove any outliers and plot a line 
of best fit. Use the line to get
 Ticks / °C. If you intend to adapt for altitude as 
well as temperature, then it would be better to use a
-set of data at similar altitude when calibrating temperature. Then its 
possible to calculate the effect of Temperature and
+set of data at similar altitude when calibrating temperature. Then it's 
possible to calculate the effect of Temperature and
 remove this from the data when calculating the effect of Altitude.
 
  You will need to ensure that your focus position is repeatable at 
the same temperature and altitude and that there
@@ -2532,7 +2532,7 @@
 some calculations may not be performed. If the Centre tile is 
excluded, no calculations can be
 performed.
 
-Note that whilst its possible to exclude tiles and still get 
calculated values, if the data
+Note that whilst it's possible to exclude tiles and still get 
calculated values, if the data
 is poor quality then it is recommended to rerun Aberration Inspector 
rather than persist with poor
 quality data.
   

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd by Yuri Chornoivan.
Committed on 02/12/2023 at 19:28.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/commands.docbook
M  +2-2doc/ekos-capture.docbook
M  +1-1doc/ekos-focus.docbook
M  +1-1doc/timezones.docbook

https://invent.kde.org/education/kstars/-/commit/41cb8e87b737a6e30234d78d2e2bfeb21c2b83bd

diff --git a/doc/commands.docbook b/doc/commands.docbook
index 8560d8da73..721a4cef01 100644
--- a/doc/commands.docbook
+++ b/doc/commands.docbook
@@ -17,7 +17,7 @@
 File
 Open Image...
 
-Open a image in the FITS Viewer tool.
+Open an image in the FITS Viewer tool.
 
 
 
diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 80c67d6a10..6610f9cb33 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -646,7 +646,7 @@ The value of image stacking is that as images are stacked, 
the accumulation of e
 
 
 Table: A table 
provides details for stacking based upon the number of hours planned for 
imaging.
-The table provides a quick reference for finding the approximate number 
of sub-exposures that might be completed for a given number of hours in a 
imaging session. But some functions that consume time are not included in this 
time calculation. For example, USB based cameras typically take some time for 
data transmission, or if the user has selected automatic dithering, additional 
time will be consumed in the imaging process, which is not included in this 
time calculation.
+The table provides a quick reference for finding the approximate number 
of sub-exposures that might be completed for a given number of hours in an 
imaging session. But some functions that consume time are not included in this 
time calculation. For example, USB based cameras typically take some time for 
data transmission, or if the user has selected automatic dithering, additional 
time will be consumed in the imaging process, which is not included in this 
time calculation.
 The far right column of the table shows the calculated time/noise ratio 
of the integrated (stacked) image that would be produced.
 
 
@@ -669,7 +669,7 @@ Depending on the various inputs and imaging conditions, the 
potential quality of
 
 
 
-Part of the value of using a Time/Noise ratio as the input for the calculation 
of the required number of sub-exposures is that it should tend to compensate 
for the differences in relative noise for sub-exposures of various lengths.  A 
shorter sub-exposure would have a lower time/noise ratio, so it has less 
capacity to improve a integrated image.  Therefore, a disproportionately higher 
number of short exposures are needed to achieve a given time/noise ratio in an 
integrated image.
+Part of the value of using a Time/Noise ratio as the input for the calculation 
of the required number of sub-exposures is that it should tend to compensate 
for the differences in relative noise for sub-exposures of various lengths.  A 
shorter sub-exposure would have a lower time/noise ratio, so it has less 
capacity to improve an integrated image.  Therefore, a disproportionately 
higher number of short exposures are needed to achieve a given time/noise ratio 
in an integrated image.
 
 As an example, consider the calculation of the number of sub-exposures 
required when two sub-exposures times were compared: a 300 second sub-exposure 
vs a 30 second sub-exposure. The 300 second sub-exposure had a calculated noise 
of 22.1, resulting in a sub-exposure time/noise ratio of 13.6. When the 'noise 
increase %' is raised to force the exposure time down to 30 seconds, we see a 
calculated noise of 9.47, resulting in a much lower sub-exposure time/noise 
ratio of 3.2.  The 300 second exposure is of significantly higher potential 
quality than the 30 second exposure. We will demand the default time/noise 
ratio of 80 for integration in both of these cases. 
 
diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 0e4292fd7f..10d53f6ef0 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -2400,7 +2400,7 @@
 will vary by equipment and must be discovered by the user by trial and 
error. Always follow the recommendations of
 the tilt / backfocus device manufacturer.
 
-Each time Aberration Inspector is run it lauches a new dialog with 
the run number appended to the title.
+Each time Aberration Inspector is run it launches a new dialog with 
the run number appended to the title.
 This way several runs can be performed and the results compared. Note, 
however, that the dialog holds a lot of
 data (roughly 10x the amount of a standard Autofocus run). The system 
resources associated with this are released
 when the dialog is closed. For this reason on lower powered machines, once 
the tool has been used, it is recommended
diff --git

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 187dcff04e640624de09bca1e8926f4138161191 by Yuri Chornoivan.
Committed on 02/12/2023 at 07:50.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +5-5doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/187dcff04e640624de09bca1e8926f4138161191

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 048c1ade91..0e4292fd7f 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -2396,13 +2396,13 @@
 
 Repeat the above process until the limit of sensitivity of the 
equipment is reached.
 
-Note the amount of adjustment, e.g. how far to turn bolts, and the 
sense, counterwise or counter-clockwise,
+Note the amount of adjustment, e.g. how far to turn bolts, and the 
sense, clockwise or counter-clockwise,
 will vary by equipment and must be discovered by the user by trial and 
error. Always follow the recommendations of
 the tilt / backfocus device manufacturer.
 
 Each time Aberration Inspector is run it lauches a new dialog with 
the run number appended to the title.
 This way several runs can be performed and the results compared. Note, 
however, that the dialog holds a lot of
-data (roughtly 10x the amount of a standard Autofocus run). The system 
resources associated with this are released
+data (roughly 10x the amount of a standard Autofocus run). The system 
resources associated with this are released
 when the dialog is closed. For this reason on lower powered machines, once 
the tool has been used, it is recommended
 to close all Aberration Inspector dialogs before imaging.
 
@@ -2650,7 +2650,7 @@
   
 
   
-  Slice: A 2D slice throught the 3D graphic is displayed.
+  Slice: A 2D slice through the 3D graphic is displayed.
   
 
 
@@ -2684,9 +2684,9 @@
   
 
 
-The 3D graphic is not essential to using Aberration Inspector. All 
relevent information is displayed in the
+The 3D graphic is not essential to using Aberration Inspector. All 
relevant information is displayed in the
 Table and Results
-sections of the dialog. Its purpose is to aid the user in undertanding 
Aberration Inspector and to orient themselves
+sections of the dialog. Its purpose is to aid the user in understanding 
Aberration Inspector and to orient themselves
 with the information the tool provides.
 
   

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 08c25289fef2471ff42c529a9ed322004ff298c4 by Yuri Chornoivan.
Committed on 30/11/2023 at 20:27.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/08c25289fef2471ff42c529a9ed322004ff298c4

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 4237c7268c..80c67d6a10 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -507,7 +507,7 @@
The concept in Dr. Glover's calculation is to provide a 
sufficiently long exposure so that the effects of camera read-noise are 
overwhelmed by the signal coming from the target, but not so long an exposure 
that the effects of light pollution rise to levels which would overwhelm the 
signal from the target.
 
 
-   The implementation of this process does not consider 
the strength (magnitude or flux) of the intended target, nor does it consider 
other factors which may cause an astrophotographer to choose a alternate 
sub-exposure time. These other factors may include: the storage requirements 
and extended post-processing time for a large number of short exposures, the 
impacts of external factors that might occur in very long exposures, such as 
tracking / guiding performance, changes in weather conditions which may disrupt 
seeing conditions, intrusions from air traffic or passing satellites.
+   The implementation of this process does not consider 
the strength (magnitude or flux) of the intended target, nor does it consider 
other factors which may cause an astrophotographer to choose an alternate 
sub-exposure time. These other factors may include: the storage requirements 
and extended post-processing time for a large number of short exposures, the 
impacts of external factors that might occur in very long exposures, such as 
tracking / guiding performance, changes in weather conditions which may disrupt 
seeing conditions, intrusions from air traffic or passing satellites.
 
 
 Approaches to imaging can vary greatly in the selection of exposure times, and 
number of sub-exposures used for integration. A well accepted approach for 
imaging deep-sky objects utilizes long exposures, requires good guiding, good 
to excellent seeing conditions, and would typically employ filtering to reduce 
the effects of light pollution. At the other extreme are approaches such as 
speckle imaging techniques (commonly 'lucky imaging'), which utilize many 
hundreds to many thousands of extremely short exposures in an attempt to 
eliminate the effects of light pollution, poor seeing conditions, and poor 
guiding. Choices made for values of certain inputs to the exposure calculator 
will vary depending upon which imaging approach is being employed.

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 323adaebb6b30b3b11428819a03dd1f5c92f0644 by Yuri Chornoivan.
Committed on 30/11/2023 at 07:16.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +7-7doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/-/commit/323adaebb6b30b3b11428819a03dd1f5c92f0644

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index bbbf7ba139..4237c7268c 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -510,7 +510,7 @@
The implementation of this process does not consider 
the strength (magnitude or flux) of the intended target, nor does it consider 
other factors which may cause an astrophotographer to choose a alternate 
sub-exposure time. These other factors may include: the storage requirements 
and extended post-processing time for a large number of short exposures, the 
impacts of external factors that might occur in very long exposures, such as 
tracking / guiding performance, changes in weather conditions which may disrupt 
seeing conditions, intrusions from air traffic or passing satellites.
 
 
-Approaches to imaging can vary greatly in the selection of exposure times, and 
number of sub-exposures used for integration. A well accepted approach for 
imaging deep-sky objects utilizes long exposures, requires good guiding, good 
to excellent seeing conditions, and would typically employ filtering to reduce 
the effects of light polution. At the other extreme are approaches such as 
speckle imaging techniques (commonly 'lucky imaging'), which utilize many 
hundreds to many thousands of extremely short exposures in an attempt to 
eliminate the effects of light pollution, poor seeing conditions, and poor 
guiding. Choices made for values of certain inputs to the exposure calculator 
will vary depending upon which imaging approach is being employed.
+Approaches to imaging can vary greatly in the selection of exposure times, and 
number of sub-exposures used for integration. A well accepted approach for 
imaging deep-sky objects utilizes long exposures, requires good guiding, good 
to excellent seeing conditions, and would typically employ filtering to reduce 
the effects of light pollution. At the other extreme are approaches such as 
speckle imaging techniques (commonly 'lucky imaging'), which utilize many 
hundreds to many thousands of extremely short exposures in an attempt to 
eliminate the effects of light pollution, poor seeing conditions, and poor 
guiding. Choices made for values of certain inputs to the exposure calculator 
will vary depending upon which imaging approach is being employed.
 
 

@@ -522,10 +522,10 @@ Approaches to imaging can vary greatly in the selection 
of exposure times, and n
 The range for Sky Quality is from 22 for the 
darkest skies, to 16 for the brightest (most light-polluted) skies. The 
magnitude scale is non-linear; it is a logarithmic scale based on the 5th root 
of 100. So 5 steps on the scale represent a change in brightness by a factor of 
100. (A Sky Quality of 17 is 100 times as bright as a Sky Quality of 22. Each 
full integer step on the scale is a change by a factor of approximately 
2.512.). https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia 
Sky Brightness  
 https://en.wikipedia.org/wiki/Light_pollution;>Wikipedia Light 
Pollution
 
-   All light scattered in the backgound sky is 
considered to be light pollution regardless of its source, so the effects of 
moonlight should be considered as "natural" light pollution. But weather 
conditions can also impact Sky Quality, as humidity or cloud cover can reflect 
and scatter any source of light through the atmosphere
+   All light scattered in the background sky is 
considered to be light pollution regardless of its source, so the effects of 
moonlight should be considered as "natural" light pollution. But weather 
conditions can also impact Sky Quality, as humidity or cloud cover can reflect 
and scatter any source of light through the atmosphere
 
A https://en.wikipedia.org/wiki/Sky_quality_meter;>Sky Quality Meter 
(SQM)
- can provide the most accurate reading of sky quality if used during an 
imaging session, but an estimated value from sky quality surveys may also be 
found on the web at sites such as https://www.lightpollutionmap.info/;>www.lightpollutionmap.info or 
https://clearoutside.com/;>www.clearoutside.com. But these 
on-line sources for estimated light pollution genearrly do not account for the 
effects of moonlight or local weather conditions.  So the values from light 
pollution web sites should only be considered as a “best case scenario” for a 
cloudless night during a new moon. 
+ can provide the most accurate reading of sky quality

[office/skrooge] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 70e5010abdb0a79910647c182e74084dd560fe23 by Yuri Chornoivan.
Committed on 27/11/2023 at 08:10.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/index.docbook

https://invent.kde.org/office/skrooge/-/commit/70e5010abdb0a79910647c182e74084dd560fe23

diff --git a/doc/index.docbook b/doc/index.docbook
index c16fdab0c..e849c16c2 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -2306,7 +2306,7 @@ file is opened. It is also recommended to create a 
different account ( "ETF"

  Assign Schedule
  
- If you scheduled an operation that is being repeated on a 
regular basis, you can link some old operations to this schedule using the 
"Assign schedule" context menu of an operation. This menu also allow to unlink 
an operation from a schedule or link it to a differrent one.
+ If you scheduled an operation that is being repeated on a 
regular basis, you can link some old operations to this schedule using the 
"Assign schedule" context menu of an operation. This menu also allow to unlink 
an operation from a schedule or link it to a different one.
  
  

[frameworks-kdoctools] [Bug 477015] GNU Free Documentation License - version 1.1

[Yuri Chornoivan]

https://bugs.kde.org/show_bug.cgi?id=477015

Yuri Chornoivan  changed:

   What|Removed |Added

 CC||yurc...@ukr.net

--- Comment #2 from Yuri Chornoivan  ---
(In reply to Christopher Yeleighton from comment #1)
> The following patch should do the trick (with rename):
> 
> -- a/common/CMakeLists.txt2023-11-04 11:02:07.0 +0100
> +++ b/common/CMakeLists.txt   2023-11-15 00:55:39.713916560 +0100
> @@ -1,6 +1,11 @@
> +set(GFDL_TITLE "GNU Free Documentation License")
> +set(GFDL_VERSION "1.2")
> +configure_file("en/fdl-license.html.in" "en/fdl-license.html" @ONLY)
> +
>  # install common files for all languages
>  foreach( _kdoctoolscommon_currentlang ${KDOCTOOLS_LANGUAGES_LIST})
>  file( GLOB _kdoctoolscommon_lang_allfiles
> "${_kdoctoolscommon_currentlang}/*" )
> +list(TRANSFORM _kdoctoolscommon_lang_allfiles REPLACE
> "^.*/common(/.*)\\.in$" "${CMAKE_CURRENT_BINARY_DIR}\\1")
>  install(FILES ${_kdoctoolscommon_lang_allfiles} DESTINATION
> ${KDE_INSTALL_DOCBUNDLEDIR}/${_kdoctoolscommon_currentlang}/kdoctools5-
> common)
>  endforeach()
>  
> @@ -8,10 +13,16 @@
>  # help:/kdoctools5-common/gpl-translated.html always works even
>  # if the translated file for the current language does not exist,
>  # thanks to kio_help's fallback on the English version.
> -set (_basetranslatedlicenses fdl gpl lgpl)
> +set (_basetranslatedlicenses fdl)
>  foreach (_licenseprefix ${_basetranslatedlicenses})
> -install(FILES en/${_licenseprefix}-license.html DESTINATION
> +install(FILES
> ${CMAKE_CURRENT_BINARY_DIR}/en/${_licenseprefix}-license.html DESTINATION
>  ${KDE_INSTALL_DOCBUNDLEDIR}/en/kdoctools5-common/
>  RENAME ${_licenseprefix}-translated.html)
>  endforeach()
>  
> +set (_basetranslatedlicenses gpl lgpl)
> +foreach (_licenseprefix ${_basetranslatedlicenses})
> +install(FILES en/${_licenseprefix}-license.html DESTINATION
> +${KDE_INSTALL_DOCBUNDLEDIR}/en/kdoctools5-common/
> +RENAME ${_licenseprefix}-translated.html)
> +endforeach()
> --- a/common/en/fdl-license.html  2023-11-04 11:02:07.0 +0100
> +++ b/common/en/fdl-license.html.in   2023-11-15 00:56:52.988901584 +0100
> @@ -2,7 +2,7 @@
> "http://www.w3.org/TR/html40/strict.dtd;>
>  
>
> -GNU Free Documentation License - version 1.1
> +@GFDL_TITLE@, version @GFDL_VERSION@
>  
>  
>  
> @@ -12,9 +12,9 @@
>  
>
>
> -GNU Free Documentation License
> +@GFDL_TITLE@
>  
> -  Version 1.2, November 2002
> +  Version @GFDL_VERSION@, November 2002
>  
> 
>  

Hi,

Is it possible to put this patch on the git tracker for the real developers'
consideration?

https://invent.kde.org/frameworks/kdoctools

Thanks in advance for your work.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[sdk/kdesrc-build] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 883f068eabace140d44e3bd9b68d415fc1c4f80d by Yuri Chornoivan.
Committed on 13/11/2023 at 17:00.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +3-3doc/index.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/883f068eabace140d44e3bd9b68d415fc1c4f80d

diff --git a/doc/index.docbook b/doc/index.docbook
index 2d2f2b79..1ade05f5 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -771,7 +771,7 @@ configuration file option.
 in pretend mode.
 
 This driver works by setting up a custom 
xsession
-session type. This type of session should work by default with the ssdm login
+session type. This type of session should work by default with the sddm login
 manager (where it appears as a Custom session), but other login
 managers (such as LightDM and
 gdm) may require additional files installed to
@@ -5055,7 +5055,7 @@ create it if necessary. Add the line:
 On some distributions, it may be necessary to perform the same
 steps with the .xsession file, also in the home directory.
 This is especially true when using graphical login managers such as
-ssdm, gdm, or xdm.
+sddm, gdm, or xdm.
 
 
 
@@ -5068,7 +5068,7 @@ text terminals and the following six are graphical 
displays.
 
 If when you start your computer you are presented to the graphical display
 manager instead, you can use the new  environment, even if it is not 
listed
-as an option. Most display managers, including ssdm, have an option to use
+as an option. Most display managers, including sddm, have an option to use
 a Custom Session when you login. With this option, your session 
settings are
 loaded from the .xsession file in your home directory. If
 you have already modified this file as described above, this option should load

Re: Repository location of English documentation files

[Yuri Chornoivan]

неділя, 29 жовтня 2023 р. 16:50:43 EET Oliver Kellogg написано:
> Correction:
> The confusing bullet is the one before,
> - the *English documentation* files in the directory l10n-kf5/documentation/
> *EXAMPLE* (you need this file to generate the translated DocBook file)
> 
> The directory l10n-kf5/documentation/  is the one that I cannot find.

Again, it will be created after the first run of update_xml.

Best regards,
Yuri

> 
> -Oliver
> 
> On Sun, Oct 29, 2023 at 3:29 PM Oliver Kellogg 
> 
> wrote:
> > > In the Kate's repo
> > > 
> > > https://invent.kde.org/utilities/kate/-/tree/master/doc?ref_type=heads
> > 
> > Ah! I don't know how I overlooked that, thanks.
> > At any rate, I find the following bullet from *POT and PO Files Used for
> > Documentation* confusing:
> > 
> > For the package "EXAMPLE" you will find
> > [...]
> > - the translated documentation (in DocBook format) in the directory
> > l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> > 
> > It is not true that the translated documentation (in DocBook format) can
> > be found in the directory
> > 
> >     l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> > 
> > (there is no such directory).
> > 
> > Cheers
> > 
> > Oliver
> > 
> > On Sun, Oct 29, 2023 at 1:32 PM Yuri Chornoivan  wrote:
> >> неділя, 29 жовтня 2023 р. 14:07:01 EET Oliver Kellogg написано:
> >> > Hi Yuri,
> >> > 
> >> > That's also good to know :)
> >> > However, I was looking for the repo location for the DocBook files of
> >> 
> >> all
> >> 
> >> > the KDE apps.
> >> 
> >> There is no such thing (and never has been afaik). They are extracted by
> >> update_xml.sh from the git repos when needed.
> >> 
> >> > Giving more context from *POT and PO Files Used for Documentation* :
> >> > 
> >> > You can find the English DocBook documentation in subdirectories of the
> >> > source code for the corresponding package. The POT files and the
> >> 
> >> translated
> >> 
> >> > PO files and DocBook files for all languages are located in the KDE
> >> 
> >> package
> >> 
> >> > named *kde-l10n*. For the package "EXAMPLE" you will find
> >> > 
> >> >-
> >> >
> >> >the POT files in the directory
> >> 
> >> l10n-kf5/templates/docmessages/*EXAMPLE*/
> >> 
> >> >-
> >> >
> >> >the translated PO files in the directory l10n-kdf5/*$LANGUAGE*
> >> >/docmessages/*EXAMPLE*/
> >> >-
> >> >
> >> >the *English documentation* files in the directory
> >> >l10n-kf5/documentation/*EXAMPLE* (you need this file to generate the
> >> >translated DocBook file)
> >> >-
> >> >
> >> >the translated documentation (in DocBook format) in the directory
> >> >l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> >> > 
> >> > Taking Kate as an example, for the POT files I see
> >> > svn+ssh://
> >> 
> >> s...@svn.kde.org/home/kde/trunk/l10n-kf6/templates/docmessages/kate
> >> 
> >> > and now my question is, where are the Kate DocBook files.
> >> 
> >> In the Kate's repo
> >> 
> >> https://invent.kde.org/utilities/kate/-/tree/master/doc?ref_type=heads
> >> 
> >> Best regards,
> >> Yuri
> >> 
> >> > Greetings
> >> > 
> >> > Oliver
> >> > 
> >> > On Sun, Oct 29, 2023 at 11:24 AM Yuri Chornoivan 
> >> 
> >> wrote:
> >> > > неділя, 29 жовтня 2023 р. 12:09:15 EET Oliver Kellogg написано:
> >> > > > Hello kde-doc-english,
> >> > > > 
> >> > > > https://l10n.kde.org/docs/translation-howto/doc-files.html
> >> 
> >> contains:
> >> > > >- the *English documentation* files in the directory
> >> > > >l10n-kf5/documentation/*EXAMPLE* (you need this file to generate
> >> 
> >> the
> >> 
> >> > > >translated DocBook file)
> >> > > > 
> >> > > > However, looking at https://websvn.kde.org/trunk/l10n-kf5/ there
> >> 
> >> is no
> >> 
> >> > > > subdirectory documentation.
> >> > > > 
> >> > > > Could you please clarify where is the origin of the DocBook files
> >> 
> >> in the
> >> 
> >> > > > repository?
> >> > > > 
> >> > > > Many thanks,
> >> > > > 
> >> > > > Oliver
> >> > > > 
> >> > > > https://eo.l10n.kde.org/teamo.php
> >> > > 
> >> > > Hi,
> >> > > 
> >> > > It is here:
> >> > > 
> >> > > https://websvn.kde.org/trunk/www/areas/l10n/docs/translation-howto/
> >> > > 
> >> > > Hope this helps.
> >> > > 
> >> > > Best regards,
> >> > > Yuri

Re: Repository location of English documentation files

[Yuri Chornoivan]

неділя, 29 жовтня 2023 р. 16:29:45 EET Oliver Kellogg написано:
> > In the Kate's repo
> > 
> > https://invent.kde.org/utilities/kate/-/tree/master/doc?ref_type=heads
> 
> Ah! I don't know how I overlooked that, thanks.
> At any rate, I find the following bullet from *POT and PO Files Used for
> Documentation* confusing:
> 
> For the package "EXAMPLE" you will find
> [...]
> - the translated documentation (in DocBook format) in the directory
> l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> 
> It is not true that the translated documentation (in DocBook format) can be
> found in the directory
> l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> (there is no such directory).

Just because the above-mentioned instructions were not followed.

Once the update_xml.sh script has been executed you will have this directory.

Best regards,
Yuri

> 
> Cheers
> 
> Oliver
> 
> On Sun, Oct 29, 2023 at 1:32 PM Yuri Chornoivan  wrote:
> > неділя, 29 жовтня 2023 р. 14:07:01 EET Oliver Kellogg написано:
> > > Hi Yuri,
> > > 
> > > That's also good to know :)
> > > However, I was looking for the repo location for the DocBook files of
> > > all
> > > the KDE apps.
> > 
> > There is no such thing (and never has been afaik). They are extracted by
> > update_xml.sh from the git repos when needed.
> > 
> > > Giving more context from *POT and PO Files Used for Documentation* :
> > > 
> > > You can find the English DocBook documentation in subdirectories of the
> > > source code for the corresponding package. The POT files and the
> > 
> > translated
> > 
> > > PO files and DocBook files for all languages are located in the KDE
> > 
> > package
> > 
> > > named *kde-l10n*. For the package "EXAMPLE" you will find
> > > 
> > >-
> > >
> > >the POT files in the directory
> > 
> > l10n-kf5/templates/docmessages/*EXAMPLE*/
> > 
> > >-
> > >
> > >the translated PO files in the directory l10n-kdf5/*$LANGUAGE*
> > >/docmessages/*EXAMPLE*/
> > >-
> > >
> > >the *English documentation* files in the directory
> > >l10n-kf5/documentation/*EXAMPLE* (you need this file to generate the
> > >translated DocBook file)
> > >-
> > >
> > >the translated documentation (in DocBook format) in the directory
> > >l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> > > 
> > > Taking Kate as an example, for the POT files I see
> > > svn+ssh://
> > 
> > s...@svn.kde.org/home/kde/trunk/l10n-kf6/templates/docmessages/kate
> > 
> > > and now my question is, where are the Kate DocBook files.
> > 
> > In the Kate's repo
> > 
> > https://invent.kde.org/utilities/kate/-/tree/master/doc?ref_type=heads
> > 
> > Best regards,
> > Yuri
> > 
> > > Greetings
> > > 
> > > Oliver
> > > 
> > > On Sun, Oct 29, 2023 at 11:24 AM Yuri Chornoivan 
> > 
> > wrote:
> > > > неділя, 29 жовтня 2023 р. 12:09:15 EET Oliver Kellogg написано:
> > > > > Hello kde-doc-english,
> > > > > 
> > > > > https://l10n.kde.org/docs/translation-howto/doc-files.html contains:
> > > > >- the *English documentation* files in the directory
> > > > >l10n-kf5/documentation/*EXAMPLE* (you need this file to generate
> > 
> > the
> > 
> > > > >translated DocBook file)
> > > > > 
> > > > > However, looking at https://websvn.kde.org/trunk/l10n-kf5/ there is
> > 
> > no
> > 
> > > > > subdirectory documentation.
> > > > > 
> > > > > Could you please clarify where is the origin of the DocBook files in
> > 
> > the
> > 
> > > > > repository?
> > > > > 
> > > > > Many thanks,
> > > > > 
> > > > > Oliver
> > > > > 
> > > > > https://eo.l10n.kde.org/teamo.php
> > > > 
> > > > Hi,
> > > > 
> > > > It is here:
> > > > 
> > > > https://websvn.kde.org/trunk/www/areas/l10n/docs/translation-howto/
> > > > 
> > > > Hope this helps.
> > > > 
> > > > Best regards,
> > > > Yuri

Re: Repository location of English documentation files

[Yuri Chornoivan]

неділя, 29 жовтня 2023 р. 14:07:01 EET Oliver Kellogg написано:
> Hi Yuri,
> 
> That's also good to know :)
> However, I was looking for the repo location for the DocBook files of all
> the KDE apps.

There is no such thing (and never has been afaik). They are extracted by 
update_xml.sh from the git repos when needed.

> Giving more context from *POT and PO Files Used for Documentation* :
> 
> You can find the English DocBook documentation in subdirectories of the
> source code for the corresponding package. The POT files and the translated
> PO files and DocBook files for all languages are located in the KDE package
> named *kde-l10n*. For the package "EXAMPLE" you will find
> 
>-
> 
>the POT files in the directory l10n-kf5/templates/docmessages/*EXAMPLE*/
>-
> 
>the translated PO files in the directory l10n-kdf5/*$LANGUAGE*
>/docmessages/*EXAMPLE*/
>-
> 
>the *English documentation* files in the directory
>l10n-kf5/documentation/*EXAMPLE* (you need this file to generate the
>translated DocBook file)
>-
> 
>the translated documentation (in DocBook format) in the directory
>l10n-kf5/*$LANGUAGE*/docs/*EXAMPLE*/
> 
> 
> Taking Kate as an example, for the POT files I see
> svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf6/templates/docmessages/kate
> and now my question is, where are the Kate DocBook files.

In the Kate's repo

https://invent.kde.org/utilities/kate/-/tree/master/doc?ref_type=heads

Best regards,
Yuri

> 
> Greetings
> 
> Oliver
> 
> On Sun, Oct 29, 2023 at 11:24 AM Yuri Chornoivan  wrote:
> > неділя, 29 жовтня 2023 р. 12:09:15 EET Oliver Kellogg написано:
> > > Hello kde-doc-english,
> > > 
> > > https://l10n.kde.org/docs/translation-howto/doc-files.html contains:
> > >- the *English documentation* files in the directory
> > >l10n-kf5/documentation/*EXAMPLE* (you need this file to generate the
> > >translated DocBook file)
> > > 
> > > However, looking at https://websvn.kde.org/trunk/l10n-kf5/ there is no
> > > subdirectory documentation.
> > > 
> > > Could you please clarify where is the origin of the DocBook files in the
> > > repository?
> > > 
> > > Many thanks,
> > > 
> > > Oliver
> > > 
> > > https://eo.l10n.kde.org/teamo.php
> > 
> > Hi,
> > 
> > It is here:
> > 
> > https://websvn.kde.org/trunk/www/areas/l10n/docs/translation-howto/
> > 
> > Hope this helps.
> > 
> > Best regards,
> > Yuri

Re: Repository location of English documentation files

[Yuri Chornoivan]

неділя, 29 жовтня 2023 р. 12:09:15 EET Oliver Kellogg написано:
> Hello kde-doc-english,
> 
> https://l10n.kde.org/docs/translation-howto/doc-files.html contains:
> 
> 
>- the *English documentation* files in the directory
>l10n-kf5/documentation/*EXAMPLE* (you need this file to generate the
>translated DocBook file)
> 
> 
> However, looking at https://websvn.kde.org/trunk/l10n-kf5/ there is no
> subdirectory documentation.
> 
> Could you please clarify where is the origin of the DocBook files in the
> repository?
> 
> Many thanks,
> 
> Oliver
> 
> https://eo.l10n.kde.org/teamo.php

Hi,

It is here:

https://websvn.kde.org/trunk/www/areas/l10n/docs/translation-howto/

Hope this helps.

Best regards,
Yuri

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 28293212a79dc7dce48e559c0ff856c10970fa8f by Yuri Chornoivan.
Committed on 24/10/2023 at 14:49.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/ekos-align.docbook

https://invent.kde.org/education/kstars/-/commit/28293212a79dc7dce48e559c0ff856c10970fa8f

diff --git a/doc/ekos-align.docbook b/doc/ekos-align.docbook
index f5ab0bf60..c96274eac 100644
--- a/doc/ekos-align.docbook
+++ b/doc/ekos-align.docbook
@@ -177,7 +177,7 @@
 
   This applies if you are using the (recommended) Internal 
Solver Solving Method.
   
-  You can choose an Options Profile on the 
StellarSolver Options tab. Profiles are simply collections 
of parameters to configure the performance of the star-extraction and 
plate-solving system inside of StellarSolver.  The 
1-Default profile is the recommended one to start with. 
There are a few other possible profiles such as Large Scale 
Solving, Small Scall Solving, and 
Single Thread Solving.
+  You can choose an Options Profile on the 
StellarSolver Options tab. Profiles are simply collections 
of parameters to configure the performance of the star-extraction and 
plate-solving system inside of StellarSolver.  The 
1-Default profile is the recommended one to start with. 
There are a few other possible profiles such as Large Scale 
Solving, Small Scale Solving, and 
Single Thread Solving.
 In the Align Options Profile Editor 
tab you can view and edit profiles. There are many parameters, most of which 
you need not change to solve issues. There are 3 types of parameters.
  
 

[education/kstars] doc: Fix minor typo, enhance formatting for translations

[Yuri Chornoivan]

Git commit 7baa2b4f58e5b8dbd2df1a6f088e3cd04fda2370 by Yuri Chornoivan.
Committed on 22/10/2023 at 08:11.
Pushed by yurchor into branch 'master'.

Fix minor typo, enhance formatting for translations

M  +2-2doc/config.docbook
M  +3-4doc/fitsviewer.docbook

https://invent.kde.org/education/kstars/-/commit/7baa2b4f58e5b8dbd2df1a6f088e3cd04fda2370

diff --git a/doc/config.docbook b/doc/config.docbook
index e31a2393e..5568d3eb8 100644
--- a/doc/config.docbook
+++ b/doc/config.docbook
@@ -1499,7 +1499,7 @@ debug issues with . There are checkboxes for 
saving images
 in logging directories that might help debug issues. Of course, saving images
 can take up disk space and should be used judiciously.
 
-  The images that can be saved are
+  The images that can be saved are
   
 
 all focus images,
@@ -1513,7 +1513,7 @@ can take up disk space and should be used judiciously.
 
 align images where the plate-solving failed.
 
-  
+  
 The images are all saved in folders parallel to the main
   logging directory. They are in folders named guide, autofocus, align, and 
align/failed.
 
diff --git a/doc/fitsviewer.docbook b/doc/fitsviewer.docbook
index f4f37bbe0..c7ae421ef 100644
--- a/doc/fitsviewer.docbook
+++ b/doc/fitsviewer.docbook
@@ -166,7 +166,7 @@ To open a FITS file, select the 
File
 
 Enable Stretching: On the very left of this 
display is a button that enables or disables stretching.
 Shadow Value: The value below which pixels are 
displayed as black can be manually entered (scale is 0 to 1.0, even for integer 
pixel values).
-Midtones Value: The midtones value which 
controls the brightness of the iamge can be manually entered (scale is 0 to 
1.0, even for integer pixel values).
+Midtones Value: The midtones value which 
controls the brightness of the image can be manually entered (scale is 0 to 
1.0, even for integer pixel values).
 Highlights Value: The value above which pixels 
are displayed as white can be manually entered (scale is 0 to 1.0, even for 
integer pixel values).
 Show Histogram: A button that displays or 
hides the image histogram is to the right of the highlights number 
box.
 Auto Stretch: A button (magic wand icon) that 
will automatically create a pleasing stretch is found on the right. It is 
disabled if the stretch is already at the automatically computed 
value.
@@ -300,7 +300,7 @@ To open a FITS file, select the 
File
 Use SkyMap Position: There is a button just 
below the Use Position checkbox that fills in RA and DEC boxes with the current 
center of the SkyMap display.
 Profile: The Profile menu selects which 
StellarSolver preset, among those used in the Ekos Align module, should be used 
for plate solving. This is further discussed below.
 Solution: The Solution section will display 
the number of stars found and the time taken to solve. The solution values for 
RA, DEC, Scale and Angle are displayed in those boxes above.
-Image: For any image where stars were 
detected, if the Mark Stars button is activated above the image display,
+Image: For any image where stars were 
detected, if the Mark Stars button is activated above the image display, then 
the detected stars are circled in red.
 
 
 FITS Viewer Mark Stars Button
@@ -314,8 +314,7 @@ To open a FITS file, select the 
File
 
 
 
-then the detected stars are circled in red.
-
+
 
 
   Using this tool the user can try and debug solving issues as 
follows.

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit a56cdba513c6881d3e92a03c7565c055069510f7 by Yuri Chornoivan.
Committed on 21/10/2023 at 07:51.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/fitsviewer.docbook

https://invent.kde.org/education/kstars/-/commit/a56cdba513c6881d3e92a03c7565c055069510f7

diff --git a/doc/fitsviewer.docbook b/doc/fitsviewer.docbook
index a26640bd4..bb2157115 100644
--- a/doc/fitsviewer.docbook
+++ b/doc/fitsviewer.docbook
@@ -162,7 +162,7 @@ To open a FITS file, select the 
File
 
   
 
-Near the bottom of the window are controls for stretching the image and 
displaying its histogram. They are discribed below from left to right.
+Near the bottom of the window are controls for stretching the image and 
displaying its histogram. They are described below from left to right.
 
 Enable Stretching: On the very left of this 
display is a button that enables or disables stretching.
 Shadow Value: The value below which pixels are 
displayed as black can be manually entered (scale is 0 to 1.0, even for integer 
pixel values).
@@ -295,7 +295,7 @@ To open a FITS file, select the 
File
 
 
 Solve Button. Pressing this button starts 
plate solving. When the system is plate solving, the button becomes an abort 
button.
-Scale: Checking the Use Scale checkbox 
constains the solver to use approximately the pixel or image scale given. The 
scale is entered in the box and the units for the scale can be chosen from 
image width in degrees, image width in arc-minutes, and arc-seconds per pixel. 
When a solve successfully completes, it replaces the value in the box with 
solution's scale.
+Scale: Checking the Use Scale checkbox 
contains the solver to use approximately the pixel or image scale given. The 
scale is entered in the box and the units for the scale can be chosen from 
image width in degrees, image width in arc-minutes, and arc-seconds per pixel. 
When a solve successfully completes, it replaces the value in the box with 
solution's scale.
 Position: Checking the Use Position checkbox 
constains the solver to search near the RA and DEC coordinates given. The 
extent of the search is given by the user in the Radius box in degrees. Note 
that RA is input in hours-minutes-seconds, e.g. 13h, and DEC is input in 
degrees-minutes-seconds, e.g. 85. When a solve successfully completes, it 
replaces the value in the RA and DEC boxes with solution's coordinates. In 
addition it fills in the Angle field with the solutions angle value in 
degrees.
 Use SkyMap Position: There is a button just 
below the Use Position checkbox that fills in RA and DEC boxes with the current 
center of the SkyMap display.
 Profile: The Profile menu selects which 
StellarSolver preset, among those used in the Ekos Align module, should be used 
for plate solving. This is further discussed below.

[education/kstars] doc: Fix XML

[Yuri Chornoivan]

Git commit 4c56f06d87ce0ef07a27cb006198ae61ba2711e1 by Yuri Chornoivan.
Committed on 21/10/2023 at 07:44.
Pushed by yurchor into branch 'master'.

Fix XML

M  +2-2doc/fitsviewer.docbook

https://invent.kde.org/education/kstars/-/commit/4c56f06d87ce0ef07a27cb006198ae61ba2711e1

diff --git a/doc/fitsviewer.docbook b/doc/fitsviewer.docbook
index f3b52babb..a26640bd4 100644
--- a/doc/fitsviewer.docbook
+++ b/doc/fitsviewer.docbook
@@ -150,7 +150,7 @@ To open a FITS file, select the 
File
 
 
 
-Stretching Controls. 
+Stretching Controls
 
   The Stretch Controls in the FITS Viewer
   
@@ -178,7 +178,7 @@ To open a FITS file, select the 
File
   The histogram, if it is enabled, may be zoomed by using the 
mouse's scroll wheel, and panned by dragging with the mouse. A cursor in the 
histogram shows the position of the pixel in the image under the mouse.
   
 
-Status Bar
+Status Bar
 
   The Status Display in the FITS Viewer
   

Re: question on docbook header formatting

[Yuri Chornoivan]

Hi,

четвер, 19 жовтня 2023 р. 00:05:15 EEST Jack написано:
> Running khelpcenter, looking at the TOC produced by meinproc5, within a
> chapter, if a sect1 has several sect2s within it, there is no extra
> space between the sect1 title and the first sect2 title, nor between
> the sequential sect2 titles.  There IS a space between the last sect2
> and the following sect1.  However, there is no space between two
> sequential sect1 titles, if the first does not contain any sect2.  This
> looks odd to me, but I suppose it has been that way for a long time.
> Am I the only one who thinks this, and is there any reasonable way to
> change it?

This can be tweaked through kde-docs.css and kde-default.css (common/en in 
kdoctools repo [1]).

Yes, I think the presentation can be better than now.

Best regards,
Yuri

[1] https://invent.kde.org/frameworks/kdoctools

> Simply adding space before any sect1 title would add
> unwanted space between a chapter title and the first sect1 title, so I
> know it's not trivial to do.
> 
> Any thoughts or suggestions?
> 
> Jack

[education/gcompris] docs/docbook: Fix XML

[Yuri Chornoivan]

Git commit f2f234c367536feb085d626f77b5a491aceb1f0e by Yuri Chornoivan.
Committed on 12/10/2023 at 07:35.
Pushed by yurchor into branch 'master'.

Fix XML

M  +0-1docs/docbook/index.docbook

https://invent.kde.org/education/gcompris/-/commit/f2f234c367536feb085d626f77b5a491aceb1f0e

diff --git a/docs/docbook/index.docbook b/docs/docbook/index.docbook
index 7937a5db92..411cd9c71e 100644
--- a/docs/docbook/index.docbook
+++ b/docs/docbook/index.docbook
@@ -306,7 +306,6 @@ or make it show real car images instead of filled 
rectangles (traffic).
 Specify the activity when starting GCompris.
 
 
-
 --start-level level
 Specify the level on which to start the activity specified by --launch 
option when starting GCompris. Ignored if no --launch option, or if level 
specified is invalid.
 

Re: KRename and Yakuake documentation

[Yuri Chornoivan]

вівторок, 10 жовтня 2023 р. 19:33:10 EEST John Kizer написано:
> Hi - I was thinking that contributing to documentation might be a way I
> could help, since I have minimal programming skills but have done a decent
> amount of writing / guide-building for tech tools over my corporate career.
> 
> I saw on this page
> (https://techbase.kde.org/Projects/Documentation/KDE_(health_table)) that
> KRename and Yakuake are both marked as red, and those are both programs I
> use regularly - is anyone else currently working on those, or would those
> be good ones to start with?
> 
> Thanks,
> 
> John Kizer

Hi,

As you know, KRename development is stale for awhile it has the "Help" button, 
which leads nowhere, so it can be the good place to start as it is stable. On 
the other hand, it has a good context help, which can help user or be a 
starter for the documentation.

Yakuake has a bunch of developers and changes from time to time so it might be 
important to have the modern version to document it. There is no "Help" button 
or menu item for "Help" so it might need some programming changes to implement 
the "Help" function. On the other hand, the docs can be borrowed from Konsole.

It seems that nobody is working on both project now. So it is up to you to 
decide what is the best for our documentation project.

Just my 2 cents.

Best regards,
Yuri

[utilities/kate] doc/katepart: Fix minor typo

[Yuri Chornoivan]

Git commit c89bea06e282bc7598b9cd5a99e25dee8d082fcc by Yuri Chornoivan.
Committed on 17/09/2023 at 17:29.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/katepart/development.docbook

https://invent.kde.org/utilities/kate/-/commit/c89bea06e282bc7598b9cd5a99e25dee8d082fcc

diff --git a/doc/katepart/development.docbook b/doc/katepart/development.docbook
index 2b5123163..e22758342 100644
--- a/doc/katepart/development.docbook
+++ b/doc/katepart/development.docbook
@@ -1228,7 +1228,7 @@ keep the matched string for the next context.
 
 You can validate every  file by using the command
 validatehl.sh mySyntax.xml.
-The file validatehl.sh use 
language.xsd which are both available in https://commits.kde.org/syntax-highlighting?path=data/schema;>Syntax
+The file validatehl.sh uses 
language.xsd which are both available in https://commits.kde.org/syntax-highlighting?path=data/schema;>Syntax
 Highlighting repository.
 
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 047e68676f04d53ac813a3e25c40f9e965dcc761 by Yuri Chornoivan.
Committed on 17/08/2023 at 07:55.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/config.docbook

https://invent.kde.org/education/kstars/-/commit/047e68676f04d53ac813a3e25c40f9e965dcc761

diff --git a/doc/config.docbook b/doc/config.docbook
index 9ecb8e4b2..9e5b759bf 100644
--- a/doc/config.docbook
+++ b/doc/config.docbook
@@ -1201,7 +1201,7 @@ Start KStars once you have images in the imageOverlays 
directory. If you then go
   To prepare your images for display, you need to plate-solve the images (one 
time only). To do this, find an image in the table, click on its filename, and 
then click Solve below the table. The Solve button's label 
should switch to Cancel during the solve, and then when 
completed successfully, the solved parameters are displayed in the table and 
the status is changed to "OK".  A successful plate-solve's information is 
stored in the user database so that solving doesn't need to be repeated. The 
solved image should from then on appear in its proper position in the SkyMap. 
You can plate-solve multiple images in a single operation by clicking on the 
first image's filename, then shift clicking on another filename. All the image 
files between the filenames should be selected. Then clicking Solve will 
attempt to solve them all. However, KStars will not attempt to plate-solve 
images whose status is "OK", it will skip those images. (If you wish to 
re-plate-solve images with status "OK", then manually change their status to 
"Unprocessed" and click "Solve").  It is possible that if you select several 
images, a few of them will not be successfully solved.
 
 
-Plate solving these images can sometimes be difficult. That is because at this 
point the system has no information as to the scale or position to look, and 
thus it is a blind solve. To improve your chance for success, you can enter an 
approxiate RA/DEC center sky position into the RA and DEC columns for the row 
you are trying to solve. You can also add an image scale, in 
arcseconds-per-pixel. You can add a default scale to the right of the Solve 
button in the box labelled Default a-s/px so that all 
solving attempts use this scale by default. You can also add a scale directly 
into the table-row-column, which would override the default. You can choose 
which StellarSolver profile the solver uses (these profiles can be edited in 
Ekos' align tab). Finally, you can adjust the solver's 
Timeout in seconds.
+Plate solving these images can sometimes be difficult. That is because at this 
point the system has no information as to the scale or position to look, and 
thus it is a blind solve. To improve your chance for success, you can enter an 
approximate RA/DEC center sky position into the RA and DEC columns for the row 
you are trying to solve. You can also add an image scale, in 
arcseconds-per-pixel. You can add a default scale to the right of the Solve 
button in the box labeled Default a-s/px so that all 
solving attempts use this scale by default. You can also add a scale directly 
into the table-row-column, which would override the default. You can choose 
which StellarSolver profile the solver uses (these profiles can be edited in 
Ekos' align tab). Finally, you can adjust the solver's 
Timeout in seconds.
 
 
 If you have problematic images that won't solve, you can still display them by 
manually entering the values (that the solver didn't find) into the table. They 
are the RA, DEC, arcsecond-per-pixel, orientation angle, and east-to-the-right 
(or West-to-the-right) settings. Once you have done that, you can then change 
the status to "OK" and KStars will save these values to the user database as if 
they had been automatically solved.

[education/kstars] doc: Fix XML

[Yuri Chornoivan]

Git commit fb7dd987b163c9b434b097e4f7238afabd530785 by Yuri Chornoivan.
Committed on 11/08/2023 at 07:45.
Pushed by yurchor into branch 'master'.

Fix XML

M  +1-1doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/fb7dd987b163c9b434b097e4f7238afabd530785

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 545d9088c..2954b8a9b 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -2043,7 +2043,7 @@
 
   
  AF Overscan: The Focus module 
can manage Backlash itself by over scanning
-outward motions by the value in the AF Overscan 
field. For example, if AF Overscan
+outward motions by the value in the AF Overscan 
field. For example, if AF Overscan
 is set to 40 then whenever Focus moves the focuser outwards, it does 
this as a 2-step process. Firstly it moves the
 focuser 40 ticks past where it wants to end up; secondly it moves back 
in by 40 ticks.
 

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit e17f98a6305f8086d3255bcad72606e3c931759c by Yuri Chornoivan.
Committed on 02/08/2023 at 20:38.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +2-2doc/ekos-guide.docbook

https://invent.kde.org/education/kstars/-/commit/e17f98a6305f8086d3255bcad72606e3c931759c

diff --git a/doc/ekos-guide.docbook b/doc/ekos-guide.docbook
index f0e40ec3b..ee07a7ade 100644
--- a/doc/ekos-guide.docbook
+++ b/doc/ekos-guide.docbook
@@ -230,7 +230,7 @@
 
 
 
-Algorithm. we strongly recommend you use the most 
up-to-date algorith: SEP MultiStar. Pretty much the only reason not to would be 
if you can't get your SEP star-detection to perform adequately.
+Algorithm. We strongly recommend you use the most 
up-to-date algorithm: SEP MultiStar. Pretty much the only reason not to would 
be if you can't get your SEP star-detection to perform adequately.
 
 
 
@@ -260,7 +260,7 @@
 To enable automatic dithering between frames, make sure to check 
the Dither checkbox. By default, Ekos should dither ( 
move) the guiding box by up to 3 pixels after every N frames captured in Ekos Capture Module. The motion duration and 
direction are randomized. Since the guiding performance can oscillate 
immediately after dithering, you can set the appropriate 
Settle duration to wait after dither is complete before 
resuming the capture process. In rare cases where the dithering process can get 
stuck in an endless loop, set the appropriate Timeout to 
abort the process. But even if dithering fails, you can select whether this 
failure should terminate the autoguiding process or not. Toggle Abort 
Autoguide on failure to select the desired behavior.
 
 
-  Dithing does not result in a long wander from the original target 
position. Ekos keeps track of the original and current target positions, and 
moves the target back towards the original target should the position have 
drifted too far.
+  Dithering does not result in a long wander from the original target 
position. Ekos keeps track of the original and current target positions, and 
moves the target back towards the original target should the position have 
drifted too far.
 
 
 One-pulse dithering is an interesting quicker option which sends a 
pulse to dither, but does not verify that the dither reached its desired 
location. It is possible that the dithering for any given dither isn't as much 
as desired, but the overall effect should be good.

[graphics/kphotoalbum] doc: Fix minor typo, enhance formatting

[Yuri Chornoivan]

Git commit f9cce72a65f7e2051e497a003a91723cadcc2f7b by Yuri Chornoivan.
Committed on 31/07/2023 at 07:55.
Pushed by yurchor into branch 'master'.

Fix minor typo, enhance formatting

M  +4-4doc/setting-properties.docbook
M  +4-3doc/viewer.docbook

https://invent.kde.org/graphics/kphotoalbum/-/commit/f9cce72a65f7e2051e497a003a91723cadcc2f7b

diff --git a/doc/setting-properties.docbook b/doc/setting-properties.docbook
index ebe9c848..6579bb67 100644
--- a/doc/setting-properties.docbook
+++ b/doc/setting-properties.docbook
@@ -224,15 +224,15 @@ window layout.
 Annotating while viewing images
 For a few decades we tagged our images as described above, but in 
the summer of 2023, it started being possible to tag images while viewing them.
 This facility doesn't support all the features described above, but it 
offers a much faster workflow to tagging images.
-Missing features when annotating images from the viewer, which you 
need to come to this dialog for are:
+Missing features when annotating images from the viewer, which you 
need to come to this dialog for are:
 
 Annotating multiple images at a time
 Tagging individual parts of an image (this face is 
...)
-Setting up tag groups (ie. specifying that Las Vegas is in 
USA, so you will see images tagged Las Vegas when watching images from 
USA)
+Setting up tag groups ( specifying that Las Vegas is 
in USA, so you will see images tagged Las Vegas when watching images from 
USA)
 Setting image dates
 
-
-See the seciton on annotating 
from the viewer
+
+See the section on annotating 
from the viewer
 
 
 
diff --git a/doc/viewer.docbook b/doc/viewer.docbook
index 696cd9e1..ea7e35e8 100644
--- a/doc/viewer.docbook
+++ b/doc/viewer.docbook
@@ -133,15 +133,16 @@ Over the years a few different attempts have been made at 
integrating tagging in
 attempt was by making it possible to tag directly by typing part of a category 
item. In addition category items could be assigned to function keys on the 
keyboard.
 The code for all of this have now been modernized to make the work flow much 
more intuitive and discover-able.
 
-There are three modes to annotating images in the viewer:
+There are three modes to annotating images in the viewer:
 
 Locked - This is the default mode 
when starting the viewer - in here no annotating or tokenizing will happen. 
This ensure you do not accidentally annotates images when viewing 
them.
 Assign Tokens - This allows you to 
set tokens on images, by simply pressing a key from A-Z on the 
keyboard.
 Assign Tags - This allows you to 
assign macros to a keyboard key. As an example, L could 
mean set the item Las Vegas in the 
Location category. In addition to that, it also allows you 
to set any tag on an image.
 
-
+
 The modes are selected from the context menu as can be seen in .
-
+
+
 The two modes are described in details below.
 
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 81129ae4f7773d05c351a863971613bcbc870d6e by Yuri Chornoivan.
Committed on 28/07/2023 at 14:15.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +3-3doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/81129ae4f7773d05c351a863971613bcbc870d6e

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index be73cc2c2..72c8cabc7 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -1702,7 +1702,7 @@
   
   
   If the Adapt Focus box is checked, the AF Runs 
are updated for Adaptive Focus. See the
-  Adaptive Focus section for 
more details on the theory of Adaptive Focus.The first AF run
+  Adaptive Focus section for 
more details on the theory of Adaptive Focus. The first AF run
   (in this example AF Run 1 on Lum) is the basis for the Adaptations. 
So the temperature and altitude of AF Run 1 on Lum is used as
   the basis for all the other AF Runs and the data is adapted back to 
what the AF solution would have been, had it been run at the
   temperature and altitude of AF Run 1 on Lum.
@@ -1726,7 +1726,7 @@
 
   
   
-  If you hover the mouse over an AF Run it will show a tooltip 
Adaptive Focus Explainer. In the example, the mouse if hovering over
+  If you hover the mouse over an AF Run it will show a tooltip 
Adaptive Focus Explainer. In the example, the mouse is hovering over
   AF Run 1 on Red. The 1st row of the Explainer shows the measured 
Autofocus result for that run (36683), adaptations for Temperature (0.0C) and 
Altitude (0.2 degrees Alt).
   The 2nd row of the Explainer shows the Adaptations: 206 total, 0 
temperature, 205.9 altitude. The 3rd row shows the Adapted Position
   of 36889.
@@ -2190,7 +2190,7 @@
 starting at 36580, before moving to 36571 and then to 36562 as shown on 
the Focus Tab in the Current Position widget and in
 the message box.
 
- The Adaptive Focus concept has been build into the Build Offsets tool.
+ The Adaptive Focus concept has been built into the Build Offsets tool.
   
 
 

[education/kwordquiz] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 9fd9a720e0ba5a2f3a058bbabc520a1a4ab39b9d by Yuri Chornoivan.
Committed on 28/07/2023 at 08:52.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/index.docbook

https://invent.kde.org/education/kwordquiz/-/commit/9fd9a720e0ba5a2f3a058bbabc520a1a4ab39b9d

diff --git a/doc/index.docbook b/doc/index.docbook
index 4e22c6b..b7b80a3 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -271,7 +271,7 @@ In the example below the user gave an incorrect answer to 
the previous question.
   
 
 
-Your choices are shown on the middle of the scren. Select the one you think is 
correct. Use Check to see if the answer is correct. If 
you have activated the automatic mode in 
Settings your selection is checked 
immediately.
+Your choices are shown on the middle of the screen. Select the one you think 
is correct. Use Check to see if the answer is correct. 
If you have activated the automatic mode in 
Settings your selection is checked 
immediately.
 
 
 Select Repeat Errors to repeat the cards you have 
counted as incorrect.

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit c35758934ffa65368f452b6f0dbc43861e55984f by Yuri Chornoivan.
Committed on 28/07/2023 at 07:41.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/c35758934ffa65368f452b6f0dbc43861e55984f

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index f8bfb320b..be73cc2c2 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -1749,7 +1749,7 @@
 consistent as possible during this time, e.g. there is enough time 
before dawn, the moon won't affect focusing of some images
 more than others, the target won't drop below your horizon during 
the process, etc.
 
- Connfigure the utility for # Focus Runs (5 is a 
good start), reference filter (e.g. Lum) and Adapt Focus
+ Configure the utility for # Focus Runs (5 is a 
good start), reference filter (e.g. Lum) and Adapt Focus
 setting. Run the utility to completion.
 
  Review the results. For each filter review each 
AF run looking for outliers. For each outlier decide what to

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 8c97889c0accfc3a3e2b3aa1997448206c900c39 by Yuri Chornoivan.
Committed on 06/07/2023 at 12:10.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/8c97889c0accfc3a3e2b3aa1997448206c900c39

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index f2b7bb710..6932da769 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -2027,14 +2027,14 @@
   
  Temperature. All the components of the imaging system will be 
affected by changes in ambient temperature.
 The most obvious will be the telescope tube. Typically this will 
expand as temperature increases and contract as
-it descreases. This will affect the focus point. But also the optical 
path the light from the imaged target takes
+it decreases. This will affect the focus point. But also the optical 
path the light from the imaged target takes
 through the atmosphere and through the imaging components of the 
telescope will be affected by temperature and
 therefore will affect the focus point.
 
  It is necessary to have a reliable source of temperature 
information available to the focus module in order
 to use the temperature feature of AF.
 
- Where the temperature source is located is, of course, upto the 
user. Given the changes in temperature effect
+ Where the temperature source is located is, of course, up to 
the user. Given the changes in temperature effect
 many components it is not obvious where the best location would be. 
Some experimentation may be required to get
 the best results but as a guide, the source should be near the imaging 
train but not near any heating effect of
 electrical equipment that would say, heat the temperature source but 
not the optical train. Consistency of location

D30134: Fix for translation-howto check-gui XMLSyntax Check step 3

[Yuri Chornoivan]

yurchor closed this revision.
yurchor added a comment.


  Committed. Thanks.

REVISION DETAIL
  https://phabricator.kde.org/D30134

To: okellogg, yurchor, aacid
Cc: kde-doc-english, gennad, fbampaloukas, skadinna

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 3525b0b4e10937840f5933437a7a8f46e0c39cb9 by Yuri Chornoivan.
Committed on 05/07/2023 at 15:00.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +9-9doc/ekos-scheduler.docbook

https://invent.kde.org/education/kstars/-/commit/3525b0b4e10937840f5933437a7a8f46e0c39cb9

diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook
index 7a67d5772..aba7d853c 100644
--- a/doc/ekos-scheduler.docbook
+++ b/doc/ekos-scheduler.docbook
@@ -21,13 +21,13 @@
 
   Introduction
 
-  The Ekos Scheduler is an important component of you imaging 
workflow. It connects to INDI, starts and stops all the other Ekos modules, 
schedules jobs according to their constraints and priorities, monitors those 
jobs as they execute, and then safely brings down the system when jobs are 
done, or before dawn. Whether you are running multi-day imaging sessions for 
multiple targets, or simplying trying to image a single target for a few hours, 
it is advisable to have the Scheduler control your imaging sessions.
+  The Ekos Scheduler is an important component of your imaging 
workflow. It connects to INDI, starts and stops all the other Ekos modules, 
schedules jobs according to their constraints and priorities, monitors those 
jobs as they execute, and then safely brings down the system when jobs are 
done, or before dawn. Whether you are running multi-day imaging sessions for 
multiple targets, or simply trying to image a single target for a few hours, it 
is advisable to have the Scheduler control your imaging sessions.
 
 
 
 Scheduler Table
 
-  The heart of the Scheduler is a table displaying the list of 
Scheduler jobs the user wants to run. Associated with each jobs are attributes 
(mostly described in the settings section below). The attributes describe the 
name of the job, where the telescope should be pointed when imaging that job, a 
description of what types of images should be captured, constraints about when 
the jobs should run (e.g. altitude, twilight, moon, landscape blockages, etc), 
things that need to be done before and after the job is run, and strategies for 
dealing with errors.
+  The heart of the Scheduler is a table displaying the list of 
Scheduler jobs the user wants to run. Associated with each jobs are attributes 
(mostly described in the settings section below). The attributes describe the 
name of the job, where the telescope should be pointed when imaging that job, a 
description of what types of images should be captured, constraints about when 
the jobs should run ( altitude, twilight, moon, landscape blockages, 
), things that need to be done before and after the job is run, and 
strategies for dealing with errors.
 
 
   You can add, delete, modify or change the order of rows in the 
Scheduler table. 
@@ -64,16 +64,16 @@
   The Scheduler table (above) lists jobs in order of priority, with 
higher jobs (on lower-numbered rows) having higher priority than jobs further 
down the list (with higher-numbered rows). 
 
 
-  The Scheduler regularly plans (an re-plans) which jobs should be 
run, and when. It can start executing a given job, and then later preempt that 
job for a new one. It can become idle if no jobs can be run (e.g. in daylight), 
and sleep until such a time that it becomes active again. Its aim is to keep 
the equipment as busy as possible, while respecting the scheduler-table's 
priorities. Here's how it works.
+  The Scheduler regularly plans (and re-plans) which jobs should be 
run, and when. It can start executing a given job, and then later preempt that 
job for a new one. It can become idle if no jobs can be run ( in daylight), 
and sleep until such a time that it becomes active again. Its aim is to keep 
the equipment as busy as possible, while respecting the scheduler-table's 
priorities. Here's how it works.
 
 
-  When the scheduler starts (or when it replans, which it does every 
second while active), it looks through the entire list of jobs, starting at the 
highest priority job, and working its way down to the lowest priority one if 
necessary. When it finds a job that can run, it starts that job, possibly 
preempting the currently running job. A jobs can run if it's constraints are 
met, e.g. the target is not blocked by the local terrain, it meets the minimum 
altitude constraint, it has not already completed all the desired imaging, ...
+  When the scheduler starts (or when it replans, which it does every 
second while active), it looks through the entire list of jobs, starting at the 
highest priority job, and working its way down to the lowest priority one if 
necessary. When it finds a job that can run, it starts that job, possibly 
preempting the currently running job. A jobs can run if its constraints are 
met,  the target is not blocked by the local terrain

D30134: Fix for translation-howto check-gui XMLSyntax Check step 3

[Yuri Chornoivan]

yurchor added a comment.


  In D30134#684291 , @okellogg wrote:
  
  > I'm not sure whose turn it is, will you commit? Shall I?
  
  
  Please do if you have access.

REVISION DETAIL
  https://phabricator.kde.org/D30134

To: okellogg, yurchor, aacid
Cc: kde-doc-english, gennad, fbampaloukas, skadinna

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit ccbee55ba492ae5ed09958258553272f6f373207 by Yuri Chornoivan.
Committed on 04/07/2023 at 03:46.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-scheduler.docbook

https://invent.kde.org/education/kstars/-/commit/ccbee55ba492ae5ed09958258553272f6f373207

diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook
index d07135377..7a67d5772 100644
--- a/doc/ekos-scheduler.docbook
+++ b/doc/ekos-scheduler.docbook
@@ -58,13 +58,13 @@
 
 
 
-
+
 Scheduling Algorithm
 
   The Scheduler table (above) lists jobs in order of priority, with 
higher jobs (on lower-numbered rows) having higher priority than jobs further 
down the list (with higher-numbered rows). 
 
 
-  The Scheduler regularly plans (an re-plans) which jobs should be 
run, and when. It can start executing a given job, and then later preempt that 
job for a new one. It can become idle if no jobs can be run (e.g. in daylight), 
and sleep until such a time that it becomes active again. Its aim is to keep 
the equipment as busy as possible, while respecting the scheduler-table's 
priorties. Here's how it works.
+  The Scheduler regularly plans (an re-plans) which jobs should be 
run, and when. It can start executing a given job, and then later preempt that 
job for a new one. It can become idle if no jobs can be run (e.g. in daylight), 
and sleep until such a time that it becomes active again. Its aim is to keep 
the equipment as busy as possible, while respecting the scheduler-table's 
priorities. Here's how it works.
 
 
   When the scheduler starts (or when it replans, which it does every 
second while active), it looks through the entire list of jobs, starting at the 
highest priority job, and working its way down to the lowest priority one if 
necessary. When it finds a job that can run, it starts that job, possibly 
preempting the currently running job. A jobs can run if it's constraints are 
met, e.g. the target is not blocked by the local terrain, it meets the minimum 
altitude constraint, it has not already completed all the desired imaging, ...

[education/kstars] doc: Fix XML

[Yuri Chornoivan]

Git commit 179c4d0cf359191ffef04707837bb8ba70c6a399 by Yuri Chornoivan.
Committed on 04/07/2023 at 03:40.
Pushed by yurchor into branch 'master'.

Fix XML

M  +1-1doc/ekos-scheduler.docbook

https://invent.kde.org/education/kstars/-/commit/179c4d0cf359191ffef04707837bb8ba70c6a399

diff --git a/doc/ekos-scheduler.docbook b/doc/ekos-scheduler.docbook
index e567f5b3c..d07135377 100644
--- a/doc/ekos-scheduler.docbook
+++ b/doc/ekos-scheduler.docbook
@@ -69,13 +69,13 @@
 
   When the scheduler starts (or when it replans, which it does every 
second while active), it looks through the entire list of jobs, starting at the 
highest priority job, and working its way down to the lowest priority one if 
necessary. When it finds a job that can run, it starts that job, possibly 
preempting the currently running job. A jobs can run if it's constraints are 
met, e.g. the target is not blocked by the local terrain, it meets the minimum 
altitude constraint, it has not already completed all the desired imaging, ...
 
-
 
   The algorithm shows its projected next start times and stop times for 
all job in the Scheduler table. It also shows its estimate of times jobs will 
run during the next 48 hours in the log panel at the bottom of the window. See 
the screenshot of the scheduler window at the top of this section.
 
 
   The scheduling algorithm described in the above paragraph is known 
as the Greedy Scheduling algorithm. It is the recommended one to use. In 
previous versions of Ekos, there was another "Classic scheduling algorithm" 
which is currently being phased out. That scheme could not preempt running 
jobs, and thus did not makes as much use of the equipment as the Greedy 
Algorithm. 
 
+
 
 Scheduler Files (.esq)
 

D30134: Fix for translation-howto check-gui XMLSyntax Check step 3

[Yuri Chornoivan]

yurchor accepted this revision.
yurchor added a comment.
This revision is now accepted and ready to land.


  Thanks

REVISION DETAIL
  https://phabricator.kde.org/D30134

To: okellogg, yurchor, aacid
Cc: kde-doc-english, gennad, fbampaloukas, skadinna

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 94c81b8120f4912f087936b0f488183b072edafa by Yuri Chornoivan.
Committed on 30/06/2023 at 19:14.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/94c81b8120f4912f087936b0f488183b072edafa

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 84b82195e3..f2b7bb7106 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -1029,7 +1029,7 @@
 applicable here as well.
 
  The difference between CFZ Shuffle and Fixed Steps is that near 
the center of the sweep (which
-should be around the Critical Focus Zone (CFZ) the algorithm takes 
steps of half the specified size.
+should be around the Critical Focus Zone (CFZ)) the algorithm takes 
steps of half the specified size.
   
 
 
@@ -1255,7 +1255,7 @@
 have how many ticks moved the drawtube the distance you measured. From 
this you can calculate the distance in microns a single
 tick moves the drawtube.
  Other types of telescope will have other ways to adjust the focal 
plane, for example, by moving the primary or
-secondary mirrors. You will need to either get the Step Size from the 
documentation for your equipment of work out how to
+secondary mirrors. You will need to either get the Step Size from the 
documentation for your equipment or work out how to
 measure it in a way that are consistent with that described above.
   
 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 99158d07034dcf2aa00d8311eed15696140c21e6 by Yuri Chornoivan.
Committed on 22/06/2023 at 12:52.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +7-7doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/99158d07034dcf2aa00d8311eed15696140c21e6

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 153ec23bc..50d31cee0 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -832,7 +832,7 @@
   
 
   
- # Stars: This ia an 
experimental feature that
+ # Stars: This is an 
experimental feature that
 calculates the number of stars in the image and uses this number as 
the focus measure.
 The idea is that as you move nearer focus so more stars become 
detectable.
 
@@ -900,7 +900,7 @@
   1 Pass focus algorithm and Curve Fits of Hyperbola and Parabola. If this 
option is checked then at the end
   of the sweep of datapoints, Ekos fits a curve and measures the R². It 
then applies Peirce's Criterion
   based on Gould's methodology for outlier identification. See https://en.wikipedia.org/wiki/Peirce%27s_criterion;>Peirce's 
Criterian for details incl
+  url="https://en.wikipedia.org/wiki/Peirce%27s_criterion;>Peirce's 
Criterion for details incl
   Peirce's original paper and Gould's paper which are both referenced in 
the notes. If Peirce's Criterion
   detects 1 or more outliers then another curve fit is attempted with the 
outliers removed. Again the R²
   is calculated and compared with the original curve fit R². If the R² is 
better, then the latest run is used,
@@ -1196,7 +1196,7 @@
   
 
   
- Tolerance: This is used by Classic and 
Wavwfront algorithms and is a scaling factor
+ Tolerance: This is used by Classic and 
Wavefront algorithms and is a scaling factor
 between 0 and 1.
  For the Classic algorithm, Goldman and Megdal suggest 1/3.
  For the Wavefront algorithm, some have suggested 1/3 or even 
1/10.
@@ -1402,11 +1402,11 @@
 
Use Offsets: It is possible 
to use filter offsets to adjust focus when swapping
   between filters, without running Autofocus. This requires some setup 
work ahead of time but has the advantage of
-  reduciung the number of Autofocus runs and therefore reducing the 
time spent autofocusing.
+  reducing the number of Autofocus runs and therefore reducing the 
time spent autofocusing.
 
In order to use this feature it is necessary to work out the 
relative focus position between all filters that you
   wish to use this functionality for. For example, if Lum and Red have 
the same focus position (they are parfocal) but Green
-  focuses 300 ticks further out than Lum (or Red) then setup Offsets 
for Lum, Red and Grren as 0, 0, 300 as shown above. If a
+  focuses 300 ticks further out than Lum (or Red) then setup Offsets 
for Lum, Red and Green as 0, 0, 300 as shown above. If a
   sequence is created to take 10 subframes of Lum, then 10 Red, then 
10 Green, then at the start, since Lum has
   Auto Focus checked, an Autofocus will be run on 
Lum and the 10 subs taken. Capture will then switch
   filters to Red. Since Red has Auto Focus 
unchecked no Autofocus will happen and Ekos will look to the
@@ -1774,7 +1774,7 @@
  The units of the y-axis depend on the selected focus Measure. For 
example, for HFR, the y-axis will either be in Pixels
 or Arc seconds depending on how Display Units is 
set.
 
- If Refine Curve Fit is selected, Focus will 
check for and potentially exclude outlying datapoonts.
+ If Refine Curve Fit is selected, Focus will 
check for and potentially exclude outlying datapoints.
 In this case datapoints 1, 5 and 7 were excluded.
 
  Under the V-Curve a number of parameters are displayed:
@@ -1825,7 +1825,7 @@
  Here is a V-Curve when Measure is set to Fourier:
  V-Curve 
Fourier
   
-  Focus V-Curve 
Fourierj
+  Focus V-Curve 
Fourier
 
  When Framing, the graph format changes to that of a "time series" 
where horizontal axis denotes the frame number.
 This is to aid you in the framing process as you can see how Measure, in 
this case HFR, changes between frames. 

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit a32a545422bd1eac0b4f6ca655d1f2363f85e807 by Yuri Chornoivan.
Committed on 20/06/2023 at 12:47.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +9-9doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/-/commit/a32a545422bd1eac0b4f6ca655d1f2363f85e807

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
old mode 100755
new mode 100644
index 51253ca27..153ec23bc
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -53,7 +53,7 @@
 is recommended to allow Ekos to select a set of stars. 
 
  Ekos supports 4 different focus algorithms: Linear 1 Pass, Linear,
-Iterative, Polynominal. Linear 1 Pass is the recommended algorithm. 
+Iterative, Polynomial. Linear 1 Pass is the recommended algorithm. 
 
 
   
@@ -560,7 +560,7 @@
   
Correcting image tilt: especially large sensors are 
very sensitive to
  incorrect distance and tilting of the sensor. In such 
cases, the image
- shows aberration, expecially in the image corners. If all 
corners show the same
+ shows aberration, especially in the image corners. If all 
corners show the same
  effect, the distance needs to be corrected. If the 
aberrations in the corners
differ, this is typically the result of a tilted 
sensor.
   
@@ -863,7 +863,7 @@
 
 
PSF: If Measure is set 
to FWHM, then the PSF
-  widget can be selected for use in fitting a surface to the star. At 
pressent just Gaussian is
+  widget can be selected for use in fitting a surface to the star. At 
present just Gaussian is
   supported.
 
 
@@ -1248,7 +1248,7 @@
  Step Size: This must be input by the user (as 
it cannot be calculated by Ekos). It relates how far
 1 tick moves the focal plane in microns. 
  For a refractor this is how far the drawtube moves when the focuser 
is moved by 1 tick. You might be able to get this
-value from the spefication of your focuser (how many ticks for a complete 
revolution of your focuser) and the thread pitch of
+value from the specification of your focuser (how many ticks for a 
complete revolution of your focuser) and the thread pitch of
 your telescope drawtube along with any gearing involved.
  Alternatively, you can measure how far the drawtube moves from end 
to end (be careful not to force the drawtube) with
 a set of calipers or a ruler. By subtracting the furthest "in" position 
(in ticks) from the furthest "out" position (in ticks) you
@@ -1405,12 +1405,12 @@
   reduciung the number of Autofocus runs and therefore reducing the 
time spent autofocusing.
 
In order to use this feature it is necessary to work out the 
relative focus position between all filters that you
-  wish to use this functionality for. For examplke, if Lum and Red 
have the same focus position (they are parfocal) but Green
+  wish to use this functionality for. For example, if Lum and Red have 
the same focus position (they are parfocal) but Green
   focuses 300 ticks further out than Lum (or Red) then setup Offsets 
for Lum, Red and Grren as 0, 0, 300 as shown above. If a
   sequence is created to take 10 subframes of Lum, then 10 Red, then 
10 Green, then at the start, since Lum has
   Auto Focus checked, an Autofocus will be run on 
Lum and the 10 subs taken. Capture will then switch
   filters to Red. Since Red has Auto Focus 
unchecked no Autofocus will happen and Ekos will look to the
-  Offsets between Red and Lum. In this case 0 - 0 = 0. So the focuser 
will not be moved and Copture will take 10 subs of Red.
+  Offsets between Red and Lum. In this case 0 - 0 = 0. So the focuser 
will not be moved and Capture will take 10 subs of Red.
   Then Capture will swap from Red to Green. Again, Green has 
Auto Focus unchecked no Autofocus will happen
   and Ekos will look to the Offsets between Green and Red. In this 
case 300 - 0 = 300. So Focus will adjust the focus position
   by +300 (move the focuser out by 300 ticks). Capture will then take 
the 10 Green subs.
@@ -1772,7 +1772,7 @@
 is selected then error bars are indicated on each datapoint that 
correspond to the standard deviation in measured value.
 
  The units of the y-axis depend on the selected focus Measure. For 
example, for HFR, the y-axis will either be in Pixels
-or Arc Sseconds depending on how Display Units is 
set.
+or Arc seconds depending on how Display Units is 
set.
 
  If Refine Curve Fit is selected, Focus will 
check for and potentially exclude outlying datapoonts.
 In this case datapoints 1, 5 and 7 were excluded.
@@ -2067,7 +2067,7 @@
 
  Currently Ekos supports a simple linear relationship between 
temperature, or altitude, and ticks. In the future,
 if t

[docs.kde.org] [Bug 468982] Enable Arabic

[Yuri Chornoivan]

https://bugs.kde.org/show_bug.cgi?id=468982

Yuri Chornoivan  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
  Latest Commit||https://invent.kde.org/webs
   ||ites/docs-kde-org/commit/9f
   ||d9ac37ca1e9f4c0a607030da207
   ||455afb73dff
 Resolution|--- |FIXED

--- Comment #2 from Yuri Chornoivan  ---
Git commit 9fd9ac37ca1e9f4c0a607030da207455afb73dff by Yuri Chornoivan.
Committed on 26/04/2023 at 09:23.
Pushed by ltoscano into branch 'master'.

Add Arabic to the docs languages (thanks to Zayed Al-Saidi)

M  +1-0languages

https://invent.kde.org/websites/docs-kde-org/commit/9fd9ac37ca1e9f4c0a607030da207455afb73dff

-- 
You are receiving this mail because:
You are the assignee for the bug.

[multimedia/haruna] doc: Fix minor typo

[Yuri Chornoivan]

Git commit b584f54a226a9edba42cded700064710e4b00a13 by Yuri Chornoivan.
Committed on 09/04/2023 at 13:38.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/index.docbook

https://invent.kde.org/multimedia/haruna/commit/b584f54a226a9edba42cded700064710e4b00a13

diff --git a/doc/index.docbook b/doc/index.docbook
index 4a5417e..973db07 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -91,7 +91,7 @@
 Playback
 
 Seek steps
-How much to seek when triggering the coresponding 
action. Seek mode is exact https://mpv.io/manual/stable/#command-interface-seek-target-[flags];>
+How much to seek when triggering the corresponding 
action. Seek mode is exact https://mpv.io/manual/stable/#command-interface-seek-target-[flags];>
 
https://mpv.io/manual/stable/#command-interface-seek-target-[flags;].
 
 

Re: Kate missing "Run current document"

[Yuri Chornoivan]

неділя, 5 лютого 2023 р. 13:59:25 EET Krzysztof Żelechowski написано:
> 
> Run current document (saves the current document and executes it as a script
> in a terminal window)

Hi,

Done.

https://invent.kde.org/utilities/kate/commit/
5d49d8433bef53e0b87726025400c9b78d7574e5

Thanks for the notice.

Best regards,
Yuri

[utilities/kate] doc/kate: Add 'Run Current Document' option to the docs. Idea by Krzysztof Żelechowski

[Yuri Chornoivan]

Git commit 5d49d8433bef53e0b87726025400c9b78d7574e5 by Yuri Chornoivan.
Committed on 05/02/2023 at 16:52.
Pushed by yurchor into branch 'master'.

Add 'Run Current Document' option to the docs. Idea by Krzysztof Żelechowski

M  +11   -0doc/kate/plugins.docbook

https://invent.kde.org/utilities/kate/commit/5d49d8433bef53e0b87726025400c9b78d7574e5

diff --git a/doc/kate/plugins.docbook b/doc/kate/plugins.docbook
index 177d5237f..618e9ad37 100644
--- a/doc/kate/plugins.docbook
+++ b/doc/kate/plugins.docbook
@@ -4018,6 +4018,17 @@ sync with the current document.  See
 
 
 
+
+
+Tools
+Run Current Document
+
+Run the current document in . Only the local documents can be 
run.
+ will show a warning before running document because this action can be
+a serious security threat.
+
+
+
 
 
 Tools

[plasma/plasma-workspace] doc/kcontrol/lookandfeel: Fix minor typo

[Yuri Chornoivan]

Git commit d9ee26f96c6598004f760e85473682bacd485bf5 by Yuri Chornoivan.
Committed on 31/01/2023 at 11:43.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/kcontrol/lookandfeel/index.docbook

https://invent.kde.org/plasma/plasma-workspace/commit/d9ee26f96c6598004f760e85473682bacd485bf5

diff --git a/doc/kcontrol/lookandfeel/index.docbook 
b/doc/kcontrol/lookandfeel/index.docbook
index bd99d95c01..1d2d6deb59 100644
--- a/doc/kcontrol/lookandfeel/index.docbook
+++ b/doc/kcontrol/lookandfeel/index.docbook
@@ -134,7 +134,7 @@
 
 
 
-  To remove an installed Global Theme, click on the button with the thrash 
icon that appears when hovering over a theme thumbnail. Note that you can only 
remove Global Themes that you have downloaded yourself.
+  To remove an installed Global Theme, click on the button with the trash icon 
that appears when hovering over a theme thumbnail. Note that you can only 
remove Global Themes that you have downloaded yourself.
 
 
 

[plasma/kwin] doc/kwinscreenedges: Fix minor typo

[Yuri Chornoivan]

Git commit 57a2f96e9ed8d84072e7a36bc6e91b2d4a6d2f77 by Yuri Chornoivan.
Committed on 31/01/2023 at 06:40.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/kwinscreenedges/index.docbook

https://invent.kde.org/plasma/kwin/commit/57a2f96e9ed8d84072e7a36bc6e91b2d4a6d2f77

diff --git a/doc/kwinscreenedges/index.docbook 
b/doc/kwinscreenedges/index.docbook
index 01e716ab2f..9476745b2c 100644
--- a/doc/kwinscreenedges/index.docbook
+++ b/doc/kwinscreenedges/index.docbook
@@ -56,7 +56,7 @@ In the Movement tab of the 
Window Behavior
 
 
-Disable the option Remain active when windows are 
fullscreen option to supress triggering screen edge actions when an 
application is running in fullscreen.
+Disable the option Remain active when windows are 
fullscreen option to suppress triggering screen edge actions when an 
application is running in fullscreen.
 
 Using the Switch desktop on edge item, configure if 
you want to switch 
 to another desktop when pushing the mouse cursor to an edge of the screen, 
 only when 

[utilities/kate] doc/katepart: Restore the missing line in docs

[Yuri Chornoivan]

Git commit 198341b8c601f116de252049e6242a40f55971b0 by Yuri Chornoivan.
Committed on 31/01/2023 at 06:34.
Pushed by yurchor into branch 'master'.

Restore the missing line in docs

M  +1-0doc/katepart/menus.docbook

https://invent.kde.org/utilities/kate/commit/198341b8c601f116de252049e6242a40f55971b0

diff --git a/doc/katepart/menus.docbook b/doc/katepart/menus.docbook
index bb24b68cb..12e818bce 100644
--- a/doc/katepart/menus.docbook
+++ b/doc/katepart/menus.docbook
@@ -968,6 +968,7 @@ Click on the right pointing triangle to expand all toplevel 
regions.
 +
 
+View
 Code Folding
 Unfold Toplevel Nodes
 

[plasma/plasma-workspace] doc/kcontrol: Fix minor typos

[Yuri Chornoivan]

Git commit f5385d57f3a9269244d6760378b59166aac8240a by Yuri Chornoivan.
Committed on 31/01/2023 at 05:46.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/kcontrol/colors/index.docbook
M  +1-1doc/kcontrol/cursortheme/index.docbook
M  +2-2doc/kcontrol/lookandfeel/index.docbook

https://invent.kde.org/plasma/plasma-workspace/commit/f5385d57f3a9269244d6760378b59166aac8240a

diff --git a/doc/kcontrol/colors/index.docbook 
b/doc/kcontrol/colors/index.docbook
index edb431ddf7..8ce7aa69a0 100644
--- a/doc/kcontrol/colors/index.docbook
+++ b/doc/kcontrol/colors/index.docbook
@@ -78,7 +78,7 @@
   From current wallpaper:
 This will automatically extract a matching color from your desktop 
background image.
   
-  Curstom:
+  Custom:
 Here you can choose from a set of predefined colors or pick a custom 
color.
   
 
diff --git a/doc/kcontrol/cursortheme/index.docbook 
b/doc/kcontrol/cursortheme/index.docbook
index 6a8861b554..3cebe63189 100644
--- a/doc/kcontrol/cursortheme/index.docbook
+++ b/doc/kcontrol/cursortheme/index.docbook
@@ -107,7 +107,7 @@ This module allows you to
 
 Sometimes it is reassuring to know that your computer didn't just
 ignore your command, and something is happening behind the scenes. In
-this dialog Configure Launch Fedback..., 
+this dialog Configure Launch Feedback..., 
 you can configure visible feedback to help you know if you
 really hit that icon or not.
 
diff --git a/doc/kcontrol/lookandfeel/index.docbook 
b/doc/kcontrol/lookandfeel/index.docbook
index 71e60b2eb4..bd99d95c01 100644
--- a/doc/kcontrol/lookandfeel/index.docbook
+++ b/doc/kcontrol/lookandfeel/index.docbook
@@ -49,7 +49,7 @@
   Plasma Style: Appearance of panels and 
widgets
   Window Decoration: Window borders and titlebar 
buttons
   Icons: Icons used throughout  and 
applications
-  Cusors: Mouse pointers
+  Cursors: Mouse pointers
   Task Switcher: Overlay for switching between open windows, 
typically invoked with the keyboard shortcut Alt+Tab
   Splash Screen: Loading screen shown during  
startup
   Login Screen: Screen with a user selector and password 
prompt shown when the computer is started up
@@ -58,7 +58,7 @@
 
 
 
-  By appling a Global Theme, you can change all of the above together. You can 
also apply only some components of a Global Theme, such as a color scheme or a 
window decoration. You can choose which components to change either when 
applying a Global Theme, or apply individual components by using the other 
System Settings subsections.
+  By applying a Global Theme, you can change all of the above together. You 
can also apply only some components of a Global Theme, such as a color scheme 
or a window decoration. You can choose which components to change either when 
applying a Global Theme, or apply individual components by using the other 
System Settings subsections.
 
 
 

[office/kmymoney/5.1] doc: Fix minor typo: to to -> to

[Yuri Chornoivan]

Git commit 213246ef6b722af59c0720eb5fa5f131dba12f36 by Yuri Chornoivan.
Committed on 26/01/2023 at 09:37.
Pushed by yurchor into branch '5.1'.

Fix minor typo: to to -> to

M  +1-1doc/details-reports.docbook

https://invent.kde.org/office/kmymoney/commit/213246ef6b722af59c0720eb5fa5f131dba12f36

diff --git a/doc/details-reports.docbook b/doc/details-reports.docbook
index e99c76c63..c4d1afd11 100644
--- a/doc/details-reports.docbook
+++ b/doc/details-reports.docbook
@@ -337,7 +337,7 @@
 
   The configuration dialog for reports which display amounts over time may
   include budget related settings.  These are only enabled if you do have one 
or
-  more budgets defined, and include a drop-down to to select one of those
+  more budgets defined, and include a drop-down to select one of those
   budgets.  If one is selected, the report will show the budgeted amount per
   time period rather that the actual amounts from transaction in that period.
   In addition, some reports may also give you the option of displaying both the

[office/kmymoney/5.1] doc: Fix minor issues in docs (take 2)

[Yuri Chornoivan]

Git commit 55b4b3792209db8f78bc156bc0b7718bf529d8a6 by Yuri Chornoivan.
Committed on 26/01/2023 at 08:45.
Pushed by yurchor into branch '5.1'.

Fix minor issues in docs (take 2)

M  +5-5doc/details-reports.docbook

https://invent.kde.org/office/kmymoney/commit/55b4b3792209db8f78bc156bc0b7718bf529d8a6

diff --git a/doc/details-reports.docbook b/doc/details-reports.docbook
index 42caf8d97..e99c76c63 100644
--- a/doc/details-reports.docbook
+++ b/doc/details-reports.docbook
@@ -669,18 +669,18 @@
 Date range
 
   Use this section to specify the date range of transactions to be included in
-  the report.  The Range dropdown includes a large number
-  of predefined ranges, but you cans select User defined and
+  the report.  The Range drop-down includes a large number
+  of predefined ranges, but you can select User defined and
   manually set From and To.  The
-  Ticks dropdown specifies the placement of tick marks on
-  the horizontal (time)  axis of the chart.  
+  Ticks drop-down specifies the placement of tick marks on
+  the horizontal (time) axis of the chart.
 
 
 
 Data range
 
   This specifies the tick marks and divisions on the vertical axis of the 
chart.
-  It is generally best to leave the Range dropdown set to
+  It is generally best to leave the Range drop-down set to
   Automatic.
 
 

[office/kmymoney/5.1] doc: Fix minor issues in docs

[Yuri Chornoivan]

Git commit d9b2a4bff6c7281fea07ed0a5f2e75fc1eda7288 by Yuri Chornoivan.
Committed on 26/01/2023 at 08:34.
Pushed by yurchor into branch '5.1'.

Fix minor issues in docs

M  +4-2doc/details-reports.docbook

https://invent.kde.org/office/kmymoney/commit/d9b2a4bff6c7281fea07ed0a5f2e75fc1eda7288

diff --git a/doc/details-reports.docbook b/doc/details-reports.docbook
index 1b1940a79..42caf8d97 100644
--- a/doc/details-reports.docbook
+++ b/doc/details-reports.docbook
@@ -107,12 +107,14 @@
   your account register for a specific period of time.  The transactions
   included in a report can be grouped together according to your liking by
   choosing the appropriate report, such as:
+
   
 By Account
 By Category
 By Month or Week
 By Payee
   
+
   You can also choose the time period for the report.
 
 
@@ -642,7 +644,7 @@
 
 
   
-Logarithmic vertial axis: Only enabled when relevant - use a 
logarithmic
+Logarithmic vertical axis: Only enabled when relevant - use a 
logarithmic
 instead of linear scale for the vertical axis.
   
 
@@ -668,7 +670,7 @@
 
   Use this section to specify the date range of transactions to be included in
   the report.  The Range dropdown includes a large number
-  of predfined ranges, but you cans select User defined and
+  of predefined ranges, but you cans select User defined and
   manually set From and To.  The
   Ticks dropdown specifies the placement of tick marks on
   the horizontal (time)  axis of the chart.  

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit 8294000cc8d6ae94e3c5ce2f4b9d01000581c194 by Yuri Chornoivan.
Committed on 16/01/2023 at 11:28.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +5-5doc/ekos-align.docbook

https://invent.kde.org/education/kstars/commit/8294000cc8d6ae94e3c5ce2f4b9d01000581c194

diff --git a/doc/ekos-align.docbook b/doc/ekos-align.docbook
index 94a506d0d..f2941416b 100644
--- a/doc/ekos-align.docbook
+++ b/doc/ekos-align.docbook
@@ -554,7 +554,7 @@
 However, unless you have a top of the line mount, then 
you'd probably want to use an autoguider to keep the same star locked in the 
same position over time. Despite all of this, if the axis of the mount is not 
properly aligned with the celestial pole, then even a mechanically-perfect 
mount would lose tracking with time. Tracking errors are proportional to the 
magnitude of the misalignment. It is therefore very important for long exposure 
imaging to get the mount polar aligned to reduce any residual errors as it 
spans across the sky.
 
 
-Before starting the process, point the mount as close as 
possible to the celestial pole with the counterweights down. If you are living 
in the Northern Hemisphere, point it as close as possible to Polaris. If 
Polaris is not visible (e.g. blocked by trees or  buildings) you may point 
elsewhere, preferably near the Meridian. Make sure there is at 30-60 degrees of 
sky viewable in an arc East or West of the Meridian from the position you 
choose. Select the direction of free sky, the number of degrees for each of two 
slews, the mount slew speed, and whether the mount will be slewing 
automatically (recommended) or manually.
+Before starting the process, point the mount as close as 
possible to the celestial pole with the counterweights down. If you are living 
in the Northern Hemisphere, point it as close as possible to Polaris. If 
Polaris is not visible ( blocked by trees or  buildings) you may point 
elsewhere, preferably near the Meridian. Make sure there is at least 30-60 
degrees of sky viewable in an arc East or West of the Meridian from the 
position you choose. Select the direction of free sky, the number of degrees 
for each of two slews, the mount slew speed, and whether the mount will be 
slewing automatically (recommended) or manually.
 
 
 The tool works by capturing and solving three images. 
After capturing each, the mount rotates by the fixed amount you entered and 
another image is captured and solved. If you chose manual, you will need to 
slew the mount by roughly the angle chosen.
@@ -593,13 +593,13 @@
 
 
 
-  If your error is low enough (e.g. less than an arc-minute) 
then you don't need to make any adjustments. Simply press stop and you're done.
+  If your error is low enough ( less than an arc-minute) 
then you don't need to make any adjustments. Simply press stop and you're done.
 
 
-  If you will be making corrections to your mount's axis, you 
should select the adjustment approach (we're using Plate Solve in this 
example), and how often the system should recapture images to re-measure the 
polar alignment error. The refresh interval should be frequent, but it doesn't 
make sense to make it faster that your CPU can capture and plate-solve the 
images. We're using 2s in this example. Then press the Refresh button to begin 
the correction process.
+  If you will be making corrections to your mount's axis, you 
should select the adjustment approach (we're using Plate Solve in this 
example), and how often the system should recapture images to re-measure the 
polar alignment error. The refresh interval should be frequent, but it doesn't 
make sense to make it faster that your CPU can capture and plate-solve the 
images. We're using 2s in this example. Then press the 
Refresh button to begin the correction process.
 
 
-  The system will capture images, and re-estimate the polar 
alignment error after each image. You can try to reduce the error by adjusting 
the Alititude and Azimuth correction knobs on your mount. The image below shows 
the screen after the altitude error has been almost zeroed. See the difference 
between the  Measured Error row, which shows the 
originally measured error after the original 3 captures, and the  
Updated Error row which shows the current error estimate.
+  The system will capture images, and re-estimate the polar 
alignment error after each image. You can try to reduce the error by adjusting 
the Altitude and Azimuth correction knobs on your mount. The image below shows 
the screen after the altitude error has been almost zeroed. See the difference 
between the  Measured Error row, which shows

[education/kstars] doc: Fix minor typo

[Yuri Chornoivan]

Git commit 04c226d02cbc98ef05bdbe0b90c9d74a94e68514 by Yuri Chornoivan.
Committed on 10/01/2023 at 19:42.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/ekos-analyze.docbook

https://invent.kde.org/education/kstars/commit/04c226d02cbc98ef05bdbe0b90c9d74a94e68514

diff --git a/doc/ekos-analyze.docbook b/doc/ekos-analyze.docbook
index 5746ea150..008870e9b 100644
--- a/doc/ekos-analyze.docbook
+++ b/doc/ekos-analyze.docbook
@@ -33,7 +33,7 @@
 
 Timeline
 
-Timeline shows the major Ekos processes, and when they were active. 
For instance, the Capture line shows when images were 
taken (wither green for RGB or color-coded by the the filter) and when imaging 
was aborted (shown as red sections). Clicking on a capture section gives 
information about that image, and double clicking on one brings up the image 
taken then in a fitsviewer, if it is available.
+Timeline shows the major Ekos processes, and when they were active. 
For instance, the Capture line shows when images were 
taken (wither green for RGB or color-coded by the filter) and when imaging was 
aborted (shown as red sections). Clicking on a capture section gives 
information about that image, and double clicking on one brings up the image 
taken then in a fitsviewer, if it is available.
 
 
 

Re: Technical Writing / Updating Documentation

[Yuri Chornoivan]

вівторок, 27 грудня 2022 р. 22:02:26 EET Aaron L написано:
> Gotcha.
> 
> I updated my computer running KDE today and noticed under the help
> application the following:
> 
> Multiple instances of Discover (showing it multiple times)

Do not have Discover installed, but it looks like a bug ub khelpcenter or 
packaging bug. It cannot be fixed by documenting.

> 
> I noticed the Virtual Desktop instructions was missing instructions as
> well.

Yes. The module help should be updated.

Best regards,
Yuri

> 
> Let me know if this is just on my end or if you see this as well.
> 
> On Sun, Dec 25, 2022 at 1:39 AM Yuri Chornoivan  wrote:
> > неділя, 25 грудня 2022 р. 01:45:33 EET Aaron L написано:
> > > Hi Yury,
> > > 
> > > I will take a look. Other documentation first.
> > > 
> > > Why is KDE using two different methods?
> > 
> > That's the multilevel question.
> > 
> > 1. Some hope that the new (other) publication system allows them to
> > rewrite
> > old docs in the modern way.
> > 
> > 2. Some believe that DocBook is hard to understand and frighten potential
> > writers.
> > 
> > 3. Some think that Sphinx is easier to adopt and manage.
> > 
> > Best regards,
> > Yuri
> > 
> > > Best,
> > > Aaron
> > > 
> > > On Sat, Dec 24, 2022 at 8:32 AM Yuri Chornoivan  wrote:
> > > > > Hi Yury,
> > > > > 
> > > > > I will read the following to get an understanding of the processes:
> > > > > 
> > > > > 
> > > > > https://community.kde.org/Get_Involved/documentation
> > > > > 
> > > > > 
> > > > > https://l10n.kde.org/docs/doc-primer/
> > > > > 
> > > > > Let me know if there's anything else I should be reading.
> > > > > 
> > > > > Best,
> > > > > Aaron
> > > > 
> > > > Yes, that's the main part. But now we have three major projects
> > > > (Krita,
> > > > Kdenlive and digiKam) that use markdown for their docs:
> > > > 
> > > > https://www.markdownguide.org/basic-syntax/
> > > > 
> > > > It's good to take this into account.
> > > > 
> > > > Best regards,
> > > > Yuri
> > > > 
> > > > On Fri, Dec 23, 2022 at 7:15 AM Yuri Chornoivan 
> > > > 
> > > > wrote:
> > > > > пʼятниця, 23 грудня 2022 р. 14:07:54 EET Aaron L написано:
> > > > > > Hi,
> > > > > > 
> > > > > > I'm looking to help out with some documentation.
> > > > > > 
> > > > > > What is currently being done?
> > > > > > 
> > > > > > I see there's a few applications that need some documentation
> > > > > > work.
> > > > > > 
> > > > > > Best,
> > > > > > Aaron
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > Actually the situation is not that bright. We have several
> > 
> > applications
> > 
> > > > > that
> > > > > were updated for 22.12 without syncing their documentation.
> > > > > 
> > > > > Spectacle
> > > > > Gwenview
> > > > > Okular
> > > > > Kate/Kwrite
> > > > > 
> > > > > Those need careful investigation. Now the major overhaul of digiKam
> > > > > documentation happens and we need to track this at some point.
> > > > > 
> > > > > https://invent.kde.org/documentation/digikam-doc/-/tree/sphinx
> > > > > 
> > > > > That's just my partial point of view.
> > > > > 
> > > > > Best regards,
> > > > > Yuri
> > > > > 
> > > > > > On Fri, Dec 23, 2022, 2:08 AM Yuri Chornoivan 
> > > > 
> > > > wrote:
> > > > > > > пʼятниця, 23 грудня 2022 р. 01:04:51 EET Aaron L написано:
> > > > > > > > Hi there,
> > > > > > > > 
> > > > > > > > I am reaching out as I would like to assist with writing and
> > > > 
> > > > updating
> > > > 
> > > > > > > some
> > > > > > > 
> > > > > > > > of the KDE application documentation. I have roughly ~7-8
> > 
> > years of
> > 
> > > > > > > writing
> > > > > > > 
> > > > > > > > and editing experience.
> > > > > > > > 
> > > > > > > > I have a computer with KDE (Kubuntu 22.04) installed.
> > > > > > > > 
> > > > > > > > Currently, I am reading the primer documentation.
> > > > > > > > 
> > > > > > > > Looking forward to hearing from you!
> > > > > > > > 
> > > > > > > > Best,
> > > > > > > > Aaron
> > > > > > > 
> > > > > > > Hi,
> > > > > > > 
> > > > > > > Welcome aboard!
> > > > > > > 
> > > > > > > Please do not hesitate to ask any questions (and subscribe to
> > > > > > > the
> > > > > 
> > > > > mailing
> > > > > 
> > > > > > > list
> > > > > > > [1]).
> > > > > > > 
> > > > > > > Thanks in advance for your help.
> > > > > > > 
> > > > > > > Best regards,
> > > > > > > Yuri
> > > > > > > 
> > > > > > > [1] https://mail.kde.org/mailman/listinfo/kde-doc-english

Re: Technical Writing / Updating Documentation

[Yuri Chornoivan]

неділя, 25 грудня 2022 р. 01:45:33 EET Aaron L написано:
> Hi Yury,
> 
> I will take a look. Other documentation first.
> 
> Why is KDE using two different methods?

That's the multilevel question.

1. Some hope that the new (other) publication system allows them to rewrite 
old docs in the modern way.

2. Some believe that DocBook is hard to understand and frighten potential 
writers.

3. Some think that Sphinx is easier to adopt and manage.

Best regards,
Yuri

> 
> Best,
> Aaron
> 
> On Sat, Dec 24, 2022 at 8:32 AM Yuri Chornoivan  wrote:
> > > Hi Yury,
> > > 
> > > I will read the following to get an understanding of the processes:
> > > 
> > > 
> > > https://community.kde.org/Get_Involved/documentation
> > > 
> > > 
> > > https://l10n.kde.org/docs/doc-primer/
> > > 
> > > Let me know if there's anything else I should be reading.
> > > 
> > > Best,
> > > Aaron
> > 
> > Yes, that's the main part. But now we have three major projects (Krita,
> > Kdenlive and digiKam) that use markdown for their docs:
> > 
> > https://www.markdownguide.org/basic-syntax/
> > 
> > It's good to take this into account.
> > 
> > Best regards,
> > Yuri
> > 
> > On Fri, Dec 23, 2022 at 7:15 AM Yuri Chornoivan 
> > 
> > wrote:
> > > пʼятниця, 23 грудня 2022 р. 14:07:54 EET Aaron L написано:
> > > > Hi,
> > > > 
> > > > I'm looking to help out with some documentation.
> > > > 
> > > > What is currently being done?
> > > > 
> > > > I see there's a few applications that need some documentation work.
> > > > 
> > > > Best,
> > > > Aaron
> > > 
> > > Hi,
> > > 
> > > Actually the situation is not that bright. We have several applications
> > > that
> > > were updated for 22.12 without syncing their documentation.
> > > 
> > > Spectacle
> > > Gwenview
> > > Okular
> > > Kate/Kwrite
> > > 
> > > Those need careful investigation. Now the major overhaul of digiKam
> > > documentation happens and we need to track this at some point.
> > > 
> > > https://invent.kde.org/documentation/digikam-doc/-/tree/sphinx
> > > 
> > > That's just my partial point of view.
> > > 
> > > Best regards,
> > > Yuri
> > > 
> > > > On Fri, Dec 23, 2022, 2:08 AM Yuri Chornoivan 
> > 
> > wrote:
> > > > > пʼятниця, 23 грудня 2022 р. 01:04:51 EET Aaron L написано:
> > > > > > Hi there,
> > > > > > 
> > > > > > I am reaching out as I would like to assist with writing and
> > 
> > updating
> > 
> > > > > some
> > > > > 
> > > > > > of the KDE application documentation. I have roughly ~7-8 years of
> > > > > 
> > > > > writing
> > > > > 
> > > > > > and editing experience.
> > > > > > 
> > > > > > I have a computer with KDE (Kubuntu 22.04) installed.
> > > > > > 
> > > > > > Currently, I am reading the primer documentation.
> > > > > > 
> > > > > > Looking forward to hearing from you!
> > > > > > 
> > > > > > Best,
> > > > > > Aaron
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > Welcome aboard!
> > > > > 
> > > > > Please do not hesitate to ask any questions (and subscribe to the
> > > 
> > > mailing
> > > 
> > > > > list
> > > > > [1]).
> > > > > 
> > > > > Thanks in advance for your help.
> > > > > 
> > > > > Best regards,
> > > > > Yuri
> > > > > 
> > > > > [1] https://mail.kde.org/mailman/listinfo/kde-doc-english

Re: Technical Writing / Updating Documentation

[Yuri Chornoivan]

> Hi Yury,
> 
> I will read the following to get an understanding of the processes:
> 
> 
> https://community.kde.org/Get_Involved/documentation
> 
> 
> https://l10n.kde.org/docs/doc-primer/
> 
> Let me know if there's anything else I should be reading.
> 
> Best,
> Aaron

Yes, that's the main part. But now we have three major projects (Krita, 
Kdenlive and digiKam) that use markdown for their docs:

https://www.markdownguide.org/basic-syntax/

It's good to take this into account.

Best regards,
Yuri

On Fri, Dec 23, 2022 at 7:15 AM Yuri Chornoivan  wrote:

> пʼятниця, 23 грудня 2022 р. 14:07:54 EET Aaron L написано:
> > Hi,
> >
> > I'm looking to help out with some documentation.
> >
> > What is currently being done?
> >
> > I see there's a few applications that need some documentation work.
> >
> > Best,
> > Aaron
>
> Hi,
>
> Actually the situation is not that bright. We have several applications
> that
> were updated for 22.12 without syncing their documentation.
>
> Spectacle
> Gwenview
> Okular
> Kate/Kwrite
>
> Those need careful investigation. Now the major overhaul of digiKam
> documentation happens and we need to track this at some point.
>
> https://invent.kde.org/documentation/digikam-doc/-/tree/sphinx
>
> That's just my partial point of view.
>
> Best regards,
> Yuri
>
> >
> > On Fri, Dec 23, 2022, 2:08 AM Yuri Chornoivan  wrote:
> > > пʼятниця, 23 грудня 2022 р. 01:04:51 EET Aaron L написано:
> > > > Hi there,
> > > >
> > > > I am reaching out as I would like to assist with writing and updating
> > >
> > > some
> > >
> > > > of the KDE application documentation. I have roughly ~7-8 years of
> > >
> > > writing
> > >
> > > > and editing experience.
> > > >
> > > > I have a computer with KDE (Kubuntu 22.04) installed.
> > > >
> > > > Currently, I am reading the primer documentation.
> > > >
> > > > Looking forward to hearing from you!
> > > >
> > > > Best,
> > > > Aaron
> > >
> > > Hi,
> > >
> > > Welcome aboard!
> > >
> > > Please do not hesitate to ask any questions (and subscribe to the
> mailing
> > > list
> > > [1]).
> > >
> > > Thanks in advance for your help.
> > >
> > > Best regards,
> > > Yuri
> > >
> > > [1] https://mail.kde.org/mailman/listinfo/kde-doc-english
>
>
>
>
>

Re: Technical Writing / Updating Documentation

[Yuri Chornoivan]

пʼятниця, 23 грудня 2022 р. 14:07:54 EET Aaron L написано:
> Hi,
> 
> I'm looking to help out with some documentation.
> 
> What is currently being done?
> 
> I see there's a few applications that need some documentation work.
> 
> Best,
> Aaron

Hi,

Actually the situation is not that bright. We have several applications that 
were updated for 22.12 without syncing their documentation.

Spectacle
Gwenview
Okular
Kate/Kwrite

Those need careful investigation. Now the major overhaul of digiKam 
documentation happens and we need to track this at some point.

https://invent.kde.org/documentation/digikam-doc/-/tree/sphinx

That's just my partial point of view.

Best regards,
Yuri

> 
> On Fri, Dec 23, 2022, 2:08 AM Yuri Chornoivan  wrote:
> > пʼятниця, 23 грудня 2022 р. 01:04:51 EET Aaron L написано:
> > > Hi there,
> > > 
> > > I am reaching out as I would like to assist with writing and updating
> > 
> > some
> > 
> > > of the KDE application documentation. I have roughly ~7-8 years of
> > 
> > writing
> > 
> > > and editing experience.
> > > 
> > > I have a computer with KDE (Kubuntu 22.04) installed.
> > > 
> > > Currently, I am reading the primer documentation.
> > > 
> > > Looking forward to hearing from you!
> > > 
> > > Best,
> > > Aaron
> > 
> > Hi,
> > 
> > Welcome aboard!
> > 
> > Please do not hesitate to ask any questions (and subscribe to the mailing
> > list
> > [1]).
> > 
> > Thanks in advance for your help.
> > 
> > Best regards,
> > Yuri
> > 
> > [1] https://mail.kde.org/mailman/listinfo/kde-doc-english

Re: Technical Writing / Updating Documentation

[Yuri Chornoivan]

пʼятниця, 23 грудня 2022 р. 01:04:51 EET Aaron L написано:
> Hi there,
> 
> I am reaching out as I would like to assist with writing and updating some
> of the KDE application documentation. I have roughly ~7-8 years of writing
> and editing experience.
> 
> I have a computer with KDE (Kubuntu 22.04) installed.
> 
> Currently, I am reading the primer documentation.
> 
> Looking forward to hearing from you!
> 
> Best,
> Aaron

Hi,

Welcome aboard!

Please do not hesitate to ask any questions (and subscribe to the mailing list 
[1]).

Thanks in advance for your help.

Best regards,
Yuri

[1] https://mail.kde.org/mailman/listinfo/kde-doc-english

[utilities/kate] doc/kate: Add new configuration option to the docs

[Yuri Chornoivan]

Git commit 8d06eb2e9a67c8e19ebf90d00313d3d0b6e54743 by Yuri Chornoivan.
Committed on 19/12/2022 at 09:56.
Pushed by yurchor into branch 'master'.

Add new configuration option to the docs

M  +9-0doc/kate/configuring.docbook

https://invent.kde.org/utilities/kate/commit/8d06eb2e9a67c8e19ebf90d00313d3d0b6e54743

diff --git a/doc/kate/configuring.docbook b/doc/kate/configuring.docbook
index f72dc0f93..ee1529c87 100644
--- a/doc/kate/configuring.docbook
+++ b/doc/kate/configuring.docbook
@@ -91,6 +91,15 @@ the right.
 
 
 
+
+
+Open each document in its own window
+If enabled, each document will be opened in its own window.
+If not enabled, each document will be opened in a new tab in the current
+window.
+
+
+
 
 
 Switch to output view upon message type

[education/kstars] doc: Remove leftover

[Yuri Chornoivan]

Git commit 0b901fb69545fe8760bcc5c27ac522d6db67324b by Yuri Chornoivan.
Committed on 02/12/2022 at 15:25.
Pushed by yurchor into branch 'master'.

Remove leftover

M  +1-1doc/ekos-capture.docbook

https://invent.kde.org/education/kstars/commit/0b901fb69545fe8760bcc5c27ac522d6db67324b

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 6587fdf06..593bf712a 100644
--- a/doc/ekos-capture.docbook
+++ b/doc/ekos-capture.docbook
@@ -214,7 +214,7 @@
 
 
 
-%s* or %sequence*: Placeholder %s* or %sequence: The image 
sequence identifier where * is the number of digits used (1-9). This tag is mandatory and must be the last element in the 
format.
+%s* or %sequence*: The image sequence identifier where * is the 
number of digits used (1-9). This tag is mandatory and 
must be the last element in the format.
 
 
 

[utilities/kate] doc/kate: Fix minor typo

[Yuri Chornoivan]

Git commit d0430138eb46fd767aa233b6e34a7b03f91a5e4c by Yuri Chornoivan.
Committed on 02/12/2022 at 06:18.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/kate/plugins.docbook

https://invent.kde.org/utilities/kate/commit/d0430138eb46fd767aa233b6e34a7b03f91a5e4c

diff --git a/doc/kate/plugins.docbook b/doc/kate/plugins.docbook
index 043341f3a..520ff3cfb 100644
--- a/doc/kate/plugins.docbook
+++ b/doc/kate/plugins.docbook
@@ -2045,7 +2045,7 @@ or you can tell it to recursively load files from 
directories as follows:
 Here, subfolders and filters define what’s part of the project.
 You can also mix version control and files based on filters.
 Hidden files will not be retrieved if the option "hidden" is 0.
-"exclude_patterns" is a list of regex patterns than can be used 
+"exclude_patterns" is a list of regex patterns that can be used 
 to exclude folders and files from the project tree. In this example, All files
 and folders in a directory build from the root will be 
excluded.
 

Re: Okular,Version 21.12.3 Linux Mint

[Yuri Chornoivan]

вівторок, 15 листопада 2022 р. 11:16:12 EET Dan Haim Ostroff написано:
> Can't find a way to delete a bookmark
> please help
> 
> thank you
> dan

Hi,

Right-click in the menu then "Delete this bookmark".

Hope this helps.

Bets regards,
Yuri

[utilities/konsole] doc/manual: Make translation easier

[Yuri Chornoivan]

Git commit 3178aec6f90e9303b8151e59fbe0f39334141fe2 by Yuri Chornoivan.
Committed on 31/10/2022 at 15:25.
Pushed by yurchor into branch 'master'.

Make translation easier

M  +2-1doc/manual/index.docbook

https://invent.kde.org/utilities/konsole/commit/3178aec6f90e9303b8151e59fbe0f39334141fe2

diff --git a/doc/manual/index.docbook b/doc/manual/index.docbook
index 8892ed13b..da3b0d397 100644
--- a/doc/manual/index.docbook
+++ b/doc/manual/index.docbook
@@ -378,7 +378,7 @@ various enhancements in Konsole.
 and
 PgDown
 scroll up/down to previous/next command prompt.
-Visual hints:
+Visual hints:
 
 
 A line is displayed above each prompt, prompt colors are less intense,
@@ -397,6 +397,7 @@ A gray bar is displayed to the left of the input and output 
lines of every other
 A gray background for the input and output lines of every other command.
 
 
+
 Each of those may be configured to never show, always show, or only when URL 
hints are shown. The configuration is in the
 Semantic Integration tab of the 
General page of the profile configuration
 window.

[education/kstars] doc: Fix minor typos

[Yuri Chornoivan]

Git commit ab1918351666930fc19cfd091a76ddee4eb7df98 by Yuri Chornoivan.
Committed on 21/10/2022 at 14:29.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +2-2doc/ekos-focus.docbook

https://invent.kde.org/education/kstars/commit/ab1918351666930fc19cfd091a76ddee4eb7df98

diff --git a/doc/ekos-focus.docbook b/doc/ekos-focus.docbook
index 0aebc2836..15be57eb4 100644
--- a/doc/ekos-focus.docbook
+++ b/doc/ekos-focus.docbook
@@ -523,7 +523,7 @@
Backlash Managed by
   Focuser: If your focuser had the ability to manage
   backlash itself then you can use this facility and turn off AF
-  Backlash Comp. Alternatively, if its possible, you could turn
+  Backlash Comp. Alternatively, if it's possible, you could turn
   off the focuser's backlash facility and set AF Backlash Comp
   on.
 
@@ -532,7 +532,7 @@
Backlash Managed by Device
   Driver: If your device driver had the ability to
   manage backlash itself then you can use this facility and turn
-  off AF Backlash Como. Alternatively, if its possible, you could
+  off AF Backlash Comp. Alternatively, if it's possible, you could
   turn off the device driver's backlash facility and set AF
   Backlash Comp on.
 

Re: Probably documentation/calligraplan/calligraplan/plan/managingresources.docbook contains wrong id

[Yuri Chornoivan]

середа, 12 жовтня 2022 р. 19:19:10 EEST Freek de Kruijf написано:
> Probably documentation/calligraplan/calligraplan/plan/
> managingresources.docbook should contain in its first line
> Description
> instead of
> Description
>^

Hi,

I think that this change is needless. It's just a common title for all  
descriptions in this folder. Cf. taskeditor.docbook:


Description

Best regards,
Yuri

[utilities/kate] doc/kate: Fix minor typos

[Yuri Chornoivan]

Git commit 3651601bb83f15d930c25c5973a14553ce7afebf by Yuri Chornoivan.
Committed on 05/10/2022 at 03:57.
Pushed by yurchor into branch 'master'.

Fix minor typos

M  +1-1doc/kate/plugins.docbook

https://invent.kde.org/utilities/kate/commit/3651601bb83f15d930c25c5973a14553ce7afebf

diff --git a/doc/kate/plugins.docbook b/doc/kate/plugins.docbook
index 1769a4cd1..c828b4948 100644
--- a/doc/kate/plugins.docbook
+++ b/doc/kate/plugins.docbook
@@ -2102,7 +2102,7 @@ You can also mix version control and files based on 
filters.
 The targets specified above will then appear in the Build Plugin  under 
 "Project Plugin Targets".
 
-If the "targets" array is specified then "build", 
"clean" and "install" are ignored. Each element in 
the array specifies a target. "name" is the name of the target, 
"build_cmd" will be used to build the target, 
"run_cmd" is will be used to run the target. Most important of all 
is  "directory", this is where the commands will be executed.
+If the "targets" array is specified then "build", 
"clean" and "install" are ignored. Each element in 
the array specifies a target. "name" is the name of the target, 
"build_cmd" will be used to build the target, 
"run_cmd" will be used to run the target. Most important of all is 
"directory", this is where the commands will be executed.
 
 
 

[utilities/konsole] doc/manual: Fix minor typo

[Yuri Chornoivan]

Git commit d749a4b4e50022782cbe2a2b8614e6ffd9f6e124 by Yuri Chornoivan.
Committed on 04/10/2022 at 04:17.
Pushed by yurchor into branch 'master'.

Fix minor typo

M  +1-1doc/manual/index.docbook

https://invent.kde.org/utilities/konsole/commit/d749a4b4e50022782cbe2a2b8614e6ffd9f6e124

diff --git a/doc/manual/index.docbook b/doc/manual/index.docbook
index 7f29d1083..c3b428728 100644
--- a/doc/manual/index.docbook
+++ b/doc/manual/index.docbook
@@ -112,7 +112,7 @@ to open this window).
 
 
 Selection Mode
- has a selction by keyboard mode. In this mode it is possible 
to move around the scrollback and select text
+ has a selection by keyboard mode. In this mode it is possible 
to move around the scrollback and select text
 without the mouse.
 
 

[system/khelpcenter] doc/fundamentals: Fix minor issue in docs

[Yuri Chornoivan]

Git commit 97eac96d33ca8bba4b9ac24ff0a0d7af203629a1 by Yuri Chornoivan.
Committed on 26/09/2022 at 05:44.
Pushed by yurchor into branch 'master'.

Fix minor issue in docs

M  +2-2doc/fundamentals/ui.docbook

https://invent.kde.org/system/khelpcenter/commit/97eac96d33ca8bba4b9ac24ff0a0d7af203629a1

diff --git a/doc/fundamentals/ui.docbook b/doc/fundamentals/ui.docbook
index 953a89bb..605a7d60 100644
--- a/doc/fundamentals/ui.docbook
+++ b/doc/fundamentals/ui.docbook
@@ -1528,12 +1528,12 @@ application you are using doesn't support it.
 
 
 Left
-Pan left, move window to monitor to the leftIn 
a multi-monitor environment
+Pan left, move window to monitor to the leftIn 
a multi-monitor environment
 
 
 
 Right
-Pan right, move window to monitor to the right
+Pan right, move window to monitor to the right
 
 
 

[system/khelpcenter] doc/fundamentals: Add shortcuts information to the docs

[Yuri Chornoivan]

Git commit 4490ef893fbff8f363bbe1ccd7d0741a5b72267d by Yuri Chornoivan.
Committed on 25/09/2022 at 19:08.
Pushed by yurchor into branch 'master'.

Add shortcuts information to the docs

BUG:459672

M  +12   -2doc/fundamentals/ui.docbook

https://invent.kde.org/system/khelpcenter/commit/4490ef893fbff8f363bbe1ccd7d0741a5b72267d

diff --git a/doc/fundamentals/ui.docbook b/doc/fundamentals/ui.docbook
index 6eb8d934..953a89bb 100644
--- a/doc/fundamentals/ui.docbook
+++ b/doc/fundamentals/ui.docbook
@@ -1528,12 +1528,22 @@ application you are using doesn't support it.
 
 
 Left
-Pan left
+Pan left, move window to monitor to the leftIn 
a multi-monitor environment
 
 
 
 Right
-Pan Right
+Pan right, move window to monitor to the right
+
+
+
+PgUp
+Maximize/Restore window
+
+
+
+PgDn
+Minimize window
 
 
 

[docs.kde.org] [Bug 459672] Missing keyboard shortcuts for resizing windows and missing descriptions for moving windows

[Yuri Chornoivan]

https://bugs.kde.org/show_bug.cgi?id=459672

Yuri Chornoivan  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
  Latest Commit||https://invent.kde.org/syst
   ||em/khelpcenter/commit/4490e
   ||f893fbff8f363bbe1ccd7d0741a
   ||5b72267d
 Resolution|--- |FIXED

--- Comment #1 from Yuri Chornoivan  ---
Git commit 4490ef893fbff8f363bbe1ccd7d0741a5b72267d by Yuri Chornoivan.
Committed on 25/09/2022 at 19:08.
Pushed by yurchor into branch 'master'.

Add shortcuts information to the docs

M  +12   -2doc/fundamentals/ui.docbook

https://invent.kde.org/system/khelpcenter/commit/4490ef893fbff8f363bbe1ccd7d0741a5b72267d

-- 
You are receiving this mail because:
You are the assignee for the bug.

[docs] [Bug 459274] "User Feedback" section is named as "Trash" in Dolphin's doc

[Yuri Chornoivan]

https://bugs.kde.org/show_bug.cgi?id=459274

Yuri Chornoivan  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||yurc...@ukr.net
 Status|REPORTED|RESOLVED

--- Comment #1 from Yuri Chornoivan  ---
Fixed. Thanks for reporting.

https://invent.kde.org/system/dolphin/-/commit/6e6993f09864e5cd738fb90bab2e261f6430a041

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: Proofreading Team

[Yuri Chornoivan]

четвер, 8 вересня 2022 р. 23:42:59 EEST Vladimir Rakhmanin написано:
> Many thanks both! I'll have a read through this shortly. If I spot any
> typos etc. should I open a PR request to that repo with suggested tweaks?

Yes. I think this way would be prefferrable.

Some hints on the account for invent.kde.org

https://community.kde.org/Infrastructure/Get_a_Developer_Account

Thanks in advance for your work.

Best regards,
Yuri

> Or should I just keep a note of them and post to this mailing list once
> I've finished reading through?
> 
> Vlad
> 
> On Thu, 8 Sept 2022 at 21:09, Yuri Chornoivan  wrote:
> > четвер, 8 вересня 2022 р. 23:00:19 EEST Albert Astals Cid написано:
> > > El dijous, 8 de setembre de 2022, a les 17:34:16 (CEST), Yuri Chornoivan
> > 
> > va
> > 
> > > escriure:
> > > > четвер, 8 вересня 2022 р. 18:32:07 EEST Vladimir Rakhmanin написано:
> > > > > Hi there!
> > > > > 
> > > > > I saw in the "Doc Primer" that you folks are looking for people to
> > 
> > help
> > 
> > > > > with proofreading some documentation - I would love to help out with
> > > > > this
> > > > > if possible.
> > > > > 
> > > > > Before I switched careers to software engineering I was a corporate
> > > > > lawyer
> > > > > for five years, so a lot of my work involved proofreading
> > 
> > documentation
> > 
> > > > > for
> > > > > grammar / spelling / punctuation errors etc., so I think I might be
> > 
> > able
> > 
> > > > > to
> > > > > assist!
> > > > > 
> > > > > Kind regards
> > > > > 
> > > > > Vlad
> > > > 
> > > > Hi,
> > > > 
> > > > Welcome aboard!
> > > > 
> > > > Thanks in advance for your work.
> > > 
> > > Yuri, I think he wanted some pointing into exactly what he can do/how he
> > 
> > can
> > 
> > > help :)
> > > 
> > > Cheers,
> > > 
> > >   Albert
> > 
> > Ok. We need to proofread Skrooge docs.
> > 
> > Text:
> > https://docs.kde.org/trunk5/en/skrooge/skrooge/index.html
> > 
> > Source (for online editing):
> > https://invent.kde.org/office/skrooge/-/blob/master/doc/index.docbook
> > 
> > Please ask if you need some information.
> > 
> > Best regards,
> > Yuri