firebird-docs — chat stuff about documentation

[Firebird-docs] AsciiDoc support for Visual Studio Code

[marius a. p. <ma...@gm...>]

Nice VSCode extension
https://marketplace.visualstudio.com/items?itemName=joaompinto.asciidoctor-vscode

Re: [Firebird-docs] Conversion of fbcache-de

[Köditz, M. <Mar...@it...>]

>On 2020-05-28 10:35, Köditz wrote:
>>>> Hi Mark,
>>>> 
>>>> thank you for the feedback. I did the conversion with help of Pandoc.
>>> 
>>> Pandoc is not my tool of choice for the conversion. I have selected 
>>> Docbookrx and implemented a number of customizations for it. For the 
>>> sake of consistency of output, I think it is better >that a single 
>>> method of conversion is used.
>>> 
>>>> I will correct it. Now I know what to look for.
>>> 
>>> Thanks.
>>> 
>>> Mark
>> 
>> Well, I tried to use Docbookrx, but got some errors. I will try it 
>> again later.
>
>Did you use the one from the firebird-modifications branch of https://github.com/mrotteveel/docbookrx ?

Yes, I used the modified one. I have to find out what the problem is.

>
>If you're working on Windows, I would recommend running it from within a WSL shell (eg Ubuntu from the Windows store).
>
>> I corrected the AsciiDoc source. The output looks much better now.
>> 
>> Is the CMS currently down? I can't access it.
>
>It seems to be up again right now, though I didn't login (I don't have the credentials on my work laptop).
>
>Mark

You're right. The CMS is back again. So I updated the German and English fbcache docs. Please have a look.

Martin

[Firebird-docs] [FirebirdSQL/firebird-documentation] a7696d: Wrong date at title section (fbcache, fbcache-de).

[Martin K. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: a7696d78cf3f91f19558b06926d4fd53e6ef4d3b
      https://github.com/FirebirdSQL/firebird-documentation/commit/a7696d78cf3f91f19558b06926d4fd53e6ef4d3b
  Author: Martin Köditz <mar...@it...>
  Date:   2020-05-28 (Thu, 28 May 2020)

  Changed paths:
    M src/docs/asciidoc/de/firebirddocs/fbcache/firebird-fbcache.adoc
    M src/docs/asciidoc/en/firebirddocs/fbcache/firebird-fbcache.adoc

  Log Message:
  -----------
  Wrong date at title section (fbcache, fbcache-de).

Re: [Firebird-docs] Conversion of fbcache-de

[Mark R. <ma...@la...>]

On 2020-05-28 10:35, Köditz wrote:
>>> Hi Mark,
>>> 
>>> thank you for the feedback. I did the conversion with help of Pandoc.
>> 
>> Pandoc is not my tool of choice for the conversion. I have selected 
>> Docbookrx and implemented a number of customizations for it. For the 
>> sake of consistency of output, I think it is better >that a single 
>> method of conversion is used.
>> 
>>> I will correct it. Now I know what to look for.
>> 
>> Thanks.
>> 
>> Mark
> 
> Well, I tried to use Docbookrx, but got some errors. I will try it 
> again later.

Did you use the one from the firebird-modifications branch of 
https://github.com/mrotteveel/docbookrx ?

If you're working on Windows, I would recommend running it from within a 
WSL shell (eg Ubuntu from the Windows store).

> I corrected the AsciiDoc source. The output looks much better now.
> 
> Is the CMS currently down? I can't access it.

It seems to be up again right now, though I didn't login (I don't have 
the credentials on my work laptop).

Mark

Re: [Firebird-docs] Conversion of fbcache-de

[Köditz, M. <Mar...@it...>]

>> Hi Mark,
>> 
>> thank you for the feedback. I did the conversion with help of Pandoc.
>
>Pandoc is not my tool of choice for the conversion. I have selected Docbookrx and implemented a number of customizations for it. For the sake of consistency of output, I think it is better >that a single method of conversion is used.
>
>> I will correct it. Now I know what to look for.
>
>Thanks.
>
>Mark

