Design Review

Reply
*David Metcalf
Message 1 of 17 (109 Views)

Word Docs

109 Views, 16 Replies
06-22-2004 05:00 PM
Noticed a Word doc is typically 3 times bigger than a PDF format of the same file. Can you add a wish list to reduce that to compare with PDF in size?
*VJoseph \(Autodesk Support\)
Message 2 of 17 (109 Views)

Re: Word Docs

06-23-2004 01:12 AM in reply to: *David Metcalf
I did not notice this behaviour - does your doc contain images? HTH VJoseph "David Metcalf" wrote in message news:40d8c826$1_3@newsprd01... > Noticed a Word doc is typically 3 times bigger than a PDF format of the same > file. Can you add a wish list to reduce that to compare with PDF in size? > >
*Rodney McManamy - CADzation
Message 3 of 17 (109 Views)

Re: Word Docs

06-23-2004 05:44 AM in reply to: *David Metcalf
The DWF format is optimized for AutoCAD drawings. What we have noticed is that anything from Word or Excel that uses gradiant fills, Word Art, fancy text, or lot's of graphics does not convert well with the DWF Writer and is typically as you said 3 or more times larger. The PDF on the other hand is optimized for Word style documents and small format but doesn't understand shx fonts so it's larger on AutoCAD drawings. The DWF Writer is still fairly new (and was developed mainly to support Revit and other non-AutoCAD CAD applications) and I'm sure will get better at office documents because it's going to have to if they want it to really compete against the PDF. In the real world it's about more than just AutoCAD drawings that need to go to the client. -- Rodney McManamy President CADzation ------------------------- rmcmanamy@cadzation.com ------------------------- 518 South Route 31 Suite 200 McHenry, IL 60050 www.cadzation.com Providing Industrial Strength PDF & DWF Solutions to the Global CAD Marketplace. "David Metcalf" wrote in message news:40d8c826$1_3@newsprd01... > Noticed a Word doc is typically 3 times bigger than a PDF format of the same > file. Can you add a wish list to reduce that to compare with PDF in size? > >
*Scott Sheppard
Message 4 of 17 (109 Views)

Re: Word Docs

06-23-2004 09:40 AM in reply to: *David Metcalf
I don't think they want to compete against PDF for nonCAD. They want CAD data to stay in DWF, so they can do intelligent processing on the objects. I think DWF Composer and DWF Writer are good for situations where you have 99 DWGs and 1 Word DOC. You can make one DWF with all 100 items. If you have 99 DOCs and 1 DWG, even Autodesk would probably recommend that you make a PDF for the Word parts and one small DWF for the DWG. People in the newsgroup seem to be apologetic when they mention PDF, e.g., "I'm sorry - I have to use it.", but they shouldn't be. IMHO Autodesk is adamant about CAD data NOT going to PDF. For other types of data, I don't think they care. "Rodney McManamy - CADzation" wrote in message news:40d97b23_2@newsprd01... > The DWF format is optimized for AutoCAD drawings. What we have noticed is > that anything from Word or Excel that uses gradiant fills, Word Art, fancy > text, or lot's of graphics does not convert well with the DWF Writer and is > typically as you said 3 or more times larger. The PDF on the other hand is > optimized for Word style documents and small format but doesn't understand > shx fonts so it's larger on AutoCAD drawings. > > The DWF Writer is still fairly new (and was developed mainly to support > Revit and other non-AutoCAD CAD applications) and I'm sure will get better > at office documents because it's going to have to if they want it to really > compete against the PDF. In the real world it's about more than just > AutoCAD drawings that need to go to the client.
*Garrick Evans
Message 5 of 17 (109 Views)

Re: Word Docs

