According to James K. Lowden <[EMAIL PROTECTED]>:
> I'm skeptical, though, of the strategy: Why should Dia want to export to Visio,
> only to see free data trapped in a closed format? Wouldn't it be more worthwhile
> to go the other way, to use Ole to free the data from Visio and write a Dia fil
I was wondering if someone actually planned to write a Kivio[*] import/export
plug-in. That would be great that Dia be open to data exchange with other
open source Diagramming software.
Hub
[*] for the ignorant, Kivio is KOffice's Visio clone.
___
*** Recent ChangeLog entries:
--- ChangeLog.previous Thu Jun 7 09:23:05 2001
+++ dia/ChangeLog Fri Jun 8 07:01:43 2001
@@ -1,3 +1,36 @@
+2001-06-07 Cyrille Chepelov <[EMAIL PROTECTED]>
+
+ * app/app_procs.c (app_init): added a call to unicode_init() (only
+ if HAVE_UNICODE,
- Message d'origine -
De : "Hubert Figuiere" <[EMAIL PROTECTED]>
À : <[EMAIL PROTECTED]>
Envoyé : vendredi 8 juin 2001 09:09
Objet : Re: dia file exchange
> Q: how would a user do to move a Dia file to Visio. 2 solutions:
> -generate a Visio file from the dia file
> -write a Dia importe
According to Cyril ZEKSER <[EMAIL PROTECTED]>:
> > Q: how would a user do to move a Dia file to Visio. 2 solutions:
> > -generate a Visio file from the dia file
> > -write a Dia importer within Visio (is it possible ?)
> >
> > solution #1 require that one of the system have both Visio and Dia, wh
Yes, Word (or Visio) itself does know anything about Dia, but Dia can pilot
Visio to draw it's own shapes and schemas, as far as you have the OLE
interface of Visio documented. It's like scripting.
Cyril
- Message d'origine -
De : "Hubert Figuiere" <[EMAIL PROTECTED]>
À : <[EMAIL PROTECT
On Fri, 08 Jun 2001, James K. Lowden wrote:
> Lars Clausen wrote:
>
>> I guess using OLE to convert files is the only viable option. Does
>> anyone here know OLE well enough to attempt such?
>
> Yes.
>
> The OLE bit wouldn't be that hard, actually, with Perl and decent
> documentation of Visi
On Fri, 8 Jun 2001, Hubert Figuiere wrote:
>
> I was wondering if someone actually planned to write a Kivio[*]
> import/export plug-in. That would be great that Dia be open to data
> exchange with other open source Diagramming software.
Hadn't seen that. There's a couple things in there that w
According to Lars Clausen <[EMAIL PROTECTED]>:
> > I was wondering if someone actually planned to write a Kivio[*]
> > import/export plug-in. That would be great that Dia be open to data
> > exchange with other open source Diagramming software.
>
> Hadn't seen that. There's a couple things in t
According to Cyril ZEKSER <[EMAIL PROTECTED]>:
> Yes, Word (or Visio) itself does know anything about Dia, but Dia can pilot
> Visio to draw it's own shapes and schemas, as far as you have the OLE
> interface of Visio documented. It's like scripting.
That is what I wrote.
Hub
_
According to Lars Clausen <[EMAIL PROTECTED]>:
> On Fri, 8 Jun 2001, Hubert Figuiere wrote:
>
> >
> > I was wondering if someone actually planned to write a Kivio[*]
> > import/export plug-in. That would be great that Dia be open to data
> > exchange with other open source Diagramming software.
On Fri, 8 Jun 2001, Hubert Figuiere wrote:
> According to Lars Clausen <[EMAIL PROTECTED]>:
>
>> The Kivio format is gzipped XML, but with binary junk at the front. The
>> stencils (shapes) that are used in the file are stored in it (a neat
>> feature, but should be optional for Dia). Other th
I can't finish building Dia because of these errors in a .po file:
file=./echo zh_TW.Big5 | sed 's,.*/,,'.gmo \
&& rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file zh_TW.Big5.po
zh_TW.Big5.po:161: illegal control sequence
zh_TW.Big5.po:382: illegal control sequence
zh_TW.Big5.po:1592:
On Fri, 8 Jun 2001, Hubert Figuiere wrote:
>
> I can't finish building Dia because of these errors in a .po file:
>
> file=./echo zh_TW.Big5 | sed 's,.*/,,'.gmo \
> && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file
> zh_TW.Big5.po
> zh_TW.Big5.po:161: illegal control sequence
> z
On 8 Jun 2001, Lars Clausen wrote:
> On Fri, 8 Jun 2001, Hubert Figuiere wrote:
>
> >
> > I can't finish building Dia because of these errors in a .po file:
> >
> > file=./echo zh_TW.Big5 | sed 's,.*/,,'.gmo \
> > && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file
> > zh_TW.Big5.po
Hubert Figuiere wrote:
>
> I can't finish building Dia because of these errors in a .po file:
>
> file=./echo zh_TW.Big5 | sed 's,.*/,,'.gmo \
> && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file zh_TW.Big5.po
> zh_TW.Big5.po:161: illegal control sequence
> zh_TW.Big5.po:382: illega
According to Ben A. Hetland <[EMAIL PROTECTED]>:
> > several occasion there are '\' that are just part of the multibyte charset.
> > What is the solution ?
>
> One solution is to replace the single '\' with an escaped '\\', since
> the \ is the standard escape character in C strings.
That's wha
The other group (of which I am a member) use Dia but need to give the
diagrams in editable format to superiors who use Visio. This is really what
I was after. I agree that open file formats are better, but to gain
acceptance, any new software needs to be able to work within the existing
stan
You could also just write a standalone (or Visio-hosted)
Perl/Python/VB/JScript tool that used the Visio OLE controls and the
MSXML parser to do the transformation in either direction. I'm not a big
Windows Scripting guy, but I've done enough basic stuff in this style
(app-to-app conversion ha
Lennon Day-Reynolds [mailto:[EMAIL PROTECTED]] wrote:
> You could also just write a standalone (or Visio-hosted)
> Perl/Python/VB/JScript tool that used the Visio OLE controls and the
> MSXML parser to do the transformation in either direction.
> I'm not a big
> Windows Scripting guy, but I've
On Fri, 8 Jun 2001, Jamin Collins wrote:
> Placing the import/export function on the Dia side would eliminate these
> hurdles and open another door for the use of Dia. It won't be easy to
> reverse engineer the format, but once again it's not impossible.
Let me just remind the dollar-hungry rev
Le jeu, jun 07, 2001, à 11:47:07 -0400, Kostas Oikonomou a écrit:
>
> Hello,
>
> I'm just beginning to use Dia, and I have a couple of questions:
>
> 1. Is it possible to set paper size as a global default, e.g. in the
> ~/.dia/diarc file?
check out /etc/papersize
-- Cyrille
--
Grum
Viso can export to DXF, VML, and others. I know that VML is a
microsoftism but it's an XML extension
and is therefore in human readable form. I haven't worked with VML but
have read what it is
supposed to be. Would it make more sense to focus on being compatible
with a file format
other than
On Fri, 08 Jun 2001, Rick Jafrate wrote:
> Viso can export to DXF, VML, and others. I know that VML is a
> microsoftism but it's an XML extension
> and is therefore in human readable form. I haven't worked with VML but
> have read what it is
> supposed to be. Would it make more sense to focus
Hi Lyle,
Lyle wrote:
> The other group (of which I am a member) use Dia but need to give the
> diagrams in editable format to superiors who use Visio. This is really what
> I was after. I agree that open file formats are better, but to gain
> acceptance, any new software needs to be able to wo
Lennon Day-Reynolds wrote:
> You could also just write a standalone (or Visio-hosted)
> Perl/Python/VB/JScript tool that used the Visio OLE controls and the
> MSXML parser to do the transformation in either direction. I'm not a big
> Windows Scripting guy, but I've done enough basic stuff in this
26 matches
Mail list logo