Well, I tried to use Docbookrx, but got some errors. I will try it again later.

I corrected the AsciiDoc source. The output looks much better now.

Is the CMS currently down? I can't access it.

Regards
Martin

[Firebird-docs] [FirebirdSQL/firebird-documentation] 4e19a3: Migrated fbcache.xml to asciidoc

[Martin K. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: 4e19a32245719f660656d4bf652bf9e3e16c5298
      https://github.com/FirebirdSQL/firebird-documentation/commit/4e19a32245719f660656d4bf652bf9e3e16c5298
  Author: Martin Köditz <mar...@it...>
  Date:   2020-05-28 (Thu, 28 May 2020)

  Changed paths:
    A src/docs/asciidoc/en/firebirddocs/fbcache/firebird-fbcache.adoc

  Log Message:
  -----------
  Migrated fbcache.xml to asciidoc


  Commit: 39498c1ab1f06c902a59143e252b71b838c899be
      https://github.com/FirebirdSQL/firebird-documentation/commit/39498c1ab1f06c902a59143e252b71b838c899be
  Author: Martin Köditz <mar...@it...>
  Date:   2020-05-28 (Thu, 28 May 2020)

  Changed paths:
    M src/docs/asciidoc/de/firebirddocs/fbcache/firebird-fbcache.adoc

  Log Message:
  -----------
  Reformatted asciiDoc of fbcache (German)


Compare: https://github.com/FirebirdSQL/firebird-documentation/compare/86161a3d073b...39498c1ab1f0

Re: [Firebird-docs] Conversion of fbcache-de

[Mark R. <ma...@la...>]

On 2020-05-28 08:38, Köditz wrote:
> Hi Mark,
> 
> thank you for the feedback. I did the conversion with help of Pandoc.

Pandoc is not my tool of choice for the conversion. I have selected 
Docbookrx and implemented a number of customizations for it. For the 
sake of consistency of output, I think it is better that a single method 
of conversion is used.

> I will correct it. Now I know what to look for.

Thanks.

Mark

Re: [Firebird-docs] Conversion of fbcache-de

[Köditz, M. <Mar...@it...>]

> Hi Mark,
>
> thank you for the feedback. I did the conversion with help of Pandoc. I will correct it. Now I know what to look for.
>
> Can we put an example excerpt in the docwriting howto? I think that would help any translator. And we will get a uniform structure.
>
> Regards
> Martin

Well, I didn't recognize that there is already a part for translators (12.1.3. Translator’s notices in AsciiDoc). So please ignore my last remark.

Regards
Martin 

Re: [Firebird-docs] Conversion of fbcache-de

[Köditz, M. <Mar...@it...>]

Hi Mark,

thank you for the feedback. I did the conversion with help of Pandoc. I will correct it. Now I know what to look for.

Can we put an example excerpt in the docwriting howto? I think that would help any translator. And we will get a uniform structure.

Regards
Martin

-----Ursprüngliche Nachricht-----
Von: Mark Rotteveel [mailto:ma...@la...] 
Gesendet: Mittwoch, 27. Mai 2020 20:33
An: fir...@li...
Betreff: Re: [Firebird-docs] Conversion of fbcache-de

On 27-05-2020 10:57, Köditz, Martin wrote:
> Hello,
> 
> this is for your information.
> 
> I converted my first doc to asciiDoc: fbcache-de. I think everything 
> is fine. I already uploaded the PDF and the HTML output.
> 
> Please feel free to give me some feedback.

In general, it looks good to me. I have three remarks.

1) The syntax of the author list of asciidoc does not formally support comments like `(deutsche Übersetzung)` in

```
Norman Dunbar; Martin Köditz (deutsche Übersetzung) ```

The syntax is something like:

<firstname> [<middlename>] [<lastname>] ['<'<emailaddress>'>']

As a result, the parser now considers `Martin Köditz (deutsche Übersetzung)` entirely as firstname (insert the {firstname_2} attribute in a document to see this). I would recommend just leaving the `(deutsche Übersetzung)` part out, and optionally add a preface before `toc::[]` to clarify.

