Gentle persons:
I don't disagree with anything that was said in response to my first
message. I thought I had made it clear that I have no love for
bit-mapped graphics when I suggested png for now with a personal bias to
lean toward svg, where appropriate, in future and that I was not
suggesti
Pavel Shramov wrote:
> Including raster formats like png or gif into pdf give horrible result
> compared
> to vector ones. Also converting vector schemas to bitmap limits you in
> editing.
>
Right, we should probably pick one format for photographic and
illustrative images, like jpeg.
And, an
On 15 November 2011 11:15, Francis wrote:
> Inkscape is in the Ubuntu distribution. He manages .svg .dxf .eps etc.
> It is easy to use.
Google also found:
http://sourceforge.net/projects/dxf-svg-convert/
(and other, paid-for options
There is something very "Linux" about the positive review "After
Inkscape is in the Ubuntu distribution. He manages .svg .dxf .eps etc.
It is easy to use.
Francis
2011/11/15 Kim Kirwan
> Everything suggested looks good, except maybe one thing.
>
> I should point out that dxf may be the original source if the
> image (a line drawing) was created in QCAD or no
Everything suggested looks good, except maybe one thing.
I should point out that dxf may be the original source if the
image (a line drawing) was created in QCAD or now, LibreCAD.
(Or possibly even AutoCAD in some cases?)
So I wouldn't be in a hurry to get rid of dxf, in case it is
the origi
On Sun, Nov 13, 2011 at 11:19:40AM -0500, Kent A. Reed wrote:
> 1. image file format
First, sorry for late response...
> Taking a survey of the files in the 2.5 docs/src directory and below, I
> find we have 368 image files in dxf, eps, gif, jpg, png, and ps format.
> (Yes, I know some of the i
instead of reverting to bitmaps, which I think are a step backwards in quality,
I rather suggest move forward to all-scalable formats where possible, like eps
or svg
if they dont work, lets fix the tools, or the image files for that matter, but
not downgrade the docs to measly bitmaps everywhe
Sebastian Kuzminsky wrote:
> On 11/13/2011 04:28 PM, Jon Elson wrote:
>
>> I had been working on a significant
>> update to the docs for the Pico Systems boards, now the PDFs are not
>> being built, so I have no idea how the PDF form of the asciidoc will
>> look.
>>
>
> The pdfs *are* being
On 11/13/2011 04:28 PM, Jon Elson wrote:
> I had been working on a significant
> update to the docs for the Pico Systems boards, now the PDFs are not
> being built, so I have no idea how the PDF form of the asciidoc will
> look.
The pdfs *are* being built Jon, we went over this a week or two ago.
Kent A. Reed wrote:
>
> The first issue is the big one in my book. How should this material be
> organized? Should it be one humongous document? Many documents?
I think the size of the current docs DOES need several separate files,
as PDFs.
I don't think "many" is required, and maybe the current
Chris Morley wrote:
> It seems to me the EMC board needs to create a clear path
> for our doc issue.
>
> I don't believe anyone is doing anything wrong, we just seem
> to be going an a few different directions with a lack of communication.
> Even when we try to communicate. :)
Yes, I strongly suppo
On 11/13/2011 3:43 PM, John Thornton wrote:
> Kent,
>
> The guidelines I was working under was:
> If the image was based on a dxf file retain that file so changes could
> be made if needed in the future.
> Use png images when possible (always use png was the actual guideline).
>
> I have no idea wh
>
> I'm happy to work on this, but I'm not until I get some assurance that
> all my work is not going to be tossed in the trash again.
>
> John
>
It seems to me the EMC board needs to create a clear path
for our doc issue.
I don't believe anyone is doing anything wrong, we just seem
to be g
Kent,
The guidelines I was working under was:
If the image was based on a dxf file retain that file so changes could
be made if needed in the future.
Use png images when possible (always use png was the actual guideline).
I have no idea what the guidelines for 2.5 is as it has been completely
c
On 13 November 2011 17:14, Kent A. Reed wrote:
> As a matter of personal prejudice, I think svg is better suited for
> vector graphics exchange than eps. We aren't exploiting the "vector"
> nature of the images in production, anyway.
I was mainly thinking of the equations in the pdf files (and I
On 11/13/2011 11:47 AM, andy pugh wrote:
> On 13 November 2011 16:19, Kent A. Reed wrote:
>
>> However, I recommend that we restrict the production image files (e.g.,
>> the files actually invoked in the asciidoc .txt files) to just two*
>> formats---gif and png.
> Why keep gif? png is effectively
On 13 November 2011 16:19, Kent A. Reed wrote:
> However, I recommend that we restrict the production image files (e.g.,
> the files actually invoked in the asciidoc .txt files) to just two*
> formats---gif and png.
Why keep gif? png is effectively an updated .gif.
I would rather we kept eps an
Gentle persons:
1. image file format
Taking a survey of the files in the 2.5 docs/src directory and below, I
find we have 368 image files in dxf, eps, gif, jpg, png, and ps format.
(Yes, I know some of the images appear in multiple formats, but that's
not the main issue here).
I think it is f
18 matches
Mail list logo
