外文翻译格式

外文文献翻译格式范例本科毕业设计（外文翻译）外文参考文献译文及原文学院信息工程学院专业信息工程（电子信息工程方向）年级班别 2006级（4）班学号 3206003186学生姓名柯思怡指导教师 ______ 田妮莉 _ __2010年6月目录熟悉微软SQL Server (1)1Section A 引言 (1)2Section B 再谈数据库可伸缩性 (4)3Section C 数据库开发的特点 (7)Get Your Arms around Microsoft SQL Server (9)1Section A Introduction to SQL Server 2005 (9)2Section B Database Scalability Revisited (13)3Section C Features for Database Development (17)熟悉微软SQL Server1 Section A 引言SQL Server 2005 是微软SQL生产线上最值得期待的产品。

在经过了上百万个邮件，成百上千的规范说明，以及数十次修订后。

微软承诺SQL Server 2005 是最新的基于Windows数据库应用的数据库开发平台。

这节的内容将指出SQL Server 2005产品的一些的重要特征。

SQL Server 2005几乎覆盖OLTP及OLAP技术的所又内容。

微软公司的这个旗舰数据库产品几乎能覆盖所有的东西。

这个软件在经过五年多的制作后，成为一个与它任何一个前辈产品都完全不同的产品。

本节将介绍整个产品的大部分功能。

当人们去寻求其想要的一些功能和技术时，可以从中提取出重要的和最感新区的内容，包括SQL Server Engine 的一些蜕变的历史，以及各种各样的SQL Server 2005的版本，可伸缩性，有效性，大型数据库的维护以及商业智能等如下：●数据库引擎增强技术。

SQL Server 2005 对数据库引擎进行了许多改进，并引入了新的功能。

本科毕业设计（论文）外文翻译基本规范一、要求1、与毕业论文分开单独成文。

2、两篇文献。

二、基本格式1、文献应以英、美等国家公开发表的文献为主（Journals from English speaking countries）。

2、毕业论文翻译是相对独立的，其中应该包括题目、作者（可以不翻译）、译文的出处（杂志的名称）（5号宋体、写在文稿左上角）、关键词、摘要、前言、正文、总结等几个部分。

3、文献翻译的字体、字号、序号等应与毕业论文格式要求完全一致。

4、文中所有的图表、致谢及参考文献均可以略去，但在文献翻译的末页标注：图表、致谢及参考文献已略去(见原文)。

（空一行，字体同正文）5、原文中出现的专用名词及人名、地名、参考文献可不翻译，并同原文一样在正文中标明出处。

二、毕业论文（设计）外文翻译（一）毕业论文（设计）外文翻译的内容要求外文翻译内容必须与所选课题相关，外文原文不少于6000个印刷符号。

译文末尾要用外文注明外文原文出处。

原文出处：期刊类文献书写方法：[序号]作者（不超过3人，多者用等或et al表示）.题（篇）名[J].刊名（版本）,出版年，卷次（期次）：起止页次.原文出处：图书类文献书写方法：[序号]作者.书名[M].版本.出版地：出版者,出版年.起止页次.原文出处：论文集类文献书写方法：[序号]作者.篇名[A].编著者.论文集名[C]. 出版地：出版者，出版年.起止页次。

要求有外文原文复印件。

（二）毕业论文（设计）外文翻译的撰写与装订的格式规范第一部分：封面1.封面格式:见“毕业论文（设计）外文翻译封面”。

普通A4纸打印即可。

第二部分：外文翻译主题1.标题一级标题，三号字，宋体，顶格，加粗二级标题，四号字，宋体，顶格，加粗三级标题，小四号字，宋体，顶格，加粗2.正文小四号字，宋体。

第三部分：版面要求论文开本大小：210mm×297mm（A4纸）版芯要求：左边距：25mm，右边距：25mm，上边距：30mm，下边距：25mm，页眉边距：23mm，页脚边距：18mm字符间距：标准行距：1.25倍页眉页角：页眉的奇数页书写—浙江师范大学学士学位论文外文翻译。

百度文库- 让每个人平等地提升自我！外文参考文献及翻译稿的要求及格式一、外文参考文献的要求1、外文原稿应与本研究项目接近或相关联；2、外文原稿可选择相关文章或节选章节，正文字数不少于1500字。

3、格式：外文文献左上角标注“外文参考资料”字样，小四宋体。

1.5倍行距。