06-23-2004 10:49 AM in reply to: *David Metcalf
Scott is right on - DWF is not intended for Office documents just as PDF is not intended for design data. DWFWriter was designed to capture design data from applications that do not export DWF directly, in particular, however, no claim has ever been made that it supports (or ever will) Microsoft Office. One of the reasons for this is the nature of the graphics flow through GDI and the driver framework, in many cases items like those mentioned previously ultimately arrive at the driver as a bitmap. Take the case of the gradient fill. This is easy to do in a W2D stream, however, even though there is a DrvGradientFill() driver hook, no Office application will EVER invoke it, so no simple op-code describing these graphics will ever exist. As a result, the driver might end up with a large bitmap with a masking region or, worse, lots of little gradually colored polygons or rects with masks. There is no state communicated across driver calls, in the latter case, the driver couldn't possibly hope to reassemble these regions as a single shaded polygon, so the DWF ends up with lots of rectangles in the best case or lots of images in the worst. This is one of the main reasons Autodesk discourages use of the DWFWriter for applications that can export DWF natively, those will always produce smaller DWF with the highest possible fidelity. hth, g "Scott Sheppard" wrote in message news:40d9b293$1_1@newsprd01... > I don't think they want to compete against PDF for nonCAD. They want CAD > data to stay in DWF, so they can do intelligent processing on the objects. I > think DWF Composer and DWF Writer are good for situations where you have 99 > DWGs and 1 Word DOC. You can make one DWF with all 100 items. If you have 99 > DOCs and 1 DWG, even Autodesk would probably recommend that you make a PDF > for the Word parts and one small DWF for the DWG. People in the newsgroup > seem to be apologetic when they mention PDF, e.g., "I'm sorry - I have to > use it.", but they shouldn't be. IMHO Autodesk is adamant about CAD data NOT > going to PDF. For other types of data, I don't think they care. > > "Rodney McManamy - CADzation" wrote in message > news:40d97b23_2@newsprd01... > > The DWF format is optimized for AutoCAD drawings. What we have noticed is > > that anything from Word or Excel that uses gradiant fills, Word Art, fancy > > text, or lot's of graphics does not convert well with the DWF Writer and > is > > typically as you said 3 or more times larger. The PDF on the other hand > is > > optimized for Word style documents and small format but doesn't understand > > shx fonts so it's larger on AutoCAD drawings. > > > > The DWF Writer is still fairly new (and was developed mainly to support > > Revit and other non-AutoCAD CAD applications) and I'm sure will get better > > at office documents because it's going to have to if they want it to > really > > compete against the PDF. In the real world it's about more than just > > AutoCAD drawings that need to go to the client. > >
*Rodney McManamy - CADzation
Message 6 of 17 (109 Views)

Re: Word Docs