3) Don't forget to add yourself to the fbcache-license section. See also:

-
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-asciidoc-copyrights-translator
-
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-copyrights-pdl-howto

3) I noticed an oddity in the transformation in section fbcache-mon-io-stats. The title of the formalpara of the xml should have been transformed as `.MONS$STAT_ID`, but it is now `*MONS$STAT_ID.*`. 
Did you manually change that?

The `.<text>` is the general way to add titles to objects (in this case to a paragraph), and is the equivalent of formalpara in the old XML when before a parapgraph. Just using bold emphasis as a replacement in such a a usecase is the 'wrong' semantic information.

As an improvement I would recommend to use a description list[1] for this.

  [1]: https://asciidoctor.org/docs/user-manual/#description-list

For example

```
*MONS$STAT_ID.*

Die Statistik-ID.

*MONS$STAT_GROUP.*

Die statistische Gruppe. Statistiken werden in folgende Gruppen unterteilt:

* 0: Die Datenbank als Ganzes.
* ...
```

Would then change to

```
MONS$STAT_ID::
Die Statistik-ID.

MONS$STAT_GROUP::
Die statistische Gruppe.
Statistiken werden in folgende Gruppen unterteilt:
+
* 0: Die Datenbank als Ganzes.
* ...
```

(use `+` to 'link' following paragraphs or other blocks to the same listitem).


> https://firebirdsql.org/file/documentation/html/de/firebirddocs/fbcache/firebird-fbcache-de.html

The title images were missing. I have fixed this by uploading the images 
folder of the build output (build/docs/asciidoc/html/de/images) to 
file/documentation/html/de.

> https://firebirdsql.org/file/documentation/pdf/de/firebirddocs/fbcache/firebird-fbcache-de.pdf
> 
> If you like I can also convert the English version.

If you have the time, that would be appreciated. Thanks!

I will ask Sergey to add redirects this weekend.

Mark
-- 
Mark Rotteveel


_______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Re: [Firebird-docs] Conversion of fbcache-de

[Mark R. <ma...@la...>]

On 27-05-2020 10:57, Köditz, Martin wrote:
> Hello,
> 
> this is for your information.
> 
> I converted my first doc to asciiDoc: fbcache-de. I think everything is 
> fine. I already uploaded the PDF and the HTML output.
> 
> Please feel free to give me some feedback.

In general, it looks good to me. I have three remarks.

1) The syntax of the author list of asciidoc does not formally support 
comments like `(deutsche Übersetzung)` in

```
Norman Dunbar; Martin Köditz (deutsche Übersetzung)
```

The syntax is something like:

<firstname> [<middlename>] [<lastname>] ['<'<emailaddress>'>']

As a result, the parser now considers `Martin Köditz (deutsche 
Übersetzung)` entirely as firstname (insert the {firstname_2} attribute 
in a document to see this). I would recommend just leaving the 
`(deutsche Übersetzung)` part out, and optionally add a preface before 
`toc::[]` to clarify.

3) Don't forget to add yourself to the fbcache-license section. See also:

- 
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-asciidoc-copyrights-translator
- 
https://www.firebirdsql.org/file/documentation/html/en/firebirddocs/docwritehowto/firebird-docwriting-guide.html#docwritehowto-copyrights-pdl-howto

3) I noticed an oddity in the transformation in section 
fbcache-mon-io-stats. The title of the formalpara of the xml should have 
been transformed as `.MONS$STAT_ID`, but it is now `*MONS$STAT_ID.*`. 
Did you manually change that?

The `.<text>` is the general way to add titles to objects (in this case 
to a paragraph), and is the equivalent of formalpara in the old XML when 
before a parapgraph. Just using bold emphasis as a replacement in such a 
a usecase is the 'wrong' semantic information.

As an improvement I would recommend to use a description list[1] for this.

  [1]: https://asciidoctor.org/docs/user-manual/#description-list

For example

```
*MONS$STAT_ID.*

Die Statistik-ID.

*MONS$STAT_GROUP.*

Die statistische Gruppe. Statistiken werden in folgende Gruppen unterteilt:

* 0: Die Datenbank als Ganzes.
* ...
```

