<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Protecting PDF drawings from AC18 in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255140#M39300</link>
    <description>I had considered this too, drawings were always able to be copied by tracing etc, the only difference is that now it is quicker &amp;amp; easier.&lt;BR /&gt;
Other programs have had the ability to explode or snap to pdf long before AC joined in.</description>
    <pubDate>Thu, 19 Mar 2015 22:17:41 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-03-19T22:17:41Z</dc:date>
    <item>
      <title>Protecting PDF drawings from AC18</title>
      <link>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255138#M39298</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi,&lt;BR /&gt;
&lt;BR /&gt;
So a question we are currently facing in the office with Archicad's latest PDF importing/exploding capabilities is that is it a bit too good at what it does. I'm sure most of your drawings go to a public database for council as ours do (saved as PDFs). What we are concerned about is the ability of other practices  to now easily "rip" a pdf for a very good base model and undercut a fee for the next stage of the job with the client.. Hence losing work and not ensuring a frustrating remodelling process for the other firm. We have tried Acrobat encryption which archicad manages to get around, and flattening the PDF to a raster file makes it too big for online submission.... &lt;BR /&gt;
&lt;BR /&gt;
Any thoughts would be greatly appreciated!&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 19 May 2023 20:12:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255138#M39298</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-19T20:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting PDF drawings from AC18</title>
      <link>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255139#M39299</link>
      <description>I think its fair to say that a lot of CAD users including your own office will have at some point accessed such files, protected or not, for possibly genuine reasons. AC's excellent PDF conversion isn't really the issue as you can still trace the original from vector or raster PDFs or even TIFFs and what you are asking is probably impossible to implement as you are effectively saying the drawings which are a matter of public record should be unreadable unless you have the permission of the author.&lt;BR /&gt;
&lt;BR /&gt;
Perhaps the ideal solution is to try and give your client best value so they don't go elsewhere for the next stage!</description>
      <pubDate>Thu, 19 Mar 2015 16:41:05 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255139#M39299</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2015-03-19T16:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: Protecting PDF drawings from AC18</title>
      <link>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255140#M39300</link>
      <description>I had considered this too, drawings were always able to be copied by tracing etc, the only difference is that now it is quicker &amp;amp; easier.&lt;BR /&gt;
Other programs have had the ability to explode or snap to pdf long before AC joined in.</description>
      <pubDate>Thu, 19 Mar 2015 22:17:41 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Protecting-PDF-drawings-from-AC18/m-p/255140#M39300</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-19T22:17:41Z</dc:date>
    </item>
  </channel>
</rss>

