Hi ugajin, I'm not quite following what your concerns are. You want the html pages to be available for users, but you don't want the users to download them? I guess you could upload the tutorial to the InkSpace Tutorial category. And then I think it's fairly typical to have a readme file together with an extension or any other program. Maybe the readme file could have a link to the tutorial?

All best, brynn

__________________________________________________

From: ugajin Sent: Sunday, July 24, 2016 4:11 AM To: maren@...68... Cc: inkscape-docs Subject: Re: [Inkscape-docs] Help please?

Hi Maren,

Yes, I am referring to the html documentation; specifically the 'tutorial.html and 'examples.html' pages. The viewBox... extension files, together with the readMe file will be downloadable. The structure that I have made, seems to work OK, and I would like to keep links in the readMe.html file for the example.html and tutorial.html pages, so ideally these pages need to be hosted, but not by me.

I have considered building a local structure, and adding the said supporting docs to the zip file. Indeed, this had been my initial approach, but as the supporting documentation grew, I began to have doubts, and to ask, why do it this way? Including them in the zip file would no doubt 'work', but it is not the approach that I would like to take.

Further, why should anyone have, or want to download files that a) they may not want, and/or b) simply in order to access, and/or peruse them? I am not against anyone downloading them per-se (e.g. if they chose to do so) and, I am less worried about users breaking any relative links. I guess, I am simply not intending the supporting documents to be downloadable.

I don't think requesting more space is an answer.

Thanks for considering matters.

Kind regards.

-u

---- On Sat, 23 Jul 2016 23:59:28 +0000 <maren@...68...> wrote ----

Hi u,

I'm not entirely sure which specific documents you are referring to.

If you mean external documents, that you don't control (the manual, for example), then you could just add a link into the README file and / or into the description text for the extension.

If you mean your own html documents, why don't you just add them to the zip file? You could make a subfolder 'documentation' or similar, if you like.

If you need more space for uploading everything, this list is the place to request it.

Kind Regards, Maren

I have been working on a new extension called viewBox..., which is awaiting upload to the Inkscape addons gallery. It is available for preview here: http://ugajin.co.uk/sketchbooks/viewBox/viewBox/viewBox.html, with a bunch of supporting documents.

The problem is what to do with the supporting documents (I do not want to host them on ugajin.co.uk). Whilst, I may upload the extension files, without the supporting documents and/or providing a link to them, this seems to me to be the wrong approach.

The viewBox and its sibling attributes are one of those things, which are not be easily accessed in Inkscape, and those cutting their teeth writing SVG using Inkscape may benefit from the supporting documentation.

Thank you for considering matters.

-u

---

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev

_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

They would be downloadable. But they wouldn't have to be downloaded for the user to read them. The visitor/user would have the choice whether to download or not. They'll be displayed in a new window, once the visitor clicks to see the full size.

Oh....well actually, I'm not sure if html files are allowed? But if you made them as an image, like a PNG file, then it would work like above.

I would have to test uploading an html file..... Hhm, I don't have any that I could use for testing. But I'll try and make one, to find out. Or maybe someone else knows already? I'll make one for testing, and if someone else hasn't already answered, by the time I finish, I'll tell you my results :-)

Is not having them downloadable, to prevent them from being edited, or used without permission?

All best, brynn

_____________________________________________

From: ugajin Sent: Sunday, July 24, 2016 3:13 PM To: Brynn Cc: maren@...68... ; inkscape-docs Subject: Re: [Inkscape-docs] Help please?

Hi Brynn

I do not want to include exercises.html and tutorial.html with the zip download. The (extension) zip will include a readMe.html file. If I upload the tutorial.html and/or exercises.html to the tutorial category, won't they still be downloadable?

I would like the tutorial, and ecercises to be readable, not downloadable.

I hope this makes sense.

Kind regards

-u

---- On Sun, 24 Jul 2016 16:41:05 +0000 Brynn<brynn@...78...> wrote ----

Hi ugajin, I'm not quite following what your concerns are. You want the html pages to be available for users, but you don't want the users to download them? I guess you could upload the tutorial to the InkSpace Tutorial category. And then I think it's fairly typical to have a readme file together with an extension or any other program. Maybe the readme file could have a link to the tutorial?

All best, brynn

__________________________________________________

From: ugajin Sent: Sunday, July 24, 2016 4:11 AM To: maren@...68... Cc: inkscape-docs Subject: Re: [Inkscape-docs] Help please?

Hi Maren,