Would then change to

```
MONS$STAT_ID::
Die Statistik-ID.

MONS$STAT_GROUP::
Die statistische Gruppe.
Statistiken werden in folgende Gruppen unterteilt:
+
* 0: Die Datenbank als Ganzes.
* ...
```

(use `+` to 'link' following paragraphs or other blocks to the same 
listitem).


> https://firebirdsql.org/file/documentation/html/de/firebirddocs/fbcache/firebird-fbcache-de.html

The title images were missing. I have fixed this by uploading the images 
folder of the build output (build/docs/asciidoc/html/de/images) to 
file/documentation/html/de.

> https://firebirdsql.org/file/documentation/pdf/de/firebirddocs/fbcache/firebird-fbcache-de.pdf
> 
> If you like I can also convert the English version.

If you have the time, that would be appreciated. Thanks!

I will ask Sergey to add redirects this weekend.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] The single Page for the documentation outline

[Paul V. <pa...@vi...>]

Hello Alexey,

I didn't understand at first that that's what you wanted. A high-level ToC
for each document on the doc index page doesn't seem useful to me and
only clutters the page.

I think everbody knows what they can expect from:

- Release Notes
- Quick Start Guide
- Firebird Language Reference
- Nbackup guide
- Firebird's isql Interactive SQL tool

etc.

The per-document ToC only becomes interesting if you already decided
that you need that document. And then you'll open it anyway.

Cheers,
Paul

> Hello Mark,
> 
> Like that Page but with high level table of contents for each document.
> 
> Regards,
> Alexey Kovyazin
> 
> 
> ??, 27 ??? 2020 ?., 14:25 Mark Rotteveel <ma...@la...>:
> 
> > On 2020-05-27 09:43, Alexey Kovyazin (ak) wrote:
> > > Hello All,
> > >
> > > As you know, Firebird documentation contains a set of documents, and
> > > they are grouped in several pages, by the topic or type of documents,
> > > like Release Notes, etc.
> > >
> > > Should we consider build the overall list of the docs and put to the
> > > Documentation starting Page?
> > >
> > > It would be like a big outline. Not like a 100% organized
> > > documentation set, of co3, but better than current distributed
> > > structure.
> > >
> > > What do you think?
> >
> > I'm not sure what you mean. This sounds like what we already have at
> > https://firebirdsql.org/en/firebird-rdbms/, that page and its subpages
> > is that list as I see it.
> >
> > Mark
> >
> >
> > _______________________________________________
> > Firebird-docs mailing list
> > Fir...@li...
> > https://lists.sourceforge.net/lists/listinfo/firebird-docs
> >

Re: [Firebird-docs] The single Page for the documentation outline

[Alexey K. (ak) <ak...@ib...>]

Hello Mark,

Like that Page but with high level table of contents for each document.

Regards,
Alexey Kovyazin


ср, 27 мая 2020 г., 14:25 Mark Rotteveel <ma...@la...>:

> On 2020-05-27 09:43, Alexey Kovyazin (ak) wrote:
> > Hello All,
> >
> > As you know, Firebird documentation contains a set of documents, and
> > they are grouped in several pages, by the topic or type of documents,
> > like Release Notes, etc.
> >
> > Should we consider build the overall list of the docs and put to the
> > Documentation starting Page?
> >
> > It would be like a big outline. Not like a 100% organized
> > documentation set, of co3, but better than current distributed
> > structure.
> >
> > What do you think?
>
> I'm not sure what you mean. This sounds like what we already have at
> https://firebirdsql.org/en/firebird-rdbms/, that page and its subpages
> is that list as I see it.
>
> Mark
>
>
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>

Re: [Firebird-docs] The single Page for the documentation outline

[Mark R. <ma...@la...>]

On 2020-05-27 09:43, Alexey Kovyazin (ak) wrote:
> Hello All,
> 
> As you know, Firebird documentation contains a set of documents, and
> they are grouped in several pages, by the topic or type of documents,
> like Release Notes, etc.
> 
> Should we consider build the overall list of the docs and put to the
> Documentation starting Page?
> 
> It would be like a big outline. Not like a 100% organized
> documentation set, of co3, but better than current distributed
> structure.
> 
> What do you think?