06-24-2004 06:40 AM in reply to: *David Metcalf
I think the problem really comes back to Autodesk's own marketing which has been educating the users by marketing the DWF against the PDF. It's like Ford marketing an Escort against a Chevy Pickup. No doubt the Escort get's better mileage but try to put a 4x8 sheet of plywood in it. In my opionion where DWF will end up being the choice is where you are going to need intelligent data downstream. PDF if you just need to view and print but DWF if you need to view, plot, measure, or view intelligent data. Or if you are working mainly with vector CAD data. And users also have to realize that the DWF Writer was created to support the Autodesk apps that don't have direct DWF output. It's no easy task printing every Windows application to a hybrid vector/raster format. There are PDF companies that have been working on this (and only this) for years and they still aren't perfect and they charge you for it. Adobe's own driver doesn't print worth a darn from Illustrator 10 but Distiller usually works pretty well or you can save directly to it. -- Rodney McManamy President CADzation ------------------------- rmcmanamy@cadzation.com ------------------------- 518 South Route 31 Suite 200 McHenry, IL 60050 www.cadzation.com Providing Industrial Strength PDF & DWF Solutions to the Global CAD Marketplace. "Garrick Evans" wrote in message news:40d9c2bf$1_1@newsprd01... > Scott is right on - DWF is not intended for Office documents just as PDF is > not intended for design data. DWFWriter was designed to capture design data > from applications that do not export DWF directly, in particular, however, > no claim has ever been made that it supports (or ever will) Microsoft > Office. One of the reasons for this is the nature of the graphics flow > through GDI and the driver framework, in many cases items like those > mentioned previously ultimately arrive at the driver as a bitmap. Take the > case of the gradient fill. This is easy to do in a W2D stream, however, > even though there is a DrvGradientFill() driver hook, no Office application > will EVER invoke it, so no simple op-code describing these graphics will > ever exist. As a result, the driver might end up with a large bitmap with a > masking region or, worse, lots of little gradually colored polygons or rects > with masks. There is no state communicated across driver calls, in the > latter case, the driver couldn't possibly hope to reassemble these regions > as a single shaded polygon, so the DWF ends up with lots of rectangles in > the best case or lots of images in the worst. This is one of the main > reasons Autodesk discourages use of the DWFWriter for applications that can > export DWF natively, those will always produce smaller DWF with the highest > possible fidelity. > > hth, > > > g > > "Scott Sheppard" wrote in message > news:40d9b293$1_1@newsprd01... > > I don't think they want to compete against PDF for nonCAD. They want CAD > > data to stay in DWF, so they can do intelligent processing on the objects. > I > > think DWF Composer and DWF Writer are good for situations where you have > 99 > > DWGs and 1 Word DOC. You can make one DWF with all 100 items. If you have > 99 > > DOCs and 1 DWG, even Autodesk would probably recommend that you make a PDF > > for the Word parts and one small DWF for the DWG. People in the newsgroup > > seem to be apologetic when they mention PDF, e.g., "I'm sorry - I have to > > use it.", but they shouldn't be. IMHO Autodesk is adamant about CAD data > NOT > > going to PDF. For other types of data, I don't think they care. > > > > "Rodney McManamy - CADzation" wrote in message > > news:40d97b23_2@newsprd01... > > > The DWF format is optimized for AutoCAD drawings. What we have noticed > is > > > that anything from Word or Excel that uses gradiant fills, Word Art, > fancy > > > text, or lot's of graphics does not convert well with the DWF Writer and > > is > > > typically as you said 3 or more times larger. The PDF on the other hand > > is > > > optimized for Word style documents and small format but doesn't > understand > > > shx fonts so it's larger on AutoCAD drawings. > > > > > > The DWF Writer is still fairly new (and was developed mainly to support > > > Revit and other non-AutoCAD CAD applications) and I'm sure will get > better > > > at office documents because it's going to have to if they want it to > > really > > > compete against the PDF. In the real world it's about more than just > > > AutoCAD drawings that need to go to the client. > > > > > >
*David Metcalf
Message 7 of 17 (109 Views)

Re: Word Docs

