程序代码:
word-break : normal | break-all | keep-all
参数:normal :
依照亚洲语言和非亚洲语言的文本规则,允许在字内换行
break-all : 该行为与亚洲语言的normal相同。也允许非亚洲语言文本行的任意字内断开,该值适合包含一些非亚洲文本的亚洲文本(英文会在因为长度的限制在单词中间断开)
keep-all : 与所有非亚洲语言的normal相同。对于中文,韩文,日文,不允许字断开。适合包含少量亚洲文本的非亚洲文本
试验结果:
normal :汉字正常断开,英文单词不断开。
break-all :汉字正常断开,英文单词断开。
keep-all :汉字不断开(好像是断开必须要有标点符号),英文单词不断开。
所以跟人感觉可以使用normal 或者break-all
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style>
table
{width:240pt;
margin-left:17.6pt;
word-break:normal;
}
</style>
<title>无标题文档</title>
</head>
<table border="1">
<tr>
<td width=100>王一是杭州一家报纸的记者,他获奖组照中的第7张投稿照片天空有云彩,而原片天空是空白的,是作者自己合成所致。在致组委会的声明中,王一称:“由于我不谨慎,在给‘金镜头’摄影比赛上传图片的时候弄错了一张照片,就是《为什么不回家》的第7张图片(孩子在法院车后追逐的图片),上传的这张是图片天空是经过PS了的。本来这张图片是不准备上传的,但因为它和没PS的原图放在了一起,在刻光盘的时候不慎取错了。在网上发现这组照片获奖,看到这张图片后,感觉有必要向比赛组委会说明,所以我在第一时间里立即向‘金镜头’组委会的有关人员说明了这一情况,并在此向‘金镜头’组委会表示深深的歉意。”组委会工作人员在向评委会宣读声明时,同时陈述了该作者在电话中向组委会申请取消《为什么不回家》获奖资格,并声明“PS行为”是作者本人行为,与其供职单位无关。评委王景春向记者透露,现在评委会已确定要取消奖项。</td></td>
<td width=440>Traditionally, most defects in implementation that aren't business logic-specific can be traced back to memory management and object lifecycle issues. These defects include memory leaks, cyclic reference counts, the failure to release an object, the failure to free allocated memory, accessing already de-allocated objects, accessing not yet allocated memory or objects, and so on. Writing impeccable code is possible, but it takes years of experience, iron discipline, a mature development process, commitment to quality from management, and strict coding and development standards, such as code reviews and quality control. Most software organizations today lack most of these ingredients. To cope with this reality, .NET aims at simplifying component development to bridge the skill gap and increase the quality of the resulting code. .NET relieves developers of almost all the burden of memory allocation for objects, memory de-allocation, and object lifecycle management. This chapter describes the .NET solution for memory and object lifecycle management and its implications for the programming model, including the pitfalls and workarounds that component developers need to apply.</td>
</tr>
</table>
<body>
</body>
</html>