I generally have to agree with what is written below, but I have to take a
minor exception on (a) regarding 'the line that you can do it with DITA or
DocBook'. Out of the box does a good job, but unfortunately the 'good job' is
at scaring people away. That being said, I'll have a freebie of a
Hi Framers,
I have a lot of unstructured docs and I have conversion table to convert
them to structured files.
I wrote a FrameScript, but there are two points that I would like to improve
on this, and I did not find any commands for these in the FrameScript
references:
1. To get the conversion
The Real Life Migration to Stuctured Doc thread got me thinking. What is
better? A custom schema or one the standards such as Docbook or DITA.
I've often thought that if one knows how to create a schema (and the
resulting EDD, DTD, XSD, etc.) you're better off creating your own,
especially since
The main advantages to using one of the standard schemas:
1) It has been developed and used by others so it has the benefit of being
tested and proven with actual documentation.
2) Even if it needs to be customized, you have a head-start in the
development process.
3) If there is already
For those few Mac people are still on the list, FM got mentioned as
one reason not to upgrade to Intel in a Wired story:
http://www.wired.com/news/technology/0,70086-0.html
Always nice to be thought of ;)
___
You are currently subscribed to Framers
Hi there!
Anybody have a fix for broken OLEs, or have any idea what's causing the
problem? When I right-click the Visio image in .fm, it apparently
recognizes it as a Visio Object, but selecting Edit or Open results in
the dreaded Cannot invoke OLE server dialog.
I tried EditLinks but options
Hi Michael,
Good points, well taken. Thanks.
Rick
I agree with Rick's points. But there are situations where it might not
be worth the effort digging deep in the available material for a
so-called standard, when -- in the end -- the customized solution still
needs non-standard modifications.
Michael,
I second Rick's opinion: Import by Reference is the way to go.
I've had good results saving PowerPoint slides as *.wmf. Visio also
saves in that format. Unfortunately I had to save a native format
version of the graphic as well as the *.wmf in another folder for Frame
Import.
Glenn
Andrew Becraft wrote:
Rick Quatro wrote:
I am not familiar with Visio, so I can't suggest a graphic
format, but
perhaps you can use EPS or PDF.
I've never had good luck with embedding my Visio diagrams as
OLE objects. I've generally used WMF, but sometimes Visio
refuses to save as
At 10:35 AM 2/1/2006, Andrew Becraft wrote:
I've never had good luck with embedding my Visio diagrams as OLE objects.
I don't have all that many Visio drawings in my doc set, but it's worked
for me for 3 years to use OLE linking for them. It may not be as solid as
saiving the drawings to EPS
Bernard wrote:
I generally have to agree with what is written below, but I have to take a
minor exception on (a) regarding 'the line that you can do it with DITA or
DocBook'. Out of the box does a good job, but unfortunately the 'good job'
is at scaring people away.
I consider DITA to be an
On Wed, 1 Feb 2006 09:22:54 -0500, Raman Pfaff [EMAIL PROTECTED] wrote:
For those few Mac people are still on the list, FM got mentioned as
one reason not to upgrade to Intel in a Wired story:
http://www.wired.com/news/technology/0,70086-0.html
Always nice to be thought of ;)
And for those Mac
--- [EMAIL PROTECTED] wrote:
I consider DITA to be an interchange format. If two
organisations can figure out how to convert their
own structure to and from DITA, they can freely
exchange data. Add five more
organisations and impose the same requirement on
them and everyone can exchange data,
Hi Framers,
I have a lot of unstructured docs and I have conversion table to convert
them to structured files.
I wrote a FrameScript, but there are two points that I would like to improve
on this, and I did not find any commands for these in the FrameScript
references:
1. To get the conversion
The "Real Life" Migration to Stuctured Doc thread got me thinking. What is
better? A custom schema or one the "standards" such as Docbook or DITA.
I've often thought that if one knows how to create a schema (and the
resulting EDD, DTD, XSD, etc.) you're better off creating your own,
especially
The main advantages to using one of the standard schemas:
1) It has been developed and used by others so it has the benefit of being
tested and "proven" with actual documentation.
2) Even if it needs to be customized, you have a head-start in the
development process.
3) If there is already an
You could also try this...
(Seen today on Slashdot)
URL:
http://hardware.slashdot.org/article.pl?sid=06/02/01/137202=rss
The Optimus Mini Keyboard
Posted by CmdrTaco on Wednesday February 01, @08:53AM
from the now-isn't-that-cute
Hello
I am missing an updated version of the German dictionaries (spelling,
hyphenation,..)
Where can I find it ?
I expected to find an indicator on the adobe website, however did not.
How do I report Framemaker 7.2 bugs/issues and feature requests ?
Thanks
Valerie Nyre
I agree with Rick's points. But there are situations where it might not
be worth the effort digging deep in the available material for a
so-called standard, when -- in the end -- the customized solution still
needs non-standard modifications.
As an example: DocBook comes with many more elements
TW-857 Tech Writer - Contract - Falls Church, VA - IMMEDIATE NEED!
Length: 3 weeks, may go longer
Rate: BOE
An engineering company in Falls Church needs a writer with the
following experience to to work on-site for 3+ weeks:
o. Recent experience writing printed and online documentation for
For those few Mac people are still on the list, FM got mentioned as
one reason not to upgrade to Intel in a Wired story:
http://www.wired.com/news/technology/0,70086-0.html
Always nice to be thought of ;)
Hi there!
Anybody have a fix for broken OLEs, or have any idea what's causing the
problem? When I right-click the Visio image in .fm, it apparently
recognizes it as a "Visio Object", but selecting Edit or Open results in
the dreaded "Cannot invoke OLE server" dialog.
I tried Edit>Links but
Hi Michael,
This is probably not the advice you wanted, but I would discourage you from
using OLE objects in FrameMaker. The safest, most-reliable approach is to
save your Visio images in a graphic format and import the graphic by
reference into FrameMaker. I am not familiar with Visio, so I
Hi Michael,
Good points, well taken. Thanks.
Rick
>I agree with Rick's points. But there are situations where it might not
> be worth the effort digging deep in the available material for a
> so-called standard, when -- in the end -- the customized solution still
> needs non-standard
Michael,
I second Rick's opinion: Import by Reference is the way to go.
I've had good results saving PowerPoint slides as *.wmf. Visio also
saves in that format. Unfortunately I had to save a native format
version of the graphic as well as the *.wmf in another folder for Frame
Import.
Glenn
Rick Quatro wrote:
> I am not familiar with Visio, so I can't suggest a graphic format, but
> perhaps you can use EPS or PDF.
I've never had good luck with embedding my Visio diagrams as OLE
objects. I've generally used WMF, but sometimes Visio refuses to save
as WMF and I have to use EMF or
Andrew Becraft wrote:
> Rick Quatro wrote:
> > I am not familiar with Visio, so I can't suggest a graphic
> format, but
> > perhaps you can use EPS or PDF.
>
> I've never had good luck with embedding my Visio diagrams as
> OLE objects. I've generally used WMF, but sometimes Visio
> refuses
At 10:35 AM 2/1/2006, Andrew Becraft wrote:
>I've never had good luck with embedding my Visio diagrams as OLE objects.
I don't have all that many Visio drawings in my doc set, but it's worked
for me for 3 years to use OLE linking for them. It may not be as solid as
saiving the drawings to EPS
On Wed, 1 Feb 2006 09:22:54 -0500, Raman Pfaff
wrote:
>For those few Mac people are still on the list, FM got mentioned as
>one reason not to upgrade to Intel in a Wired story:
>
>http://www.wired.com/news/technology/0,70086-0.html
>
>Always nice to be thought of ;)
And for those Mac users
--- mcarr at allette.com.au wrote:
> I consider DITA to be an interchange format. If two
> organisations can figure out how to convert their
own structure > to and from DITA, they can freely
exchange data. Add five more
> organisations and impose the same requirement on
them and everyone can
I generally have to agree with what is written below, but I have to take a
minor exception on (a) regarding 'the line that you can do it with DITA or
DocBook'. Out of the box does a good job, but unfortunately the 'good job' is
at scaring people away. That being said, I'll have a freebie of a
Dominick A. DeFlorio wrote:
> We must move to structure to meet our future XML goal, but are
> unfamiliar with both the transition and method to do so. We are also
> unfamiliar with the possibilities and cost involved. We are merely
> looking at all of the possibilities and the long term value
Rick Quatro wrote:
> I agree with Marcus's excellent post, but one thing to consider on the
> above point: even if you hire it out, try to learn as much about each
> process, especially if you can devote some time to it. In today's job
> climate, it pays to learn as much as you can about XML
33 matches
Mail list logo
