Sans Serif Won't Word Wrap

[chemexchange]

In Office 2007, when I start a new document and select the Sans Serif font it
will not word wrap. When I'm typing and get close to the right margin, it
breaks the word apart instead of carrying the whole word to the next line.
All other fonts work fine. Any ideas?

 

[Tom Ferguson]

Can and will you tell us exactly which font it is: it's name, filename,
source?

There are a few fonts "out there" whose font files incorrectly identify them
as "symbol" fonts. Symbol fonts are not intended to be used for text;
therefore, line breaks are allowed within character groups. That allows line
breaks within words.

The solution is to use another font for the text. Alternately, you could
open the font file in a font editor and change that designation. Then,
remake the font file.

Tom
MSMVP 1998-2007

 

[chemexchange]

I'm using WinXP SP2 and in the Windows\Font directory the name of the font is
SansSerif (True Type). The name of the file is sanss__.ttf, with a file size
of 53k and date of 9/18/1996. I ran the TweakUI program to repair the Font
folder hoping that would fix it, but no luck. I can use any other font,
including Microsoft Sans Serif font and it works fine. Just not regular ole
sans serif. Is there a particular reason some fonts in the Windows\Font
folder have multiple underscores in their file naming?

 

[Tom Ferguson]

So far, I have not been able to trace a font with the file name sanss___.ttf
to test.

Are there files ion the directory for italic, bold, or bold italic versions
of the font?

----------

I am not surprised that "fixing" the font folder did not help.

A patient goes in his doctor's office. When the doctor entered the examining
room, the patient said, "When I raise my arm over my shoulder like this, my
shoulder hurts." After a few moments contemplation, the doctor replied,
"Don't raise your arm like that."

Translation: Don't use the font. (Unless you have and know how to use a font
editor to fix the file.)

As for the underscores: in the days of the Microsoft Disk Operating System
(MSDOS), used from the days of the first IBM PC types until Windows NT
platforms became common, filenames had 11 characters in 8.3 format. The
first 8 characters specified the unique file name and the three characters
after the dot indicated file type. E.g. doc for Microsoft Word files, exe
for executable program files, &c


Tom
MSMVP 1998-2007

 

[CyberTaz]

Do you - or did you ever - have AutoCad installed? What you're attempting to
use (I believe) is a character construction tool used by that program... If
you want the "boring details" have a look here:

http://www4.dogus.edu.tr/bim/bil_kay/pak_prog/autocad14/ch16.htm

I'm not even sure why it should show up in Word's font list, but I'd
definitely stay away from it

HTH |:>)
Bob Jones
[MVP] Office:Mac

 

[chemexchange]

CyberTaz,

Thanks for the answer. That is exactly what happened. The way this came
about was one of our professors at the university was submitting a proposal
to an agency. The agency required the use of the "Sans Serif" font. When
the prof tried using the font he got the word wrap problem. I saw the
Microsoft Sans Serif font in the list, tried it and it worked fine. So, I
just told him to start using that and that I seriously doubted the agency
would deny his submission on using the Microsoft Sans Serif font.

 

[Tom Ferguson]

Well, while I'm glad you reached a satisfactory solution, I am still very
puzzled by various aspects of this. Not that my puzzlement need worry
anyone.

Perhaps the agency required a Sans Serif font as opposed to the Sans Serif
font. In which case there are many fonts that would be acceptable to them:
e.g. Frutiger, Futura, Avenir, Universe.

There is a Microsoft Sans Serif but note that there is no bold, italic or
bold italic file for it so those styles are produced by the rasteriser if
requested. The result might not be ideal on all printers.

I did check through the AutoCad connection but made no headway on it.
Cybertaz mentioned his doubt about a tool showing up on the font list as
opposed to a font. In this we share.

I have a vague recollection of a font, with a similar if not the same name,
supplied as a sample font with a font creation/editing tool. Perhaps there
is a connection there.

Anyway, aside from curiosity, no matter.

Tom
MSMVP 1998-2007

 

[chemexchange]

Honestly, I just use whatever the default font is in Word. So, personally,
I've never had any font problems or even changed from the default font for I
don't know how many untold years. The professor having the problem came to
me in a panic. He just needed the sans serif font to work. Of course, I had
no idea what the sans serif font was, except that it meant "without serif".

He had started a doc and while typing noticed it wasn't word wrapping. He
then came to me with the problem. He emailed me a copy of his doc, so I
opened it on my computer and sure enought was having the same problem. If
you tried to highlight the existing text and change it to another font
(didn't matter which one), all existing text would turn to ascii characters!

I checked the Windows\Font folder and there are four different sans serif
fonts listed:

sanss___.ttf
sanssb__.ttf
sanssbo_.ttf
sanssso__.ttf

I'm confused at to what happened also, but I told the prof to use any sans
serif font and not "the sans serif" font listed in the drop down list.

Thanks for all your efforts.

 

[Tom Ferguson]

Thanks for the additional information.

In particular, "If you tried to highlight the existing text and change it
to another font (didn't matter which one), all existing text would turn to
ascii characters!" indicates a problem that is usually referred to as an
encoding issue. As you might be aware, as you keyboard, the text is stored
as a series of codes. These codes are mapped to glyphs in a font file
according to a rule set. In certain circumstances which are most commonly
seen if a document is created in one language version and rendered on
another, problems occur. I have no idea what triggered the problem in this
case. However, there is a macro available from the Microsoft Download site
that fixes that problem. It fixes the encoding and changes ever font
occurrence to Arial. However, after the repair, you can then successfully
select any font you want.
http://www.microsoft.com/Downloads/...b9-a6b9-4618-9514-ec0c4a244570&displaylang=en

The macro was intended for a particular situation and a particular Word
version; however, it is useful for other near-parallel situations.

The Microsoft Sans Serif font has the file name micross.ttf. If you right
mouse click on the file name, you can see the maker's name. I would be
interesting to know what that is for the file set you list.

Glad to be of assistance where and if possible.

Tom
MSMVP 1998-2007