From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: use svg file type for ice
Date: Tue, 31 Mar 2020 18:56:28 +0100 [thread overview]
Message-ID: <cec2e9d8-c637-c284-b0b9-41690c7a30eb@intel.com> (raw)
In-Reply-To: <016303c94c5246869ebe45bf9494cddb@intel.com>
On 3/31/2020 4:19 PM, Wang, Haiyue wrote:
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Tuesday, March 31, 2020 21:25
>> To: Wang, Haiyue <haiyue.wang@intel.com>; dev@dpdk.org; Ye, Xiaolong <xiaolong.ye@intel.com>
>> Subject: Re: [PATCH v2] doc: use svg file type for ice
>>
>> On 3/31/2020 1:06 PM, Haiyue Wang wrote:
>>> Replace the binary format png with text type svg.
>>>
>>> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
>>> ---
>>> v2: Fix the commit tile log format error
>>>
>>> ---
>>> doc/guides/nics/img/ice_dcf.png | Bin 39168 -> 0 bytes
>>> doc/guides/nics/img/ice_dcf.svg | 727 ++++++++++++++++++++++++++++++++
>>
>> <...>
>>
>>> diff --git a/doc/guides/nics/img/ice_dcf.svg b/doc/guides/nics/img/ice_dcf.svg
>>> new file mode 100644
>>> index 000000000..58851ca5d
>>> --- /dev/null
>>> +++ b/doc/guides/nics/img/ice_dcf.svg
>>> @@ -0,0 +1,727 @@
>>> +<?xml version="1.0" encoding="UTF-8" standalone="no"?>
>>> +<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
>>> +<svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg"
>> xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" width="568px" height="513px" viewBox="0 0
>> 568 513" enable-background="new 0 0 568 513" xml:space="preserve"> <image id="image0" width="568"
>> height="513" x="0" y="0"
>>> +
>> href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAjgAAAIBCAIAAADLYlLEAAAABGdBTUEAALGPC/xhBQAAACBjSF
>> JN
>>> +AAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAABmJLR0QA/wD/AP+gvaeTAAAA
>>> +CXBIWXMAABJ0AAASdAHeZh94AACAAElEQVR42uzdZ3wbx5kw8NmO3gGCvVeJpHrvkm3JlmvcHTtx
>>> +Sb1znOSScy538d29l7tcitN9SWynOO7dlquK1XulRIm9N5DoHdj+fqBMURQpUWIBSTz/nz9Yi8Vi
>>> +dgnsszPzzAwWCoU0Gg0CAAAAppJwOIzjOIZhuCzLiS4MAAAAMJQsy/0RCk90SQAAAIBhyJ+DGhUA
>>> +AICp6EKNCgIVAACAKUuWZTLRZQAAXDWe5+vr6xNdCgAmVkZGRv//QKACYPqJRqPvvPNOTk4OhmGJ
>>> +LgsA408Uxba2tm9/+9v9bX4QqACYlkiSfOCBBwiCSHRBABh/oVDo6aef7v9/SKYAAAAw1UF6OgAA
>>> +gCkNAhUAAIApDQIVAACAqWigZwoCFQAAgCkNsv4AAGBCRKPR7du3v/XWW7/4xS9SUlIGtv/+97/n
>>> +ef6WW245duzYwYMHN2zYcMsttwy86nK5vv71r6elpf3P//yPVqsdYxk6OjreeuutXbt29fX1EQSx
>>> +Zs2axx9/3G634/j411J+8pOf6PX6m2++OTMzc3yPPE6ByncK9e0d99MG10KTjzI2J7oQIGHCPIrw
>>> +iS4EQAghJIpMDClaO7q37jl0w+bb+jdGI+E33npnw423RAlNU2ffjs92xkWUM2tBSmoaQigSDu/e
>> <...>
>>
>> Hi Haiyue,
>>
>> This still looks like in binary format. The .svg should be text based, like:
>>
>> https://git.dpdk.org/dpdk/tree/doc/guides/nics/img/intel_perf_test_setup.svg?h=v20.02
>>
>>
>
> Hi Ferruh,
>
> I used the 'https://www.aconvert.com/image/png-to-svg/' online tool to convert the PNG
> to SVG. Looks like that I need to create it from zero ? Any tools suggested ?
>
When you convert, tools mostly wraps binary data and it looks like .svg but it
is not actually. In the past I remember Inkscape does the conversion to the
actual .svg format but it is not trivial and quality reduces a lot.
The best way I am aware is to recreate it as .svg from scratch unfortunately.
next prev parent reply other threads:[~2020-03-31 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 12:01 [dpdk-dev] [PATCH v1] doc: use svg file type for ice nic Haiyue Wang
2020-03-31 12:06 ` [dpdk-dev] [PATCH v2] doc: use svg file type for ice Haiyue Wang
2020-03-31 13:24 ` Ferruh Yigit
2020-03-31 15:19 ` Wang, Haiyue
2020-03-31 17:56 ` Ferruh Yigit [this message]
2020-04-01 5:44 ` [dpdk-dev] [PATCH v3] doc: use svg file type for ice PMD Haiyue Wang
2020-04-01 12:11 ` Ferruh Yigit
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=cec2e9d8-c637-c284-b0b9-41690c7a30eb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=xiaolong.ye@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).