public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batmand-howto conversation
Date: Sun, 25 Jan 2009 16:15:40 +0100	[thread overview]
Message-ID: <200901251615.40954.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <200901230126.27298.sven.eckelmann@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]

On Friday 23 January 2009 01:26:18 Sven Eckelmann wrote:
[...]
> Hm, sounds interesting, but I see different problems. First thing is the
> different copyright. You specified GPL2 for the batman(-adv) documentation
> and Wesley released his stuff as CC-by-nc-sa-3.0. These licenses aren't
> compatible in the way that you relicense his work under the GPL2 [2], but
> you can ask him if he relicenses his work.
Ok, I asked him and he agreed.

> The second thing is that somebody has to rewrite it into XML Docbook. This
> isn't that bad but I will definitely not doing anything like that until
> somebody explained me why you are using a SGML Docbook tool to convert a
> XML docbook to your target format. When you try it on another distribution
> than debian etch/lenny you will propably receive an error (try for example
> one of our public accessible machines at tuc).
Pushed fix in a clone of your git repo and requested merge.

> And maybe somebody can answer the question what is the right way to do the
> conversation job? I found different references that their is/was some xsl
> stylesheet to convert them to pdf but I don't want to fiddle about xsltproc
> and different xsl paths on each plattform. I tried xmlto some time ago
> (small shell script which does all the xslt stuff for me), but the output
> was quite bad and it had problems with the images (hm, reminds me on the
> fact that the current way the images are handled inside batman-adv-doc is a
> hack too).
Seems to be better now. xmlto with fo output +fop isn't that bad. Their are 
problems with images when you try to generate pdf directly but generating ps 
and then pdf works fine. I read that renderx xep works better, but it is a 
commercial tool.

Regards,
	Sven


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-25 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 20:36 [B.A.T.M.A.N.] batmand-howto conversation Sven Eckelmann
2009-01-22 23:10 ` Simon Wunderlich
2009-01-23  0:26   ` Sven Eckelmann
2009-01-25 15:15     ` Sven Eckelmann [this message]
2009-01-25 20:14     ` Sven Eckelmann

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=200901251615.40954.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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