1088­h­g锡耶纳大学的主场是哪?叫什么?

&lt!ENTITY shy
CDATA "­" -- soft hyphen -->
&lt!ENTITY reg
CDATA "®" -- registered sign -->
- - - - - - - - - - - - - - -
Here, &amp#173 is still associated with CDATA in the standards, but
it is not clear whether its glyph should be rendered or not in implementations.
The bug has probably died by now, but the unexpected malfunctions
haven't started happening yet.
Finally, in HTML&4.01, most of the info about line-breaking and
hyphenation (outside of PRE, XMP and LISTING elements) is:
The BR element forcibly breaks (ends) the current line of text.
Prohibiting a line break
Sometimes authors may want to prevent a line break from occurring between two words.
The & entity (  or  ) acts as a space where user agents should not
cause a line break.
9.3.3 Hyphenation
In HTML, there are two types of hyphens: the plain hyphen and the soft hyphen. The plain hyphen
should be interpreted by a user agent as just another character. The soft hyphen tells the user agent
where a line break can occur.
Those browsers that interpret soft hyphens must observe the following semantics: If a line
is broken at a soft hyphen, a hyphen character must be displayed at the end of the first
line. If a line is not broken at a soft hyphen, the user agent must not display a hyphen
character. For operations such as searching and sorting, the soft hyphen should always be
In HTML, the plain hyphen is represented by the "-" character (&amp#45; or &amp#x2D;). The soft hyphen is
represented by the character entity reference & (&amp#173; or &amp#xAD;)
The bug is dead _ long live the bug.
What appears to have happened is somewhat like synecdoche, but not quite the same.
Reference to the whole by the name of a part _ all hands on deck
_ is usually an entertaining figure
of speech, and it is usually done on purpose.
The use of soft hyphen to refer to
hyphenation is merely soft thought _ a bit of linguistic driftwood that
has washed ashore so slowly that
nobody could be blamed for failing to notice it.
It is an accident that has placed
an intolerable burden on poor little &shy _ no wonder it hardly ever shows itself
Roughly stated, the argument has been that authors who wish to anticipate the imminent
implementation of hyphenation with &#173 would not like to see all those unwanted hyphens
that wouldn't go away until the task was completed.
(HTML&4.0 appeared about six-
and- a- half years ago.)
Consider something like "ruba-dubdub" again: the kinds of outcome an author might like to
specify include:
ruba-dubdub
no breaks allowed anywhere
rub&?hb>a-dubdub
allow (hyphen followed by break)
ruba&h?b>dubdub
hyphen followed by (allow break)
ruba-dub&?hb>dub
allow (hyphen followed by break)
Note the simplicity that follows from the introduction of the two bogus tags:
after all, hyphenation is markup.
Of course there are other ways to do the
tasks, such as:

我要回帖

更多关于 锡耶纳大学 的文章

 

随机推荐