Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Fonts in NX5 and above 1
- Thread starter nmiltner
- Start date
$z will show as the reg trademark symbol.
It may or may not work in the font that you are using - change the font of the "$z" to "blockfont" if it is not showing up correctly
a tip: do a search in Help > Documentation > enter "symbols and text control characters"
and what you get should help you
It may or may not work in the font that you are using - change the font of the "$z" to "blockfont" if it is not showing up correctly
a tip: do a search in Help > Documentation > enter "symbols and text control characters"
and what you get should help you
-
1
- #3
JohnRBaker
Mechanical
The attached 'crib-sheet' might prove useful.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
As an added note to the crib sheet.
The crib sheet is ONLY valid with Blockfont as supplied by Siemens.
John has posted a modifed Blockfont file that has additional characters that are not on the crib sheet.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
The crib sheet is ONLY valid with Blockfont as supplied by Siemens.
John has posted a modifed Blockfont file that has additional characters that are not on the crib sheet.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
- Thread starter
- #6
- Thread starter
- #8
One more question on symbols and fonts. This time it pertains to attributes. If i put, for instance the $r in my attributes, for a diameter symbol, that are used in title blocks I actually get $r in the text line that is on my print. Any way around this?
To be more clear: attribute Gauge=$r .125
expected text line Ø .125
actual text line: $r .125
To be more clear: attribute Gauge=$r .125
expected text line Ø .125
actual text line: $r .125
I never realized that those "$" fonts cannot be used as the attributes that appear in the title block (or anyplace else). That is very interesting.
I am going to play around a bit to try to make it work, but I would love to hear if John Baker has a solution.
I am going to play around a bit to try to make it work, but I would love to hear if John Baker has a solution.
- Thread starter
- #11
Mickey,
I tried the <O> as well. That too isn't working.
Jerry,
Yes, they are ascii combinations. For instance, if your font is iso1, and you type alt+0176 you get ° (the degree symbol). You can find the alt combinations in windows character map. NOTE: not all characters are supported.
I tried the <O> as well. That too isn't working.
Jerry,
Yes, they are ascii combinations. For instance, if your font is iso1, and you type alt+0176 you get ° (the degree symbol). You can find the alt combinations in windows character map. NOTE: not all characters are supported.
JohnRBaker
Mechanical
An Attribute, when referenced by a note, is interpreted as a literal string. That is, the exact characters are inserted into the note exactly as they appear in the Attribute. They are NOT 'evaluated' as they are when you type them in directly. I suspect that if we DID 'evaluate' them, so that the control characters WERE interpreted AS control characters rather then just as a text string, that this could cause all sorts of problems since there would be no way of determining what the user was expecting. That is, which Attributes are to be treated exactly as they appear, and which ones would need to be 'evaluated'. At least when entering text directing into NX you can always override the control characters by typing in a double '$$'.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
JohnRBaker
Mechanical
Turns that there is a way of working around this, but you have to manually edit the text string which is used to reference the Attribute.
When you create the link to the attribute the string that is shown in the test editor will look something like...
<W@ATTRIBUTE_NAME>
...and the result will be non-evaluated. However if you were to edit it so that it was...
<W&@ATTRIBUTE_NAME>
...then it would be evaluated (the edit involved adding the '&'). I had forgotten about that until someone just reminded me of it.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
When you create the link to the attribute the string that is shown in the test editor will look something like...
<W@ATTRIBUTE_NAME>
...and the result will be non-evaluated. However if you were to edit it so that it was...
<W&@ATTRIBUTE_NAME>
...then it would be evaluated (the edit involved adding the '&'). I had forgotten about that until someone just reminded me of it.
John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
To an Engineer, the glass is twice as big as it needs to be.
- Thread starter
- #16
- Status