标题：三号，Times New Roman字体加粗，居中，行距1.5倍。

段前段后空一行。

作者（居中）及正文：小四号，Times New Roman字体，首行空2字符。

4、A4纸统一打印。

二、中文翻译稿1、中文翻译稿要与外文文献匹配，翻译要正确；2、中文翻译稿另起一页；3、格式：左上角标“中文译文”，小四宋体。

标题：宋体三号加粗居中，行距1.5倍。

段前、段后空一行。

作者（居中）及正文：小四号宋体，数字等Times New Roman字体，1.5倍行距，首行空2字符。

正文字数1500左右。

4、A4纸统一打印。

格式范例如后所示。

百度文库 - 让每个人平等地提升自我！外文参考文献Implementation of internal controls of small andmedium-sized pow erStephen Ryan The enterprise internal control carries out the strength to refer to the enterprise internal control system execution ability and dynamics, it is the one whole set behavior and the technical system, is unique competitive advantage which the enterprise has; Is a series of …………………………标题：三号，Times New Roman字体加粗，居中，行距1.5倍。

附件5 论文及外文翻译写作格式样例附录1 内封格式示例（设置成小二号字，空3行）我国居民投资理财现状及发展前景的研究（黑体，加粗，小二，居中，空2行）The Research on Status and Future of Inhabitants’Investment and Financial Management in China （Times New Roman体，加粗，小二，居中，实词首字母大写，空5行）院系经济与管理学院（宋体，四号，首行缩进6字符）专业公共事业管理（宋体，四号，首行缩进6字符）班级 6408101 （宋体，四号，首行缩进6字符）学号 200604081010 （宋体，四号，首行缩进6字符）姓名李杰（宋体，四号，首行缩进6字符）指导教师张芸（宋体，四号，首行缩进6字符）职称副教授（宋体，四号，首行缩进6字符）负责教师（宋体，四号，首行缩进6字符）（空7行）沈阳航空航天大学（宋体，四号，居中）2010年6月（宋体，四号，居中）附录2 摘要格式示例（设置成三号，空2行）摘要（黑体，加粗，三号，居中，两个字之间空两格）（空1行）我国已经步入经济全球化发展的21世纪，随着市场经济的快速增长和对外开放的进一步深化，我国金融市场发生了巨大的变化。

一方面，投资理财所涉及到的领域越来越广，不仅仅是政府、企业、社会组织进行投资理财，居民也逐步进入到金融市场中，开始利用各种投资工具对个人、家庭财产进行打理，以达到资产保值、增值，更好的用于消费、养老等的目的；另一方面，我国居民投资理财观念逐渐趋于成熟化、理性化；同时，其投资理财工具以及方式手段亦越来越向多元化、完善化发展。

本论文以我国居民投资理财为研究对象，综合运用现代经济学、金融学和管理学的理论；统计学、概率学的方法和工具，主要对我国居民投资理财的历史演变、发展现状、意识观念、存在的问题和主要投资理财工具进行了分析和探讨，并提出了改善和促进我国居民理财现状的对策和建议，指出了普通居民合理化投资理财的途径。

毕业论文外文文献翻译要求
一、翻译的外文文献可以是一篇，也可以是两篇，但英文字符要求不少于2万
二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并在中文译文首页用“脚注”形式注明原文作者及出处，外文原文后应附中文译文。

三、中文译文的基本撰写格式为：
1.题目:采用三号、黑体字、居中打印；
2.正文:采用小四号、宋体字，行间距一般为固定值20磅，标准字符间距。

页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸。

四、英文的基本撰写格式为：
1.题目：采用三号、Times New Roman字、加黑、居中打印
2.正文：采用小四号、Times New Roman字。

行间距一般为固定值20磅，标准字符间距。

页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸.
3.脚注：五号,Times New Roman，顺序为作者.题目.出处，
五、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目,封面中文小四号宋体，英文小四号Times New Roman），
六、装订：左侧均匀装订，上下共两个钉，并按“封面、外文原文、译文”的顺序统一装订。

七、忌自行更改表格样式
大连工业大学艺术与信息工程学院
毕业设计(论文)外文文献
外文题目
翻译题目
系别
专业班级
学生姓名
指导教师
大连工业大学艺术与信息工程学院
毕业设计(论文)开题报告
题目名称
系别
专业班级
学生姓名
指导教师
开题报告日期年月日。