Yes, I am referring to the html documentation; specifically the 'tutorial.html and 'examples.html' pages. The viewBox... extension files, together with the readMe file will be downloadable. The structure that I have made, seems to work OK, and I would like to keep links in the readMe.html file for the example.html and tutorial.html pages, so ideally these pages need to be hosted, but not by me.

I have considered building a local structure, and adding the said supporting docs to the zip file. Indeed, this had been my initial approach, but as the supporting documentation grew, I began to have doubts, and to ask, why do it this way? Including them in the zip file would no doubt 'work', but it is not the approach that I would like to take.

Further, why should anyone have, or want to download files that a) they may not want, and/or b) simply in order to access, and/or peruse them? I am not against anyone downloading them per-se (e.g. if they chose to do so) and, I am less worried about users breaking any relative links. I guess, I am simply not intending the supporting documents to be downloadable.

I don't think requesting more space is an answer.

Thanks for considering matters.

Kind regards.

-u

---- On Sat, 23 Jul 2016 23:59:28 +0000 <maren@...68...> wrote ----

Hi u,

I'm not entirely sure which specific documents you are referring to.

If you mean external documents, that you don't control (the manual, for example), then you could just add a link into the README file and / or into the description text for the extension.

If you mean your own html documents, why don't you just add them to the zip file? You could make a subfolder 'documentation' or similar, if you like.

If you need more space for uploading everything, this list is the place to request it.

Kind Regards, Maren

I have been working on a new extension called viewBox..., which is awaiting upload to the Inkscape addons gallery. It is available for preview here: http://ugajin.co.uk/sketchbooks/viewBox/viewBox/viewBox.html, with a bunch of supporting documents.

The problem is what to do with the supporting documents (I do not want to host them on ugajin.co.uk). Whilst, I may upload the extension files, without the supporting documents and/or providing a link to them, this seems to me to be the wrong approach.

The viewBox and its sibling attributes are one of those things, which are not be easily accessed in Inkscape, and those cutting their teeth writing SVG using Inkscape may benefit from the supporting documentation.

Thank you for considering matters.

-u

---

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev

_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

HTML can't really be rendered directly as it opens the website up to abuses which are hard to control. We have a way to embed svg files, but even these can only be enabled one by one by an admin and all svg files not 'embedded' will be shown in <img> tags and thus rendered by the browser without css and javascript support.

I'd upload a pdf if you have a document about some external resource (like an extension). We may have a way to have blogs (like the planet) on the website, so that could be a way if you have a blog.

But for ANY documentation or tutorial about inkscape that is useful enough, we should try and include it either in the docs project or the website. I'd be happy to see a collection of html tutorials on the website using the website's cms if we have the quality of submissions.

Best Regards, Martin Owens

On Mon, 2016-07-25 at 04:30 +0200, Sylvain Chiron wrote:

...

Is not having them downloadable, to prevent them from being edited, or used  without permission?

Well, I don't see what you could mean with ‘allowing to view a file but not to download it’. A file must be downloaded to be viewed, and then can be taken, copied, edited. You should only think about law and copyright if you have special wishes.

Whether the website provides an explicit ‘Download’ button or you use the ‘Save as…’ menu item of your browser when viewing, there's not much difference. -- Sylvain

---

---

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are  consuming the most bandwidth. Provides multi-vendor support for NetFlow,  J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

Ditto! ____________________________

From: ugajin Sent: Monday, July 25, 2016 7:37 AM To: Martin Owens Cc: Sylvain Chiron ; inkscape-docs@lists.sourceforge.net ; brynn@...78... Subject: Re: Re: [Inkscape-docs] Help please?

Hosting html tutorials on Inkscape.org sounds like a great idea.

Kind regards

-u

---- On Mon, 25 Jul 2016 05:42:27 +0000 Martin Owens <doctormo@...2...> wrote ----

HTML can't really be rendered directly as it opens the website up to abuses which are hard to control. We have a way to embed svg files, but even these can only be enabled one by one by an admin and all svg files not 'embedded' will be shown in <img> tags and thus rendered by the browser without css and javascript support.

I'd upload a pdf if you have a document about some external resource (like an extension). We may have a way to have blogs (like the planet) on the website, so that could be a way if you have a blog.

But for ANY documentation or tutorial about inkscape that is useful enough, we should try and include it either in the docs project or the website. I'd be happy to see a collection of html tutorials on the website using the website's cms if we have the quality of submissions.

Best Regards, Martin Owens

On Mon, 2016-07-25 at 04:30 +0200, Sylvain Chiron wrote:

...

Is not having them downloadable, to prevent them from being edited, or used without permission?

Well, I don't see what you could mean with ‘allowing to view a file but not to download it’. A file must be downloaded to be viewed, and then can be taken, copied, edited. You should only think about law and copyright if you have special wishes.

Whether the website provides an explicit ‘Download’ button or you use the ‘Save as…’ menu item of your browser when viewing, there's not much difference. -- Sylvain

---

---

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs------------------...

What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

Hello Everybody, Roy Torley here. Quick aside from the main topic. I just want to keep you in the loop that I haven't put in time yet to take care of copyleft details for my tutorial. It is on the to-do list, though. Working on Chapter 4, slowly but steadily.

I appreciate your keeping me in the conversation. I hope you all are having a pleasant summer.

Best wishes,

Roy Torley

Hi again, Regarding the possibility of html tutorials on the website, should a feature request "bug report" be made, to avoid losing the idea? Or is it something that's already coming down the road, and doesn't need a reminder? Or, when Martin said "I'd be happy to see a collection of html tutorials on the website using the website's cms if we have the quality of submissions. " does that mean using the Django editor?

Thanks, brynn

A couple of corrections for you Sylvain,

Copyleft - using copyright terms to REQUIRE that copies retain the same license no matter how it's modified or re-copied. GPL and Creative Commons Share-alike are copyleft. Apache, MIT and Creative Commons Attribution are not copyleft licences. Although all are open source and Free Software licenses.

About us, we didn't plan to copy your content at all, at least for the moment, but libre content is always appreciated.

We require permission to make copies for all content on the website. Because delivering content makes a copy upon each request. When you view a website's contents you are making a copy.

A link is ok though, and like you say it's easy enough to link. But it's more helpful I think to consider digesting good content into our docs rather than linking. Because we're more likely to maintain things centrally and be able to apply upgrades in visual appearance and translations.

I just added a link to your tutorial on the Inkscape wiki (there's probably not much restriction for it) — that wiki whose hundreds of dead links from years and incorrectly formatted contents really scare me —: http://wiki.inkscape.org/wiki/index.php/Tutorials_and_help#English_.2 8en.29

The wiki is dedicated to inkscape development. So tutorials about inkscape development (coding, website devel, writing docs) makes sense. But tutorials about how inkscape can be used should go on the website itself.

You can use the wiki to plan out or draft content though, as long as the intention is that it'll end up on our public facing website at some point.

Best Regards, Martin Owens

Le 02/08/2016 à 00:10, Martin Owens a écrit :

Copyleft - using copyright terms to REQUIRE that copies retain the same license no matter how it's modified or re-copied. GPL and Creative Commons Share-alike are copyleft. Apache, MIT and Creative Commons Attribution are not copyleft licences. Although all are open source and Free Software licenses.

Indeed it's more rigorous — :) —, even though I don't think there's much software that is licensed under Creative Commons terms. But it may be possible.

...

http://wiki.inkscape.org/wiki/index.php/Tutorials_and_help#English_.2 8en.29

The wiki is dedicated to inkscape development. So tutorials about inkscape development (coding, website devel, writing docs) makes sense. But tutorials about how inkscape can be used should go on the website itself.

You can use the wiki to plan out or draft content though, as long as the intention is that it'll end up on our public facing website at some point.

Okay; I hadn't understood it like that yet… The wiki has a very poor organization. You may have noticed that I started to work on it, at least on the home page. On this home page, section ‘Project Info’, there are still several page that are addressed to normal users (and redundent with the main website): About, Features, the FAQ (for questions not related to development)… I'd like to make things clearer but I'll need your help of course — :) — as I don't know much about the project and the way you see things.

My first thoughts: * Couldn't we remove ‘/wiki/index.php’ from the URL and get something like ‘http://wiki.inkscape.org/Inkscape%E2%80%99 that would be clear enough, more logical/KISS, easier to type and shorter when copied? * Do we still want to support the wiki translation (for release notes maybe)? Then could we use MediaWiki's new and official translation system (used on https://meta.wikimedia.org/ for example)? -- Sylvain

Le 02/08/2016 à 17:30, Martin Owens a écrit :

This is a matter of cleaning up content. You can delete pages, as well as making sure the content is available on the website itself. Older pages ended up on the wiki because the old website was not editable and was frozen for a long time.

Okay — :). I'll do. Well, I can't delete pages; I just put the {{Outdated}} template on them.

...

• Couldn't we remove ‘/wiki/index.php’ from the URL and get something

like ‘http://wiki.inkscape.org/Inkscape%E2%80%99 that would be clear enough, more logical/KISS, easier to type and shorter when copied?

I wouldn't know anything about that. That sounds like a php thing.

I would rather think about some MediaWiki setting… or web server configuration (.htaccess for instance, or the way folders are organized).

https://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory Well, seems we mustn't use the root directory. But we should at least remove that annoying index.php/ part.

No, development is in English. If a thing needs translation, then that's a very big sign that the content shouldn't be on the wiki but on the website somewhere. Although for some fields on the website, we're still working on translation support.

Cool — :). Therefore I'll put all non-English pages in a subcategory of the attic. -- Sylvain

