Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index



If you really need to read Visio, the free package of Dia does a good job, or so I have been told. I has Visio on one system till MS disabled it when they bought it out and now wanted me to pay them for the new version. After that, I could never get it running on a system with MSO 2002/2003 or newer. I did a large network project using Visio before MSO killed me. Now I would use Dia if I need a Visio type of system with all its libraries.

SO
I wonder if the people at Dia would have any input filters that would be useful to LO to support the older Visio files?

On 01/21/2012 03:28 PM, Tom Davies wrote:
Hi :)

I agreed with NoOp once he had explained the situation.  Being able to
read a 12year old undocumented and proprietary format is impressive enough.  There are a lot of 
other interesting challenges out there :)
Regards from
Tom :)


--- On Sat, 21/1/12, Fridrich Strba<fridrich.strba@bluewin.ch>  wrote:

From: Fridrich Strba<fridrich.strba@bluewin.ch>
Subject: [libreoffice-users] Re: [Visio] Re: So what's with LibO 3.5?
To: users@global.libreoffice.org
Cc: "NoOp"<glgxg@sbcglobal.net>
Date: Saturday, 21 January, 2012, 13:20

Hello,

On 13/01/12 22:42, NoOp wrote:
On 01/13/2012 02:31 AM, Tom Davies wrote:
Hi :) That might be very interesting to the devs and now would be
excellent timing to let them know you have some files from that era.
    Regards from Tom :)
They've contributed quite a lot of work:
<http://libregraphicsworld.org/blog/entry/the-ultimate-quest-of-bringing-visio-support-to-libreoffice>
and at this point introducing:

/Samples/Network Diagram$ file "Basic Wide Area Network Diagram.VSD"
Basic Wide Area Network Diagram.VSD: CDF V2 Document, Little Endian, Os:
Windows, Version 4.0, Code page: 1252, Author: Copyright \022 1997 Visio
Corporation.  All rights reserved., Keywords: v5.0, Title: Basic Wide
Area Network Diagram

into the picture probably wouldn't be appreciated. I think it better to
let them get the current code settled before asking for support of 15
year old Visio Technical v5.0 code/diagram-format.
I would not mind to try to support Visio 5.0 file-format. Nevertheless a collection of documents is 
not enough for us to understand how the file-format is working.

You know that there is no documentation whatsoever for the binary file-formats, so what we need is 
an application that is generating those documents so that we can experiment with it.

So, the deal is: Get to me a pre-Microsoft Visio that generates version 5 diagrams natively and I 
will do my best to add that file-format to libvisio.

For the time being, though, only MS Visio 2000 and later is supported.

Cheers

Fridrich

-- For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted




--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.