caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] LablGtk2-Ocaml-Tutorial (SooHyoung Oh) now on github
Date: Fri, 18 Dec 2015 23:12:57 +0100	[thread overview]
Message-ID: <20151218231257.Horde.vw7LFQSutZRpKbjhG9wTMp6@webmail.in-berlin.de> (raw)
In-Reply-To: <567478E8.8000705@freenet.de>

...ah, well.
Didn't noticed DocBook...

So the html looked so bad, because it was generated...

Did the conversion work?

I changed the links directly in the html-files.
Broken links now should be all corrected.

Will conversion work with that changed html?!


images still missing.


Ciao,
    Oliver



Zitat von "Mr. Herr" <misterherr@freenet.de> (Fri, 18 Dec 2015 22:21:44 +0100)

> I won't interfere
>
> The source is marked <meta name="GENERATOR" content="Modular DocBook  
> HTML Stylesheet
> Version 1.7">
> so my guess is conversion will work well.
>
> Max
>
> On 18.12.2015 22:14, Martin DeMello wrote:
>> I think it's worth converting to markdown (hopefully pandoc should  
>> be able to do
>> this) and then making changes to the markdown. I'll do this tonight  
>> if no one sends
>> in a pull request for it first.
>>
>> martin
>>
>> On Fri, Dec 18, 2015 at 12:20 PM, Mr. Herr <misterherr@freenet.de
>> <mailto:misterherr@freenet.de>> wrote:
>>
>>     On 18.12.2015 20:32, Oliver Bandel wrote:
>>     > Hello,
>>     >
>>     > I made the LablGtk2-Ocaml-Tutorial,
>>     > initially written by SooHyoung Oh,
>>     > available on github.
>>     >
>>     > I already corrected some of the links, which pointed to nirvana,
>>     > to point to the official laglgtk-docs.
>>     > Some more changes will follow, so that the other links to the  
>> lablgtk-API-docs
>>     > also will work.
>>     >
>>     > The tutorial is available here:
>>     >   https://github.com/klartext/lablgtk2-ocaml-Tutorial
>>     >
>>
>>     I just cloned it. Is the source for the html files lying around  
>> somewhere?
>>
>>     If not, should I just correct/enhance the html files?
>>
>>     Max
>>
>>
>>     --
>>     Caml-list mailing list.  Subscription management and archives:
>>     https://sympa.inria.fr/sympa/arc/caml-list
>>     Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>>     Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>>
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs




  reply	other threads:[~2015-12-18 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 19:32 Oliver Bandel
2015-12-18 20:20 ` Mr. Herr
2015-12-18 21:14   ` Martin DeMello
2015-12-18 21:21     ` Mr. Herr
2015-12-18 22:12       ` Oliver Bandel [this message]
2015-12-18 22:59         ` Martin DeMello
2015-12-19 21:43         ` Damien Guichard
2015-12-19 22:53           ` Oliver Bandel
2015-12-18 21:36     ` Oliver Bandel
2015-12-18 21:33   ` Oliver Bandel
2015-12-19  1:28 ` Oliver Bandel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151218231257.Horde.vw7LFQSutZRpKbjhG9wTMp6@webmail.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).