Hi Maren,
I talked with Chris this morning about how to set things up. But we
were mostly trialing, thinking and researching. So not decisions or
anything.
> Even the booktype server of flossmanuals works with automation.
> Using one of those would also have the advantage that, once set up,
>
Hi Miguel,
I think this is a GREAT advantage for the entire Inkscape project. It makes
all the sense of the world to help users do all the needed workarounds and,
if they want, help send funds to the project ($$) and/or a bug request on
Gitlab(is it at Gitlab really?).
Amazing. The more
I agree with Brynn. We should first focus in create the official/original
doc of Inkscape on Gitlab and then try to do this hard copy book to sell in
the inkscape store.
I just wanted to gather the opinions of you guys if more or less following
the index of a 3rd party material is a good idea or
Hi all,
oh, wow, I've just been offline for a couple of hours - wouldn't have
expected that, if finally someone gives the 'go' for a manual, there
would be such a huge echo (we've been discussing this on and off for a
/very/ long time already). That's just cool :D
Just some comments to various
>> And won't such a new book of tutorials have to be published? .
> Books done in Scribus can be "published" in a variety of ways,
Yes, I understand that. But I thought Victor was talking about a hardback
book,
like at the link he provided. That kind of book is hard to get published,
On Sat, 2017-04-29 at 07:19 -0600, brynn wrote:
> As far as I understand, all that's needed is an English translation
> of...well I
> can't find a link to the French version. Here's a link to whatever
> has been
> translated already:
>
> It's fine to pull content
> from properly licenced sources, imho, too.
>
> I disagree. This would create a tangle of licenses and attribution
> requirements that will make the contents less usable in/by other
> projects. We should remove the burden of attribution where possible.
It doesn't
I don't mean to slow anyone's roll here. But wouldn't it make more sense to
put
any kind of energy towards documentation into the much discussed, direly
needed,
user-focused, step by step manual? Rather than starting from scratch on a
whole
different kind of project?
There are many books
Am 29.04.2017 um 10:05 schrieb C R:
> I have requested access to the gitlab repo. Once allowed, I'll drop a
> Scribus document in there with a cover, and the master pages with some
> initial styling for the document. I'll also do a README file with an
> initial layout/contents proposal based on
