Custom Text Style: Still a Prob

I am having a problem maintaining my custom text font definitions. Here's the steps to reproduce this:

(1) Open a .dwg file from scratch

(2) Insert an attributed block that contains attributes' that have custom text styles

(3) The custom text styles are:
(3a) based on standard AutoCAD fonts
(3b) defined in the original title block file
(3c) not defined in the destination

I was under the impression that the custom text fonts definitions would be unaffected when inserted into any AutoCAD file as long as the custom text fonts were based on standard AutoCAD fonts.

How do I set up my attributes in the block or source file or....etc so as to maintain my custom text fonts appearance when transferred to a new file?

Thanks,
Clint Hill

 

Step one is really to create the text style and define the attribute in the
external drawing that forms the block.

Command: -style
Enter name of text style or [?] <Standard>: Test
New style.
Specify full font name or font filename (TTF or SHX) <txt>: RomanD
Specify height of text <0.0000>:
Specify width factor <1.0000>:
Specify obliquing angle <0>:
Display text backwards? [Yes/No] <N>:
Display text upside-down? [Yes/No] <N>:
Vertical? <N>
"Test" is now the current text style.

Command: -attdef
Current attribute modes: Invisible=N Constant=N Verify=N Preset=N
Enter an option to change [Invisible/Constant/Verify/Preset] <done>:
Enter attribute tag name: Test
Enter attribute prompt:
Enter default attribute value: 123
Current text style: "Test" Text height: 0.2000
Specify start point of text or [Justify/Style]: 0,0
Specify height <0.2000>:
Specify rotation angle of text <0>:

Command: saveas

I saved that as TestBlk in my Temp folder.

(2) Command: _qnew

Command: -style
Enter name of text style or [?] <Standard>: ?
Enter text style(s) to list <*>:
Text styles:
Style name: "Standard" Font files: txt
Height: 0.0000 Width factor: 1.0000 Obliquing angle: 0
Generation: Normal
Current text style: "Standard"

(3) Command: -insert
Enter block name or [?]: TestBlk
Specify insertion point or [Scale/X/Y/Z/Rotate/PScale/PX/PY/PZ/PRotate]: 0,0
Enter X scale factor, specify opposite corner, or [Corner/XYZ] <1>:
Enter Y scale factor <use X scale factor>:
Specify rotation angle <0>:

Command: -style
Enter name of text style or [?] <Standard>: ?
Enter text style(s) to list <*>:
Text styles:
Style name: "Standard" Font files: txt
Height: 0.0000 Width factor: 1.0000 Obliquing angle: 0
Generation: Normal
Style name: "Test" Font files: RomanD.shx
Height: 0.0000 Width factor: 1.0000 Obliquing angle: 0
Generation: Normal
Current text style: "Standard"


See, it works. The "Test" style *is* using RomanD in the new drawing where
the style didn't exist before.


--
R. Robert Bell


I am having a problem maintaining my custom text font definitions. Here's
the steps to reproduce this:

(1) Open a .dwg file from scratch

(2) Insert an attributed block that contains attributes' that have custom
text styles

(3) The custom text styles are:
(3a) based on standard AutoCAD fonts
(3b) defined in the original title block file
(3c) not defined in the destination

I was under the impression that the custom text fonts definitions would be
unaffected when inserted into any AutoCAD file as long as the custom text
fonts were based on standard AutoCAD fonts.

How do I set up my attributes in the block or source file or....etc so as to
maintain my custom text fonts appearance when transferred to a new file?

Thanks,
Clint Hill

 

IMHO, nothing to do w/ the creation of attributes, or standard AutoCAD
fonts...

in the options/files/support search path, make sure that the path of the
custom font
is above all the other folders, and make sure you are not working in a
folder that
contains that custom font file ,current directory, or the acad.exe folder

HTH
mark

unaffected when inserted into any AutoCAD file as long as the custom text
fonts were based on standard AutoCAD fonts.

to maintain my custom text fonts appearance when transferred to a new file?

 

Mark,

Clint stated that the new style was based on a standard AutoCAD font, so
that is not the issue.

--
R. Robert Bell



IMHO, nothing to do w/ the creation of attributes, or standard AutoCAD
fonts...

in the options/files/support search path, make sure that the path of the
custom font
is above all the other folders, and make sure you are not working in a
folder that
contains that custom font file ,current directory, or the acad.exe folder

HTH
mark

unaffected when inserted into any AutoCAD file as long as the custom text
fonts were based on standard AutoCAD fonts.

to maintain my custom text fonts appearance when transferred to a new file?

 

robert,

he could have same name of fonts, but different content, at different
locations
on the system, which will create the problem clint is talking about...
he might be creating the attributes in a folder containing "romans.shx"
of different definitions than the one autocad stores in its "romans.shx" in
its search path,
the current working directory takes precedence, so you will see the results
differently.

i suggest clint searches (system search) of the font file he is using, and a
(findfile ...)
of the font from inside autocad, at creation time, and insertion time.

mark

 

Mark & Ed,

I wish I could have joined in sooner! Very good points and content. I was really banking on AutoCAD coming through for me in defining custom styles from common AutoCAD fonts. This is pretty 'hairy' stuff for someone who has a low risk tolerance and an aversion to 'egg on the face'.

Ed, I thank you for sharing the excellently detailed test case here. Your points are the same as the answer I received from Subscription Tech Support.

IMHO, of course, this particular case is ***may be*** related to support path issues. As I stated earlier things have been in flux with the new hardware and software.
We have the network version of AutoCAD. This all occurred on machine that referenced our old license server. The installation (of AutoCAD) that references this old server is in question. Some of the AutoCAD Mechanical's support files are not being found.

That's why we recently moved the license to our new server install and our AutoCAD is referencing a different directory. Mine is the only seat installed from it and working OK at present. So, that's why I'm leaning more toward it being a support file issue in this case. Who knows!!!??

I'll do more tests when other get re-installed from the new server and let you know what the verdict is for our edification and for my sanity. ....GEeeeezzz!!!!

Thanks,
Clint