Menu
▾
▴
Re: [brlcad-devel] DocBook
|
From: Tom B. <tom...@gm...> - 2011-09-15 18:16:46
|
On Thu, Sep 15, 2011 at 11:56, brlcad <br...@ma...> wrote: ... > On Sep 15, 2011, at 09:12 AM, Clifford Yapp <cli...@gm...> wrote: ... > 1. It looks like the GNU FreeFonts are licensed with the GPL, with an > exemption for using the fonts in documents without making the documents > GPL. Sean, what's your take on that - is it OK to for us to include those? > > While it is probably okay for most of our immediate uses, I think it > unnecessarily complicates or even prohibits reuse elsewhere in the package > (non-documentation). I'd rather we not. There are lots of outstanding open ... The main reason I wanted to use the GNU freefonts is because of the large number of glyphs. I will now look at the DejaVu fonts and see how they work. The reason I think we should use a specific font is to ensure we can show ALL (or at least most) of the glyphs needed for math and special symbols. Then we can have a list of unicode numbers to reference the needed glyphs for db authors (and insist on ASCII source files to avoid editor inconsistencies--I'm finding several non-ascii characters that I can't see (many I can figure out from context) and may have to look at the pdf's produced to see what was intended. The validation is helping with that chore. > 2. I'm having trouble tracking down the offo-hyphenation license - seems to > be related to the LaTeX license, from what I've found so far. Sean, is that > acceptable? ... > From what I read, the offo-hyphenation sources are a mixture of Apache 2.0 > and BSD-style licensed content, so it should be fine to use. I think I see Cliff's problem with the offo suite. The Apache FOP page mentions that users have to check the licensing themselves. I have collected the offo source and will look into it further. I will not use it for BRL-CAD until we get a closer look. From what I can see so far part of the English hyphenation is restricted to non-commercial use (UK I believe). We will have to look at each language separately--especially Spanish since we have some es docs. Best, -Tom |