06-24-2004 08:45 AM in reply to: *David Metcalf
Thank you guys, all this discussion was enlightening and help me articulate the purpose of DWF for design data vs PDF. David "Rodney McManamy - CADzation" wrote in message news:40dad9ec$1_1@newsprd01... > I think the problem really comes back to Autodesk's own marketing which has > been educating the users by marketing the DWF against the PDF. It's like > Ford marketing an Escort against a Chevy Pickup. No doubt the Escort get's > better mileage but try to put a 4x8 sheet of plywood in it. > > In my opionion where DWF will end up being the choice is where you are going > to need intelligent data downstream. PDF if you just need to view and print > but DWF if you need to view, plot, measure, or view intelligent data. Or if > you are working mainly with vector CAD data. > > And users also have to realize that the DWF Writer was created to support > the Autodesk apps that don't have direct DWF output. It's no easy task > printing every Windows application to a hybrid vector/raster format. There > are PDF companies that have been working on this (and only this) for years > and they still aren't perfect and they charge you for it. Adobe's own > driver doesn't print worth a darn from Illustrator 10 but Distiller usually > works pretty well or you can save directly to it. > > > -- > Rodney McManamy > President > CADzation > ------------------------- > rmcmanamy@cadzation.com > ------------------------- > 518 South Route 31 Suite 200 > McHenry, IL 60050 > www.cadzation.com > Providing Industrial Strength > PDF & DWF Solutions to the > Global CAD Marketplace. > > "Garrick Evans" wrote in message > news:40d9c2bf$1_1@newsprd01... > > Scott is right on - DWF is not intended for Office documents just as PDF > is > > not intended for design data. DWFWriter was designed to capture design > data > > from applications that do not export DWF directly, in particular, however, > > no claim has ever been made that it supports (or ever will) Microsoft > > Office. One of the reasons for this is the nature of the graphics flow > > through GDI and the driver framework, in many cases items like those > > mentioned previously ultimately arrive at the driver as a bitmap. Take > the > > case of the gradient fill. This is easy to do in a W2D stream, however, > > even though there is a DrvGradientFill() driver hook, no Office > application > > will EVER invoke it, so no simple op-code describing these graphics will > > ever exist. As a result, the driver might end up with a large bitmap with > a > > masking region or, worse, lots of little gradually colored polygons or > rects > > with masks. There is no state communicated across driver calls, in the > > latter case, the driver couldn't possibly hope to reassemble these regions > > as a single shaded polygon, so the DWF ends up with lots of rectangles in > > the best case or lots of images in the worst. This is one of the main > > reasons Autodesk discourages use of the DWFWriter for applications that > can > > export DWF natively, those will always produce smaller DWF with the > highest > > possible fidelity. > > > > hth, > > > > > > g > > > > "Scott Sheppard" wrote in message > > news:40d9b293$1_1@newsprd01... > > > I don't think they want to compete against PDF for nonCAD. They want CAD > > > data to stay in DWF, so they can do intelligent processing on the > objects. > > I > > > think DWF Composer and DWF Writer are good for situations where you have > > 99 > > > DWGs and 1 Word DOC. You can make one DWF with all 100 items. If you > have > > 99 > > > DOCs and 1 DWG, even Autodesk would probably recommend that you make a > PDF > > > for the Word parts and one small DWF for the DWG. People in the > newsgroup > > > seem to be apologetic when they mention PDF, e.g., "I'm sorry - I have > to > > > use it.", but they shouldn't be. IMHO Autodesk is adamant about CAD data > > NOT > > > going to PDF. For other types of data, I don't think they care. > > > > > > "Rodney McManamy - CADzation" wrote in message > > > news:40d97b23_2@newsprd01... > > > > The DWF format is optimized for AutoCAD drawings. What we have > noticed > > is > > > > that anything from Word or Excel that uses gradiant fills, Word Art, > > fancy > > > > text, or lot's of graphics does not convert well with the DWF Writer > and > > > is > > > > typically as you said 3 or more times larger. The PDF on the other > hand > > > is > > > > optimized for Word style documents and small format but doesn't > > understand > > > > shx fonts so it's larger on AutoCAD drawings. > > > > > > > > The DWF Writer is still fairly new (and was developed mainly to > support > > > > Revit and other non-AutoCAD CAD applications) and I'm sure will get > > better > > > > at office documents because it's going to have to if they want it to > > > really > > > > compete against the PDF. In the real world it's about more than just > > > > AutoCAD drawings that need to go to the client. > > > > > > > > > > > >
*MichaelK
Message 8 of 17 (109 Views)

Re: Word Docs