外文翻译指导记录怎么写外文翻译指导记录怎么写外文翻译、开题报告要求一套完整的毕业设计(论文)材料由外文翻译、开题报告和毕业设计(论文)正文三部分组成，按照统一的封面和格式编写。

和字体大小将按照学院的规定。

文本格式和书写要求（一）外文翻译通过文献综述和翻译，进一步提高外语运用能力，熟悉本专业几大外文书刊，了解国内外毕业设计(论文)信息和动态。

1、格式：（1）外文（译文前面附被翻译的外文原件复印件）；（2）翻译成中文格式：①标题②署名（作者名）** 著译者：***③翻译正文④外文著录为了反映文稿的科学依据和译者尊重他人研究成果的严肃态度以及向读者提出有关信息的出处，要求译者按著录/题名/出版事项顺序排列注明：期刊——著者，题名，期刊名称，出版年，卷号（期号），起始页码。

书籍——著者，书名、版次（第一版不标注），出版地，出版者，出版年，起始页码。

2、内容要求：（1）阅读每位学生在文献查阅环节中，必须阅读5～10万个印刷符号的外语文献资料（最好阅读与课题或本专业有联系的内容），择其重要的翻译1～2万个印刷符号（约3000汉字）。

（2）翻译①标题应真实地反映出翻译外文的主体内容或原外文标题内容，一般控制在20个汉字以内。

可以用副标题对标题予以补充说明；②标题下方正中为外文作者署名；③外文翻译成中文的内容；④外文著录（二）开题报告1、格式：（1）课题名称；（2）学生、专业、指导教师和教学单位署名；（3）开题报告的正文撰写。

2、内容要求：（1）课题名称要求与毕业设计（论文）正文标题名称一致（一般控制在20个汉字以内，可以用副标题对标题予以补充说明）。

（2）学生、指导教师和教学单位署名：题目下方中间是学生签名，学生签名下方是专业名称，专业名称下方是指导老师签名，指导老师签名下方是教学单位签名(教学单位指学院)。

（3）开题报告的正文撰写要求包括（不少于2500字）：①课题来源②研究目的和意义③研究的内容与途径④国内外研究现状与发展趋势通过提问和分析问题，综合前人文献提出的理论和事实，比较各种学术观点，明确所提问题的历史、现状和发展方向。

杭州电子科技大学毕业论文外文文献翻译要求根据《普通高等学校本科毕业设计（论文）指导》的内容，特对外文文献翻译提出以下要求：一、翻译的外文文献可以是一篇，也可以是两篇，但总字符要求不少于1.5万（或翻译成中文后至少在3000字以上）。

二、翻译的外文文献应主要选自学术期刊、学术会议的文章、有关著作及其他相关材料，应与毕业论文（设计）主题相关，并作为外文参考文献列入毕业论文（设计）的参考文献。

并在每篇中文译文首页用“脚注”形式注明原文作者及出处，中文译文后应附外文原文。

脚注的方法：插入----引用---脚注和尾注三、中文译文的基本撰写格式为：1.题目:采用小三号、黑体字、居中打印；2.正文:采用小四号、宋体字，行间距为固定值20磅，标准字符间距。

页边距为左3cm，右2.5cm，上下各2.5cm，页面统一采用A4纸。

英文原文如为word文档，请用罗马字体排版，段前空两格。

从正文开始编写页码，页码居中。

四、封面格式由学校统一制作（注：封面上的“翻译题目”指中文译文的题目），填充内容为加粗小三号楷体_GB2312，并按“封面、译文一、外文原文一、译文二、外文原文二、考核表”的顺序统一装订。

五、忌自行更改表格样式，学号请写完整。

封面和考核表均为一页纸张，勿换行换页。

毕业论文外文文献翻译毕业设计（论文）题目Xxx翻译（1）题目指翻译后的中文译文的题目翻译（2）题目指翻译后的中文译文的题目学院会计学院（以本模板为准）专业会计学（以本模板为准）姓名XXXXXX（以本模板为准）班级XX020811（以本模板为准）学号XX023101（以本模板为准）指导教师XXXXXX（以本模板为准）外文翻译考核表。

翻译规范——Format（2011年修订版）请仔细阅读以下规定。

本篇大部分规定为格式方面的规定，而部分翻译项目则可能对其格式另有特殊规定。

1. SPACE（空格）除非有特别指示，请在每个翻译项目的中文文字（双字节字符）和英文字或数字（均为单字节）之间留一个单字节空格。

