Diameter symbol showing as \U+2

[Jonathan Pitt]

Hi all, had a search through the forum but could only find problems relating to diameter symbols showing as question marks so my problem seems slightly different.

Basically I have created a drawing in 2008 LT, it is a line diagram showing duct routes of an HVAC systrem in a ship. To denote the size of the duct I have created a multileader with a diameter symbol in using %%C. Ø125 for 125 diameter duct.

We have a few different versions of AutoCAD (2004 LT and 2007 Mechanical) and these multileaders are fine on them (albeit, they are proxy objects so we can't do anything with them!) However, one station using 2007 Mechanical, we are having a problem with.

The symbols show up fine when the drawing is initially opened, but after saving to a different file name then reopened, what was 'Ø125' now becomes '\U+2'. This new drawing is fine when I open it in 2008 LT, but older versions will then only see the incorrect detail?

Any ideas would be gratefully accepted.

Many thanks,

Jonathan.

[drdesignz]

Try addiding 205 to \U+2:

\U+2205

[Jonathan Pitt]

In the 2007 version the multilines are proxy objects so they are not editable.

I tried saving them using the unicode shortcut in 2008 LT but the process of saving and reopening in 2007 still has the same effect and they still change into just \U+2.

Because we have other machines where this problem is not happening I am guessing there is a setting somewhere on the problem machine?

[RobertB]

Make sure everyone is using Unicode-compliant fonts. I'm betting the text style is being substituted for a font that is not Unicode-compliant.

[Jonathan Pitt]

I did spot a section in the help files about setting alternative fonts using the fontalt command. I'll give his a go and set it to RomanS which is the font I am using and see how it goes.

Cheers Richard

Edit, tried setting the problem computer to altfont of romans.shx and that didn't work. Is that what you meant Richard, or am I barking up the wrong tree there?

[cadtag]

compare the dates for the font files on the machines.. it's possible an older version (non-Unicode) is being used. If the date if from the last century, it's not unicode