I'm not sure what you mean. This sounds like what we already have at 
https://firebirdsql.org/en/firebird-rdbms/, that page and its subpages 
is that list as I see it.

Mark

Re: [Firebird-docs] The single Page for the documentation outline

[Paul V. <pa...@vi...>]

Hello Alexey,

> As you know, Firebird documentation contains a set of documents, and they
> are grouped in several pages, by the topic or type of documents, like
> Release Notes, etc.
>
> Should we consider build the overall list of the docs and put to the
> Documentation starting Page?

Absolutely. I never liked the way it is now. Before the move we had the index
on one page, with several category headers, which worked fine.

Furthermore, we saved huge amounts of vertical space by using one table
row per document, putting the (English) name in the first column and the
links to the various language versions in columns 2 and 3, like this:

[Name column]          |     HTML      |      PDF/other
--------------------------------------------------------------------

1.5 Quick Start Guide  |  en fr de pt  |  en fr de pt

2.0 Quick Start Guide  |  en de es pt  |  en de es pt

...

Worked perfectly, all on one page, with as little scrolling as possible.

Cheers,
Paul

Re: [Firebird-docs] The single Page for the documentation outline

[Köditz, M. <Mar...@it...>]

> Hello All,
>
> As you know, Firebird documentation contains a set of documents, and they are grouped in
> several pages, by the topic or type of documents, like Release Notes, etc.
>
> Should we consider build the overall list of the docs and put to the Documentation starting Page?
>
> It would be like a big outline. Not like a 100% organized documentation set, of co3, but better than current distributed structure.
>
> What do you think?
>
> Regards,
> Alexey Kovyazin

Hi Alexey,

do suggest some kind of big TOC? Yes, I would prefer it.

Regards
Martin

[Firebird-docs] Conversion of fbcache-de

[Köditz, M. <Mar...@it...>]

Hello,

this is for your information.

I converted my first doc to asciiDoc: fbcache-de. I think everything is fine. I already uploaded the PDF and the HTML output.

Please feel free to give me some feedback.

https://firebirdsql.org/file/documentation/html/de/firebirddocs/fbcache/firebird-fbcache-de.html
https://firebirdsql.org/file/documentation/pdf/de/firebirddocs/fbcache/firebird-fbcache-de.pdf

If you like I can also convert the English version.

Regards
Martin

[Firebird-docs] The single Page for the documentation outline

[Alexey K. (ak) <ak...@ib...>]

Hello All,

As you know, Firebird documentation contains a set of documents, and they
are grouped in several pages, by the topic or type of documents, like
Release Notes, etc.

Should we consider build the overall list of the docs and put to the
Documentation starting Page?

It would be like a big outline. Not like a 100% organized documentation
set, of co3, but better than current distributed structure.

What do you think?

Regards,
Alexey Kovyazin

Re: [Firebird-docs] First 'new' documents online

[Mark R. <ma...@la...>]

On 2020-05-27 08:37, Köditz wrote:
> Hi Mark,
> 
> well, I misunderstood the document's structure. I just looked for the
> switch 'asciidocHtml' which already creates some kind of 'chunked'
> document. In the docbuilding howto you can only see 'docbookHtml'. But
> now I know how to work with it.

The docbuilding howto also documents asciidocHtml: 
https://firebirdsql.org/file/documentation/html/en/firebirddocs/docbuildhowto/firebird-docbuilding-howto.html#docbuildhowto-building-output-docs

However, that doesn't produce chunked output.

> Since I already have CMS access I should be able to publish the docs
> by myself. Otherwise I will call for help.

Ok, that is fine.

However, there is more necessary than just publishing the new docs: I 
also need to coordinate with Sergey to add redirects from the old 
documents to the new documents (if only so bookmarks and published links 
elsewhere will continue to work and point to the new docs).

So if you publish new documents, let me know which, so I can set this 
up.

Mark