Example 1:今天是2002 年5 月26 日正确。

今天是2002 年5 月26 日错误，数字前没有留出一个单字节空格。

今天是2002 年5 月26 日错误，2 个中文字间无需留出一个空格。

欲知以上各行间有何区别，可到Word > 工具> 选项> 视图> “格式标记”下选择“全部”或者“隐藏文字”。

Example 2:熟练操作WINDOWS 98 中文环境。

在“作”和“W”，“S”和“9”，及“8”和“中”之间都需要留出一个空格。

英文字或数字位于句首或句末的，则无需留空。

Example 1:2002 年5 月26 日是个重要的日子。

正确。

2002 年5 月26 日是个重要的日子错误，句首无须留出一个空格。

Example 2:他的英文名叫做John。

正确。

他的英文名叫做John 。

地址: 福州左海帝景3座1105室网址: 错误，句末无须留出一个空格。

2. PUNCTUATION（标点符号）usage1) 中文须使用双字节标点符号，如，。

、“”！；：; 英文则须使用单字节标点符号, . , “” ! ; :。

双字节标点符号和单字节标点符号的区示：输入状态不同，即双字节标点符号须在中文输入状态下输入，而单字节标点符号须在英文状态下输入；For example:“计算机世界”杂志要用双字节引号，“Computer World” 应使用单字节英文引号。

2) 英文中并列的单字节逗号“,”，中文翻译要改成双字节顿号“、” 等。

3) 书名、协议名称、法律合同规章名称译成英文时应该采用斜体形式，中文时则应在其名称前后加上书名号《》。

因为学校对毕业论文中的外文翻译并无规定，为统一起见，特做以下要求：1、每篇字数为1500字左右，共两篇；2、每篇由两部分组成：译文 +原文。

3 附件中是一篇范本，具体字号、字体已标注。

外文翻译（包含原文）（宋体四号加粗）外文翻译一（宋体四号加粗）作者：（宋体小四号加粗）Kim Mee Hyun Director, Policy Research & Development Team, Korean Film Council （小四号）出处：（宋体小四号加粗）Korean Cinema from Origins to RenaissanceP358~P34C）韩国电影的发展及前景（标题：宋体四号加粗）1996~现在在过去的十年间，韩国电影经历了难以置信的增长。

上个世纪60年代，韩国电影迅速崛起，然而很快便陷入停滞状态，直到90年代以后，韩国电影又重新进入繁盛时期。

在这个时期，韩国电影在数量上并没有大幅的增长，但多部电影的观影人数达到了上千万人次。

1996年，韩国本土电影的市场占有量只有23.1%。

但是到了1998年，市场占有量增长到35.8%,到2001年更是达到了50% 虽然从1996年开始，韩国电影一直处在不断上升的过程中，但是直到1999年姜帝圭导演的《生死谍变》的成功才诞生了韩国电影的又一个高峰。

虽然《生死谍变》创造了韩国电影史上的最高电影票房纪录，但是1999年以后最高票房纪录几乎每年都会被刷新。

当人们都在津津乐道所谓的“韩国大片”时，2000年朴赞郁导演的《共同警备区JSA〉和2001年郭暻泽导演的《朋友》均成功刷新了韩国电影最高票房纪录。

2003年康佑硕导演的《实尾岛》和2004年姜帝圭导演的又一部力作《太极旗飘扬》开创了观影人数上千万人次的时代。

姜帝圭和康佑硕导演在韩国电影票房史上扮演了十分重要的角色。

从1993年的《特警冤家》到2003年的《实尾岛》，康佑硕导演了多部成功的电影。

成都东软学院外文资料和译文格式要求一、译文必须采用计算机输入、打印，幅面A4。

外文资料原文（复印或打印）在前，译文在后，于左侧装订。

二、具体要求1、至少翻译一篇内容与所选课题相关的外文文献。

2、译文汉字字数不少于4000字。

3、正文格式要求：宋体五号字。

译文格式参见《译文格式要求》，宋体五号字，单倍行距。

纸张纸张为A4纸，页边距上2.54cm、下2.54cm、左3.17cm、右3.17cm。

装订外文资料原文（复印或打印）在前，译文在后封面封面的专业、班级、姓名、学号等信息要全部填写正确。

封面指导教师必须为讲师以上职称，若助教则需要配备一名讲师协助指导。

讲师在前，助教在后。

