[education/kstars] doc: Fix links in documentation

2024-01-10 Thread 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
 


[docs.kde.org] [Bug 479608] New: Enable ca@valencia language code

2024-01-10 Thread Antoni Bella
https://bugs.kde.org/show_bug.cgi?id=479608

Bug ID: 479608
   Summary: Enable ca@valencia language code
Classification: Websites
   Product: docs.kde.org
   Version: unspecified
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: docs.kde.org
  Assignee: kde-doc-english@kde.org
  Reporter: antonibel...@yahoo.com
  Target Milestone: ---

SUMMARY
***

Please, enable ca@valencia translations.

All frameworks are ready, Kstars is disabled for app request but you can enable
into web (copy index.docbook file manually and would not be the deleted).

Next step are Plasma doc (KHelpCenter are ready).

KF6 need her frist build (tell me about it).
***

EXPECTED RESULT

  Valencian language availability in more webs.

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

[education/kstars] /: sub-exposure calculator documentation updates

2024-01-10 Thread Jasem Mutlaq
Git commit 1599677064d794e6fa66e108f9ef8445365f2a9f by Jasem Mutlaq, on behalf 
of Joseph McGee.
Committed on 10/01/2024 at 11:40.
Pushed by mutlaqja into branch 'master'.

sub-exposure calculator documentation updates

M  +4-4doc/ekos-capture.docbook
M  +---doc/exposure-calculator.png
M  +1-1kstars/ekos/capture/capture.ui
M  +1-1
kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.cpp
M  +14   -2
kstars/ekos/capture/exposurecalculator/exposurecalculatordialog.ui

https://invent.kde.org/education/kstars/-/commit/1599677064d794e6fa66e108f9ef8445365f2a9f

diff --git a/doc/ekos-capture.docbook b/doc/ekos-capture.docbook
index 597cd5bf25..6d8ee36371 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/Light_pollution;>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
 
@@ -558,7 +558,7 @@ Approaches to imaging can vary greatly in the selection of 
exposure times, and n
 
 
 
-Focal Ratio: The selector 
for Focal Ratio set the value from the optical train, which 
is needed for the evaluation of light gathering capability.
+Focal Ratio: The selector 
for Focal Ratio sets the value from the optical train, which 
is needed for the evaluation of light gathering capability.
 
 The value of the focal ratio of the optic has 
a direct effect on the exposure calculation. A lower focal ratio is considered 
to be a "faster optic" as it has a greater light gathering capability than an 
optic with a longer focal ratio. So the exposure calculation will be reduced 
when a lower focal ratio is used, and increased when a higher focal ratio is 
used.
 
@@ -691,7 +691,7 @@ For a strong target, (example, Orion Nebula with magnitude 
4), would provide a r
 
 
 
-Depending on the various inputs and imaging conditions, the potential quality 
of a sub-exposure can vary greatly. In poor sky quality with little or no 
filtering, the computed sub-exposure time will naturally be short to avoid an 
overwhelming noise from light pollution, and the exposure time relative to the 
computed noise will be low (a low time/noise ratio). To achieve a high quality 
integrated image from low time/noise ratio sub-exposures may require thousands 
sub-exposures.  If the user is concerned about imaging and processing time or 
storage capacity; then a higher time/noise ratio would needed to reduce the 
quantity of sub-exposures. Conversely, when input conditions result in a 
sub-exposure with a long exposure time relative to the computed noise (as with 
narrow-band imaging), the result is a sub-exposure with a very high time/noise 
ratio.  In such cases the default value of 80, might result in very few 
sub-exposures for the integration.  But the delta value will be quite high, 
indicating that raising the time-noise ratio will greatly improve the potential 
quality of the integrated image.  

[sdk/kdesrc-build] /: Check that all option names read from config are recognised

2024-01-10 Thread Andrew Shark
Git commit f99141cadf12bbb7221ddc88ea6ce3e208b492df by Andrew Shark.
Committed on 10/01/2024 at 10:26.
Pushed by ashark into branch 'master'.

Check that all option names read from config are recognised

For every option name read from the config, we will check if it is in 
`@all_possible_options` array. And if not, raise an exception.

To differentiate between normal config options and non-standard config options 
(options with custom name defined by user), we will prepend non-standard 
options with underscore. So users can still use this convenience feature.