[Firebird-docs] [FirebirdSQL/firebird-documentation] 86161a: Converted fbcache-de to AsciiDoc. Corrected some t...

[Martin K. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/FirebirdSQL/firebird-documentation
  Commit: 86161a3d073b61c162276df3423fc777aa25dc33
      https://github.com/FirebirdSQL/firebird-documentation/commit/86161a3d073b61c162276df3423fc777aa25dc33
  Author: Martin Köditz <mar...@it...>
  Date:   2020-05-27 (Wed, 27 May 2020)

  Changed paths:
    A src/docs/asciidoc/de/firebirddocs/fbcache/firebird-fbcache.adoc

  Log Message:
  -----------
  Converted fbcache-de to AsciiDoc. Corrected some typos.

Re: [Firebird-docs] First 'new' documents online

[Köditz, M. <Mar...@it...>]

Hi Mark,

well, I misunderstood the document's structure. I just looked for the switch 'asciidocHtml' which already creates some kind of 'chunked' document. In the docbuilding howto you can only see 'docbookHtml'. But now I know how to work with it.

Since I already have CMS access I should be able to publish the docs by myself. Otherwise I will call for help.

Regards
Martin

Re: [Firebird-docs] First 'new' documents online

[Mark R. <ma...@la...>]

To avoid any chance of miscommunication and possible double work, could 
you let me know what document you are looking to translate, and how you 
want to approach this?

Mark

On 2020-05-26 15:17, Köditz wrote:
> Please, forget my previous Mail. I found everything in the new Docs.
> 
> But how can I create the chunked output?
> 
> Regards
> Martin
> 
> 
> 
>> Hi Mark,
>> 
>> I'd like to update the German docs. What do I have to do?
>> 
>> Regards
>> Martin
> 
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs

Re: [Firebird-docs] First 'new' documents online

[Mark R. <ma...@la...>]

On 2020-05-26 15:17, Köditz wrote:
> Please, forget my previous Mail. I found everything in the new Docs.
> 
> But how can I create the chunked output?

You can't create chunked output, that is something we 'lose' in the 
migration. That is also why, when migrating, I'm defining redirects from 
the old chunked html files to the new single page html file.

Mark

Re: [Firebird-docs] First 'new' documents online

[Mark R. <ma...@la...>]

On 2020-05-26 14:56, Köditz wrote:
> Hi Mark,
> 
> I'd like to update the German docs. What do I have to do?

I can do the initial conversion to asciidoc for existing German docs, 
and then you can take it from there.

However, playing devil's advocate: is investing time in translating the 
Docbuilding Howto and Docwriting Guide really worth the effort, wouldn't 
that be better invested in translating end-user documentation?

Also I'd like to raise the question: what to do with translated docs 
that aren't actively maintained? Keep them as-is and maybe delete them 
from the site, or convert and republish?

Mark

Re: [Firebird-docs] First 'new' documents online

[Norman D. <No...@du...>]

Hi Martin,

I don't believe that you can, currently, create chunked HTML with 
Asciidoctor. s Mark stated in his thread recently about Chunked HTML:

Asciidoctor does not support chunked HTML output (there is an 
experimental, third-party plugin, but that plugin is tied to a specific, 
out-of-date asciidoctor version).


HTH

Cheers,
Norm.


On 26/05/2020 14:17, Köditz, Martin wrote:
> Please, forget my previous Mail. I found everything in the new Docs.
> 
> But how can I create the chunked output?
> 
> Regards
> Martin
> 
> 
> 
>> Hi Mark,
>>
>> I'd like to update the German docs. What do I have to do?
>>
>> Regards
>> Martin
> 
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
> 


-- 
Norman Dunbar
Dunbar IT Consultants Ltd

Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG

Company Number: 05132767

Re: [Firebird-docs] First 'new' documents online

[Köditz, M. <Mar...@it...>]

Please, forget my previous Mail. I found everything in the new Docs.

But how can I create the chunked output?

Regards
Martin



> Hi Mark,
>
> I'd like to update the German docs. What do I have to do? 
> 
> Regards
> Martin