指导教师姓名后面空一个中文空格，加职称。

页眉页眉说明宋体小五，左端“XX学院毕业设计（论文）”，右端“译文”。

页眉中的学院名称要与封面学院名称一致。

字数本科4000字。

附：外文资料和译文封面、空白页成都东软学院外文资料和译文专业：软件工程移动互联网应用开发班级：2班姓名：罗荣昆学号：12310420216指导教师：2015年 12月 8日Android page layoutUsing XML-Based LayoutsW hile it is technically possible to create and attach widgets to our activity purely through Java code, the way we did in Chapter 4, the more common approach is to use an XML-based layout file. Dynamic instantiation of widgets is reserved for more complicated scenarios, where the widgets are not known at compile-time (e g., populating a column of radio buttons based on data retrieved off the Internet).With that in mind, it’s time to break out the XML and learn how to lay out Android activities that way.What Is an XML-Based Layout?As the name suggests, an XML-based layout is a specification of widgets’ relationships to each other—and to their containers (more on this in Chapter 7)—encoded in XML format. Specifi cally, Android considers XML-based layouts to be resources, and as such layout files are stored in the res/layout directory inside your Android project.Each XML file contains a tree of elements specifying a layout of widgets and their containers that make up one view hierarchy. The attributes of the XML elements are properties, describing how a widget should look or how a container should behave. For example, if a Button element has an attribute value of android:textStyle = "bold", that means that the text appearing on the face of the button should be rendered in a boldface font style.Android’s SDK ships with a tool (aapt) which uses the layouts. This tool should be automatically invoked by your Android tool chain (e.g., Eclipse, Ant’s build.xml). Of particular importance to you as a developer is that aapt generates the R.java source file within your project, allowing you to access layouts and widgets within those layouts directly from your Java code. Why Use XML-Based Layouts?Most everything you do using XML layout files can be achieved through Java code. For example, you could use setTypeface() to have a button render its textin bold, instead of using a property in an XML layout. Since XML layouts are yet another file for you to keep track of, we need good reasons for using such files.Perhaps the biggest reason is to assist in the creation of tools for view definition, such as a GUI builder in an IDE like Eclipse or a dedicated Android GUI designer like DroidDraw1. Such GUI builders could, in principle, generate Java code instead of XML. The challenge is re-reading the UI definition to support edits—that is far simpler if the data is in a structured format like XML than in a programming language. Moreover, keeping generated XML definitions separated from hand-written Java code makes it less likely that somebody’s custom-crafted source will get clobbered by accident when the generated bits get re-generated. XML forms a nice middle ground between something that is easy for tool-writers to use and easy for programmers to work with by hand as needed.Also, XML as a GUI definition format is becoming more commonplace. Microsoft’s XAML2, Adobe’s Flex3, and Mozilla’s XUL4 all take a similar approach to that of Android: put layout details in an XML file and put programming smarts in source files (e.g., JavaScript for XUL). Many less-well-known GUI frameworks, such as ZK5, also use XML for view definition. While “following the herd” is not necessarily the best policy, it does have the advantage of helping to ease the transition into Android from any other XML-centered view description language. OK, So What Does It Look Like?Here is the Button from the previous chapter’s sample application, converted into an XMLlayout file, found in the Layouts/NowRedux sample project. This code sample along with all others in this chapter can be found in the Source Code area of .<?xml version="1.0" encoding="utf-8"?><Button xmlns:android="/apk/res/android"android:id="@+id/button"android:text=""android:layout_width="fill_parent"android:layout_height="fill_parent"/>The class name of the widget—Button—forms the name of the XML element. Since Button is an Android-supplied widget, we can just use the bare class name. If you create your own widgets as subclasses of android.view.View, you would need to provide a full package declara tion as well.The root element needs to declare the Android XML namespace:xmlns:android="/apk/res/android"All other elements will be children of the root and will inherit that namespace declaration.Because we want to reference this button from our Java code, we need to give it an identifier via the android:id attribute. We will cover this concept in greater detail later in this chapter.The remaining attributes are properties of this Button instance:• android:text indicates the initial text to be displayed on the button face (in this case, an empty string)• android:layout_width and android:layout_height tell Android to have the button’swidth and height fill the “parent”, in this case the entire screen—these attributes will be covered in greater detail in Chapter 7.Since this single widget is the only content in our activity, we only need this single element. Complex UIs will require a whole tree of elements, representing the widgets and containers that control their positioning. All the remaining chapters of this book will use the XML layout form whenever practical, so there are dozens of other examples of more complex layouts for you to peruse from Chapter 7 onward.What’s with the @ Signs?Many widgets and containers only need to appear in the XML layout file and do not need to be referenced in your Java code. For example, a static label (TextView) frequently only needs to be in the layout file to indicate where it should appear. These sorts of elements in the XML file do not need to have the android:id attribute to give them a name.Anything you do want to use in your Java source, though, needs an android:id.The convention is to use @+id/... as the id value, where the ... represents your locally unique name for the widget in question. In the XML layout example in the preceding section, @+id/button is the identifier for the Button widget.Android provides a few special android:id values, of the form @android:id/.... We will see some of these in various chapters of this book, such as Chapters 8 and 10.We Attach These to the Java How?Given that you have painstakingly set up the widgets and containers in an XML layout filenamed main.xml stored in res/layout, all you need is one statement in your activity’s onCreate() callback to use that layout:setContentView(yout.main);This is the same setContentView() we used earlier, passing it an instance of a View subclass (in that case, a Button). The Android-built view, constructed from our layout, is accessed from that code-generated R class. All of the layouts are accessible under yout, keyed by the base name of the layout file—main.xml results in yout.main.To access our identified widgets, use findViewById(), passing in the numeric identifier of the widget in question. That numeric identifier was generated by Android in the R class asR.id.something (where something is the specific widget you are seeking). Those widgets are simply subclasses of View, just like the Button instance we created in Chapter 4.The Rest of the StoryIn the original Now demo, the button’s face would show the current time, which would reflect when the button was last pushed (or when the activity was first shown, if the button had not yet been pushed).Most of that logic still works, even in this revised demo (NowRedux). However,rather than instantiating the Button in our activity’s onCreate() callback, we can reference the one from the XML layout:package youts;import android.app.Activity;import android.os.Bundle;import android.view.View;import android.widget.Button; import java.util.Date;public class NowRedux extends Activity implements View.OnClickListener { Button btn;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);btn=(Button)findViewById(R.id.button);btn.setOnClickListener(this);upd ateTime();}public void onClick(View view) { updateTime();}private void updateTime() {btn.setText(new Date().toString()); }}The first difference is that rather than setting the content view to be a view we created in Java code, we set it to reference the XML layout (setContentView(yout.main)). The R.java source file will be updated when we rebuild this project to include a reference to our layout file (stored as main.xml in our project’s res/l ayout directory).The other difference is that we need to get our hands on our Button instance, for which we use the findViewById() call. Since we identified our button as @+id/button, we can reference the button’s identifier as R.id.button. Now, with the Button instance in hand, we can set the callback and set the label as needed.As you can see in Figure 5-1, the results look the same as with the originalNow demo.Figure 5-1. The NowRedux sample activity Employing Basic WidgetsE very GUI toolkit has some basic widgets: fields, labels, buttons, etc. Android’s toolkit is no different in scope, and the basic widgets will provide a good introduction as to how widgets work in Android activities.Assigning LabelsThe simplest widget is the label, referred to in Android as a TextView. Like in most GUI toolkits, labels are bits of text not editable directly by users. Typically, they are used to identify adjacent widgets (e.g., a “Name:” label before a field where one fills in a name).In Java, you can create a label by creating a TextView instance. More commonly, though, you will create labels in XML layout files by adding a TextView element to the layout, with an android:text property to set the value of the label itself. If you need to swap labels based on certain criteria, such as internationalization, you may wish to use a resource reference in the XML instead, as will be described in Chapter 9. TextView has numerous other properties of relevance for labels, such as:• android:typeface to set the typeface to use for the label (e.g., monospace) • android:textStyle to indicate that the typeface should be made bold (bold), italic (italic),or bold and italic (bold_italic)• android:textColor to set the color of the label’s text, in RGB hex format (e.g., #FF0000 for red)For example, in the Basic/Label project, you will find the following layout file:<?xml version="1.0" encoding="utf-8"?><TextView xmlns:android=/apk/res/androidandroid:layout_width="fill_parent"android:layout_height="wrap_content"android:text="You were expecting something profound?" />As you can see in Figure 6-1, just that layout alone, with the stub Java source provided by Android’s p roject builder (e.g., activityCreator), gives you the application.Figure 6-1. The LabelDemo sample applicationButton, Button, Who’s Got the Button?We’ve already seen the use of the Button widget in Chapters 4 and 5. As it turns out, Button is a subclass of TextView, so everything discussed in the preceding section in terms of formatting the face of the button still holds. Fleeting ImagesAndroid has two widgets to help you embed images in your activities: ImageView and ImageButton. As the names suggest, they are image-based analogues to TextView and Button, respectively.Each widget takes an android:src attribute (in an XML layout) to specify what picture to use. These usually reference a drawable resource, described in greater detail in the chapter on resources. You can also set the image content based on a Uri from a content provider via setImageURI().ImageButton, a subclass of ImageView, mixes in the standard Button behaviors, for responding to clicks and whatnot.For example, take a peek at the main.xml layout from the Basic/ImageView sample project which is found along with all other code samples at : <?xml version="1.0" encoding="utf-8"?><ImageView xmlns:android=/apk/res/androidandroid:id="@+id/icon"android:layout_width="fill_parent"android:layout_height="fill_parent"android:adjustViewBounds="true"android:src="@drawable/molecule" />The result, just using the code-generated activity, is shown in Figure 6-2.Figure 6-2. The ImageViewDemo sample applicationFields of Green. Or Other Colors.Along with buttons and labels, fields are the third “anchor” of most GUI toolkits. In Android, they are implemented via the EditText widget, which is a subclass of the TextView used for labels.Along with the standard TextView properties (e.g., android:textStyle), EditText has many others that will be useful for you in constructing fields, including:• android:autoText, to control if the fie ld should provide automatic spelling assistance• android:capitalize, to control if the field should automatically capitalize the first letter of entered text (e.g., first name, city) • android:digits, to configure the field to accept only certain digi ts • android:singleLine, to control if the field is for single-line input or multiple-line input (e.g., does <Enter> move you to the next widget or add a newline?)Beyond those, you can configure fields to use specialized input methods, such asandroid:numeric for numeric-only input, android:password for shrouded password input,and android:phoneNumber for entering in phone numbers. If you want to create your own input method scheme (e.g., postal codes, Social Security numbers), you need to create your own implementation of the InputMethod interface, then configure the field to use it via android: inputMethod.For example, from the Basic/Field project, here is an XML layout file showing an EditText:<?xml version="1.0" encoding="utf-8"?><EditTextxmlns:android=/apk/res/androidandroid:id="@+id/field"android:layout_width="fill_parent"android:layout_height="fill_parent"android:singleLine="false" />Note that android:singleLine is false, so users will be able to enter in several lines of text. For this project, the FieldDemo.java file populates the input field with some prose:package monsware.android.basic;import android.app.Activity;import android.os.Bundle;import android.widget.EditText;public class FieldDemo extends Activity { @Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);EditText fld=(EditText)findViewById(R.id.field);fld.setText("Licensed under the Apache License, Version 2.0 " + "(the \"License\"); you may not use this file " + "except in compliance with the License. You may " + "obtain a copy of the License at " +"/licenses/LICENSE-2.0");}}The result, once built and installed into the emulator, is shown in Figure 6-3.Figure 6-3. The FieldDemo sample applicationNote Android’s emulator only allows one application in the launcher per unique Java package. Since all the demos in this chapter share the monsware.android.basic package, you will only see one of these demos in your emulator’s launcher at any one time.Another flavor of field is one that offers auto-completion, to help users supply a value without typing in the whole text. That is provided in Android as the AutoCompleteTextView widget and is discussed in Chapter 8.Just Another Box to CheckThe classic checkbox has two states: checked and unchecked. Clicking the checkbox toggles between those states to indicate a choice (e.g., “Ad d rush delivery to my order”). In Android, there is a CheckBox widget to meet this need. It has TextView as an ancestor, so you can use TextView properties likeandroid:textColor to format the widget. Within Java, you can invoke: • isChecked() to determi ne if the checkbox has been checked• setChecked() to force the checkbox into a checked or unchecked state • toggle() to toggle the checkbox as if the user checked itAlso, you can register a listener object (in this case, an instance of OnCheckedChangeListener) to be notified when the state of the checkbox changes.For example, from the Basic/CheckBox project, here is a simple checkbox layout:<?xml version="1.0" encoding="utf-8"?><CheckBox xmlns:android="/apk/res/android"android:id="@+id/check"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="This checkbox is: unchecked" />The corresponding CheckBoxDemo.java retrieves and configures the behavior of the checkbox:public class CheckBoxDemo extends Activityimplements CompoundButton.OnCheckedChangeListener { CheckBox cb;@Overridepublic void onCreate(Bundle icicle) { super.onCreate(icicle);setContentView(yout.main);cb=(CheckBox)findViewById(R.id.check);cb.setOnCheckedChangeListener(this);}public void onCheckedChanged(CompoundButton buttonView,boolean isChecked) {if (isChecked) {cb.setText("This checkbox is: checked");}else {cb.setText("This checkbox is: unchecked");}}}Note that the activity serves as its own listener for checkbox state changes since it imple ments the OnCheckedChangeListener interface (via cb.setOnCheckedChangeListener(this)). The callback for the listener is onCheckedChanged(), which receives the checkbox whose state has changed and what the new state is. In this case, we update the text of the checkbox to reflect what the actual box contains.The result? Clicking the checkbox immediately updates its text, as you can see in Figures 6-4 and 6-5.Figure 6-4. The CheckBoxDemo sample application, with the checkbox uncheckedFigure 6-5. The same application, now with the checkbox checkedTurn the Radio UpAs with other implementations of radio buttons in other toolkits, Android’s radio buttons are two-state, like checkboxes, but can be grouped such that only one radio button in the group can be checked at any time.Like CheckBox, RadioButton inherits from CompoundButton, which in turn inherits fromTextView. Hence, all the standard TextView properties for font face, style, color, etc., are available for controlling the look of radio buttons. Similarly, you can call isChecked() on a RadioButton to see if it is selected, toggle() to select it, and so on, like you can with a CheckBox.Most times, you will want to put your RadioButton widgets inside of aRadioGroup. The RadioGroup indicates a set of radio buttons whose state is tied, meaning only one button out of the group can be selected at any time. If you assign an android:id to your RadioGroup in your XML layout, you can access the group from your Java code and invoke:• check() to check a specific radio button via its ID (e.g., group.check(R.id.radio1))• clearCheck() to clear all radio buttons, so none in the group are checked• getCheckedRadioButtonId() to get the ID of the currently-checked radio button (or -1 if none are checked)For example, from the Basic/RadioButton sample application, here is an XML layout showing a RadioGroup wrapping a set of RadioButton widgets: <?xml version="1.0" encoding="utf-8"?> <RadioGroupxmlns:android=/apk/res/androidandroid:orientation="vertical"android:layout_width="fill_parent"android:layout_height="fill_parent" ><RadioButton android:id="@+id/radio1"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Rock" /><RadioButton android:id="@+id/radio2"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Scissors" /><RadioButton android:id="@+id/radio3"android:layout_width="wrap_content"android:layout_height="wrap_content"android:text="Paper" /></RadioGroup>Figure 6-6 shows the result using the stock Android-generated Java forthe project and this layout.Figure 6-6. The RadioButtonDemo sample application Note that the radio button group is initially set to be completely unchecked at the outset. To pre-set one of the radio buttons to be checked, use either setChecked() on the RadioButton or check() on the RadioGroup from within your onCreate() callback in your activity.It’s Quite a ViewAll widgets, including the ones previously shown, extend View, and as such give all widgets an array of useful properties and methods beyond those already described.Useful PropertiesSome of the properties on View most likely to be used include:• Controls the focus sequence:• android:nextFocusDown• android:nextFocusLeft• android:nextFocusRight• android:nextFocusUp• android:visibility, which controls wheth er the widget is initially visible• android:background, which typically provides an RGB color value (e.g., #00FF00 for green) to serve as the background for the widgetUseful MethodsYou can toggle whether or not a widget is enabled via setEnabled() and see if it is enabled via isEnabled(). One common use pattern for this is to disable some widgets based on a CheckBox or RadioButton selection.You can give a widget focus via requestFocus() and see if it is focused via isFocused(). You might use this in concert with disabling widgets as previously mentioned, to ensure the proper widget has the focus once your disabling operation is complete.To help navigate the tree of widgets and containers that make up an activity’s overall view, you can use:• get Parent() to find the parent widget or container• findViewById() to find a child widget with a certain ID• getRootView() to get the root of the tree (e.g., what you provided to the activity via setContentView())Android 页面布局使用XML进行布局虽然纯粹通过Java代码在activity上创建和添加部件，在技术上是可行的，我们在第4章中做的一样，更常见的方法是使用一种基于XML的布局文件。