Other changes of this commit:
- Allow substituting references to global options when they have underscore in 
their name.
- Add ability to _use_ custom variable immediately after defining in global 
section
- Fix end word typo in `t/data/kde-projects/kdesrc-buildrc-with-deps`.
- Temporary show a help message for the recently renamed option "kdedir".

M  +19   -1doc/kdesrc-buildrc.docbook
M  +18   -6modules/ksb/Application.pm
M  +2-2t/data/branch-time-based/kdesrc-buildrc
M  +1-1t/data/kde-projects/kdesrc-buildrc-with-deps

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

diff --git a/doc/kdesrc-buildrc.docbook b/doc/kdesrc-buildrc.docbook
index 53396e46..68cd4d7e 100644
--- a/doc/kdesrc-buildrc.docbook
+++ b/doc/kdesrc-buildrc.docbook
@@ -95,7 +95,7 @@ linkend="conf-use-modules">use-modules for more 
information.
 option-value.
 
 One modification that  performs is that a sequence
-${name-of-option} is replaced
+"${name-of-option}" is 
replaced
 with the value of that option from the global configuration. This allows you
 to reference the value of existing options, including options already set by
 .
@@ -104,6 +104,24 @@ to reference the value of existing options, including 
options already set by
 To see an example of this in use, see
 .
 
+You can also introduce your own non-standard global variables for 
referencing them further in the config.
+To do this, your option name should be prepended with underscore symbol. 
Example:
+
+Introducing your own global option for referencing later in 
config
+
+global
+  _ver 6  # ← your custom variable (starting with underscore)
+  _kde ~/kde${_ver}  # ← custom variable can contain another defined variable
+  source-dir ${_kde}/src  # ← note that nested variable (_kde → _ver) is also 
resolved
+end global
+
+options kdepim
+  log-dir /custom/path/logs${_ver} # ← you can use custom variable just like a 
standard
+end options
+
+
+
+
 
 
 
diff --git a/modules/ksb/Application.pm b/modules/ksb/Application.pm
index 26cf9ec2..2a99c248 100644
--- a/modules/ksb/Application.pm
+++ b/modules/ksb/Application.pm
@@ -805,18 +805,18 @@ sub _readNextLogicalLine
 
 # Takes an input line, and extracts it into an option name, and simplified
 # value. The value has "false" converted to 0, white space simplified (like in
-# Qt), and tildes (~) in what appear to be path-like entries are converted to
-# the home directory path.
+# Qt), tildes (~) in what appear to be path-like entries are converted to
+# the home directory path, and reference to global option is substituted with 
its value.
 #
 # First parameter is the build context (used for translating option values).
 # Second parameter is the line to split.
 # Return value is (option-name, option-value)
-sub _splitOptionAndValue
+sub _splitOptionAndValue_and_substitute_value
 {
 my $ctx = assert_isa(shift, 'ksb::BuildContext');
 my $input = shift;
 my $fileName = shift->currentFilename();
-my $optionRE = qr/\$\{([a-zA-Z0-9-]+)\}/;
+my $optionRE = qr/\$\{([a-zA-Z0-9-_]+)\}/;  # Example of matched string is 
"${option-name}" or "${_option-name}".
 
 # The option is the first word, followed by the
 # flags on the rest of the line.  The interpretation
@@ -836,7 +836,6 @@ sub _splitOptionAndValue
 $value = 0 if lc($value) eq 'false';
 
 # Replace reference to global option with their value.
-# The regex basically just matches ${option-name}.
 my ($sub_var_name) = ($value =~ $optionRE);
 while ($sub_var_name)
 {
@@ -936,6 +935,8 @@ sub _parseModuleOptions ($ctx, $fileReader, $module, 
$endRE=undef)
 _markModuleSource($module, $fileReader->currentFilename() . ":$.");
 $module->setOption('#entry_num', $moduleID++);
 
+my @all_possible_options = sort keys %{$ctx->{build_options}->{global}};
+
 # Read in each option
 while (($_ = _readNextLogicalLine($fileReader)) && ($_ !~ $endRE))
 {
@@ -949,7 +950,18 @@ sub _parseModuleOptions ($ctx, $fileReader, $module, 
$endRE=undef)
 die make_exception('Config', "Invalid file $current_file");
 }
 
-my ($option, $value) = _splitOptionAndValue($ctx, $_, $fileReader);
+my ($option, $value) = _splitOptionAndValue_and_substitute_value($ctx, 
$_, $fileReader);
+
+
+if (substr($option, 0, 1) eq "_") {  # option names starting with 
underscore are treated as user