Re: non breaking space
Re: non breaking space
- Subject: Re: non breaking space
- From: Bill Briggs <email@hidden>
- Date: Tue, 20 Jul 2004 14:52:57 -0300
At 9:12 AM -0700 20/07/2004, Dan McCann wrote:
Paul Berkowitz wrote:
Hmmm. I always knew 202 as "option-space" (that's how it's typed on a US
keyboard). I guess that's the same thing. I certainly know contexts where,
unlike regular space, it doesn't get trimmed (although Apple's Address Book
does trim it from the beginning and end of contact names).
In HTML-speak, when you see "nbsp;" is it referring to 202 or to a regular
space 32? I always assumed the latter.
>And its Unicode is 160 = 00A0 ? I see that's even called NO-BREAK SPACE. OK,
thanks, Emmanuel
I tried 202 (option-space) in my efforts. As far as I can tell it's an
mspace; that is, it breaks like a regular space but is wider than a regular
space.
I don't think so. 202 is, and acts like a non-breaking space in
FrameMaker and Eudora, and can be identified as such in the pallet in
Tex-Edit Plus when copied and pasted from those two applications to
TEP. There is a behaviour of the non-breaking space that may make it
appear as a bit wider than a normal space, and that's because of the
way it's treated in the kerning table and the way type is handled in
justification of a line of text in a given application. It's
definitely not an em space (not even wide enough to be an en space).
For example, in FrameMaker when you type text in proportional type
(which is most of the time), before you get a line wrap the type will
auto-adjust word and letter spacing (within preset extremes) to
justify itself. When this happens and letter spacing shrinks, the
normal space character, 32, will shrink as do the other spacings
between other characters (and in accordance with kerning table). But
if you put a non-breaking space in there (Opt-space), they remain a
fixed width, no matter how much the line of text compresses or
stretches. It's fixed width, and in a line of text that compresses
spacing to justify, it will appear wider. You'd likely see the same
effect in most word processors.
The weird thing is, every reference I looked at calls 202 a non
breaking space. As far as I know nbsp; refers to 160.
As far as HTML is concerned, the reason you use a non-breaking space
is because the HTML parser will ignore multiple normal spaces
(multiple 32 or 0x20) and collapse them to a single space. So the
nbsp character forces the parser to add in a space for each instance
of a non-breaking one. When you copy any text from the browser and
paste it to your text editor, if there were nbsp chars, they come
through as nbsp too, which may cause odd behaviour if you're not
expecting this. You can verify this easily using the char
identification in Tex-Edit.
- web
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.