Re: digiKam handbook migrated from DocBook to Sphinx/ReStructuredText

2022-12-30 Thread Luigi Toscano 
Gilles Caulier ha scritto:
> Hi,
> 
> Yes, these kinds of urls formatting will be restored. I currently do a
> second pass in the rdt files to see if I forget links and I found some
> missing entries.

Talking about changes: I see the documentation was relicensed from GFDL to
CC-BY SA 4, and it looks like several content was copied, not rewritten. Did
you get the permissions from all contributors of the docbooks before
relicensing? Otherwise we must use the previous license until that's sorted
out, asking translators to apply both.


Ciao
-- 
Luigi

Re: digiKam handbook migrated from DocBook to Sphinx/ReStructuredText

2022-12-30 Thread Gilles Caulier 
Hi,

Yes, these kinds of urls formatting will be restored. I currently do a
second pass in the rdt files to see if I forget links and I found some
missing entries.

Best

Gilles

Le sam. 31 déc. 2022 à 00:06, Freek de Kruijf  a écrit :
>
> Op donderdag 29 december 2022 08:51:47 CET schreef Gilles Caulier:
> > Hi all translation team,
> >
> > I'm glad to announce that the whole digiKam handbook based on DocBook
> > format is not fully migrated to the Sphinx/RestructuredText framework.
> > This will help to maintain the manual more easily in time, as
> > ReStructuredText is so far better in all forms than the DocBook
> > format, especially for huge documentation.
> >
> > The infrastructure is based on the KDenLive works (based too on the
> > Krita works). For the translations of this manual, it will be the same
> > workflow.
> >
> > Online manual is hosted in a dedicated web site available here :
> >
> > https://docs.digikam.org/en/index.html
> >
> > This means that older Docbook translations from the older manual are
> > now obsolete...
> >
> > Typically the obsolete POT files are there (docbook):
> >
> > https://websvn.kde.org/trunk/l10n-kf5/templates/docmessages/digikam-doc/
> >
> > The new POT files are there (ReStructuredText):
> >
> > https://websvn.kde.org/trunk/l10n-kf5/templates/messages/digikam-doc/
> >
> > The git repository for the new manual still the same than previous one :
> >
> > https://invent.kde.org/documentation/digikam-doc
> >
> > Look at the README file for details.
> >
> > Thanks to contribute and all the best for this new year
> >
> > Gilles Caulier
>
> When copying the translated text from docmessages into the digikam-doc
> environment I noticed that several time the original English text from
> docmessages did contain structures like "this URL", which appear in the text in
> digikam-doc as "this URL".
>
> Will these URL's reappear at a later time in the new text as:
> `this URL`_ ?
>
> I also found the structure, originally with a URL and now only "here". So here
> does not point to anything.
>
> --
>
> fr.gr.
>
> Freek de Kruijf
> vertaler/coördinator van KDE
>
>
>

Re: digiKam handbook migrated from DocBook to Sphinx/ReStructuredText

2022-12-30 Thread Freek de Kruijf 
Op donderdag 29 december 2022 08:51:47 CET schreef Gilles Caulier:
> Hi all translation team,
> 
> I'm glad to announce that the whole digiKam handbook based on DocBook
> format is not fully migrated to the Sphinx/RestructuredText framework.
> This will help to maintain the manual more easily in time, as
> ReStructuredText is so far better in all forms than the DocBook
> format, especially for huge documentation.
> 
> The infrastructure is based on the KDenLive works (based too on the
> Krita works). For the translations of this manual, it will be the same
> workflow.
> 
> Online manual is hosted in a dedicated web site available here :
> 
> https://docs.digikam.org/en/index.html
> 
> This means that older Docbook translations from the older manual are
> now obsolete...
> 
> Typically the obsolete POT files are there (docbook):
> 
> https://websvn.kde.org/trunk/l10n-kf5/templates/docmessages/digikam-doc/
> 
> The new POT files are there (ReStructuredText):
> 
> https://websvn.kde.org/trunk/l10n-kf5/templates/messages/digikam-doc/
> 
> The git repository for the new manual still the same than previous one :
> 
> https://invent.kde.org/documentation/digikam-doc
> 
> Look at the README file for details.
> 
> Thanks to contribute and all the best for this new year
> 
> Gilles Caulier

When copying the translated text from docmessages into the digikam-doc 
environment I noticed that several time the original English text from 
docmessages did contain structures like "this URL", which appear in the text in 
digikam-doc as "this URL". 

Will these URL's reappear at a later time in the new text as:
`this URL`_ ?

I also found the structure, originally with a URL and now only "here". So here 
does not point to anything.

-- 

fr.gr.

Freek de Kruijf
vertaler/coördinator van KDE