On Thu, 2016-08-04 at 09:36 +0200, Sylvain Chiron wrote:

...

https://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory Well, seems we mustn't use the root directory. But we should at least remove that annoying index.php/ part.

I think ET is the person who last updated the wiki configuration.

Remember that there may be many external pages that link to that page. I don't think we need to do cosmetics, and in the process break those links, at least not as a priority.

Regards, Maren

Martin,------------------------------------------------------------------------------

---

Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

Le 05/08/2016 à 01:53, maren@...68... a écrit :

Sylvain, could you compare the 'branding' page contents in the Wiki with the trademark page contents on the website?

I think they contain different things. Please do not deactivate any Wiki pages that don't have a proper replacement. Rather move the contents, if you think it must be moved (but branding is also relevant for development

• people need to use the correct fonts etc.).

I agree, they're quite different, and I had noticed it… Actually, the content was tagged with ‘Needs work’, thus I thought it was not so important. I think that Branding info should be on the main website, as it deserves to be translated and is not exclusively targetted to development.

I replaced the frame from a blue one to a green one, so that the next person who wants to work on it will look for moving it to the website rather than improving it here. http://wiki.inkscape.org/wiki/index.php/Template:Should_be_moved

Le 05/08/2016 à 01:58, maren@...68... a écrit :

...

On Thu, 2016-08-04 at 09:36 +0200, Sylvain Chiron wrote:

...

https://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory Well, seems we mustn't use the root directory. But we should at least remove that annoying index.php/ part.

I think ET is the person who last updated the wiki configuration.

Remember that there may be many external pages that link to that page. I don't think we need to do cosmetics, and in the process break those links, at least not as a priority.

I did remember — :). But I thought it was not my role to think about that, and in parallel I thought the problem can be simply dealt with by redirecting any ^/wiki/index.php/(.*)$ to /wiki/$1 in the web server configuration, providing we won't be able to have a subpage of ‘index.php’ unless we change the ‘/wiki/’ path.

Regards, -- Sylvain

Of course data has to be downloaded to be rendered, but routinely, such data is not stored permanently by default. Also, and I shouldn't perhaps generalise, it may be presumed that most people do not habitually save web pages.

-u

---- On Mon, 25 Jul 2016 02:30:51 +0000 Sylvain Chiron&lt;chironsylvain@...120...102...&gt; wrote ----

&gt; Is not having them downloadable, to prevent them from being edited, or used &gt; without permission?

Well, I don't see what you could mean with ‘allowing to view a file but not to download it’. A file must be downloaded to be viewed, and then can be taken, copied, edited. You should only think about law and copyright if you have special wishes.

Whether the website provides an explicit ‘Download’ button or you use the ‘Save as…’ menu item of your browser when viewing, there's not much difference. -- Sylvain

------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs

Yes, I recall the link issue, so pdf could be a way forward.

However, for me, there is still something about publishing content in pdf which doesn't sit right. I feel it makes a different kind of statement, and I like (and prefer) the proto nature of html. To emulate the structure of the viewBox... project, which isn't complex using a pdf model on Inkscape.org, may not be without other issues. As I write, I am looking at example url paths for a few tutorials... Further, each pdf tutorial document needs to be able to include links to downloadable resources, which may need to be hosted on an external server, as (in my case) I don't think it will makes sense to upload them to the gallery.

Hosting html tutorials on Inkscape.org could be a better solution all round.

-u

---- On Mon, 25 Jul 2016 02:46:37 +0000 Brynn&lt;brynn@...78...&gt; wrote ----

It it possible to upload an html file. But what shows up in the gallery is the html code, not the page. So I think you'd have to make it an image file.