07-16-2004 05:38 PM in reply to: *David Metcalf
PDF seems to be getting a bad rap. Autodesk choose to create their own standard (probably to give us one more thing to upgrade every year) rather than working with Adobe. Bentley has proven that it can and does allow you to put as you said "a 4x8 sheet of plywood in it" and maybe the file is slightly larger but it is also their first stab at it. The PDF format is only going to get better and I only hope Autodesk will not ignore it when it catches up. It already handles layers, xrefs, searchable text, plotting, intelligent links and security and from what I heard it will soon handle measuring and much more. BTW, MicroStation also writes a PDFs directly from their product without the use of a distiller, heck you can even create a PDF of DWG files as well. Just my two cents... "Rodney McManamy - CADzation" wrote in message news:40dad9ec$1_1@newsprd01... > I think the problem really comes back to Autodesk's own marketing which has > been educating the users by marketing the DWF against the PDF. It's like > Ford marketing an Escort against a Chevy Pickup. No doubt the Escort get's > better mileage but try to put a 4x8 sheet of plywood in it. > > In my opionion where DWF will end up being the choice is where you are going > to need intelligent data downstream. PDF if you just need to view and print > but DWF if you need to view, plot, measure, or view intelligent data. Or if > you are working mainly with vector CAD data. > > And users also have to realize that the DWF Writer was created to support > the Autodesk apps that don't have direct DWF output. It's no easy task > printing every Windows application to a hybrid vector/raster format. There > are PDF companies that have been working on this (and only this) for years > and they still aren't perfect and they charge you for it. Adobe's own > driver doesn't print worth a darn from Illustrator 10 but Distiller usually > works pretty well or you can save directly to it. > > > -- > Rodney McManamy > President > CADzation > ------------------------- > rmcmanamy@cadzation.com > ------------------------- > 518 South Route 31 Suite 200 > McHenry, IL 60050 > www.cadzation.com > Providing Industrial Strength > PDF & DWF Solutions to the > Global CAD Marketplace. > > "Garrick Evans" wrote in message > news:40d9c2bf$1_1@newsprd01... > > Scott is right on - DWF is not intended for Office documents just as PDF > is > > not intended for design data. DWFWriter was designed to capture design > data > > from applications that do not export DWF directly, in particular, however, > > no claim has ever been made that it supports (or ever will) Microsoft > > Office. One of the reasons for this is the nature of the graphics flow > > through GDI and the driver framework, in many cases items like those > > mentioned previously ultimately arrive at the driver as a bitmap. Take > the > > case of the gradient fill. This is easy to do in a W2D stream, however, > > even though there is a DrvGradientFill() driver hook, no Office > application > > will EVER invoke it, so no simple op-code describing these graphics will > > ever exist. As a result, the driver might end up with a large bitmap with > a > > masking region or, worse, lots of little gradually colored polygons or > rects > > with masks. There is no state communicated across driver calls, in the > > latter case, the driver couldn't possibly hope to reassemble these regions > > as a single shaded polygon, so the DWF ends up with lots of rectangles in > > the best case or lots of images in the worst. This is one of the main > > reasons Autodesk discourages use of the DWFWriter for applications that > can > > export DWF natively, those will always produce smaller DWF with the > highest > > possible fidelity. > > > > hth, > > > > > > g > > > > "Scott Sheppard" wrote in message > > news:40d9b293$1_1@newsprd01... > > > I don't think they want to compete against PDF for nonCAD. They want CAD > > > data to stay in DWF, so they can do intelligent processing on the > objects. > > I > > > think DWF Composer and DWF Writer are good for situations where you have > > 99 > > > DWGs and 1 Word DOC. You can make one DWF with all 100 items. If you > have > > 99 > > > DOCs and 1 DWG, even Autodesk would probably recommend that you make a > PDF > > > for the Word parts and one small DWF for the DWG. People in the > newsgroup > > > seem to be apologetic when they mention PDF, e.g., "I'm sorry - I have > to > > > use it.", but they shouldn't be. IMHO Autodesk is adamant about CAD data > > NOT > > > going to PDF. For other types of data, I don't think they care. > > > > > > "Rodney McManamy - CADzation" wrote in message > > > news:40d97b23_2@newsprd01... > > > > The DWF format is optimized for AutoCAD drawings. What we have > noticed > > is > > > > that anything from Word or Excel that uses gradiant fills, Word Art, > > fancy > > > > text, or lot's of graphics does not convert well with the DWF Writer > and > > > is > > > > typically as you said 3 or more times larger. The PDF on the other > hand > > > is > > > > optimized for Word style documents and small format but doesn't > > understand > > > > shx fonts so it's larger on AutoCAD drawings. > > > > > > > > The DWF Writer is still fairly new (and was developed mainly to > support > > > > Revit and other non-AutoCAD CAD applications) and I'm sure will get > > better > > > > at office documents because it's going to have to if they want it to > > > really > > > > compete against the PDF. In the real world it's about more than just > > > > AutoCAD drawings that need to go to the client. > > > > > > > > > > > >
*Shaan Hurley, Autodesk, Inc.
Message 9 of 17 (109 Views)

