 |
|
 |
Font translation
|
|
|
Posted by Jean-Guy on March 31, 2001:
For multiple lines of text from PCADD to ACAD try this:
Courier New Size 6 + 5 leading on PCADD shows as size 10, single line, on ACADD
Courier New Size 10 + 7 leading on PCADD shows as size 18, single line, on ACADD
Courier New Size 20 + 13 leading on PCADD shows as size 36, single line, on ACADD
The scale factor between True Type font on PCADD and PC_MONO_TEXT on ACADD seems to be about 1.75, so:
Size 6 x 1.75 = 10 on ACADD
Size 7 x 1.75 = 12 on ACADD
Size 8 x 1.75 = 14 on ACADD
Size 9 x 1.75 = 16 on ACADD
Don`t forget to add leading on Courier New TrueType if you don`t want to see a "sort of overlap" when convert to ACADD.
Virtual PC 4 works slow but fine with ACADD 2000
XREF ?Posted by Jeff on April 16, 2001 at 07:59:24:
I need an easy way to receive a base drawing comprised largely of xref files (about 20-30) xrefs! Is the only way to deal with this to have the sender bind them into the drawing? I would like to make it easy for people on both ends. Currently they send me a folder of all these dwg files.....
In Reply Posted by Jesse Thompson on April 16, 2001 at 09:52:26::
Yes, you do want the sender to bind all the Xrefs. They will be inserted into the AutoCad drawing as Blocks, which should translate into PC as groups. Try unchecking the "Explode Blocks to Original Layers" on the PowerCadd DWG import screen to keep the groups together...
If they do not bind the Xrefs, you will have a hell of a time getting all 20 individual DWG files to register correctly in PC.
The messy part is going to be the layering. Each Xref will get a string of text added in front of each layer, to keep every layer name unique in AutoCAD. You will most likely end up with hundreds of layers binding 20-30 xref's. The Purge Layers command is highly recommended.
Jesse Thompson
In Reply Posted by RandyM on April 16, 2001 at 11:35:51:
A note of caution here...we have received similar projects and all too often there are nested XREFs, that is, XREFs within XREF's and these do not bind to the master document unless individually bound first. I'm not sure if ACAD2000 can do this in one command but ACADR14 does not to my knowledge.
Posted by CJH on February 21, 2002 at 09:10:23:
WIth Acadd files newer than R14, and in particular if they have been created using Architectural Desktop, there are 'smart' wall elements that will not translate into Pcadd. Also, the newer Acadd files use a 'tabs' feature much like we use 'sheets' to switch from drawing page to page, which creates translation issues.
The solution to translating these files is:
1. Any xrefed files must be bound to the file you are translating.
2. Individual sheets or the entire model can be translated by first doing a 'wblock' command while in model space which will create a new file with xref's included, then open it, select all and explode 3 times: this will 'unsmart' the 'smart elements down to simple lines, circles, etc..
3. You can have your client using Acadd do this, but they will not like it as the select all and explode commands can take over 10 miniutes each time with a complex file even on a 1Ghz P3.If you do a lot of importing Acadd files you are best off to buy a decent PC for $1,500 and run Acadd LT for $500, then you can set up the files properly yourself-you also have the benefit of seing the clients drawing just as they do on the PC. You will also soon see why you get more done using Pcadd than your peers do using Acadd.
Posted by fjjRA on July 02, 2002 at 10:25:59:
Many material suppliers have details you can get or download in autocad EXE format... If you change the "EXE" to "ZIP" then drag to Suffit these files open in DWG format for importing into PC (follow Bullpen advice for importing)- trick works with Vectorworks and should work with PC with the DWG translator.
| clue us in on your hot AC*D shortcuts... |
