firebird-docs — chat stuff about documentation

Re: [Firebird-docs] Experimenting with asciidoc / asciidoctor

[Paul B. <pb...@ma...>]

Mark,

Thats very smart I like it.

Regards
Paul

> -----Original Message-----
> From: Mark Rotteveel [mailto:ma...@la...]
> Sent: 14 June 2018 16:05
> To: Chatter regarding Firebird documentation
> Subject: [Firebird-docs] Experimenting with asciidoc / asciidoctor
>
>
> I'm trying to modernize the build of the documentation by converting it
> to gradle (which should allow us to do away with manual setup and
> downloading of things, and may fix issues with more recent Java
> versions), but I got side-tracked into experimenting with asciidoc /
> asciidoctor (see https://asciidoctor.org/).
>
> I was wondering how people think about migrating from docbook to
> asciidoc. Asciidoc is an "almost plain text" format that is used a lot
> these days for documentation (as an example, Hibernate and Spring
> switched from docbook to asciidoc), as its markup is a lot simpler and
> allows for editing with basic tools and is even - relatively - readable
> without having rendered it to HTML or PDF. It has been based on docbook
> (as originally asciidoc was converted to docbook before actually rendering).
>
> Pros of asciidoc:
> - Simpler, could lower bar of entry for contributions
> - More readable
> - Wider support in tools
>
> Cons:
> - Some of the more semantic features of docbook are not supported by
> asciidoc (but we don't really use those AFAIK).
> - Tools for asciidoc are simpler (compared to - for example - XMLMind;
> might be a pro)
>
> Conversion could be done document by document (Spring did that), that
> will probably complicate the setup, but would allow for spreading out
> the conversion.
>
> I have converted two documents from docbook to asciidoc using
> https://github.com/asciidoctor/docbookrx, and fixed a number of obvious
> issues with features not supported by the converter. I haven't checked
> the documents fully, so it is possible some other things 'disappeared'
> or render incorrectly in this conversion. I have also enabled table of
> content rendering, otherwise all the defaults have been used (including
> default styles).
>
> The two HTML renderings can be found on
> https://mrotteveel.github.io/firebird-documentation/
>
> Sources are on
> https://github.com/mrotteveel/firebird-documentation/tree/asciidoc-conversion-experiment
>
> Specifically (linking to raw, because otherwise GitHub renders asciidoc
> files):
>
> https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/f
butil_isql.adoc

and

https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/wireprotoco
l.adoc

(switch extension to .xml to view the docbook sources)

Example of how GitHub renders it from the repository:
https://github.com/mrotteveel/firebird-documentation/blob/asciidoc-conversion-experiment/src/docs/firebirddocs/fbutil_isql.adoc
--
Mark Rotteveel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Re: [Firebird-docs] Experimenting with asciidoc / asciidoctor

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

On 15-6-2018 11:26, Alexey Kovyazin wrote:
> Hello,
> 
> I like the result - html docs looks really cool.
> Also, I think it is more suitable for the translation.
> 
> Do you have PDF version to take a look at?

I have now also added PDF versions on 
https://mrotteveel.github.io/firebird-documentation/ (you may need to do 
a hard refresh due to caching). Again, this is just default without any 
Firebird specific styling, etc.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Experimenting with asciidoc / asciidoctor

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

Hello,

I like the result - html docs looks really cool.
Also, I think it is more suitable for the translation.

Do you have PDF version to take a look at?

Regards,
Alexey Kovyazin
IBSurgeon


On 14.06.2018 17:04, Mark Rotteveel wrote:
> I'm trying to modernize the build of the documentation by converting 
> it to gradle (which should allow us to do away with manual setup and 
> downloading of things, and may fix issues with more recent Java 
> versions), but I got side-tracked into experimenting with asciidoc / 
> asciidoctor (see https://asciidoctor.org/).
>
> I was wondering how people think about migrating from docbook to 
> asciidoc. Asciidoc is an "almost plain text" format that is used a lot 
> these days for documentation (as an example, Hibernate and Spring 
> switched from docbook to asciidoc), as its markup is a lot simpler and 
> allows for editing with basic tools and is even - relatively - 
> readable without having rendered it to HTML or PDF. It has been based 
> on docbook (as originally asciidoc was converted to docbook before 
> actually rendering).
>
> Pros of asciidoc:
> - Simpler, could lower bar of entry for contributions
> - More readable
> - Wider support in tools
>
> Cons:
> - Some of the more semantic features of docbook are not supported by 
> asciidoc (but we don't really use those AFAIK).
> - Tools for asciidoc are simpler (compared to - for example - XMLMind; 
> might be a pro)
>
> Conversion could be done document by document (Spring did that), that 
> will probably complicate the setup, but would allow for spreading out 
> the conversion.
>
> I have converted two documents from docbook to asciidoc using 
> https://github.com/asciidoctor/docbookrx, and fixed a number of 
> obvious issues with features not supported by the converter. I haven't 
> checked the documents fully, so it is possible some other things 
> 'disappeared' or render incorrectly in this conversion. I have also 
> enabled table of content rendering, otherwise all the defaults have 
> been used (including default styles).
>
> The two HTML renderings can be found on 
> https://mrotteveel.github.io/firebird-documentation/
>
> Sources are on 
> https://github.com/mrotteveel/firebird-documentation/tree/asciidoc-conversion-experiment
>
> Specifically (linking to raw, because otherwise GitHub renders 
> asciidoc files):
>
> https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/fbutil_isql.adoc 
>
>
> and
>
> https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/wireprotocol.adoc 
>
>
> (switch extension to .xml to view the docbook sources)
>
> Example of how GitHub renders it from the repository: 
> https://github.com/mrotteveel/firebird-documentation/blob/asciidoc-conversion-experiment/src/docs/firebirddocs/fbutil_isql.adoc

[Firebird-docs] Experimenting with asciidoc / asciidoctor

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

I'm trying to modernize the build of the documentation by converting it 
to gradle (which should allow us to do away with manual setup and 
downloading of things, and may fix issues with more recent Java 
versions), but I got side-tracked into experimenting with asciidoc / 
asciidoctor (see https://asciidoctor.org/).

I was wondering how people think about migrating from docbook to 
asciidoc. Asciidoc is an "almost plain text" format that is used a lot 
these days for documentation (as an example, Hibernate and Spring 
switched from docbook to asciidoc), as its markup is a lot simpler and 
allows for editing with basic tools and is even - relatively - readable 
without having rendered it to HTML or PDF. It has been based on docbook 
(as originally asciidoc was converted to docbook before actually rendering).

Pros of asciidoc:
- Simpler, could lower bar of entry for contributions
- More readable
- Wider support in tools

Cons:
- Some of the more semantic features of docbook are not supported by 
asciidoc (but we don't really use those AFAIK).
- Tools for asciidoc are simpler (compared to - for example - XMLMind; 
might be a pro)

Conversion could be done document by document (Spring did that), that 
will probably complicate the setup, but would allow for spreading out 
the conversion.

I have converted two documents from docbook to asciidoc using 
https://github.com/asciidoctor/docbookrx, and fixed a number of obvious 
issues with features not supported by the converter. I haven't checked 
the documents fully, so it is possible some other things 'disappeared' 
or render incorrectly in this conversion. I have also enabled table of 
content rendering, otherwise all the defaults have been used (including 
default styles).

The two HTML renderings can be found on 
https://mrotteveel.github.io/firebird-documentation/

Sources are on 
https://github.com/mrotteveel/firebird-documentation/tree/asciidoc-conversion-experiment

Specifically (linking to raw, because otherwise GitHub renders asciidoc 
files):

https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/fbutil_isql.adoc

and

https://raw.githubusercontent.com/mrotteveel/firebird-documentation/asciidoc-conversion-experiment/src/docs/firebirddocs/wireprotocol.adoc

(switch extension to .xml to view the docbook sources)

Example of how GitHub renders it from the repository: 
https://github.com/mrotteveel/firebird-documentation/blob/asciidoc-conversion-experiment/src/docs/firebirddocs/fbutil_isql.adoc
-- 
Mark Rotteveel

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

[Nico L. <nl...@mn...>]

Hi Mark and Frank, thanks again for Your feedback.
I will go thru and fix it. 
Kind Regards

Re: [Firebird-docs] Can contribute

[Dumitru <dum...@ya...>]

 Hello Mark,
I don't insist for access to upload.I agree with you.If you start to updating documentation for “normal” writers (not guest), I think it is a good opportunity for translating it in Romanian too.


    On Wednesday, April 25, 2018, 10:24:47 AM GMT+3, Mark Rotteveel <ma...@la...> wrote:  
 
 On 24-4-2018 21:44, Norman Dunbar wrote:
> I thought the VPN was ancient history? Am I wrong?

No you aren't, I just assumed SSH access was meant.

> I remember writing the docs for how to use it, and then it got changed 
> so that we simply provide an ssh public key (but not dsa!) and that 
> gives us access to sftp our documents directly to the web site. I need 
> to write a new set of "how to upload" manuals!

I don't think everyone should have access to upload manuals. For one it 
throws up additional risks and barriers: uploading to the site should 
only be done by trusted users (or even better: it should be an automatic 
CI build that does it), and expecting all contributors to be able to 
upload then either means we trust all contributors, or that we only 
accept contributions from trusted users.

In other words, we need to have discern between types of contributors: 
eg 'trusted' contributors ('coordinators'?) can upload documentation, 
all other contributors just need to create pull requests on GitHub.

Note: I think we already work this way, but given this document 
https://www.firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/fbvpn.html 
we may be giving the incorrect expression that all contributors need to 
be able to do this.

As an aside, we need to look at updating all the documentation under 
"Manuals for Firebird Docwriters" on the site to be in line with the 
brave new world of GitHub.

Mark
-- 
Mark Rotteveel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs
  

Re: [Firebird-docs] Can contribute

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

On 24-4-2018 21:44, Norman Dunbar wrote:
> I thought the VPN was ancient history? Am I wrong?

No you aren't, I just assumed SSH access was meant.

> I remember writing the docs for how to use it, and then it got changed 
> so that we simply provide an ssh public key (but not dsa!) and that 
> gives us access to sftp our documents directly to the web site. I need 
> to write a new set of "how to upload" manuals!

I don't think everyone should have access to upload manuals. For one it 
throws up additional risks and barriers: uploading to the site should 
only be done by trusted users (or even better: it should be an automatic 
CI build that does it), and expecting all contributors to be able to 
upload then either means we trust all contributors, or that we only 
accept contributions from trusted users.

In other words, we need to have discern between types of contributors: 
eg 'trusted' contributors ('coordinators'?) can upload documentation, 
all other contributors just need to create pull requests on GitHub.

Note: I think we already work this way, but given this document 
https://www.firebirdsql.org/file/documentation/reference_manuals/user_manuals/html/fbvpn.html 
we may be giving the incorrect expression that all contributors need to 
be able to do this.

As an aside, we need to look at updating all the documentation under 
"Manuals for Firebird Docwriters" on the site to be in line with the 
brave new world of GitHub.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Can contribute

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

I thought the VPN was ancient history? Am I wrong?

I remember writing the docs for how to use it, and then it got changed so that we simply provide an ssh public key (but not dsa!) and that gives us access to sftp our documents directly to the web site. I need to write a new set of "how to upload" manuals!

Correct me please, if I'm wrong - it wouldn't be the first time! 


Cheers,
Norm.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [Firebird-docs] Can contribute

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

On 24-4-2018 16:52, Dumitru via Firebird-docs wrote:
> Hello Paul,
> 
> I do not have preferences for documentation to translate. The firefird 
> community in Romania is underdeveloped. The site http://firebirdsql.ro/ 
> does not work for me. In most cases it is closed. And when it works, 90% 
> is in English. I think to start with the Romanian translation and then 
> creating a firebird forum in romania to promote firebird in Romania.
> 
> 
> I've read the 
> https://www.firebirdsql.org/en/reference-manuals/#docwriters 
> instructions. I have already installed WinCvs and XMLmind DocBook 
> Editor. For now I waiting a vpn account and other stuff for start.

You don't need a VPN account to write documentation. That is only 
necessary for uploading documentation to the Firebird website, and to be 
honest I don't think each and every documentation contributor needs that.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] Can contribute

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

The most important is documentation translation in the first stage

Firebird romanian forum is here

https://groups.google.com/forum/#!forum/firebird-ro

I will take care about firebirdsql.ro , now is moving between hosts and
also we needed translators :)

The best way it will be to have an official way to translate the site and
to add that content in the main firebirdsql.org cms



On Tue, Apr 24, 2018 at 5:52 PM, Dumitru via Firebird-docs <
fir...@li...> wrote:

> Hello Paul,
>
> I do not have preferences for documentation to translate. The firefird
> community in Romania is underdeveloped. The site http://firebirdsql.ro/
> does not work for me. In most cases it is closed. And when it works, 90% is
> in English. I think to start with the Romanian translation and then
> creating a firebird forum in romania to promote firebird in Romania.
>
>
> I've read the https://www.firebirdsql.org/en/reference-manuals/#docwriters
> instructions. I have already installed WinCvs and XMLmind DocBook Editor.
> For now I waiting a vpn account and other stuff for start.
>
>
>
> On Tuesday, April 24, 2018, 5:23:11 PM GMT+3, Paul Vinkenoog <
> pa...@vi...> wrote:
>
>
> Hello Dumitru,
>
> > I can try to contribute to FireBird with translation from
> Russian/English to Romanian.
> > If you interesting, please send me a reply.
>
> Yes, that would be much appreciated!
>
> Do you already have an idea which manual you want to translate first?
> I guess you know the Romanian Firebird community and can decide what's
> most wanted/needed.
>
> Also, are you familiar with our setup of the manual module (recently
> moved to https://github.com/FirebirdSQL/firebird-documentation) and
> working with DocBook sources? The latter shouldn't be difficult BTW,
> even if you are new to it.
>
> Hope to hear from you soon! Please keep following this list, as this
> is where we discuss doc matters and help each other - even if it's
> VERY quiet sometimes ;-)
>
> Cheers,
> Paul Vinkenoog
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>
>

Re: [Firebird-docs] Can contribute

[Dumitru <dum...@ya...>]

 Hello Paul,
I donot have preferences for documentation to translate. The firefirdcommunity in Romania is underdeveloped. The sitehttp://firebirdsql.ro/ does not work for me. In most cases it isclosed. And when it works, 90% is in English. I think to start withthe Romanian translation and then creating a firebird forum inromania to promote firebird in Romania.




I'veread the https://www.firebirdsql.org/en/reference-manuals/#docwritersinstructions. I have already installed WinCvs and XMLmind DocBookEditor. For now I waiting a vpn account and other stuff for start.



    On Tuesday, April 24, 2018, 5:23:11 PM GMT+3, Paul Vinkenoog <pa...@vi...> wrote:  
 
 Hello Dumitru,

> I can try to contribute to FireBird with translation from Russian/English to Romanian.
> If you interesting, please send me a reply.

Yes, that would be much appreciated!

Do you already have an idea which manual you want to translate first?
I guess you know the Romanian Firebird community and can decide what's
most wanted/needed.

Also, are you familiar with our setup of the manual module (recently
moved to https://github.com/FirebirdSQL/firebird-documentation) and
working with DocBook sources? The latter shouldn't be difficult BTW,
even if you are new to it.

Hope to hear from you soon! Please keep following this list, as this
is where we discuss doc matters and help each other - even if it's
VERY quiet sometimes ;-)

Cheers,
Paul Vinkenoog

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs
  

Re: [Firebird-docs] Can contribute

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

Hello Dumitru,

> I can try to contribute to FireBird with translation from Russian/English to Romanian.
> If you interesting, please send me a reply.

Yes, that would be much appreciated!

Do you already have an idea which manual you want to translate first?
I guess you know the Romanian Firebird community and can decide what's
most wanted/needed.

Also, are you familiar with our setup of the manual module (recently
moved to https://github.com/FirebirdSQL/firebird-documentation) and
working with DocBook sources? The latter shouldn't be difficult BTW,
even if you are new to it.

Hope to hear from you soon! Please keep following this list, as this
is where we discuss doc matters and help each other - even if it's
VERY quiet sometimes ;-)

Cheers,
Paul Vinkenoog

[Firebird-docs] Can contribute

[Dumitru <dum...@ya...>]

 Hello,

I can try to contribute to FireBird with translation from Russian/English to Romanian.
If you interesting, please send me a reply.

Thank you.

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

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

On 7-4-2018 10:37, Nico Latzer wrote:
> 
>   Hi Mark, many thanks for Your feedback. i made my first draft of example application and documentation available under
> http://home.mnet-online.de/nl/fb/

Thanks.

As already indicated by Frank, it would be better to use fdb (or 
pyfirebirdsql), kinterbasdb is no longer actively maintained since 2007.

Some comments

- Your style is conversational which is helpful for an introduction, but 
I think the stream-of-thought parts need to be a more compact and less 
'personal'.
- I think that as a result of the stream-of-thought, some sections raise 
questions, but don't explicitly answer them, or posit a conclusion, 
without explaining it (eg in Choosing our Transaction Handling)
- Add some more in-depth technical details on what the code does (or add 
some references to documentation)
- The code on page 3/4 has an SQL injection bug, specifically: 
"lower(name) like '%%%s%%'" % quote(flt)
Either avoid the SQL injection or specifically point this out with a warning

Some language nitpicking
- i should be I
- Don't capitalize words that shouldn't be capitalized in English

I haven't carefully reviewed the python code, as I haven't actively done 
things with Python for years.

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

[Frank Schlottmann-G. <fr...@sc...>]

Am 07.04.2018 um 10:37 schrieb Nico Latzer:
> 
>   Hi Mark, many thanks for Your feedback. i made my first draft of example application and documentation available under
> http://home.mnet-online.de/nl/fb/

Nice, but I would prefer to see fdb instead of the quite outdated 
kinterbasdb:

eg.:

import fdb
conn=None

modifyTPB=fdb.ISOLATION_LEVEL_READ_COMMITED #write +read_committed +wait
readOnlyTPB=fdb.ISOLATION_LEVEL_READ_COMMITED_RO
...

conn = fdb.connect('examples','SYSDBA','masterkey')



kind regards
Frank
-- 
"Fascinating creatures, phoenixes, they can carry immensely heavy loads,
   their tears have healing powers and they make highly faithful pets."
       - J.K. Rowling

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

[Nico L. <nl...@mn...>]

 Hi Mark, many thanks for Your feedback. i made my first draft of example application and documentation available under 
http://home.mnet-online.de/nl/fb/ 





On Wed, 28 Mar 2018 15:22:14 +0200
Mark Rotteveel <ma...@la...> wrote:

> On 8-3-2018 20:22, Nico Latzer wrote:
> > Hello all, yesterday i browsed a little bit thru the newly published "FB 3 Developers Guide",
> > and i found it very valuable and impressivly well done. NOw my question is, does it make sense to
> > provide an additional application example based on  "Python Tkinter"? if so i would be
> > pleased to take this part and try my best to reach your level. Please let me know your thoughts
> 
> For some reason your message didn't end up on the list until now, but I 
> think that would be a great idea!
> 
> Mark
> -- 
> Mark Rotteveel

Re: [Firebird-docs] TEST:: Dumitru Rubey

[Helen B. <he...@ii...>]

I wrote:


> Dumitru has indicated he is willing to translate some documentation to
> Romanian.  He has been trying to subscribe and has not had any kind of
> feedback.  Of course, under the privacy restrictions imposed last year
> by Sourceforge, I can no longer check the subscriber list.

> Dumitru, please reply to this message if you see it.

Dumitru is seeing the messages now and will post when he is ready.

Dumitru, there might be a short delay, as the first message from every
new subscriber is held for moderation.  I should receive a
notification but I will watch from the admin interface for a few days,
in case this Sourceforge hiccup is permanent.

Helen

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

[Helen B. <he...@ii...>]

Mark wrote:

> On 8-3-2018 20:22, Nico Latzer wrote:
>> Hello all, yesterday i browsed a little bit thru the newly published "FB 3 Developers Guide",
>> and i found it very valuable and impressivly well done. NOw my question is, does it make sense to
>> provide an additional application example based on  "Python Tkinter"? if so i would be
>> pleased to take this part and try my best to reach your level. Please let me know your thoughts

> For some reason your message didn't end up on the list until now, but I
> think that would be a great idea!

Certainly something odd was going on.  In fact, I released this
message only yesterday, having had no notifications from SF about it.
On going into the Admin interface, I found the forwarding address for
admin had been deleted and there was a small pile of SPAM there, along
with Nico's message for moderation.

Maybe we need to think about a migration to Google groups or Yahoo
groups for this list. We can no longer get the subscriber list but I
have an archive going back to Noah's flood.  It should not be too hard
to assemble a migration list.

Helen

Re: [Firebird-docs] FB firebird-3-developer-s-guide-relea

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

On 8-3-2018 20:22, Nico Latzer wrote:
> Hello all, yesterday i browsed a little bit thru the newly published "FB 3 Developers Guide",
> and i found it very valuable and impressivly well done. NOw my question is, does it make sense to
> provide an additional application example based on  "Python Tkinter"? if so i would be
> pleased to take this part and try my best to reach your level. Please let me know your thoughts

For some reason your message didn't end up on the list until now, but I 
think that would be a great idea!

Mark
-- 
Mark Rotteveel

Re: [Firebird-docs] TEST:: Dumitru Rubey

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

On 27-3-2018 21:04, Helen Borrie wrote:
> 
> Dumitru has indicated he is willing to translate some documentation to
> Romanian.  He has been trying to subscribe and has not had any kind of
> feedback.  Of course, under the privacy restrictions imposed last year
> by Sourceforge, I can no longer check the subscriber list.
> 
> Dumitru, please reply to this message if you see it.

I wonder if these are still hickups from their datacenter migration. Not 
sure if it was stuck in moderation or really just delayed, but that 
email from Nico Latzer dated 8th of March also just showed up yesterday.

Mark
-- 
Mark Rotteveel

[Firebird-docs] TEST:: Dumitru Rubey

[Helen B. <he...@ii...>]

Dumitru has indicated he is willing to translate some documentation to
Romanian.  He has been trying to subscribe and has not had any kind of
feedback.  Of course, under the privacy restrictions imposed last year
by Sourceforge, I can no longer check the subscriber list.

Dumitru, please reply to this message if you see it.

Helen

Re: [Firebird-docs] German langref25 completed

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

Hi Martin,

> yes, I also created the HMTL output. Do you want the zipped version?

Yes, please. I'll place it online tonight.

Cheers,
Paul

Re: [Firebird-docs] German langref25 completed

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

Hi Paul,

yes, I also created the HMTL output. Do you want the zipped version?

Regards
Martin

-----Ursprüngliche Nachricht-----
Von: Paul Vinkenoog [mailto:pa...@vi...] 
Gesendet: Montag, 12. März 2018 13:38
An: Chatter regarding Firebird documentation <fir...@li...>
Betreff: Re: [Firebird-docs] German langref25 completed

Martin Köditz wrote:

> I've just finished the translation of the last chapter. We have a complete German language reference now. I sent Alexey the pdf. The source code is on Github.

That's great, Martin! Thanks for all your hard work. I see the PDF isn't online yet, but I'll keep an eye on it.

BTW, did you also produce an HTML set?

Cheers,
Paul Vinkenoog

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________
Firebird-docs mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-docs

Re: [Firebird-docs] German langref25 completed

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

Hi all,

> > I've just finished the translation of the last chapter. We have a complete German language reference now. I sent Alexey the pdf. The source code is on Github.
>
> That's great, Martin! Thanks for all your hard work. I see the PDF isn't online yet, but I'll keep an eye on it.

Online now; looks good! :-)

Cheers,
Paul

Re: [Firebird-docs] German langref25 completed

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

Martin Köditz wrote:

> I've just finished the translation of the last chapter. We have a complete German language reference now. I sent Alexey the pdf. The source code is on Github.

That's great, Martin! Thanks for all your hard work. I see the PDF isn't online yet, but I'll keep an eye on it.

BTW, did you also produce an HTML set?

Cheers,
Paul Vinkenoog