Re: Word Docs

07-17-2004 03:26 PM in reply to: *David Metcalf
Michael, PDF is good for Word documents, and it should focus on what it is good for being an old postscript based format. When it comes to design documents the DWF format beats PDF hands down in more ways than just file size and Michael it is not just a "slight file size difference". Bentley only chose to use PDF with Adobe as they could not have swallowed their pride for the betterment of their own customers. Bentley also had to partner with someone because they had no electronic format solution. Even so, you can still produce a DWF from Bentley products and many others using the free and available DWFWriter printer driver. You can create PDF files from AutoCAD already so why reinvent the wheel inside AutoCAD when there are hundreds of PDF printer drivers and applications to do so. So when discussing design documents it is not PDF that is in the lead, it is DWF that wins. If the discussion were on what is best for text documents then PDF wins. PDF is only more accepted because of its word based documentation background. Do you really need to teach the old PDF dog a new trick or ability for design document data? It is about choice whether it be PDF or DWF and I just show the strengths of the DWF for the design documentation output. Now if Bentley customers were to ask the same questions and DWF related posts, in most cases they either get deleted by PhilTer or a snide and rude reply containing "DWF is proprietary", which is unfortunate in that they take the one size fits all camp. There is no need to buy anything with DWF, and there are full API and toolkits for free with no strings. There is no one size or format that fits all data types. What you need to do is use the best suited format for the task at hand. http://autodesk.blogs.com/between_the_lines/dwf_it/index.html http://autodesk.blogs.com/between_the_lines/2004/06/more_dwf_vs_pdf.html Cheers, -Shaan http://autodesk.blogs.com/between_the_lines/ "MichaelK" wrote in message news:40f87513$1_1@newsprd01... > PDF seems to be getting a bad rap. Autodesk choose to create their own > standard (probably to give us one more thing to upgrade every year) rather > than working with Adobe. Bentley has proven that it can and does allow you > to put as you said "a 4x8 sheet of plywood in it" and maybe the file is > slightly larger but it is also their first stab at it. > > The PDF format is only going to get better and I only hope Autodesk will not > ignore it when it catches up. It already handles layers, xrefs, searchable > text, plotting, intelligent links and security and from what I heard it will > soon handle measuring and much more. BTW, MicroStation also writes a PDFs > directly from their product without the use of a distiller, heck you can > even create a PDF of DWG files as well. > > Just my two cents...
*MichaelK
Message 10 of 17 (109 Views)

Re: Word Docs

