This link has been bookmarked by 34 people . It was first bookmarked on 24 Feb 2007, by Paul Wray.
-
21 Oct 11
-
08 Aug 11
-
27 Jul 11
-
09 Dec 10
-
15 Oct 10
-
27 Sep 10
-
A document containing such an expression should probably contain, near the beginning, a statement like “In this document, the circumflex character ^ is used to indicate exponentiation, i.e. raising to a power.”
-
-
29 Aug 10
David RobertsHow to present mathematical expressions using a language that has so little markup for them? You often need to resort to images, but if you need just some special symbols or simple expressions, something could be done in HTML – perhaps assisted with st
-
29 Oct 08
-
21 Aug 08
-
23 Jul 08
-
11 Jun 08
-
07 May 08
-
04 Feb 08
-
01 Dec 07
-
26 Nov 07
-
06 Sep 06
-
26 Apr 06
-
17 Jan 06
-
26 Aug 05
-
Line breaks as problems Line breaks are often undesirable inside expressions, but Web browsers generally treat every space as a potential line break position. There are several ways to deal with this: * Using the no-break space character (presentable using ) instead of a normal space. * Using the nonstandard but rather widely supported nobr markup around a string that should be kept together. Example:
a + b + c . (You might avoid the problem by writing just a+b+c, but spaces give a more “airy†presentation.) * Using the nowrap attribute in a td (or th) element. This is useful if it’s OK to prevent all line breaks inside a table cell (except line breaks explicitly requested using br tags). * Using white-space:nowrap (or maybe white-space:pre) in CSS. Typically this means that you would use something like the following: in HTML: 42 m and in CSS: .q { white-space: nowrap; } It is debatable whether it is more logical to use the CSS way than no-break spaces. In a sense, it is a structural property of an expression like “42 m†that its two parts belong closely together, so that in any normal presentation, there should be no line break between them, or any pause in speech presentation. On the practical side, no-break spaces surely work more reliably, partly because browser support for the white-space is still limited, partly due to general CSS caveats. Note that the nobr markup is the only sure cure against IE’s tendency to treat every hyphen as a potential line break opportunity, even in a string like a-b or -a! But if you have decided to use “special charactersâ€, then you might use the real minus sign, −, instead of hyphen, and that would avoid the hyphen problem. See Dashes and hyphens. There are even more oddities in IE: it may also treat any of -()[]{}«»%°·\ as indicating a potential line break position (before or after, depending on the character). Thus, it may well split “sin(x)â€
-
-
20 May 05
-
26 Aug 04
-
28 Jul 04
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.