Re: digiKam handbook migrated from DocBook to Sphinx/ReStructuredText

2022-12-30 Thread Albert Astals Cid 
El dijous, 29 de desembre de 2022, a les 8:51:47 (CET), Gilles Caulier va 
escriure:
> Hi all translation team,

kde-doc-english@kde.org is "This is a list for people who are writing 
documentation for the KDE project and its software." not the translation team.

Cheers,
  Albert

[network/smb4k] doc: Update handbook.

2022-12-30 Thread Alexander Reinholdt 
Git commit 9f9e7c564435212b036d87d55e847ed6714de303 by Alexander Reinholdt.
Committed on 30/12/2022 at 08:03.
Pushed by areinholdt into branch 'master'.

Update handbook.

M  +8-9doc/index.docbook

https://invent.kde.org/network/smb4k/commit/9f9e7c564435212b036d87d55e847ed6714de303

diff --git a/doc/index.docbook b/doc/index.docbook
index 714e5f6a..f658f4aa 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -3321,7 +3321,7 @@ ntlm auth = yes
 
   Option: -a/--archive, 
same as -rlptgoD (no -A, -X, 
-U, -N, -H)
   Switch the archive mode on. This is a quick way of saying 
you want recursion and want to preserve almost everything. Note that 
-a does not preserve hardlinks (-H), access 
control lists (ACLs, -A), extended attributes (xattrs, 
-X), access (use) times (-U) nor create times 
(-N). You must separately specify these options. The only 
exception to the above equivalence is when --files-from is 
specified, in which case -r is not implied.
-  In case you do not want to run 
rsync in archive mode, choose the appropriate 
arguments in the settings yourself.
+  In case you do not want to run rsync1
 in archive mode, choose the appropriate arguments in the settings 
yourself.
   Default: selected
 
   
@@ -3400,7 +3400,7 @@ ntlm auth = yes
 
 
   Option: --backup-dir=DIR
-  In combination with the --backup option, 
this tells rsync to store all backups in the specified folder. This is very 
useful for incremental backups. You can additionally specify a backup suffix 
using the --suffix option (otherwise the files backed up in 
the specified folder will keep  their original filenames).
+  In combination with the --backup option, 
this tells rsync1
 to store all backups in the specified folder. This is very useful for 
incremental backups. You can additionally specify a backup suffix using the 
--suffix option (otherwise the files backed up in the 
specified folder will keep  their original filenames).
   This option is only available if you ticked the 
Make backups option above.
   Default: not selected; DIR: $HOME
 
@@ -3596,7 +3596,7 @@ ntlm auth = yes
 
 
   Option: -A/--acls
-  Preserve access control lists. This option causes rsync to 
update the destination ACLs to be the same as the source ACLs. The option also 
implies --perms. The source and destination systems must have compatible ACL 
entries for this option to work properly.
+  Preserve access control lists. This option causes rsync1
 to update the destination ACLs to be the same as the source ACLs. The option 
also implies --perms. The source and destination systems must have compatible 
ACL entries for this option to work properly.
   Default: not selected
 
   
@@ -3606,7 +3606,7 @@ ntlm auth = yes
 
 
   Option: 
-X/--xattrs
-  Preserve extended attributes. This option causes rsync to 
update the destination extended attributes to be the same as the source 
ones.
+  Preserve extended attributes. This option causes rsync1
 to update the destination extended attributes to be the same as the source 
ones.
   Default: not selected
 
   
@@ -3616,7 +3616,7 @@ ntlm auth = yes
 
 
   Option: 
-U/--atimes
-  Preserve access times. This tells rsync to set the access 
(use) times of the destination files to the same value as the source 
files.
+  Preserve access times. This tells rsync1
 to set the access (use) times of the destination files to the same value as 
the source files.
   Default: not selected
 
   
@@ -3626,7 +3626,7 @@ ntlm auth = yes
 
 
   Option: 
-N/--crtimes
-  Preserve create times. This tells rsync to set the create 
times (newness) of the destination files to the same value as the source 
files.
+  Preserve create times. This tells rsync1
 to set the create times (newness) of the destination files to the same value 
as the source files.
   Default: not selected
 
   
@@ -3725,7 +3725,7 @@ ntlm auth = yes
 
 
   Option: --skip-compress=LIST
-  Overwrite the list of file suffixes that will not be 
compressed. The LIST should be one or more file suffixes (without the dot) 
separated by slashes. You may specify an empty string to indicate that no file 
should be skipped. The default list of suffixes will be replaced by this list. 
For further details, see the manual page of rsync.
+  Overwrite the list of file suffixes that will not be 
compressed. The LIST should be one or more file suffixes (without the dot)