07-19-2004 10:47 AM in reply to: *David Metcalf
Shaan, I come from a duel (Bentley and AutoDesk) shop and my bent is coming from an IT position. I don't believe the rhetoric that every task needs its own specific tools, yes sometimes they do but it is not always bad. Taken with that approach, Windows wouldn't do have the things it does today. Product Innovation should not be hampered by limitations the industry decides for us. Personally, I'm tired of having to install specific apps just to add a few feature that we may or may not ever use. See comments below... "Shaan Hurley, Autodesk, Inc." wrote in message news:40f9a777_2@newsprd01... > Michael, > > PDF is good for Word documents, and it should focus on what it is good for > being an old postscript based format. When it comes to design documents the > DWF format beats PDF hands down in more ways than just file size and Michael > it is not just a "slight file size difference". Bentley only chose to use > PDF with Adobe as they could not have swallowed their pride for the > betterment of their own customers. Bentley also had to partner with someone > because they had no electronic format solution. Even so, you can still > produce a DWF from Bentley products and many others using the free and > available DWFWriter printer driver. I went to Bentley's User Conference in May and they did swallow their pride, they choose to better their solutions on a format that nearly everyone in the world has adopted and accepted. They actually have a proprietary format solution called DPR (which has been around even before DWF was even a concept) that could have been enhanced to take on more functionality but they actually choose PDF because it is what their USERS wanted and Adobe was willing to help make it a reality. > > You can create PDF files from AutoCAD already so why reinvent the wheel > inside AutoCAD when there are hundreds of PDF printer drivers and > applications to do so. You can but you don't have much options or control, besides these all use distillers and are not nearly as functional as Bentley's writer. I sound like I am pro Bentley but I actually am quite neutral but this is a subject that I have a problem with when it comes to AutoDesk. You guys like to make everything proprietary and much like Microsoft, you want us to upgrade every other year by taking out functionality like saving to an older version for instance. It is not a limitation of the software to save back to vesion 11 but rater a deliberate choice that forces us to upgrade. By making the reader free it sounds like you have a great solution but IF it because a standard in the industry your company will then have a larger base to sell the composer to. It all comes back to money not pride... > > So when discussing design documents it is not PDF that is in the lead, it is > DWF that wins. If the discussion were on what is best for text documents > then PDF wins. PDF is only more accepted because of its word based > documentation background. Do you really need to teach the old PDF dog a new > trick or ability for design document data? If they, Adobe, succeeds at creating a rich AEC content PDF (which their representative at the Bentley conference says they are) then what is the difference? Just because you don't want to spend the time to teach a dog new tricks doesn't mean it can't be as good or better, it just depends on the profesional that is doing the training. Heck, looking at the team of Adobe has on this they may even put out a better solution they DWF... > > It is about choice whether it be PDF or DWF and I just show the strengths of > the DWF for the design documentation output. Now if Bentley customers were > to ask the same questions and DWF related posts, in most cases they either > get deleted by PhilTer or a snide and rude reply containing "DWF is > proprietary", which is unfortunate in that they take the one size fits all > camp. As an IT person I tend to agree with Bentley on this one... > > There is no need to buy anything with DWF, and there are full API and > toolkits for free with no strings. Time is money and if PDF can provide the tools for free and most of my clients have the reader already installed then I would choose PDF... > > There is no one size or format that fits all data types. > What you need to do is use the best suited format for the task at hand. > > http://autodesk.blogs.com/between_the_lines/dwf_it/index.html > http://autodesk.blogs.com/between_the_lines/2004/06/more_dwf_vs_pdf.html > > Cheers, > -Shaan > http://autodesk.blogs.com/between_the_lines/ > > > "MichaelK" wrote in message > news:40f87513$1_1@newsprd01... > > PDF seems to be getting a bad rap. Autodesk choose to create their own > > standard (probably to give us one more thing to upgrade every year) rather > > than working with Adobe. Bentley has proven that it can and does allow > you > > to put as you said "a 4x8 sheet of plywood in it" and maybe the file is > > slightly larger but it is also their first stab at it. > > > > The PDF format is only going to get better and I only hope Autodesk will > not > > ignore it when it catches up. It already handles layers, xrefs, > searchable > > text, plotting, intelligent links and security and from what I heard it > will > > soon handle measuring and much more. BTW, MicroStation also writes a PDFs > > directly from their product without the use of a distiller, heck you can > > even create a PDF of DWG files as well. > > > > Just my two cents... > > >
Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Need installation help?

Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.