This is part of the problem I think I might have mentioned to you in either another message or the forum. I'm trying to figure out how to make tutorials for the website, with links. It can't be a PNG and have a link in it. It almost would have to be an SVG file. Or maybe PDF.

But anyway, to put your tutorials in the InkSpace Tutorials section, it can't be an html file.

Sorry, I wish I had a good answer for you.

All best, brynn

_______________________________________________________

From: ugajin Sent: Sunday, July 24, 2016 3:13 PM To: Brynn Cc: maren@...68... ; inkscape-docs Subject: Re: [Inkscape-docs] Help please?

Hi Brynn

I do not want to include exercises.html and tutorial.html with the zip download. The (extension) zip will include a readMe.html file. If I upload the tutorial.html and/or exercises.html to the tutorial category, won't they still be downloadable?

I would like the tutorial, and ecercises to be readable, not downloadable.

I hope this makes sense.

Kind regards

-u

---- On Sun, 24 Jul 2016 16:41:05 +0000 Brynn&lt;brynn@...78...&gt; wrote ----

Hi ugajin, I'm not quite following what your concerns are. You want the html pages to be available for users, but you don't want the users to download them? I guess you could upload the tutorial to the InkSpace Tutorial category. And then I think it's fairly typical to have a readme file together with an extension or any other program. Maybe the readme file could have a link to the tutorial?

All best, brynn

__________________________________________________

From: ugajin Sent: Sunday, July 24, 2016 4:11 AM To: maren@...68... Cc: inkscape-docs Subject: Re: [Inkscape-docs] Help please?

Hi Maren,

Yes, I am referring to the html documentation; specifically the 'tutorial.html and 'examples.html' pages. The viewBox... extension files, together with the readMe file will be downloadable. The structure that I have made, seems to work OK, and I would like to keep links in the readMe.html file for the example.html and tutorial.html pages, so ideally these pages need to be hosted, but not by me.

I have considered building a local structure, and adding the said supporting docs to the zip file. Indeed, this had been my initial approach, but as the supporting documentation grew, I began to have doubts, and to ask, why do it this way? Including them in the zip file would no doubt 'work', but it is not the approach that I would like to take.

Further, why should anyone have, or want to download files that a) they may not want, and/or b) simply in order to access, and/or peruse them? I am not against anyone downloading them per-se (e.g. if they chose to do so) and, I am less worried about users breaking any relative links. I guess, I am simply not intending the supporting documents to be downloadable.

I don't think requesting more space is an answer.

Thanks for considering matters.

Kind regards.

-u

---- On Sat, 23 Jul 2016 23:59:28 +0000 &lt;maren@...68...&gt; wrote ----

Hi u,

I'm not entirely sure which specific documents you are referring to.

If you mean external documents, that you don't control (the manual, for example), then you could just add a link into the README file and / or into the description text for the extension.

If you mean your own html documents, why don't you just add them to the zip file? You could make a subfolder 'documentation' or similar, if you like.

If you need more space for uploading everything, this list is the place to request it.

Kind Regards, Maren

&gt; &gt; I have been working on a new extension called viewBox..., which is &gt; awaiting upload to the Inkscape addons gallery. It is available for &gt; preview here: &gt; http://ugajin.co.uk/sketchbooks/viewBox/viewBox/viewBox.html, with a bunch &gt; of supporting documents. &gt; &gt; The problem is what to do with the supporting documents (I do not want to &gt; host them on ugajin.co.uk). Whilst, I may upload the extension files, &gt; without the supporting documents and/or providing a link to them, this &gt; seems to me to be the wrong approach. &gt; &gt; The viewBox and its sibling attributes are one of those things, which are &gt; not be easily accessed in Inkscape, and those cutting their teeth writing &gt; SVG using Inkscape may benefit from the supporting documentation. &gt; &gt; Thank you for considering matters. &gt; &gt; -u &gt; &gt; ------------------------------------------------------------------------------ &gt; What NetFlow Analyzer can do for you? Monitors network bandwidth and &gt; traffic &gt; patterns at an interface-level. Reveals which users, apps, and protocols &gt; are &gt; consuming the most bandwidth. Provides multi-vendor support for NetFlow, &gt; J-Flow, sFlow and other flows. Make informed decisions using capacity &gt; planning &gt; reports.http://sdm.link/zohodev2dev_______________________________________________ &gt; Inkscape-docs mailing list &gt; Inkscape-docs@lists.sourceforge.net &gt; https://lists.sourceforge.net/lists/listinfo/inkscape-docs &gt;

------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev

_______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs