[oats-sig] Ang: Re: Ang: Re: Ang: Re: Ang: Re: Ang: Re: Ang: Re: wmf to svg conversion

Mats,

For general use you'd need to drop the MS specific namespaces (winfx
and xslt) which aren't used and  I suspect are artifacts of the
conversion transforms.

Steve

2008/7/8 Robert Rasiewicz <robert.wk at gmail.com>:
> Mats,
>
> For FF to render those you'd need to add the following attribute to the
> output .svg file (in the top-most <svg> node:
>    xmlns="http://www.w3.org/2000/svg"
>
> You can find an example in the attached.
>
> Indeed FF renders them correctly as rounded and Inkscape appears to be
> ignoring those attributes.
>
> Now - this should really be done as part of Inkscape's xaml2svg xslt but I
> can also add this in post-processing stage of the conversion util - I will
> try and do it sometime this week.
>
> r.
>
> On Tue, Jul 8, 2008 at 11:20 AM, Mats Lundälv <mats.lundalv at vgregion.se>
> wrote:
>>
>> Hi Robert,
>>
>> You (and Andrej?) have done a fantastic job in no time - congratulations!!
>> Your conversions look close to perfect when I open them in Inkscape. In
>> Firefox I only see the xml code - very compact - lacking meta and
>> presentatin information etc I guess?
>>
>> The only general tweek I would like to do so far - to what I can see in
>> Inkscape - is changing the line style to rounded ends - to make the symbols
>> look nicer and less "edgy".
>> Funny enough: When I look in the code it looks like
>> stroke-linecap/line-joins areactually are set to "Round"? I don't know
>> enough about svg-xml, but Inkscape does not seem to pick it up.
>> When I change the line style Line-ends in Inkscape, and save, I get a much
>> larger svg-xml file of course, where the stroke-linecap="Round" setting is
>> duplicated in a "style" entry in the path tag: style="stroke-linecap:round"
>>
>> I also need to check that the fixed hights and vertical positioning of the
>> symbols is retained a bit more, but this looks very good!
>> How can we best communicate this progress to the OOo, Inscape and
>> Batik projects?
>>
>> Cheers,
>> Mats
>>
>> -----<oats-sig-bounces at lists.becta.org.uk> skrev: -----
>>
>> Till: "OATs Project Special Interest Group" <oats-sig at lists.becta.org.uk>
>> Från: Robert Rasiewicz <robert.wk at gmail.com>
>> Sänt av: <oats-sig-bounces at lists.becta.org.uk>
>> Datum: 2008-07-08 10:25
>> Ärende: Re: [oats-sig] Ang: Re: Ang: Re: Ang: Re: Ang: Re: Ang: Re: wmf to
>> svg conversion
>>
>> Mats,
>>
>> Paste2Xaml libraries have been fixed by Andrej Benedik and he's released a
>> new version now.
>>
>> I've subsequently updated the conversion util and added some exception
>> handling to it.
>> We should now be able to see if it's missing components or something else
>> causing it to fail on your machine.
>> In principle - if Paste2Xaml is working, the conversion util should work
>> also.
>>
>> Updated files you can find here
>>    http://www.3point14.com/pub/WMF_to_SVG_0_2_binaries.zip
>>    http://www.3point14.com/pub/WMF_to_SVG_0_2_sources.zip
>>
>> Attached are svg files created using the tool - I think you should find
>> the results satisfactory.
>>
>> r.
>>
>> On Sat, Jul 5, 2008 at 12:24 AM, Mats Lundälv <mats.lundalv at vgregion.se>
>> wrote:
>>>
>>> Hi Robert,
>>> Thanks for your efforts!
>>>
>>> I have now tested opening my wmf files with the Paste2Xaml tool - and
>>> unfortunately it does not handle any of the circles, semi-circle or circle
>>> segment components of the wmf:s - just like SVGFactory they just disappear.
>>> Only straight lines are displayed. I didn't manage to run your app, probably
>>> because I don't have the latest .net components installed - or is it a
>>> command line tool? Anyway it should not work any better than the Paste2Xaml
>>> routines that it uses, I suppose?
>>>
>>> The application that actually let's me both open the wmf:s correctly and
>>> save them as reasonably usable svg images now is OOo Draw. The problem there
>>> is that the line widths are set to zero, and that the black line colour is
>>> set to undefined. I can open these converted svg images in Inkscape and
>>> manually correct them to a good result - but it would be a HUGE work for the
>>> between 3000-4000 thousand files I'm working with - close to undoable.
>>>
>>> ImageMagick can also open and display the wmf:s correctly, but cannot
>>> convert to correct svg.
>>>
>>> The most promising auto-conversion tool so far is probably the
>>> wmf2svg-0.8.1.jar tool. It actually picks up all components of the wmf, and
>>> the converted svg:s are basically nicely displayed in both Firefox and
>>> Inkscape - except it cannot handle the circular elements correctly:
>>> Circles are correctly positioned but double diameter in size
>>> Semi-circles are collapsed to a blob - a very small filled semi-circle -
>>> incorrectly positioned
>>> Circle segments are displayed in a weird way - double diameter -
>>> incorrect position, orientation (ignored mirroring/flipping) and rotation
>>> (45 degrees).
>>>
>>> So what are the alternatives:
>>> - Find a way to use the components that OOorg uses and try to get them
>>> improved
>>> or/and
>>> - Approach the developer of wmf2svg-0.8.1 and try to persuade him to take
>>> a look at my odd line drawing wmf files and try to handle the circular
>>> shapes better
>>> - others?
>>>
>>> I attach a few samples of the Blissymbol wmf files I'm struggling with,
>>> if any of you want to see for yourselves what happens ;-)
>>>
>>> Cheers,
>>> Mats
>>
>>
>>
>> [bilaga "bliss_svg.zip" borttagen av Mats Lundälv/vgregion]
>
>

-- 
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk